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 11:29:38 +0200 [thread overview]
Message-ID: <20131011112938.16a751d7@skate> (raw)
In-Reply-To: <CAAXf6LXMvV4rrxbcAozT69PsEVp2CgpgDNhZXnQ6ytdWZz+SvA@mail.gmail.com>
Dear Thomas De Schampheleire,
On Fri, 11 Oct 2013 11:16:33 +0200, Thomas De Schampheleire wrote:
> The principle of keep three toolchains that differ sufficiently seems
> ok to me. I don't think we should care about 'buggy' releases: Linaro
> is responsible of delivering quality toolchains. If it happens that a
> newly released toolchain is no good for some reason, we can still step
> that one back, or take the newer one if it was released in the mean
> time.
>
> So, this proposal would for example have (fictional)
> Linaro 2012.11 (based on gcc 4.4)
> Linaro 2013.02 (gcc 4.4 but new glibc)
> Linaro 2013.08 (gcc 4.8)
Ok. So a bit like the Sourcery CodeBench toolchains are updated to
their latest patch level, but we keep several "major version" with
their latest patch level.
But in the case of Sourcery CodeBench toolchain, we do those patch
level version bumps without changing the Config.in option name, so
the bump is transparent to users.
For the Linaro toolchains, the Config.in option name contain the
precise version. So, what happens when we bump Linaro 2013.08 to Linaro
2012.09 (which also uses gcc 4.8, and therefore should replace Linaro
2012.08) ?
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 9:29 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 [this message]
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
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=20131011112938.16a751d7@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