>> The other issue is caching: autoconf 2.50 will, by default, not
>> generate a config.cache, since that has caused too many problems.
Guido> Leave it as it is unless there are many complaints.
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.
Skip
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