kc3-lang/automake

Branch :

Log

Commit	Date	Message
84fbf466	2012-01-20 20:52:02	fixlet: flags for Fortran77 compiler are in FFLAGS, not F77FLAGS This change fixes automake bug#10555. Note that the bug was a minor one, since it didn't affect the compilation rules generated by automake, but only only the "hints" printed by automake in some error messages (e.g., "The usual way to define `FFLAGS' is to add AC_PROG_F77 to configure.ac"). * lib/Automake/Variable.pm (%_ac_macro_for_var): The code generated by AC_PROG_F77 uses FFLAGS, not F77FLAGS, as the variable where to look for switches for the Fortran 77 compiler: adjust accordingly.
be0d69f0	2012-01-19 15:09:23	cosmetics: fix a botched comment in a maintainer check * Makefile.am (sc_tests_make_without_am_makeflags): Adjust botched description of this check.
52246cc7	2012-01-18 17:55:40	cmdline parsing: move into a dedicated perl module With this change, we delegate most of the automake and aclocal code for command-line options parsing to a new module "Automake::Getopt". This allows better code sharing between automake and aclocal, and also with Autoconf, which will sync the new module from us. See also autoconf commit 'v2.68-120-gf4be358' (2012-01-17, "getopt: new Autom4te::Getopt module"), and this mailing list discussion: <http://lists.gnu.org/archive/html/autoconf-patches/2012-01/msg00033.html> This change might interact with the behaviour described in automake bug#7434; for example, starting from now, "automake -Wfoo --version" will cause automake to emit diagnostic like "unknown warning category 'foo'" before actually printing the version number and exiting. This is not a big deal in practice, and the code sharing and simplifications introduced by this patch is certainly worth it. Still, we should revisited the issue in the future. * lib/Automake/Getopt.pm: New module, basically a slightly-edited copy of the 'lib/Autom4te/Getopt.pm' file from the autoconf devel repository (commit v2.68-120-gf4be358). It defines and exports ... (parse_options): ... this new function. * automake.in (parse_arguments): Use the new function. * aclocal.in (parse_arguments): Likewise. * lib/Automake/Makefile.am (dist_perllib_DATA): Add the new file. * tests/getopt.test: Remove. * tests/list-of-tests.mk: Update.
a1e77caf	2012-01-18 13:40:21	cosmetics: move CheckListOfTests.am into tests/ After the previous change 'v1.11-660-gfbeda3d', the makefile fragment 'CheckListOfTests.am' is used only by the Makefile.am in 'tests'; so keeping them two nearer makes sense. It also help in reducing potential confusion, since (after that same change) the whole Automake testsuite is expected to be (and remain) contained into the 'tests' subdirectory. * CheckListOfTests.am: Move ... * tests/CheckListOfTests.am: ... to this. * tests/Makefile.am (include): Adjust.
fbeda3da	2012-01-18 12: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.
2a9862a8	2012-01-18 09:45:01	gitlog-to-changelog: update from upstream * lib/gitlog-to-changelog: Update from gnulib upstream. The only changes should be cosmetic and/or minor fixlets.
a6e60819	2012-01-17 23:31:19	changelog: don't cluster multiple entries under the same "date line" * lib/gitlog-to-changelog: Synced from gnulib. The new version has a new option '--no-cluster', that disables clustering of adjacent commit messages under the same "date line". * Makefile.am (gitlog_to_changelog_options): Add '--no-cluster'. Also add a proper '--format' specification to ensure we have a blank line between the summary line and the commit message body.
443114bf	2012-01-17 15:48:56	fixup: contrib: really integrate in automake build system * configure.ac (AC_CONFIG_FILES): Add 'contrib/Makefile'. * Makefile.am (SUBDIRS): Add 'contrib'.
e29c4918	2012-01-17 13:55:00	contrib: new, a directory for non-mainstream functionalities This new 'contrib' hierarchy will be a good place were to move implementation/support for obsolescent features we are not yet ready to remove completely, or were to leave experimental or third-party features to cook before their eventual inclusion in the automake core. * contrib: New directory. * contrib/README: New file. * contrib/Makefile.am: New file. (EXTRA_DIST): Distribute README.
3d6197fe	2012-01-16 18: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-13 22: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.
12dc0ec5	2012-01-16 16:42:25	vala: avoid potential useless remakes (minor bugfix) * automake.in (lang_vala_finish_target): Ensure the timestamp file from which the C files generated from Vala sources depend on gets created with a modification time that is truly older than those of said generated C files. This prevents make from attempting useless rebuilds (which were bound to happen deterministically on systems with sub-second timestamp resolutions). It is worth noting that, luckily, those useless rebuild ended up being a no-op, since the Vala compiler is careful not to update the timestamp of an output file if its content has not changed from the previous version. Still, the useless rebuilds messed up "make -q" and "make -n" invocations, and were technically incorrect (despite being, as noted, inoffensive in practice). Problem revealed by failure of tests vala-mix.test and vala5.test on a fast Solaris 10 system whose filesystem had a sub-second timestamp resolution.
3da9c4c7	2012-01-16 15: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.
20d99e05	2012-01-08 19:26:18	docs: deprecate .log -> .html conversion by parallel-tests That feature is to be deprecated in the 1.11.x series, and removed in the 1.12 release. Reference: <http://lists.gnu.org/archive/html/automake/2012-01/msg00005.html> * doc/automake.texi (Simple Tests using parallel-tests): Deprecate the '.log' -> '.html' conversion and the targets 'check-html' and 'recheck-html'. Related rewording and reformatting. * NEWS (Future backward-incompatibilities): Update.
d9a7182e	2012-01-13 18: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-13 17: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-16 10: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-16 10: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'.
48c9d57f	2012-01-15 23:45:31	build: explicitly declare some targets as .PHONY * Makefile.am (fetch, git-dist, git-release, maintainer-check): Declare as ".PHONY".
3b594a8c	2012-01-15 23:38:58	maint: remove obsolete/broken maintainer targets * Makefile.am (git-diff): Remove. First, we don't distribute diffs between an automake version and the next one anyway, so this target is pointless. Moreover, its recipe has been broken for quite a long time now, always generating an empty diff due to the spurious '$(PACKAGE)' argument that was passed to the "git diff" invocation. (path-check): Remove. The 'pathchk' program running in this check complains about any file with name longer than 14 characters, which is a ridiculously low limit for today standards. Also, we already had several test scripts (no less than 195!) that were exceeding that limit, and nobody ever complained (not even on MinGW/MSYS nor Cygwin).
8856653e	2012-01-15 23:08:21	build: improve silencing of automake build system In this change, we continue the silencing of the automake build system that has been started in commit v1.11-642-g17542c3, but which has been left incomplete there for an (absent-mindness) mistake. * Makefile.am (INSTALL): Silence the recipe. (automake, aclocal): Likewise, and improve them a little since we are at it. * lib/Automake/Makefile.am (Config.pm): Likewise.
9d9f00ed	2012-01-15 21: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-15 20: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.
05c02989	2012-01-15 17:14:04	gnupload: moved to gnulib Since the gnupload script is not required by automake-generated code (be it configure or Makefile content), and is not specifically tied to automake in any way, it is better to have its master copy installed in the gnulib repository, as is already done for similar generally-useful, maintainer-oriented scripts. We can them sync it from there. See also gnulib commit v0.0-6822-gf8b7120, and: <http://lists.gnu.org/archive/html/bug-gnulib/2012-01/msg00222.html> * Makefile.am (FETCHFILES): Added 'gnupload'. (fetch): Also sync 'gnupload' from the gnulib repository. * lib/gnupload: Synced from gnulib. * NEWS: Update.
def0340b	2012-01-15 17:10:21	sync: gitlog-to-changelog from gnulib upstream * lib/gitlog-to-changelog: Synced from upstream, by "make fetch".
59367c05	2012-01-14 10:32:13	test defs: backport optimized 'using_gmake' implementation * tests/defs.in (using_gmake): Backport optimized, result-caching implementation from master.
0188e0f5	2012-01-13 21: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.
4013982e	2012-01-14 09:57:55	vala: use "$(am__cd) $(srcdir)", not "cd $(srcdir)" * automake.in (lang_vala_finish_target): In the generated rules, use '$(am__cd)', not bare 'cd', to chdir into $(scdir). Issue revealed by the maintainer check 'sc_cd_relative_dir'.
539cae3b	2012-01-13 12: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-11 18: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-01 19: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-12 10: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-12 09:41:06	tests: make 'aclocal-install-absdir.test' executable * tests/aclocal-install-absdir.test: Make it executable.
d850165e	2012-01-08 12: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-07 01: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-07 01: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-03 16: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-06 14: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-06 13: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.
e3b0e124	2012-01-05 15:13:30	parallel-tests: avoid issue with overly long lines in sed input See automake bug#10437: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10437> and coreutils bug#10427: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10427#8> * lib/am/check.am (recheck, recheck-html): In order to strip trailing whitespace from the definition of the `$list' variable, we used to invoke sed in a way that could cause it to get passed overly long input lines, causing spurious failures. So rework the logic of the recipe to avoid any sed invocation, relying on simpler shell idioms instead. (check-TESTS): Reorganize the recipe to be more similar to the one of `recheck', for consistency and simplicity. * NEWS: Update. Report and analysis by Paul Eggert.
a6ccc2ae	2012-01-04 10:21:57	sync: auxiliary files from upstream synced * lib/texinfo.tex: Synced from upstream, by "make fetch". * lib/gitlog-to-changelog: Likewise. * lib/config.guess: Likewise. * lib/config.sub: Likewise.
b40372f9	2012-01-04 10:18:15	sync: fix syncing of 'gitlog-to-changelog' script * Makefile.am (FETCHFILES): Also list 'gitlog-to-changelog'.
e23a89ed	2012-01-04 10:09:25	maintcheck: avoid false positive in sc_tests_plain_make * Makefile.am (sc_tests_plain_make): Ensure to only match full `make' words. Avoid false positive in `silent-nested-vars.test'.
4e4dae50	2012-01-03 09: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-02 20: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-02 09: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-03 13: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-01 10:42:34	tests: make 'lzip.test' executable * tests/lzip.test: Make it executable.
2a461709	2012-01-01 10:39:10	Merge branch 'deprecate-lzma' into maint * deprecate-lzma: dist: obsolete support for lzma (superseded by xz and lzip)
e637fa2a	2011-12-30 15: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-31 08:47:34	Merge branch 'dist-lzip' into maint * dist-lzip: dist: add support for lzip compression
bff8ceca	2011-12-30 19: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.
34feafee	2011-12-30 18:13:28	docs: fix a couple broken anchors * doc/automake.texi: In previous commit v1.11-605-g5f71f2b (related to automake bug#8071), we had renamed the chapters about aclocal and automake invocation, and added anchors to the old names as not to break hyperlinks to our on-line manual. Unfortunately, these anchors had been erroneously placed before the relevant `@node' commands, instead that just after, so that they ended up pointing to the wrong chapters. Fix this. Since we are at it, tweak the wording of the comments to the anchors to better match that used in the autoconf manual. Report and suggestion by Eric Blake.
0878bd34	2011-12-30 14: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-30 13: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
5f71f2b5	2011-12-28 20:28:29	docs: fix paragraph names for automake and aclocal invocations All the other autotools entitle their invocation nodes "autofoo Invocation", whereas automake used to call its "Invoking Automake" and "Invoking aclocal". So let's try to be more consistent. This change is related to automake bug#8071. Suggestion by Reuben Thomas and Eric Blake. * doc/automake.texi (Invoking Automake): Node renamed ... (automake Invocation): ... to this. (Invoking aclocal): Node renamed ... (aclocal Invocation): ... to this. Add proper @anchor directives to avoid breaking existing web hyperlinks still using the old names of the renamed nodes.
34749105	2011-12-28 15: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-28 10: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
e6fa05e7	2011-12-28 10:17:30	maint: autogenerate ChangeLog Following the practice set by various other GNU projects, we start to automatically generate the ChangeLog file from the git commit messages. This will avoid duplication (as the ChangeLog entries were always inserted both in the git commit message and in the version-controlled ChangeLog file), and potential problems with spurious merge conflicts (which, although greatly mitigated by Bruno Haible's `git-merge-changelog' helper program, have never been completely solved). * ChangeLog: Moved ... * ChangeLog.11:... to this. * Makefile.am (EXTRA_DIST): Add it. (gitlog_to_changelog_command, gitlog_to_changelog_options): New variables. (ChangeLog, am--changelog-regen-hook): New targets. * .gitignore: Add ChangeLog.
f533e9d4	2011-12-27 22:45:23	fix: last ChangeLog entry Spotted by Dave Hart.
77b2c71c	2011-12-27 19: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'.
6c9aa325	2011-12-27 19:12:46	gitlog-to-changelog: new auxiliary script, synced from gnulib We have plans to stop maintaining a version-controlled ChangeLog file in the Automake repository, and instead begin to generate it automatically from the git log messages. To do so, we will use the `gitlog-to-changelog' script from gnulib. * lib/gitlog-to-changelog: New, synced from gnulib. * Makefile.am (fetch): Fetch and sync it. * lib/Makefile.am (EXTRA_DIST): Distribute it.
44da9cbd	2011-12-27 14: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.
a2a44d35	2011-12-26 22:38:58	fix: last entry in ChangeLog
0eaa8781	2011-12-26 18: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'.
b1b43854	2011-12-26 20:08:23	docs: fix node names for automake and aclocal invocations With the older node names, an "info automake" command issued from the command line would have opened the node about the invocation of the automake program, rather than the Top node of the automake documentation. To invoke the Top node, one had to issue the command "info Automake" instead (note the different capitalization). This was suboptimal, and certainly confusing. With this change, "info automake" will open the Top node of the automake documentation; to access the nodes about the invocation of the automake and aclocal program, one has now to issue "info automake-invocation" and "info aclocal-invocation" respectively. This change fixes automake bug#8071. See also commits `v2.61a-22-ge9215d1' and `v2.61a-72-g8c07b48' in the autoconf git repository, which tackled a similar issue. * doc/automake.texi (@direntry): Rename nodes `aclocal' and `automake' to `aclocal-invocation' and `automake-invocation' respectively. * NEWS: Update.
8493499b	2011-12-25 09: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-24 10: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-24 09: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-24 09: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-24 09:29:15	Merge branch 'tests-gettext-macros-require' into maint * tests-gettext-macros-require: tests: fix handling of gettext macros requirement
763f3ec3	2011-12-24 09: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-23 13:09:50	Merge branch 'missing-fixes' into maint * missing-fixes: tests: fix failure due to debugging code forgotten into a test
03f51958	2011-12-23 12: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-23 00: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-23 00: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>
dcc28ec3	2011-12-22 21:47:41	hacking: distribute it, and mention it in the ChangeLog Not distributing the HACKING file might make it more difficult, for some random curious user, to get informed about or interested in the Automake development process, or to send us patches. * Makefile.am (EXTRA_DIST): Add HACKING. * HACKING: It's OK to distribute this file, and to mention it in the ChangeLog.
5f335bed	2010-11-13 12: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>
f75e3bf5	2011-12-22 19:51:52	maint: distribute .xz tarballs, not .bz2 ones Many GNU packages are moving towards xz-compressed tarballs, so let's follow suit, by dropping the creation and distribution of a bzip2-compressed tarball and switching to xz instead. For compatibility and safeness, we will continue to create and distribute a gzip-compressed tarball as well. * configure.ac (AM_INIT_AUTOMAKE): Drop `dist-bzip2', add `dist-xz'. * NEWS: Update. Suggested by Jim Meyering.
4c659806	2011-12-22 19:20:46	Merge branch 'pr9768-fix' into maint * pr9768-fix: include: avoid "deleted .am file" problem
d3e03785	2011-12-22 19:16:48	maint: better use of autoconf 2.68 features * configure.ac: Now that Automake requires autoconf 2.68 for its own bootstrapping and build system, we can assume that PACKAGE_URL gets automatically AC_SUBT'd.
01c5ee33	2011-12-22 19:05:32	cosmetics: use proper m4 quoting in configure.ac * configure.ac (AC_CONFIG_SRCDIR): Use proper m4 quoting for its arguments. (AC_CONFIG_AUX_DIR): Likewise. (AC_PROG_PATH): Likewise.
9f7864ba	2011-10-16 14: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-14 10: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-22 18: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-22 10: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.
9999ab73	2011-12-05 23:40:48	python: remove relics for Python 1.5 support * m4/python.m4: The comments in here claim to support only Python >= 2.0, yet this file still has specific support for Python 1.5. Just remove it, python 1.5 is 12 years old now, and practically defunct. * NEWS: Update. See also commit `Release-1-10-205-gd5bec12', "Support for Python 3.0, drop support for pre-2.0."
0ca3983b	2011-12-21 19:58:15	configure: remove extraneous 'eval's from AM_RUN_LOG invocations * configure.ac: Remove extra 'eval's from AM_RUN_LOG invocations; for example, instead of "AM_RUN_LOG([eval $PERL --version])", simply use "AM_RUN_LOG([$PERL --version])"
e73061d3	2011-12-21 19:21:41	configure: report TeX version in config.log * configure.ac: If possible, report the version of the selected TeX program; this should render the logs more informative.
5431402f	2011-12-22 14:27:47	maint: snapshots from `maint' are still development snapshots The maintenance-oriented development line in the `maint' branch, while being usually pretty stable and 99% backward-compatible, is not always right off production-quality; but until now, the Automake package version declared in configure.ac hid this fact, since it appeared to be the version of a stable release (e.g., 11.1). Fix this. * configure.ac (AC_INIT): Bump version to "1.11.0a"
ea67a2ea	2011-12-08 21:48:25	configure: print proper message for test releases * configure.ac: If the current release is detected to be a test release or a development snapshot, print a proper warning for the user. * README-alpha: Delete, it's obsolete now (and in fact this file hasn't been touched in eleven years, since release 1.4b or so). * HACKING (Release procedure): Don't say to update README-alpha.
f60ca932	2011-12-09 18:46:54	devel: help in comparing Makefile.in from different commits Now that the generated Makefile.in, configure and aclocal.m4 files are no longer committed in Automake's git repository, a simple "git diff" or "git log" no longer shows if and how a change in Automake results in changes to the Makefile.in files and/or configure script of its own build system. Still, the ability to peek so easily at such differences has proved itself quite useful in the past, often revealing inconsistencies and blunders, and sometimes even bugs; so it would be a pity to lose that altogether. With this change, we add a new maintainer recipe that re-introduces much of that capability, by generating and comparing on the fly the Makefile.in, configure and aclocal.m4 derived from two arbitrary commits of the Automake repository. * Makefile.am (autodiffs, compare-autodiffs): New phony targets.
e9150626	2011-12-08 22: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).
26133b3b	2011-12-22 12:47:26	Merge branch 'missing-fixes' into maint * missing-fixes: missing: don't try to re-run tar with a munged command line missing: inform the user if GNU tar is called missing: if GNU tar exists but fails when called, give up missing: miscellaneous fixlets
fdc16456	2011-12-09 09:51:21	maint: remove executable bit from automake.in * automake.in: This file is not meant to be executed, only to be preprocessed to create the `automake' script; so don't leave it executable.
75f2b50a	2011-10-30 11: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.
a930b7d1	2011-10-30 10:30:09	missing: inform the user if GNU tar is called * lib/missing: If the code trying to run GNU tar is reached, it means that the previous attempt to run the default tar program has failed, very likely producing some error message. At this point, just running GNU tar without further comments might be confusing.
82bf2d35	2011-10-30 10:12:28	missing: if GNU tar exists but fails when called, give up * lib/missing: If the code trying to run GNU tar is reached, don't continue if the invoked GNU tar program fails, as there is little point in doing so (and can even be confusing and counter-productive).
b2b375c3	2011-10-30 09:57:50	missing: miscellaneous fixlets * lib/missing: Some shells, such as Solaris or FreeBSD /bin/sh, warn about missing programs before performing redirections. Therefore, where we have to silently check whether a program exists, perform redirections on a subshell. Remove redundant uses of double-quotes in variable definitions. Delete an extra blank line.
7f713c38	2011-12-20 21: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).