All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-mips@linux-mips.org
Subject: Re: native gcc for mipsel / uClibc (building or binaries)?
Date: Sun, 12 Feb 2006 12:32:35 -0800	[thread overview]
Message-ID: <43EF9B63.7020506@total-knowledge.com> (raw)
In-Reply-To: <43EF985C.4060609@wpkg.org>

Tomasz Chmielewski wrote:

> Ilya A. Volynets-Evenbakh wrote:
>
>> Are you sure it is what you want? I somehow suspect that you want to
>> generate toolchain to build things
>> natively on your mipsel box to run on said box. If that is true,
>> buildroot (http://buildroot.uclibc.org) will do everything
>
>
> Buildroot also builds gcc which works on let's say x86 and makes
> binaries for mipsel/uclibc).
>
> I need the gcc binaries which will work on mipsel, and which will
> build for mipsel.

Buildroot builds _both_. At least it has support for building both.

>
>
>> for you. Also, I think crosstool does it by default as well (not 100%
>> sure though). Look under your destination dir
>> for <target>/bin/gcc.
>
>
> Crosstool by default builds the binaries on system X that will run on
> system X and build for Y.
>
> So now I have binaries that build for mipsel/uclibc on x86, but I
> can't build gcc that will work on mipsel/uclibc with it.

Let's say you build with instdir /crosstool
Then look for mipsel toolchain binaries in
/crosstool/gcc-x.y.z-glibc-K.L.M/mipsel-linux-gnu/mipsel-linux-gnu/bin

-- 
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com

  reply	other threads:[~2006-02-12 20:26 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 [this message]
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

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=43EF9B63.7020506@total-knowledge.com \
    --to=ilya@total-knowledge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.