This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Possible GCC 4.3 driver regression caused by your patch
- From: Greg Schafer <gschafer at zip dot com dot au>
- To: Carlos O'Donell <carlos at codesourcery dot com>
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org
- Date: Tue, 11 Mar 2008 12:47:52 +1100
- Subject: Re: Possible GCC 4.3 driver regression caused by your patch
- References: <20080301225746.GA25180@eyo32.local> <47CAEF1E.20509@codesourcery.com>
On Sun, Mar 02, 2008 at 01:17:02PM -0500, Carlos O'Donell wrote:
> Greg Schafer wrote:
> >Hi Carlos and Mark,
> >
> >Your "Relocated compiler should not look in $prefix" patch here:
> >
> >http://gcc.gnu.org/ml/gcc/2006-10/msg00280.html
> >
> >appears to have caused a regression in my GCC 4.3 testing.
> >
> >In summary, there is a small window *during the GCC build itself* where GCC
> >does not pick up the correct startfiles. For example, when GCC_FOR_TARGET
> >is
> >called to build the target libraries, the startfiles in $prefix/lib are not
> >used. Instead, the startfiles from the host's /usr/lib are used which
> >breaks
> >my build. Note that the problem seems to rectify itself once the just-built
> >GCC is installed into $prefix.
> >
> >Here's the scenario:
> >
> > - Native build
> > - i686-pc-linux-gnu
> > - --prefix=/temptools
> > - Glibc already installed in /temptools/lib
>
> What options did you use to configure the compiler? Could you double
> check your host system is actually i686-pc-linux-gnu? When you say
> "breaks my build", what error are you seeing?
The issue is now filed as
http://gcc.gnu.org/PR35532
It would be appreciated if the responsible Codesourcery folks could address
this regression.
Thanks
Greg