From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-23
Date: Tue, 24 May 2016 16:58:44 +0200 [thread overview]
Message-ID: <20160524165844.6cd99638@free-electrons.com> (raw)
In-Reply-To: <574459AC.5010001@zacarias.com.ar>
Hello,
On Tue, 24 May 2016 10:39:56 -0300, Gustavo Zacarias wrote:
> Yes, don't use 4.5.0 - 4.5.4 headers, it's already fixed by dropping the
> connman workaround patch which isn't compatible with the proper fix,
> Thomas rebuilding the test toolchains and bumping the headers to 4.5.5.
> As for covering the broken headers scenario any patch that's created for
> that is unlikely to be accepted upstream, and any toolchain that ships
> with those broken headers could be called "broken".
I have rebuilt the toolchains and deployed them yesterday, I've sent an
e-mail about this on the list. So normally, those issues should no
longer show up. If they do, then we have another problem (or I messed
up the toolchain update).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-24 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-23 Thomas Petazzoni
2016-05-24 13:36 ` Vicente Olivert Riera
2016-05-24 13:39 ` Gustavo Zacarias
2016-05-24 13:44 ` Vicente Olivert Riera
2016-05-24 14:58 ` Thomas Petazzoni [this message]
2016-05-24 20:48 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-05-24 21:01 ` Bernd Kuhls
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=20160524165844.6cd99638@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