On Mon, Jun 17, 2024, at 10:30 PM, Jacob Bachmeyer wrote: ... Don't have enough brain right now to comment on any of the rest of your suggestions, but:
>once conftest.file is newer than configure, surely > config.status, which is produced after all tests are run, /must/ also be > newer than configure? > > How is this last check/delay actually necessary? Are there broken > systems out there that play games with causality? I regret to say, yes, there are. For example, this can happen with NFS if there are multiple clients updating the same files and they don't all agree on the current time. Think build farm with several different configurations being built out of the same srcdir - separate build dirs, of course, but that doesn't actually help here since the issue is ensuring the Makefile doesn't think *configure* (not config.status) needs rebuilt. zw
