Skip Montanaro <skip@pobox.com> writes: > Agreed. Most machines are fast enough nowadays that the absence of > config.cache isn't a major stumbling block. If they are that > sensitive to the performance reduction, they can install autoconf > themselves and generate a local version of the configure script. I found that the most convenient way to get configure caching is to define a variable CONFIG_SITE pointing to a file that reads if test "$cache_file" = /dev/null; then cache_file="$HOME/.ac/config.cache" fi That way, all configure scripts will share a cache. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4