Hi! I returned from vacation today, and I had a look at the gnulib buildbot summary available from:
http://autobuild.josefsson.org/gnulib/ Several modules -- acl, argmatch, backupfile, closeout, copy-file, etc, essentially all failed modules except fts-lgpl -- now fail with an error output like the one below. Any ideas what may have caused this? It seems absolute-header.m4 should have been included in the file list, but I'm not sure which module is responsible. Btw, is there interest in having automatic e-mails when, say, a module becomes unbuildable, and have been in an unbuildable state for more than, say, 5 days? I don't like noisy e-mails, but it seems like it should be possible to write a script that is conservative enough to only send mails when there likely is a real problem. Ideas on how the logic to decide whether to send an e-mail or not should work would be useful. I don't think people will remember to look at the summary page often enough to make it worthwhile. /Simon + /data/gnulib/gnulib/gnulib-tool --dir /data/gnulib/gnulib/../build/acl --with-tests --create-testdir acl Module list with included dependencies: acl error exit exitfail gettext-h inline quote quotearg stdbool wctype xalloc xalloc-die File list: lib/acl.c lib/acl.h lib/error.c lib/error.h lib/exit.h lib/exitfail.c lib/exitfail.h lib/gettext.h lib/quote.c lib/quote.h lib/quotearg.c lib/quotearg.h lib/stdbool_.h lib/wctype_.h lib/xalloc-die.c lib/xalloc.h lib/xmalloc.c m4/acl.m4 m4/error.m4 m4/exitfail.m4 m4/inline.m4 m4/mbrtowc.m4 m4/mbstate_t.m4 m4/onceonly_2_57.m4 m4/quote.m4 m4/quotearg.m4 m4/stdbool.m4 m4/wctype.m4 m4/wint_t.m4 m4/xalloc.m4 executing aclocal -I glm4 executing mkdir build-aux executing autoconf configure:6145: error: possibly undefined macro: gl_ABSOLUTE_HEADER If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
