From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ron Huber To: cygwin@sourceware.cygnus.com Subject: Re: fork errors Date: Thu, 06 Apr 2000 14:28:00 -0000 Message-id: <3.0.32.20000406141723.01af2510@carrera.sd.inri.com> X-SW-Source: 2000-04/msg00054.html 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