Nick>
AC_CONFIG_COMMANDS_POST([cat >conftest.mk <<'EOF'
configure: config.status
false
EOF
while ${MAKE-make} -f conftest.mk >/dev/null 2>&1
do
touch config.status
done])
One missing element is that there is no limit, which would be a bit of a
problem if the clock skew is severe (e.g., if configure's mtime is years
or even minutes in the future), so something extra is probably desirable
to bound the amount of time this runs to something practical.
It's easy enough to use a shell variable and limit it to 100(0) runs or
whatever.
But I have to wonder about inserting the filesystem sleep :(. Otherwise
it seems like all the runs could easily happen "at once" (e.g., in
memory/caches) and nothing would change.
Since on reasonable systems, as you say, the loop would never be
entered, it shouldn't create a delay.
Anyway, later for that. --thanks, karl.
