> What's wrong with "rm config.cache"? autoconf 2.50+ does not even create > a config.cache by default any more. The problem is when someone does "cvs update" and suddenly everything breaks because they got a newly configured configure which doesn't like the config.cache they've got sitting around.