Jan Prikryl <[EMAIL PROTECTED]> writes:
> > Yup. It's not the default for OpenSSL, though. It installs in
> > /usr/local/ssl/lib by default. As `configure --help' tells you:
>
> Well, as a "normal" user I would expect the configure script will be
> able to cope with the fact that OpenSSL has been installed in a more
> or less "standard" system path.
I started to implement this, but had problems because you can't set LDFLAGS
to have a particular library path and run AC_CHECK_LIB, then change LDFLAGS
and re-run AC_CHECK_LIB. configure caches the results of the first check
and re-uses them for the second check, not realizing that LDFLAGS having
been set has a side-effect of changing the potential results of the check.
Presumably the AC_CHECK_LIB checks would have to be rewritten as custom
checks to get around this.
> On my RedHat linux the current Makefile still compile with
> -I/usr/local/ssl/include, and links with -L/usr/local/ssl/lib even if
> there is no such a directory on my system. It works, of course, as on
> RedHat installs OpenSSL into /usr/lib.
>
> > It would be very easy to modify configure to try a couple more
> > directories for SSL_ROOT besides the default /usr/local/ssl. In
> > fact, I was expecting to add automatic checks for /usr/local and
> > /usr in my second pass at this.
>
> I would really plead for the libssl check looking for the library not
> only in /usr/local/ssl/lib, but also at least in /usr/lib and
> /usr/local/lib (and maybe /opt/lib or /opt/ssl/lib and
> /usr/freeware/lib - the latter being SGI specific) and setting the
> include paths and library paths appropriately.
Well, feel free to have at it. I don't have any more time to spend on this
at the moment (my duties in "the real world" call). In the meantime, at
least I've updated INSTALL to tell you how to properly use --with-ssl:
If you have OpenSSL installed in its default /usr/local/ssl directory
(i.e. libraries are in /usr/local/ssl/lib), you can simply
`configure --with-ssl'. If you have it installed elsewhere, you need
to specify your alternate OpenSSL root directory. For instance, if
libcrypto.* and libssl.* are in /usr/local/lib, you need to
`configure --with-ssl=/usr/local'.
Also, please note that unlike with Christian Fraenkel's initial
implementation of the OpenSSL support, you won't just "silently" get a wget
without https://... support if you don't tell it where the OpenSSL libraries
are. Instead, you'll get this hard-to-miss notice:
[...]
checking for RSA_new in -lcrypto... no
checking for SSL_new in -lssl... no
WARNING: Failed to link with OpenSSL libraries in /usr/local/ssl/lib.
Wget will be built without support for https://... URLs.
checking whether NLS is requested... yes
language catalogs: cs da de el et fr gl hr it ja nl no pl pt_BR ru sk sl sv zh
[...]
---------------------------------------------------------------
Dan Harkless | To help prevent SPAM contamination,
GNU Wget co-maintainer | please do not mention this email
http://sunsite.dk/wget/ | address in Usenet posts -- thank you.
