From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-25
Date: Tue, 26 Nov 2013 11:53:31 +0100 [thread overview]
Message-ID: <20131126115331.6389b4cb@skate> (raw)
In-Reply-To: <20131126073003.0DD121014E8@stock.ovh.net>
Hello,
On Tue, 26 Nov 2013 08:30:02 +0100 (CET), Thomas Petazzoni wrote:
> mipsel | attr-2.4.47 | NOK | http://autobuild.buildroot.net/results/b575154552a06c414a2ef2a39f572523ccd7bf54/
> mipsel | attr-2.4.47 | NOK | http://autobuild.buildroot.net/results/12fd65f29ae90559762456faa6e949968201cbe2/
These builds.
> mipsel | gettext-0.18.3.1 | NOK | http://autobuild.buildroot.net/results/e07a73638feb7b4992973299f1096eef1e5032e4/
and this one are now fixed. They were caused by the external toolchain
being built for MIPS IV, but we have deprecated MIPS IV support
recently, so by default, mipsel is now mips32. So I've just rebuilt the
Buildroot external toolchain for mips32, and it fixes those problems.
I've also started updating the Buildroot external toolchains to use
toolchains produced with 2013.11-rc2, but not all toolchains have been
updated yet.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-26 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-25 Thomas Petazzoni
2013-11-26 8:41 ` Will Newton
2013-11-26 9:03 ` Thomas De Schampheleire
2013-11-26 9:10 ` Ryan Barnett
2013-11-26 10:53 ` Thomas Petazzoni [this message]
2013-11-26 10:59 ` Markos Chandras
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=20131126115331.6389b4cb@skate \
--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