On Sun, 2007-09-30 at 09:06 +0100, William Pursell wrote:
> Eric Blake wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > According to William Pursell on 9/29/2007 11:14 AM:
> >> I'm talking about those files named $cache_file in
> >> my $CONFIG_SITE. Since they hold lines of the form:
> >> ac_cv_func_foo=${ac_cv_func_foo=yes}
> >> the cache is invalid if I remove the package
> >> containing libfoo.
> >
> > One of the easiest ways to do this is use a site configuration to enforce
> > a global cache file. Then, when removing a package, you merely delete the
> > global cache (since the state it cached is out of date), and any package
> > you then recompile will have to rerun tests for uncached data, but can
> > share information learned from other packages and saved in the global cache.
> > http://www.gnu.org/software/autoconf/manual/html_node/Site-Defaults.html#Site-Defaults
> >
>
>
> I'm not convinced of the practicality of a single global cache file.
Agreed. IMO config.site is not useful.
> In fact, I found it completely impractical, as invoking configure
> with different settings of CFLAGS would report that the cache
> was invalid and needed to be purged.
What's even worse: A carelessly set up config.site interferes with
cross-compilation.
> I think my underlying question boild down to:
> is there anyway to update a cache file,
None that I am aware about.
> or is the
> accepted technique to simply remove it and start over?
My recommendation: Don't use config-caches.
Ralf
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
