linux-mips
[Top] [All Lists]

Re: native gcc for mipsel / uClibc (building or binaries)?

To: Tomasz Chmielewski <mangoo@wpkg.org>
Subject: Re: native gcc for mipsel / uClibc (building or binaries)?
From: Richard Sandiford <richard@codesourcery.com>
Date: Mon, 13 Feb 2006 10:35:54 +0000
Cc: David Daney <ddaney@avtrex.com>, linux-mips@linux-mips.org
In-reply-to: <43EFAD1D.9010100@wpkg.org> (Tomasz Chmielewski's message of "Sun, 12 Feb 2006 22:48:13 +0100")
Mail-followup-to: Tomasz Chmielewski <mangoo@wpkg.org>,David Daney <ddaney@avtrex.com>, linux-mips@linux-mips.org, richard@codesourcery.com
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <43EF7C06.3080006@wpkg.org> <43EFA945.1030906@avtrex.com> <43EFAD1D.9010100@wpkg.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux)
Tomasz Chmielewski <mangoo@wpkg.org> writes:
> Now, when I try to compile gcc (--build=i686-pc-linux-glibc
>  > --target=mipsel-linux --host=mipsel-linux), it breaks, as during the 
> build process gcc's ./configure has a schizophrenia: it tries to compile
> some parts for mipsel (as I'd expect), but it also tries to compile and
> execute the binaries during the build process.

Just to rule out one possibility, were the x86-hosted tools in
your path when you ran configure and make?  They need to be.

> This means, it creates some binaries/libs needed for the build process
> (like libiberty), then tries to run/use them, but as they are mipsel
> binaries, the build process breaks.

Recent versions compile two versions of libiberty, one for the build
machine and one for the host.  The build version is used for things
like genattrtab (a build-time tool used only to build gcc itself)
while the host version is linked into the final compilers.

Richard

<Prev in Thread] Current Thread [Next in Thread>