Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: add comment with bug report reference
Date: Sun, 30 Oct 2016 17:18:09 +0100	[thread overview]
Message-ID: <20161030161809.GG1797@waldemar-brodkorb.de> (raw)
In-Reply-To: <20161030164340.6d8d079b@free-electrons.com>

Hi Thomas,
Thomas Petazzoni wrote,

> Hello,
> 
> On Sun, 30 Oct 2016 14:25:11 +0100, Waldemar Brodkorb wrote:
> > Add requested bug report
> > 
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> > ---
> >  package/binutils/Config.in.host | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/package/binutils/Config.in.host b/package/binutils/Config.in.host
> > index a7610b4..dce6996 100644
> > --- a/package/binutils/Config.in.host
> > +++ b/package/binutils/Config.in.host
> > @@ -18,6 +18,7 @@ choice
> >  	config BR2_BINUTILS_VERSION_2_27_X
> >  		bool "binutils 2.27"
> >  		# supported but broken on Microblaze
> > +		# see https://sourceware.org/bugzilla/show_bug.cgi?id=20748
> >  		depends on !BR2_microblaze
> 
> Your bug report is about binutils 2.27 generating broken binaries for
> microblaze/musl, but you disable binutils 2.27 completely for
> microblaze, and not just for musl. Why so?

Because the binutils bug affects musl/uClibc-ng and glibc.
I just used musl to bisect and simplified the bug report.
Furthermore I normally get very good support from the musl devs
in case of toolchain issues.

best regards
 Waldemar

  reply	other threads:[~2016-10-30 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 13:25 [Buildroot] [PATCH] binutils: add comment with bug report reference Waldemar Brodkorb
2016-10-30 15:43 ` Thomas Petazzoni
2016-10-30 16:18   ` Waldemar Brodkorb [this message]
2016-10-30 17:10     ` Thomas Petazzoni
2016-11-01 15:18 ` Thomas Petazzoni

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=20161030161809.GG1797@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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