Roumen Petrov <bugtr...@roumenpetrov.info> writes: > wf...@niif.hu wrote: > >>> So the right question is did reporter test with FSF version? >> >> I'm the reporter, and I didn't test any other version, as I wasn't >> even sure whether my example was correct and was supposed to work. > > You sample is correct . One minor nit is AM_PROG_AR - it is not > required for posted example. If you project requires use of this macro > you should request automake 1.11.2 as minimum.
Hi Roumen, Thanks for the confirmation. Initially I didn't include AM_PROG_AR in the sample, but then autoreconf emitted much noise like /usr/share/automake-1.16/am/ltlibrary.am: warning: 'a/liba.la': linking libtool libraries using a non-POSIX /usr/share/automake-1.16/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac' Makefile.am:4: while processing Libtool library 'a/liba.la' (and the same for libb), and eventually I gave in. > Result on posted test case - pass: > $ ./translib ; echo $? > 12 Thanks for posting your results. Meanwhile I also tested with FSF libtool 2.4.6, and the final "make" indeed succeeds with it, unlike with Debian's libtool. The decisive difference is that with the FSF version the full build path to libb.so is explicitly added to the final link command, thus the linker needn't search for it by itself. On the other hand, this overlinks the final binary: $ objdump -p .libs/translib | fgrep NEEDED NEEDED liba.so NEEDED libb.so NEEDED libc.so.6 libb.so is unneeded here (but is present in the installed program as well). Coincidentally, the most prominent search result https://wiki.mageia.org/en/Overlinking_issues_in_packaging mentions that "this is fixed using a patch from Debian" for libtool. What's your position on this? Is overlinking a problem or not? (It causes problems for distributions.) Should everybody use --as-needed globally to combat it? Something else entirely? -- Thanks, Feri
