Thomas Munro <thomas.munro@gmail.com> writes:
> Hmm, given that configure uses more time than compiling (assuming 100%
> ccache hits) and is woefully serial, I wonder what ingredients you'd
> need to hash to have bulletproof cache invalidation for a persistent
> configure cache, ie that survives between runs.
The buildfarm uses a simple trick that seems to work remarkably well:
if the animal's previous run failed (for any reason) then blow away
the configure cache. Maybe that could be adapted here.
regards, tom lane