Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Richard Sandiford <richard@codesourcery.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: David Daney <ddaney@avtrex.com>, linux-mips@linux-mips.org
Subject: Re: native gcc for mipsel / uClibc (building or binaries)?
Date: Mon, 13 Feb 2006 10:35:54 +0000	[thread overview]
Message-ID: <87slqnczqt.fsf@talisman.home> (raw)
In-Reply-To: <43EFAD1D.9010100@wpkg.org> (Tomasz Chmielewski's message of "Sun, 12 Feb 2006 22:48:13 +0100")

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

      reply	other threads:[~2006-02-13 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 18:18 native gcc for mipsel / uClibc (building or binaries)? Tomasz Chmielewski
2006-02-12 19:27 ` Ilya A. Volynets-Evenbakh
2006-02-12 20:19   ` Tomasz Chmielewski
2006-02-12 20:32     ` Ilya A. Volynets-Evenbakh
2006-02-12 20:49       ` Tomasz Chmielewski
2006-02-12 21:31 ` David Daney
2006-02-12 21:48   ` Tomasz Chmielewski
2006-02-13 10:35     ` Richard Sandiford [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87slqnczqt.fsf@talisman.home \
    --to=richard@codesourcery.com \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mangoo@wpkg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox