From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-28
Date: Fri, 30 Sep 2016 08:42:55 +0200 [thread overview]
Message-ID: <20160930084255.07d4833e@free-electrons.com> (raw)
In-Reply-To: <20160930060433.GO1947@waldemar-brodkorb.de>
Hello,
On Fri, 30 Sep 2016 08:04:33 +0200, Waldemar Brodkorb wrote:
> Thomas Petazzoni wrote,
>
> > m68k | nload-0.7.4 | NOK | http://autobuild.buildroot.net/results/b0d10b82f2308a92a8d6c8ac768c9efa2c1770b7
>
> This should be fixed by the update to uClibc-ng 1.0.18.
> Tested here with the internal toolchain.
OK. Should I rebuild just the m68k toolchains with uClibc-ng 1.0.18, or
are there potentially fixes or patches affecting other architectures as
well?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-30 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-28 Thomas Petazzoni
2016-09-30 6:04 ` Waldemar Brodkorb
2016-09-30 6:42 ` Thomas Petazzoni [this message]
2016-09-30 11:27 ` Waldemar Brodkorb
2016-09-30 22:51 ` Arnout Vandecappelle
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=20160930084255.07d4833e@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