Several reasons. 1. What version of libevent?
2. What openssl's installed in system? 3. Does openssl headers is compatible (the same exactly) with openssl binaries? Check them all. 09.07.2019 05:20, Chris via Unbound-users пишет: > Sorry for a stupid question. > > FreeBSD 12.0-RELEASE-p7 > > I updated to 1.9.2 and noticed unbound was linked to OpenSSL 1.0.2q: > > unbound -h > > Version 1.9.2 > linked libs: libevent 2.1.8-stable (it uses kqueue), OpenSSL 1.0.2q 20 > Nov 2018 > linked modules: dns64 respip validator iterator > > Doing a version check for OpenSSL > > openssl version > > OpenSSL 1.1.1a-freebsd 20 Nov 2018 > > So I did a new .config > ./configure --with-libevent --without-pthreads > --without-solaris-threads --with-ssl=/usr/local/openssl-1.1.1 > > But make encountered this error. > > /usr/bin/ld: warning: libcrypto.so.111, needed by > /usr/local/lib/libevent.so, may conflict with libcrypto.so.9 > /usr/bin/ld: undefined reference to symbol > `DSA_set0_key@@OPENSSL_1_1_0' (try adding -lcrypto) > //lib/libcrypto.so.111: could not read symbols: Bad value > cc: error: linker command failed with exit code 1 (use -v to see > invocation) > *** Error code 1 > > Im sure im doing something really stupid wrong, but, I don't know what > it is and have wacked away at this for hours.. > > -- "C++ seems like a language suitable for firing other people's legs." ***************************** * C++20 : Bug to the future * *****************************
signature.asc
Description: OpenPGP digital signature
