Hrvoje Niksic <[EMAIL PROTECTED]> writes:
> "Dan Harkless" <[EMAIL PROTECTED]> writes:
> > 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
>
> Is it the standard configure caching mechanism, the "(cached)" thing?
> I think that can be turned off.
Per-check, you mean? We wouldn't want to turn it off for the whole
configure run just for the benefit of this check. I looked at the autoconf
documentation but didn't see a way to turn it off for a particular
(predefined) check. Custom checks are not automatically cached, though, so
doing the AC_CHECK_LIB stuff manually would do the trick.
> > [...]
> > 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.
>
> Maybe we should even abort the build at this point. If the user said
> `--with-ssl', he probably meant it.
Yeah, I considered that, but I thought back and couldn't remember configure
ever bombing out on me. On the other hand, I have seen several configure
scripts that print out a custom summary message at the end showing how the
program ended up being configured (especially useful when some configure
options are automatic on certain OSes). I figured this message was
analogous to that approach.
A weaker reason not to abort is that someone might want to package wget with
their application and always try to configure it --with-ssl. They might
hope for SSL support but not consider it fatal if it isn't there. If our
configure bombs out if --with-ssl fails its checks, they'd have to add
--with-ssl to their main configure and force users to think about the
choice. Like a said, a relatively weak reason, but...
---------------------------------------------------------------
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.
