Subject: [bug#53950] [PATCH] m4: cache build env sanity checks
Sounds fine to me. Thanks.
On Sat, Feb 12, 2022 at 2:07 AM Mike Frysinger wrote:
> The current code sleeps at least 1 second to make sure the generated
> files are strictly newer than the source files. It does this for a
> few reasons: POSIX only guarantees that `sleep` accept integers, and
> filesystems have a history (c.
The current code sleeps at least 1 second to make sure the generated
files are strictly newer than the source files. It does this for a
few reasons: POSIX only guarantees that `sleep` accept integers, and
filesystems have a history (c.f. Windows) of bad timestamp resolution.
For the first part, w
When rerunning configure in an existing build dir, cache the previous
results about environment settings. There should be no need to retest
these in a dir that has already been configured.
* m4/sanity.m4: Cache sanity results.
---
m4/sanity.m4 | 11 ++-
1 file changed, 6 insertions(+), 5
