LYNX-DEV config caching (was BUG? Problem with suggested name)

[Klaus Weide]

On Fri, 26 Sep 1997, T.E.Dickey wrote:

> > On Fri, 26 Sep 1997, Klaus Weide wrote:
> > 
> > > I think there may still be problems with the caching of configure results,
> > > did you have a config.cache around when running configure?  If so,
> > > try to remove it and run configure again.
> > > 
> > This seems to crop up over and over (not just for Lynx). I've been caught
> > by not deleting config.cache.  Why can't we set ./configure to first
> > delete config.cache etc, and do a clean pass each time? Its not as if the
> > configure phase is especially long.
> I don't think that would work -- for long -- since it relies on getting to
> the configure script's input file before it needs it.
> 
> Except for testing, I run configure within a wrapper that deletes
> config.cache, etc., anyway, since I'd only re-run configure if I wanted to
> change the environment (e.g., pick a different compiler).

Since people have problems with it, nobody has spoken in favor of it, and
you are not testing it:
Can't the configure caching simply be disabled (or not be enabled)?

    Klaus

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;