I'm tracking down why I get warnings from dpkg-shlibdeps on a package that builds dlopen modules with libtool. For reference, a build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=jabberd2&arch=amd64&ver=2.3.4-1%2Bb1&stamp=1446749350 According to dpkg-shlibdeps dlopen modules should not have a soname: "A private library (like a plugin) should not have a SONAME and doesn't need to be versioned." See http://linux.die.net/man/1/dpkg-shlibdeps for more text. However when I build the package manually I can see that libtool does add a soname to the module: jas@latte:~/src/jabberd2/sm$ /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -funsigned-char -module -export-dynamic -o mod_amp.la -rpath /usr/local/lib/jabberd mod_amp.lo ../subst/libsubst.la -lssl -lcrypto -lgsasl -ludns -lidn -lexpat -lresolv -lcrypt -ldl -lz libtool: link: rm -fr .libs/mod_amp.la .libs/mod_amp.lai .libs/mod_amp.so .libs/mod_amp.so.0 .libs/mod_amp.so.0.0.0 libtool: link: gcc -shared -fPIC -DPIC .libs/mod_amp.o -Wl,--whole-archive ../subst/.libs/libsubst.a -Wl,--no-whole-archive -lssl -lcrypto /usr/lib/libgsasl.so -ludns -lidn /usr/lib/x86_64-linux-gnu/libexpat.so -lresolv -lcrypt -ldl -lz -O2 -Wl,-soname -Wl,mod_amp.so.0 -o .libs/mod_amp.so.0.0.0 libtool: link: (cd ".libs" && rm -f "mod_amp.so.0" && ln -s "mod_amp.so.0.0.0" "mod_amp.so.0") libtool: link: (cd ".libs" && rm -f "mod_amp.so" && ln -s "mod_amp.so.0.0.0" "mod_amp.so") libtool: link: ( cd ".libs" && rm -f "mod_amp.la" && ln -s "../mod_amp.la" "mod_amp.la" ) jas@latte:~/src/jabberd2/sm$ What is correct here? Is libtool is doing the right thing in adding the soname? /Simon
signature.asc
Description: PGP signature
_______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool