public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Rau" <larry@savaJe.com>
To: <cygwin@sourceware.cygnus.com>
Subject: fork_copy error
Date: Mon, 20 Mar 2000 23:13:00 -0000	[thread overview]
Message-ID: <NDBBJBEKCLPIHDFIFMKKCEJCCHAA.larry@savaJe.com> (raw)

On win98 se2 with cygwin version:
BASH.EXE-2.02$ uname -a
CYGWIN_98-4.10 POWERPLAY 1.1.0(0.18/3/2) 2000-03-20 00:14:57 i586 unknown

I get the following error during a large make (around 5k files
don't know where it fails.. bunch of javac launches)

0 [main] MAKE 1003 fork_copy: user/cygwin data pass 2 failed, 0x4580000..0
x47E5000, done 0, Win32 error 8
make: vfork: No more processes

Once this occurs if I re-run the make it will process some more
files and then give the same error. Eventually make will just fail
to run anymore compiles (in this case always javac).  The only way
to cure it is to reboot win98.  Exiting all bash shell's is not 
enough.  The rest of win98 appears to function ok (well normal) as
far as I can tell.

Does anyone else experience this?  On smaller makes running gcc I
have not had a problem.  

Is Win2k much more stable for using cygwin?  I've been thinking of
upgrading as I think my main tools will run on win2k: gcc,cygwin,wincvs.

.........

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2000-03-20 23:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 23:13 Larry Rau [this message]
2000-03-21  5:13 Earnie Boyd
2000-03-21  8:41 ` Chris Faylor
2000-03-21 14:11 ` Larry Rau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NDBBJBEKCLPIHDFIFMKKCEJCCHAA.larry@savaJe.com \
    --to=larry@savaje.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).