From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: fix bfin problem
Date: Fri, 5 Aug 2016 21:17:42 +0200 [thread overview]
Message-ID: <20160805211742.2ec2426c@free-electrons.com> (raw)
In-Reply-To: <20160731082620.GA28355@waldemar-brodkorb.de>
Hello,
On Sun, 31 Jul 2016 10:26:20 +0200, Waldemar Brodkorb wrote:
> Fix for LINKER BUG: .rofixup section size mismatch problems.
>
> Bug was already reported by Stuart Henderson to binutils upstream:
> https://sourceware.org/bugzilla/show_bug.cgi?id=13391
The bug dates back from 2011, and nobody cared. Does this mean that we
will have to carry this "temporary workaround" forever in Buildroot?
I've applied your patch, but I must say I'm not too happy to see this
kind of things being added :-/
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-05 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 8:26 [Buildroot] [PATCH] binutils: fix bfin problem Waldemar Brodkorb
2016-08-05 19:17 ` Thomas Petazzoni [this message]
2016-08-05 19:22 ` Waldemar Brodkorb
2016-08-05 19:28 ` 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=20160805211742.2ec2426c@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