From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] toolchain: add option for toolchains affected by GCC PR libstdc++/64735
Date: Fri, 10 Feb 2017 07:52:30 +0100 [thread overview]
Message-ID: <1486709550.9565.1.camel@embedded.rocks> (raw)
In-Reply-To: <20170209213057.33fa79ba@free-electrons.com>
Hi Thomas,
On Thu, 2017-02-09 at 21:30 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Thu,??9 Feb 2017 18:47:54 +0100, J?rg Krause wrote:
>
> > +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735
>
> I've taken a part of your commit log, and added it as a comment here.
>
> > +config BR2_TOOLCHAIN_HAS_GCC_BUG_64735
> > + bool
>
> Instead of having this option selected by the architecture code, I've
> added the relevant "default y" and "depends on" here. I believe it's
> not worth spreading these selects all over the place.
You're right! It's much cleaner this way. Thanks!
> Now that I write this, I realize I've written the logic in the wrong
> way, I'll fix that up now.
J?rg
next prev parent reply other threads:[~2017-02-10 6:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 17:47 [Buildroot] [PATCH 0/6] Deal with GCC PR libstdc++/64735 Jörg Krause
2017-02-09 17:47 ` [Buildroot] [PATCH 1/6] toolchain: add option for toolchains affected by " Jörg Krause
2017-02-09 20:30 ` Thomas Petazzoni
2017-02-10 6:52 ` Jörg Krause [this message]
2017-02-09 17:47 ` [Buildroot] [PATCH 2/6] arch: mark NIOS II as " Jörg Krause
2017-02-09 20:32 ` Thomas Petazzoni
2017-02-09 17:47 ` [Buildroot] [PATCH 3/6] arch/arm: mark ARMv{4, 5} " Jörg Krause
2017-02-09 17:47 ` [Buildroot] [PATCH 4/6] arch/sparc: mark SPARCv8 " Jörg Krause
2017-02-09 17:47 ` [Buildroot] [PATCH 5/6] package/mpd: " Jörg Krause
2017-02-09 20:33 ` Thomas Petazzoni
2017-02-09 17:47 ` [Buildroot] [PATCH 6/6] package/mpd: add choice between version 0.19 and 0.20 Jörg Krause
2017-02-09 20:34 ` Thomas Petazzoni
2017-02-10 7:04 ` Jörg Krause
2017-02-11 14:25 ` Thomas Petazzoni
2017-02-10 7:34 ` Jörg Krause
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=1486709550.9565.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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.