[gnutls-devel] minimal compile of gnutls has undefined symbols

[Nikos Mavrogiannopoulos]

On Wed, 2015-03-18 at 23:21 -0700, David Marx wrote:
> I am trying to compile up a minimal static gnutls library to use
> with a basic TLS client, such as section 6.1.1 Simple client
> example with X.509 certificate support of The GnuTLS Manual for
> version 3.3, gnutls.pdf.  I am disabling everything I can find to
> disable.  When I do, there are functions that are undefined, I
> believe some or all of these functions are being called from
> inside the gnutls library, but are ifdefed out.
> 
> set -ex
> cd gnutls-3.3.13
> ./configure \
> --prefix=/usr --mandir=/usr/share/man --bindir=/usr/bin/amd64 \
> --libdir=/usr/lib/amd64 --sbindir=/usr/sbin/amd64 \
> --disable-dtls-srtp-support --disable-alpn-support \
> --disable-rsa-export --disable-heartbeat-support \
> --disable-srp-authentication --disable-psk-authentication \
> --disable-anon-authentication --disable-dhe --disable-ecdhe \
> --disable-openpgp-authentication --disable-ocsp \
> --disable-session-tickets --disable-openssl-compatibility \
> --disable-non-suiteb-curves --disable-crywrap --disable-libdane \
> --without-p11-kit --without-tpm --without-zlib --disable-shared \
> --enable-static --libexecdir=/usr/lib/amd64 --sysconfdir=/etc/gnu \
> --infodir=/usr/share/info \
> PKG_CONFIG_PATH=/net/scapen-csx12-0/scratch/dmmarx/12a/u/components/nettle/build/prototype/i386/usr/lib/amd64/pkgconfig 
> \
> NETTLE_CFLAGS="-I /usr/include/gmp -I \
> /net/scapen-csx12-0/scratch/dmmarx/12a/u/components/nettle/build/prototype/i386/usr/include" 
> \
> NETTLE_LIBS=/net/scapen-csx12-0/scratch/dmmarx/12a/u/components/nettle/build/prototype/i386/usr/lib/amd64/libnettle.a 
> \
> HOGWEED_LIBS=/net/scapen-csx12-0/scratch/dmmarx/12a/u/components/nettle/build/prototype/i386/usr/lib/amd64/libhogweed.a
> gmake $*
> 
> I see the following undefines.

Thanks, I've committed a fix in master and added a task on ci.gitlab.com
to allow detecting regressions easier. However when you disable so much
stuff the test suite will be unusable and you'll have to add
--disable-tests as well.

regards,
Nikos