Matthias, thanks for the objects.
I can't see a way of getting the info we wanted on the command line,
but I hacked up a linker to print the symbol that causes each as-needed
object to be pulled in. The one that was causing libnl-route.so.3 to be
pulled in was __aeabi_d2ulz.
__aeabi_d2ulz is normally provided by libgcc. I notice that libnl-route
isn't linked against libgcc.so though, and presumably used the static
version instead. I wonder whether that was from linking libnl-route
with --static-libgcc, from some libtool weirdness, or something else.
A workaround would be to link against libgcc.so instead.
The bug is that __aeabi_d2ulz is defined as an alias of __fixunsdfdi.
__fixunsdfdi is correctly marked as hidden in libgcc.a,
but __aeabi_d2ulz isn't. So this is indeed a GCC bug.
** Changed in: binutils-linaro
Status: New => Invalid
** Also affects: gcc-linaro
Importance: Undecided
Status: New
** Changed in: gcc-linaro
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823711
Title:
libvirt version 0.9.2-4ubuntu8 failed to build on armel
To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils-linaro/+bug/823711/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
