From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix elf2flt build
Date: Mon, 31 Aug 2015 14:28:54 +0200 [thread overview]
Message-ID: <20150831142854.28f7fb92@free-electrons.com> (raw)
In-Reply-To: <55E443B0.4010503@gmail.com>
Douglas,
On Mon, 31 Aug 2015 14:08:16 +0200, Douglas RAILLARD wrote:
> BTW: Are there any benefits in using 2.24 (default) instead of 2.25.1
> and also gcc 4.9.x (default) instead of gcc 5.x ?
It's just because when it comes to toolchain components, we are a bit
conservative, and generally default to the version just before the last
one. New version of gcc/binutils often exhibits some issues on
non-mainstream architectures, so this policy allows to wait a bit that
the big issues are found/fixed before we use them as the default.
For example, gcc 5.x has more strict rules which causes many packages
to not build anymore. Hence, we cannot use it as the default for the
moment.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-31 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 16:47 [Buildroot] [PATCH 1/1] Fix elf2flt build Douglas RAILLARD
2015-08-27 18:35 ` Thomas Petazzoni
2015-08-27 21:00 ` Douglas RAILLARD
[not found] ` <6966330.pLhB8QsgjT@raillard-dv6>
2015-08-28 8:09 ` Thomas Petazzoni
2015-08-28 10:17 ` Douglas RAILLARD
2015-08-28 11:20 ` Thomas Petazzoni
2015-08-28 13:01 ` Waldemar Brodkorb
2015-08-30 15:43 ` Douglas RAILLARD
2015-08-31 6:05 ` Waldemar Brodkorb
2015-08-31 12:08 ` Douglas RAILLARD
2015-08-31 12:28 ` 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=20150831142854.28f7fb92@free-electrons.com \
--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