Re: config.cache considered harmful

[Olly Betts]

In message <[EMAIL PROTECTED]>, Pavel 
Roskin writes:
>Hello, Martin!
>
>> Let's think about when you would ever want to reuse a cache within a
>> simple single GNU package.  I claim you _never_ want to reuse that
>> config.cache file sitting in your foo-1.9 directory.  Why are you
>> re-running configure, anyways, instead of just running `make'?
>
>Because I want to try a different _configuration_:
>
>CFLAGS=-ggdb3 ./configure --enable-cute-feature --without-bloat
>
>Cache really saves time when I turn on/off debugging and optional
>features. It remains valid in this case.

It also saves a lot of time if you're using automake and doing work
that involves changing your Makefile.am-s.  Whenever one is modified,
running make will run automake to update the corresponding
Makefile.in, then rerun configure to produce a new Makefile from that
Makefile.in.

Cheers,
Olly