[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221214190119.GO25951@gate.crashing.org>
Date: Wed, 14 Dec 2022 13:01:19 -0600
From: Segher Boessenkool <segher@...nel.crashing.org>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Ben Hutchings <ben@...adent.org.uk>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"linux-trace-devel@...r.kernel.org"
<linux-trace-devel@...r.kernel.org>,
Salvatore Bonaccorso <carnil@...ian.org>
Subject: Re: [PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35
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
Powered by blists - more mailing lists