kc3-lang/automake

Branch :

Log

Commit	Date	Message
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).
63da4921	2011-12-16 11: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-16 01: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-16 01:22:57	tests: make two test scripts executable * tests/remake-am-pr10111.test: Make executable. * tests/remake-m4-pr10111.test: Likewise.
30bd6d1e	2011-12-14 21:14:04	readme: reference webpages for automake mailing lists * README: Rationalize and reorganize the (brief) description of the automake mailing lists. In particular, instead of suggesting the reader to write to the `-request' addresses to subscribe to mailing lists, point him to the relevant webpages, where he can also subscribe via a web form.
acd3ff40	2011-12-14 21:10:20	readme: update advice about testsuite execution * README: Now that the automake testsuite uses the parallel-tests driver, there is no need for the user to capture the stdout of "make check" to determine which tests have failed: a detailed log is automatically saved into the `tests/test-suite.log' file. Since we are at it, improve the wording by dropping an extra "please".
ccbb437e	2011-12-14 20: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).
e94a2808	2011-12-12 10:20:00	hacking: some more fixlets * HACKING (Release Procedure): Place the list of pre-release bootstrap-and-test commands on a line of its own, so it's easy to select and then paste it into a terminal window. Fix the explanation of "make git-release", as, since the previous change, "make git-release" would simply run "make dist" rather than "make distcheck". Suggestion from Jim Meyering.
9c78ef3d	2011-12-12 09:10:56	* NEWS: Fix typo in 'make dist-bzip2' description.
9508ef35	2011-12-10 18:26:52	release: don't run "make distcheck" automatically * Makefile.am (git-dist): The developers should test extensively before finally creating the release tarball; so don't run "make distcheck" on their behalf here; instead ... * HACKING (Release procedure): ... state here that "make check" and "make distcheck" should be run before calling "make git-dist".
6416c6b8	2011-12-05 20:18:00	hacking: update on-line documentation for stable releases only * HACKING (Release procedure): On-line documentation at www.gnu.org should be updated for stable releases only.
f2d8555c	2011-12-05 20:15:46	hacking: described release procedure applies to beta releases too * HACKING (Release procedure): Explicitly state that the described procedure is valid for alpha/beta versions as well.
b2b29281	2011-12-05 20:10:18	readme: the documentation is production quality now * README-alpha: The documentation is now quite mature, no need to decry it.
38087e06	2011-12-05 19:57:07	hacking: tell about platform-testers mailing list * HACKING (Release procedure): Announces for alpha and beta releases should be sent to the `platform-testers@gnu.org' mailing list. Some related rewording.
beff03e0	2011-12-05 19:48:34	hacking: we don't use sources.redhat.com anymore * HACKING (Release procedure): Don't explain how to upload the web pages at sources.redhat.com; we don't use that anymore.
c3d58912	2011-12-05 19:41:19	hacking: miscellaneous minor fixes * HACKING (Administrivia): If a commit fixes a bug registered at GNU debbugs, its bug number be reported in the ChangeLog entry. Re-order the entries to give more visibility to the advice on how to verify that a commit really fixes a bug. (Working with git): Improve advice about which pre-existing branch a topic branch should be based on.
c8e01d58	2011-12-09 23:17:18	dist-xz, dist-bzip2: don't hard-code -9, honor envvar settings Before the present change, automake-generated `dist-xz' rule used a hard-coded `xz -9'. That was a problem because on this front, xz differs from gzip and bzip2. While the latter two don't incur any run-time decompression penalty for using a higher compression level, specifying -9 with xz imposes a potentially fatal virtual memory requirement on any client that wants to decompress your tar.xz file. People have complained that a tarball compressed with -9 cannot be uncompressed in a low-memory environment (wrt-based embedded). Hence, instead of defaulting to -9, which is useful only for very large tarballs, it defaults to -e (equivalent to -6e). This limits the default memory requirements imposed on decompressors, yet still gives very good compression ratios. * lib/am/distdir.am (dist-xz): Do not hard-code xz's -9: that made it impossible to override. Actually don't default to -9, either, since that induced inordinately large virtual memory usage when merely decompressing. Instead, use its XZ_OPT envvar, defaulting to -e if not defined. Suggested by Lasse Collin. (dist, dist-all) [?XZ?]: Likewise (dist-bzip2): Similarly, do not hard-code -9, but do continue to use -9 by default. Honor the BZIP2 envvar. (dist, dist-all) [?BZIP2?]: Likewise * NEWS: Update. * doc/automake.texi (The Types of Distributions): Describe the newly enabled environment variables. This is inspired to commit v1.11-389-g6da46f3, with additional changes to reflect that the xz compression level should default to -e, not -9.
7dbb5500	2011-12-09 12:47:53	news: fix typos, grammaros and suboptimal wording * NEWS: Fix typos, grammaros and suboptimal wording. Reported by Jim Meyering.
6346183d	2011-12-07 21:02:39	maint: sync auxiliary files from upstream * lib/texinfo.tex: Synced from upstream, by "make fetch". * lib/config.guess: Likewise. * lib/config.sub: Likewise.
ca0ba5df	2011-10-24 23: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).
053534fc	2011-12-04 12:11:30	depcomp: spelling fix * lib/depcomp (-h): Fix misspelling in usage diagnostic.
a7983a0f	2011-11-26 14: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-24 12: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-20 11: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-16 17: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-22 20: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.
d2ef3f5b	2011-11-22 11:52:40	fix: regenerate doc/Makefile
a4eeb532	2011-11-19 19:53:57	texinfo: work around Solaris 10 xpg4 shell bug in install rules * lib/am/texinfos.am (install-html-am): Use an extra variable indirection to work around a bug in Solaris 10 /usr/xpg4/bin/sh. Bug revealed by a failure of `txinfo21.test'. See also: <http://lists.gnu.org/archive/html/bug-autoconf/2011-11/msg00005.html> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10026#23>
4bae0177	2011-11-17 09:04:10	configure: report perl version in config.log * configure.ac: Report the version of the selected perl interpreter in config.log; this should render the logs more informative.
eaa53725	2011-11-13 10: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-12 22: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-12 18: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-12 18: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-10 12: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-08 19: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-08 18: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-07 16:07:25	Merge branch 'fix-pr9579' into maint * fix-pr9579: tests: fix spurious failure in 'distcheck-override-infodir.test'
00eb9d62	2011-11-07 16:05:48	tests: fix spurious failure in 'distcheck-override-infodir.test' * tests/distcheck-override-infodir.test ($required): Add 'install-info'.
f6195336	2011-11-07 15: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-03 11:28:56	Merge branch 'fix-pr9890' into maint * fix-pr9890: maint-mode: fix botched configure messages
a45c6364	2011-10-29 12: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.
3df373a8	2011-10-30 11:58:23	Merge branch 'fix-pr9773' into maint * fix-pr9773: fix: regenerate Makefiles
12f0a410	2011-10-30 11:58:06	fix: regenerate Makefiles
182935ac	2011-10-29 12:22:50	Merge branch 'fix-pr9773' into maint * fix-pr9773: info: allow user to inhibit creation/update of '${infodir}/dir'