https://sourceware.org/bugzilla/show_bug.cgi?id=24815
Ismael Luceno changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=24815
--- Comment #9 from Ismael Luceno ---
(In reply to Fangrui Song from comment #7)
> -Wl,-t,-y,lzma_end is also useful
>
> When linking an executable, something like --no-allow-shlib-undefined is the
> default (the opposite allow-shlib-undefine
https://sourceware.org/bugzilla/show_bug.cgi?id=24815
--- Comment #8 from Ismael Luceno ---
# For completeness, this is from the glibc system that's otherwise equal to the
musl-libc one:
$ gcc -v test.c -lxml2 2>&1 | awk
'$1~/collect2$/{for(i=1;i<=NF;i++)print$i;exit}'
/usr/lib/gcc/x86_64-pc-linu
https://sourceware.org/bugzilla/show_bug.cgi?id=24815
--- Comment #5 from Ismael Luceno ---
(In reply to Alan Modra from comment #4)
> What target did you use to configure binutils? If it didn't match
> *-*-linux-* then some linker features are not enabled.
From the build log:
> checking build
https://sourceware.org/bugzilla/show_bug.cgi?id=24815
--- Comment #3 from Ismael Luceno ---
Just for the record:
# One random glibc system (gcc 8):
$ gcc -v test.c 2>&1 | awk '$1~/collect2$/{for(i=1;i<=NF;i++)print$i;exit}'
/usr/lib/gcc/x86_64-linux-gnu/8/collect2
-plugin
/usr/lib/gcc/x86_64-lin
https://sourceware.org/bugzilla/show_bug.cgi?id=24815
--- Comment #2 from Ismael Luceno ---
(In reply to Nick Clifton from comment #1)
> Hi Ismael,
>
> Have you tried linking with the "--allow-shlib-undefined" linker command
> line option enabled ?
>
> By default the ld linker insists tha
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: ismael at linux dot com
Target Milestone: ---
The system I'm having problems with is a musl-libc based system; I've an almost
identical system with glibc which works fine.
$ echo 'int
