From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-02-19
Date: Sun, 21 Feb 2016 10:01:14 +0100 [thread overview]
Message-ID: <20160221100114.591bd29e@free-electrons.com> (raw)
In-Reply-To: <871t86cvak.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Sun, 21 Feb 2016 09:38:43 +0100, Peter Korsgaard wrote:
> > Yes, it is really a work-around, but it is so much simpler than adding
> > a BR2_TOOLCHAIN_HAS_GCC_BUG_58952, selecting it for all broken
> > toolchain + adding the autobuilder exceptions that are needed to also
> > exclude the custom external toolchains that are affected.
>
> > (Not sure Peter will agree, since my proposal is not the cleanest
> > solution, but it's by far the one with the least impact.)
>
> Yes, I agree - And preferably send the patch upstream as well!
Well, in essence, this patch will not be accepted upstream. It is a
crappy work-around for a compiler bug, so it would be very logical for
upstream to reject this patch.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-21 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-02-19 Thomas Petazzoni
2016-02-20 15:16 ` Jörg Krause
2016-02-20 15:16 ` Jörg Krause
2016-02-20 19:48 ` Jörg Krause
2016-02-20 23:06 ` Thomas Petazzoni
2016-02-21 8:38 ` Peter Korsgaard
2016-02-21 9:01 ` Thomas Petazzoni [this message]
2016-02-21 9:17 ` Peter Korsgaard
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=20160221100114.591bd29e@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