From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] toolchain-external: update Linaro ARM toolchain
Date: Fri, 11 Oct 2013 14:22:35 +0200 [thread overview]
Message-ID: <20131011142235.1b446183@skate> (raw)
In-Reply-To: <CAAXf6LU22crjgist0QpFxAGP=DECKjzRj-+2xccBgyxDtWTUfA@mail.gmail.com>
Dear Thomas De Schampheleire,
On Fri, 11 Oct 2013 14:15:57 +0200, Thomas De Schampheleire wrote:
> It wouldn't solve that case, but maybe it doesn't matter to us. If the
> Linaro project co-names their toolchains based on date + gcc, then we
> can limit us to that. We then accept whatever eglibc version they
> select for that release.
>
> If a user wants to stick to a given eglibc and gcc version, and Linaro
> updates eglibc without updating gcc, then that user will have to do
> something special. I think it's not realistic for us to handle this in
> a clearer way than Linaro does, except by providing a 'custom version'
> option.
Ok. From an user perspective, I'm not quite convinced that it makes more
sense to index according to the gcc release than the binutils, gdb, or
eglibc version, or the EABI, or something else, but ok, fair enough.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-11 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 14:06 [Buildroot] [git commit] toolchain-external: update Linaro ARM toolchain Peter Korsgaard
2013-10-10 6:53 ` Arnout Vandecappelle
2013-10-10 7:57 ` Thomas Petazzoni
2013-10-11 9:01 ` Luca Ceresoli
2013-10-11 9:16 ` Thomas De Schampheleire
2013-10-11 9:29 ` Thomas Petazzoni
2013-10-11 10:19 ` Peter Korsgaard
2013-10-11 10:23 ` Thomas Petazzoni
2013-10-11 11:40 ` Thomas De Schampheleire
2013-10-11 11:50 ` Peter Korsgaard
2013-10-11 12:11 ` Thomas Petazzoni
2013-10-11 12:15 ` Thomas De Schampheleire
2013-10-11 12:22 ` Thomas Petazzoni [this message]
2013-10-11 13:05 ` Peter Korsgaard
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=20131011142235.1b446183@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