Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <199906272326.SAA19813@mercury.xraylith.wisc.edu>
To: Chris Faylor <cgf AT cygnus DOT com>
cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Hey! A snapshot! 
In-Reply-To: Your message of "Sun, 27 Jun 1999 18:44:06 EDT."
             <19990627184406 DOT A8416 AT cygnus DOT com> 
Date: Sun, 27 Jun 1999 18:26:13 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Chris Faylor <cgf AT cygnus DOT com> writes:
> On Sun, Jun 27, 1999 at 04:36:15PM -0500, Mumit Khan wrote:
> >Could you please explain a bit what these problems are/were and what
> >workarounds are needed? 
> 
> I would if I could.  One problem was an internal compiler error when
> compiling syscalls.cc.  Another was a "cc1 looping" problem when
> compiling environ.cc and others.
> 
> I believe that both were due to internal Cygnus development that hadn't
> hit EGCS yet, but I could be mistaken.

I haven't seen either, so it must be due to what you suspect. Glad things
are working now.

fyi, I can build 1999-06-26 with gcc-2.95-1999-06-26.

Regards,
Mumit