On Sat, 03 Sep 2005, mts.spb.s...@mail.ru wrote: > I did not have lzo's lib and headers before I attempted OpenVPN > port, so I had to "./configure --disable-lzo".
So get LZO, compile and install it, then compile OpenVPN. > When I ported OpenSSL (long ago) - I ./configure'd it to use zlib. Doesn't matter. Why would OpenVPN care for zlib? > Now, when I use the resulting ssl.lib for OpenVPN (or any other > SSL-dependent package) - I have to link with zlib as well (otherwise > I get unresolved symbols errors). Right. > What if I port lzo too and use it for OpenVPN configuration? > I will still have to link with the zlib, but which compression the > OpenVPN daemon will use if lzo is enabled in it's configuration? If OpenSSL wants zlib, you need to link with it, no matter if LZO is there or not. LZO is a different compression, not compatible with zlib. -- Matthias Andree
