Hi Eric,
> Is it worth trying to silence the spurious "Alarm clock" message
Yes: The normal configure output should be as regular as possible,
because we want users to report anomalies to us.
> by changing strstr.m4 (and friends with related timeout idioms) to use:
>
> static void quit (int sig) { exit (sig + 128); }
> ...
> signal (SIGALRM, quit);
>
> instead of the current:
>
> signal (SIGALRM, SIG_DFL);
If you write it like this, it will be a no-op (because the shell does
not see the signal that killed the process, it sees the exit code of the
process). You need to write
static void quit (int sig) { exit (1); }
with an exit code between 1 and 127.
Affected files: strstr.m4, strcasestr.m4, memmem.m4.
Bruno
