Thanks, Jonas, I actually found exactly the same message in the archives, and the workaround actually works well -- even though I'm on OpenSuSE 10.3.
So I can compile Pound now, and transferring the pound and poundctl binaries to a test machine yields a running Pound :) My question: Is there any way to find out if this Pound binary is actually using the statically linked OpenSSL from my build machine and not the one which is on my test machine? Unfortunately I don't have a test machine without OpenSSL at my hand ... Cheers, Andreas. Am 20.02.2012 17:49, schrieb Jonas Pasche: > Hi Andreas, > >> However, when configuring Pound, I still get an error: >> >> worker1:/usr/local/src/Pound-2.6 # >> LDFLAGS="-L/usr/local/openssl_build/usr/local/lib" ./configure >> --prefix=/usr/local/pound_build >> --with-ssl=/usr/local/openssl_build/usr/local/openssl >> configure: *** Checking for libraries *** >> checking for dlopen in -ldl... no >> checking for socket in -lsocket... no >> checking for hstrerror in -lresolv... no >> checking for BIO_new in -lcrypto... no >> Missing OpenSSL (-lcrypto) - aborted > > Chances are that this isn't an OpenSSL problem at all. Are you compiling > with gcc 4.1.2 (e.g. on a CentOS 5 machine)? In that case it's necessary > to strip "-Wno-unused-result" from the CPPFLAGS line in the configure > script. Look here for details: > > http://www.apsis.ch/pound/pound_list/archive/2011/2011-02/1296582645000/index_html#1297290669000 > > Jonas -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
