Message-ID: <006d01c2c0c1$efabccb0$0100a8c0@acp42g>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: "Richard Dawe" <rich AT phekda DOT freeserve DOT co DOT uk>
Cc: "DJGPP workers" <djgpp-workers AT delorie DOT com>
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>
Subject: Re: GCC 3.2.1 build failure
Date: Tue, 21 Jan 2003 07:23:59 +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

> > So far this is what we have:-
> > a) Bash 2.05 version does not matter
> > b) Find version that work:-
> >     - 4.1 any version including latest CVS build
> >     - 4.1.7 with CVS of Oct 2002
> >     - 4.1.7 with CVS of Dec 2002
> > c) Find version that does not work
> >     - 4.1.7 with CVS of  Jan 2003
>
> I tried to build find 4.1.7, but it failed:
..SNIP..
> I reconfigured to disable NLS (./configure --disable-nls). Oh, this
created
> libintl.h by symlinking. Maybe some of the missing files (in this and
other
> packages) are due to the symlinks? I have been using unzip to unzip, not
> djtar. But find417s.zip does not seem to contain libintl.h. Maybe it's a
> problem with the archiver and symlinks? That seems unlikely, since they're
> just regular files.

I will have a look at this along with Grep.

> As a work-around, if you run config.status after extracting the sources,
it
> will create libintl.h.
>
> 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.

Regards
Andrew