avoiding undesirable undef[weak] syms after relocatable linking

H.J. Lu hjl.tools@gmail.com
Sat Apr 13 13:52:31 GMT 2024


On Sat, Apr 13, 2024 at 3:15 AM Alexandre Oliva <oliva@adacore.com> wrote:
>
> Hello, Nick,
>
> On Apr 12, 2024, Nick Clifton <nickc@redhat.com> wrote:
>
> > Hi Alex,
> >> And here's how to trigger the problem:
> >> as t.s -o t.o && ar cr t.a t.o && ranlib t.a && as m.s -o m.o &&
> >> ld m.o -o m -r && nm m | grep bar
> >> w bar
>
> > Which version of the binutils are you using ?  And for which target ?
>
> Originally, 2.42 snapshots on multiple vxworks targets, but I'd tried on
> x86_64-linux-gnu as well.  Unfortunately, I see now that I made a
> mistake in the command posted by email: somehow I dropped t.a from the
> link command, presumably while editing it to remove local artifacts.
> Please accept my apologies.  Here's the correct command, now (not)
> adjusted, so that it runs from the top of a binutils build tree.  The
> (unmodified) [tm].s files are attached.
>
> $ gas/as-new t.s -o t.o && binutils/ar cr t.a t.o && binutils/ranlib t.a && gas/as-new m.s -o m.o && ld/ld-new m.o t.a -o m -r && binutils/nm-new m | grep bar
>                  w bar
> $ ld/ld-new --version
> GNU ld (GNU Binutils) 2.42.50.20240413
> [...]
> $ git log
> commit 4ad25f3bed6bc4c010962b11fde1c70ce8c22cae
> [...]
>
>

Please open a bug report.

Thanks.

-- 
H.J.


More information about the Binutils mailing list