This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bootstraping i686-linux gcc on x86_64-linux fails during libgcc stage1 on trunk
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Laurent GUERBY <laurent at guerby dot net>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 2 Mar 2010 16:34:06 -0800
- Subject: Re: Bootstraping i686-linux gcc on x86_64-linux fails during libgcc stage1 on trunk
- References: <1267575504.17566.479.camel@pc2.unassigned-domain>
On Tue, Mar 2, 2010 at 4:18 PM, Laurent GUERBY <laurent@guerby.net> wrote:
> Hi,
>
> I'm trying to build a fully 32 bits GCC on a x86_64-linux 64 bits debian
> system which has all the 32 bits libraries installed (this is for the
> GCC compile farm testers).
>
> I've played with various things including --with-ld= and putting a fake
> "ld" script in PATH but something is hardcoding "/usr/bin/ld" and at the
> end of stage1 it always fails to link libgcc, after having successfully
> built a 32 bits cc1 & friends.
>
> crti.o & friends in 32 bits are in /usr/lib32 on this system.
>
> What am I doing wrong? Is there a way to tell libgcc build to
> use ld the right way?
>
I don't know about Debian. I can bootstap ia32 gcc trunk on Fedora/x86-64
with
# CC="gcc -m32" CXX="g++ -m32" ../src-trunk/configure \
--enable-clocale=gnu --with-system-zlib --enable-shared --with-d
emangler-in-ld --with-fpmath=sse i686-linux
CC="gcc -m32" CXX="g++ -m32" is the key.
--
H.J.