kc3-lang/automake

Branch :

Log

Author Commit Date CI Message
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'
cb9f2c28 2011-10-24 19:45:42 Merge branch 'fix-pr8485-and-pr8526' into maint * fix-pr8485-and-pr8526: deps: partially revert commit `v1.11-512-geeee551'
1ec16686 2011-10-23 13:19:21 info: allow user to inhibit creation/update of '${infodir}/dir' With this change, we allow the user to request the install-info rules not to update the `${infodir}/dir' file, by exporting the environment variable `AM_UPDATE_INFO_DIR' to the value "no". This is especially useful to distro packagers, and is a definite improvement over our previous hack of looking whether the `install-info' program was the Debian or GNU version -- hack which had been silently broken with recent versions of debian install-info BTW (probably since dpkg 1.15.4, 2009-09-06). This change fixes automake bug#9773. See also Debian Bug#543992. * lib/am/texinfos.am: Don't look anymore at the output of `install-info --version' to decide whether to use it to update the `${infodir}/dir' or not; instead, honour the environment variable `AM_UPDATE_INFO_DIR'. * tests/install-info-dir.test: New test. * tests/Makefile.am (TESTS): Add it. * tests/defs: Also unset `AM_UPDATE_INFO_DIR', to avoid unwanted interferences from the environment. * doc/automake.texi (Texinfo): Update. * NEWS: Likewise. * THANKS: Likewise. Report by Jonathan Nieder.
9b5ced02 2011-10-22 20:51:43 Merge branch 'dejagnu-siteexp-extend' into maint * dejagnu-siteexp-extend: dejagnu: allow the package developer to extend site.exp
beef7a66 2011-02-01 09:52:43 dejagnu: allow the package developer to extend site.exp Fixes automake bug#7873. * lib/am/dejagnu.am (site.exp): Depend from the files listed in $(EXTRA_DEJAGNU_SITE_CONFIG), if any. Append their contents to the generated site.exp (still preserving user edits). * doc/automake.texi (Dejagnu Tests): Update. * tests/dejagnu-siteexp-append.test: New test. * tests/dejagnu-siteexp-extend.test: Likewise. * tests/dejagnu-siteexp-useredit.test: Likewise.ù * NEWS: Update. * tests/Makefile.am (TESTS): Update. Suggestion by Rainer Orth.
6a2fe818 2011-10-22 20:42:17 Merge branch 'dejagnu-srcdir-discrepancy' into maint * dejagnu-srcdir-discrepancy: dejagnu: ensure 'srcdir' is defined as a relative directory Fix testsuite failure of check12.test without DejaGNU. Extend and improve tests on DejaGnu support.
e98cba8d 2011-10-21 08:39:48 * THANKS: Fix whitespace issue.
40c34328 2011-10-20 22:25:45 deps: partially revert commit `v1.11-512-geeee551' This change partly reverts commit "Create subdirs for generated sources even when not dep tracking", of 2011-04-02. That commit had caused the bugs #8485 and #8526. Since we are nearing the bug-fixing automake release 1.11.2, the safest policy at the moment is to just revert the problematic hunks: an older, known bug is better than a regression. * automake.in (handle_single_transform): Don't add a dirstamp dependency, even when $object is derived and lands in a subdir. * tests/Makefile.am (XFAIL_TESTS): Add lex-subobj-nodep.test, remove yacc-dist-nobuild-subdir.test.
d2b90968 2011-10-20 21:44:23 Merge branch 'test-subpkg-fix-spurious-freebsd-fail' into maint * test-subpkg-fix-spurious-freebsd-fail: tests: fix spurious failure with FreeBSD make and Yacc in VPATH
7cb64d4f 2011-10-20 21:38:52 Merge branch 'fix-pr8788' into maint * fix-pr8788: tests: avoid spurious failure in 'parallel-tests3.test'
65c01584 2011-10-20 21:31:09 tests: fix spurious failures with "chatty" make implementations * tests/distcheck-missing-m4.test: On failure, some make implementations (such as Solaris make) print the whole failed recipe on standard output. This was causing a spurious failure in the checks grepping the output from make. Work around this. * tests/distcheck-outdated-m4.test: Likewise.
100e9740 2011-10-20 17:45:12 Merge branch 'aclocal-path' into maint * aclocal-path: tests: fix spurious failure on fast machines
f8f8ec0e 2011-10-20 17:44:04 tests: fix spurious failure on fast machines * tests/aclocal-path-precedence.test: Also remove the `configure' script between different test runs, to ensure it is always remade by autoconf. Add proper explicative comments.
d91f357d 2011-10-20 17:31:11 tests: avoid spurious failure of 'uninstall-fail.test' on Solaris * tests/uninstall-fail.test: All the Solaris 10 shells (/bin/sh, /bin/ksh, and /usr/xpg4/bin/sh), upon failing to chdir to a directory with the `cd' builtin, print a message like: "sh: /root: permission denied" which doesn't report the `cd' builtin anywhere. Relax the grepping of the error message accordingly.
7a770586 2011-10-19 13:43:46 Merge branch 'fix-pr9578' into maint * fix-pr9578: tests: avoid spurious failure of 'uninstall-fail.test' on Cygwin
8c021e00 2011-10-19 13:42:40 tests: avoid spurious failure of 'uninstall-fail.test' on Cygwin * tests/uninstall-fail.test: Be sure to really skip this test on systems that allows files to be removed from unwritable directories. Motivated by a spurious failure on Cygwin 1.5.
ded01c88 2011-01-13 20:33:26 dejagnu: ensure 'srcdir' is defined as a relative directory This change fixes automake bug#7833. * lib/am/dejagnu.am (check-DEJAGNU): Prefer using plain $(srcdir) over calculating and using the absolute path of $(srcdir). * tests/dejagnu-relative-srcdir.test: New test. * tests/dejagnu-absolute-builddir.test: Likewise. * tests/Makefile.am (TESTS): Update. Report by Ian Lance Taylor. Suggestions by Ralf Wildenhues.
f5b69b8a 2011-10-18 21:05:24 tests: avoid spurious failure in 'parallel-tests3.test' This fixes automake bug#8788. * tests/parallel-tests3.test: To ensure that the serial run of the dummy testsuite is still ongoing when the parallel run has terminated, use `kill -0', not a bare `kill'. This will prevent a testsuite crash on NetBSD 5.1, and a testsuite hang on FreeBSD 8.2. Also, since we are at it, try harder to avoid possible hangs of the script in other unusual situations.
7e5ae808 2011-10-18 17:53:21 tests: fix spurious failure with FreeBSD make and Yacc in VPATH * tests/subpkg.test: Some cosmetic adjustments. Move the tests checking that $(YLWRAP) is defined and installed properly when ylwrap is in a default auxdir found in a parent package ... * tests/subpkg-yacc.test: ... into this new test, which carefully avoids to trigger the known bug#7884 (combo FreeBSD make plus Yacc plus VPATH build). * tests/Makefile.am (TESTS): Update.
94ad7e48 2011-10-17 17:46:05 Merge branch 'aclocal-path' into maint
02ab80ce 2011-10-17 17:45:41 tests: fix spurious failure with autoconf 2.62 * tests/aclocal-path-precedence.test: Rewrite configure.in, rather than appending to it, to avoid spurious failures (at least with autoconf 2.62) due to repeated calls to AC_INIT. Also, add package name and version arguments to AC_INIT, to avoid spurious errors from automake.
ae412c38 2011-10-16 10:50:47 docs: avoid using colon character inside arguments of @pxref Fixes automake bug#9753 * doc/automake.texi (VPATH Builds): Avoid using colon character `:' inside arguments of @pxref, as this can cause problems in the generated `.info' files, and such an usage will be explicitly forbidden by future texinfo documentation. * THANKS: Update. Reported by Дилян Палаузов.
ba0c477b 2011-10-07 11:08:15 parallel-tests: warn on conditional TEST_EXTENSIONS definition Before this change, automake would have still bailed out, but with a confusing error message (about an invalid redefinition of TEST_EXTENSIONS). * automake.in (handle_tests): Warn explicitly if TEST_EXTENSIONS has conditional contents. * tests/test-extensions-con.test: New test. * tests/Makefile.am (TESTS): Add it. * NEWS: Update.
d710255c 2011-10-06 21:40:17 Merge branch 'fix-pr9400' into maint * fix-pr9400: parallel-tests: don't allow @substitutions@ in TEST_EXTENSIONS
b9b79d88 2011-10-06 21:30:04 parallel-tests: don't allow @substitutions@ in TEST_EXTENSIONS Even after the last commit `v1.11-476-g90bea64', the checks performed by automake on entries in $(TEST_EXTENSIONS) tried to allow for @substitited@ stuff. This however ends up allowing quite brittle setups, which, most importantly, are of no real practical usefulness anyway. So it's better to just disallow @substitutions@ in TEST_EXTENSIONS altogether, offering a clear error message, instead of risking weird bugs and unexpected behaviors in the generated Makefile.in. * automake.in ($TEST_EXTENSION_PATTERN): Turned from a regular expression ... (is_valid_test_extension): ... into this subroutine. Don't allow generic @substitutions@ anymore (possibly making an exception for `@EXEEXT@' under the proper circumstances). * tests/test-extensions.test: Adjust and extend.
7d40532a 2011-10-06 16:22:25 Merge branch 'fix-pr9579' into maint * fix-pr9579: tests: fix spurious failure in 'insthook.test'
39a9fd16 2011-10-06 16:21:16 tests: fix spurious failure in 'insthook.test' * tests/insthook.test (Makefile.am): Add a proper `uninstall-hook' target to remove the symlink created by the `install-exec-hook' target; this prevents "make distcheck" from failing spuriously. Since we are at it, delete an extra blank line, and add a trailing `:' command.
736fde9f 2011-10-06 16:14:46 Merge branch 'fix-pr9579' into maint * fix-pr9579: maintcheck: fix spurious failure regenerate Makefile.in
0773a998 2011-10-06 16:10:40 maintcheck: fix spurious failure * lib/am/distdir.am: Use `$(infodir)', not `${infodir}', to avoid complaints from the `sc_no_brace_variable_expansions' maintainer check.
1cfe9542 2011-10-06 16:10:23 regenerate Makefile.in
59919b1a 2011-10-06 13:42:11 fix: make a test script executable * tests/nobase-nodist.test: Make executable.
e8082fb6 2011-10-06 13:26:58 coverage: expose automake bug#9651 * tests/dist-auxfile.test: New test, xfailing. * tests/dist-auxfile-2.test: Likewise. * tests/Makefile.am (TESTS, XFAIL_TESTS): Add them.
bbfca16e 2011-10-06 10:45:25 Merge branch 'fix-pr9400' into maint * fix-pr9400: parallel-tests: automake error our on invalid TEST_EXTENSIONS
90bea64b 2011-10-01 21:31:07 parallel-tests: automake error our on invalid TEST_EXTENSIONS This change fixes automake bug#9400. * automake.in (handle_tests): Bail out if a suffix specified in TEST_EXTENSIONS would produce an invalid `xxx_LOG_COMPILER' variable or an invalid suffix rule. Before this change, automake would have issued a confusing error messages (about invalid or non-POSIX variables being defined), and in some situations would have even produced a broken `Makefile.in' file. ($TEST_EXTENSION_PATTERN): New helper variable. * doc/automake.texi (Simple Tests using parallel-tests): Document the limitations on TEST_EXTENSIONS explicitly. * NEWS: Update. * tests/test-extensions.test: New test. * tests/Makefile.am (TESTS): Update.
c5d19098 2011-10-01 19:31:22 fix: regenerate Makefile
e834f228 2011-10-01 19:28:24 Merge branch 'fix-pr7988' into maint * fix-pr7988: docs: don't suggest installing `.m4' files in hard-coded location
6816b316 2011-10-01 19:22:37 Merge branch 'fix-pr9579' into maint * fix-pr9579: distuninstallcheck: fail also when only one file is left installed
8dc8556c 2011-09-28 16:49:35 Merge branch 'fix-pr9578' into maint * fix-pr9578: fix: regenerate Makefile.in files
2126b691 2011-09-28 16:46:58 fix: regenerate Makefile.in files
b1023676 2011-09-28 13:21:11 Merge branch 'fix-pr9578' into maint * fix-pr9578: maintcheck: fix usage of `cd' instead of `$(am__cd)'
a2803e6a 2011-09-28 13:17:13 maintcheck: fix usage of `cd' instead of `$(am__cd)' * lib/am/inst-vars.am (am__uninstall_files_from_dir): Use `$(am__cd)', not plain `cd'.
b100d18d 2011-09-25 14:29:19 docs: don't suggest installing `.m4' files in hard-coded location This change fixes automake bug#7988. * doc/automake.texi (aclocal Options): State that the use of the `--print-ac-dir' option to determine the directory where third-party packages can install their `.m4' files is discouraged now. (Extending aclocal): Suggest telling the user about ACLOCAL_PATH. * THANKS: Update. Report by Peter Johansson.
a2498fe8 2011-09-23 16:06:59 distuninstallcheck: fail also when only one file is left installed This change fixes automake bug#9579. * lib/am/distdir.am (distuninstallcheck): Be stricter in ignoring a potential `dir' file created by install-info and left installed. Also, be more careful about "this can't happen" kind of errors. (am__distuninstallcheck_listfiles): New internal helper macro. * tests/distcheck-pr9579.test: New test. * tests/distcheck-override-infodir.test: Likewise. * tests/Makefile.am (TESTS): Add them. * NEWS, THANKS: Update. Report by Nick Bowler.
c4f363ff 2011-09-26 21:50:37 Merge branch 'fix-pr9578' into maint * fix-pr9578: uninstall: "make uninstall" before "make install" works
eae5cfa9 2011-09-23 22:50:14 uninstall: "make uninstall" before "make install" works This change fixes automake bug#9578. * lib/am/inst-vars.am (am__uninstall_files_from_dir): New internal macro, that defines a shell code fragment to uninstall files from a given directory. * lib/am/data.am (uninstall-%DIR%%PRIMARY%): Use it, to reduce code duplication and improve consistency and correctness. * lib/am/libs.am (uninstall-%DIR%LIBRARIES): Likewise. * lib/am/lisp.am (uninstall-%DIR%LISP): Likewise. * lib/am/mans.am (uninstall-man%SECTION%): Likewise. * lib/am/python.am (uninstall-%DIR%LIBRARIES): Likewise. * lib/am/scripts.am (uninstall-%DIR%SCRIPTS): Likewise. * tests/uninstall-pr9578.test: New test. * tests/uninstall-fail.test: New test. * tests/Makefile.am (TESTS): Add them. * NEWS, THANKS: Update. Report by Nick Bowler.
b9fa1fc1 2011-09-22 16:40:32 Merge branch 'aclocal-path' into maint * aclocal-path: tests: fix tests on aclocal search path precedences
33805241 2011-09-22 16:40:03 tests: fix tests on aclocal search path precedences * tests/aclocal-path-precedence.test: Call `$ACLOCAL' with the proper overridden system acdir.
15721c48 2011-09-20 20:20:53 fix: typo in NEWS