Andreas Metzler <ametz...@downhill.at.eu.org> writes: > Recent versions of gnutls indeed are not using Debian libtool anymore. > When using Debian's patched libtool some unnecessary linkage is > removed, but libgpg-error stays. However afaict the problem used to be > masked by a libtool problem, but currently is not a libtool problem > anymore. The culprit seems to be that this test > > --------------------------- > AC_LIB_HAVE_LINKFLAGS(gcrypt,, [#include <gcrypt.h>], > [enum gcry_cipher_algos i = GCRY_CIPHER_CAMELLIA128]) > if test "$ac_cv_libgcrypt" != yes; then > AC_MSG_ERROR([[ > *** > *** libgcrypt was not found. You may want to get it from > *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ > *** > ]]) > fi > --------------------------- > gives us "checking how to link with libgcrypt... /usr/lib/libgcrypt.so > /usr/lib/libgpg-error.so", since AC_LIB_HAVE_LINKFLAGS recursively > expands la files. We therefore end up with > > /bin/bash ./libtool --tag=CC --mode=link cc [...] gnutls_psk_netconf.lo > gl/liblgnu.la x509/libgnutls_x509.la -L/usr/lib -lz -L/usr/lib -lgcrypt > -L/usr/lib -lgpg-error openpgp/libgnutls_openpgp.la > opencdk/libminiopencdk.la
I don't see that, here is what I get: checking how to link with libgcrypt... -lgcrypt However I see that the buildd's also get your result: http://experimental.debian.net/fetch.php?&pkg=gnutls26&ver=2.8.1-1&arch=ia64&stamp=1244720486&file=log&as=raw checking how to link with libgcrypt... /usr/lib/libgcrypt.so /usr/lib/libgpg-error.so Strange, it shouldn't do that. I'll see if I can track down why I get a different result than you and the buildd's. /Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org