With the optimized sanity check that only sleeps sometimes (and
if not, then sometimes near the end of configure), currently the
configure output may change from one run to the other, depending
on timing only. The actual semantics are harmless, but since
people diff configure output it seems better to stabilize that.
No semantic change other than that. Pushed to resurrected
sanity-sleep-fix-master branch, merging to master.
Thanks,
Ralf
More stable configure output from sanity check.
* m4/sanity.m4 (AM_SANITY_CHECK): Always print check line
about ensuring newer files, even if we don't actually need
to wait any more.
diff --git a/m4/sanity.m4 b/m4/sanity.m4
index 94e1e51..ba97076 100644
--- a/m4/sanity.m4
+++ b/m4/sanity.m4
@@ -73,12 +73,12 @@ am_sleep_pid=
if grep 'slept: no' conftest.file >/dev/null 2>&1; then
( sleep 1 ) &
am_sleep_pid=$!
- AC_CONFIG_COMMANDS_PRE(
- [if test -n "$am_sleep_pid"; then
- AC_MSG_CHECKING([that generated files are newer than configure])
- wait $am_sleep_pid
- AC_MSG_RESULT([done])
- fi])
fi
+AC_CONFIG_COMMANDS_PRE(
+ [AC_MSG_CHECKING([that generated files are newer than configure])
+ if test -n "$am_sleep_pid"; then
+ wait $am_sleep_pid
+ fi
+ AC_MSG_RESULT([done])])
rm -f conftest.file
])
