From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-trace-devel@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: Tue, 13 Dec 2022 14:25:35 -0600 [thread overview]
Message-ID: <20221213202535.GL25951@gate.crashing.org> (raw)
In-Reply-To: <c4629a12d4a2a21ff131624d3ef1d9f8b5fd64ad.1670954579.git.christophe.leroy@csgroup.eu>
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 :-)
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Ben Hutchings <ben@decadent.org.uk>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-trace-devel@vger.kernel.org, stable@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35
Date: Tue, 13 Dec 2022 14:25:35 -0600 [thread overview]
Message-ID: <20221213202535.GL25951@gate.crashing.org> (raw)
In-Reply-To: <c4629a12d4a2a21ff131624d3ef1d9f8b5fd64ad.1670954579.git.christophe.leroy@csgroup.eu>
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 :-)
Segher
next prev parent reply other threads:[~2022-12-13 20:33 UTC|newest]
Thread overview: 8+ 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 18:03 ` Christophe Leroy
2022-12-13 20:25 ` Segher Boessenkool [this message]
2022-12-13 20:25 ` Segher Boessenkool
2022-12-14 15:33 ` Christophe Leroy
2022-12-14 15:33 ` Christophe Leroy
2022-12-14 19:01 ` Segher Boessenkool
2022-12-14 19:01 ` Segher Boessenkool
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=20221213202535.GL25951@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 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.