[Openvpn-devel] Re: compile statically with LZO and SSL support?

[Dirk T. <da...@ke...>]

Charles Duffy <cduffy <at> spamcop.net> writes:

> 
> On Wed, 20 Oct 2004 14:02:13 +0000, Dirk Tronienne wrote:
> > How has the Makefile (...what else?) to be modified for LZO? Is "LDADD =
> > -static -lssl -lcrypto -lzo" correct?
> 
> If you're using static libfoo, etc. then you don't use "-lfoo"; instead
> you add "/path/to/libfoo.a" to the link command.
> 
Thanks for help but this doesn´t seem to work for me. There has to be another 
problem. I tried OpenVPN_beta14 on SuSE 9.1 

Here is what I tried:
1. ./configure --enable-lzo
2. Edit the Makefile: ADD "LDADD = -static /usr/lib/liblzo.a"
3. After starting "make" I get the following error messages:
---snip---
 sig.o socket.o socks.o ssl.o status.o thread.o tun.o work.o  -static
/usr/lib/liblzo.a -lssl -lcrypto -llzo

/root/openvpn-2.0_beta14/misc.c:108: warning: Using 'getgrnam' in statically
linked applications requires at runtime the shared libraries from the glibc
version used for linking

/usr/lib/gcc-lib/i586-suse-linux/3.3.3/../../../libcrypto.a(b_sock.o)
(text.unlikely+0x5c3): In function `BIO_get_port':: warning: Using
'getservbyname' in statically linked applications requires at runtime 
the shared libraries from the glibc version used for linking

/usr/lib/gcc-lib/i586-suse-linux/3.3.3/../../../libcrypto.a(dso_dlfcn.o)
(text.unlikely+0x183): In function `dlfcn_bind_func':
: undefined reference to `dlsym'


---snap---

Seems that there is a problem with "libc2?
I got no clue....

Perhaps any of you already has compiled openVPN with statically linked LZO
(and OpenSLL)?


Thank you,

Dirk