From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Recommended cross toolchain for ARM
Date: Sat, 27 Jul 2013 16:14:45 +0200 [thread overview]
Message-ID: <20130727161445.1ca8a5c0@skate> (raw)
In-Reply-To: <20130723060305.GA6169@zuhnb712.ap.bm.net>
Dear Woody Wu,
On Tue, 23 Jul 2013 14:03:05 +0800, Woody Wu wrote:
> Do you guys have a suggested cross toolchain? I want to use glibc
> instead of uclibc, so in the buildroot default supported options, it
> left only Sourcery CodeBench (SCB). But SCB seems not a very completed
> toolchain, when I use it to compile some of my applications, I found it
> missed with some definitions (such as RLIM_*) which should normally
> appear in a standard header file.
Sourcery CodeBench toolchains usually work fine. Could you point to
specific problems with them, i.e which package fails to build, with
which version of the Sourcery CodeBench? Most likely, if your
application fails to build with a Sourcery CodeBench toolchain, it's
because your application doesn't #include the right header files.
> Then I tried, Linaro, but it seems that it do not well support my armv5t
> core. Anyway, I run with errors after configured it with buildroot.
The Linaro toolchains are built for ARMv7, so the C library they
contain will only work on ARMv7+ processors.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-27 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 6:03 [Buildroot] Recommended cross toolchain for ARM Woody Wu
2013-07-23 20:33 ` Tim Nelson
2013-07-24 3:22 ` Woody Wu
2013-07-24 4:25 ` Steve Calfee
2013-07-24 14:16 ` Grant Edwards
2013-07-27 14:14 ` Thomas Petazzoni [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=20130727161445.1ca8a5c0@skate \
--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