From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] New pre-built Buildroot toolchains in the autobuilder
Date: Tue, 17 May 2016 15:12:17 +0200 [thread overview]
Message-ID: <20160517151217.045c17c4@free-electrons.com> (raw)
Hello,
I have just rebuilt and deployed all the pre-built Buildroot external
toolchains used on the autobuilders with Buildroot 2016.05-rc1. Most
notably, this should fix numerous build failures of the 'mpv' package,
which are due to missing support for XSI math in uClibc (it has been
enabled in the uClibc configuration recently).
The other changes are:
- br-arm-basic, br-arm-cortex-a9-glibc, br-arm-cortex-a9-musl,
br-arm-full-nothread, br-mips32r6-el-hf-glibc, br-mips64-n64-full,
br-mips64r6-el-hf-glibc, br-mipsel-o32-full, br-nios2-glibc,
br-powerpc-603e-basic-cpp, br-powerpc-e500mc-full, br-sh4-full,
br-x86-64-musl, br-xtensa-full now use 4.5 kernel headers instead
of 4.4 kernel headers
- br-arm-full now uses gcc 4.8 instead of gcc 4.7
- br-sparc-glibc has been removed, in favor of br-sparc-uclibc. The
reasoning is that uClibc is now the default C library chosen for
the Sparc architecture in Buildroot. br-sparc-uclibc uses uClibc,
3.14 kernel headers (i.e intentionally not the latest), gcc 4.9.
I have not yet added configurations for ARM noMMU and m68k, as I'm
waiting for 2016.05 to be released to start getting build failures for
those architectures.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2016-05-17 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 13:12 Thomas Petazzoni [this message]
2016-05-17 18:44 ` [Buildroot] New pre-built Buildroot toolchains in the autobuilder André Hentschel
2016-05-17 19:27 ` 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=20160517151217.045c17c4@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