Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <20000407122854.21265.qmail@web113.yahoomail.com>
Date: Fri, 7 Apr 2000 05:28:54 -0700 (PDT)
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: earnie_boyd AT yahoo DOT com
Subject: Re: fork errors
To: Ron Huber <rhuber AT sd DOT inri DOT com>, cygwin AT sourceware DOT cygnus DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

This appears to be a setup problem to me.  Paste the output of `cygcheck -b -r
-s' in a mail.

Earnie.

--- Ron Huber <rhuber AT sd DOT inri DOT com> wrote:
> 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 AT sourceware DOT cygnus DOT com
> 
> 

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com