[FYI 0/2] {maint} tests: fix a spurious failure when run in a VPATH build

2012-11-07 Thread Stefano Lattarini
This failure was breaking make distcheck. Not a big deal, but I want to release 1.12.5 soon enough, so better fix it now. Stefano Lattarini (2): tests: rename $am_testauxdir - $am_testaux_srcdir tests: new variable $am_testaux_builddir t/ax/tap-summary-aux.sh| 2 +-

[PATCH 1/2] {maint} tests: rename $am_testauxdir - $am_testaux_srcdir

2012-11-07 Thread Stefano Lattarini
This is just a preparatory change in view of a future commit. * t/ax/test-defs.in: Here. * t/ax/tap-summary-aux.sh: And here. * t/ax/testsuite-summary-checks.sh: And here. * t/distcheck-missing-m4.sh: And here. * t/distcheck-outdated-m4.sh: And here. * t/self-check-shell-no-trail-bslash.sh: And

Re: [PATCH 6/6] aclocal: avoid spurious warnings from autom4te with AC_CONFIG_MACRO_DIRS

2012-11-07 Thread Nick Bowler
On 2012-11-03 13:36 +0100, Stefano Lattarini wrote: To allow us to work around this issue, autom4te has introduced a new singleton warning category, 'm4require-without-m4defun', that allow us to silence that particular kind of warnings (and only it). [...] diff --git a/configure.ac

Re: [PATCH 6/6] aclocal: avoid spurious warnings from autom4te with AC_CONFIG_MACRO_DIRS

2012-11-07 Thread Eric Blake
On 11/07/2012 01:08 PM, Nick Bowler wrote: I really think this test needs to be done at runtime. Two reasons: (1) A user may first ugprade Automake, then upgrade Autoconf. They will then get the spurious warnings even though they have sufficiently recent versions of both

[FYI] Merge branch 'maint' into master

2012-11-07 Thread Stefano Lattarini
commit 93c2c33e04e4e5b78da45ec8c251899acce5d322 Merge: dd3fb7e bd0d41d Author: Stefano Lattarini stefano.lattar...@gmail.com Date: Wed Nov 7 21:51:01 2012 +0100 Merge branch 'maint' * maint: tests: new variable $am_testaux_builddir tests: rename $am_testauxdir -

[FYI] {master} tests: remove mostly-redundant tests on silent rules

2012-11-07 Thread Stefano Lattarini
We used to have several couples of tests named like 'silent-foo-gcc.sh' and 'silent-foo-generic.sh'. Differently from what the names suggest, the first test in such a couple (that is, silent-foo-gcc.sh) was not meant to check specific GCC-related features, but rather to check how the silent rules

Re: [PATCH 6/6] aclocal: avoid spurious warnings from autom4te with AC_CONFIG_MACRO_DIRS

2012-11-07 Thread Stefano Lattarini
Hi Eric, sorry for the delay. On 11/07/2012 09:33 PM, Eric Blake wrote: On 11/07/2012 01:08 PM, Nick Bowler wrote: I really think this test needs to be done at runtime. Two reasons: (1) A user may first ugprade Automake, then upgrade Autoconf. They will then get the spurious

Re: [PATCH 6/6] aclocal: avoid spurious warnings from autom4te with AC_CONFIG_MACRO_DIRS

2012-11-07 Thread Eric Blake
On 11/07/2012 04:23 PM, Stefano Lattarini wrote: Allowing file inclusion as the witness of whether to warn would work even for older autoconf (where including the file has no effect), rather than the current situation of warning about an unknown option. Good thinking. And since aclocal is