https://sourceware.org/bugzilla/show_bug.cgi?id=24815
--- Comment #2 from Ismael Luceno <ismael at linux dot com> --- (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 that undefined symbols in shared libraries > must be resolved by other libraries/objects present on the linker command > line. (The gold linker does not default to this behaviour by the way). > The reason being that it forces builders to put all of the shared libraries > that their application needs on the command line. Thus making it clear > to anyone examining the command line, or the build system, exactly which > shared libraries are needed by the application. Hi Nick, That seems to work fine. Now, the thing is that I don't see GCC calling ld with that argument on the glibc-based system... yet it links the file correctly... One fundamental difference though, is that the glibc system is using the lto plugin. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
