>>>>> "PR" == Pavel Roskin <[EMAIL PROTECTED]> writes: >> Oops. Actually I'm not doing it by hand - I was thinking of what >> happens when you change configure.in rather than Makefile.am. Changes >> to configure.in are typically somewhat rarer. PR> ... and the person doing them is supposed to understand how caching works PR> and whether config.cache should be removed, edited or left as is. Make the defaults safe, and give the user the flexibility to use unsafe shortcuts using explicit directives. Passing CFLAGS directly to make is a perfect example. Allow the use of a cache file - just don't make it the default.
- Re: config.cache considered harmful Russ Allbery
- Re: config.cache considered harmful Tom Tromey
- Re: config.cache considered harmful Martin Buchholz
- Re: config.cache considered harmful Ian Lance Taylor
- Re: config.cache considered harmful Pavel Roskin
- Re: config.cache considered harmful Lars Hecking
- Re: config.cache considered harmful Olly Betts
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Olly Betts
- Re: config.cache considered harmful Pavel Roskin
- Re: config.cache considered harmful Martin Buchholz
- Re: config.cache considered harmful Harlan Stenn
- Re: config.cache considered harmful Pavel Roskin
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Greg A. Woods
- Re: config.cache considered harmful Tom Tromey
- Re: config.cache considered harmful Greg A. Woods
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Martin Buchholz
- Re: config.cache considered harmful Pavel Roskin
- Re: config.cache considered harmful Akim Demaille