On Sat, Apr 16, 2005 at 01:52:39PM -0500, Bob Friesenhahn wrote: > I believe that this problem is due to a missing LDADD in the > libgcrypt Automake makefiles and I formally reported this as a bug > to the libgcrypt developers some six or eight months ago. I think I > even supplied a patch.
I am confused now. The Makefile.am in question looks like this:
----------------------------------------
[...]
lib_LTLIBRARIES = libgcrypt.la
[...]
libgcrypt_la_CFLAGS = @GPG_ERROR_CFLAGS@
libgcrypt_la_SOURCES = g10lib.h types.h cipher.h \
misc.c global.c sexp.c \
stdmem.c stdmem.h secmem.c secmem.h \
mpi.h missing-string.c module.c \
ath.h ath.c
libgcrypt_la_LDFLAGS = $(libgcrypt_version_script_cmd) -version-info \
@LIBGCRYPT_LT_CURRENT@:@LIBGCRYPT_LT_REVISION@:@LIBGCRYPT_LT_AGE@
libgcrypt_la_DEPENDENCIES = ../cipher/libcipher.la ../mpi/libmpi.la \
$(srcdir)/libgcrypt.vers
libgcrypt_la_LIBADD = ../cipher/libcipher.la ../mpi/libmpi.la \
@LTLIBOBJS@ @GPG_ERROR_LIBS@
----------------------------------------
There is no LDADD, but LIBADD (which I though to be appropriate for
this purpose). What exactly should be changed here?
> I suggest that you report this as a bug to the libgcrypt developers.
Actually I am one of these. =)
Moritz
--
Moritz Schulte
pgpFqVm8pUf8g.pgp
Description: PGP signature
_______________________________________________ Bug-libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-libtool
