From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Update of toolchains used in the autobuilders
Date: Sun, 18 Oct 2015 15:32:59 +0200 [thread overview]
Message-ID: <20151018153259.0bd5eaca@free-electrons.com> (raw)
Hello,
I've rebuilt all pre-built Buildroot toolchains used for the
autobuilders with the latest Buildroot, and deployed them in the
autobuilders.
Things worth mentioning:
- the br-arm-full-static and br-x86-64-core2-full toolchains are
built with 3.14 kernel headers instead of the default (latest) ones,
in order to test a bit some older kernel headers. Note that the
br-arm-full configuration was already built with 3.10 headers for the
same reason, and continues to be built with 3.10 headers.
- the br-mips64-n64-full toolchain could not be built. It used to use
glibc, but now that uClibc support for MIPS64 has been enabled, it
tried to build with uClibc, and the build fails (I'll report the
problem separately to Waldemar and Vicente)
- the pre-built musl toolchains have not been updated, because due to
commit bb41933d3642f44c8d2db07886b2e5bf18b97fad, there is no longer
a libc.a generated in the musl toolchains, which breaks the external
toolchain logic to find the sysroot.
- I've added a br-sparc64-glibc configuration, following the addition
of Sparc64 support by Waldemar. Hopefully this configuration will
give less issues than the 32 bits Sparc v8 configuration we have.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
reply other threads:[~2015-10-18 13:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151018153259.0bd5eaca@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