make maintainer-clean and config.cache - Mailing list pgsql-hackers

From Jeff Janes
Subject make maintainer-clean and config.cache
Date
Msg-id CAMkU=1yJYO394QLV6M7gjGRLtKf=dt8ufE-HTBFOBHzbJcWjBw@mail.gmail.com
Whole thread Raw
Responses Re: make maintainer-clean and config.cache  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
In side-note in another thread Tom pointed out the speed improvements of using an autoconf cache when re-building, which sounded nice to me as config takes an annoyingly long time and is not parallelized.

But the config.cache files gets deleted by make maintainer-clean.  Doesn't that mostly defeat the purpose of having a cache?  Am I doing something wrong here, or just thinking about it wrong?

time ./configure --config-cache > /dev/null 
real 0m21.538s

time ./configure --config-cache > /dev/null 
real 0m3.425s

make maintainer-clean > /dev/null ; 
## presumably git checkout a new commit here
time ./configure --config-cache > /dev/null 
real 0m21.260s

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: REINDEX INDEX results in a crash for an index of pg_class since9.6
Next
From: Jeff Janes
Date:
Subject: Re: compiler warning in pgcrypto imath.c