From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Steven Rostedt <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35
Date: Wed, 14 Dec 2022 13:01:19 -0600 [thread overview]
Message-ID: <20221214190119.GO25951@gate.crashing.org> (raw)
In-Reply-To: <8d1c27fe-bac5-8007-a852-f9c15a49a6ba@csgroup.eu>
On Wed, Dec 14, 2022 at 03:33:24PM +0000, Christophe Leroy wrote:
> Le 13/12/2022 à 21:25, Segher Boessenkool a écrit :
> > On Tue, Dec 13, 2022 at 07:03:07PM +0100, Christophe Leroy wrote:
> >> In binutils 2.35, 'nm -D' changed to show symbol versions along with
> >> symbol names, with the usual @@ separator.
> >
> > 2.37 instead? And --without-symbol-versions is there to restore the
> > old behaviour. The script is parsing the output already so this patch
> > is simpler maybe, but :-)
>
> Do you mean that the original commit from Ben should have done it
> differently ?
Probably.
> My patch is only a backport of original commit 39efdd94e314
> ("libtraceevent: Fix build with binutils 2.35") due to Makefile being at
> a different place in 4.14.
<shrug>. It's not such a great idea to spread misinformation further,
imo. Maybe the mailing list archives will help dampen that already now.
Thanks,
Segher
prev parent reply other threads:[~2022-12-14 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:03 [PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35 Christophe Leroy
2022-12-13 20:25 ` Segher Boessenkool
2022-12-14 15:33 ` Christophe Leroy
2022-12-14 19:01 ` Segher Boessenkool [this message]
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=20221214190119.GO25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=acme@redhat.com \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).