From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-net
Date: Mon, 4 Jan 2016 09:32:18 -0500 [thread overview]
Message-ID: <20160104143218.GD4093@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmW+-QYbSr0W1cremgT2kmti932bGuVULLJO4vyj_gq_gA@mail.gmail.com>
On Mon, Jan 04, 2016 at 11:56:34AM +0800, Bin Meng wrote:
[snip]
> Still downloading ELDK toolchains so cannot comment ELDK compiler
> behavior :) One question, what's our recommended toolchains for
> U-Boot? I have been using kernel.org toolchains as mentioned in the
> buildman doc and some other ones mentioned in the moveconfig doc.
Well, the way I look at it we have two answers:
1) In general, any sane for your architecture gcc 4.x or later should
work. I'm not going to test every possible combination here but
maintainers (who might have less visible needs like hey, our product
uses toolchain X, so I need to use it) may also say their board needs to
work with toolchain X.
2) To me, ELDK current release, current kernel.org toolchains and
current commodity distro (Debian, Fedora, SuSE, etc) toolchains should
work too.
I personally use ELDK 5.6 or PowerPC and MIPS, kernel.org for most
everything else and Debian 8 arm-none-eabi (gcc 4.8.x) as that does both
armv7 and armv7m, and then Debian/Unstable gcc 5.x for
x86/aarch64/arm/sandbox/powerpc.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160104/981ea653/attachment.sig>
next prev parent reply other threads:[~2016-01-04 14:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 17:58 [U-Boot] Pull request: u-boot-net Joe Hershberger
2015-12-24 3:47 ` Tom Rini
2015-12-29 3:02 ` Joe Hershberger
2015-12-29 14:09 ` Tom Rini
2016-01-02 17:09 ` Tom Rini
2016-01-04 2:35 ` Bin Meng
2016-01-04 3:46 ` Tom Rini
2016-01-04 3:56 ` Bin Meng
2016-01-04 8:31 ` Bin Meng
2016-01-04 14:24 ` Tom Rini
2016-01-05 4:08 ` Bin Meng
2016-01-05 13:18 ` Tom Rini
2016-01-04 11:46 ` Dirk Eibach
2016-01-04 13:48 ` Bin Meng
2016-01-04 14:22 ` Tom Rini
2016-01-05 4:18 ` Bin Meng
2016-01-05 13:18 ` Tom Rini
2016-01-07 2:49 ` Bin Meng
2016-01-07 16:29 ` Tom Rini
2016-01-13 20:58 ` Joe Hershberger
2016-01-13 23:01 ` Tom Rini
2016-01-13 23:10 ` Tom Rini
2016-01-14 13:20 ` Tom Rini
2016-01-04 14:32 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-04 16:06 Joe Hershberger
2012-04-09 15:16 ` Wolfgang Denk
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=20160104143218.GD4093@bill-the-cat \
--to=trini@konsulko.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