Re: Autom4te.cache

[Dan Kegel]

Bill Wendling wrote:
> } | So, why doesn't this give me a better time to autoconf the configure.in
> } | if things are cached?
> } 
> } You said yourself you changed configure.ac, what did you expect???
> } 
> I added an inline comment...that was the change.
>
> Then what exactly is the use of autom4te.cache? It gets generated with
> autoconf, so one expects it to speed up autoconfing, right? Or is it only
> to speed up autoheader?
>
> } If you _need_ figures, then take these ones for instance:
> } 
> } ~/src/fileutils-4.1.5 % time ( rm -rf autom4te.cache; autoconf; rm -rf autom4te.cache; autoheader )           
> } autoheader: `config.hin' is unchanged
> } ( rm -rf autom4te.cache; autoconf; rm -rf autom4te.cache; autoheader )  
> 72,61s user 1,05s system 97% cpu 1:15,44 total
> } ~/src/fileutils-4.1.5 % time ( rm -rf autom4te.cache; autoconf; autoheader )   
> } autoheader: `config.hin' is unchanged                           
> } ( rm -rf autom4te.cache; autoconf; autoheader )  38,10s user 0,51s system 97% cpu 39,470 total

The name, autom4te.cache, is quite cryptic.

Any chance it could be renamed autoconf.cache?  Or is that a silly question?

- Dan
(who is annoyed that he has to modify all his build scripts to delete
autom4te.cache now before packaging up his source trees)