I noticed this when testing m4 on FreeBSD:
checking whether strstr works in linear time... Alarm clock
no
That's because conftest ends via a signal in this case, and some shells,
including FreeBSD's /bin/sh, are rather verbose about processes that
died because of a signal rather than a normal exit.
Is it worth trying to silence the spurious "Alarm clock" message 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);
--
Eric Blake ebl...@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
