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] Pre-built Buildroot toolchains updated
Date: Mon, 12 Jun 2017 23:11:22 +0200	[thread overview]
Message-ID: <20170612231122.71cd02f0@windsurf.lan> (raw)

Hello,

FYI, I have updated the pre-built Buildroot toolchains used by
autobuild.buildroot.org.

Main changes are:

 - Most toolchains now use gcc 6.x (instead of 5.x), since 6.x is our
   default version.

 - I've switched one toolchain to use gcc 7.x (br-arm-cortex-a9-glibc),
   so it's our first toolchain using gcc 7.x. You can expect some gcc
   7.x issues.

 - uClibc 1.0.25 is used.

 - Toolchains that were using gcc 4.8 are now using 4.9, since we have
   removed support for 4.8 in the internal toolchain backend.

 - Most toolchains now use 4.11 kernel headers instead of 4.10, because
   there is a variety here, with some toolchains using 3.10, 4.1, etc.
   I'm keeping some disparity here, just to test various combinations.

For the details, see:

  https://git.buildroot.org/buildroot-test/commit/?id=c4f9ab50e66d08a3d726f612364abb6a08f13f20

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

             reply	other threads:[~2017-06-12 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 21:11 Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-05  9:43 [Buildroot] Pre-built Buildroot toolchains updated Thomas Petazzoni
2016-07-07 19:53 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=20170612231122.71cd02f0@windsurf.lan \
    --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