From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/binutils: upstream fixes for 2.31.1
Date: Mon, 18 Mar 2019 22:05:22 +0100 [thread overview]
Message-ID: <20190318220522.5b18fff5@windsurf> (raw)
In-Reply-To: <20190317211848.3721-1-nolange79@gmail.com>
Hello Norbert,
On Sun, 17 Mar 2019 22:18:48 +0100
Norbert Lange <nolange79@gmail.com> wrote:
> combining musl and binutils 2.31.1 will
> produce static applications that crash
> immediately.
> Picked 3 upstream commits to remedy this.
>
> see https://sourceware.org/bugzilla/show_bug.cgi?id=23428
>
> Signed-off-by: Norbert Lange <nolange79@gmail.com>
> ---
> ...OPERTY_X86_ISA_1_USED-note-if-needed.patch | 568 +++++++++++++++++
> ...ly-merge-GNU_PROPERTY_X86_ISA_1_USED.patch | 588 ++++++++++++++++++
> ...operly-add-X86_ISA_1_NEEDED-property.patch | 140 +++++
> 3 files changed, 1296 insertions(+)
> create mode 100644 package/binutils/2.31.1/0012-x86-Add-a-GNU_PROPERTY_X86_ISA_1_USED-note-if-needed.patch
> create mode 100644 package/binutils/2.31.1/0013-x86-Properly-merge-GNU_PROPERTY_X86_ISA_1_USED.patch
> create mode 100644 package/binutils/2.31.1/0014-x86-Properly-add-X86_ISA_1_NEEDED-property.patch
Applied to master, thanks. So those commits are all in binutils 2.32,
so we're good there. What about binutils 2.30 ? Are they affected as
well, or not affected because the issue is a regression introduced
between binutils 2.30 and 2.31 ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-18 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 21:18 [Buildroot] [PATCH v2 1/1] package/binutils: upstream fixes for 2.31.1 Norbert Lange
2019-03-18 21:05 ` Thomas Petazzoni [this message]
2019-03-18 21:28 ` Norbert Lange
2019-03-27 14:42 ` 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=20190318220522.5b18fff5@windsurf \
--to=thomas.petazzoni@bootlin.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 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.