From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] codesourcery as external toolchain
Date: Sat, 17 Apr 2010 17:07:52 +0200 [thread overview]
Message-ID: <20100417170752.38a18d39@surf> (raw)
In-Reply-To: <n2o5fbe85791004162357h11a18ae5v1db91f6fefb81db6@mail.gmail.com>
Hello,
Please reply to the Buildroot mailing-list and not to me directly,
thanks!
On Sat, 17 Apr 2010 08:57:19 +0200
Atom Proton <atomx01@gmail.com> wrote:
> Thanks for your answer. I'm apply your changes, and now is working
> arm-none-linux-gnueabi toolchain ( tested version:
> http://www.codesourcery.com/downloads/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2).
Great!
> But I wont use uClibc (arm-uclinuxeabi toolchain), and this is don't
> working now. I have tested
> http://www.codesourcery.com/downloads/public/gnu_toolchain/arm-uclinuxeabi/arm-2009q1-163-arm-uclinuxeabi-i686-pc-linux-gnu.tar.bz2.
> Here is the output of compilation with arm-uclinuxeabi toolchain:
This is not a Linux/uClibc toolchain, but a uClinux toolchain. It
generates FLAT binaries, for no-MMU targets. This type of toolchain is
currently unsupported in Buildroot, because we don't have support for
no-MMU (it might be added in the future, but we don't have it at the
moment).
I don't think CodeSourcery provides Linux/uClibc toolchains. If you
want one, I think you have no other solutions that building your own,
using Crosstool-NG.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-04-17 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:47 [Buildroot] codesourcery as external toolchain Atom Proton
2010-04-17 0:16 ` Thomas Petazzoni
[not found] ` <n2o5fbe85791004162357h11a18ae5v1db91f6fefb81db6@mail.gmail.com>
2010-04-17 15:07 ` Thomas Petazzoni [this message]
2010-04-17 17:35 ` Baruch Siach
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=20100417170752.38a18d39@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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