/ Zope / Apsis / Pound Mailing List / Archive / 2012 / 2012-02 / Compiling pound -- custom openssl install dir

[ << ] [ >> ]

[ Remove Backend Headers? / Sauron99(at)gmx.de ] [ poundctl not working / Robert Hicks ... ]

Compiling pound -- custom openssl install dir
"Andreas H." <lists(at)hilboll.de>
2012-02-20 17:35:27 [ FULL ]

trying to compile Pound 2.6, I'm running into issues using my
self-compiled openssl 0.9.8t:

I compiled openssl and installed it into /usr/local/openssl_build:

   worker1:/usr/local/src/Pound-2.6 # ls -l
   insgesamt 3888
   drwxr-xr-x 2 root root    4096 20. Feb 17:11 engines
   -rw-r--r-- 1 root root 3375606 20. Feb 17:11 libcrypto.a
   -rw-r--r-- 1 root root  582034 20. Feb 17:11 libssl.a
   drwxr-xr-x 2 root root    4096 20. Feb 17:11 pkgconfig

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
   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

Do I understand this correctly that when I statically link agains
openssl, I only need the Pound install on my production machine, and not
the openssl installation?

Any help is greatly appreciated :)


Re: [Pound Mailing List] Compiling pound -- custom openssl install dir
Jonas Pasche <jpasche(at)jonaspasche.com>
2012-02-20 17:49:55 [ FULL ]
Hi Andreas,

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:


signature.asc application/pgp-signature 199 Bytes

Re: [Pound Mailing List] Compiling pound -- custom openssl install dir
"Andreas H." <lists(at)hilboll.de>
2012-02-20 18:23:51 [ FULL ]
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 ...


Am 20.02.2012 17:49, schrieb Jonas Pasche:[...][...][...]