I did some more investigation and found that 4nt
sets the environment variable COMSPEC=c:\bin\4NT.EXE
After quitting the 4nt shell COMPSEC reverts to
COMSPEC=C:\WINNT35\system32\cmd.exe.
It appears that 4NT may be unsuitable for the task
at hand is more suitable as an interactive shell as
suggested in the code of execunix.c.
An idea which works is to set JAMSHELL as:
if $(NT) {
JAMSHELL = C:\\WINNT35\\system32\\cmd.exe /c % ;
}
in ones Jamfile (is Jambase preferred ?).
N.B.
JAMSHELL = C:\WINNT35\system32\cmd.exe /c % ;
(without the escaped \, fails miserably).
Hope this helps someone.. (including myself :-))
Cheers,
Kirk.
Kirk Abbott wrote:
I just upgraded to jam2.2 and managed to get it
bootstrapped using make. The last step of the
bootstrapping processing is to invoke jam0 to
build itself. Then everything just seems to hang,
i.e it just seems to compile 1 file then stop.
After poking around for a while I started typing
in exits at the command prompt and then the compilation
process resumed. If one does this a sufficient number
of times then the compilation stops.
Has anyone seen this before ?
Is a workaround to set JAMSHELL to be command.com or cmd.exe ?
I am using NT4.0.
Actually quitting from 4NT and just running from cmd.exe
does work.
Cheers,
Kirk.
1 message in com.perforce.jammingjam locking up under 4NT shell again
