Re: [PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35

2022-12-14 Thread Segher Boessenkool
On Wed, Dec 14, 2022 at 03:33:24PM +, 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

Re: [PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35

2022-12-14 Thread Christophe Leroy
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

Re: [PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35

2022-12-13 Thread Segher Boessenkool
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

[PATCH] [BACKPORT FOR 4.14] libtraceevent: Fix build with binutils 2.35

2022-12-13 Thread Christophe Leroy
From: Ben Hutchings [upstream commit 39efdd94e314336f4acbac4c07e0f37bdc3bef71] In binutils 2.35, 'nm -D' changed to show symbol versions along with symbol names, with the usual @@ separator. When generating libtraceevent-dynamic-list we need just the names, so strip off the version suffix if