This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: fork errors
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: fork errors
- From: Ron Huber <rhuber at sd dot inri dot com>
- Date: Thu, 06 Apr 2000 14:17:23 -0700
Thanks Larry for the response,
Reviewed the mailing list. Did not see any answers.
We are using Cygwin B20 12/1/98. What is the later and greater?
How do I get patches? Costs? Can I get a demo to verify that
indead this will fix the problem?
Have a snap shot of the log below:
-------------------------------------------------------
MagVar.cpp
________ cd dll';' make vlibs
__________ cd Loader';' make vlibs
sh F:\ICSF_nightly\ICSFBuild/VMKDEV/etc/mkdirhier
F:\ICSF_nightly\ICSFBuild\Windows_NT.4.0/JMV\obj\libLoadMagVar
F:\ICSF_nightly\ICSFBuild/VMKDEV/etc/mkdirhier: Cannot fork
NMAKE : fatal
error U1077: 'sh' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'vmake' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'vmake' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'vmake' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'vmake' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'vmake' : return code '0x2'
Stop.
-------------------------------------------------------
Watching the Task Manager there seems to be plenty of memory and CPU power.
We also defrag prior to the checkout/build.
The weird thing about this is not everyone building on NT
gets these fork errors. Could it be another process
running at the same time?
More ideas? Thanks
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com