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: <199907110041.TAA23918@mercury.xraylith.wisc.edu>
To: "K. Haley" <khaley AT bigfoot DOT com>
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Anyone using gcc-2.95 pre on win95? 
In-Reply-To: Your message of "Sat, 10 Jul 1999 15:54:29 MDT."
             <4 DOT 1 DOT 19990710154717 DOT 00942970 AT pop DOT mail DOT yahoo DOT com> 
Date: Sat, 10 Jul 1999 19:41:19 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

"K. Haley" <khaley AT bigfoot DOT com> writes:
> I've seen this problem, but it went away when I upgraded to one of the July
> development snapshots.  It's strange that only your version of cpp was
> affected and not the egcs version.  Upgrading also fixed a PATH problem
> where bash would ignore one of my paths, and a problem with the compilers
> reading the specs file.

Thanks for the info. John Fortin also "fixed" it by upgrading. This is
one of those bizarre ones -- we tested for unique inode numbers and
that's when it came out. Of course, I remembered the inode problem on
Win9x after spending quite a bit of time on this problem.

gcc-2.95 cpp uses inodes to optimize header access (or at least, more so
than what egcs-1.1.2 cpp did), and that's why it's showing.

Regards,
Mumit


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