Do you have static libraries in your SSL lib or just shared libraries? i.e. libssl.a (static) and libssl.so (dynamic) or just one or the other?

Have you tested with ldd?

For example, on my machine, I get this showing me I'm linking dynamically.

ldd /usr/sbin/stunnel libutil.so.1 => /lib/libutil.so.1 (0x40023000) libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40027000) libnsl.so.1 => /lib/libnsl.so.1 (0x4003b000) libdl.so.2 => /lib/libdl.so.2 (0x40050000) libssl.so.2 => /lib/libssl.so.2 (0x40053000) libcrypto.so.2 => /lib/libcrypto.so.2 (0x40080000) libc.so.6 => /lib/i686/libc.so.6 (0x42000000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Regards, KAM

-----Original Message----- From: Hal Vaughan [mailto:hal@thresholddigital.com] Sent: Wednesday, March 15, 2006 12:55 PM To: Kevin A. McGrail Subject: Re: [stunnel-users] Static Version Built?

On Wednesday 15 March 2006 12:24, you wrote:

It's not going to use source. It's going to use headers and compiled libraries. Specifying it just helps point it to the correct headers and libraries if you for example, have them installed in an unusual place or have more than one set on your machine.

Does it link to those libs or incorporate them into the binary (if I'm building static with the correct command line options)?

Sorry to ask so many questions, but I've had no experience in C or C++.

Thanks,

Hal