It's faster but also adds another thing that can go wrong.
If config.cache is out of date (for example, you switch compilers or use different settings), it needs to be removed.
I'm using a configure cache for many years and I never got any issue because of this cache. If the C compiler changes or if C flags (especially the optimization level) change, configure complains: I just delete the cache in this case. The error message is quite explicit and helpful.
Activity
encukou commented on Aug 6, 2025
It's faster but also adds another thing that can go wrong.
If config.cache is out of date (for example, you switch compilers or use different settings), it needs to be removed.
corona10 commented on Aug 6, 2025
I will find a contributor during PyCon KR sprint next week.
vstinner commented on Aug 6, 2025
I'm using a configure cache for many years and I never got any issue because of this cache. If the C compiler changes or if C flags (especially the optimization level) change, configure complains: I just delete the cache in this case. The error message is quite explicit and helpful.
pythongh-1547: Recommend --config-cache for configure
pythongh-1547: Also mention --cache-file=config.cache alias
pythongh-1547: Recommend --config-cache for configure
pythongh-1547: Also mention --cache-file=config.cache alias
pythongh-1547: Remove --config-cache from platform-specific configure…
pythongh-1547: Restructure --config-cache as optional speedup tip
pythongh-1547: Use tip admonition for --config-cache
pythongh-1547: Add --config-cache to macOS platform-specific configur…
Recommend `--config-cache` for `./configure` (#1794)