Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Wed, 16 Jun 1999 17:02:17 -0400
From:	Phil Edwards <pedwards AT jaj DOT com>
Message-Id:	<199906162102.RAA21060@jaj.com>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	yikes, what are these?

Well, I was heartened by the news that people had gotten some of the not-
overly-recent EGCS snapshots to build under Cygwin.  So, after reinstalling
B20.1 and setting up some mounts, I tried to configure:

[6]> ../srcdir/egcs-19990502/configure --prefix=/home/EGCS
Configuring for a i586-pc-cygwin32 host.
    0       0 [main] D:\cygnus\cygwin-b20\H-i586-cygwin32\bin\sh.exe 1088 fhandler_base::fork_fixup: ../srcdir/egcs-19990502/move-if-change - Win32 error 6, handle 0xEC
fork: ResumeThread failed, rc = 0, Win32 error 6../srcdir/egcs-19990502/configure: Cannot fork
    0       0 [proc] D:\cygnus\cygwin-b20\H-i586-cygwin32\bin\sh.exe 1117 wait_subproc: wait failed.  nchildren 1, wait -1, Win32 error 6
    0    2007 [proc] sh 1117 wait_subproc: event[1] 0x20, Win32 error 6
[a ^C finally took effect here]
[7]> 


I hope these numbers mean something more to somebody out there than they
do to me...

My next thought was to look at the developer's snapshots, in case there
were any obvious nots in a ChangeLog.  I grabbed a recent cygwin-inst,
but the major subdirectory ("usr" in Earnie's scheme) was named
i586-pc-cygwin32 instead of i586-cygwin32.  All of the binaries would
still have been looking in the wrong directory, so I'm not certain what
I should have done there.

Am I jumping the gun on the next release?  Should I wait for B21 or keep
pushing on this one?


(If you reply to the list, please don't cc another copy to me.  Thanks!)
Phil


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

- Raw text -