That's a great speedup!
In my experience, the only time config.cache is a problem is if
you make a change to your system (install a new program, etc)
or try to make a copy of a source directory and then recompile
it on a new platform.
To address this, we should just make sure that "make veryclean"
gets rid of the "config.cache" files, including ones that might
be in subdirectories.
Go ahead and check it into the HEAD; if we have any problems,
we'll address them before we release 1.1.
Matt Brubeck wrote:
> Because of our multi-directory autoconf setup, I find that running
> './configure -C' (to enable config.cache) reduces running time for the
> script from 125 seconds to 71 seconds.
> Would it be a good idea to enable the cache-file option by default in the
> config script? I'm not quite clear on exactly what conditions can lead to
> problems with the cache file, and whether we need to worry about that.
> At the very least, perhaps the README should at least mention the -C
> option. It can't hurt to use it the first time configure is run, and it
> can shave a whole minute from the build time.
> Audacity-devel mailing list