From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-11-21
Date: Sun, 22 Nov 2015 13:35:28 +0100 [thread overview]
Message-ID: <20151122133528.6d1fbbf2@free-electrons.com> (raw)
In-Reply-To: <20151122100315.GT19876@waldemar-brodkorb.de>
Hello,
On Sun, 22 Nov 2015 11:03:15 +0100, Waldemar Brodkorb wrote:
> > This is a uClibc issue which was affected a number of architectures.
> > Has it been fixed already for ARC ? Waldemar, Alexey ?
>
> Should be fixed by using a recent ARC toolchain with uClibc-ng
> 1.0.9. Update the ARC toolchains :)
Good. In fact I've already rebuilt all the toolchains, I just need to
deploy them. Will hopefully get to this later today.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-22 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-21 Thomas Petazzoni
2015-11-22 9:57 ` [Buildroot] Analysis of build " Thomas Petazzoni
2015-11-22 10:03 ` Waldemar Brodkorb
2015-11-22 12:35 ` Thomas Petazzoni [this message]
2015-11-22 13:47 ` Rodrigo Rebello
2015-11-23 16:53 ` Waldemar Brodkorb
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=20151122133528.6d1fbbf2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.