Den lör 11 nov. 2023 kl 16:43 skrev Stefan Sperling <s...@elego.de>:
> On Sat, Nov 11, 2023 at 04:34:07PM +0100, Stefan Sperling wrote: > > On Sat, Nov 11, 2023 at 04:23:52PM +0100, Daniel Sahlberg wrote: > > > As for the original problem, updating to the latest version of the Neon > > > library doesn't help, I still get the same linking error. I''m sure > there > > > is something fishy with my Debian install... > > > > Which libssl is your build trying to use? > The libssl-dev package, which is OpenSSL version 1.1.1w-0+deb11u1. > > > > There is nothing in Makefile.svn that would try to pick a particular > > version of OpenSSL. It just expects that a compatible version is > > already installed. > > > > Maybe you have multiple versions installed and that confuses things? > Don't think so. There is only one libssl.a (and libssl.so) on my system. Doing nm -g | grep OPENSSL_init_ssl (which is not the function in the error message but as I've written before SSL_library_init is just a #define for OPENSSL_init_ssl, with the appropriate define for OPENSSL_API_COMPAT) finds: 00000000000000270 T OPENSSL_init_ssl > What is the output of this command on your system (in the ~/svn > build dir): > > nm objdir/neon-0.32.5/src/ne_openssl.o | grep -i SSL_library_init > > This doesn't print anything for me. If this shows the symbol > on your system that would indicate a wrong OPENSSL_VERSION macro > being used during the build. > ne_openssl.o isn't built, the build fails already when running configure on neon. Kind regards, Daniel
