Hacker News new | past | comments | ask | show | jobs | submit login

I could have sworn that config.cache used to be on by default. And indeed it was until autoconf-2.50 which was released in 2001.



Interesting; do you know / did they document why it was disabled?


I couldn't find an explanation but my guess is that it probably had some edge case failures (like corrupt files after an abort) or it didn't invalidate the cache when autoconf or environment changes affected the test results.

I used to have a wrapper that tried to use a shared config.cache across all projects but I stopped using it around the same time. I can't remember my personal reasons either but must have been something like the above.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: