From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Choosing toolchain (was: 'Re: Compiling U-Boot')
Date: Wed, 27 Nov 2013 16:03:04 +0100 [thread overview]
Message-ID: <529609A8.2070909@gmail.com> (raw)
In-Reply-To: <mu6tw5a94p3xtcffa4d0drrg.1385563272231@email.android.com>
Dear Alexey Smishlayev,
On 11/27/2013 03:43 PM, Alexey Smishlayev wrote:
> Thank you for the advice!
> The toolchain I'm using was provided by manufacturer of the embedded board I am working with.
> Which toolchain should I pick instead?
reference for u-boot is ELDK [1]. Some use mentor (formerly
codesourcery) toolchain [2] successfully. Others build it for there own
by one of the million instructions [3]. ct-ng [4], yocto [5], buildroot
[6] could also be a good choice.
> Should I use the other one for Linux kernel compilation aswell?
You need not, but why care for two different toolchains?
Best regards
Andreas Bie?mann
[1] http://www.denx.de/wiki/DULG/ELDK
[2]
http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/
[3]
https://www.google.com/search?q=arm+linux+toolchain#q=build+arm+linux+toolchain
[4] http://crosstool-ng.org/
[5] https://www.yoctoproject.org/
[6] http://buildroot.uclibc.org/
parent reply other threads:[~2013-11-27 15:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mu6tw5a94p3xtcffa4d0drrg.1385563272231@email.android.com>]
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=529609A8.2070909@gmail.com \
--to=andreas.devel@googlemail.com \
--cc=u-boot@lists.denx.de \
/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