Hi,
On Fri, Feb 19, 2010 at 04:53:31PM -0600, Karl O. Pinc wrote:
> > As said: I would welcome contact to someone who is using
> > uClibc+OpenVPN
> > and could help me test this and adapt the code if needed.
>
> To run the risk of harping on a theme....
>
> If the problem is that someone is './configure --no-ipv6'-ing
> ipv6 away then maybe openvpn needs to have a similar ./configure
> option? Or could ./configure just test against UCLIBC_HAS_IPV6?
This is where this discussion started: do we really need to #ifdef
the IPv6 related code in OpenVPN, or can we assume that any recent OS
that has tun/tap will provide the necessary functions anyway.
Adding lots of #ifdefs doesn't improve code readability and feature
testing, and makes future maintenance harder (because it's not always
obvious if something you change might break a different combination of
optional compile-time features that what you use).
For uClibc, the answer could be "it should be sufficient to just define
'in6_addr_any' locally in OpenVPN code, if uClibc is detected" - that's
just 16 bytes of static data.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
