From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>,
linux-mips@linux-mips.org
Subject: Re: native gcc for mipsel / uClibc (building or binaries)?
Date: Sun, 12 Feb 2006 21:19:40 +0100 [thread overview]
Message-ID: <43EF985C.4060609@wpkg.org> (raw)
In-Reply-To: <43EF8C16.9020104@total-knowledge.com>
Ilya A. Volynets-Evenbakh wrote:
> Canadian cross is when you build toolchain on system X to run on system
> Y, and generate code for system Z.
all right, so I misunderstood, I need to build gcc on system X to run on
system Y.
> 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.
> 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.
--
Tomasz Chmielewski
Software deployment with Samba
http://wpkg.org
next prev parent reply other threads:[~2006-02-12 20:13 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 [this message]
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
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=43EF985C.4060609@wpkg.org \
--to=mangoo@wpkg.org \
--cc=ilya@total-knowledge.com \
--cc=linux-mips@linux-mips.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.