kmx git

Commit	Date	Message
fbeda3da	2012-01-18T12:17:11	tests: move all under the same hierarchy ('tests/' directory) This simplifies the organization of the Automake source tree and reduces the (lamentably high) number of Makefiles in the Automake build system by one. It also makes the maintainer check that verifies the consistency of list of tests more self-contained and simpler. Finally, it might be a first step forward the transition to a non-recursive build system for automake (if we ever decide to go down that road fully some day). * lib/Automake/tests: All the '.pl' tests in here moved ... tests/pm: ... into this new directory. * lib/Automake/tests/Makefile.am: Remove, its meaningful contents moved ... * tests/Makefile.am: ... here, with obvious adjustments. (test_subdirs): New variable, for the sake of the recipe of 'maintainer-check-list-of-tests'. * CheckListOfTests (maintainer-check-list-of-tests): Enhance its recipe to make it able to deal with test script residing in subdirectories. * Makefile.am (maintainer-check-list-of-tests): Simplified. (TEST_SUBDIRS): Remove, no more needed. * tests/list-of-tests.mk (perl_TESTS): New variable, lists the '.pl' tests just moved into 'tests/pm'. (handwritten_TESTS): Add the contents of '$(perl_TESTS)'. * lib/Automake/Makefile.am (SUBDIRS): Remove. * configure.ac (AC_CONFIG_FILES): Update. * .gitignore: Adjust.
3d6197fe	2012-01-16T18:35:50	Merge branch 'check-html-deprecate' into maint * check-html-deprecate: recheck: fix interaction with "make -n" recheck: behave better with non-GNU make check: separate .log -> .html conversion from core testsuite harness docs: deprecate .log -> .html conversion by parallel-tests
8fec2399	2012-01-13T22:39:47	recheck: fix interaction with "make -n" * lib/am/check.am (recheck): Ensure the recipe does not erroneously remove '.log' files when running under "make -n". For the sake of NetBSD make, this also means that ... (.MAKE): ... this cannot depend on 'recheck' anymore. * tests/parallel-tests-dryrun.test: New test. * tests/list-of-tests.mk: Add it.
3da9c4c7	2012-01-16T15:38:56	vala: enhance tests * tests/vala.test: Extend test. Throw in some cosmetic and consistency changes since we are at it. * tests/vala5.test: Avoid uselessly requiring libtool. Ensure a failure happens in case VALAFLAGS are not supported as expected. Extend test in some ways. Throw in some cosmetic and consistency changes since we are at it. * tests/vala-mix.test: New test. * tests/list-of-tests.mk: Add it.
d9a7182e	2012-01-13T18:53:43	recheck: behave better with non-GNU make * automake.in (handle_tests): Also substitute '%CHECK_DEPS%' with the value of the '@check' array, containing the list of early test dependencies like '$(check_SCRIPTS)', $(check_PROGRAMS)', etc. * lib/am/check.am (recheck): Explicitly depend on '%CHECK_DEPS%'. (check, recheck): Unify the implementation of their recipes, with different code paths taken depending on the name of the target. This makes the implementation of "recheck" less brittle in the process (especially when non-GNU make and AM_MAKEFLAGS overriding are involved). * lib/am/check-html.am (check-html, recheck-html): Likewise. * tests/check.test: Adjust to avoid spurious failure. * tests/parallel-tests2.test: Improve coverage.
20f2ac90	2012-01-13T17:56:13	check: separate .log -> .html conversion from core testsuite harness That feature is to be deprecated in the 1.11.x series, and removed from the automake core in the 1.12 release, where it will instead be offered in a semi-independent extra '.am' fragment. So let's start better separating the .log -> .html conversion from the "core code" of the parallel-tests harness. Reference: <http://lists.gnu.org/archive/html/automake/2012-01/msg00005.html> lib/am/check.am (.log.html, check-html, recheck-html): Move these targets ... * automake.in (handle_tests): ... and the initialization of the TEST_SUITE_HTML variable and the cleaning of the $(TEST_SUITE_HTML) file ... * lib/am/check-html.am: ... in this new file, with related (minor) refactorings, enhancements and simplifications. * lib/am/check.am (.MAKE. PHONY, AM_RECURSIVE_TARGETS): Adjust. * lib/am/Makefile.am (dist_am_DATA): Add 'check-html.am'. * tests/parallel-tests2.test: Improve coverage.
068b2f53	2012-01-16T10:18:06	tests: list some forgotten test cases in $(TESTS) This way, they will be properly executed by "make check", and properly distributed. Our previous commit 'v1.11-647-g27f1a1c' is already paying its dividends! * tests/list-of-tests.mk (handwritten_TESTS): Add check12.test, dist-missing-included-m4.test, dist-missing-am.test, and dist-missing-m4.test.
27f1a1c9	2012-01-16T10:05:59	maintcheck: consistency of list of test scripts This is basically a backport of commit 'v1.11-358-g7b6ab07' and its follow-ups. The possibility of easily checking that the list of test scripts listed in a Makefile equals that of the tests on the filesystem has proved itself so useful that it's worth taking the annoyance of backporting it to maint. * CheckListOfTests.am: New file, backported from master (commit 'v1.11-1736-g083a75b') with minor adjustments. (maintainer-check-list-of-tests): New target, check for consistency between the list of tests defined in the including Makefile and the list of tests on the filesystem. (clean-maintcheck-testslist-tmp): New rule, to clean up temporary files that might be left around by the rules associated with the previous target. (clean-local): Depend on it. * lib/Automake/tests/Makefile.am: Include `CheckListOfTests.am'. * tests/Makefile.am: Likewise. * Makefile.am (maintainer-check-list-of-test): New target, calling recursively into `tests/' and `lib/Automake/tests/', using ... (TEST_SUBDIRS): ... this new variable. (maintainer-check): Added dependency from the new target `maintainer-check-list-of-tests'.
9d9f00ed	2012-01-15T21:07:44	tests: move list of tests in its own Makefile fragment This change will make it easier to merge maint into master, which has a similar Makefile setup in the testsuite. * tests/Makefile.am (include): Inclusion of ... * tests/list-of-tests.mk: ... this new file. * tests/Makefile.am (TESTS): Move most of its content into, and redefine in function of, ... * tests/list-of-tests.mk (handwritten_TESTS): ... this new variable. * tests/gen-parallel-tests: Update.
17542c3c	2012-01-15T20:46:43	build: silence automake build system * configure.ac (AM_SILENT_RULES): Invoke with "yes" as a parameter, to activate silent rules by default. * NEWS: Update. * Makefile.am (sc_perl_syntax): Silence its recipe unconditionally, similarly to what is done for other syntax checks. (release-stats): Be silent by default but not unconditionally, thanks to the use of $(AM_V_GEN). (path-check, git-diff): Be silent by default, thanks to the use of $(AM_V_GEN). * m4/Makefile.am ($(top_srcdir)/m4/amversion.m4): Likewise. * doc/Makefile.am ($(srcdir)/amhello-1.0.tar.gz): Likewise. * tests/Makefile.am ($(srcdir)/parallel-tests.am): Likewise. ($(parallel_tests)): Likewise.
59367c05	2012-01-14T10:32:13	test defs: backport optimized 'using_gmake' implementation * tests/defs.in (using_gmake): Backport optimized, result-caching implementation from master.
0188e0f5	2012-01-13T21:56:54	tests: unify some tests on "make -n", reducing duplication * tests/maken2.test: Merge into ... * tests/maken.test: ... this test, to avoid unnecessary code duplication. Make checks depending on GNU make conditional to the actual presence of GNU make. * tests/maken4.test: Similarly, merge into ... * tests/maken3.test: ... this test. * tests/Makefile.am (TESTS): Remove maken2.test and maken4.test.
539cae3b	2012-01-13T12:42:36	Merge branch 'fix-pr10470' into maint * fix-pr10470: dist: avoid $(distdir) removal failure on MSYS/MinGW coverage: expose automake bug#10470 (distcheck-related)
dfb5e52f	2012-01-11T18:09:07	dist: avoid $(distdir) removal failure on MSYS/MinGW This change fixes automake bug#10470. On MSYS (1.0.17) it is not possible to remove a directory that is in use, and this, together with timing issues, could cause spurious failures in the cleanup code of the "distcheck" recipe. In fact, it should be noted that assuming a directory can be removed while it the CWD of a running process is a POSIX violation: "If the directory is the root directory or the current working directory of any process, it is unspecified whether the function succeeds, or whether it shall fail and set errno to [EBUSY]." * lib/am/distdir.am (am__remove_distdir): If rm fails, sleep some seconds and retry, to give potential "pending" processes some time to exit and "release" the directory. * tests/Makefile.am (XFAIL_TESTS): Remove 'distcheck-pr10470.test'. Report and suggestions by Peter Rosin and Eric Blake.
f1df5481	2012-01-01T19:06:00	tests: fix spurious failure of 'get-sysconf.test' * tests/get-sysconf.test: Do not assume that a ChangeLog file exists in $(srcdir): now that the ChangeLog is autogenerated and not under version control anymore, this is not necessary true. Instead, if we are running from a git checkout, use "git log" to get information on the version of the automake snapshot being tested (and fall back on extracting the first ChangeLog entry otherwise). Reported by Jim Meyering in automake bug#10418. Cherry picked from commit v1.11-1675-g104f302.
657eed2e	2012-01-12T10:06:14	coverage: expose automake bug#10470 (distcheck-related) * tests/distcheck-pr10470.test: New test. * tests/Makefile.am (TESTS, XFAIL_TESTS): Add it. Report and suggestions by Peter Rosin and Eric Blake.
e064ff79	2012-01-12T09:41:06	tests: make 'aclocal-install-absdir.test' executable * tests/aclocal-install-absdir.test: Make it executable.
d850165e	2012-01-08T12:49:57	tests: require GNU make in 'vala-vapth.test' * vala-vpath.test ($required): Add the "GNUmake" requirement, since rules generated by vala support are expected to work with GNU make only.
72f7e5de	2012-01-07T01:08:11	vala: fix VPATH builds This change fixes automake bug#9859. * automake.in (lang_vala_finish_target): Create the stamp file '${derived}_vala.stamp' in $(srcdir), not in $(builddir). Also, don't try to chdir to the $(srcdir) to trigger the rebuild rules, since that is just wrong in a VPATH setup. * tests/vala-vpath.test, tests/vala2.test: Extend to catch more possible VPATH issues. * tests/Makefile.am (XFAIL_TESTS): Remove 'vala-vpath.test'. * NEWS, THANKS: Update. Co-authored-by: Stefano Lattarini <stefano.lattarini@gmail.com> Copyright-paperwork-exempt: yes
c7ee8c6d	2012-01-07T01:06:37	tests: fix some bugs in the vala-vpath test * tests/vala-vpath.test: There are (trivial) problems in this testcase that would cause the build to fail even if the core issue were resolved. Fix those. Copyright-paperwork-exempt: yes
01c3294b	2012-01-03T16:12:46	dist: do not wrap calls to 'tar' with the 'missing' script The `missing' script is meant to allow non-developers to build a package in the face of slightly-skewed timestamps (as might happen e.g. when the package is obtained from a VCS checkout rather than from a distribution tarball). It is not the business of the `missing' script to try to provide wrappers for all the maintainer tools (in this case, to tool being a decent tar program). Such wrapping of `tar' was not only inappropriate, but it was also preventing the legitimate overriding (at make runtime) of the `tar' program used in the creation of the distribution tarballs. See also automake bug#9822. * lib/missing: Don't try to specially wrap `tar' invocations anymore. * m4/tar.m4 (_AM_PROG_TAR): In the definitions of the `AMTAR' variable, do not wrap the `tar' invocation with the `missing' script anymore. Instead, allow the user to override the intended tar program at make runtime, by defining the `TAR' environment variable. [$1 == v7]: Similarly for the definitions of the `am__tar' and `am__untar' variables. Since we are at it, don't make them depend anymore on the definition of the obsolescent `AMTAR' variable. * NEWS: Update. * tests/missing-tar.test: Remove, it's obsolete. * tests/tar-override.test: New test. * tests/Makefile.am (TESTS): Update. Reported by Akim Demaille.
741a0a1e	2012-01-06T14:51:55	fixup: previous commit v1.11-627-g1e0aedc * tests/acloca18.test: Do not remove an aclocal.m4 file that is needed by a later autoconf invocation.
92f688d8	2012-01-06T13:15:17	tests: fix spurious failures due to autom4te caching * tests/aclocal9.test: Call aclocal and autoconf with the `--force' option. * tests/acloca10.test: Sleep between re-runs of aclocal and autoconf. * tests/acloca18.test: Explicitly remove also the configure script and the aclocal.m4 before re-invoking aclocal and autoconf.
4e4dae50	2012-01-03T09:06:09	install: pkglibexec_SCRIPTS is a valid prefix/primary combination It makes little sense for `libexec_SCRIPTS' to be accepted as valid while `pkglibexec_SCRIPTS' is not. So fix this inconsistency by explicitly allowing `pkglibexec_SCRIPTS' as well. It is worth noting that the inconsistency has been there for a long time, but only the quite recent commit `v1.11-373-g9ca6326' "Warnings about primary/prefix mismatch fixed and extended" has made it noisy enough to be noticed. * automake.in (handle_scripts): Also list `pkglibexec' among the prefixes valid for the `SCRIPTS' primary. * doc/automake.texi (Scripts): Likewise. * tests/primary-prefix-valid-couples.test: Update. * THANKS: Likewise. * NEWS: Likewise. Reported by Dennis Schridde on the automake list: <http://lists.gnu.org/archive/html/automake/2012-01/msg00002.html>
971000c1	2012-01-02T20:32:54	coverage: expose automake bug#10128 * tests/objext-pr10128.test: New test, still expected to fail. * tests/Makefile.am (TESTS, XFAIL_TESTS): Add it.
f4e221b6	2012-01-02T09:40:13	progs, libs: implement EXTRA_foo_DEPENDENCIES Backported from commit `v1.11-377-g6edafbb'. The feature implemented by that change is quite unobtrusive, so adding it to a maintenance release is acceptable. Also, there have been requests from real-world users for this feature since it has been implemented in master; see automake bug#9320: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9320> and this short discussion on the automake list: <http://lists.gnu.org/archive/html/automake/2010-11/msg00099.html> It would be a pity to make such users wait even more (until Automake 1.12 is out) before they could start using this feature. Thus we backport it, so that it will appear in the next maintenance version of automake (1.11.3). * automake.in (handle_programs, handle_libraries) (handle_ltlibraries): Mark EXTRA__DEPENDENCIES as recognized. doc/automake.texi (Linking, Program and Library Variables) (LIBOBJS): Document EXTRA__DEPENDENCIES. lib/am/library.am (%LIBRARY%): Also depend on $(EXTRA_%XLIBRARY%_DEPENDENCIES). * lib/am/ltlibrary.am (%LTLIBRARY%): Also depend on (%XLTLIBRARY%_DEPENDENCIES). * lib/am/program.am (%PROGRAM%%EXEEXT%): Also depend on $(EXTRA_%XPROGRAM%_DEPENDENCIES). * tests/extradep.test, tests/extradep2.test: New tests. * tests/Makefile.am (TESTS): Update. * NEWS: Update.
4337813b	2012-01-03T13:56:17	tests: fix spurious failures in 'pr300.test' This change fixes automake bug#10426. tests/pr300-lib.test: Call configure with an explicit '--libdir' option, to avoid spurious failures due to users possibly overriding '${libdir}' in ther config.site files. * tests/pr300-ltlib.test: Likewise. Reported by Bruno Haible.
28040759	2012-01-01T10:42:34	tests: make 'lzip.test' executable * tests/lzip.test: Make it executable.
2a461709	2012-01-01T10:39:10	Merge branch 'deprecate-lzma' into maint * deprecate-lzma: dist: obsolete support for lzma (superseded by xz and lzip)
e637fa2a	2011-12-30T15:54:40	dist: obsolete support for lzma (superseded by xz and lzip) The lzma utilities are today superseded by the xz utilities; in fact, the official site at <http://tukaani.org/lzma/> reads: ``LZMA Utils are legacy data compression software with high compression ratio. LZMA Utils are no longer developed, ... Users of LZMA Utils should move to XZ Utils.'' and the existing automake manual (as of 1.11.2) already says: ``dist-xz Generate an 'xz' tar archive of the distribution. xz archives are frequently smaller than bzip2-compressed archives. The 'xz' format will soon (early 2009) displace the 'lzma' format'' Also, the `dist-lzma' target still suffers of never-solved bugs, due to the too-high compression ratio its uses by default, which might cause an unacceptable memory consumption when one tries to compress or, worse, decompress the created tarballs; see also: <http://lists.gnu.org/archive/html/automake/2011-12/msg00025.html> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9658> * NEWS: Update. * doc/automake.texi (Dist, Options): State that `dist-lzma' will go away in the next major automake version. * lib/Automake/Options.pm (_process_option_list): Deprecate `dist-lzma'. * tests/lzma.test: Update.
bbce9c2b	2011-12-31T08:47:34	Merge branch 'dist-lzip' into maint * dist-lzip: dist: add support for lzip compression
bff8ceca	2011-12-30T19:22:55	test defs: more granular overriding of the make program Before this change, the only way the user could override the make program used in the automake test cases was to override the $MAKE variable in the environment. This had the annoying side effect of requiring that, whenever a non-default make program was to be used in the test cases, that same make program had to be used to drive the execution of the automake testsuite; otherwise, the recursive make invocations could pick up $MAKE from the environment, and use that instead of re-executing with the correct make. So, for example, if one wanted to try how Solaris /usr/ccs/bin/make behaved in the automake test cases, he couldn't run the testsuite in parallel mode, because that make lacks support for concurrent execution of recipes; on fast machines, this easily meant a 4x or higher slow-down. Once the problem is clear, the solution is pretty simple: allow the use of another variable, besides $MAKE, to override the make program to be used in the test cases. See also commit `v1.11-1318-g3ceeef4', that introduced a more general version of this change to the master branch. * tests/defs.in: Allow the make implementation to be used by the test cases to be overridden by the `$AM_TESTSUITE_MAKE' variable, in preference to the `$MAKE' variable.
0878bd34	2011-12-30T14:35:18	dist: add support for lzip compression * NEWS: Update. * automake.in (handle_dist): Recognize dist-lzip. (make_paragraphs): Map LZIP to dist-lzip. * doc/automake.texi (Dist, Options): Describe dist-lzip. * lib/Automake/Options.pm (_process_option_list): Recognize `dist-lzip'. * lib/am/distdir.am (dist-lzip): New target. (DIST_ARCHIVES) [?LZIP?]: Add `dist-lzip'. (dist, dist-all) [?LZIP?]: Add command to create an lzip-compressed tarball. (distcheck): Handle lzip-compressed tarballs just like the others. * tests/lzip.test: New test. * tests/Makefile.am (TESTS): Add it.
cec3f327	2011-12-30T13:47:57	Merge remote-tracking branch 'silent-fixes' into maint * origin/silent-fixes: fix: last entry in ChangeLog tests: tweak tests on silent-rules for makes without nested vars silent-rules: fallback for makes without nested vars
34749105	2011-12-28T15:15:50	tests: fix spurious failure due to autom4te caching * tests/acloca18.test: Remove stale autom4te.cache directories, to prevent racy, spurious failures. * tests/python11.test: Likewise. Fix a typo in comments since we are at it.
c87ceb55	2011-12-28T10:54:47	Merge branch 'maint' into silent-fixes * maint: maint: autogenerate ChangeLog fix: last ChangeLog entry tests: drop unnecessary requirement in 'subpkg.test' gitlog-to-changelog: new auxiliary script, synced from gnulib docs: "aclocal --install -I /abs/dir" actually copies files docs: fix node names for automake and aclocal invocations
77b2c71c	2011-12-27T19:31:03	tests: drop unnecessary requirement in 'subpkg.test' * tests/subpkg.test ($required): Drop "bison", it is not required anymore since commit `v1.11-502-g7e5ae80'.
44da9cbd	2011-12-27T14:55:41	docs: "aclocal --install -I /abs/dir" actually copies files This change is for automake bug#8407. In the past, there had been some debate and confusion about whether "aclocal --install" should copy third-party .m4 files in the first directory passed to the `-I' option even when such directory was given as an absolute path, or whether it was better to do so only for directories specified with a relative path. The rationale for this latter behaviour was that, before the existence of the `ACLOCAL_PATH' variable, the only way (a poor way, I might add) for a common user to extend the search path of a system-wide installation of aclocal was to export something like ACLOCAL="aclocal -I /my/extra/macros" in the environment. Today, the correct way to proceed is undoubtedly through the use of ACLOCAL_PATH, so we can settle the question once and for all, and start verifying the correct behaviour of `-I' with a new test. * tests/aclocal-install-absdir.test: New test. * tests/Makefile.am (TESTS): Add it. * doc/automake.texi (aclocal Options): Be more explicit about this part of `--install' semantics.
0eaa8781	2011-12-26T18:23:24	tests: tweak tests on silent-rules for makes without nested vars * tests/silent-nested-vars.test: Define $MAKE to `./mymake' in the environment, so that it will be automatically picked up by configure. Related tweaks and simplifications. Remove the checks verifying that silent rules are respected also when the 'subdir-objects' option is set, the checks testing the old syntax for user-defined silent rules, and the tests using the default $MAKE programs: they are redundant w.r.t. other test cases. Related simplifications. Remove the temporary files used in a sanity check as soon as they are not needed anymore. Do not capture also the standard error of configure: we only want to grep its standard output. Consistently use `stdout' for the name of files where to save the standard output captured from make and configure, for consistency with other tests. Make grepping of configure output and of the generated Makefile stricter. Improve and tweak the `mymake' script a little. * tests/silent6.test: Make grepping of make stdout slightly stricter. After having configured with silent rules disabled, try to force the use silent rules with `make V=1'.
8493499b	2011-12-25T09:56:44	silent-rules: fallback for makes without nested vars This fixes two problems reported for Automake (Bug#9928, Bug#10237) and is in response to a bug report for building coreutils on HP NonStop OS (Bug#10234). The problem is that HP NonStop 'make' treats a line like "AM_V_CC = $(am__v_CC_$(V))" as one that expands a macro with the funny name am__v_CC_$(V instead of the desired name am__v_CC_1 or am__v_CC_0, and since the funny macro is not defined the line is equivalent to "AM_V_CC = )"; this inserts a stray ")" when $(AM_V_CC) is used, which eventually causes 'make' to fail. The basic idea is that instead of generating Makefile.in lines like "AM_V_CC = $(am__v_CC_$(V))", we generate "AM_V_CC = $(am__v_CC_@AM_V@)". We then AC_SUBST $(V) for @AM_V@ in the usual case where `make' supports nested variables, and substitute 1 (or 0) otherwise. Similarly for usages like $(am__v_CC_$(AM_DEFAULT_VERBOSITY)). With this change, make implementations that doesn't grasp nested variable expansions will still be able to run Makefiles generated using the silent-rules option. They won't allow the user to override the make verbosity at runtime through redefinition of $(V) (as in "make V=0"); but this is still an improvement over not being able to work at all. * NEWS: Document this. * automake.in (define_verbose_var): When defining the variables, use @AM_V@ rather than $(V), and use @AM_DEFAULT_V@ rather than $(AM_DEFAULT_VERBOSITY). * doc/automake.texi (Automake silent-rules Option): Explain new system. * m4/silent.m4 (AM_SILENT_RULES): Check whether `make' supports nested variables, and substitute AM_V and AM_DEFAULT_V accordingly. * tests/silent-nested-vars.test: New test. * tests/Makefile.am (TESTS): Add it.
bfc83bde	2011-12-24T10:43:26	gitignore: use only one .gitignore file, in the top-level directory * doc/.gitignore, doc/amhello/.gitignore, lib/Automake/.gitignore, lib/Automake/tests/.gitignore, tests/.gitignore: Deleted, their contents merged into ... * .gitignore: ... this top-level file. Since we are at it, improve it by anchoring files where it makes sense.
eada9138	2011-12-24T09:58:17	Merge branch 'tests-gettext-macros-require' into maint * tests-gettext-macros-require: tests: one more fixlet for gettext macros requirement
e1fad75e	2011-12-24T09:56:49	tests: one more fixlet for gettext macros requirement * tests/gettext-macros.test (configure.in): Add calls to AC_INIT and AC_PROG_CC, to avoid a spurious failure in the later aclocal invocation. Luckily, this wart wasn't causing any spurious SKIP or FAIL, but only the redundant addition to the `-Wno-syntax' option to some aclocal invocations in the gettext tests.
9ea4c454	2011-12-24T09:29:15	Merge branch 'tests-gettext-macros-require' into maint * tests-gettext-macros-require: tests: fix handling of gettext macros requirement
763f3ec3	2011-12-24T09:25:00	tests: fix handling of gettext macros requirement The code introduced in the earlier change `v1.11-581-gb7d67d5' and aimed at automatically fetching all the .m4 files provided by gettext has proven inadequate, since it hasn't managed to truly and always get all the required .m4 files. For example, it has failed to fetch the file `intldir.m4' (present in gettext 0.18.1, and where the macro `AM_GNU_GETTEXT_INTL_SUBDIR' is defined), which in turn has caused spurious SKIPs of at least the test `gettext3.test'. The reason for this debacle is that autopoint looks at the version specified in AM_GNU_GETTEXT_VERSION to decide which version of the gettext infrastructure to bring in; since we were unconditionally specifying the older 0.10.35 version, the newer `.m4' files weren't brought in. * tests/gettext-macros.test: In AM_GNU_GETTEXT_VERSION, instead of unconditionally specifying the older 0.10.35 version, specify the version of the available `gettextize' or `autopoint' program, dynamically extracted with the help of ... (extract_program_version):... this new function, and saved ... ($autopoint_version): ... in this new variable.
007455d9	2011-12-23T13:09:50	Merge branch 'missing-fixes' into maint * missing-fixes: tests: fix failure due to debugging code forgotten into a test
03f51958	2011-12-23T12:47:19	tests: fix failure due to debugging code forgotten into a test * tests/missing-tar.test: Don't ever call the `missing' script with `sh -x'; this was used for debugging, but an instance of it slipped into the committed test case. Bug revealed by a failure on a Solaris 10 system with GNU tar installed as `gtar'.
3c5d083e	2011-12-23T00:42:46	Merge branch 'tests-libtool-gettext-requirements' into maint * tests-libtool-gettext-requirements: tests: avoid spurious failure of libtool and gettext tests
39e4f272	2011-12-23T00:42:24	tests: avoid spurious failure of libtool and gettext tests On Solaris 10 (and presumably earlier), /bin/sh trips up on here-documents that contains a command substitution and are fed to a shell function: # All as expected. $ cat <<END `pwd` END /home/stefano $ echo status = $? status = 0 # An apparently innocuous function ... $ kitty () { cat; } # ... but hilarity ensues! $ kitty <<END `pwd` END /tmp/sh137723: cannot open $ echo status = $? status = 1 We need to work around this misbehaviour in a couple of our tests (whose failures where causing cascading failures in a lot of other tests). * tests/gettext-macros.test: Avoid the use of command substitution in a here-document passed to the `indent' function, by using the `echo' builtin instead. * tests/libtool-macros.test: Likewise. See also: <http://lists.gnu.org/archive/html/bug-autoconf/2011-12/msg00001.html>
5f335bed	2010-11-13T12:21:28	regex: deprecate the obsolete macro AM_WITH_REGEX This is a backport of commit v1.11-433-g37b0aee. Today, practically nobody uses the GNU rx library, which, according to its own website <http://www.gnu.org/software/rx/rx.html>, has been "decommissioned". Consequently, the automake-provided macro AM_WITH_REGEX is not used nor required anymore. Deprecate it, so that it will be possible to safely remove it in the next major automake version. * m4/regex.m4 (AM_WITH_REGEX): Give a warning of the class `obsolete' when this macro is used. * doc/automake.texi (Public Macros): Move description of `AM_WITH_REGEX' from here ... (Obsolete Macros): ... to here, and declare it as obsolete and "to be removed in a future version". * tests/regex-obsolete.test: New test. * tests/Makefile.am (TESTS): Add it. * NEWS: Update. See also: <http://lists.gnu.org/archive/html/automake-patches/2010-11/msg00131.html>
9f7864ba	2011-10-16T14:57:37	include: avoid "deleted .am file" problem * automake.in (handle_configure): When processing `configure.am', also expand `HAVE-MAKEFILE-IN-DEPS' to a boolean telling whether `MAKEFILE-IN-DEPS' is empty or not. * lib/am/configure.am [?HAVE-MAKEFILE-IN-DEPS?] (%MAKEFILE-IN-DEPS%): New target without dependencies, to avoid the "deleted .am file" problem. Emit this only when `?HAVE-MAKEFILE-IN-DEPS?' is true, to avoid generating an "empty" dependency declaration. * tests/deleted-am.test: Make grepping of error message stricter. * tests/dist-missing-am.test: Likewise. * tests/remake-deleted-am.test: New test. * tests/remake-deleted-am-2.test: Likewise. * tests/remake-deleted-am-subdir.test: Likewise. * tests/remake-renamed-am.test: Likewise. * tests/makefile-deps.test: Likewise. * tests/Makefile.am (TESTS): Add the new tests. * NEWS: Update. Fixes automake bug#9768. Report by Peter Johansson. See also commit `Release-1-10-40-gd0ebf71', which fixed a similar problem for .m4 files included by configure.ac.
b7d67d55	2011-12-14T10:35:04	tests: better handling of gettext and libtool requirements This change fixes automake bug#9807. Before this change, the automake testsuite only looked for the `.m4' files containing libtool and gettext macros definitions in the directory `${prefix}/share/aclocal' (and in the directories specified by the `dirlist' file in there, if any), where ${prefix} was the configure-time automake installation prefix (defaulting to `/usr/local'). This approach had various shortcomings and disadvantages. Let's briefly describe the three major ones. First, on most GNU/Linux systems, a libtool or gettext installed from distro-provided packages (e.g., by dpkg on Debian/Ubuntu, or by rmp on RedHat/Fedora) would have `/usr', not `/usr/local', as its ${prefix}; so, trying to run the automake testsuite with a simple "./configure && make && make check" would have failed to execute the libtool and gettext tests on most GNU/Linux distros. It's true that it was quite easy to work around this issue, by creating a proper `/usr/local/share/aclocal/dirlist' file with an entry pointing to `/usr/share/aclocal' (a workaround in fact used by most automake developers); but the typical user wasn't aware of the necessity of this trick, so the libtool and gettext tests was usually skipped on testsuite runs "in the wild", thus needlessly reducing coverage. Second, the older testsuite behaviour made more difficult for the developers to run the testsuite with non-default libtool or gettext. For example, assume the developer is working on a system that has a default libtool version 1.5 installed in the /usr/local hierarchy; to improve coverage, the developer installs also a more modern libtool version, say 2.4, in its home directory, let's say in ~/libtool-2.4; he then tries to run the automake testsuite with this more modern libtool by doing an (apparently) simple: $ PATH=$HOME/libtool-2.4:$PATH make check But the automake testsuite would still look for libtool macros in /usr/local/share/aclocal, not in ~/libtool-2.4/share/aclocal, so the wrong version of the macros would be picked up, and the tests would either fail spuriously or (which would be worse) pass without truly covering the libtool version the developers was thinking to be testing with. Worse again, the automake testsuite would unconditionally look for libtool macros in /usr/local/share/aclocal, so even something like: $ export ACLOCAL_PATH=$HOME/libtool-2.4/share/aclocal $ PATH=$HOME/libtool-2.4:$PATH make check wouldn't work. Third and last, during a "make distcheck", automake is configured with a ${prefix} pointing to a proper subdirectory of the build directory (usually `pwd`/_inst), which gets created on-the-fly; in this case, with the old approach, the automake testsuite never found the libtool and gettext macro files, ans so the libtool and gettext tests was always skipped in a "make distcheck". * tests/libtool-macros.test: New helper test, looking (with the help of the `libtoolize' script) for libtool macro files required by most libtool tests, and making them easily accessible. * tests/gettext-macros.test: New helper test, looking (with the help of the `libtoolize' script) for libtool macro files required by most libtool tests, and making them easily accessible. * tests/defs.in: Update to make it rely on the results and setups of `libtool-macros.test' and `gettext-macros.test'. * tests/Makefile.am: Declare dependency of all the logs of libtool tests from `libtool-macros.log', and all the logs of gettext tests from `gettext-macros.log'. (TESTS): Add the new tests.
a95d9dc4	2011-12-22T18:17:26	fix: typos and grammaros in comments of the new test * tests/get-sysconf.test: Fix few typos, grammaros and botched wording. Reported by Eric Blake.
fe8162b7	2011-12-22T10:34:28	tests: report useful system information in 'test-suite.log' It has already happened various times that a user has run the automake testsuite, experienced a failure, read the messages telling him "See tests/test-suite.log" and "Please report to bug-automake@gnu.org", and done exactly that -- sending us only the contents of `tests/test-suite.log', which are usually not enough to start debugging the reported failure. So we have to ask him for more details, and usually also for the `config.log' file generated by configure. It's time to fix this recurring feedback inefficiency. We do so by creating a dummy test case that takes care of copying the contents of `config.log', plus other useful system information, in the final `test-suite.log'. * tests/get-sysconf.test: New test, gathering system information and then always terminating with a SKIP, so that its output gets copied in `test-suite.log'. * tests/Makefile.am (TESTS): Add it.
e9150626	2011-12-08T22:54:18	repo: don't commit generated files in the git repository anymore It has been quite some time since autoconf and libtool have stopped committing the generated autotools files in their git repositories, with no significant ill effects we're aware of. It's true that the autoconf bootstrap process has now the minor annoyance that a pre-installed autoconf is required to complete it; but luckily automake will not have a similar annoyance, since our bootstrap script take care, through some hoops, to use the very automake and aclocal versions from the current git checkout to generate the required aclocal.m4 and Makefile.in files. In fact, this has been a necessity also in the past, because automake has been known to use in its own build system new development features that hadn't been present in any previously released automake distribution. * aclocal.m4: Delete. * configure: Likewise. * Makefile.in: Likewise. * doc/Makefile.in: Likewise. * lib/Automake/Makefile.in: Likewise. * lib/Automake/tests/Makefile.in: Likewise. * lib/Makefile.in: Likewise. * lib/am/Makefile.in: Likewise. * m4/Makefile.in: Likewise. * tests/Makefile.in: Likewise. * .gitignore: Ignore configure, aclocal.m4, and all the Makefile.in files. * configure.ac (AC_PREREQ): New macro call, to require the latest autoconf (2.68 for the moment).
75f2b50a	2011-10-30T11:55:28	missing: don't try to re-run tar with a munged command line * lib/missing: If the default `tar' program fails with the given arguments, and GNU tar is not available, don't try to re-run the default `tar' with a munged command line (e.g., ditching possibly unportable options), as that could be subtly alter the intended semantics (and maybe even create a somewhat corrupted tarball). Also, it's worth noting that the main purpose of the `missing' script is to allow a non-developer to build the package in the face of slightly-skewed timestamps, not to provide wrappers for all the maintainer tools -- so we don't have to try too hard when `missing' is just called to wrap `tar'. * tests/missing-tar.test: New test. * tests/Makefile.am (TESTS): Add it.
7f713c38	2011-12-20T21:42:54	tests: fix spurious failure on systems lacking unistd.h This is for automake bug#10324. * tests/silent-lex-generic.test (foo.l): Add a dummy #define of YY_NO_UNISTD_H, so that the generated foo.c file won't require unistd.h to be present (it is not present when compiling with, e.g., MSVC 9).
63da4921	2011-12-16T11:12:31	test defs: hack to support autoconf-wrapper programs * tests/defs.in ($AUTOCONF): Add a dummy `-B' option to the autoconf invocation, so that, when the Debian autoconf wrapper is involved, it will correctly dispatch an autoconf >= 2.50 instead of defaulting to autoconf 2.13. ($AUTOHEADER, $AUTORECONF): Likewise, but for autoheader and autoreconf respectively. Reported by Bruno Haible: <http://lists.gnu.org/archive/html/automake/2011-12/msg00039.html>
fb49574d	2011-12-16T01:46:14	tests: fix a minor spurious failure with FreeBSD make * tests/remake-am-pr10111.test: Avoid using `#' comments in makefile recipes, as these have been confusing FreeBSD make. The failure was masked by the fact that this test is currently expected to fail. Suggested by a report from Bruno Haible.
d2b76f88	2011-12-16T01:22:57	tests: make two test scripts executable * tests/remake-am-pr10111.test: Make executable. * tests/remake-m4-pr10111.test: Likewise.
ccbb437e	2011-12-14T20:53:10	readme: don't reference the old homepage at sources.redhat.com * README: Don't reference the old homepage at sources.redhat.com, which is no longer active; reference the homepage on www.gnu.org instead. See also automake bug#10157 and bug#10248. * tests/README: Likewise, and remove related extra-pedantic advice about copyright papers for test cases (we'll ask for those papers explicitly when we think they are warranted).
ca0ba5df	2011-10-24T23:18:34	tests: fix spurious failures due to missing 'yywrap()' function The AC_PROG_LEX Autoconf macro does not diagnose a failure to find the "lex library" expected to provide a `yywrap' function (function which is required to link most lex-generated programs). On the contrary, when all the link attempts (i.e., with `-ll' and `-lfl') fail, configure declares that no lex library is needed, and simply proceeds with the configuration process -- only for the build to possibly fail later, at make time. This behaviour is intended; the Autoconf manual reads: ``You are encouraged to use Flex in your sources, since it is both more pleasant to use than plain Lex and the C source it produces is portable. In order to ensure portability, however, you must either provide a function `yywrap' or, if you don't use it (e.g., your scanner has no `#include'-like feature), simply include a `%noyywrap' statement in the scanner's source.'' This AC_PROG_LEX behaviour is causing some spurious failures of the Automake testsuite in environments which lack a proper library providing `yywrap' (this happens for example on Fedora-based systems). The proper workaround is to simply provide a fall-back implementation of `yywrap' in our lexers. * tests/cond35.test: Provide a dummy `yywrap' function. * tests/lex3.test: Likewise. * tests/silent-lex-generic.test: Likewise. * tests/silent-lex-gcc.test: Likewise. * tests/silent-many-generic.test: Likewise. * tests/silent-many-gcc.test: Likewise. Reported by Jim Meyering: <http://lists.gnu.org/archive/html/automake-patches/2011-10/msg00092.html> Cherry-picked (with some edits) from commits `v1.11-1085-gb5c3968' (master) and `v1.11-871-geb147a1' (testsuite-work).
a7983a0f	2011-11-26T14:54:00	tests: fix 'distcheck-override-infodir.test' on Cygwin * tests/distcheck-override-infodir.test (Makefile.am): Do not add any `/' between $(DESTDIR) and the following paths. Otherwise, when $(DESTDIR) is empty, the recipes will try to access files with a leading double slash, which have an implementation-defined interpretation (e.g., for Cygwin, they mean UNC paths).
39a0fd02	2011-11-24T12:14:49	cosmetics: typofix in comments * tests/remake-am-pr10111.test (Makefile.am): Fix typo in comments. * THANKS: Update. Reported by Krzysztof Żelechowski.
6bceecd1	2011-10-20T11:55:01	coverage: undistributed '.am' and '.m4' files are diagnosed The stub rules emitted to work around the "deleted header problem" for `.m4' files (included by autoconf in e.g., configure.ac) and for `.am' files (included by automake in e.g., Makefile.am) should not prevent "make" from correctly complaining when such a required file is missing from a distribution tarball. * tests/dist-missing-am.test: New test. * tests/dist-missing-m4.test: Likewise. * tests/dist-missing-included-m4.test: Likewise. * tests/Makefile.am (TESTS): Add them. Suggestion by Ralf Wildenhues.
237b9320	2011-10-16T17:07:19	coverage: required but missing '.am' and '.m4' files are diagnosed The stub rules emitted to work around the "deleted header problem" for `.m4' files (included by autoconf in e.g., configure.ac) and for `.am' files (included by automake in e.g., Makefile.am) should not prevent the remake rules from correctly erroring out when a still-required file is missing. * tests/deleted-am.test: New test. * tests/deleted-m4.test: Likewise. * tests/Makefile.am (TESTS): Add them.
83374141	2011-11-22T20:50:53	coverage: expose automake bug#10111 in the testsuite * tests/remake-am-pr10111.test: New test, xfailing. * tests/remake-m4-pr10111.test: Likewise. * tests/Makefile.am (TESTS, XFAIL_TESTS): Add them.
eaa53725	2011-11-13T10:25:43	tests: fix spurious failure with older install-info * tests/install-info-dir.test (foo.texi): Also add proper `@settitle', `@dircategory' and `@direntry' directive, otherwise older versions of `install-info' (e.g., 4.8) will fail to create the `dir' index file in ${infodir}. Problem revealed by a failure on NetBSD 5.1.
75ae56f0	2011-11-12T22:24:36	maintcheck: fix spurious failure in 'color2.test' * tests/color2.test: Avoid creative quoting to avoid a spurious failure of the `sc_tests_Exit_not_exit' maintainer check.
eae36caf	2011-11-12T18:41:53	tests: fix spurious error in 'uninstall-fail.test' on Solaris * tests/uninstall-fail.test: Solaris 10 /usr/xpg4/bin/sh can add a line number before the `:' in the error messages issued by shell builtins. Account for that in our grepping of make output.
77d7a6f7	2011-11-12T18:25:38	tests: fix typo in 'uninstall-fail.test' * tests/uninstall-fail.test: Always use `$rm_f_is_silent_on_error' instead of the bogus `$rm_f_is_silent_on_failure'.
18f250e8	2011-11-10T12:43:54	tests: avoid a spurious failure of 'ltinit.test' MinGW * tests/ltinit.test: Be laxer in grepping configure output, to avoid spurious failures on systems which lack POSIX dynamic linking (e.g., MinGW), or when cross-compiling for such systems. See also commit `v1.11-855-ge9e5d4a'. Report and suggestion from Peter Rosin.
c6151471	2011-11-08T19:50:29	tests: testsuite is now safe to run with dmake in parallel mode * tests/defs.in: Unset variables DMAKE_CHILD, DMAKE_DEF_PRINTED and DMAKE_MAX_JOBS, which are exported by Solaris dmake when run in parallel mode, and which might confuse make processes spawned by our testsuite.
d9ea65c0	2011-11-08T18:41:30	tests: fix spurious failures w.r.t. parallel make and colorization * tests/color2.test: Skip the test if the $MAKE program fails to consider the standard output as a tty when spawned by `expect'. This is required for make implementations, like FreeBSD make and Solaris dmake, that redirect the output of recipes to temporary files or pipes when run in parallel mode. Since we are at it, simplify the detection of a working `expect' program, and throw in other minor simplifications.
549f3844	2011-11-07T16:07:25	Merge branch 'fix-pr9579' into maint * fix-pr9579: tests: fix spurious failure in 'distcheck-override-infodir.test'
00eb9d62	2011-11-07T16:05:48	tests: fix spurious failure in 'distcheck-override-infodir.test' * tests/distcheck-override-infodir.test ($required): Add 'install-info'.
f6195336	2011-11-07T15:59:43	tests: avoid another failure of 'uninstall-fail.test' on Solaris * tests/uninstall-fail.test: On Solaris 10, if `/bin/rm' is run with the `-f' option, it doesn't print any error message when failing to remove a file (due to e.g., "Permission denied"). Yikes. Cater to this incompatibility, by relaxing the test when a faulty `rm' is detected.
1ba50d12	2011-11-03T11:28:56	Merge branch 'fix-pr9890' into maint * fix-pr9890: maint-mode: fix botched configure messages
a45c6364	2011-10-29T12:15:59	maint-mode: fix botched configure messages This change fixes automake bug#9890. * m4/maintainer.m4 (AM_MAINTAINER_MODE): Fix the "checking ..." configure message related to the enabling/disabling of maintainer mode. * tests/help-maintainer.test: Renamed ... * tests/maintmode-configure-msg.test: ... to this, and extended to cover the fixed bug. Also, since we are at it, make grepping of configure help screens stricter, and throw in some few other changes to reduce code duplication and enhance readability. * tests/Makefile.am (TESTS): Update. * THANKS: Update with Zack's new e-mail address. Report and initial patch by Zack Weinberg, test cases added by Stefano Lattarini.
182935ac	2011-10-29T12:22:50	Merge branch 'fix-pr9773' into maint * fix-pr9773: info: allow user to inhibit creation/update of '${infodir}/dir'
cb9f2c28	2011-10-24T19:45:42	Merge branch 'fix-pr8485-and-pr8526' into maint * fix-pr8485-and-pr8526: deps: partially revert commit `v1.11-512-geeee551'
1ec16686	2011-10-23T13:19:21	info: allow user to inhibit creation/update of '${infodir}/dir' With this change, we allow the user to request the install-info rules not to update the `${infodir}/dir' file, by exporting the environment variable `AM_UPDATE_INFO_DIR' to the value "no". This is especially useful to distro packagers, and is a definite improvement over our previous hack of looking whether the `install-info' program was the Debian or GNU version -- hack which had been silently broken with recent versions of debian install-info BTW (probably since dpkg 1.15.4, 2009-09-06). This change fixes automake bug#9773. See also Debian Bug#543992. * lib/am/texinfos.am: Don't look anymore at the output of `install-info --version' to decide whether to use it to update the `${infodir}/dir' or not; instead, honour the environment variable `AM_UPDATE_INFO_DIR'. * tests/install-info-dir.test: New test. * tests/Makefile.am (TESTS): Add it. * tests/defs: Also unset `AM_UPDATE_INFO_DIR', to avoid unwanted interferences from the environment. * doc/automake.texi (Texinfo): Update. * NEWS: Likewise. * THANKS: Likewise. Report by Jonathan Nieder.
9b5ced02	2011-10-22T20:51:43	Merge branch 'dejagnu-siteexp-extend' into maint * dejagnu-siteexp-extend: dejagnu: allow the package developer to extend site.exp
beef7a66	2011-02-01T09:52:43	dejagnu: allow the package developer to extend site.exp Fixes automake bug#7873. * lib/am/dejagnu.am (site.exp): Depend from the files listed in $(EXTRA_DEJAGNU_SITE_CONFIG), if any. Append their contents to the generated site.exp (still preserving user edits). * doc/automake.texi (Dejagnu Tests): Update. * tests/dejagnu-siteexp-append.test: New test. * tests/dejagnu-siteexp-extend.test: Likewise. * tests/dejagnu-siteexp-useredit.test: Likewise.ù * NEWS: Update. * tests/Makefile.am (TESTS): Update. Suggestion by Rainer Orth.
6a2fe818	2011-10-22T20:42:17	Merge branch 'dejagnu-srcdir-discrepancy' into maint * dejagnu-srcdir-discrepancy: dejagnu: ensure 'srcdir' is defined as a relative directory Fix testsuite failure of check12.test without DejaGNU. Extend and improve tests on DejaGnu support.
40c34328	2011-10-20T22:25:45	deps: partially revert commit `v1.11-512-geeee551' This change partly reverts commit "Create subdirs for generated sources even when not dep tracking", of 2011-04-02. That commit had caused the bugs #8485 and #8526. Since we are nearing the bug-fixing automake release 1.11.2, the safest policy at the moment is to just revert the problematic hunks: an older, known bug is better than a regression. * automake.in (handle_single_transform): Don't add a dirstamp dependency, even when $object is derived and lands in a subdir. * tests/Makefile.am (XFAIL_TESTS): Add lex-subobj-nodep.test, remove yacc-dist-nobuild-subdir.test.
d2b90968	2011-10-20T21:44:23	Merge branch 'test-subpkg-fix-spurious-freebsd-fail' into maint * test-subpkg-fix-spurious-freebsd-fail: tests: fix spurious failure with FreeBSD make and Yacc in VPATH
7cb64d4f	2011-10-20T21:38:52	Merge branch 'fix-pr8788' into maint * fix-pr8788: tests: avoid spurious failure in 'parallel-tests3.test'
65c01584	2011-10-20T21:31:09	tests: fix spurious failures with "chatty" make implementations * tests/distcheck-missing-m4.test: On failure, some make implementations (such as Solaris make) print the whole failed recipe on standard output. This was causing a spurious failure in the checks grepping the output from make. Work around this. * tests/distcheck-outdated-m4.test: Likewise.
100e9740	2011-10-20T17:45:12	Merge branch 'aclocal-path' into maint * aclocal-path: tests: fix spurious failure on fast machines
f8f8ec0e	2011-10-20T17:44:04	tests: fix spurious failure on fast machines * tests/aclocal-path-precedence.test: Also remove the `configure' script between different test runs, to ensure it is always remade by autoconf. Add proper explicative comments.
d91f357d	2011-10-20T17:31:11	tests: avoid spurious failure of 'uninstall-fail.test' on Solaris * tests/uninstall-fail.test: All the Solaris 10 shells (/bin/sh, /bin/ksh, and /usr/xpg4/bin/sh), upon failing to chdir to a directory with the `cd' builtin, print a message like: "sh: /root: permission denied" which doesn't report the `cd' builtin anywhere. Relax the grepping of the error message accordingly.
7a770586	2011-10-19T13:43:46	Merge branch 'fix-pr9578' into maint * fix-pr9578: tests: avoid spurious failure of 'uninstall-fail.test' on Cygwin
8c021e00	2011-10-19T13:42:40	tests: avoid spurious failure of 'uninstall-fail.test' on Cygwin * tests/uninstall-fail.test: Be sure to really skip this test on systems that allows files to be removed from unwritable directories. Motivated by a spurious failure on Cygwin 1.5.
ded01c88	2011-01-13T20:33:26	dejagnu: ensure 'srcdir' is defined as a relative directory This change fixes automake bug#7833. * lib/am/dejagnu.am (check-DEJAGNU): Prefer using plain $(srcdir) over calculating and using the absolute path of $(srcdir). * tests/dejagnu-relative-srcdir.test: New test. * tests/dejagnu-absolute-builddir.test: Likewise. * tests/Makefile.am (TESTS): Update. Report by Ian Lance Taylor. Suggestions by Ralf Wildenhues.
f5b69b8a	2011-10-18T21:05:24	tests: avoid spurious failure in 'parallel-tests3.test' This fixes automake bug#8788. * tests/parallel-tests3.test: To ensure that the serial run of the dummy testsuite is still ongoing when the parallel run has terminated, use `kill -0', not a bare `kill'. This will prevent a testsuite crash on NetBSD 5.1, and a testsuite hang on FreeBSD 8.2. Also, since we are at it, try harder to avoid possible hangs of the script in other unusual situations.
7e5ae808	2011-10-18T17:53:21	tests: fix spurious failure with FreeBSD make and Yacc in VPATH * tests/subpkg.test: Some cosmetic adjustments. Move the tests checking that $(YLWRAP) is defined and installed properly when ylwrap is in a default auxdir found in a parent package ... * tests/subpkg-yacc.test: ... into this new test, which carefully avoids to trigger the known bug#7884 (combo FreeBSD make plus Yacc plus VPATH build). * tests/Makefile.am (TESTS): Update.
94ad7e48	2011-10-17T17:46:05	Merge branch 'aclocal-path' into maint
02ab80ce	2011-10-17T17:45:41	tests: fix spurious failure with autoconf 2.62 * tests/aclocal-path-precedence.test: Rewrite configure.in, rather than appending to it, to avoid spurious failures (at least with autoconf 2.62) due to repeated calls to AC_INIT. Also, add package name and version arguments to AC_INIT, to avoid spurious errors from automake.
ba0c477b	2011-10-07T11:08:15	parallel-tests: warn on conditional TEST_EXTENSIONS definition Before this change, automake would have still bailed out, but with a confusing error message (about an invalid redefinition of TEST_EXTENSIONS). * automake.in (handle_tests): Warn explicitly if TEST_EXTENSIONS has conditional contents. * tests/test-extensions-con.test: New test. * tests/Makefile.am (TESTS): Add it. * NEWS: Update.

fbeda3da

2012-01-18T12:17:11

tests: move all under the same hierarchy ('tests/' directory) This simplifies the organization of the Automake source tree and reduces the (lamentably high) number of Makefiles in the Automake build system by one. It also makes the maintainer check that verifies the consistency of list of tests more self-contained and simpler. Finally, it might be a first step forward the transition to a non-recursive build system for automake (if we ever decide to go down that road fully some day). * lib/Automake/tests: All the '*.pl' tests in here moved ... * tests/pm: ... into this new directory. * lib/Automake/tests/Makefile.am: Remove, its meaningful contents moved ... * tests/Makefile.am: ... here, with obvious adjustments. (test_subdirs): New variable, for the sake of the recipe of 'maintainer-check-list-of-tests'. * CheckListOfTests (maintainer-check-list-of-tests): Enhance its recipe to make it able to deal with test script residing in subdirectories. * Makefile.am (maintainer-check-list-of-tests): Simplified. (TEST_SUBDIRS): Remove, no more needed. * tests/list-of-tests.mk (perl_TESTS): New variable, lists the '.pl' tests just moved into 'tests/pm'. (handwritten_TESTS): Add the contents of '$(perl_TESTS)'. * lib/Automake/Makefile.am (SUBDIRS): Remove. * configure.ac (AC_CONFIG_FILES): Update. * .gitignore: Adjust.

3d6197fe

2012-01-16T18:35:50

Merge branch 'check-html-deprecate' into maint * check-html-deprecate: recheck: fix interaction with "make -n" recheck: behave better with non-GNU make check: separate .log -> .html conversion from core testsuite harness docs: deprecate .log -> .html conversion by parallel-tests

8fec2399

2012-01-13T22:39:47

recheck: fix interaction with "make -n" * lib/am/check.am (recheck): Ensure the recipe does not erroneously remove '.log' files when running under "make -n". For the sake of NetBSD make, this also means that ... (.MAKE): ... this cannot depend on 'recheck' anymore. * tests/parallel-tests-dryrun.test: New test. * tests/list-of-tests.mk: Add it.

3da9c4c7

2012-01-16T15:38:56

vala: enhance tests * tests/vala.test: Extend test. Throw in some cosmetic and consistency changes since we are at it. * tests/vala5.test: Avoid uselessly requiring libtool. Ensure a failure happens in case VALAFLAGS are not supported as expected. Extend test in some ways. Throw in some cosmetic and consistency changes since we are at it. * tests/vala-mix.test: New test. * tests/list-of-tests.mk: Add it.

d9a7182e

2012-01-13T18:53:43

recheck: behave better with non-GNU make * automake.in (handle_tests): Also substitute '%CHECK_DEPS%' with the value of the '@check' array, containing the list of early test dependencies like '$(check_SCRIPTS)', $(check_PROGRAMS)', etc. * lib/am/check.am (recheck): Explicitly depend on '%CHECK_DEPS%'. (check, recheck): Unify the implementation of their recipes, with different code paths taken depending on the name of the target. This makes the implementation of "recheck" less brittle in the process (especially when non-GNU make and AM_MAKEFLAGS overriding are involved). * lib/am/check-html.am (check-html, recheck-html): Likewise. * tests/check.test: Adjust to avoid spurious failure. * tests/parallel-tests2.test: Improve coverage.

20f2ac90

2012-01-13T17:56:13

check: separate .log -> .html conversion from core testsuite harness That feature is to be deprecated in the 1.11.x series, and removed from the automake core in the 1.12 release, where it will instead be offered in a semi-independent extra '*.am' fragment. So let's start better separating the .log -> .html conversion from the "core code" of the parallel-tests harness. Reference: <http://lists.gnu.org/archive/html/automake/2012-01/msg00005.html> * lib/am/check.am (.log.html, check-html, recheck-html): Move these targets ... * automake.in (handle_tests): ... and the initialization of the TEST_SUITE_HTML variable and the cleaning of the $(TEST_SUITE_HTML) file ... * lib/am/check-html.am: ... in this new file, with related (minor) refactorings, enhancements and simplifications. * lib/am/check.am (.MAKE. PHONY, AM_RECURSIVE_TARGETS): Adjust. * lib/am/Makefile.am (dist_am_DATA): Add 'check-html.am'. * tests/parallel-tests2.test: Improve coverage.

068b2f53

2012-01-16T10:18:06

tests: list some forgotten test cases in $(TESTS) This way, they will be properly executed by "make check", and properly distributed. Our previous commit 'v1.11-647-g27f1a1c' is already paying its dividends! * tests/list-of-tests.mk (handwritten_TESTS): Add check12.test, dist-missing-included-m4.test, dist-missing-am.test, and dist-missing-m4.test.

27f1a1c9

2012-01-16T10:05:59

maintcheck: consistency of list of test scripts This is basically a backport of commit 'v1.11-358-g7b6ab07' and its follow-ups. The possibility of easily checking that the list of test scripts listed in a Makefile equals that of the tests on the filesystem has proved itself so useful that it's worth taking the annoyance of backporting it to maint. * CheckListOfTests.am: New file, backported from master (commit 'v1.11-1736-g083a75b') with minor adjustments. (maintainer-check-list-of-tests): New target, check for consistency between the list of tests defined in the including Makefile and the list of tests on the filesystem. (clean-maintcheck-testslist-tmp): New rule, to clean up temporary files that might be left around by the rules associated with the previous target. (clean-local): Depend on it. * lib/Automake/tests/Makefile.am: Include `CheckListOfTests.am'. * tests/Makefile.am: Likewise. * Makefile.am (maintainer-check-list-of-test): New target, calling recursively into `tests/' and `lib/Automake/tests/', using ... (TEST_SUBDIRS): ... this new variable. (maintainer-check): Added dependency from the new target `maintainer-check-list-of-tests'.

9d9f00ed

2012-01-15T21:07:44

tests: move list of tests in its own Makefile fragment This change will make it easier to merge maint into master, which has a similar Makefile setup in the testsuite. * tests/Makefile.am (include): Inclusion of ... * tests/list-of-tests.mk: ... this new file. * tests/Makefile.am (TESTS): Move most of its content into, and redefine in function of, ... * tests/list-of-tests.mk (handwritten_TESTS): ... this new variable. * tests/gen-parallel-tests: Update.

17542c3c

2012-01-15T20:46:43

build: silence automake build system * configure.ac (AM_SILENT_RULES): Invoke with "yes" as a parameter, to activate silent rules by default. * NEWS: Update. * Makefile.am (sc_perl_syntax): Silence its recipe unconditionally, similarly to what is done for other syntax checks. (release-stats): Be silent by default *but not unconditionally*, thanks to the use of $(AM_V_GEN). (path-check, git-diff): Be silent by default, thanks to the use of $(AM_V_GEN). * m4/Makefile.am ($(top_srcdir)/m4/amversion.m4): Likewise. * doc/Makefile.am ($(srcdir)/amhello-1.0.tar.gz): Likewise. * tests/Makefile.am ($(srcdir)/parallel-tests.am): Likewise. ($(parallel_tests)): Likewise.

59367c05

2012-01-14T10:32:13

test defs: backport optimized 'using_gmake' implementation * tests/defs.in (using_gmake): Backport optimized, result-caching implementation from master.

0188e0f5

2012-01-13T21:56:54

tests: unify some tests on "make -n", reducing duplication * tests/maken2.test: Merge into ... * tests/maken.test: ... this test, to avoid unnecessary code duplication. Make checks depending on GNU make conditional to the actual presence of GNU make. * tests/maken4.test: Similarly, merge into ... * tests/maken3.test: ... this test. * tests/Makefile.am (TESTS): Remove maken2.test and maken4.test.

539cae3b

2012-01-13T12:42:36

Merge branch 'fix-pr10470' into maint * fix-pr10470: dist: avoid $(distdir) removal failure on MSYS/MinGW coverage: expose automake bug#10470 (distcheck-related)

dfb5e52f

2012-01-11T18:09:07

dist: avoid $(distdir) removal failure on MSYS/MinGW This change fixes automake bug#10470. On MSYS (1.0.17) it is not possible to remove a directory that is in use, and this, together with timing issues, could cause spurious failures in the cleanup code of the "distcheck" recipe. In fact, it should be noted that assuming a directory can be removed while it the CWD of a running process is a POSIX violation: "If the directory is the root directory or the current working directory of any process, it is unspecified whether the function succeeds, or whether it shall fail and set errno to [EBUSY]." * lib/am/distdir.am (am__remove_distdir): If rm fails, sleep some seconds and retry, to give potential "pending" processes some time to exit and "release" the directory. * tests/Makefile.am (XFAIL_TESTS): Remove 'distcheck-pr10470.test'. Report and suggestions by Peter Rosin and Eric Blake.

f1df5481

2012-01-01T19:06:00

tests: fix spurious failure of 'get-sysconf.test' * tests/get-sysconf.test: Do not assume that a ChangeLog file exists in $(srcdir): now that the ChangeLog is autogenerated and not under version control anymore, this is not necessary true. Instead, if we are running from a git checkout, use "git log" to get information on the version of the automake snapshot being tested (and fall back on extracting the first ChangeLog entry otherwise). Reported by Jim Meyering in automake bug#10418. Cherry picked from commit v1.11-1675-g104f302.

657eed2e

2012-01-12T10:06:14

coverage: expose automake bug#10470 (distcheck-related) * tests/distcheck-pr10470.test: New test. * tests/Makefile.am (TESTS, XFAIL_TESTS): Add it. Report and suggestions by Peter Rosin and Eric Blake.

e064ff79

2012-01-12T09:41:06

tests: make 'aclocal-install-absdir.test' executable * tests/aclocal-install-absdir.test: Make it executable.

d850165e

2012-01-08T12:49:57

tests: require GNU make in 'vala-vapth.test' * vala-vpath.test ($required): Add the "GNUmake" requirement, since rules generated by vala support are expected to work with GNU make only.

72f7e5de

2012-01-07T01:08:11

vala: fix VPATH builds This change fixes automake bug#9859. * automake.in (lang_vala_finish_target): Create the stamp file '${derived}_vala.stamp' in $(srcdir), not in $(builddir). Also, don't try to chdir to the $(srcdir) to trigger the rebuild rules, since that is just wrong in a VPATH setup. * tests/vala-vpath.test, tests/vala2.test: Extend to catch more possible VPATH issues. * tests/Makefile.am (XFAIL_TESTS): Remove 'vala-vpath.test'. * NEWS, THANKS: Update. Co-authored-by: Stefano Lattarini <stefano.lattarini@gmail.com> Copyright-paperwork-exempt: yes

c7ee8c6d

2012-01-07T01:06:37

tests: fix some bugs in the vala-vpath test * tests/vala-vpath.test: There are (trivial) problems in this testcase that would cause the build to fail even if the core issue were resolved. Fix those. Copyright-paperwork-exempt: yes

01c3294b

2012-01-03T16:12:46

dist: do not wrap calls to 'tar' with the 'missing' script The `missing' script is meant to allow non-developers to build a package in the face of slightly-skewed timestamps (as might happen e.g. when the package is obtained from a VCS checkout rather than from a distribution tarball). It is *not* the business of the `missing' script to try to provide wrappers for all the maintainer tools (in this case, to tool being a decent tar program). Such wrapping of `tar' was not only inappropriate, but it was also preventing the legitimate overriding (at make runtime) of the `tar' program used in the creation of the distribution tarballs. See also automake bug#9822. * lib/missing: Don't try to specially wrap `tar' invocations anymore. * m4/tar.m4 (_AM_PROG_TAR): In the definitions of the `AMTAR' variable, do not wrap the `tar' invocation with the `missing' script anymore. Instead, allow the user to override the intended tar program at make runtime, by defining the `TAR' environment variable. [$1 == v7]: Similarly for the definitions of the `am__tar' and `am__untar' variables. Since we are at it, don't make them depend anymore on the definition of the obsolescent `AMTAR' variable. * NEWS: Update. * tests/missing-tar.test: Remove, it's obsolete. * tests/tar-override.test: New test. * tests/Makefile.am (TESTS): Update. Reported by Akim Demaille.

741a0a1e

2012-01-06T14:51:55

fixup: previous commit v1.11-627-g1e0aedc * tests/acloca18.test: Do not remove an aclocal.m4 file that is needed by a later autoconf invocation.

92f688d8

2012-01-06T13:15:17

tests: fix spurious failures due to autom4te caching * tests/aclocal9.test: Call aclocal and autoconf with the `--force' option. * tests/acloca10.test: Sleep between re-runs of aclocal and autoconf. * tests/acloca18.test: Explicitly remove also the configure script and the aclocal.m4 before re-invoking aclocal and autoconf.

4e4dae50

2012-01-03T09:06:09

install: pkglibexec_SCRIPTS is a valid prefix/primary combination It makes little sense for `libexec_SCRIPTS' to be accepted as valid while `pkglibexec_SCRIPTS' is not. So fix this inconsistency by explicitly allowing `pkglibexec_SCRIPTS' as well. It is worth noting that the inconsistency has been there for a long time, but only the quite recent commit `v1.11-373-g9ca6326' "Warnings about primary/prefix mismatch fixed and extended" has made it noisy enough to be noticed. * automake.in (handle_scripts): Also list `pkglibexec' among the prefixes valid for the `SCRIPTS' primary. * doc/automake.texi (Scripts): Likewise. * tests/primary-prefix-valid-couples.test: Update. * THANKS: Likewise. * NEWS: Likewise. Reported by Dennis Schridde on the automake list: <http://lists.gnu.org/archive/html/automake/2012-01/msg00002.html>

971000c1

2012-01-02T20:32:54

coverage: expose automake bug#10128 * tests/objext-pr10128.test: New test, still expected to fail. * tests/Makefile.am (TESTS, XFAIL_TESTS): Add it.

f4e221b6

2012-01-02T09:40:13

progs, libs: implement EXTRA_foo_DEPENDENCIES Backported from commit `v1.11-377-g6edafbb'. The feature implemented by that change is quite unobtrusive, so adding it to a maintenance release is acceptable. Also, there have been requests from real-world users for this feature since it has been implemented in master; see automake bug#9320: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9320> and this short discussion on the automake list: <http://lists.gnu.org/archive/html/automake/2010-11/msg00099.html> It would be a pity to make such users wait even more (until Automake 1.12 is out) before they could start using this feature. Thus we backport it, so that it will appear in the next maintenance version of automake (1.11.3). * automake.in (handle_programs, handle_libraries) (handle_ltlibraries): Mark EXTRA_*_DEPENDENCIES as recognized. * doc/automake.texi (Linking, Program and Library Variables) (LIBOBJS): Document EXTRA_*_DEPENDENCIES. * lib/am/library.am (%LIBRARY%): Also depend on $(EXTRA_%XLIBRARY%_DEPENDENCIES). * lib/am/ltlibrary.am (%LTLIBRARY%): Also depend on (%XLTLIBRARY%_DEPENDENCIES). * lib/am/program.am (%PROGRAM%%EXEEXT%): Also depend on $(EXTRA_%XPROGRAM%_DEPENDENCIES). * tests/extradep.test, tests/extradep2.test: New tests. * tests/Makefile.am (TESTS): Update. * NEWS: Update.

4337813b

2012-01-03T13:56:17

tests: fix spurious failures in 'pr300*.test' This change fixes automake bug#10426. * tests/pr300-lib.test: Call configure with an explicit '--libdir' option, to avoid spurious failures due to users possibly overriding '${libdir}' in ther config.site files. * tests/pr300-ltlib.test: Likewise. Reported by Bruno Haible.

28040759

2012-01-01T10:42:34

tests: make 'lzip.test' executable * tests/lzip.test: Make it executable.

2a461709

2012-01-01T10:39:10

Merge branch 'deprecate-lzma' into maint * deprecate-lzma: dist: obsolete support for lzma (superseded by xz and lzip)

e637fa2a

2011-12-30T15:54:40

dist: obsolete support for lzma (superseded by xz and lzip) The lzma utilities are today superseded by the xz utilities; in fact, the official site at <http://tukaani.org/lzma/> reads: ``LZMA Utils are legacy data compression software with high compression ratio. LZMA Utils are no longer developed, ... Users of LZMA Utils should move to XZ Utils.'' and the existing automake manual (as of 1.11.2) already says: ``dist-xz Generate an 'xz' tar archive of the distribution. xz archives are frequently smaller than bzip2-compressed archives. The 'xz' format will soon (early 2009) displace the 'lzma' format'' Also, the `dist-lzma' target still suffers of never-solved bugs, due to the too-high compression ratio its uses by default, which might cause an unacceptable memory consumption when one tries to compress or, worse, decompress the created tarballs; see also: <http://lists.gnu.org/archive/html/automake/2011-12/msg00025.html> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9658> * NEWS: Update. * doc/automake.texi (Dist, Options): State that `dist-lzma' will go away in the next major automake version. * lib/Automake/Options.pm (_process_option_list): Deprecate `dist-lzma'. * tests/lzma.test: Update.

bbce9c2b

2011-12-31T08:47:34

Merge branch 'dist-lzip' into maint * dist-lzip: dist: add support for lzip compression

bff8ceca

2011-12-30T19:22:55

test defs: more granular overriding of the make program Before this change, the only way the user could override the make program used in the automake test cases was to override the $MAKE variable in the environment. This had the annoying side effect of requiring that, whenever a non-default make program was to be used in the test cases, that same make program had to be used to drive the execution of the automake testsuite; otherwise, the recursive make invocations could pick up $MAKE from the environment, and use that instead of re-executing with the correct make. So, for example, if one wanted to try how Solaris /usr/ccs/bin/make behaved in the automake test cases, he couldn't run the testsuite in parallel mode, because that make lacks support for concurrent execution of recipes; on fast machines, this easily meant a 4x or higher slow-down. Once the problem is clear, the solution is pretty simple: allow the use of another variable, besides $MAKE, to override the make program to be used in the test cases. See also commit `v1.11-1318-g3ceeef4', that introduced a more general version of this change to the master branch. * tests/defs.in: Allow the make implementation to be used by the test cases to be overridden by the `$AM_TESTSUITE_MAKE' variable, in preference to the `$MAKE' variable.

0878bd34

2011-12-30T14:35:18

dist: add support for lzip compression * NEWS: Update. * automake.in (handle_dist): Recognize dist-lzip. (make_paragraphs): Map LZIP to dist-lzip. * doc/automake.texi (Dist, Options): Describe dist-lzip. * lib/Automake/Options.pm (_process_option_list): Recognize `dist-lzip'. * lib/am/distdir.am (dist-lzip): New target. (DIST_ARCHIVES) [?LZIP?]: Add `dist-lzip'. (dist, dist-all) [?LZIP?]: Add command to create an lzip-compressed tarball. (distcheck): Handle lzip-compressed tarballs just like the others. * tests/lzip.test: New test. * tests/Makefile.am (TESTS): Add it.

cec3f327

2011-12-30T13:47:57

Merge remote-tracking branch 'silent-fixes' into maint * origin/silent-fixes: fix: last entry in ChangeLog tests: tweak tests on silent-rules for makes without nested vars silent-rules: fallback for makes without nested vars

34749105

2011-12-28T15:15:50

tests: fix spurious failure due to autom4te caching * tests/acloca18.test: Remove stale autom4te.cache directories, to prevent racy, spurious failures. * tests/python11.test: Likewise. Fix a typo in comments since we are at it.

c87ceb55

2011-12-28T10:54:47

Merge branch 'maint' into silent-fixes * maint: maint: autogenerate ChangeLog fix: last ChangeLog entry tests: drop unnecessary requirement in 'subpkg.test' gitlog-to-changelog: new auxiliary script, synced from gnulib docs: "aclocal --install -I /abs/dir" actually copies files docs: fix node names for automake and aclocal invocations

77b2c71c

2011-12-27T19:31:03

tests: drop unnecessary requirement in 'subpkg.test' * tests/subpkg.test ($required): Drop "bison", it is not required anymore since commit `v1.11-502-g7e5ae80'.

44da9cbd

2011-12-27T14:55:41

docs: "aclocal --install -I /abs/dir" actually copies files This change is for automake bug#8407. In the past, there had been some debate and confusion about whether "aclocal --install" should copy third-party .m4 files in the first directory passed to the `-I' option even when such directory was given as an absolute path, or whether it was better to do so only for directories specified with a relative path. The rationale for this latter behaviour was that, before the existence of the `ACLOCAL_PATH' variable, the only way (a poor way, I might add) for a common user to extend the search path of a system-wide installation of aclocal was to export something like ACLOCAL="aclocal -I /my/extra/macros" in the environment. Today, the correct way to proceed is undoubtedly through the use of ACLOCAL_PATH, so we can settle the question once and for all, and start verifying the correct behaviour of `-I' with a new test. * tests/aclocal-install-absdir.test: New test. * tests/Makefile.am (TESTS): Add it. * doc/automake.texi (aclocal Options): Be more explicit about this part of `--install' semantics.

0eaa8781

2011-12-26T18:23:24

tests: tweak tests on silent-rules for makes without nested vars * tests/silent-nested-vars.test: Define $MAKE to `./mymake' in the environment, so that it will be automatically picked up by configure. Related tweaks and simplifications. Remove the checks verifying that silent rules are respected also when the 'subdir-objects' option is set, the checks testing the old syntax for user-defined silent rules, and the tests using the default $MAKE programs: they are redundant w.r.t. other test cases. Related simplifications. Remove the temporary files used in a sanity check as soon as they are not needed anymore. Do not capture also the standard error of configure: we only want to grep its standard output. Consistently use `stdout' for the name of files where to save the standard output captured from make and configure, for consistency with other tests. Make grepping of configure output and of the generated Makefile stricter. Improve and tweak the `mymake' script a little. * tests/silent6.test: Make grepping of make stdout slightly stricter. After having configured with silent rules disabled, try to force the use silent rules with `make V=1'.

8493499b

2011-12-25T09:56:44

silent-rules: fallback for makes without nested vars This fixes two problems reported for Automake (Bug#9928, Bug#10237) and is in response to a bug report for building coreutils on HP NonStop OS (Bug#10234). The problem is that HP NonStop 'make' treats a line like "AM_V_CC = $(am__v_CC_$(V))" as one that expands a macro with the funny name am__v_CC_$(V instead of the desired name am__v_CC_1 or am__v_CC_0, and since the funny macro is not defined the line is equivalent to "AM_V_CC = )"; this inserts a stray ")" when $(AM_V_CC) is used, which eventually causes 'make' to fail. The basic idea is that instead of generating Makefile.in lines like "AM_V_CC = $(am__v_CC_$(V))", we generate "AM_V_CC = $(am__v_CC_@AM_V@)". We then AC_SUBST $(V) for @AM_V@ in the usual case where `make' supports nested variables, and substitute 1 (or 0) otherwise. Similarly for usages like $(am__v_CC_$(AM_DEFAULT_VERBOSITY)). With this change, make implementations that doesn't grasp nested variable expansions will still be able to run Makefiles generated using the silent-rules option. They won't allow the user to override the make verbosity at runtime through redefinition of $(V) (as in "make V=0"); but this is still an improvement over not being able to work at all. * NEWS: Document this. * automake.in (define_verbose_var): When defining the variables, use @AM_V@ rather than $(V), and use @AM_DEFAULT_V@ rather than $(AM_DEFAULT_VERBOSITY). * doc/automake.texi (Automake silent-rules Option): Explain new system. * m4/silent.m4 (AM_SILENT_RULES): Check whether `make' supports nested variables, and substitute AM_V and AM_DEFAULT_V accordingly. * tests/silent-nested-vars.test: New test. * tests/Makefile.am (TESTS): Add it.

bfc83bde

2011-12-24T10:43:26

gitignore: use only one .gitignore file, in the top-level directory * doc/.gitignore, doc/amhello/.gitignore, lib/Automake/.gitignore, lib/Automake/tests/.gitignore, tests/.gitignore: Deleted, their contents merged into ... * .gitignore: ... this top-level file. Since we are at it, improve it by anchoring files where it makes sense.

eada9138

2011-12-24T09:58:17

Merge branch 'tests-gettext-macros-require' into maint * tests-gettext-macros-require: tests: one more fixlet for gettext macros requirement

e1fad75e

2011-12-24T09:56:49

tests: one more fixlet for gettext macros requirement * tests/gettext-macros.test (configure.in): Add calls to AC_INIT and AC_PROG_CC, to avoid a spurious failure in the later aclocal invocation. Luckily, this wart wasn't causing any spurious SKIP or FAIL, but only the redundant addition to the `-Wno-syntax' option to some aclocal invocations in the gettext tests.

9ea4c454

2011-12-24T09:29:15

Merge branch 'tests-gettext-macros-require' into maint * tests-gettext-macros-require: tests: fix handling of gettext macros requirement

763f3ec3

2011-12-24T09:25:00

tests: fix handling of gettext macros requirement The code introduced in the earlier change `v1.11-581-gb7d67d5' and aimed at automatically fetching all the .m4 files provided by gettext has proven inadequate, since it hasn't managed to truly and always get *all* the required .m4 files. For example, it has failed to fetch the file `intldir.m4' (present in gettext 0.18.1, and where the macro `AM_GNU_GETTEXT_INTL_SUBDIR' is defined), which in turn has caused spurious SKIPs of at least the test `gettext3.test'. The reason for this debacle is that autopoint looks at the version specified in AM_GNU_GETTEXT_VERSION to decide which version of the gettext infrastructure to bring in; since we were unconditionally specifying the older 0.10.35 version, the newer `.m4' files weren't brought in. * tests/gettext-macros.test: In AM_GNU_GETTEXT_VERSION, instead of unconditionally specifying the older 0.10.35 version, specify the version of the available `gettextize' or `autopoint' program, dynamically extracted with the help of ... (extract_program_version):... this new function, and saved ... ($autopoint_version): ... in this new variable.

007455d9

2011-12-23T13:09:50

Merge branch 'missing-fixes' into maint * missing-fixes: tests: fix failure due to debugging code forgotten into a test

03f51958

2011-12-23T12:47:19

tests: fix failure due to debugging code forgotten into a test * tests/missing-tar.test: Don't ever call the `missing' script with `sh -x'; this was used for debugging, but an instance of it slipped into the committed test case. Bug revealed by a failure on a Solaris 10 system with GNU tar installed as `gtar'.

3c5d083e

2011-12-23T00:42:46

Merge branch 'tests-libtool-gettext-requirements' into maint * tests-libtool-gettext-requirements: tests: avoid spurious failure of libtool and gettext tests

39e4f272

2011-12-23T00:42:24

tests: avoid spurious failure of libtool and gettext tests On Solaris 10 (and presumably earlier), /bin/sh trips up on here-documents that contains a command substitution *and* are fed to a shell function: # All as expected. $ cat <<END `pwd` END /home/stefano $ echo status = $? status = 0 # An apparently innocuous function ... $ kitty () { cat; } # ... but hilarity ensues! $ kitty <<END `pwd` END /tmp/sh137723: cannot open $ echo status = $? status = 1 We need to work around this misbehaviour in a couple of our tests (whose failures where causing cascading failures in a lot of other tests). * tests/gettext-macros.test: Avoid the use of command substitution in a here-document passed to the `indent' function, by using the `echo' builtin instead. * tests/libtool-macros.test: Likewise. See also: <http://lists.gnu.org/archive/html/bug-autoconf/2011-12/msg00001.html>

5f335bed

2010-11-13T12:21:28

regex: deprecate the obsolete macro AM_WITH_REGEX This is a backport of commit v1.11-433-g37b0aee. Today, practically nobody uses the GNU rx library, which, according to its own website <http://www.gnu.org/software/rx/rx.html>, has been "decommissioned". Consequently, the automake-provided macro AM_WITH_REGEX is not used nor required anymore. Deprecate it, so that it will be possible to safely remove it in the next major automake version. * m4/regex.m4 (AM_WITH_REGEX): Give a warning of the class `obsolete' when this macro is used. * doc/automake.texi (Public Macros): Move description of `AM_WITH_REGEX' from here ... (Obsolete Macros): ... to here, and declare it as obsolete and "to be removed in a future version". * tests/regex-obsolete.test: New test. * tests/Makefile.am (TESTS): Add it. * NEWS: Update. See also: <http://lists.gnu.org/archive/html/automake-patches/2010-11/msg00131.html>

9f7864ba

2011-10-16T14:57:37

include: avoid "deleted .am file" problem * automake.in (handle_configure): When processing `configure.am', also expand `HAVE-MAKEFILE-IN-DEPS' to a boolean telling whether `MAKEFILE-IN-DEPS' is empty or not. * lib/am/configure.am [?HAVE-MAKEFILE-IN-DEPS?] (%MAKEFILE-IN-DEPS%): New target without dependencies, to avoid the "deleted .am file" problem. Emit this only when `?HAVE-MAKEFILE-IN-DEPS?' is true, to avoid generating an "empty" dependency declaration. * tests/deleted-am.test: Make grepping of error message stricter. * tests/dist-missing-am.test: Likewise. * tests/remake-deleted-am.test: New test. * tests/remake-deleted-am-2.test: Likewise. * tests/remake-deleted-am-subdir.test: Likewise. * tests/remake-renamed-am.test: Likewise. * tests/makefile-deps.test: Likewise. * tests/Makefile.am (TESTS): Add the new tests. * NEWS: Update. Fixes automake bug#9768. Report by Peter Johansson. See also commit `Release-1-10-40-gd0ebf71', which fixed a similar problem for .m4 files included by configure.ac.

b7d67d55

2011-12-14T10:35:04

tests: better handling of gettext and libtool requirements This change fixes automake bug#9807. Before this change, the automake testsuite only looked for the `.m4' files containing libtool and gettext macros definitions in the directory `${prefix}/share/aclocal' (and in the directories specified by the `dirlist' file in there, if any), where ${prefix} was the configure-time automake installation prefix (defaulting to `/usr/local'). This approach had various shortcomings and disadvantages. Let's briefly describe the three major ones. First, on most GNU/Linux systems, a libtool or gettext installed from distro-provided packages (e.g., by dpkg on Debian/Ubuntu, or by rmp on RedHat/Fedora) would have `/usr', not `/usr/local', as its ${prefix}; so, trying to run the automake testsuite with a simple "./configure && make && make check" would have failed to execute the libtool and gettext tests on most GNU/Linux distros. It's true that it was quite easy to work around this issue, by creating a proper `/usr/local/share/aclocal/dirlist' file with an entry pointing to `/usr/share/aclocal' (a workaround in fact used by most automake developers); but the typical user wasn't aware of the necessity of this trick, so the libtool and gettext tests was usually skipped on testsuite runs "in the wild", thus needlessly reducing coverage. Second, the older testsuite behaviour made more difficult for the developers to run the testsuite with non-default libtool or gettext. For example, assume the developer is working on a system that has a default libtool version 1.5 installed in the /usr/local hierarchy; to improve coverage, the developer installs also a more modern libtool version, say 2.4, in its home directory, let's say in ~/libtool-2.4; he then tries to run the automake testsuite with this more modern libtool by doing an (apparently) simple: $ PATH=$HOME/libtool-2.4:$PATH make check But the automake testsuite would still look for libtool macros in /usr/local/share/aclocal, not in ~/libtool-2.4/share/aclocal, so the wrong version of the macros would be picked up, and the tests would either fail spuriously or (which would be worse) pass without truly covering the libtool version the developers was thinking to be testing with. Worse again, the automake testsuite would *unconditionally* look for libtool macros in /usr/local/share/aclocal, so even something like: $ export ACLOCAL_PATH=$HOME/libtool-2.4/share/aclocal $ PATH=$HOME/libtool-2.4:$PATH make check wouldn't work. Third and last, during a "make distcheck", automake is configured with a ${prefix} pointing to a proper subdirectory of the build directory (usually `pwd`/_inst), which gets created on-the-fly; in this case, with the old approach, the automake testsuite never found the libtool and gettext macro files, ans so the libtool and gettext tests was *always* skipped in a "make distcheck". * tests/libtool-macros.test: New helper test, looking (with the help of the `libtoolize' script) for libtool macro files required by most libtool tests, and making them easily accessible. * tests/gettext-macros.test: New helper test, looking (with the help of the `libtoolize' script) for libtool macro files required by most libtool tests, and making them easily accessible. * tests/defs.in: Update to make it rely on the results and setups of `libtool-macros.test' and `gettext-macros.test'. * tests/Makefile.am: Declare dependency of all the logs of libtool tests from `libtool-macros.log', and all the logs of gettext tests from `gettext-macros.log'. (TESTS): Add the new tests.

a95d9dc4

2011-12-22T18:17:26

fix: typos and grammaros in comments of the new test * tests/get-sysconf.test: Fix few typos, grammaros and botched wording. Reported by Eric Blake.

fe8162b7

2011-12-22T10:34:28

tests: report useful system information in 'test-suite.log' It has already happened various times that a user has run the automake testsuite, experienced a failure, read the messages telling him "See tests/test-suite.log" and "Please report to bug-automake@gnu.org", and done exactly that -- sending us only the contents of `tests/test-suite.log', which are usually not enough to start debugging the reported failure. So we have to ask him for more details, and usually also for the `config.log' file generated by configure. It's time to fix this recurring feedback inefficiency. We do so by creating a dummy test case that takes care of copying the contents of `config.log', plus other useful system information, in the final `test-suite.log'. * tests/get-sysconf.test: New test, gathering system information and then always terminating with a SKIP, so that its output gets copied in `test-suite.log'. * tests/Makefile.am (TESTS): Add it.

e9150626

2011-12-08T22:54:18

repo: don't commit generated files in the git repository anymore It has been quite some time since autoconf and libtool have stopped committing the generated autotools files in their git repositories, with no significant ill effects we're aware of. It's true that the autoconf bootstrap process has now the minor annoyance that a pre-installed autoconf is required to complete it; but luckily automake will not have a similar annoyance, since our bootstrap script take care, through some hoops, to use the very automake and aclocal versions from the current git checkout to generate the required aclocal.m4 and Makefile.in files. In fact, this has been a necessity also in the past, because automake has been known to use in its own build system new development features that hadn't been present in any previously released automake distribution. * aclocal.m4: Delete. * configure: Likewise. * Makefile.in: Likewise. * doc/Makefile.in: Likewise. * lib/Automake/Makefile.in: Likewise. * lib/Automake/tests/Makefile.in: Likewise. * lib/Makefile.in: Likewise. * lib/am/Makefile.in: Likewise. * m4/Makefile.in: Likewise. * tests/Makefile.in: Likewise. * .gitignore: Ignore configure, aclocal.m4, and all the Makefile.in files. * configure.ac (AC_PREREQ): New macro call, to require the latest autoconf (2.68 for the moment).

75f2b50a

2011-10-30T11:55:28

missing: don't try to re-run tar with a munged command line * lib/missing: If the default `tar' program fails with the given arguments, and GNU tar is not available, don't try to re-run the default `tar' with a munged command line (e.g., ditching possibly unportable options), as that could be subtly alter the intended semantics (and maybe even create a somewhat corrupted tarball). Also, it's worth noting that the main purpose of the `missing' script is to allow a non-developer to build the package in the face of slightly-skewed timestamps, not to provide wrappers for all the maintainer tools -- so we don't have to try too hard when `missing' is just called to wrap `tar'. * tests/missing-tar.test: New test. * tests/Makefile.am (TESTS): Add it.

7f713c38

2011-12-20T21:42:54

tests: fix spurious failure on systems lacking unistd.h This is for automake bug#10324. * tests/silent-lex-generic.test (foo.l): Add a dummy #define of YY_NO_UNISTD_H, so that the generated foo.c file won't require unistd.h to be present (it is not present when compiling with, e.g., MSVC 9).

63da4921

2011-12-16T11:12:31

test defs: hack to support autoconf-wrapper programs * tests/defs.in ($AUTOCONF): Add a dummy `-B' option to the autoconf invocation, so that, when the Debian autoconf wrapper is involved, it will correctly dispatch an autoconf >= 2.50 instead of defaulting to autoconf 2.13. ($AUTOHEADER, $AUTORECONF): Likewise, but for autoheader and autoreconf respectively. Reported by Bruno Haible: <http://lists.gnu.org/archive/html/automake/2011-12/msg00039.html>

fb49574d

2011-12-16T01:46:14

tests: fix a minor spurious failure with FreeBSD make * tests/remake-am-pr10111.test: Avoid using `#' comments in makefile recipes, as these have been confusing FreeBSD make. The failure was masked by the fact that this test is currently expected to fail. Suggested by a report from Bruno Haible.

d2b76f88

2011-12-16T01:22:57

tests: make two test scripts executable * tests/remake-am-pr10111.test: Make executable. * tests/remake-m4-pr10111.test: Likewise.

ccbb437e

2011-12-14T20:53:10

readme: don't reference the old homepage at sources.redhat.com * README: Don't reference the old homepage at sources.redhat.com, which is no longer active; reference the homepage on www.gnu.org instead. See also automake bug#10157 and bug#10248. * tests/README: Likewise, and remove related extra-pedantic advice about copyright papers for test cases (we'll ask for those papers explicitly when we think they are warranted).

ca0ba5df

2011-10-24T23:18:34

tests: fix spurious failures due to missing 'yywrap()' function The AC_PROG_LEX Autoconf macro does not diagnose a failure to find the "lex library" expected to provide a `yywrap' function (function which is required to link most lex-generated programs). On the contrary, when all the link attempts (i.e., with `-ll' and `-lfl') fail, configure declares that no lex library is needed, and simply proceeds with the configuration process -- only for the build to possibly fail later, at make time. This behaviour is intended; the Autoconf manual reads: ``You are encouraged to use Flex in your sources, since it is both more pleasant to use than plain Lex and the C source it produces is portable. In order to ensure portability, however, you must either provide a function `yywrap' or, if you don't use it (e.g., your scanner has no `#include'-like feature), simply include a `%noyywrap' statement in the scanner's source.'' This AC_PROG_LEX behaviour is causing some spurious failures of the Automake testsuite in environments which lack a proper library providing `yywrap' (this happens for example on Fedora-based systems). The proper workaround is to simply provide a fall-back implementation of `yywrap' in our lexers. * tests/cond35.test: Provide a dummy `yywrap' function. * tests/lex3.test: Likewise. * tests/silent-lex-generic.test: Likewise. * tests/silent-lex-gcc.test: Likewise. * tests/silent-many-generic.test: Likewise. * tests/silent-many-gcc.test: Likewise. Reported by Jim Meyering: <http://lists.gnu.org/archive/html/automake-patches/2011-10/msg00092.html> Cherry-picked (with some edits) from commits `v1.11-1085-gb5c3968' (master) and `v1.11-871-geb147a1' (testsuite-work).

a7983a0f

2011-11-26T14:54:00

tests: fix 'distcheck-override-infodir.test' on Cygwin * tests/distcheck-override-infodir.test (Makefile.am): Do not add any `/' between $(DESTDIR) and the following paths. Otherwise, when $(DESTDIR) is empty, the recipes will try to access files with a leading double slash, which have an implementation-defined interpretation (e.g., for Cygwin, they mean UNC paths).

39a0fd02

2011-11-24T12:14:49

cosmetics: typofix in comments * tests/remake-am-pr10111.test (Makefile.am): Fix typo in comments. * THANKS: Update. Reported by Krzysztof Żelechowski.

6bceecd1

2011-10-20T11:55:01

coverage: undistributed '.am' and '.m4' files are diagnosed The stub rules emitted to work around the "deleted header problem" for `.m4' files (included by autoconf in e.g., configure.ac) and for `.am' files (included by automake in e.g., Makefile.am) should not prevent "make" from correctly complaining when such a required file is missing from a distribution tarball. * tests/dist-missing-am.test: New test. * tests/dist-missing-m4.test: Likewise. * tests/dist-missing-included-m4.test: Likewise. * tests/Makefile.am (TESTS): Add them. Suggestion by Ralf Wildenhues.

237b9320

2011-10-16T17:07:19

coverage: required but missing '.am' and '.m4' files are diagnosed The stub rules emitted to work around the "deleted header problem" for `.m4' files (included by autoconf in e.g., configure.ac) and for `.am' files (included by automake in e.g., Makefile.am) should not prevent the remake rules from correctly erroring out when a still-required file is missing. * tests/deleted-am.test: New test. * tests/deleted-m4.test: Likewise. * tests/Makefile.am (TESTS): Add them.

83374141

2011-11-22T20:50:53

coverage: expose automake bug#10111 in the testsuite * tests/remake-am-pr10111.test: New test, xfailing. * tests/remake-m4-pr10111.test: Likewise. * tests/Makefile.am (TESTS, XFAIL_TESTS): Add them.

eaa53725

2011-11-13T10:25:43

tests: fix spurious failure with older install-info * tests/install-info-dir.test (foo.texi): Also add proper `@settitle', `@dircategory' and `@direntry' directive, otherwise older versions of `install-info' (e.g., 4.8) will fail to create the `dir' index file in ${infodir}. Problem revealed by a failure on NetBSD 5.1.

75ae56f0

2011-11-12T22:24:36

maintcheck: fix spurious failure in 'color2.test' * tests/color2.test: Avoid creative quoting to avoid a spurious failure of the `sc_tests_Exit_not_exit' maintainer check.

eae36caf

2011-11-12T18:41:53

tests: fix spurious error in 'uninstall-fail.test' on Solaris * tests/uninstall-fail.test: Solaris 10 /usr/xpg4/bin/sh can add a line number before the `:' in the error messages issued by shell builtins. Account for that in our grepping of make output.

77d7a6f7

2011-11-12T18:25:38

tests: fix typo in 'uninstall-fail.test' * tests/uninstall-fail.test: Always use `$rm_f_is_silent_on_error' instead of the bogus `$rm_f_is_silent_on_failure'.

18f250e8

2011-11-10T12:43:54

tests: avoid a spurious failure of 'ltinit.test' MinGW * tests/ltinit.test: Be laxer in grepping configure output, to avoid spurious failures on systems which lack POSIX dynamic linking (e.g., MinGW), or when cross-compiling for such systems. See also commit `v1.11-855-ge9e5d4a'. Report and suggestion from Peter Rosin.

c6151471

2011-11-08T19:50:29

tests: testsuite is now safe to run with dmake in parallel mode * tests/defs.in: Unset variables DMAKE_CHILD, DMAKE_DEF_PRINTED and DMAKE_MAX_JOBS, which are exported by Solaris dmake when run in parallel mode, and which might confuse make processes spawned by our testsuite.

d9ea65c0

2011-11-08T18:41:30

tests: fix spurious failures w.r.t. parallel make and colorization * tests/color2.test: Skip the test if the $MAKE program fails to consider the standard output as a tty when spawned by `expect'. This is required for make implementations, like FreeBSD make and Solaris dmake, that redirect the output of recipes to temporary files or pipes when run in parallel mode. Since we are at it, simplify the detection of a working `expect' program, and throw in other minor simplifications.

549f3844

2011-11-07T16:07:25

Merge branch 'fix-pr9579' into maint * fix-pr9579: tests: fix spurious failure in 'distcheck-override-infodir.test'

00eb9d62

2011-11-07T16:05:48

tests: fix spurious failure in 'distcheck-override-infodir.test' * tests/distcheck-override-infodir.test ($required): Add 'install-info'.

f6195336

2011-11-07T15:59:43

tests: avoid another failure of 'uninstall-fail.test' on Solaris * tests/uninstall-fail.test: On Solaris 10, if `/bin/rm' is run with the `-f' option, it doesn't print any error message when failing to remove a file (due to e.g., "Permission denied"). Yikes. Cater to this incompatibility, by relaxing the test when a faulty `rm' is detected.

1ba50d12

2011-11-03T11:28:56

Merge branch 'fix-pr9890' into maint * fix-pr9890: maint-mode: fix botched configure messages

a45c6364

2011-10-29T12:15:59

maint-mode: fix botched configure messages This change fixes automake bug#9890. * m4/maintainer.m4 (AM_MAINTAINER_MODE): Fix the "checking ..." configure message related to the enabling/disabling of maintainer mode. * tests/help-maintainer.test: Renamed ... * tests/maintmode-configure-msg.test: ... to this, and extended to cover the fixed bug. Also, since we are at it, make grepping of configure help screens stricter, and throw in some few other changes to reduce code duplication and enhance readability. * tests/Makefile.am (TESTS): Update. * THANKS: Update with Zack's new e-mail address. Report and initial patch by Zack Weinberg, test cases added by Stefano Lattarini.

182935ac

2011-10-29T12:22:50

Merge branch 'fix-pr9773' into maint * fix-pr9773: info: allow user to inhibit creation/update of '${infodir}/dir'

cb9f2c28

2011-10-24T19:45:42

Merge branch 'fix-pr8485-and-pr8526' into maint * fix-pr8485-and-pr8526: deps: partially revert commit `v1.11-512-geeee551'

1ec16686

2011-10-23T13:19:21

info: allow user to inhibit creation/update of '${infodir}/dir' With this change, we allow the user to request the install-info rules not to update the `${infodir}/dir' file, by exporting the environment variable `AM_UPDATE_INFO_DIR' to the value "no". This is especially useful to distro packagers, and is a definite improvement over our previous hack of looking whether the `install-info' program was the Debian or GNU version -- hack which had been silently broken with recent versions of debian install-info BTW (probably since dpkg 1.15.4, 2009-09-06). This change fixes automake bug#9773. See also Debian Bug#543992. * lib/am/texinfos.am: Don't look anymore at the output of `install-info --version' to decide whether to use it to update the `${infodir}/dir' or not; instead, honour the environment variable `AM_UPDATE_INFO_DIR'. * tests/install-info-dir.test: New test. * tests/Makefile.am (TESTS): Add it. * tests/defs: Also unset `AM_UPDATE_INFO_DIR', to avoid unwanted interferences from the environment. * doc/automake.texi (Texinfo): Update. * NEWS: Likewise. * THANKS: Likewise. Report by Jonathan Nieder.

9b5ced02

2011-10-22T20:51:43

Merge branch 'dejagnu-siteexp-extend' into maint * dejagnu-siteexp-extend: dejagnu: allow the package developer to extend site.exp

beef7a66

2011-02-01T09:52:43

dejagnu: allow the package developer to extend site.exp Fixes automake bug#7873. * lib/am/dejagnu.am (site.exp): Depend from the files listed in $(EXTRA_DEJAGNU_SITE_CONFIG), if any. Append their contents to the generated site.exp (still preserving user edits). * doc/automake.texi (Dejagnu Tests): Update. * tests/dejagnu-siteexp-append.test: New test. * tests/dejagnu-siteexp-extend.test: Likewise. * tests/dejagnu-siteexp-useredit.test: Likewise.ù * NEWS: Update. * tests/Makefile.am (TESTS): Update. Suggestion by Rainer Orth.

6a2fe818

2011-10-22T20:42:17

Merge branch 'dejagnu-srcdir-discrepancy' into maint * dejagnu-srcdir-discrepancy: dejagnu: ensure 'srcdir' is defined as a relative directory Fix testsuite failure of check12.test without DejaGNU. Extend and improve tests on DejaGnu support.

40c34328

2011-10-20T22:25:45

deps: partially revert commit `v1.11-512-geeee551' This change partly reverts commit "Create subdirs for generated sources even when not dep tracking", of 2011-04-02. That commit had caused the bugs #8485 and #8526. Since we are nearing the bug-fixing automake release 1.11.2, the safest policy at the moment is to just revert the problematic hunks: an older, known bug is better than a regression. * automake.in (handle_single_transform): Don't add a dirstamp dependency, even when $object is derived and lands in a subdir. * tests/Makefile.am (XFAIL_TESTS): Add lex-subobj-nodep.test, remove yacc-dist-nobuild-subdir.test.

d2b90968

2011-10-20T21:44:23

Merge branch 'test-subpkg-fix-spurious-freebsd-fail' into maint * test-subpkg-fix-spurious-freebsd-fail: tests: fix spurious failure with FreeBSD make and Yacc in VPATH

7cb64d4f

2011-10-20T21:38:52

Merge branch 'fix-pr8788' into maint * fix-pr8788: tests: avoid spurious failure in 'parallel-tests3.test'

65c01584

2011-10-20T21:31:09

tests: fix spurious failures with "chatty" make implementations * tests/distcheck-missing-m4.test: On failure, some make implementations (such as Solaris make) print the whole failed recipe on standard output. This was causing a spurious failure in the checks grepping the output from make. Work around this. * tests/distcheck-outdated-m4.test: Likewise.

100e9740

2011-10-20T17:45:12

Merge branch 'aclocal-path' into maint * aclocal-path: tests: fix spurious failure on fast machines

f8f8ec0e

2011-10-20T17:44:04

tests: fix spurious failure on fast machines * tests/aclocal-path-precedence.test: Also remove the `configure' script between different test runs, to ensure it is always remade by autoconf. Add proper explicative comments.

d91f357d

2011-10-20T17:31:11

tests: avoid spurious failure of 'uninstall-fail.test' on Solaris * tests/uninstall-fail.test: All the Solaris 10 shells (/bin/sh, /bin/ksh, and /usr/xpg4/bin/sh), upon failing to chdir to a directory with the `cd' builtin, print a message like: "sh: /root: permission denied" which doesn't report the `cd' builtin anywhere. Relax the grepping of the error message accordingly.

7a770586

2011-10-19T13:43:46

Merge branch 'fix-pr9578' into maint * fix-pr9578: tests: avoid spurious failure of 'uninstall-fail.test' on Cygwin

8c021e00

2011-10-19T13:42:40

tests: avoid spurious failure of 'uninstall-fail.test' on Cygwin * tests/uninstall-fail.test: Be sure to really skip this test on systems that allows files to be removed from unwritable directories. Motivated by a spurious failure on Cygwin 1.5.

ded01c88

2011-01-13T20:33:26

dejagnu: ensure 'srcdir' is defined as a relative directory This change fixes automake bug#7833. * lib/am/dejagnu.am (check-DEJAGNU): Prefer using plain $(srcdir) over calculating and using the absolute path of $(srcdir). * tests/dejagnu-relative-srcdir.test: New test. * tests/dejagnu-absolute-builddir.test: Likewise. * tests/Makefile.am (TESTS): Update. Report by Ian Lance Taylor. Suggestions by Ralf Wildenhues.

f5b69b8a

2011-10-18T21:05:24

tests: avoid spurious failure in 'parallel-tests3.test' This fixes automake bug#8788. * tests/parallel-tests3.test: To ensure that the serial run of the dummy testsuite is still ongoing when the parallel run has terminated, use `kill -0', not a bare `kill'. This will prevent a testsuite crash on NetBSD 5.1, and a testsuite hang on FreeBSD 8.2. Also, since we are at it, try harder to avoid possible hangs of the script in other unusual situations.

7e5ae808

2011-10-18T17:53:21

tests: fix spurious failure with FreeBSD make and Yacc in VPATH * tests/subpkg.test: Some cosmetic adjustments. Move the tests checking that $(YLWRAP) is defined and installed properly when ylwrap is in a default auxdir found in a parent package ... * tests/subpkg-yacc.test: ... into this new test, which carefully avoids to trigger the known bug#7884 (combo FreeBSD make plus Yacc plus VPATH build). * tests/Makefile.am (TESTS): Update.

94ad7e48

2011-10-17T17:46:05

Merge branch 'aclocal-path' into maint

02ab80ce

2011-10-17T17:45:41

tests: fix spurious failure with autoconf 2.62 * tests/aclocal-path-precedence.test: Rewrite configure.in, rather than appending to it, to avoid spurious failures (at least with autoconf 2.62) due to repeated calls to AC_INIT. Also, add package name and version arguments to AC_INIT, to avoid spurious errors from automake.

ba0c477b

2011-10-07T11:08:15

parallel-tests: warn on conditional TEST_EXTENSIONS definition Before this change, automake would have still bailed out, but with a confusing error message (about an invalid redefinition of TEST_EXTENSIONS). * automake.in (handle_tests): Warn explicitly if TEST_EXTENSIONS has conditional contents. * tests/test-extensions-con.test: New test. * tests/Makefile.am (TESTS): Add it. * NEWS: Update.

kc3-lang/automake/tests

tests

Log