Date: Tue, 6 Nov 2012 01:03:35 +0000 (UTC) From: Dan Mahoney <dmahoney@isc.org> To: questions@freebsd.org Subject: Linker Flags against Kerberos5 Libraries Message-ID: <alpine.BSF.2.00.1211030051220.98242@bikeshed.isc.org>
next in thread | raw e-mail | index | archive | help
Hey all, I've been working with someone doing development against the stock kerberos libraries installed in FreeBSD 8.3, and they've noticed that the symbols present in some of the kerberos libraries don't stand on their own. For example: configure:13089: cc -o conftest -O2 -pipe -fno-strict-aliasing -I/usr/local/include -L/usr/local/lib conftest.c -lkrb5 -lasn1 -lcom_err -lcrypto -lcrypt -lpam >&5 /usr/lib/libasn1.so: undefined reference to `rk_strpoolcollect' /usr/lib/libkrb5.so: undefined reference to `bswap16' /usr/lib/libkrb5.so: undefined reference to `hx509_certs_init' /usr/lib/libkrb5.so: undefined reference to `hx509_cert_get_serialnumber' /usr/lib/libkrb5.so: undefined reference to `strlwr' /usr/lib/libasn1.so: undefined reference to `rk_hex_encode' /usr/lib/libkrb5.so: undefined reference to `hx509_cert_find_subjectAltName_otherName' /usr/lib/libkrb5.so: undefined reference to `hx509_certs_find' /usr/lib/libkrb5.so: undefined reference to `net_write' /usr/lib/libkrb5.so: undefined reference to `socket_sockaddr_size' /usr/lib/libkrb5.so: undefined reference to `hx509_verify_attach_anchors' [...] >From this, it would seem to be the case that any program linked against any of the Kerberos libraries will fail unless linked against ALL of them, and the libraries don't seem to depend on each other. My questions: 1) Is there a sane way of detecting the required linker flags? 2) Is there a better mailing list I should be asking these on? -Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1211030051220.98242>