From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] toolchain-external: update Linaro ARM toolchain
Date: Thu, 10 Oct 2013 08:53:49 +0200 [thread overview]
Message-ID: <52564EFD.10506@mind.be> (raw)
In-Reply-To: <20131009143431.9A85B9B970@busybox.osuosl.org>
On 10/09/13 16:06, Peter Korsgaard wrote:
> -config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_06
> - bool "Linaro 2013.06"
> +config BR2_TOOLCHAIN_EXTERNAL_LINARO_2013_07
> + bool "Linaro 2013.07"
I believe I asked this before: do we really want to remove external
toolchains without going through a deprecation cycle? Why do we offer in
a released buildroot three different Linaro toolchain versions that are
all gcc 4.8 and that you cannot use anymore three months later?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-10-10 6:53 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 [this message]
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
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=52564EFD.10506@mind.be \
--to=arnout@mind.be \
--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