From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2017.09-rc1
Date: Tue, 3 Oct 2017 21:27:46 +0200 [thread overview]
Message-ID: <20171003212746.22c89884@windsurf.home> (raw)
In-Reply-To: <20170921182828.26985-1-didin@synopsys.com>
Hello,
On Thu, 21 Sep 2017 21:28:28 +0300, Evgeniy Didin wrote:
> diff --git a/package/binutils/arc-2017.09-rc1/0006-Fixes-LINKER-BUG-.rofixup-section-size-mismatch.patch b/package/binutils/arc-2017.09-rc1/0006-Fixes-LINKER-BUG-.rofixup-section-size-mismatch.patch
> new file mode 100644
> index 000000000..e5409efe1
> --- /dev/null
> +++ b/package/binutils/arc-2017.09-rc1/0006-Fixes-LINKER-BUG-.rofixup-section-size-mismatch.patch
> @@ -0,0 +1,31 @@
> +From 122de3b633f4273826a2d01702d7c515f93ec2be Mon Sep 17 00:00:00 2001
> +From: Waldemar Brodkorb <wbx@openadk.org>
> +Date: Sat, 29 Jul 2017 14:08:20 +0200
> +Subject: [PATCH] Fixes: LINKER BUG: .rofixup section size mismatch
> +
> +Workaround from adi-toolchain commit:
> +af414ec1fb628ddb1562f062f3db49823ca14ca2
> +[#6798] binutils-2.21/bfd: temp workaround for rofixup mismatch errors.
> +
> +Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> +---
> + bfd/elf32-bfin.c | 3 ++-
> + 1 file changed, 2 insertions(+), 1 deletion(-)
What is the point of adding this Blackfin-only patch to the patch stack
used only for the ARC binutils version ?
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-03 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 18:28 [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2017.09-rc1 Evgeniy Didin
2017-09-28 18:47 ` Alexey Brodkin
2017-10-03 19:27 ` Thomas Petazzoni [this message]
2017-10-04 13:24 ` Alexey Brodkin
2017-10-08 14:23 ` 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=20171003212746.22c89884@windsurf.home \
--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