Message-ID: <006001c2c1f8$94196e60$0100a8c0@acp42g>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: <djgpp-workers AT delorie DOT com>, "Richard Dawe" <rich AT phekda DOT freeserve DOT co DOT uk>,
   "Wojciech Galazka" <wojciech DOT galazka AT polkomtel DOT com DOT pl>,
   "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
References: <250B3114DA16D511B82C00E0094005F809D31B49 AT MSGWAW11> <006001c2bf9f$7e46a720$0100a8c0 AT acp42g> <3E2AF573 DOT F1612407 AT phekda DOT freeserve DOT co DOT uk> <002b01c2c06c$0f834fa0$0100a8c0 AT acp42g> <3E2BE454 DOT C5513197 AT phekda DOT freeserve DOT co DOT uk> <006d01c2c0c1$efabccb0$0100a8c0 AT acp42g>
Subject: Re: GCC 3.2.1 build failure
Date: Wed, 22 Jan 2003 20:27:38 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Reply-To: djgpp-workers AT delorie DOT com

> > find 4.1.7 built against current CVS seems to work fine. Maybe the fix I
> made
> > to __solve_symlinks() on 23rd December 2002 broke stat("./.")? Laurynas
> > committed another fix on 17th January 2003. Perhaps that is the change
> that
> > fixes the problem? Maybe you were just unlucky, when you took your CVS
> > snapshot?
> I hope so.
>
> I am pulling down the latest CVS code and will start a complete re-build
> before I leave for work and hopefully when  I get back tonight the update
> will be finished and working.
I can now build GCC with find 4.1.7 built against the CVS code. And the
resulting GCC works as far as I tested.

Andrew