| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | make maintainer-clean and config.cache |
| Date: | 2019-05-04 13:16:57 |
| Message-ID: | CAMkU=1yJYO394QLV6M7gjGRLtKf=dt8ufE-HTBFOBHzbJcWjBw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2019-05-04 13:23:47 | Re: compiler warning in pgcrypto imath.c |
| Previous Message | Michael Paquier | 2019-05-04 13:06:37 | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |