From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [for-next 2/3] package/gcc: switch to gcc 6.x as the default
Date: Fri, 26 May 2017 15:13:44 +0200 [thread overview]
Message-ID: <20170526151344.2db79ce8@free-electrons.com> (raw)
In-Reply-To: <20170525183457.12169-2-romain.naour@gmail.com>
Hello,
On Thu, 25 May 2017 20:34:56 +0200, Romain Naour wrote:
> Even if gcc 5 is still maintained for some time (gcc 5.5 is pending),
> switch to gcc 6.x since it has been released since 2016-04-27 and
> gcc 7.x is available since 2017-05-02.
>
> We have been having toolchains in the autobuilders with gcc
> 6.x for a while, so the vast majority of the problems should have
> already been solved.
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> package/gcc/Config.in.host | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-26 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 18:34 [Buildroot] [for-next 1/3] package/gcc: remove old hashes (gcc 4.5, 4.7, 4.8) Romain Naour
2017-05-25 18:34 ` [Buildroot] [for-next 2/3] package/gcc: switch to gcc 6.x as the default Romain Naour
2017-05-26 13:13 ` Thomas Petazzoni [this message]
2017-05-25 18:34 ` [Buildroot] [for-next 3/3] package/gcc: remove gcc 4.9 Romain Naour
2017-05-26 13:14 ` Thomas Petazzoni
2017-06-11 20:30 ` Arnout Vandecappelle
2017-06-13 22:04 ` Peter Korsgaard
2017-06-14 5:30 ` Arnout Vandecappelle
2017-06-14 6:56 ` Thomas Petazzoni
2017-06-14 7:06 ` Peter Korsgaard
2017-07-01 8:40 ` Romain Naour
2017-06-14 7:03 ` Peter Korsgaard
2017-07-08 6:16 ` daggs
2017-07-09 9:44 ` Romain Naour
2017-05-26 13:13 ` [Buildroot] [for-next 1/3] package/gcc: remove old hashes (gcc 4.5, 4.7, 4.8) Thomas Petazzoni
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=20170526151344.2db79ce8@free-electrons.com \
--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