21 Jun
2024
21 Jun
'24
10:07 p.m.
On 6/20/24 8:34 PM, Alexis wrote:
Warner Losh <imp(a)bsdimp.com> writes:
Well, `all' is pretty broad.
You can set some site-specific defaults:
https://www.gnu.org/software/autoconf/manual/autoconf-2.63/html_node/Site-D…
and use a site-specific cache file:
https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Cache-…
This cache file can be written by every `configure' run, if you like. It's
just a shell script.
Isn't that what thecautoconf cache is for?
There's a cross-project cache? That is, a cache not just for the project
for which autoconf was run, but for _all_ software built on that machine?
(Over the decades i've regularly observed
instances where autoconf doesn't
seem to be making use of results of its previous runs for a particular
project; i don't know if that's because the build maintainer didn't
configure autoconf correctly.
You have to tell configure to use the cache file.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet(a)case.edu http://tiswww.cwru.edu/~chet/