Hi, On Mon, Jan 17, 2011 at 10:48:01PM +0100, Matthias Andree wrote: > Am 17.01.2011 22:30, schrieb Gert Doering: > > > since there's folks on this list that understand configure way better > > than I do... > > > > Building OpenVPN on Solaris and on NetBSD fails "as is" because configure > > does not find the lzo headers and library. > > > > On NetBSD, these are (usually) installed by pkgsrc, and live in > > /usr/pkg/include and /usr/pkg/lib. > > There would surely be a pkgsrc package that passes the proper > CPPFLAGS/LDFLAGS. > ftp://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/net/openvpn/README.html
Yes, if building from pkgsrc, the caller takes care to make sure
"everything works".
It's just if I grab the tarball and run "configure" that it doesn't find
lzo - even if it's in "the standard place for that OS".
> > On Solaris, if installed "from the source", the LZO stuff lives in
> > /usr/local/include and /usr/local/lib (same place the libraries would
> > end up on NetBSD if installed manually, not from pkgsrc).
>
> Unless you install from Blastware, or Sunfreeware, or Pkgsrc, or OpenPKG,
> or...
> (you name it) -- each with its own default directories.
Yeah, sure. But especially /usr/local/<stuff> seems to be something
that normally "just works" (being $prefix/<stuff> by default), but
doesn't seem to in OpenVPN
> Until that time, passing CPPFLAGS and LDFLAGS on the ./configure command line
> like ./configure CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib would
> do
> the trick.
Well, I know how to do that, of course :-) - there's even
"--with-lzo-header=..." and "--with-lzo-lib=..." - but I still wonder if
life shouldn't be easier for the 95%-case on a given distribution.
"If other packages can get this automatically, why do we need switches
for OpenVPN"?
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
pgpSZbFyviykS.pgp
Description: PGP signature
