"Dan Harkless" <[EMAIL PROTECTED]> writes:
> > 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.
Why not? Some programs do exactly that. Configure caching is mostly
a failed experiment anyway. It used to be interesting to developers
who ran configure every now and then on the hardware of the time.
Today hardware is fast enough that configure runs in a short amount of
time, so the initial "itch" is no longer there.
> 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.
If we abort on `--with-ssl', there should definitely be a way of
saying "autodetect SSL". In fact, I think such an autodetect thing
should be the default.
