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
Message-ID:	<37688D3D.E572808C@1c.ru>
Date:	Thu, 17 Jun 1999 09:53:01 +0400
From:	Vadim Egorov <egorovv AT 1c DOT ru>
X-Mailer:	Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language:	ru,en
MIME-Version:	1.0
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: yikes, what are these?
References:	<199906162102 DOT RAA21060 AT jaj DOT com>
X-MDaemon-Deliver-To:	cygwin AT sourceware DOT cygnus DOT com
X-Return-Path:	EgorovV AT 1c DOT ru

Hello,

Yes, I had to build one of the recent egcs snapshots from sources but it
was quite painless. I used Jan 15 cygwin snapshot -- it might have made 
the trick -- and Mumit Khan's egcs-1.1.2 on the top of WinNT 4.0 sp5.  

To have the same directory structure as clean B20.1 installation I run
configure scripts using i586-cygwin32 as host parameter.

BTW, you can take gcc-2.95 dev snapshot binaries from Mumit Khan's site.

Regards,
Vadim


Phil Edwards wrote:
> 
> 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

-- 
*********************************************
Vadim Egorov, 1C      *       ÷ÁÄÉÍ åÇÏÒÏ×,1C
egorovv AT 1c DOT ru         *         egorovv AT 1c DOT ru
*********************************************


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

- Raw text -