Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:11:19 +0200	[thread overview]
Message-ID: <20131011141119.7d87610d@skate> (raw)
In-Reply-To: <874n8ouivj.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Fri, 11 Oct 2013 13:50:08 +0200, Peter Korsgaard wrote:

>  Thomas> Of course, we still have to decide whether we want gcc 4.8, 4.7, and
>  Thomas> 4.6, or rather larger jumps like
>  Thomas> gcc 4.8, 4.4, 4.0 or something like that.
> 
> As we support each individual 4.x version between 4.3 and 4.8 for the
> internal toolchain (+/- odd architectures) and Linaro is pretty leading
> edge, I would say 4.6 -> 4.8.

This still doesn't solve the case where Linaro 2013.11 would jump from
the next eglibc version, but keeping the same gcc version, for example.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-11 12:11 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 [this message]
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=20131011141119.7d87610d@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