All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] gcc: switch to gcc 4.9 as the default version
Date: Tue, 23 Jun 2015 21:28:02 +0200	[thread overview]
Message-ID: <87egl25inx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150623180202.34e83978@free-electrons.com> (Thomas Petazzoni's message of "Tue, 23 Jun 2015 18:02:02 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 > These are always using the default gcc version. However, it is true
 > that all the other Buildroot toolchain configuration use pre-built
 > external toolchains, that are stuck to whatever was the default back
 > when 2015.05, except the following toolchains that already use gcc 4.9:

 > br-aarch64-glibc.config:BR2_GCC_VERSION_4_9_X=y
 > br-arm-cortex-a9-glibc.config:BR2_GCC_VERSION_4_9_X=y
 > br-arm-cortex-a9-musl.config:BR2_GCC_VERSION_4_9_X=y

 > But I can certainly trigger a rebuild of the toolchains with the most
 > recent Buildroot, using gcc 4.9 as the default, and having one
 > toolchain using gcc 5.1 to catch issues. Should I do this?

I think it would be interesting to do so, yes.

Thanks!

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2015-06-23 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 22:19 [Buildroot] [git commit] gcc: switch to gcc 4.9 as the default version Peter Korsgaard
2015-06-23  7:46 ` Arnout Vandecappelle
2015-06-23 16:02   ` Thomas Petazzoni
2015-06-23 19:28     ` Peter Korsgaard [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=87egl25inx.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.