开源软件构建与测试

_service:tar_scm:automake.spec Changed

_service:tar_scm:backport-tests-fix-py-compile-basedir.sh-missing-test.patch Deleted

@@ -1,32 +0,0 @@
-From ae8fb00111ba0c4922609cd9beb552fb41b66cc6 Mon Sep 17 00:00:00 2001
-From: Jim Meyering <meyering@fb.com>
-Date: Tue, 18 Jan 2022 02:00:22 -0800
-Subject: PATCH tests: fix py-compile-basedir.sh: missing "test"
-
-Prompted by a patch from Thomas Deutschmann <whissi@gentoo.org>,
-via https://lists.gnu.org/r/automake-patches/2022-01/msg00001.html:
-commit v1.16.1-26-gb279a0d46 ("tests: in python tests, do not
-require .pyo files (for python3)") was missing a `test` call.
-Reported to Gentoo at https://bugs.gentoo.org/715040.
-* t/py-compile-basedir.sh: Rather than just adding the missing
-"test", rewrite using a case statement, to avoid some duplication.
----
- t/py-compile-basedir.sh | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/t/py-compile-basedir.sh b/t/py-compile-basedir.sh
-index 44b6b07c1..22e605f9d 100644
---- a/t/py-compile-basedir.sh
-+++ b/t/py-compile-basedir.sh
-@@ -43,7 +43,7 @@ for d in foo foo/bar "$(pwd)/foo" . .. ../foo ''; do
-   py_installed "$d2/sub/$f.pyc"
-   files=$(find "$d2" | grep '\.pyco$')
-   # with new-enough Python3, there are six files.
--  test $(echo "$files" | wc -l) -eq 4 || $(echo "$files" | wc -l) -eq 6
-+  case $(echo "$files" | wc -l) in 4|6) ;; *) false;; esac
-   case $d2 in
-     .|..) rm -f $files;;
-        *) rm -rf "$d2";;
--- 
-2.27.0
-

_service Changed

_service:tar_scm:automake-1.16.5.tar.xz/PLANS/rm-f-without-args.txt Deleted

@@ -1,40 +0,0 @@
-Summary
--------
-
-POSIX will say in a future version that calling "rm -f" with no argument
-is OK; and this sensible behaviour seem to be already very widespread in
-"the wild" (and possibly lacking only on those systems that are well on
-their way to obsolescence).
-
-Se we'd like to simplify several automake-generated "cleaning" rules
-accordingly, to get rid of the awful idiom:
-
-  test -z "$(VAR)" || rm -f $(VAR)
-
-See automake bug#10828.
-
-For Automake 1.14 (DONE)
-------------------------
-
-Add a temporary "probe check" in AM_INIT_AUTOMAKE that verifies that
-the no-args "rm -f" usage is supported on the system configure is
-being run on; complain loudly if this is not the case, and tell the
-user to report the situation to us.
-
-For Automake 2.0
-----------------
-
-Make any failure in the configure-time probe check introduced by the
-previous point fatal; and in case of failure, also suggest to the user
-to install an older version of GNU coreutils to work around the
-limitation of his system (this version should be old enough not to
-be bootstrapped with Automake 2.0, otherwise the user will face a
-bootstrapping catch-22).
-
-In all our recipes, start assuming "rm -f" with no argument is OK;
-simplify and de-uglify the recipes accordingly.
-
-For Automake 3.0
-----------------
-
-Remove the runtime probe altogether.

_service:tar_scm:automake-1.16.5.tar.xz/ChangeLog -> _service:tar_scm:automake-1.17.tar.xz/ChangeLog Changed

@@ -1,3 +1,2966 @@
+2024-07-10  Karl Berry  <karl@freefriends.org>
+
+	maint: prepare for 1.17 release.
+
+	* configure.ac (AC_INIT): 1.17.
+	(APIVERSION): also 1.17. (Yikes.)
+	* m4/amversion.m4: likewise (auto-updated).
+	* HACKING: tweak release info some more.
+
+2024-07-10  Karl Berry  <karl@freefriends.org>
+
+	maint: ignore all *.out in .gitignore.
+
+	* .gitignore (*.out): ignore all at top level; common temp files.
+
+2024-07-09  Karl Berry  <karl@freefriends.org>
+
+	test: explanation of MTIME_RESOLUTION resetting.
+
+	* t/ax/test-defs.in (MTIME_RESOLUTION): separate the case
+	where am_cv_filesystem_timestamp_resolution is not set for
+	more explanations, but still reset MTIME_RESOLUTION to 1
+	even if it is already set. Which it should be when running
+	tests, because config.status is sourced. But it's too late in
+	the release process to change this now; after the release,
+	can try keeping a non-empty MTIME_RESOLUTION.
+
+2024-07-08  Karl Berry  <karl@freefriends.org>
+
+	automake: info about Automake and Libtool being in different prefixes.
+
+	In response to https://bugs.gnu.org/71847.
+
+	* doc/automake.texi (Libtool library used but LIBTOOL is undefined):
+	new node. Tweak aclocal section.
+	* lib/Automake/Variable.pm (require_variables): refer to the
+	new node in the message for LT_INIT.
+	* maintainer/maint.mk (announcement) <AO>: new fn; use it
+	to output a link to the new node for test releases only.
+	* HACKING: mention M-x texinfo-master-menu, et al.
+	* doc/amhello/README: mention that the package is named amhello.
+
+2024-07-08  Karl Berry  <karl@freefriends.org>
+
+	maint: secondary updates from make fetch.
+
+	* lib/gendocs.sh: update with make fetch.
+	* lib/gitlog-to-changelog: likewise.
+	* lib/gnupload: likewise.
+	* lib/update-copyright: likewise.
+
+2024-07-03  Karl Berry  <karl@freefriends.org>
+
+	doc: tweak announce-gen invocation HACKING.
+
+	* HACKING: generalize gnulib/build-aux/announce-gen invocation.
+
+2024-07-03  Bruno Haible  <bruno@clisp.org>
+
+	automake: display whether sleep supports fractional seconds as yes/no.
+
+	https://lists.gnu.org/archive/html/automake/2024-07/msg00003.html
+
+	* m4/sanity.m4 (_AM_SLEEP_FRACTIONAL_SECONDS): Set
+	am_cv_sleep_fractional_seconds to yes/no, not true/false,
+	for consistency with other results.
+	Also "quote" this and other $am_cv values.
+	(_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): Test for yes/no.
+	* t/ax/test-defs.in: Set am_cv_sleep_fractional_seconds to 'no',
+	not 'false'.
+
+2024-07-01  Karl Berry  <karl@freefriends.org>
+
+	doc: tweak release info in HACKING.
+
+	* HACKING: mention gnulib/build-aux/announce-gen, etc.
+
+2024-06-30  Karl Berry  <karl@freefriends.org>
+
+	automake: avoid Perl-level warning on empty variable $().
+
+	https://lists.gnu.org/archive/html/automake/2024-06/msg00085.html
+
+	* lib/Automake/Variable.pm (scan_variable_expansions): recognize
+	and do nothing if the variable name is empty: $().
+	* t/varempty.sh: new test.
+	* t/list-of-tests.mk (handwritten_TESTS): add it.
+
+2024-06-29  Karl Berry  <karl@freefriends.org>
+
+	automake: test $MAKE if that's defined.
+
+	https://lists.gnu.org/archive/html/automake/2024-06/msg00051.html
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): test $MAKE
+	if it's defined, else "make".
+
+2024-06-20  Jim Meyering  <meyering@meta.com>
+
+	maint: post-release: bump version to 1.16.93
+
+	* configure.ac (AC_INIT): Post-release version bump to 1.16.93.
+	* am/amversion.m4: Update by running ./bootstrap.
+
+2024-06-20  Karl Berry  <karl@freefriends.org>
+
+	test-driver: rm spurious blank line.
+
+	* lib/test-driver (print_usage): remove spurious blank line.
+	Report from Bruno,
+	https://lists.gnu.org/archive/html/automake/2024-06/msg00075.html
+
+2024-06-20  Karl Berry  <karl@freefriends.org>
+
+	maint: prepare for 1.16.92 pretest.
+
+	* configure.ac (AC_INIT): 1.16.92.
+	* m4/amversion.m4: likewise (auto-updated).
+
+2024-06-20  Karl Berry  <karl@freefriends.org>
+
+	maint: wording tweaks for announcement.
+
+	* NEWS: Automake 2.0 may not happen.
+	* maintainer/maint.mk (announcement): missed newline.
+
+2024-06-20  Karl Berry  <karl@freefriends.org>
+
+	test: sync list-of-tests.
+
+	* t/list-of-tests.mk (handwritten_TESTS): add back t/instdir-ltlib.sh;
+	turns out all tests need to be listed there, XFAIL_TESTS is not
+	included, and that seems ok.
+	* t/CheckListOfTests.am (maintainer-check-list-of-tests): only
+	delete temp files if result is successful.
+
+2024-06-19  Karl Berry  <karl@freefriends.org>
+
+	automake: insane typo * instead of 2.
+
+	* m4/sanity.m4 (AM_SANITY_CHECK): managed to replace 2 with *
+	in ls -t test. Clearly I have gone insane.
+
+2024-06-19  Karl Berry  <karl@freefriends.org>
+
+	maint: secondary updates from make fetch.
+
+	* lib/gendocs.sh: update with make fetch.
+	* lib/gitlog-to-changelog: likewise.
+
+2024-06-19  Karl Berry  <karl@freefriends.org>
+
+	doc: rewrite subsecond NEWS entry, sanity.m4 "make" testing wrong, etc.
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): mention
+	that testing of "make" is wrong here; but $(MAKE) is not available?
+	Do some special pleading that it won't matter in practice; we'll see.
+	https://lists.gnu.org/archive/html/automake/2024-06/msg00051.html
+	(AM_SANITY_CHECK): use $* instead of $*2 to avoid
+	the confusing apparent (but not) use of shell arrays; the square
+	brackets are parsed off by m4.
+	* lib/am/check.am (output_system_information): en passant, mention
+	that $(AWK) should always be defined since AC_PROG_AWK is part of
+	AM_INIT_AUTOMAKE nowadays.
+	* NEWS: rewrite subsecond NEWS entry:workaround, more references.
+
+2024-06-19  Karl Berry  <karl@freefriends.org>
+
+	doc: original purpose of $sleep is when AC_OUTPUT is not used.
+
+	* t/ax/test-defs.in (sleep): mention original purpose of $sleep,
+	namely when AC_OUTPUT is not used and hence the sleep done in
+	AC_CONFIG_COMMANDS_* is not done:
+	  https://lists.gnu.org/archive/html/bug-automake/2010-10/msg00000.html
+	Discovered by Bruno in his rearch on the "sleep" history:
+	  https://lists.gnu.org/archive/html/automake/2024-06/msg00054.html
+
+2024-06-19  Karl Berry  <karl@freefriends.org>
+
+	lib scripts: add "(GNU Automake)" to --version output, etc.
+
+	* lib/ar-lib: add "(GNU Automake)" to --version output,
+	and the "Report bugs" block to --help.
+	* lib/compile: likewise.
+	* lib/depcomp: likewise.
+	* lib/install-sh: likewise.
+	* lib/mdate-sh: likewise.
+	* lib/missing: likewise.
+	* lib/mkinstalldirs: likewise.
+	* lib/py-compile: likewise.
+	* lib/tap-driver.sh: likewise.
+	* lib/test-driver: likewise.
+	* lib/ylwrap: likewise.
+	* t/py-compile-usage.sh: update --version pattern.
+
+2024-06-18  Mike Frysinger  <vapier@gentoo.org>
+
+	aclocal: add --aclocal-path option to override ACLOCAL_PATH envvar.
+
+	From https://lists.gnu.org/archive/html/automake-patches/2022-01/msg00029.html
+	(plus wording tweaks from Karl; and thanks to Bogdan for research).
+
+	* bin/aclocal.in (usage): relabel output of m4 search path
+	components to be somewhat more correct (Karl), although it's still
+	a mess.
+	(parse_arguments): add new option --aclocal-path=s.
+	(parse_ACLOCAL_PATH): use $aclocal_path instead of hardwiring envvar.
+	* doc/automake.texi (aclocal Options): document it.
+	(dirlist): new anchor so we can reference it.
+	(Modifying the Macro Search Path: @file{ACLOCAL_PATH}): mention
+	the option.
+	(Possible future incompatibility): tone down; it might never happen.
+	* t/aclocal-path-precedence.sh: test the option.
+	* NEWS: mention the new option.
+
+2024-06-18  Karl Berry  <karl@freefriends.org>
+
+	doc: preserve old node name.
+
+	Following 4981e5997 (doc: modernize version control doc).
+
+	* doc/automake.texi (CVS): insert @anchor{CVS} so this (prior)
+	node name will still work, e.g., in HTML. Reflow surrounding source.
+
+2024-06-17  Bruno Haible  <bruno@clisp.org>
+
+	automake: omit 1s test in _AM_FILESYSTEM_TIMESTAMP_RESOLUTION, for speed.
+
+	From https://lists.gnu.org/archive/html/automake/2024-06/msg00055.html
+	plus https://lists.gnu.org/archive/html/automake/2024-06/msg00054.html.
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): Don't test
+	whether 1 sec works; instead just accept the 2 sec delay in the
+	Automake test $sleep in exchange for not incurring the 2s delay of
+	running the test for all packages on 1s-resolution platforms.
+	Platforms that support subsecond mtimes will still use them.
+
+2024-06-17  Collin Funk  <collin.funk1@gmail.com>
+
+	test: Improve output of system information in test-suite.log.
+
+	Fixes https://bugs.gnu.org/71421.
+
+	* lib/am/check.am ($(TEST_SUITE_LOG): Use $(AWK) instead of 'awk'.
+	Remove an extra space in uname output.  Start the line with
+	"System information", and other sections with "Distribution
+	information".
+	* NEWS: add reference to #71421.
+
+2024-06-17  Bruno Haible  <bruno@clisp.org>
+
+	automake: allow omitting logs of skipped tests from test-suite.log.
+
+	* doc/automake.texi (Parallel Test Harness): Describe the contents of
+	test-suite.log. Mention IGNORE_SKIPPED_LOGS.
+	(Command-line arguments for test drivers): Document the
+	--collect-skipped-logs option.
+	* lib/test-driver (print_usage): Document --collect-skipped-logs.
+	(collect_skipped_logs): New variable.
+	(gcopy): Use collect_skipped_logs.
+	* lib/am/check.am (am__common_driver_flags): Add the contents of
+	am__collect_skipped_logs.
+	(am__check_pre): Set am__collect_skipped_logs.
+	* t/parallel-tests-without-skipped-logs.sh: New file, based on
+	t/parallel-tests-no-color-in-log.sh.
+	* t/list-of-tests.mk (handwritten_TESTS): Add it.
+	* NEWS: Mention the change.
+
+2024-06-17  Karl Berry  <karl@freefriends.org>
+
+	doc: more subsecond references.
+
+	* NEWS: add the original commit reference: 720a11531,
+	        https://lists.gnu.org/archive/html/automake-commit/2022-02/msg00009.html
+
+2024-06-16  Collin Funk  <collin.funk1@gmail.com>
+
+	test: Accommodate C23 compilers.
+
+	From https://bugs.gnu.org/71425.
+
+	* t/yacc-deleted-headers.sh: Declare yyparse before use.
+	* t/yacc-depend.sh: Likewise.
+	* t/yacc-mix-c-cxx.sh: Likewise.
+	* t/yacc-d-basic.sh: Likewise. Use void instead of empty parameter
+	list.
+	* t/yacc-depend2.sh: Likewise.
+	* NEWS: mention this.
+	* THANKS: add Collin.
+
+2024-06-16  Karl Berry  <karl@freefriends.org>
+
+	test: the instdir-ltlib test is expected to fail.
+
+	Discussed in https://bugs.gnu.org/71596.
+
+	* t/list-of-tests.mk (handwritten_TESTS): move t/instdir-ltlib.sh
+	(XFAIL_TESTS): to here. It previously worked by accident
+	because lib_LTLIBRARIES was misspelled as lib_LTIBRARIES;
+	Paul Eggert fixed that on June 7,
+	commit 1d35638b23e95fe6f41c828a3442f6d7f242f4c4, and the
+	test started failing as a result.
+
+	* t/instdir-ltlib.sh: add some doc.
+	* t/all.sh: likewise. (Another xfail test, which is mysterious to me.)
+
+2024-06-16  Karl Berry  <karl@freefriends.org>
+
+	aclocal: path separator is ; on OS/2 and Windows.
+
+	Adapted from and fixes https://bugs.gnu.org/71534.
+
+	* bin/aclocal.in (parse_ACLOCAL_PATH): use $^O to recognize OS/2
+	and Windows for the environment path element separator.
+	* NEWS: mention this.
+
+2024-06-15  Yves Orton  <demerphq@gmail.com>
+
+	automake: sort keys for reproducibility.
+
+	Fixes https://bugs.gnu.org/25629.
+
+	* bin/aclocal.in: sort keys for reproducibility.
+	* bin/automake.in: likewise.
+	* contrib/tap-driver.pl: likewise.
+	* lib/Automake/Channels.pm: likewise.
+	* lib/Automake/Condition.pm: likewise.
+	* lib/Automake/DisjConditions.pm: likewise.
+	* lib/Automake/Getopt.pm: likewise.
+	* lib/Automake/Rule.pm: likewise.
+	* THANKS: Add Yves.
+	* NEWS: mention this.
+
+2024-06-12  Karl Berry  <karl@freefriends.org>
+
+	automake: omit make subsecond tests if at one-second resolution.
+
+	Partially ameliorates report from Bruno Haible, thread at
+	https://lists.gnu.org/archive/html/automake/2024-06/msg00015.html
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): if
+	resolution is only one second, assume make works, to
+	avoid several sleeps.
+
+2024-06-12  Karl Berry  <karl@freefriends.org>
+
+	doc: typo in t/color-tests2.sh comment.
+
+	* t/color-tests2.sh: "a working a working".
+
+2024-06-07  Paul Eggert  <eggert@cs.ucla.edu>
+
+	doc: modernize version control doc
+
+	Be more generic about version control instead of saying “CVS”.
+	In the specific examples, use Git instead of CVS.
+
+2024-06-07  Paul Eggert  <eggert@cs.ucla.edu>
+
+	maint: spelling and whitespace fixes
+
+	Most of these spelling fixes are just to comments and documentation.
+	However, some affect tests as follows:
+	* t/cond36.sh (tparse.h): Fix misspelling of dependency.
+	* t/disthook.sh: Fix misspelling of file.
+	* t/help3.sh: Fix misspelling of long option.
+	* t/instdir-ltlib.sh: Fix misspellings of macro names.
+	This causes the test to fail, so someone with libtool
+	expertise needs to look into this.
+	* t/tap-no-spurious-numbers.sh (highno): Fix misspelling of shell var.
+
+2024-06-07  Paul Eggert  <eggert@cs.ucla.edu>
+
+	maint: fix version mismatch
+
+	* m4/amversion.m4 (AM_AUTOMAKE_VERSION)
+	(AM_SET_CURRENT_AUTOMAKE_VERSION): Bump to 1.16.91 (auto-updated).
+
+2024-06-06  Jim Meyering  <meyering@meta.com>
+
+	maint: post-release: bump version to 1.16.91
+
+	* configure.ac (AC_INIT): Post-release version bump to 1.16.91.
+
+2024-06-02  Jim Meyering  <meyering@meta.com>
+
+	tests: work also with v2.72-9-g7a6347d1 and newer
+
+	* t/dist-missing-m4.sh: Accommodate a slightly different diagnostic
+	("undefined or overquoted macro" rather than "possibly undefined macro")
+	in autoconf as of v2.72-9-g7a6347d1.
+
+2024-06-02  Karl Berry  <karl@freefriends.org>
+
+	maint: support test releases numbered from .90 for announcements.
+
+	* maintainer/maint.mk (beta_version_rx, alpha_version_rx):
+	update to use MAJOR.MINOR.90, .92, ..., for "beta" (test) releases,
+	and .91, .93, ... for "alpha" (development). Follows the
+	2024-01-21 change.
+	* HACKING: typo en passant.
+
+2024-05-31  Karl Berry  <karl@freefriends.org>
+
+	maint: secondary updates from make fetch.
+
+	* doc/help2man: restore copyright list as in upstream.
+	* lib/gendocs.sh: update with make fetch.
+	* lib/texinfo.tex: likewise.
+
+2024-05-31  Karl Berry  <karl@freefriends.org>
+
+	maint: prepare for next pretest.
+
+	* HACKING: typo, tweak release info.
+	* maintainer/maint.mk: typo.
+	* maintainer/syntax-checks.mk: typo, and exclude test-defs.sh
+	(actually .in) from the `...` test because I can't figure out how
+	to get the same results with $(...).
+
+2024-05-29  Karl Berry  <karl@freefriends.org>
+
+	missing: shellcheck disable=SC2006,SC2268
+
+	From Jacob Bachmeyer, in thread around
+	https://lists.gnu.org/archive/html/automake-patches/2022-01/msg00014.html
+
+	* lib/missing: disable shellcheck warnings about `...`.
+	We must support pre-POSIX shells in Automake.
+	(scriptversion=2024-05-29.18)
+
+2024-05-27  Karl Berry  <karl@freefriends.org>
+
+	test: check that subsecond mtime works with make.
+
+	Trying to fix https://bugs.gnu.org/68808.
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): check
+	that make works with subsecond mtimes, as well as sleep and ls.
+	(Known to fail with the make 3.81 that ships with macOS.)
+	* configure.ac (MTIME_RESOLUTION): notice if it erroneously
+	expands to the empty string, i.e., fall back to 1 if
+	$am_cv_filesystem_timestamp_resolution ended up being unset.
+	* t/ax/test-defs.in (MTIME_RESOLUTION): also fall back to 1
+	if the variable to not set, with a message.
+	Fix other typos en passant.
+	* HACKING: tweak.
+
+2024-05-26  Bogdan  <bogdro_rep@gmx.us>
+
+	test: objc tests on openbsd.
+
+	Fixes https://bugs.gnu.org/68179.
+
+	* t/objcxx-deps.sh: test for objc_getProperty and other
+	functions in the objc library.
+	* t/objcxx-minidemo.sh: likewise.
+	* t/strip2.sh (STRIP): use -x instead of --verbose to test
+	strip with multiple words, to work with openbsd (and aix) strip.
+
+2024-05-21  Mark Wooding  <mdw@distorted.org.uk>
+
+	doc: test-driver option args are separate words.
+
+	For https://bugs.gnu.org/70638.
+
+	As now mentioned in the manual, the description of the
+	test-driver command-line interface has been wrong since 2011
+	when it was first added. The manual, and the driver usage
+	messages themselves, have consistently shown option arguments
+	joined to the option name with `=' characters, while the
+	implementation of Automake has always provided option arguments
+	in the following argument word, and the provided test drivers
+	only accepted option arguments in the following argument word.
+
+	Because Automake has never used the `=' syntax, there can't
+	possibly be a working driver which actually follows the
+	specification as written, so, despite the fierce language of the
+	manual, we agreed that changing the specification was the right
+	approach. The `test-driver' program's usage message has already
+	been fixed (#22445), but the full extent of the problem wasn't
+	noticed at that time.
+
+	* doc/automake.texi (Command-line arguments for test drivers): Fix the
+	table of options to show arguments passed as separate words; add
+	footnote explaining this rather sorry situation.
+	* doc/automake.texi (Use TAP with the Automake test harness):
+	Remove `=' from documentation of `--diagnostic-string', because
+	that was never acceptable either.
+	* lib/tap-driver.sh: Fix usage message.
+	* contrib/tap-driver.pl: Change usage message to match the defined
+	protocol.  (This implementation parses options using Perl's
+	`Getopt::Long' module, so it accepts the `=' syntax as specified, but
+	this program isn't actually used.)
+
+2024-05-21  Karl Berry  <karl@freefriends.org>
+
+	doc: NEWS subsecond reference.
+
+	* NEWS: another subsecond reference.
+
+2024-05-06  Reuben Thomas  <rrt@sc3d.org>
+
+	doc: update Vala documentation
+
+	From https://bugs.gnu.org/70557#29.
+
+	* doc/automake.texi (Vala Support): Update the URL for Vala.
+	Drop the mention of a version requirement, as no current system
+	  will have a too-old version of Vala.
+	Note the restriction on conditional inclusion of source files in
+	  *_SOURCES.
+
+2024-04-29  Reuben Thomas  <rrt@sc3d.org>
+
+	doc: typos in test file.
+
+	From https://bugs.gnu.org/70557#23.
+
+	* t/vala-vapi.sh: typos.
+
+2024-04-27  Reuben Thomas  <rrt@sc3d.org>
+
+	doc: Vala-related typo in automake.in
+
+	From https://bugs.gnu.org/70557.
+
+	* bin/automake.in (lang_vala_finish_target): typo.
+
+2024-02-07  Bogdan  <bogdro_rep@gmx.us>
+
+	test: protect more yacc declarations against C vs. C++ linkage.
+
+	Fix for more of https://bugs.gnu.org/68832.
+
+	* t/yacc-clean-cxx.sh: more #ifdef of yylex, etc., following
+	https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62886,
+	now for OpenIndiana. Specifically:
+	#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+	* t/yacc-cxx.sh: likewise.
+	* t/yacc-d-cxx.sh: likewise.
+	* t/yacc-mix-c-cxx.sh: likewise.
+
+2024-02-03  Karl Berry  <karl@freefriends.org>
+
+	test: make bug-reporting message on test failure more explicit.
+
+	From https://bugs.gnu.org/68855.
+
+	* NEWS: mention this.
+	* lib/am/check.am ($(TEST_SUITE_LOG)) <please_report>: new fn,
+	new wording.
+	* t/ax/test-defs.in (failure_footer_text): new wording.
+	(failure_footer_text_colorized): add red.
+	* t/ax/tap-summary-aux.sh (failure_footer): use failure_footer_text*.
+	* t/tap-doc2.sh: change grep.
+	* t/testsuite-summary-color.sh: likewise.
+	* t/testsuite-summary-count-many.sh: likewise.
+	* t/testsuite-summary-count.sh: likewise.
+	* t/testsuite-summary-reference-log.sh: likewise.
+
+2024-01-30  Karl Berry  <karl@freefriends.org>
+
+	doc: mention pyenv.
+
+	* HACKING: mention pyenv as a way to test different Python versions.
+
+2024-01-29  Karl Berry  <karl@freefriends.org>
+
+	test: elide leading spaces within case for macOS sh.
+
+	Yet another fix in https://bugs.gnu.org/68119.
+
+	* t/py-compile-basedir.sh: sed away the leading spaces
+	from wc -l output within the case statement.
+
+2024-01-28  Bogdan  <bogdro_rep@gmx.us>
+
+	test: another check for PEP-3147 induced by Python 3.12.1.
+
+	Fix for more of https://bugs.gnu.org/68119.
+
+	* t/ax/am-test-lib.sh (python_has_pep3147) <am_pep3147_tag>:
+	check sys.implementation.cache_tag as well as the (old)
+	imp.get_tag. For Python 3.12.1.
+
+2024-01-28  Karl Berry  <karl@freefriends.org>
+
+	test: more rerunning autotools, C++ std:: portability.
+
+	Trying to fix more of https://bugs.gnu.org/68119.
+
+	* t/aclocal-deleted-header-aclocal-amflags.sh: $sleep
+	before file modifications.
+	* t/aclocal-deleted-header.sh: likewise.
+	* t/aclocal-deps.sh: likewise.
+	* t/subdir-add2-pr46.sh: likewise.
+	* t/yacc-mix-c-cxx.sh: #include <cstdlib> before using std::...,
+	following yacc-cxx and yacc-d-cxx tests.
+
+2024-01-27  Karl Berry  <karl@freefriends.org>
+
+	test: output system information after summary report.
+
+	From https://bugs.gnu.org/68746.
+
+	* lib/am/check.am ($(TEST_SUITE_LOG)) <output_system_information>:
+	new shell fn, called inline to write basic os information
+	into test-suite.log.
+	Also, question (do not change) the ".. contents:: :depth: 2"
+	line; what is this for?
+
+2024-01-27  Karl Berry  <karl@freefriends.org>
+
+	maint: secondary updates from make fetch.
+
+	* INSTALL: updated from make distcheck.
+	* maintainer/maint.mk (fetch): update top-level INSTALL
+	if we update lib/INSTALL.
+	* lib/gendocs.sh: update with make fetch.
+
+2024-01-24  Karl Berry  <karl@freefriends.org>
+
+	maint: Update files from upstream with 'make fetch'.
+
+	* lib/INSTALL: update with make fetch.
+	* lib/config.guess: likewise.
+	* lib/config.sub: likewise.
+	* lib/gitlog-to-changelog: likewise.
+	* lib/update-copyright: likewise.
+
+2024-01-24  Karl Berry  <karl@freefriends.org>
+
+	doc: typo for Channels.pm, mention files for which we are the master.
+
+	* HACKING: mention files for which we are the master.
+	* lib/Automake/ChannelDefs.pm: typo for Automake::Channels;
+	mention that we hold the master copy of this.
+	* lib/Automake/Channels.pm: update/add text for master copy notice.
+	* lib/Automake/Configure_ac.pm: likewise.
+	* lib/Automake/FileUtils.pm: likewise.
+	* lib/Automake/Getopt.pm: likewise.
+	* lib/Automake/XFile.pm: likewise.
+
+2024-01-24  Karl Berry  <karl@freefriends.org>
+
+	doc: more about pretest numbering.
+
+	* HACKING: mention change to numbered pretests.
+	* configure.ac: and hence am_beta_version_rx won't match any more.
+	Let's just call all pretests development snapshots.
+
+2024-01-23  Karl Berry  <karl@freefriends.org>
+
+	automake: recommend autoreconf -f with version mismatches.
+
+	From https://bugs.gnu.org/68674.
+
+	* bin/automake.in (scan_autoconf_traces): change error
+	to suggest running autoreconf -f. The version mismatch is
+	most likely to happen due to the cache files, which
+	aclocal && automake (the previous recommendation) does not delete.
+	(scan_autoconf_files): likewise.
+	* doc/automake.texi (Auto-generating aclocal.m4): mention autoreconf.
+	Other minor wording changes.
+
+2024-01-21  Karl Berry  <karl@freefriends.org>
+
+	maint: use 1.xx.90-style pretest versions.
+
+	In response to https://bugs.gnu.org/54412.
+
+	* configure.ac (AC_INIT): 1.16.90.
+	* m4/amversion.m4: Likewise (auto-updated).
+
+2024-01-20  Karl Berry  <karl@freefriends.org>
+
+	python: use deb_system instead of posix_local if prefix = /usr.
+
+	Continuing with https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54412.
+
+	* m4/python.m4 (AM_PATH_PYTHON) <am_python_setup_scheme>:
+	factor out common scheme-related code to this new variable.
+	If the scheme is posix_local and the prefix is /usr,
+	use deb_system (for Debian package builds).
+	* NEWS: more explanations (and unrelated references, en passant).
+
+2024-01-17  Gianfranco Costamagna  <locutusofborg@debian.org>
+
+	python: use posix_prefix instead of posix_local on Debian.
+
+	From https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54412#17.
+	(Patch slightly adapted by Bogdan from original by Gianfranco,
+	as posted by Stefano Rivera in message#14.)
+
+	* m4/python.m4 (AM_PATH_PYTHON): replace Debian's posix_local
+	scheme with posix_prefix.
+	* doc/automake.texi (Python) <pythondir>: say a bit more.
+	* NEWS: mention this.
+
+2024-01-17  Karl Berry  <karl@freefriends.org>
+
+	automake: a millisecond is too fast for subsecond-mtime.
+
+	This patch is from https://bugs.gnu.org/68325.
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): don't try
+	for a millisecond; make a hundredth of a second the fastest we'll go.
+
+	Apparently there are plenty of systems which supposedly support
+	subsecond-mtimes down to the millisecond and yet randomly
+	fail parallelized tests. For example:
+	https://debbugs.gnu.org/cgi/bugreport.cgi?bug=68119#18
+	Maybe the tests themselves need fixing. (The ones that run
+	autotools multiple times in succession.) A work in progress.
+
+2024-01-17  Karl Berry  <karl@freefriends.org>
+
+	doc: mention debian python 3.10 changes; master menu; etc.
+
+	* doc/automake.texi (Creating amhello): mention libtool too.
+	(FAQ): remove spurious leftover "Errors with distclean" menu entry.
+	(Top): Regenerate master menu (M-x texinfo-master-menu).
+
+2024-01-13  Mike Frysinger  <vapier@gentoo.org>
+
+	python: add 3.20 - 3.16 to the version search list.
+
+	* m4/python.m4: Add python3.20 - python3.16.
+	* NEWS: Mention these versions too.
+
+2024-01-01  Paul Eggert  <eggert@cs.ucla.edu>
+
+	maint: make update-copyright
+
+2024-01-01  Paul Eggert  <eggert@cs.ucla.edu>
+
+	maint: make fetch
+
+2023-12-31  Karl Berry  <karl@freefriends.org>
+
+	doc: overview of autotools ordering.
+
+	* doc/automake.texi (Creating amhello): briefly mention the order
+	in which to run the autotools, a la autoreconf. A couple other tweaks.
+
+2023-12-31  Bruno Haible  <bruno@clisp.org>
+
+	test: don't hang waiting for Solaris lex/yacc to read from stdin.
+
+	From https://bugs.gnu.org/68165.
+
+	* t/get-sysconf.sh: Don't let $LEX or $YACC read from stdin when
+	trying --version and --help. Only lex --version hangs, but may
+	as well avoid it in general.
+
+2023-12-30  Bruno Haible  <bruno@clisp.org>
+
+	dist: Use -9 instead of --best, and only for gzip, to pacify Alpine.
+
+	From https://bugs.gnu.org/68151.
+
+	* lib/am/distdir.am (GZIP_ENV): Set to -9, not --best, since
+	Alpine does not support --best.
+	(distcheck): Don't use GZIP_ENV when invoking gzip for decompression,
+	since Alpine does not support -1..-9 with decompression.
+	* doc/automake.texi (The Types of Distributions): Document the change.
+	* NEWS: mention this. (En passant, add more change links.)
+
+2023-12-27  Jim Meyering  <meyering@meta.com>
+
+	maint: avoid a false-positive syntax-check failure
+
+	* maintainer/syntax-checks.mk (sc_tests_plain_sleep): This would match
+	the "sleep 1" in a comment.  So filter out shell-style comments before
+	matching.
+
+2023-12-27  Jim Meyering  <meyering@meta.com>
+
+	maint: avoid a racy distcheck failure
+
+	* lib/am/distdir.am (am__remove_distdir): Use ";" not "&&" after
+	the chmod-running find, so that a failing find doesn't cause the
+	entire rule to fail.  This could happen when a directory like
+	doc/automake.t2d being processed by find is concurrently deleted
+	by another rule.
+
+2023-12-26  Hans Ulrich Niedermann  <hun@n-dimensional.de>
+
+	doc: typos in NEWS.
+
+	From https://lists.gnu.org/archive/html/automake/2023-12/msg00037.html.
+
+	* NEWS: typos.
+
+2023-12-25  Karl Berry  <karl@freefriends.org>
+
+	test: silent-defaults.sh rerun autotools each time.
+
+	Follow-up to https://bugs.gnu.org/32868.
+
+	* t/silent-defaults.sh: rerun $ACLOCAL && $AUTOMAKE for each trial,
+	else test failed. (Why it has always succeeded before now, and/or
+	what has changed, I don't know.) Remake the cache for each trial,
+	for reliability. Echo trial description.
+	* doc/automake.texi (Silent Rules): tweak text.
+	(Unsilencing Automake): new node.  Mention
+	make --debug=p to completely unsilence rules.
+
+2023-12-25  Karl Berry  <karl@freefriends.org>
+
+	test: self-announce leading installcheck/protocol/PATH information.
+
+	* t/ax/am-test-lib.sh (am_extra_info): self-announce where the
+	initial reports on installcheck, test protocol, and PATH
+	come from. Apparently this doesn't disturb the tests.
+	If other people don't like the extra verbiage, no problem to remove.
+
+2023-12-25  Karl Berry  <karl@freefriends.org>
+
+	test: force long sleep with explicit cache variable setting.
+
+	From https://bugs.gnu.org/67670.
+
+	* t/ax/test-defs.in: when MTIME_RESOLUTION is set to 1
+	because automake/autom4te do not support subsecond-mtime,
+	also set am_cv_sleep_fractional_seconds=false. Otherwise
+	the random parallel test failures from given bug and others return.
+	* m4/sanity.m4 (_AM_SLEEP_FRACTIONAL_SECONDS): reformat.
+	(_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): elide "the" in AC_CACHE_CHECK.
+	* t/amassign.sh: end with :.
+	* HACKING: more on debugging tests.
+	* NEWS: update.
+
+2023-12-24  Dimitri Papadopoulos  <dimitri.papadopoulos@gmail.com>
+
+	doc: typos from codespell.
+
+	Report and patch: https://bugs.gnu.org/68003.
+
+	* bin/automake.in: typo from codespell.
+	* configure.ac: likewise.
+	* t/dist-auxdir-many-subdirs.sh: likewise.
+	* t/instmany-mans.sh: likewise.
+	* t/instmany-python.sh: likewise.
+	* t/instmany.sh: likewise.
+	* t/nostdinc.sh: likewise.
+	* t/parallel-tests-fork-bomb.sh: likewise.
+	* t/rm-f-probe.sh: likewise.
+	* t/tap-basic.sh: likewise.
+	* t/test-driver-custom-multitest.sh: likewise.
+	* t/txinfo-vtexi3.sh: likewise.
+
+2023-12-24  Dimitri Papadopoulos  <dimitri.papadopoulos@gmail.com>
+
+	doc: update location of FETCHFILES variable.
+
+	Report and patch: https://bugs.gnu.org/68004.
+
+	* HACKING: FETCHFILES has been moved: Makefile.am ->
+	maintainer/maint.mk.
+
+2023-12-24  Karl Berry  <karl@freefriends.org>
+
+	maint: email in THANKS for Zack Weinberg.
+
+	* THANKS (Zack Weinberg): update from zackw@panix.com to
+	zack@owlfolio.org, per Zack.
+
+2023-12-24  Karl Berry  <karl@freefriends.org>
+
+	test: do not leave files as mode zero.
+
+	Follows up on https://bugs.gnu.org/67868.
+
+	* t/dist-with-unreadable-makefile-fails.sh: chmod u+rw at end.
+	Also follow usual pattern of ending tests with :, not explicit exit.
+	* t/tap-bad-prog.tap: chmod u+r at end (since only r removed).
+
+2023-12-24  Karl Berry  <karl@freefriends.org>
+
+	warn: avoid "only used once" warning for subsecond_mtime.
+
+	* bin/automake.in (version): uselessly use
+	$Automake::FileUtils::subsecond_mtime a second time to
+	avoid Perl warning.
+
+2023-12-23  Karl Berry  <karl@freefriends.org>
+
+	doc: more on help2man and "Errors with distclean".
+
+	This fixes (the rest of) https://bugs.gnu.org/67891.
+
+	* doc/automake.texi (Errors with distclean): make a subsection of
+	"Checking the Distribution". Contrast help2man usage examples of
+	Autoconf (includes man pages in distribution) and
+	Automake (no man pages, distributes the help2man script instead).
+	(Checking the Distribution): convert subheadings to subsections.
+	* doc/local.mk: also mention autoconf vs. automake approaches here,
+	and point to the manual.
+	(checklinkx): en passant, remove unused checklinkx exclude.
+
+2023-12-22  Zack Weinberg  <zack@owlfolio.org>
+
+	maint: sync autoconf Channels.pm and ChannelsDefs.pm.
+
+	Patch from https://bugs.gnu.org/67971.
+
+	The changes address <https://savannah.gnu.org/support/?110872>,
+	about m4_warn code/documentation consistency.
+	It should be impossible to reach report_bad_channel from code in
+	Automake.
+
+	* lib/Automake/Channels.pm (msg): If the channel argument is invalid,
+	don't crash; report the mistake and use the `syntax' channel.
+	(report_bad_channel): New function for reporting invalid channels.
+
+	* lib/Automake/ChannelDefs.pm (usage): Clarify that the list of
+	warning categories is exhaustive, and that ``all'', ``none'',
+	``no-CATEGORY'', and ``error'' are not warning categories.
+
+2023-12-21  Karl Berry  <karl@freefriends.org>
+
+	maint: tweak announcement text again.
+
+	* maintainer/maint.mk (announcement):
+	"(instead of replying to this mail),"
+
+2023-12-21  Karl Berry  <karl@freefriends.org>
+
+	automake: avoid unnecessary use of \K.
+
+	This fixes (part of) https://bugs.gnu.org/67891
+	and follows up on https://bugs.gnu.org/55025.
+
+	* bin/automake.in (generate_makefile) <posix>: avoid use of
+	\K when removing comment and blank lines before a .POSIX target,
+	since Solaris 10 has perl 5.8.4, and \K was added in 5.10.
+
+2023-12-20  Dave Hart  <davehart@gmail.com>
+
+	doc: typo in tap-driver.sh.
+
+	* lib/tap-driver.sh: to not too.
+
+2023-12-20  Karl Berry  <karl@freefriends.org>
+
+	maint: post-release administrivia.
+
+	* configure.ac (AC_INIT): now 1.16j, since 1.16i pretest was
+	released (on 2023-12-18).
+	* m4/amversion.m4: Likewise (auto-updated by "make bootstrap").
+
+2023-12-18  Karl Berry  <karl@freefriends.org>
+
+	maint: announcement text tweaks.
+
+	* HACKING: mention DEVEL_SNAPSHOT=1 for us.
+	* NEWS: tweak text.
+	* maintainer/maint.mk (announcement): tweak text,
+	ls -l ./announcement as a clue as to where the result is.
+
+2023-12-17  karl  <karl@mist.freefriends.org.(none)>
+
+	dist: more forcefully deal with mode 0 directories created by tests.
+
+	From https://bugs.gnu.org/67868.
+
+	* lib/am/distdir.am (am__remove_distdir): make directories
+	readable and searchable, not just writable. (Also typo.)
+	* t/local.mk (clean-local-check): ensure directories are
+	at least mode 700
+	* t/uninstall-fail.sh: restore reasonable permissions of
+	the mode 0 $inst/share directory at the end.
+
+2023-12-13  Karl Berry  <karl@freefriends.org>
+
+	doc: checklinkx tweaks.
+
+	* HACKING: mention checklinkx to check for broken links.
+	* contrib/checklinkx: mention us in version info;
+	use warnings instead of -w.
+
+2023-12-11  Karl Berry  <karl@freefriends.org>
+
+	maint: Update files from upstream with 'make fetch'.
+
+	* lib/INSTALL: update with make fetch.
+	* lib/config.guess: Update.
+	* lib/config.sub: Likewise.
+	* lib/gendocs.sh: Likewise.
+	* lib/gendocs_template: Likewise.
+	* lib/texinfo.tex: Likewise.
+	* lib/update-copyright: Likewise.
+
+2023-12-10  Reuben Thomas  <rrt@sc3d.org>
+
+	doc: add advice to list Yacc/Lex generated sources in BUILT_SOURCES.
+
+	For https://bugs.gnu.org/62791.
+
+	* doc/automake.texi (Yacc and Lex): it seems to be necessary to
+	list the generated C source file for a Yacc/Lex file, as well as the
+	header file, in BUILT_SOURCES.
+
+2023-12-10  Karl Berry  <karl@freefriends.org>
+
+	doc: NEWS entry for OBJCXX tags.
+
+	This helps https://bugs.gnu.org/67539.
+
+	* NEWS: update; forgot to commit with prior code change.
+
+2023-12-10  Karl Berry  <karl@freefriends.org>
+
+	automake: pass OBJC and OBJCXX tags to libtool.
+
+	This helps https://bugs.gnu.org/67539.
+
+	* bin/automake.in <register_language>: pass libtool_flag
+	of OBJC and OBJCXX for the respective languages.
+
+2023-12-10  Zack Weinberg  <zack@owlfolio.org>
+
+	automake: again revise file mtime resolution support.
+
+	This patch is from https://bugs.gnu.org/67670.
+
+	In order for the Automake testsuite to be able to use sub-second
+	delays to control whether certain files are considered newer
+	than others, five(!) separate pieces of software all need to
+	cooperate: automake itself, autoconf's internal `autom4te'
+	utility, the Perl interpreter and its libraries, the sleep(1)
+	shell utility, and finally the filesystem hosting the build
+	directory. The existing tests for this are a combination of
+	inadequate and incorrect. This patch, in conjunction with a
+	patch just committed to Autoconf trunk,
+	https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=39d96e6fff7ceae63b823872602caf4d255a38c8
+
+	should make everything much more robust, as follows:
+
+	- _AM_FILESYSTEM_TIMESTAMP_RESOLUTION is completely rewritten.
+	 It no longer looks for autom4te at all, because this macro is
+	 invoked unconditionally from AM_INIT, so *every* project that
+	 uses Automake would get this test that's only relevant to
+	 Automake's own testsuite. Also, it tries sleeping for as little
+	 as one millisecond (smaller delays consistently get rounded up
+	 to 1ms on my computer and I expect that's universal), it should
+	 accurately detect FAT's two-second resolution now, and it should
+	 not be tripped up anymore by running at precisely the moment
+	 that will make a 0.1s sleep cross a 1s boundary (this may sound
+	 unlikely but it used to cause a couple of test failures *every
+	 time* I ran the automake testsuite on a network filesystem that
+	 only supported 1s resolution).
+
+	- In support of the above, the test for working ls -t moved from
+	 AM_SANITY_CHECK to _AM_FILESYSTEM_TIMESTAMP_RESOLUTION. This
+	 allowed me to simplify the test for $srcdir/configure being
+	 older than a freshly created file.
+
+	- If automake is capable of reading high-resolution file
+	 modification timestamps from the operating system, it prints
+	 `Features: subsecond-mtime' as the second line of --version
+	 output. (We can't just assume this works for sufficiently new
+	 automake, because it depends on whether the Perl interpreter
+	 provides this capability, and that's not a simple question of
+	 which version of Perl you have, either.)
+
+	- The Autoconf patch mentioned above adds the same annotation to the
+	 output of autom4te --version.
+
+	- Finally, t/ax/test-defs.in looks for the
+	 `Features: subsecond-mtime' string from both automake and
+	 autom4te and resets the sleep time to one second if it's not
+	 there. There might be a better place to put this, somewhere
+	 it'll execute every time the *overall testsuite* is invoked
+	 rather than once for each test, but I couldn't find one.
+
+	Tested on x86-64-linux with development automake and development
+	autoconf.
+
+	Previous discussion:
+	- https://lists.gnu.org/archive/html/automake/2023-03/msg00000.html
+	- https://lists.gnu.org/archive/html/automake/2023-04/msg00002.html
+	- https://lists.gnu.org/archive/html/automake/2023-12/msg00005.html
+	- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64756
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): Rewrite for
+	greater reliability.  Don't probe autom4te at all here.
+	Check for working ls -t here.
+	(AM_SANITY_CHECK): Do not cache the result.
+	Do not check for working `ls -t' here.
+	Disentangle control flow in the loop probing the relative ages of
+	  build and source directory.
+
+	* lib/Automake/FileUtils.pm: Sync from autoconf.
+	* bin/automake.in (version): Include `Features: subsecond-mtime'
+	  in the output if $Automake::FileUtils::subsecond_mtime is true.
+	* configure.ac: Rename the substitution variable MODIFICATION_DELAY
+	  to MTIME_RESOLUTION.
+	* t/ax/test-defs.in: Require both $AUTOMAKE and $AUTOM4TE to report
+	  support for high-resolution timestamps before setting $sleep to
+	  delay for less than one second.
+	* NEWS: Update info.
+
+2023-12-02  Paul Eggert  <eggert@cs.ucla.edu>
+
+	Simplify recent $PERL check
+
+	* configure.ac: Don’t spin off subprocesses to check $PERL.
+
+2023-12-02  Karl Berry  <karl@freefriends.org>
+
+	configure: better check for the perl patch containing whitespace.
+
+	More for https://bugs.gnu.org/62896.
+
+	* configure.ac: quote "$PERL" and check directly with grep.
+
+2023-12-02  Karl Berry  <karl@freefriends.org>
+
+	doc: autoconf portability link, python NEWS.
+
+	        More for https://bugs.gnu.org/67268.
+
+	* doc/automake.texi (Usage of Conditionals): link to
+	Autoconf's Limitations of Builtins, e.g.,
+	https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/html_node/Limitations-of-Builtins.html
+	* NEWS: Python version preferences are not just miscellaneous.
+
+2023-12-02  Mike Frysinger  <vapier@gentoo.org>
+
+	python: prioritize python 3.x over 2.x
+
+	Since Python 2.x went EOL years ago, stop searching for it before
+	any of the Python 3 versions.
+
+	* m4/python.m4: Move python2 after all python3 versions.
+	* NEWS: Mention update in version search.
+
+2023-11-24  Olly Betts  <olly@survex.com>
+
+	compile: support libtool .lo, needed for Xapian on Windows.
+
+	* lib/compile (func_cl_wrapper):handle *.lo like *.o.
+
+2023-11-23  Karl Berry  <karl@freefriends.org>
+
+	missing et al.: mention automake home page and gnu.org/gethelp.
+
+	* lib/compile: in --help message, include automake home page
+	and gnu.org/gethelp, following automake --help.
+	* lib/depcomp: likewise.
+	* lib/install-sh: likewise.
+	* lib/mdate-sh: likewise.
+	* lib/missing: likewise.
+	* lib/mkinstalldirs: likewise.
+	* lib/py-compile: likewise.
+	* lib/ylwrap: likewise.
+
+2023-11-23  Alex Vong  <alexvong1995@gmail.com>
+
+	missing: add autoreconf, autogen and perl as supported programs.
+
+	From:
+	https://lists.gnu.org/archive/html/automake-patches/2015-08/msg00000.html
+
+	* lib/missing: add autoreconf, autogen and perl as supported programs,
+	potentially especially useful from bootstrap scripts. Alphabetize.
+	* NEWS: mention.
+	* THANKS: new contributor.
+
+2023-11-21  Karl Berry  <karl@freefriends.org>
+
+	contrib: remove test-driver.scm, maintained elsewhere.
+
+	* contrib/test-driver.scm: remove.
+	Original patch and discussion:
+	https://lists.gnu.org/archive/html/automake-patches/2016-05/msg00000.html
+
+	Suggestion from guile-devel in 2023 that it's been updated outside
+	of Automake, and merging would not be especially helpful:
+	https://lists.gnu.org/archive/html/guile-devel/2023-11/msg00036.html
+
+2023-11-21  Pavel Raiskup  <praiskup@redhat.com>
+
+	automake: make the ARFLAGS default 'cr' instead of 'cru'.
+
+	In some GNU/Linux distributions people started to compile 'ar'
+	binary with --enable-deterministic-archives (binutils project).
+	That, however, in combination with our previous long time working
+	default AR_FLAGS=cru causes warnings on such installations:
+	ar: `u' modifier ignored since `D' is the default (see `U')
+
+	The 'u' option (at least with GNU binutils) did small optimization
+	during repeated builds because it instructed 'ar' to not
+	open/close unchanged *.o files and to rather read their contents
+	from old archive file.  However, its removal should not cause a
+	big performance hit for usual workflows.
+
+	Distributions started using --enable-deterministic-archives
+	knowing that it would disable the 'u', just to rather have a bit
+	more deterministic builds.
+
+	Also, to justify this change a bit more, keeping 'u' in ARFLAGS
+	could only result in many per-project changes to override
+	Automake's ARFLAGS default, just to silence such warnings.
+
+	Fixes bug#20082.  Reported by Eric Blake.
+
+	* bin/automake.in (handle_libraries): Use 'ARFLAGS=cr' by default.
+	* doc/automake.texi (Building a library): Mention the changed
+	ARFLAGS default.
+	(@c LocalWords): Replace 'cru' with 'cr'.
+	* m4/ar-lib.m4 (AM_PROG_AR): Cut out 'cru' string into separate
+	ARFLAGS variable with new default 'cr'.
+	* NEWS: Document.
+
+2023-11-19  Jakub Wilk  <jwilk@jwilk.net>
+
+	doc: typos in tap-driver.sh.
+
+	* lib/tap-driver.sh: fix typos.
+
+2023-11-18  Karl Berry  <karl@freefriends.org>
+
+	doc: mention shell operators preferred over `test` options.
+
+	* doc/automake.texi (Usage of Conditionals): mention that shell
+	operators (&&, ||, ()) are preferred over `test` options (-a, -o,
+	). Idea and POSIX url reference from Michael Stapelberg,
+	https://lists.gnu.org/archive/html/automake-patches/2016-10/msg00002.html
+
+2023-11-15  Karl Berry  <karl@freefriends.org>
+
+	tests: give input file to sed.
+
+	* t/posixtarget.sh: sed ... Makefile | grep,
+	not sed ... | grep Makefile, to avoid waiting forever on stdin.
+
+2023-11-15  Mike Frysinger  <vapier@gentoo.org>
+
+	m4: use AS_IF instead of ! builtin.
+
+	* m4/sanity.m4: Switch `if !` to AS_IF.
+
+2023-11-01  Jim Meyering  <meyering@meta.com>
+
+	fix: syntax error in sanity.m4
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): Fix
+	syntax error from preceding change: add a missing double quote.
+
+2023-11-01  Karl Berry  <karl@freefriends.org>
+
+	doc: more NEWS on fractional seconds.
+
+	* NEWS: fixed autom4te is not yet released.
+
+2023-11-01  Karl Berry  <karl@freefriends.org>
+
+	doc: references for non-fractional timestamps.
+
+	The non-fractional fix from Bogdan fixes
+	https://bugs.gnu.org/64756, discussed earlier in a long thread on
+	automake in 2023-03 and 2023-04; references in the bug.
+	Jacob Bachmeyer contributed to the analysis and fixes.
+
+	* m4/sanity.m4:
+
+2023-11-01  Karl Berry  <karl@freefriends.org>
+
+	doc: add bug numbers to NEWS.
+
+	* NEWS: add some bug numbers.
+
+2023-11-01  Bogdan  <bogdro_rep@gmx.us>
+
+	m4: fall back to non-fractional timestamps with older autom4te.
+
+	* m4/sanity.m4 (_AM_FILESYSTEM_TIMESTAMP_RESOLUTION): if
+	HiRes is not present in Autom4te/FileUtils.pm, do not consider
+	fractional sleeps.
+
+2023-11-01  Karl Berry  <karl@freefriends.org>
+
+	m4: syntax fix for lex change.
+
+	* m4/lex.m4: dnl caused "fiif" in output.
+
+2023-11-01  Karl Berry  <karl@freefriends.org>
+
+	doc: tiny Texinfo cleanups.
+
+	* doc/automake.texi (Public macros): Missed @var usage.
+	(Dependencies): "The Autoconf Manual" in cross-manual xref.
+
+2023-11-01  Bogdan  <bogdro_rep@gmx.us>
+
+	tests: add new test for AM_PROG_LEX arguments.
+
+	See https://bugs.gnu.org/65600 and https://bugs.gnu.org/65730
+	and https://lists.gnu.org/archive/html/automake/2023-07/msg00007.html.
+
+	* t/lex-args.sh: New test.
+	* t/list-of-tests.mk (handwritten_tests): Add it.
+
+2023-11-01  Łukasz Stelmach  <stlman@poczta.fm>
+
+	m4: update invocation of AC_PROG_LEX.
+
+	* m4/lex.m4: Pass on any arguments given to AC_PROG_LEX.
+	* doc/automake.texi: Describe this.
+	* NEWS: Mention this.
+	* THANKS: New contributor.
+
+2023-10-30  Karl Berry  <karl@freefriends.org>
+
+	doc: user conditional for dependency tracking.
+
+	* doc/automake.texi (Automatic dependency tracking): Describe
+	basing a conditional for dependency tracking on the shell variable
+	enable_dependency_tracking. Mentioned by Nick Bowler.
+	https://lists.gnu.org/archive/html/automake/2023-09/msg00004.html
+
+	* HACKING: Capitalization.
+
+2023-10-06  Karl Berry  <karl@freefriends.org>
+
+	tests: add test for new posix option.
+
+	See https://bugs.gnu.org/55025.
+
+	* t/posixtarget.sh: New test.
+	* t/list-of-tests.mk (handwritten_tests): Add it.
+	* t/README: mention using existing tests as a basis.
+
+2023-10-06  Vincent Lefevre  <vincent@vinc17.net>
+
+	automake: new option posix to emit .POSIX target first.
+
+	This patch is from https://bugs.gnu.org/55025.
+
+	* lib/Automake/Options.pm (_is_valid_easy_option): declare new
+	option "posix".
+	* bin/automake.in (generate_makefile): if the "posix" option is
+	present, add a .POSIX special target as the first non-comment
+	line in the Makefile.in files.
+	* NEWS: mention this.
+	* doc/automake.texi: likewise.
+
+2023-08-29  Frédéric Bérat  <fberat@redhat.com>
+
+	tests: avoid implicit function declarations.
+
+	This patch is from https://bugs.gnu.org/59993 (v2 part 2).
+
+	* t/c-demo.sh: This patch is related to an effort to prepare
+	Automake for future GCC/Clang versions which set c99 as default
+	standard to be used.
+
+	C99 requires that functions be properly declared before use.
+	This is true for both user functions and standard functions,
+	e.g., printf.
+
+	* t/cond35.sh: Likewise.
+	* t/dist-vs-built-sources.sh: Likewise.
+	* t/lex-clean.sh: Likewise.
+	* t/lex-multiple.sh: Likewise.
+	* t/lex-nodist.sh: Likewise.
+	* t/ltcond2.sh: Likewise.
+	* t/ltconv.sh: Likewise.
+	* t/subobj-clean-lt-pr10697.sh: Likewise.
+	* t/subobj-clean-pr10697.sh: Likewise.
+	* t/tags-pr12372.sh: Likewise.
+	* t/yacc-basic.sh: Likewise.
+	* t/yacc-clean.sh: Likewise.
+	* t/yacc-nodist.sh: Likewise.
+
+	This patch is from https://bugs.gnu.org/59993.
+
+2023-08-28  Frédéric Bérat  <fberat@redhat.com>
+
+	tests: don't try to prevent flex from including unistd.h.
+
+	This patch is from https://bugs.gnu.org/59994.
+
+	* t/cond35.sh: This patch is related to an effort to prepare
+	Automake for future GCC/Clang versions which set c99 as default
+	standard to be used.
+
+	In the current version of flex, not having unistd.h leads to
+	implicit function declarations that are not compatible with C99.
+
+	A future version of flex will (hopefully) make the "NO_UNISTD"
+	flag a no-op, and include unistd.h by default.
+
+	Also, while flex-dedicated tests had this macro set,
+	yacc tests did not, despite their use of flex.
+
+	For consistency, all the yacc/flex related tests now have the
+	"--never-interactive" option set in AM_LFLAGS, and do not try
+	define an isatty function.
+
+	* t/lex-clean-cxx.sh: Likewise.
+	* t/lex-clean.sh: Likewise.
+	* t/lex-depend-cxx.sh: Likewise.
+	* t/lex-depend.sh: Likewise.
+	* t/lex-header.sh: Likewise.
+	* t/lex-lib-external.sh: Likewise.
+	* t/lex-lib.sh: Likewise.
+	* t/lex-libobj.sh: Likewise.
+	* t/lex-line.sh: Likewise.
+	* t/lex-multiple.sh: Likewise.
+	* t/lex-nodist.sh: Likewise.
+	* t/lex-noyywrap.sh: Likewise.
+	* t/lex-pr204.sh: Likewise.
+	* t/lex-subobj-nodep.sh: Likewise.
+	* t/lex3.sh: Likewise.
+	* t/lex5.sh: Likewise.
+	* t/lexvpath.sh: Likewise.
+	* t/silent-lex.sh: Likewise.
+	* t/silent-many-languages.sh: Likewise.
+	* t/silent-yacc-headers.sh: Likewise.
+	* t/silent-yacc.sh: Likewise.
+	* t/subpkg-yacc.sh: Likewise.
+	* t/suffix10.tap: Likewise.
+	* t/yacc-auxdir.sh: Likewise.
+	* t/yacc-basic.sh: Likewise.
+	* t/yacc-bison-skeleton-cxx.sh: Likewise.
+	* t/yacc-bison-skeleton.sh: Likewise.
+	* t/yacc-clean-cxx.sh: Likewise.
+	* t/yacc-clean.sh: Likewise.
+	* t/yacc-cxx-grepping.sh: Likewise.
+	* t/yacc-cxx.sh: Likewise.
+	* t/yacc-d-basic.sh: Likewise.
+	* t/yacc-d-cxx.sh: Likewise.
+	* t/yacc-d-vpath.sh: Likewise.
+	* t/yacc-deleted-headers.sh: Likewise.
+	* t/yacc-depend.sh: Likewise.
+	* t/yacc-depend2.sh: Likewise.
+	* t/yacc-dist-nobuild-subdir.sh: Likewise.
+	* t/yacc-dist-nobuild.sh: Likewise.
+	* t/yacc-dry.sh: Likewise.
+	* t/yacc-grepping.sh: Likewise.
+	* t/yacc-grepping2.sh: Likewise.
+	* t/yacc-headers-and-dist-pr47.sh: Likewise.
+	* t/yacc-line.sh: Likewise.
+	* t/yacc-misc.sh: Likewise.
+	* t/yacc-mix-c-cxx.sh: Likewise.
+	* t/yacc-nodist.sh: Likewise.
+	* t/yacc-pr204.sh: Likewise.
+	* t/yacc-subdir.sh: Likewise.
+	* t/yacc-vpath.sh: Likewise.
+	* t/yacc-weirdnames.sh: Likewise.
+	* t/yflags-cmdline-override.sh: Likewise.
+	* t/yflags-cxx.sh: Likewise.
+	* t/yflags-d-false-positives.sh: Likewise.
+	* t/yflags-force-conditional.sh: Likewise.
+	* t/yflags-force-override.sh: Likewise.
+	* t/yflags-var-expand.sh: Likewise.
+	* t/yflags.sh: Likewise.
+
+2023-08-28  Frédéric Bérat  <fberat@redhat.com>
+
+	tests: avoid implicit function declaration in t/depcomp.sh.
+
+	This patch is from https://bugs.gnu.org/60962.
+
+	* t/ax/depcomp.sh: save and restore sub/subfoo.h, so its
+	declaration will be seen, as required by C99.
+	* THANKS: add Frédéric.
+
+2023-08-09  Karl Berry  <karl@freefriends.org>
+
+	maint: Ineiev in THANKS.
+
+	* THANKS: add Ineiev.
+
+2023-08-09  Jan Engelhardt  <jengelh@inai.de>
+
+	automake: portability warning for dollar-escaped dollar signs.
+
+	This bug and fix was posted at
+	https://lists.gnu.org/archive/html/automake/2023-08/msg00003.html.
+
+	* lib/Automake/Variable.pm (scan_variable_expansions): rewrite
+	scan_variable_expansions regex to handle dollar-escaped dollar signs.
+	* t/dollarvar2.sh: test it.
+
+2023-08-05  Ineiev  <ineiev@gnu.org>
+
+	doc: missing docdir and lispdir in _DATA description.
+
+	This changes fixes https://bugs.gnu.org/65032.
+
+	* doc/automake.texi (Data): add docdir and lispdir,
+	index doc_DATA and lisp_DATA.
+
+2023-07-20  Bruno Haible  <bruno@clisp.org>
+
+	automake: disable GNU make's internal pattern rules, for speed.
+
+	From https://bugs.gnu.org/64743.
+
+	* lib/am/footer.am: Disable GNU make's internal pattern rules.
+	* lib/Automake/Rule.pm (_conditionals_for_rule): Add special handling
+	for these pattern rules from footer.am.
+	(define): Likewise.
+	* t/nodep.sh: Update test to avoid matching the new %:: rules.
+	* t/fnoc.sh: Update test to avoid matching the new %:: SCCS rule.
+
+	* NEWS: Mention this.
+	* doc/automake.texi (Suffixes): Likewise.
+	(Doc changes written by Karl.)
+
+2023-07-14  Mike Frysinger  <vapier@gentoo.org>
+
+	automake: set test delays to am_cv_filesystem_timestamp_resolution.
+
+	This patch is from https://bugs.gnu.org/60808.
+
+	* configure.ac: Set test delays to
+	am_cv_filesystem_timestamp_resolution, instead of hardwiring
+	5sec on DJGPP and 2sec elsewhere. This speeds up test runs
+	significantly, informally as much 30%.
+
+2023-07-13  Bogdan  <bogdro_rep@gmx.us>
+
+	texi: assume .texi.in generates .texi.
+
+	This change refines the fix for https://bugs.gnu.org/54063.
+
+	* bin/automake.in (scan_texinfo_file): if .texi doesn't exist,
+	but .texi.in exists, read the latter for the Texinfo source.
+	Use the @setfilename argument, if present, to generate rules.
+	* t/txinfo-no-texi-but-texi-in.sh: new test.
+	* t/list-of-tests.mk (handwritten_tests): add it.
+
+	* doc/automake.texi (Texinfo): document this.
+	* NEWS: mention this.  (Doc changes written by Karl.)
+
+2023-07-09  Bogdan  <bogdro_rep@gmx.us>
+
+	tests: avoid some SunOS declaration conflicts.
+
+	This change: finishes fixing https://bugs.gnu.org/34151
+	  and https://bugs.gnu.org/30612 and https://bugs.gnu.org/42393;
+	fixes https://bugs.gnu.org/44795 and https://bugs.gnu.org/49755;
+	partially fixes https://bugs.gnu.org/45205
+	  and https://bugs.gnu.org/55073.
+	Still open: https://bugs.gnu.org/15256;
+
+	* t/lex-clean-cxx.sh: test __cplusplus, __sun, and __EXTERN_C__
+	before using extern "C" for the yylex decl, as explained at
+	https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45205#13.
+	* t/lex-depend-cxx.sh: likewise.
+
+	* t/yacc-cxx.sh: "using" std::exit, std::free, std::malloc.
+	* t/yacc-d-cxx.sh: likewise.
+	* t/yacc-mix-c-cxx.sh: likewise.
+
+	* NEWS: mention this.
+
+2023-07-06  Bogdan  <bogdro_rep@gmx.us>
+
+	python: generalize tests.
+
+	This change finishes fixing https://bugs.gnu.org/30556.
+
+	* t/python-prefix.sh: use $PYTHON if set, not hardwiring "python".
+	* t/python-virtualenv.sh (get-pyexecdir): new make target;
+	use it instead of hardwiring $py_site.
+
+2023-07-05  Bogdan  <bogdro_rep@gmx.us>
+
+	python: support noinst_PYTHON preceding foo_PYTHON.
+
+	This change fixes https://bugs.gnu.org/24507.
+
+	* lib/am/python.am (am__pep3147_tweak): remove conditional
+	on %?INSTALL%.
+	* t/python-pr10995.sh: test with make uninstall.
+
+2023-07-01  Bogdan  <bogdro_rep@gmx.us>
+
+	automake: do not warn that POSIX variables are non-POSIX.
+
+	This change fixes https://bugs.gnu.org/9587.
+
+	* lib/Automake/Variable.pm (_VARIABLE_PATTERN_EXTRA_POSIX):
+	new variable for $(*D) and the like.
+	(_VARIABLE_PATTERN): use it.
+	* t/vars3.sh: update test.
+	* NEWS: mention this.
+	POSIX spec (currently):
+	  https://pubs.opengroup.org/onlinepubs/9699919799/utilities/make.html
+
+2023-06-29  Karl Berry  <karl@freefriends.org>
+
+	doc: discuss setting uid/gid information in tarballs.
+
+	In response to https://bugs.gnu.org/19615.
+
+	* doc/automake.texi (Basics of Distribution): give
+	example of specifying the TAR_OPTIONS (environment)
+	variable used by GNU tar.
+
+2023-06-28  Karl Berry  <karl@freefriends.org>
+
+	maint: Update files from upstream with 'make fetch'.
+
+	* lib/INSTALL: update with make fetch.
+	* lib/config.guess: Update.
+	* lib/config.sub: Likewise.
+	* lib/gitlog-to-changelog: Likewise.
+	* lib/texinfo.tex: Likewise.
+	* lib/update-copyright: Likewise.
+
+2023-06-27  Karl Berry  <karl@freefriends.org>
+
+	doc: discuss workaround for V=99 failing.
+
+	In response to https://bugs.gnu.org/20077.
+
+	* doc/automake.texi (Tricks For Silencing Make): state and discuss
+	workarounds for the limitation of $(V) only being settable to 0 or 1.
+
+2023-06-24  Karl Berry  <karl@freefriends.org>
+
+	doc: bring a few examples up to date.
+
+	* doc/automake.texi (Built Sources Example): use @kbd for typed
+	commands; show current output.
+	(Checking the Distribution): refer to Third-Party Makefiles
+	for the do-nothing dvi target example.
+	Other small wording tweaks throughout.
+
+	* HACKING: consistently omit $ prompt.
+	Say a bit more about versions of Autoconf.
+	Describe actual current status of branches (only master in use).
+	Give some topic examples.
+	"rerun" not "re-run".
+	Other small wording tweaks throughout.
+
+2023-06-23  Karl Berry  <karl@freefriends.org>
+
+	test: avoid sometime-race condition for dist-no-built-sources test.
+
+	* t/dist-no-built-sources.sh: rm the dist .tar.gz and .tar
+	generated after inspecting, to avoid it being considered up to
+	date on the second time through the loop.
+
+2023-06-08  Paul Eggert  <eggert@cs.ucla.edu>
+
+	depcomp spelling fix
+
+	* lib/depcomp: Fix spelling in comment.
+	Originally reported by Josh Soref <jsoref@gmail.com> in:
+	https://lists.gnu.org/r/bug-gnulib/2023-06/msg00057.html
+
+2023-05-29  Karl Berry  <karl@freefriends.org>
+
+	doc: improve NAME string for man pages.
+
+	This change fixes https://bugs.gnu.org/62853 and
+	https://bugs.gnu.org/62854.
+
+	* doc/local.mk (update_mans): move $(AM_V_GEN): to calls;
+	include --name="$${HELP2MAN_NAME}".
+	(-%D%/aclocal-$(APIVERSION).1, %D%/automake-$(APIVERSION).1):
+	set HELP2MAN_NAME in environment to pass to help2man.
+
+2023-05-27  Bogdan  <bogdro_rep@gmx.us>
+
+	configure: exit explicitly if the path to perl contains spaces.
+
+	This change ameloriates https://bugs.gnu.org/62896.
+
+	* configure.ac: exit explicitly if the result of AC_PATH_PROG for
+	perl contains spaces, since shebang lines cannot support such paths.
+	* THANKS (Bogdan): add.
+
+2023-05-27  Karl Berry  <karl@freefriends.org>
+
+	doc: HACKING bug merge; doc/local.mk help2man update hints.
+
+	* HACKING: give bug merge example.
+	* doc/local.mk: how to update help2man manually;
+	fix checklinkx sleep comment.
+
+2023-05-27  Karl Berry  <karl@freefriends.org>
+
+	maint: Update files from upstream with 'make fetch' + help2man.
+
+	* lib/INSTALL: update with make fetch.
+	* lib/config.guess: Update.
+	* lib/config.sub: Likewise.
+	* lib/gendocs.sh: Likewise.
+	* lib/gnupload: Likewise.
+	* lib/texinfo.tex: Likewise.
+	* lib/update-copyright: Likewise.
+	* doc/help2man: now 1.49.1.
+
+2023-03-29  Paul Eggert  <eggert@cs.ucla.edu>
+
+	Port py-compile to Python 2.6-
+
+	* lib/py-compile: Port to Python 2.6 and earlier,
+	which lack importlib.
+
+2023-03-29  Paul Eggert  <eggert@cs.ucla.edu>
+
+	do not assume GNU tar in test
+
+	* t/dist-no-built-sources.sh: Don’t assume
+	GNU Tar’s ability of decompressing tarballs.
+	Solaris 10 ‘tar’ doesn’t do that.
+
+2023-03-29  Jacob Bachmeyer  <jcb@gnu.org>  (tiny change)
+
+	Remove parentheses around test argument lists
+
+	This works around a parser bug in Perl 5.6.2.
+	* t/pm/General.pl: Remove parentheses on argument lists.
+
+2023-03-29  Jacob Bachmeyer  <jcb@gnu.org>  (tiny change)
+
+	Improve test for blocked signals
+
+	This fixes ERRORs reported by:
+	 * t/parallel-tests-interrupt.tap
+	 * t/self-check-exit.tap
+	 * t/self-check-is-blocked-signal.tap
+	 * t/tap-signal.tap
+
+	 * t/ax/am-test-lib.sh (is_blocked_signal): Revise Perl code
+	   to more closely follow documented interfaces where
+	   available.  This also works around bugs and limitations
+	   of the POSIX module in Perl 5.6.
+
+2023-03-29  Paul Eggert  <eggert@cs.ucla.edu>
+
+	Port 'make check' to platforms lacking libtool
+
+	* t/get-sysconf.sh: Don’t fail if libtoolize is missing.
+
+2023-03-29  Paul Eggert  <eggert@cs.ucla.edu>
+
+	configure: recommend perl 5.10 or better
+
+	* configure.ac (PERL): Recommend perl 5.10 or better,
+	since 5.10 has higher-resolution timestamps.
+
+2023-03-29  Jacob Bachmeyer  <jcb@gnu.org>  (tiny change)
+
+	Gracefully degrade if Time::HiRes is not available
+
+2023-03-29  Jacob Bachmeyer  <jcb@gnu.org>  (tiny change)
+
+	Revert "maint: require perl 5.010 or later"
+
+	This reverts commit 4e3744a15c4d8bdb46c11ead2fb56c5f591b714b.
+
+2023-03-01  Karl Berry  <karl@freefriends.org>
+
+	doc: tweak old NEWS about ACLOCAL_AMFLAGS.
+
+	* NEWS: any ACLOCAL_AMFLAGS deprecation will be in a major
+	release (the hypothetical 2.0), not sooner.
+	* NEWS-2.0: developers who don't wish to be maintainers are also
+	welcome and needed.
+
+2023-02-28  Karl Berry  <karl@freefriends.org>
+
+	dirstamp: revert change of Jan 11 2023.
+
+	Fixes (hopefully) automake bug https://bugs.gnu.org/61867.
+
+	* bin/automake.in: restore explicit per-directory pattern rules,
+	since evidently @D is not supported on BSD-derived makes,
+	whatever POSIX says.  That is, revert this commit:
+	https://git.savannah.gnu.org/gitweb/?p=automake.git;a=commitdiff;h=55f8fcfd08cbf15d65d61dd2db934b6c3171cf06
+
+2023-02-02  Paul Eggert  <eggert@cs.ucla.edu>
+
+	Use higher-resolution file timestamps
+
+	* lib/Automake/FileUtils.pm (mtime):
+	Return higher-resolution file timestamps.
+	This isn’t perfect, but it’s better than what we had.
+	Code change taken from Autoconf to partially fix a race
+	<https://bugs.gentoo.org/show_bug.cgi?id=782985>.
+
+2023-02-02  Paul Eggert  <eggert@cs.ucla.edu>
+
+	maint: require perl 5.010 or later
+
+	This is needed for better treatment of high-res timestamps.
+
+2023-01-15  Frédéric Bérat  <fberat@redhat.com>
+
+	tests: depcomp: ensure make_ok() fails when run_make fails
+
+	While running automake tests with -std-gnu=c99, the compiler report
+	errors which lead to make to fail. Yet, these failures are ignored
+	during the tests, which considers them to be successful as stderror is
+	check for one specific pattern.
+
+	If make fails, investigation should be made to discover why, whatever
+	the reason for the failure is.
+
+	* t/ax/depcomp.sh: Make make_ok fail when make fails.
+
+2023-01-14  Mike Frysinger  <vapier@gentoo.org>
+
+	distdir/emacs: avoid `test -d` with MKDIR_P
+
+	We don't need to do the `test -d ... || mkdir ...` dance when we
+	have the MKDIR_P helper, so simplify this code a bit.
+
+	* lib/am/distdir.am: Use $(MKDIR_P).
+	* lib/am/lisp.am: Drop redundant `test -d`.
+
+2023-01-13  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: rework gettext to only check 'external' behavior
+
+	The gettext project deprecated non-external use back in 2010 with the
+	0.18 release, and made it fatal with the 0.20 release in 2019.  With
+	that version, calling AM_GNU_GETTEXT() fails, which means all Automake
+	tests are now skipped.  The t/gettext-macros.sh helper probes gettext
+	as such:
+
+	>+ autopoint --force
+	>  autopoint: *** AM_GNU_GETTEXT without 'external' argument is no longer supported in version 0.21.1
+	>  autopoint: *** Stop.
+	> ...
+	>+ aclocal-1.16 -Werror -Wno-syntax -I m4 --install
+	>  aclocal-1.16: warnings are treated as errors
+	>  configure.ac:4: warning: macro 'AM_GNU_GETTEXT' not found in library
+	>  configure.ac:5: warning: macro 'AM_GNU_GETTEXT_VERSION' not found in library
+	>+ echo skip_all_ "couldn't find or get gettext macros"
+
+	Since t/gettext-macros.sh generates a helper that all other gettext
+	tests use to see if gettext is available, all they get skipped.
+
+	Rework our existing tests to only check the 'external' gettext mode.
+	This should work with older versions, and we don't really need to
+	keep track of old non-external mode since it's been deprecated for
+	so long.
+
+	* t/gettext-basics.sh: Use external gettext mode, and adjust tests.
+	* t/gettext-config-rpath.sh: Likewise.
+	* t/gettext-macros.sh: Likewise.
+	* t/gettext-pr381.sh: Likewise.
+	* t/subdir-cond-gettext.sh: Likewise.
+
+2023-01-13  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: disable git log pager usage
+
+	When running this code locally, the git log call can trigger a pager
+	depending on the local settings, which in turn forces the test to be
+	interactive.  Run git with --no-pager to force disable it.
+
+	* t/get-sysconf.sh: Run git with --no-pager.
+
+2023-01-13  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: change `sort|uniq` to `sort -u`
+
+	These are equivalent, but more performant.  We already use `sort -u`
+	elsewhere in the codebase, so nothing new here really.
+
+	* t/add-missing.tap: Change `sort|uniq` to `sort -u`.
+	* t/CheckListOfTests.am: Likewise.
+
+2023-01-12  Frédéric Bérat  <fberat@redhat.com>
+
+	tests: Fix 'type defaults' error in link_cond due to main not being properly declared
+
+	This is related to an effort to prepare Automake for future GCC/Clang
+	versions which set c99 as default standard to be used.
+	Not properly declaring main as "int main(...)" is rejected since c99.
+
+	* t/link_cond.sh: Add (void) to main definition.
+
+2023-01-12  Mike Frysinger  <vapier@gentoo.org>
+
+	dirstamp: switch to a pattern rule
+
+	We can leverage $(@D) to generate a single pattern rule for all dirstamp
+	rules.  This saves many lines in the output -- normally we create 2 rules
+	(or 6 lines) per subdir, and projects that use subdirs tend to use them
+	quite a bit.
+
+	In the most extreme & unlikely case (1 subdir, no depdir support), the
+	line count is the same.  In every other case, it's always a win.
+
+	Looking at a few real world projects, the line deltas:
+	* GNU libgloss: +3 -66
+	* GNU newlib:   +3 -714
+	* GNU sim:      +3 -138
+
+	There shouldn't be any concerns about portability with $(@D) because:
+	(0) This has been in POSIX (and beyond) for decades,
+	(1) We only generate this rule iff we know the dirstamp is in a subdir
+	    (so we'd never have a case where $(@D) would expand to the cwd, and
+	    that is where a few implementations are known to be buggy),
+	(2) We already rely on $(@D) in our depdir code, and have since 2014
+	    (the Automake 1.16 release).
+
+2023-01-11  Mike Frysinger  <vapier@gentoo.org>
+
+	dirstamp: use append too instead of truncate
+
+	We changed the depfiles logic to use >> (append) instead of > (truncate)
+	due to it being slightly faster & nicer to the disk.  Do the same with
+	the dirstamp files as we only need the files to exist -- we don't care
+	about their content, and we never put anything in them ourselves.  If
+	someone else were to, we clean them up normally with `make clean`.
+
+	Simple test case on my Linux 6.1 w/ext4 on SSD:
+
+	@: > foo.txt
+	for (i = 0; i < 1000000; ++i) close(open("foo.txt", O_WRONLY|O_CREAT|O_TRUNC, 0666));
+	-> 769 msec
+
+	@: >>foo.txt
+	for (i = 0; i < 1000000; ++i) close(open("foo.txt", O_WRONLY|O_CREAT|O_APPEND, 0666));
+	-> 2 sec
+
+2023-01-08  Mike Frysinger  <vapier@gentoo.org>
+
+	rm: convert more cases to am__rm_f
+
+	Fixes automake bug https://bugs.gnu.org/10828.
+
+	Clean up a few more cases where we were doing `test ... || rm ...` to
+	avoid calling `rm -f` without arguments by leveraging am__rm_f.  These
+	were harder to find in the source due to their constructed nature.
+
+	The clean programs rules in particular were much more complicated than
+	they needed to be.  This logic boiled down to two things: delete the
+	list of programs, and then delete the list without the exeext suffix,
+	but only if the list of programs is non-empty.
+
+	The check-TESTS rule was converted to am__rm_f, but a simplification
+	was missed where the $list variable is inlined.
+
+	* bin/automake.in: Delete test -z logic and always call am__rm_f.
+	* contrib/check-html.am: Use $(am__rm_f) helper.
+	* doc/automake.texi: Update examples to match current behavior.
+	* lib/am/check.am: Inline $list variable.
+	* lib/am/progs.am: Rewrite rule to use $(am__rm_f).
+
+2023-01-08  Karl Berry  <karl@freefriends.org>
+
+	doc: overriding targets doesn't mean third-party Makefiles.
+
+	Fixes automake bug https://bugs.gnu.org/60607.
+
+	* doc/automake.texi (dvi and distcheck): simply show
+	dvi: as an example of a do-nothing Makefile (xref to Extending),
+	instead of cross-referencing the complicated method in
+	Third-Party Makefiles.
+	(Clean, Extending): wording tweaks.
+
+2023-01-04  Mike Frysinger  <vapier@gentoo.org>
+
+	check: drop unused trs_list variable
+
+	When the code that used this variable was removed, the variable
+	itself was left behind.  Clean that up now too.
+
+	* lib/am/check.am: Delete trs_list.
+
+2023-01-03  Mike Frysinger  <vapier@gentoo.org>
+
+	depend: trim spurious leading tab
+
+	These vars are replaced with a list of remove commands that are joined
+	with a \n and each line always has a leading \t inserted.  That means
+	the literal tab here before the var leads to 2 tabs included in the
+	output.  While not functionally a problem, it can be a bit confusing
+	when reading the output as it implies something is amiss.  Trimming
+	the tab also aligns with the other .am files which don't include it.
+
+	* lib/am/depend.am: Delete tab before %DISTRMS%.
+
+2023-01-03  Mike Frysinger  <vapier@gentoo.org>
+
+	maint: make update-copyright
+
+2023-01-03  Mike Frysinger  <vapier@gentoo.org>
+
+	maint: Update files from upstream with 'make fetch'
+
+	Pulls some 2023 copyright updates.
+
+	* lib/config.guess: Update.
+	* lib/config.sub: Likewise.
+	* lib/gendocs.sh: Likewise.
+	* lib/gendocs_template: Likewise.
+	* lib/gitlog-to-changelog: Likewise.
+	* lib/gnupload: Likewise.
+	* lib/texinfo.tex: Likewise.
+	* lib/update-copyright: Likewise.
+
+2022-12-12  Karl Berry  <karl@freefriends.org>
+
+	test: avoid apostrophe in test document.
+
+	From automake patch https://bugs.gnu.org/59989
+	(though a different solution), suggestion by Frederic Berat.
+
+	* t/txinfo-include.sh: avoid apostrophes in test document,
+	since Texinfo 7.0 turns them into UTF-8 by default.
+
+2022-10-06  Kelvin M. Klann  <kmk3.code@protonmail.com>
+
+	doc: typo in HACKING changes.
+
+	* HACKING: allow backward compatibilities again.
+
+2022-10-01  Karl Berry  <karl@freefriends.org>
+
+	distcheck: more .NOTPARALLEL.
+
+	* t/backcompat.sh: add .NOTPARALLEL.
+	* t/subdir-add2-pr46.sh: likewise.
+	(Maybe the problem is more general?)
+
+2022-10-01  Karl Berry  <karl@freefriends.org>
+
+	maint: Update files from upstream with 'make fetch' + help2man.
+
+	* INSTALL: update with make fetch.
+
+2022-10-01  Karl Berry  <karl@freefriends.org>
+
+	maint: Update files from upstream with 'make fetch' + help2man.
+
+	* lib/INSTALL: update with make fetch.
+	* lib/config.guess: Update.
+	* lib/config.sub: Likewise.
+	* lib/gendocs.sh: Likewise.
+	* lib/texinfo.tex: Likewise.
+	* doc/help2man: now 1.49.1.
+
+2022-10-01  Karl Berry  <karl@freefriends.org>
+
+	maintcheck: placate maintainer-check and grep 3.8.
+
+	* maintainer/syntax-checks.mk (sc_rm_minus_f): no \ before -
+	(diagnosed by grep 3.8).
+	* t/comment12.sh: use $(...) instead of `...`.
+	* t/comments-escaped-in-var.sh: use AUTOMAKE_fails and grep
+	for expected warning message.
+	* t/list-of-tests.mk (handwritten_TESTS): add t/py-compile-files.sh.
+	* t/subdir-add2-pr46.sh (.NOTPARALLEL): add; showed up with
+	parallelized internal make. Seems unreproducible.
+
+2022-10-01  Karl Berry  <karl@freefriends.org>
+
+	more HACKING tweaks
+
+2022-10-01  Karl Berry  <karl@freefriends.org>
+
+	aclocal: protect against Perl undefined warnings.
+
+	* bin/aclocal.in (usage): check that envvars (ACLOCAL_AUTOMAKE_DIR,
+	ACLOCAL_PATH) are defined before printing values.
+	* HACKING: describe running scripts from checkout, et al.
+
+2022-09-28  Karl Berry  <karl@freefriends.org>
+
+	doc: rearrange NEWS.
+
+	* NEWS: reclassify bugs vs. features.
+
+2022-09-28  Zack Weinberg  <zackw@panix.com>
+
+	python: better Python compilation portability.
+
+	This change is per automake thread:
+	https://lists.gnu.org/archive/html/automake/2022-09/msg00002.html
+
+	* lib/py-compile: Test directly for availability of
+	importlib.util.cache_from_source.  Untangle logic for when
+	to generate -O and -OO bytecode.  Reformat embedded Python fragments.
+
+2022-09-28  Karl Berry  <karl@freefriends.org>
+
+	forgot NEWS update
+
+2022-09-28  Zack Weinberg  <zackw@panix.com>
+
+	dist: ignore "silly rename" files from nfs/afs/smb.
+
+	This change is per automake thread:
+	https://lists.gnu.org/archive/html/automake/2022-09/msg00002.html
+
+	* lib/am/distdir.am (distcleancheck_listfiles): filter "silly rename"
+	files (.nfs* .smb* .__afs*), unavoidably created by deleting files
+	that are still open in some process on network file systems.
+
+2022-09-27  Richard Hopkins  <emacs@unbit.co.uk>
+
+	automake: do not use -Q with emacs invocations.
+
+	This change is for https://bugs.gnu.org/58102.
+	(By the way, the previous two commits were for bugs
+	58026 (silent .elc compilation) and
+	58025 (load bytecomp), respectively, but I forgot to mention them.)
+
+	* m4/lispdir.m4 (AM_PATH_LISPDIR): omit -Q option.
+	Also (from karl), use -no-site-file (one hyphen) for consistency
+	with the other options.
+	* NEWS: mention this.
+	* doc/automake.texi (Hard-Coded Install Paths): likewise.
+
+2022-09-26  Richard Hopkins  <emacs@unbit.co.uk>
+
+	automake: load -l bytecomp for Emacs.
+
+	* lib/am/lisp.am (.el.elc): Require the bytecomp library so
+	byte-compile-dest-file-function can be used when available.
+
+2022-09-26  Richard Hopkins  <emacs@unbit.co.uk>
+
+	automake: silent make output for Emacs byte compilation.
+
+	* lib/am/lisp.am: Use $(AM_V_GEN) in .el.elc rule.
+	* NEWS: mention this.
+	* THANKS: add new contributor.
+
+2022-09-18  Karl Berry  <karl@freefriends.org>
+
+	doc: typo in depcomp.
+
+	* lib/depcomp: obsosete -> obsolete. Report from anonymous.
+
+2022-07-25  Alexander Neumann  <neumann@imt.uni-luebeck.de>
+
+	compile: look for clang-cl.
+
+	* lib/compile: check for clang-cl, calling func_cl_wrapper.
+	* THANKS: add new contributor.
+
+2022-05-23  Jim Meyering  <meyering@fb.com>
+
+	fix: autoreconf fails due to .m4 files added but not installed
+
+	* m4/local.mk (dist_automake_ac_DATA): Add both rmf.m4 and xargsn.m4.
+	Building grep from "make maintainer-clean" state, failed like this:
+	  configure.ac:41: warning: _AM_PROG_RM_F is m4_require'd but not\
+	    m4_defun'd
+	  configure.ac:41: warning: _AM_PROG_XARGS_N is m4_require'd but not\
+	    m4_defun'd
+	  configure:5058: error: possibly undefined macro: _AM_PROG_RM_F
+	  configure:5059: error: possibly undefined macro: _AM_PROG_XARGS_N
+
+2022-05-23  Jan Engelhardt  <jengelh@inai.de>
+
+	deps: create empty file instead of dummy file.
+
+	This change is per an automake thread, see both before and after:
+	https://lists.gnu.org/archive/html/automake/2022-05/msg00006.html
+
+	* lib/am/depend.am ($(am__depfiles_remade)): create empty files
+	for dependencies instead of files with a line '# dummy'. Turns out
+	this is noticeably faster.
+	* THANKS: update Jan's email address.
+	* NEWS: mention this.
+
+2022-03-12  Mike Frysinger  <vapier@gentoo.org>
+
+	doc: refer to automake manual in all man pages
+
+	Fixes automake bug https://bugs.gnu.org/54363.
+
+	There is no "aclocal" manual as it's all integrated into the automake
+	manual, so have all the help2man calls force automake as the manual.
+
+	* doc/local.mk: Use --info-page=automake for man pages.
+
+2022-03-05  Mike Frysinger  <vapier@gentoo.org>
+
+	automake: fall back gracefully when texinfo inputs don't exist
+
+	Fixes automake bug https://bugs.gnu.org/54063.
+
+	The function scanning for @setfilename will fall back to a default
+	value if the input doesn't have one defined.  But we need to handle
+	the case where the file doesn't even exist before falling back.
+
+	* bin/automake.in: Scan /dev/null for @setfilename if input doesn't exist.
+	* t/list-of-tests.mk: Add txinfo-no-setfilename-no-inputs.sh.
+	* t/txinfo-no-setfilename-no-inputs.sh: New test.
+
+2022-03-05  Mike Frysinger  <vapier@gentoo.org>
+
+	m4: handle id failures when checking ustar support
+
+	Fixes automake bug https://bugs.gnu.org/20713.
+
+	If `id` fails, display a specific warning message to the user.
+
+	* m4/tar.m4: Check $am_uid & $am_gid if they're unknown.
+
+2022-02-27  Mike Frysinger  <vapier@gentoo.org>
+
+	m4: rework silent-rules macros to avoid double expansion
+
+	Fixes automake bug https://bugs.gnu.org/32868.
+
+	The AM_SILENT_RULES macro defines all the silent-rules related setup.
+	It's also called by users to change the default verbosity level.  This
+	leads to a quirk where automake calls it, expands the full context,
+	and then users call it, and it's fully expanded again.
+
+	Instead, let's rename AM_SILENT_RULES to _AM_SILENT_RULES and move the
+	initialization logic to late in the configure stage.  This allows the
+	user-centric AM_SILENT_RULES call to expand into a single line to set
+	the default verbosity.
+
+	* m4/init.m4: Switch to _AM_SILENT_RULES.
+	* m4/silent.m4: Rename AM_SILENT_RULES to _AM_SILENT_RULES.  Delay
+	evaluation of AM_SILENT_RULES to the end.  Define new AM_SILENT_RULES to
+	set default rules verbosity.
+	* t/silent-defaults.sh: New tests.
+	* t/list-of-tests.mk: Add t/silent-defaults.sh.
+
+2022-02-23  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: make silent-custom regex a little more robust
+
+	Fixes automake bug https://bugs.gnu.org/32800.
+
+	Have the regex match the entire path with word boundaries on both
+	sides.  This should reduce false positives when the full cwd happens
+	to match parent directories.
+
+	* t/silent-custom.sh: Update the header output regex.
+
+2022-02-23  Mike Frysinger  <vapier@gentoo.org>
+
+	py-compile: fix optimized compiling for Python 3.5+
+
+	Fixes automake bug https://bugs.gnu.org/38043.
+
+	Split the optimized compilation logic into a new section.  This avoids
+	trying to support multiple versions of major versions in a single script
+	as it gets harder to verify new changes don't break old versions as time
+	goes on.
+
+	Now for Python 3.5+, compile with -O0 (which is "higher" than -O).
+
+	* NEWS: Mention fix.
+	* THANKS: Add Michal Górny.
+	* lib/py-compile: Add new section for compiling Python 3.5+.
+
+2022-02-23  Mike Frysinger  <vapier@gentoo.org>
+
+	manual: mention LT_INIT
+
+	The AC_PROG_LIBTOOL macro name is the old/deprecated one, so include
+	LT_INIT here too to avoid confusing people who have switched.
+
+	* doc/automake.texi: Add LT_INIT after AC_PROG_LIBTOOL.
+
+2022-02-23  Mike Frysinger  <vapier@gentoo.org>
+
+	automake: allow required files to be in subdirs
+
+	Fixes automake bug https://bugs.gnu.org/20300.
+
+	The internal method for caching path lookups expects the $filename to
+	only be a filename.  If it's actually a subdir/file itself, then the
+	cache logic gets confused, and it never matches.  This manifests as
+	AC_REQUIRE_AUX_FILE(subdir/file) claiming that the subdir/file path
+	doesn't exist even when it does.
+
+	Before we process any required files, since we already construct the
+	full path locally, reset the dir & file inputs to the final values.
+
+	* bin/automake.in: Split dir & file name back out from the constructed
+	required file path.
+	* t/auxdir-subsubdir.sh: New test.
+	* t/list-of-tests.mk: Add t/auxdir-subsubdir.sh.
+
+2022-02-23  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: fix yacc C++ tests with some C++ compilers
+
+	Fixes automake bug https://bugs.gnu.org/20031.
+
+	The C++ standard does not require symbols be placed into the global
+	namespace, just in the std namespace.  The GNU implementation will
+	place symbols in both.  For our specific code, we don't care either.
+
+	Unfortunately, it looks like generated flex code assumes that some
+	stdlib.h symbols (free, malloc, exit) are in the global namespace,
+	even when compiling for C++.  So when we include <cstdlib> but not
+	<stdlib.h>, we might not get the symbols in the global namespace.
+
+	We can workaround this by including stdlib.h in these tests without
+	invalidating the point of the tests in general.
+
+	* t/yacc-cxx.sh: Include stdlib.h.
+	* t/yacc-d-cxx.sh: Likewise.
+	* t/yacc-mix-c-cxx.sh: Likewise.
+
+2022-02-23  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: log autoconf & libtool version
+
+	Having these in the sysconf log can be helpful when triaging test
+	failures from users.
+
+	* t/get-sysconf.sh: Log autoconf & libtoolize version.
+
+2022-02-23  Mike Frysinger  <vapier@gentoo.org>
+
+	automake: support embedded \# in variable appends
+
+	Fixes automake bug https://bugs.gnu.org/7610.
+
+	Use of \# is not portable.  POSIX does not provide any way of retaining
+	the # marker in variables.  There is wide spread support for \# though
+	in GNU & BSD Make implementations.
+
+	Today, with plain variable assignments, Automake leaves the line alone:
+	  foo = blah\#blah
+	This will leave it to the implementation to decide what to do.  But if
+	you try to append to it, Automake follows POSIX and strips it:
+	  foo = blah\#blah
+	  foo += what
+	  -> foo = blah\ what
+
+	Instead, let's issue a portability warning whenever \# is used, even if
+	it isn't being appended, and do not strip the \# when appending.  Now:
+	  foo = blah\#blah
+	  foo += what
+	  -> warning: escaping \# comment markers is not portable
+	  -> foo = blah\#blah what
+
+	* NEWS: Mention change in \# handling.
+	* lib/Automake/VarDef.pm: Do not strip # if escaped.
+	* lib/Automake/Variable.pm: Warn if \# is used.
+	* t/comment12.sh: New test.
+	* t/comments-escaped-in-var.sh: New test.
+	* t/list-of-tests.mk: Add comment12.sh & comments-escaped-in-var.sh.
+
+2022-02-20  Mike Frysinger  <vapier@gentoo.org>
+
+	python: use xargs -n when uninstalling files
+
+	Fixes automake bug https://bugs.gnu.org/53340.
+
+	If the system has xargs, then utilize it to uninstall files to stay
+	within long command line limits.  If the system doesn't have xargs,
+	fall back to running the remove command one at a time.  Since every
+	reasonable system should have `xargs -n`, and POSIX requires it, the
+	fallback probably rarely gets used, so don't bother optimizing.
+
+	* lib/am/inst-vars.am: Use am__xargs_n to call rm -f on the files.
+	* lib/am/python.am: Drop am__base_list and for loop and let the
+	am__uninstall_files_from_dir break up the long command lines.
+	* m4/init.m4: Call _AM_PROG_XARGS_N.
+	* m4/xargsn.m4: New test for `xargs -n`.
+
+2022-02-20  Mike Frysinger  <vapier@gentoo.org>
+
+	rm: handle -f w/no arguments gracefully
+
+	Fixes automake bug https://bugs.gnu.org/10828.
+
+	Delete the configure check that would abort if `rm -f` does not work,
+	and delete the plans to make this a hard requirement in the future.
+
+	Instead, test to see if `rm -f` fails w/out arguments.  If it does,
+	define am__rm_f such that it always passes at least the "" argument
+	when deleting files.  If it doesn't fail, then we can omit the "".
+
+	Then go through lib/am/ and update places where we use the pattern
+	`test -z ... || rm -f ...` and replace with $(am__rm_f).
+
+	* NEWS: Mention support for `rm -f` w/out arguments.
+	* PLANS/rm-f-without-args.txt: Remove.
+	* lib/am/check.am: Use new $(am__rm_f) helper.
+	* lib/am/clean.am: Likewise.
+	* lib/am/header-vars.am: Likewise.
+	* lib/am/inst-vars.am: Likewise.
+	* lib/am/libs.am: Likewise.
+	* lib/am/ltlib.am: Likewise.
+	* lib/am/progs.am: Likewise.
+	* lib/am/texinfos.am: Likewise.
+	* m4/init.m4: Delete `rm -f` checks and call _AM_PROG_RM_F.
+	* m4/rmf.m4: Define new _AM_PROG_RM_F macro.
+	* t/rm-f-probe.sh: Update test.
+
+2022-02-20  Mike Frysinger  <vapier@gentoo.org>
+
+	NEWS: fix typo in fix-timestamp.sh script name
+
+	As pointed out by Eric Blake.
+
+	* NEWS: Fix typo.
+
+2022-02-15  Mike Frysinger  <vapier@gentoo.org>
+
+	python: fix exit status handling with uninstall
+
+	The st variable is set at the top of this shell script, and then here
+	is a pipeline where it tries to update it in the subshell.  But since
+	setting variables in a subshell doesn't propagate back up, it doesn't
+	actually work.  Have the final subshell in the pipeline manage its own
+	exit status and exit with that so that the final status of the pipeline
+	is the right value.
+
+	* lib/am/python.am: Fix final subshell exit status passing.
+
+2022-02-12  Mike Frysinger  <vapier@gentoo.org>
+
+	m4: speed up filesystem modification checks
+
+	The current code sleeps at least 1 second to make sure the generated
+	files are strictly newer than the source files.  It does this for a
+	few reasons: POSIX only guarantees that `sleep` accept integers, and
+	filesystems have a history (c.f. Windows) of bad timestamp resolution.
+
+	For the first part, we can easily probe sleep to see if it accepts a
+	decimal number with a fractional part -- just run `sleep 0.001`.
+
+	For the second part, we can create two files and then run sleep in a
+	loop to see when one is considered newer than the other.
+
+	For many projects, this 1 second delay is largely amortized by the
+	rest of the configure script.  Autoconf lends itself to being both
+	large & slow.  But in projects with many smallish configure scripts
+	with many cached vars, the time to rerun is dominated by this single
+	sleep call.  For example, building libgloss against a compiler with
+	many (60+) multilib configurations, we see:
+	Using sleep 1
+	$ time ./config.status
+	real    2m28.164s
+	user    0m33.651s
+	sys     0m9.083s
+	Using sleep 0.1
+	$ time ./config.status
+	real    0m39.569s
+	user    0m33.517s
+	sys     0m8.969s
+
+	And in case anyone wonders, going below 0.1s doesn't seem to make a
+	statistically significant difference, at least in this configuration.
+	It appears to be within "noise" limits.
+	Using sleep 0.001
+	$ time ./config.status
+	real    0m39.760s
+	user    0m33.342s
+	sys     0m9.080s
+
+	* NEWS: Mention updated timestamp checking.
+	* m4/sanity.m4: Determine whether `sleep` accepts fractional seconds.
+	Determine (roughly) the filesystem timestamp resolution.  Use this to
+	sleep less when waiting for generated file timestamps to update.
+
+2022-02-12  Mike Frysinger  <vapier@gentoo.org>
+
+	m4: cache build env sanity checks
+
+	When rerunning configure in an existing build dir, cache the previous
+	results about environment settings.  There should be no need to retest
+	these in a dir that has already been configured.
+
+	* m4/sanity.m4: Cache sanity results.
+
+2022-02-08  Mike Frysinger  <vapier@gentoo.org>
+
+	elisp: run emacs with --no-site-file
+
+	Fixes automake bug https://bugs.gnu.org/21547.
+
+	If users have interactive site file logic, the lispdir probing can
+	hang, as can the compilation of elisp files.  Use --no-site-file to
+	disable loading any of that possible user logic.
+
+	* NEWS: Note emacs --no-site-file change.
+	* doc/automake.texi: Run emacs with --no-site-file.
+	* lib/am/lisp.am: Likewise.
+	* m4/lispdir.m4: Likewise.
+
+2022-02-08  Mike Frysinger  <vapier@gentoo.org>
+
+	ar-lib: ignore -nologo option
+
+	We already invoke $AR with -NOLOGO all the time, so we can ignore the
+	option entirely if the user specifies it.
+
+	* lib/ar-lib: Ignore -NOLOGO.
+
+2022-02-08  Mathieu Lirzin  <mthl@gnu.org>
+
+	tests: do not assume AM_MAKEINFOHTMLFLAGS is used in non-html targets
+
+	Fixes automake bug https://bugs.gnu.org/30172.
+
+	Since AM_MAKEINFOHTMLFLAGS overrides AM_MAKEINFOFLAGS only for html
+	targets, make sure we restore the hacked up makefile before testing
+	the non-html formats.  This normally doesn't cause a problem for most
+	people, but if their tex install doesn't work correctly, texi2dvi will
+	fallback to running $MAKEINFO and using invalid flags in the process.
+
+	* THANKS: Add Mathieu Lirzin.
+	* t/txinfo-many-output-formats.sh: Restore Makefile.am after testing
+	html targets.
+	* t/txinfo-many-output-formats-vpath.sh: Likewise.
+
+2022-02-05  Mike Frysinger  <vapier@gentoo.org>
+
+	py-compile: fix display when compiling multiple files
+
+	The compilation steps print the filename as it runs, but forgets to add
+	a space after it, so they all get squashed together:
+	$ ./py-compile 1.py 2.py 3.py
+	Byte-compiling python modules...
+	1.py2.py.3.py
+
+	* lib/py-compile: Add missing write.
+
+2022-02-05  Mike Frysinger  <vapier@gentoo.org>
+
+	manual: document Python version support status
+
+	Clarify to users what versions of Python are supported and until when.
+	This will make it easier for us to decide what versions to support.
+
+	* doc/automake.texi: Add Supported Python versions section.
+
+2022-02-05  Mike Frysinger  <vapier@gentoo.org>
+
+	py-compile: drop support for Python 0.x & 1.x
+
+	Python 2.0 was released in 2000.  There's really no way for us to check
+	those old versions, so let's just drop them.  No one will miss them.
+
+	* NEWS: Note Python version support removal.
+	* lib/py-compile: Abort if major version 0 or 1 is found.
+	* t/py-compile-env.sh: Rework slightly to handle new version probing.
+
+2022-02-05  Mike Frysinger  <vapier@gentoo.org>
+
+	py-compile: handle filenames with whitespace
+
+	The list of files is put into a string and then split on whitespace.
+	Fix the way the list of files are passed to the compile script.
+
+	* lib/py-compile: Pass files as arguments, not as a string.
+	* t/py-compile-files.sh: New test.
+
+2022-02-05  Mike Frysinger  <vapier@gentoo.org>
+
+	py-compile: clean up usage info
+
+	Include the full summary of options in the output.
+
+	* lib/py-compile: Update usage output.
+	* t/py-compile-usage.sh: Update test to match new output.
+
+2022-01-31  Mike Frysinger  <vapier@gentoo.org>
+
+	maint: include versioned manual in update
+
+	When publishing the updated manual, include the versioned copy too,
+	and have their index.html link to the full version index.
+
+	* maintainer/maint.mk: Copy manual to manual/$(VERSION)/, and insert
+	index-full.html link into index.html.
+
+2022-01-31  Mike Frysinger  <vapier@gentoo.org>
+
+	AM_PROG_AR: require before AC_PROG_AR
+
+	The new autoconf AC_PROG_AR macro has similar logic to what we have in
+	AM_PROG_AR, but less than what we need (since autoconf doesn't support
+	the MS archiver), so make sure we are run before AC_PROG_AR.
+
+	* m4/ar-lib.m4: Call AC_BEFORE for AC_PROG_AR.
+
+2022-01-30  Mike Frysinger  <vapier@gentoo.org>
+
+	maint: Update files from upstream with 'make fetch'
+
+	* lib/config.guess: Update.
+	* lib/config.sub: Likewise.
+	* lib/gendocs.sh: Likewise.
+	* lib/gendocs_template: Likewise.
+	* lib/gitlog-to-changelog: Likewise.
+	* lib/gnupload: Likewise.
+	* lib/texinfo.tex: Likewise.
+	* lib/update-copyright: Likewise.
+
+2022-01-28  Mike Frysinger  <vapier@gentoo.org>
+
+	maint: only sync the manual subdir
+
+	This code only updates files under manual/, so no need to checkout the
+	entire site first.
+
+	* maintainer/maint.mk: Only checkout $(PACKAGE)/manual tree.
+
+2022-01-27  Mike Frysinger  <vapier@gentoo.org>
+
+	texi: define new AM_TEXI2FLAGS variable
+
+	To provide a bit more flexibility when invoking TEXI2DVI & TEXI2PDF,
+	and provide a bit of symmetry with .info & .html generation, provide
+	a AM_TEXI2FLAGS setting that is passed to all TEXI2xxx invocations.
+
+	* doc/automake.texi: Mention new AM_TEXI2FLAGS setting.
+	* lib/am/texibuild.am: Pass $(AM_TEXI2FLAGS) to TEXI2DVI & TEXI2PDF.
+	* NEWS: Mention AM_TEXI2FLAGS.
+	* t/txinfo-many-output-formats.sh: Check for AM_TEXI2FLAGS.
+
+2022-01-27  Mike Frysinger  <vapier@gentoo.org>
+
+	texi: pass automatic -I to dvi & pdf generation
+
+	Fixes automake bug https://bugs.gnu.org/23599.
+
+	When generating info/html pages, automake adds -I flags to source
+	dirs that contain the texi files, but it doesn't do this for dvi or
+	pdf formats.  Instead, automake has been relying on texi2dvi to use
+	makeinfo for expanding macros, and it hasn't done that by default in
+	a long time.
+
+	Since adding --expand to the texi2dvi call is undesirable (due to bad
+	and unpredictable BEHAVIOR), pass those automatic -I flags directly
+	to TEXI2DVI & TEXI2PDF so they work regardless of --expand behavior.
+
+	We have to keep the MAKEINFO= setting around as texi2dvi might itself
+	fall back to it if the version of tex is old or broken.
+
+	* bin/automake.in: Add comment about $makeinfoflags usage.
+	* doc/automake.texi: Mention automatic -I subdir flags.
+	* lib/am/texibuild.am: Pass %MAKEINFOFLAGS% to TEXI2DVI & TEXI2PDF.
+	* t/txinfo-subdir-pr343.sh: Check for -I subdir usage.
+
+2022-01-27  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: remove spurious +x bits
+
+	None of these files are (or can be) executed directly, so drop the
+	spurious +x permission bit.  None of the other tests do this either.
+
+	* t/built-sources-install-exec.sh: Remove +x bit.
+	* t/ccnoco-deps.sh: Likewise.
+	* t/ccnoco-lib.sh: Likewise.
+	* t/ccnoco-lt.sh: Likewise.
+	* t/perf/cond.sh: Likewise.
+	* t/perf/testsuite-recheck.sh: Likewise.
+	* t/perf/testsuite-summary.sh: Likewise.
+	* t/python-prefix.sh: Likewise.
+	* t/tags-lisp-space.sh: Likewise.
+	* t/test-extensions-empty.sh: Likewise.
+
+2022-01-27  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: add coverage for nobase_ and dist_ prefixes
+
+	From automake bug https://bugs.gnu.org/14245.
+
+	We have tests that check nobase_ and nodist_ interaction, but not
+	nobase_ and dist_.  We had a report against automake 1.12 that this
+	combo did not work.  It seems to work now, but lets include a test
+	to make sure we don't regress.
+
+	Based on Daiki Ueno's example, but fixed up to pass against master.
+
+	* t/list-of-tests.mk: Add t/nobase-dist.sh.
+	* t/nobase-dist.sh: New test.
+
+2022-01-26  Mike Frysinger  <vapier@gentoo.org>
+
+	python: add 3.10 - 3.15 to the version search list
+
+	Fixes automake bug https://bugs.gnu.org/53530.
+
+	Based on the cadence of Automake releases, add the current Python
+	release (3.10), the current Python development (3.11), and then 4
+	more versions on top of that.  It doesn't hurt to check for a few
+	extra versions here since this is the fallback logic when the main
+	`python` and `python3` programs aren't found.
+
+	* m4/python.m4: Add python3.10 - python3.15.
+	* NEWS: Mention new Python versions.
+
+2022-01-24  Mike Frysinger  <vapier@gentoo.org>
+
+	progs, libs: support _RANLIB overrides
+
+	Much like we have per-target support for _AR and _LINK, add an _RANLIB
+	override too.  This allows selection of specific ranlib tools in case
+	a non-standard archiver tool was forced.
+
+	* bin/automake.in: Check for _RANLIB per-target settings.
+	* doc/automake.texi: Document _RANLIB override.
+	* lib/am/library.am: Change $(RANLIB) to $(%XLIBRARY%_RANLIB).
+	* t/list-of-tests.mk: Add ranlib_override.sh.
+	* t/ranlib_override.sh: New test.
+	* NEWS: Mention new feature.
+
+2022-01-24  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: add _AR override coverage
+
+	There were no tests for per-target _AR settings, so add some.
+
+	* t/ar_override.sh: New test.
+	* t/list-of-tests.mk: Add ar_override.sh.
+
+2022-01-24  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: clear autotools env vars
+
+	Fixes automake bug https://bugs.gnu.org/16714.
+
+	The testsuite will try and retain these env vars when recursively
+	running itself, but doesn't distinguish between vars coming from
+	the env where the tests were launched.  This breaks if the user
+	happens to `export ACLOCAL=alocal` before `make check`.
+
+	This gets a little more confusing in that the Makefile appears to
+	export these already:
+	ACLOCAL = ".../automake/pre-inst-env" aclocal-1.16
+
+	In reality, while those are set in the make execution environment,
+	they aren't exported into the process environment, so children
+	(i.e. shell processes in make rules) don't have them set.  That's
+	why tests work for most people today.
+
+	However, if the user has first exported "ACLOCAL" in the parent
+	make environment (regardless of value), then make's value will
+	reset the process environment, and then that will leak into the
+	children.  That's why we see errors that look like the makefile
+	env vars are leaking for these people.
+
+	At any rate, the fix is to update the test harness to clear these
+	vars that the test suite relies upon, especially the ones that are
+	also set in the Makefiles.  That includes AUTOUPDATE even though
+	it currently isn't used inside any of the tests.
+
+	* t/local.mk: Add ACLOCAL, AUTOCONF, AUTOHEADER, AUTOMAKE, and
+	AUTOUPDATE to the env unset list.
+	* t/ax/runtest.in: Likewise.
+
+2022-01-23  Mike Frysinger  <vapier@gentoo.org>
+
+	aclocal: add m4 search path info to --help
+
+	Add a short summary to --help of the current paths that will be
+	searched.  Make sure to omit this from the man page when running
+	help2man since pre-inst-env specifically clears some and others
+	to the current build directory.
+
+	* bin/aclocal.in: Include m4 search paths in usage.
+	* doc/local.mk: Run help2man with AUTOMAKE_HELP2MAN=true.
+
+2022-01-23  Mike Frysinger  <vapier@gentoo.org>
+
+	tests: fix quoting in eval
+
+	We need to escape the quotes so eval sees them when expanding the
+	variable value, not when quoting the variable name itself.
+
+	* t/local.mk: Escape quotes to eval.
+
+2022-01-23  Karl Berry  <karl@freefriends.org>
+
+	doc: singular/plural agreement, since it's easy.
+
+	* HACKING: singular/plural agreement.
+	* t/README: likewise.
+
+2022-01-22  Mike Frysinger  <vapier@gentoo.org>
+
+	THANKS: fix sorting
+
+	* THANKS: Sort a bunch of names.
+
+2022-01-21  Zack Weinberg  <zackw@panix.com>
+
+	build: fix ChangeLog generation in external build directory
+
+	When gitlog-to-changelog is run in a build directory that is neither the same
+	as, nor a subdirectory of, the source directory, it needs a --srcdir option or
+	it will fail to generate the changelog.  For instance
+
+	$ git clone https://git.savannah.gnu.org/git/automake.git
+	…
+	$ (cd automake && ./bootstrap)
+	$ mkdir b-automake
+	$ cd b-automake
+	$ ../automake/configure
+	…
+	$ make dist
+	…
+	  GEN      ChangeLog
+	gitlog-to-changelog:../s-automake/.git-log-fix: unused entry: 22729165f6bb902daeb8a4d8e7cb06982390f327
+	gitlog-to-changelog:../s-automake/.git-log-fix: unused entry: 3b369e6bbe0fb6d7359398935706c87dd9375cb6
+	make2: *** ../automake/maintainer/maint.mk:48: ChangeLog Error 1
+
+	 * maintainer/maint.mk (gitlog_to_changelog_options): Add --srcdir option.
+
+2022-01-18  Mike Frysinger  <vapier@gentoo.org>
+
+	build: fix race in parallel builds
+
+	As reported by Hongxu Jia:
+	> The automake-$(APIVERSION) is a hardlink of automake, if it is
+	> created later than update_mans executing, there is a failure
+	> snip
+	> |: && mkdir -p doc && ./pre-inst-env /usr/bin/env perl ../automake-1.16.1/doc/help2man --output=doc/aclocal-1.16.1 aclocal-1.16
+	> |help2man: can't get `--help' info from aclocal-1.16
+	> |Try `--no-discard-stderr' if option outputs to stderr
+	> Makefile:3693: recipe for target 'doc/aclocal-1.16.1' failed
+	> snip
+	>
+	> The automake_script is required by update_mans and update_mans
+	> invokes automake-$(APIVERSION) rather than automake to generate
+	> doc, so we should assign `automake-$(APIVERSION)' to automake_script.
+	>
+	> The same reason to tweak aclocal_script.
+
+	However, rather than update the _script variables to point to the
+	hardlinked copies of the programs, we can have the help2man steps
+	run the existing scripts directly.  This makes the relationship a
+	bit more explicit and avoids implicit dependencies on names.
+
+	* doc/local.mk: Pass $(aclocal_script) and $(automake_script) to $(update_mans).
+	* THANKS: Add Hongxu Jia.
+
+2022-01-18  Pavel Raiskup  <praiskup@redhat.com>
+
+	lib: drop unused shell variables
+
+	Detected by ShellCheck.
+
+	* lib/depcomp: Drop never used $digits.
+	* lib/ylwrap: Drop --basedir and $basedir, seems like that was old
+	C&P error from 210797967a.
+
+2022-01-18  Mike Frysinger  <vapier@gentoo.org>
+
+	gitignore: drop redundant config.h.in~ rule
+
+	Since we're ignoring all *~ files, we don't need this explicit one.
+
+	* .gitignore: Delete config.h.in~ rule.
+
+2022-01-18  Matthew Leeds  <matthew.leeds@endlessm.com>
+
+	doc: use gender-neutral pronouns in t/README
+
+	* t/README: s/him/them/
+
+2022-01-18  Jim Meyering  <meyering@fb.com>
+
+	tests: fix py-compile-basedir.sh: missing "test"
+
+	Prompted by a patch from Thomas Deutschmann <whissi@gentoo.org>,
+	via https://lists.gnu.org/r/automake-patches/2022-01/msg00001.html:
+	commit v1.16.1-26-gb279a0d46 ("tests: in python tests, do not
+	require .pyo files (for python3)") was missing a `test` call.
+	Reported to Gentoo at https://bugs.gentoo.org/715040.
+	* t/py-compile-basedir.sh: Rather than just adding the missing
+	"test", rewrite using a case statement, to avoid some duplication.
+
+2022-01-12  Jim Meyering  <meyering@fb.com>
+
+	maint: make update-copyright
+
+2021-12-18  Bruno Haible  <bruno@clisp.org>
+
+	doc: %reldir% and %canon_reldir% do not expand to the empty string.
+
+	This change fixes https://bugs.gnu.org/52500.
+
+	* doc/automake.texi (Include): correct wrong text.
+	(Along the way, correct plain-text "Makefile" to "@file{Makefile}".)
+
+2021-12-12  Mike Frysinger  <vapier@gentoo.org>
+
+	configure: skip kcc on case-insensitive filesystems; add clang++.
+
+	This change fixes https://bugs.gnu.org/21336.
+
+	* configure.ac: Skip KCC check on case-insensitive filesystems; on
+	macOS 10.10 and later, a kerberos tool named "kcc" is installed.
+	Add clang++ to the C++ search list, as with current autoconf.
+
+2021-12-12  Mike Frysinger  <vapier@gentoo.org>
+
+	maint: update .gitignore.
+
+	* .gitignore: ignore *~ .# and (from Zack Weinberg, autosave files)
+	.*.swop \#*#, closer to matching Autoconf.
+	https://lists.gnu.org/archive/html/automake-patches/2021-12/msg00005.html
+	https://lists.gnu.org/archive/html/automake-patches/2021-12/msg00010.html
+
+2021-12-12  Mike Frysinger  <vapier@gentoo.org>
+
+	m4: replace AC_DIAGNOSE with m4_warn
+
+	AC_DIAGNOSE was marked obsolete with autoconf-2.62 in 2008.
+
+	* m4/obsolete.m4: Change AC_DIAGNOSE to m4_warn.
+
+2021-11-27  Mike Frysinger  <vapier@gentoo.org>
+
+	dejagnu: add support for silent builds with site.exp.
+
+	* lib/am/dejagnu.am (site.exp): Use $(AM_V_GEN) and merge all
+	independent shell calls into one.
+
+2021-11-04  Karl Berry  <karl@freefriends.org>
+
+	doc: rearrange Multiple Outputs node.
+
+	This change fixes https://bugs.gnu.org/48188.
+
+	* doc/automake.texi (Multiple Outputs): move GNU pattern rule
+	approach to the front, since it is probably best if GNU make
+	can be assumed.  Suggestion from Frank Heckenbach.
+	Also, remove one of the examples that did not work, per Paul Smith.
+
+2021-11-02  Mike Frysinger  <vapier@gentoo.org>
+
+	config headers: add support for silent builds
+
+	* lib/am/remake-hdr.am (%STAMP%): Use $(AM_V_at) and $(AM_V_GEN).
+	(%CONFIG_HIN%): Likewise.
+
+2021-11-01  Karl Berry  <karl@freefriends.org>
+
+	doc: correct @node placement for new subsubsection.
+
+	This change addresses https://bugs.gnu.org/51532.
+
+	* doc/automake.texi (Linking Multiple Yacc Parsers): unfortunately
+	I misplaced the @node after the @subsection; correct that.
+
+2021-10-03  Jim Meyering  <meyering@fb.com>
+
+	maint: Post-release administrivia
+
+	* configure.ac (AC_INIT): Bump version number to 1.16i.
+	* m4/amversion.m4: Likewise (auto-updated by "make bootstrap").
+
 2021-10-03  Jim Meyering  <meyering@fb.com>
 
 	version 1.16.5

_service:tar_scm:automake-1.16.5.tar.xz/GNUmakefile -> _service:tar_scm:automake-1.17.tar.xz/GNUmakefile Changed

_service:tar_scm:automake-1.16.5.tar.xz/HACKING -> _service:tar_scm:automake-1.17.tar.xz/HACKING Changed

@@ -3,15 +3,15 @@
 
 * This file attempts to describe the conventions to use when hacking automake.
 
-* After git checkout from Savannah, can do initial build with, e.g.:
-  $ ./bootstrap && ./configure --prefix=/tmp/amdev && make
+* After git checkout from Savannah, you can do an initial build with, e.g.:
+    ./bootstrap && ./configure --prefix=/tmp/amdev && make
 
 ============================================================================
 = Administrivia
 
 * The correct response to most actual bugs is to write a new test case
-  which demonstrates the bug.  Then fix the bug, re-run the test suite,
-  and check everything in.  Run the test suite in parallel.
+  which demonstrates the bug.  Then fix the bug, rerun the test suite,
+  and check everything in.  Run the test suite in parallel or it takes ages.
 
 * If you incorporate a change from somebody on the net:
   - First, if it is not a tiny change, you must make sure they have
@@ -24,23 +24,33 @@
   the short url form, like https://bugs.gnu.org/1234.  See section below
   about commit messages.
 
-* If somebody reports a new bug, mention their name in the commit message
-  that fixes or exposes the bug, and add a line for them in THANKS.
+* If a person or people report a new bug, mention their name(s) in the
+  commit message that fixes or exposes the bug, and add a line for them
+  in THANKS.
 
 * When documenting a non-trivial idiom or example in the manual, be
   sure to add a test case for it, and to reference such test case from
   a proper Texinfo comment.
 
-* Some files in the automake package are not owned by automake (many by
-  gnulib, https://gnu.org/s/gnulib); these files are listed in the
-  $(FETCHFILES) variable in Makefile.am.  They should never be edited
-  here.  All but one of them can be updated from respective upstreams
-  with "make fetch" (this should be done especially before releases).
-  The only exception is 'lib/COPYING' (from FSF), which should be
-  updated by hand whenever the GPL gets updated (which shouldn't happen
-  that often anyway :-)
-
-* All changes that are not trivial bug fixes must be mentioned in NEWS.
+* Some files in the automake package are not owned by automake (many
+  by gnulib, https://gnu.org/s/gnulib); these files are listed in the
+  $(FETCHFILES) variable in maintainer/maint.mk.  They should never be
+  edited here.  All but two of them can be updated from respective
+  upstreams with "make fetch" (this should be done especially before
+  releases). The only exceptions are help2man (install the current
+  version and copy in by hand) and 'lib/COPYING' (from FSF), which
+  should be updated by hand whenever the GPL gets updated (which
+  shouldn't happen that often anyway :-).
+
+  Conversely, automake holds the master copy of a number of files that
+  are copied into other projects, such as install-sh, mdate-sh,
+  Channels.pm and ChannelDefs.pm, and plenty more; grep for bug-automake
+  in lib/* for most of the scripts, and see <gnulib>/config/srclist.txt
+  and <autoconf>/build-aux/fetch.pl for lists of such files on two
+  notable receiving ends. Do your best not to break them.
+
+* All changes from the last release that are not trivial bug fixes should
+  be mentioned in NEWS.
 
 * Changes which are potentially controversial, require a non-trivial
   plan, or must be implemented gradually with a roadmap spanning several
@@ -62,12 +72,21 @@
   can be automatically fetched using the GNU Guix package manager with the
   following command:
 
-  $ guix environment automake --ad-hoc \
+    guix environment automake --ad-hoc \
       gettext help2man texinfo libtool flex bison dejagnu zip icedtea \
       python gcc-toolchain gfortran pkg-config vala
 
   For other environments, you'll need to install the equivalent.
 
+* To run the bin/automake or bin/aclocal scripts in a checkout, it is
+  necessary to set PERL5LIB, as in:
+     am=/path/to/automake/checkout
+     env PERL5LIB=$am/lib $am/bin/automake --help
+     env PERL5LIB=$am/lib $am/bin/aclocal --help
+
+* If you need to test different Python versions, pyenv is probably the
+  most convenient way at this writing. https://github.com/pyenv
+
 ============================================================================
 = Naming
 
@@ -80,7 +99,7 @@
   We used to use '_am_' as the prefix for an internal AC_SUBSTs.
   However, it turns out that NEWS-OS 4.2R complains if a Makefile
   variable begins with the underscore character.  Yay for them.
-  I changed the target naming convention just to be safe.
+  We changed the target naming convention just to be safe.
 
 * If you'd like to read some general background on automake and the
   other GNU autotools, you might try this not-too-long web page (not
@@ -99,7 +118,7 @@
 
 * Never use basename or dirname.  Instead, use sed.
 
-* Do not use 'cd' within back-quotes, use '$(am__cd)' instead.
+* Do not use 'cd' within backquotes, use '$(am__cd)' instead.
   Otherwise the directory name may be printed, depending on CDPATH.
   More generally, do not ever use plain 'cd' together with a relative
   directory that does not start with a dot, or you might end up in one
@@ -114,7 +133,7 @@
   nothing is to be actually installed.  See automake bug#11030.
 
 ============================================================================
-= Editing automake.in and aclocal.in
+= Editing conventions
 
 * Indent using GNU style.  For historical reasons, the perl code
   contains portions indented using Larry Wall's style (perl-mode's
@@ -122,7 +141,19 @@
   default).  Write new code using GNU style.
 
 * Don't use & for function calls, unless really required.
-  The use of & prevents prototypes from being checked.
+  The use of & prevents prototypes from being checked; it's also
+  uncommon in modern Perl code.
+  (Perl prototypes are unlike function prototypes in other
+   languages, so understand what they do.)
+
+* For automake.texi:
+  - After and during editing, run make info for error checking, and make pdf
+    to catch TeX-only errors.
+  - After adding a new node, you can update the @detailmenu with 
+    M-x texinfo-master-menu (not tested with current Emacs releases, but
+    hopefully it still works).
+  - You'll probably have already added it to the higher-level menu under
+    which the new node was added, since that's necessary to run "make info".
 
 ============================================================================
 = Automake versioning and compatibility scheme
@@ -159,15 +190,15 @@
   nor contain any potentially destabilizing refactoring or sweeping change,
   nor introduce new features whose implementation might be liable to cause
   bugs or regressions in existing code.  However, it might be acceptable to
-  introduce very limited and localized backward-incompatibilities, *only*
+  introduce very limited and localized backward-incompatibility, *only*
   if that is necessary to fix non-trivial bugs, address serious performance
   issues, or greatly enhance usability.  But please, do this sparsely and
   rarely!
 
-* Major releases can introduce backward-incompatibilities (albeit such
-  incompatibilities should be announced well in advance, and a smooth
+* Major releases can introduce backward incompatibility (albeit such
+  incompatibility should be announced well in advance, and a smooth
   transition plan prepared for them), and try more risky and daring
-  refactorings and code cleanups.  Still, backward compatibilities are
+  refactorings and code cleanups.  Still, backward incompatibility is
   extremely undesirable and should be avoided at all costs.
 
 * For more information, refer to the extensive discussion associated
@@ -180,14 +211,23 @@
   use the 'bootstrap' script.  It uses the code from the source
   tree, so the resulting files (aclocal.m4 and Makefile.in) should
   be the same as you would get if you install this version of
-  automake and use it to generate those files.  Be sure to have the
-  latest stable version of Autoconf installed and available early
-  in your PATH. To get a faithful and correct rebuild, run:
+  automake and use it to generate those files.
+
+* To get a faithful and correct rebuild, run:
     ./bootstrap && ./config.status --recheck && make clean all
-  (per https://bugs.gnu.org/11347)
 
-* The Automake git tree currently carries three basic branches: 'master',
-  'next' and 'maint'.
+* Usually, it is best to run against the latest stable versions of
+  Autoconf, Libtool, etc., since that is what most users will
+  do. However, sometimes it may be necessary to use the development
+  versions due to bugs fixed, etc. Whatever is first in PATH wins.
+  (Some background: https://bugs.gnu.org/11347)
+
+* The Automake git tree currently carries three basic branches:
+  'master', 'next' and 'maint'.  In practice, for quite a few years now,
+  as of this writing in 2023, we have been using only the master branch,
+  due to lack of time and desire to deal with anything but fixing bugs.
+  The branch information in the items below and above should thus be
+  taken with a large dose of salt.
 
 * The 'master' branch is where the development of the next release
   takes place.  It should be kept in a stable, almost-releasable state,
@@ -253,7 +293,7 @@
   to follow.  See the further points below for clarifications and minor
   corrections.
 
-      topic: brief description (this is the "summary line")
+      topic: brief description (this is the "summary line").
 
       <reference to relevant bugs, if any>
 
@@ -277,6 +317,12 @@
 
       <detailed list of touched files>
 
+* To choose the topic label, please review the previous commits in the
+  git log or the ChangeLog file from a release tarball. There are no
+  hard-and-fast rules; the aim is a usable description. So script
+  names, Makefile targets, and more are all viable. Some examples:
+  aclocal automake build cosmetics doc maint python release test ylwrap
+
 * The <detailed list of touched files> should usually be provided (but
   for short or trivial changes), and should follow the GNU guidelines
   for ChangeLog entries (described explicitly in the GNU Coding
@@ -288,7 +334,7 @@
     * t/foo.sh: New test.
     * t/list-of-tests.mk (handwritten_TESTS): Add it.
     * doc/automake.texi (Some Node): Document it.
-    * NEWS: mention it.
+    * NEWS: Mention it.
 
 * If your commit fixes an automake bug registered in the tracker (say
   numbered 1234), you should put the following line after the summary
@@ -323,52 +369,54 @@
 
 * See file 't/README' for more information.
 
-* Use "make check" and "make maintainer-check" liberally.
+* Use "make check" and "make maintainer-check" liberally.  It is often
+  useful to set VERBOSE=1 for more reporting on what is being done.
 
 * Export the 'keep_testdirs' environment variable to "yes" to keep
-  test directories for successful tests also.
+  *.dir test directories for successful tests also.
 
-* Use perl coverage information to ensure your new code is thoroughly
+* Use Perl coverage information to ensure your new code is thoroughly
   tested by your new tests.
 
 * To run the tests, you should install expect, shar, language compilers,
   gettext macros.  Anything you don't install won't be tested.  The test
   suite will report on tests skipped due to software not available.
 
-* You can run a single test, with, e.g.,
+* Run the test suite in parallel (e.g., "make -j12 check"), both so it
+  doesn't take forever and because that is what most users will do.  You
+  can also parallelize the makes that run inside each test with, e.g.:
+    make check AM_TESTSUITE_MAKE="make -j$(( 1*$(nproc) + 1 ))"
+  If you like, try different levels of parallelization to see what
+  runs the fastest on your machine.  We'll use -j12 in our examples;
+  adjust as needed.
 
-    make check TESTS='t/aclocal-acdir.sh'
+* To summarize, here is a typical make check invocation:
+    make -j12 VERBOSE=1 check keep_testdirs=yes
 
+* Then check t/test-suite.log for the overall results.  The directory
+  t/TESTNAME.dir is where the work will be left, if the test fails.
+
+* You can run a single test, with, e.g.,
+    make check TESTS='t/aclocal-acdir.sh'
   where t/aclocal-acdir.sh can be any t/*.sh test, including a new one
   you are writing.  You may want to add --no-print-dir to silence GNU
   make about the many cd commands, and/or env VERBOSE=1 to get more
   information about what make is running.
 
-* Then check t/test-suite.log for the overall results.  The directory
-  t/TESTNAME.dir is where the work will be left, if the test fails.
-  During development of a new test, you want to end it with "exit 33"
-  (or whatever) to make it fail even when it would succeed, so you can
-  inspect the test directory to be sure things worked as expected.
-
-  You can also set keep_testdirs=yes on the command line to keep the
-  *.dir results.
-
-* Run the test suite in parallel (e.g., "make -j12 check"), both so it
-  doesn't take forever and because that is what most users will do.  You
-  can also parallelize the makes that run inside each test with, e.g.:
-
-    make check AM_TESTSUITE_MAKE="make -j$(( 1*$(nproc) + 1 ))"
-
-  If you like, try different levels of parallelization to see what
-  runs the fastest on your machine.
+* Sometimes you may want to see when each test starts running, not only
+  when they complete.  This can be done by setting TESTS_ENVIRONMENT:
+    make -j12 VERBOSE=1 TESTS_ENVIRONMENT='echo RUNNING: "$$f";' check
 
 * Run "make maintainer-check" before commit.  Watch out for trailing spaces.
+  Probably useful to run it more verbosely:
+    make AM_V_GEN= AM_V_at= VERBOSE=1 maintainer-check
 
-* It is good to run also run "make -j12 distcheck" before pushing a
-  commit since that exercises yet more testing, after "make -j12 check"
-  succeeds.
+* After "make -j12 check" succeeds. Run "make -j12 distcheck" before
+  pushing a commit, since that exercises yet more of the code.
 
-* Use make V=1 to un-silence (some) of what make does.
+* To unsilence Automake's "pretty" output for debugging, see the
+  "Unsilencing Automake" node in the manual. In short: run make --debug=p.
+  For the Automake test suite in particular, add VERBOSE=1.
 
 * To set up a new test, first write the test file in t/good-name.sh.
   Choose a name that fits with existing ones, as best you can devise.
@@ -383,21 +431,60 @@
   - You can run the new test on its own with
     make check TESTS='t/good-name.sh'
 
+  - During development of a new test, it can be useful to end it with
+  "exit 33" (or any random value) to force it to fail even when it would
+  otherwise succeed, so you can inspect the test.dir/test.log and other
+  test.dir/* files to be sure things worked as expected.
+
   - At some point before releasing, add the test to the appropriate
   variable in t/list-of-tests.mk, most likely the (alphabetical)
   handwritten_TESTS.
 
+* Some hints for debugging test failures or trying to understand the
+  (complex) test infrastructure.
+
+  - The t/ax/ dir contains most of the test infrastructure files.
+
+  - You may want to try a simple test just to exercise the setup;
+  t/amassign.sh is such a test. For a simple test that runs automake
+  twice (sometimes useful in finding concurrency failures), try
+  t/nodef.sh.
+
+  - To trace the (complex) test initialization code, change the set -e
+  to set -ex (or whatever you wish) in t/ax/test-init.sh.
+  Automake itself enables -x for the *.log and test-suite.log files,
+  in am_test_setup in t/ax/test-lib.sh. You may want to change to -vx.
+
+  - If you want to run the individual commands of a test one by one in a
+  shell, you have to reproduce the test environment. Start a subshell and:
+    PATH=$am/bin:$am/t/ax:$PATH # where $am is your automake source checkout
+    set +u          # if needed; automake cannot handle this "nounset" option
+    . test-init.sh  # beginning of test
+  Then each command you type will be executed in the test environment,
+  including -x being enabled. Each test prints the PATH value at the beginning.
+
+  - If you need to debug a test which fails under installcheck, you need
+  to invoke make with am_running_installcheck=yes, as is done by the
+  installcheck-testsuite target in t/local.mk.
+
+  - If you want to see the (complex shell) commands that make is
+  running, despite all of Automake's attempt at silence, run (GNU)
+    make --debug=p ... other make args ...
+
 ============================================================================
 = Bug tracker
 
 * Automake uses the debbugs instance at https://bugs.gnu.org.  Email
   from the tracker is sent to bug-automake@gnu.org, and vice versa.
-  (https://gnu.org/s/automake for all the mailing lists; you should subscribe.)
+  Ditto automake-patches@gnu.org. (See
+  https://gnu.org/s/automake for all the mailing lists; if you're
+  working on Automake, please subscribe.)
 
-* To see all open bugs (and recently closed ones):
+* To see all open bugs resp. patches (and recently closed ones):
     https://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=automake
+    https://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=automake-patches
 
-* For a full search form, initialized to show bugs tagged confirmed:
+* For a full search form, initialized to show only bugs tagged confirmed:
     https://debbugs.gnu.org/cgi/pkgreport.cgi?package=automake;include=tags%3Aconfirmed
 
 * We use the "confirmed" tag to mean bugs that have been reviewed, are
@@ -407,7 +494,7 @@
 * To download the so-called maintainer mbox for a bug, say 12345:
     https://debbugs.gnu.org/cgi/bugreport.cgi?bug=12345;mbox=yes;mboxmaint=yes
   Only the maintainer mbox consistently has the bug# prefix on Subject:
-  lines, so it is generally the most usable.
+  lines, so it is the most usable, as far as we know.
 
 * To close a bug, you can mail (or bcc) to 12345-done@debbugs.gnu.org.
   It's best to do this with a note saying that the bug is being closed
@@ -417,45 +504,75 @@
   control@debbugs.gnu.org with a one-line body:
     tags 12345 + help confirmed
 
+* To merge bugs 12345 and 56789, mail to
+  control@debbugs.gnu.org with a one-line body:
+    merge 12345 56789
+
 * In general, all bug operations are done by mail.  Reference information:
     https://debbugs.gnu.org/server-control.html # dev info
 
 ============================================================================
 = Release procedure
 
-* The steps outlined here are meant to be followed for alpha and stable
-  releases as well.  Where differences are expected, they will be
-  explicitly described.
+* The steps outlined here are meant to be followed for all releases,
+  whether stable, beta, alpha, or other.  Where differences are
+  expected, they will be explicitly mentioned.
 
-* Fetch new versions of the files that are maintained by the FSF by
-  running "make fetch".  In case any file in the automake repository
-  has been updated, commit and re-run the testsuite.
+* Fetch new versions of the files that are maintained elsewhere by
+  running "make fetch".  help2man has to be updated separately.  If
+  any files in the automake repository get updated, commit them and
+  rerun the testsuite.
 
 * Ensure that the copyright notices of the distributed files are up to
-  date.  The maintainer-only target "update-copyright" can help with
-  this.
+  date.  The maintainer-only target "update-copyright" can help with this.
 
 * Check NEWS; in particular, ensure that all the relevant differences
-  with the last release are actually reported.
+  with the last release are included.
+
+* Update the AC_INIT version number in configure.ac.  Leading up to a release,
+  say 1.17, pretests should be numbered from 1.16.90. Even numbers
+  (1.16.90, 1.16.92, ...) should be the pretest releases; odd numbers
+  (1.16.91, 1.16.93, ...) should be only the development versions.
+  Leading up to a release 1.17.1, we would have 1.16.0.90, etc.
+  Before 1.17 (July 2024), we used suffixed letters for pretests,
+  as is traditional, but deficient sorting algorithms did not like that.
 
-* Update the version number in configure.ac.
-  (The idea is that every other alpha number will be a net release.
-  The repository will always have its own "odd" number so we can easily
-  distinguish net and repo versions.)
+* If making a minor or major release (1.x), also update APIVERSION
+  in configure.ac.
 
-* Run these commands, in this order:
+* Create an announcement message with "make announcement".  Edit the
+  generated 'announcement' file appropriately, in particularly filling
+  in by hand any "TODO" left in there.  It's useful to do this early,
+  because carefully writing the announcement can easily bring to light
+  things that still need to be worked on.
 
+* Run these commands, in this order (as mentioned, adjust -j as desired):
     make bootstrap
-    make check keep_testdirs=yes
+    make -j12 check keep_testdirs=yes
     make maintainer-check
-    make distcheck
-    make check-no-trailing-backslash-in-recipes
-    make check-cc-no-c-o
-
-  It is also advised to run "git clean -fdx" before invoking the
-  bootstrap, to ensure a really clean rebuild.  However, it must
-  be done carefully, because that command will remove *all* the
-  files that are not tracked by git!
+    make -j12 check-no-trailing-backslash-in-recipes
+    make -j12 check-cc-no-c-o
+    make -j12 distcheck                                # regular distcheck
+    make -j12 distcheck AM_TESTSUITE_MAKE="make -j12"  # parallelize makes
+
+  You can run "git clean -fdx" before invoking the bootstrap, to ensure
+  a completely clean rebuild.  However, it must be done carefully,
+  because that command will remove *all* the files that are not tracked
+  by git!  Run git status first to ensure all removals are ok.
+
+* Create additional info for the announcement with the announce-gen
+  script that is part of gnulib (it requires the release tarball):
+    pkg=automake
+    prever=1.16.92
+    newver=1.16.94
+    reltype=alpha # or beta or stable
+    host=`if test $reltype = stable; then echo ftp; else echo alpha; fi`
+    gpgkey=0x... #  gpg --fingerprint
+    $gnulib/build-aux/announce-gen --release-type=$reltype \
+      --package-name=$pkg --previous-version=$prever \
+      --current-version=$newver --gpg-key-id=$gpgkey \
+      --url-directory=https://$host.gnu.org/gnu/$pkg
+  and merge this with the just-written announcement file.
 
 * Run "make git-tag-release".
   This will run the maintainer checks, verify that the local git
@@ -464,6 +581,8 @@
   of $(VERSION)).
 
 * Run "make git-upload-release".
+  For pretest releases: "DEVEL_SNAPSHOT=1 make git-upload-release".
+
   This will first verify that you are releasing from a tagged version
   and that the local git repository and working tree are clean and
   up-to-date, and will then run "make dist" to create the tarballs,
@@ -471,53 +590,48 @@
   locations.  In case you need to sign with a non-default key, you can
   use "make GNUPLOADFLAGS='--user KEY' git-upload-release".
 
-* For stable releases you'll have to update the manuals at www.gnu.org.
+* For stable releases you also need to update the manuals on www.gnu.org.
 
-  - Generate manuals (with the help of the standard gendocs.sh script):
+  - Check links:
+       make html
+       make checklinkx # various perl prerequisites, see contrib/checklinkx
+    or use:
+      <https://validator.w3.org/checklink>
 
+  - Generate manuals (with the help of the standard gendocs.sh script):
        make web-manual
 
     The ready-to-be-uploaded manuals (in several formats) will be left
     in the 'doc/web-manuals' directory.
 
   - Commit the updated manuals to web CVS:
-
       make web-manual-update
 
     If your local username is different from your username at Savannah,
     you'll have to override the 'CVS_USER' make variable accordingly;
     for example:
-
       make web-manual-update CVS_USER=slattarini
 
-  - Check for link errors, fix them, recheck until convergence:
-    <http://validator.w3.org/checklink>
-
-* Create an announcement message with "make announcement".  Edit the
-  generated 'announcement' file appropriately, in particularly filling
-  in by hand any "TODO" left in there.
-
 * Update version number in configure.ac to next alpha number.
-  Re-run ./bootstrap and commit.
+  Rerun ./bootstrap and commit.
 
 * Don't forget to "git push" your changes so they appear in the public
   git tree.
 
 * Send the announcement generated in the earlier steps at least to
   <autotools-announce@gnu.org> and <automake@gnu.org>.  If the release
-  is a stable one, the announcement must also go to <info-gnu@gnu.org>;
+  is a stable one, the announcement also goes to <info-gnu@gnu.org>;
   if it is an alpha or beta release, announcement should be sent also
   to <platform-testers@gnu.org>, to maximize the possibility of early
-  testing on exotic or proprietary systems.  Finally, copy an abridged
+  testing on the widest variety of systems.  Finally, copy an abridged
   version of the announcement into the NEWS feed at:
   <https://savannah.gnu.org/projects/automake>.
-  Be sure to link a  version to the complete announcement (from
-  the version you sent to the automake list, as get archived on
+  Be sure to link a version to the complete announcement (from
+  the version you sent to the automake list, as archived at
   <https://lists.gnu.org/archive/html/automake/>).
 
------
-
-Copyright (C) 2003-2021 Free Software Foundation, Inc.
+---------
+Copyright (C) 2003-2024 Free Software Foundation, Inc.
 
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by

_service:tar_scm:automake-1.16.5.tar.xz/INSTALL -> _service:tar_scm:automake-1.17.tar.xz/INSTALL Changed

@@ -1,177 +1,177 @@
 Installation Instructions
 *************************
 
-   Copyright (C) 1994-1996, 1999-2002, 2004-2017, 2020-2021 Free
-Software Foundation, Inc.
-
-   Copying and distribution of this file, with or without modification,
-are permitted in any medium without royalty provided the copyright
-notice and this notice are preserved.  This file is offered as-is,
-without warranty of any kind.
-
 Basic Installation
 ==================
 
-   Briefly, the shell command './configure && make && make install'
-should configure, build, and install this package.  The following
-more-detailed instructions are generic; see the 'README' file for
-instructions specific to this package.  Some packages provide this
-'INSTALL' file but do not implement all of the features documented
-below.  The lack of an optional feature in a given package is not
-necessarily a bug.  More recommendations for GNU packages can be found
-in *note Makefile Conventions: (standards)Makefile Conventions.
-
-   The 'configure' shell script attempts to guess correct values for
+   The following shell commands:
+
+     test -f configure || ./bootstrap
+     ./configure
+     make
+     make install
+
+should configure, build, and install this package.  The first line,
+which bootstraps, is intended for developers; when building from
+distribution tarballs it does nothing and can be skipped.
+
+   The following more-detailed instructions are generic; see the
+‘README’ file for instructions specific to this package.  Some packages
+provide this ‘INSTALL’ file but do not implement all of the features
+documented below.  The lack of an optional feature in a given package is
+not necessarily a bug.  More recommendations for GNU packages can be
+found in the GNU Coding Standards.
+
+   Many packages have scripts meant for developers instead of ordinary
+builders, as they may use developer tools that are less commonly
+installed, or they may access the network, which has privacy
+implications.  If the ‘bootstrap’ shell script exists, it attempts to
+build the ‘configure’ shell script and related files, possibly using
+developer tools or the network.  Because the output of ‘bootstrap’ is
+system-independent, it is normally run by a package developer so that
+its output can be put into the distribution tarball and ordinary
+builders and users need not run ‘bootstrap’.  Some packages have
+commands like ‘./autopull.sh’ and ‘./autogen.sh’ that you can run
+instead of ‘./bootstrap’, for more fine-grained control over
+bootstrapping.
+
+   The ‘configure’ shell script attempts to guess correct values for
 various system-dependent variables used during compilation.  It uses
-those values to create a 'Makefile' in each directory of the package.
-It may also create one or more '.h' files containing system-dependent
-definitions.  Finally, it creates a shell script 'config.status' that
+those values to create a ‘Makefile’ in each directory of the package.
+It may also create one or more ‘.h’ files containing system-dependent
+definitions.  Finally, it creates a shell script ‘config.status’ that
 you can run in the future to recreate the current configuration, and a
-file 'config.log' containing compiler output (useful mainly for
-debugging 'configure').
+file ‘config.log’ containing output useful for debugging ‘configure’.
 
-   It can also use an optional file (typically called 'config.cache' and
-enabled with '--cache-file=config.cache' or simply '-C') that saves the
+   It can also use an optional file (typically called ‘config.cache’ and
+enabled with ‘--cache-file=config.cache’ or simply ‘-C’) that saves the
 results of its tests to speed up reconfiguring.  Caching is disabled by
 default to prevent problems with accidental use of stale cache files.
 
    If you need to do unusual things to compile the package, please try
-to figure out how 'configure' could check whether to do them, and mail
-diffs or instructions to the address given in the 'README' so they can
+to figure out how ‘configure’ could check whether to do them, and mail
+diffs or instructions to the address given in the ‘README’ so they can
 be considered for the next release.  If you are using the cache, and at
-some point 'config.cache' contains results you don't want to keep, you
+some point ‘config.cache’ contains results you don’t want to keep, you
 may remove or edit it.
 
-   The file 'configure.ac' (or 'configure.in') is used to create
-'configure' by a program called 'autoconf'.  You need 'configure.ac' if
-you want to change it or regenerate 'configure' using a newer version of
-'autoconf'.
+   The ‘autoconf’ program generates ‘configure’ from the file
+‘configure.ac’.  Normally you should edit ‘configure.ac’ instead of
+editing ‘configure’ directly.
 
    The simplest way to compile this package is:
 
-  1. 'cd' to the directory containing the package's source code and type
-     './configure' to configure the package for your system.
+  1. ‘cd’ to the directory containing the package’s source code.
+
+  2. If this is a developer checkout and file ‘configure’ does not yet
+     exist, type ‘./bootstrap’ to create it.  You may need special
+     developer tools and network access to bootstrap, and the network
+     access may have privacy implications.
 
-     Running 'configure' might take a while.  While running, it prints
-     some messages telling which features it is checking for.
+  3. Type ‘./configure’ to configure the package for your system.  This
+     might take a while.  While running, ‘configure’ prints messages
+     telling which features it is checking for.
 
-  2. Type 'make' to compile the package.
+  4. Type ‘make’ to compile the package.
 
-  3. Optionally, type 'make check' to run any self-tests that come with
+  5. Optionally, type ‘make check’ to run any self-tests that come with
      the package, generally using the just-built uninstalled binaries.
 
-  4. Type 'make install' to install the programs and any data files and
+  6. Type ‘make install’ to install the programs and any data files and
      documentation.  When installing into a prefix owned by root, it is
      recommended that the package be configured and built as a regular
-     user, and only the 'make install' phase executed with root
+     user, and only the ‘make install’ phase executed with root
      privileges.
 
-  5. Optionally, type 'make installcheck' to repeat any self-tests, but
+  7. Optionally, type ‘make installcheck’ to repeat any self-tests, but
      this time using the binaries in their final installed location.
      This target does not install anything.  Running this target as a
-     regular user, particularly if the prior 'make install' required
+     regular user, particularly if the prior ‘make install’ required
      root privileges, verifies that the installation completed
      correctly.
 
-  6. You can remove the program binaries and object files from the
-     source code directory by typing 'make clean'.  To also remove the
-     files that 'configure' created (so you can compile the package for
-     a different kind of computer), type 'make distclean'.  There is
-     also a 'make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
-  7. Often, you can also type 'make uninstall' to remove the installed
-     files again.  In practice, not all packages have tested that
-     uninstallation works correctly, even though it is required by the
-     GNU Coding Standards.
-
-  8. Some packages, particularly those that use Automake, provide 'make
-     distcheck', which can by used by developers to test that all other
-     targets like 'make install' and 'make uninstall' work correctly.
-     This target is generally not run by end users.
+  8. You can remove the program binaries and object files from the
+     source code directory by typing ‘make clean’.  To also remove the
+     files that ‘configure’ created (so you can compile the package for
+     a different kind of computer), type ‘make distclean’.  There is
+     also a ‘make maintainer-clean’ target, but that is intended mainly
+     for the package’s developers.  If you use it, you may have to
+     bootstrap again.
+
+  9. If the package follows the GNU Coding Standards, you can type ‘make
+     uninstall’ to remove the installed files.
 
 Compilers and Options
 =====================
 
    Some systems require unusual options for compilation or linking that
-the 'configure' script does not know about.  Run './configure --help'
+the ‘configure’ script does not know about.  Run ‘./configure --help’
 for details on some of the pertinent environment variables.
 
-   You can give 'configure' initial values for configuration parameters
+   You can give ‘configure’ initial values for configuration parameters
 by setting variables in the command line or in the environment.  Here is
 an example:
 
-     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+     ./configure CC=gcc CFLAGS=-g LIBS=-lposix
 
-   *Note Defining Variables::, for more details.
+   See “Defining Variables” for more details.
 
 Compiling For Multiple Architectures
 ====================================
 
    You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you can use GNU 'make'.  'cd' to the
-directory where you want the object files and executables to go and run
-the 'configure' script.  'configure' automatically checks for the source
-code in the directory that 'configure' is in and in '..'.  This is known
-as a "VPATH" build.
-
-   With a non-GNU 'make', it is safer to compile the package for one
-architecture at a time in the source code directory.  After you have
-installed the package for one architecture, use 'make distclean' before
-reconfiguring for another architecture.
-
-   On MacOS X 10.5 and later systems, you can create libraries and
-executables that work on multiple system types--known as "fat" or
-"universal" binaries--by specifying multiple '-arch' options to the
-compiler but only a single '-arch' option to the preprocessor.  Like
-this:
-
-     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-                 CPP="gcc -E" CXXCPP="g++ -E"
-
-   This is not guaranteed to produce working output in all cases, you
-may have to build one architecture at a time and combine the results
-using the 'lipo' tool if you have problems.
+same time, by placing the object files for each system in their own
+directory.  To do this, you can use GNU ‘make’.  ‘cd’ to the directory
+where you want the object files and executables to go and run the
+‘configure’ script.  ‘configure’ automatically checks for the source
+code in the directory that ‘configure’ is in and in ‘..’.  This is known
+as a “VPATH” build.
+
+   With a non-GNU ‘make’, it is safer to compile the package for one
+system at a time in the source code directory.  After you have installed
+the package for one system, use ‘make distclean’ before reconfiguring
+for another system.
+
+   Some platforms, notably macOS, support “fat” or “universal” binaries,
+where a single binary can execute on different architectures.  On these
+platforms you can configure and compile just once, with options specific
+to that platform.
 
 Installation Names
 ==================
 
-   By default, 'make install' installs the package's commands under
-'/usr/local/bin', include files under '/usr/local/include', etc.  You
-can specify an installation prefix other than '/usr/local' by giving
-'configure' the option '--prefix=PREFIX', where PREFIX must be an
+   By default, ‘make install’ installs the package’s commands under
+‘/usr/local/bin’, include files under ‘/usr/local/include’, etc.  You
+can specify an installation prefix other than ‘/usr/local’ by giving
+‘configure’ the option ‘--prefix=PREFIX’, where PREFIX must be an
 absolute file name.
 
    You can specify separate installation prefixes for
 architecture-specific files and architecture-independent files.  If you
-pass the option '--exec-prefix=PREFIX' to 'configure', the package uses
+pass the option ‘--exec-prefix=PREFIX’ to ‘configure’, the package uses
 PREFIX as the prefix for installing programs and libraries.
 Documentation and other data files still use the regular prefix.
 
    In addition, if you use an unusual directory layout you can give
-options like '--bindir=DIR' to specify different values for particular
-kinds of files.  Run 'configure --help' for a list of the directories
+options like ‘--bindir=DIR’ to specify different values for particular
+kinds of files.  Run ‘configure --help’ for a list of the directories
 you can set and what kinds of files go in them.  In general, the default
-for these options is expressed in terms of '${prefix}', so that
-specifying just '--prefix' will affect all of the other directory
+for these options is expressed in terms of ‘${prefix}’, so that
+specifying just ‘--prefix’ will affect all of the other directory
 specifications that were not explicitly provided.
 
    The most portable way to affect installation locations is to pass the
-correct locations to 'configure'; however, many packages provide one or
+correct locations to ‘configure’; however, many packages provide one or
 both of the following shortcuts of passing variable assignments to the
-'make install' command line to change installation locations without
+‘make install’ command line to change installation locations without
 having to reconfigure or recompile.
 
    The first method involves providing an override variable for each
-affected directory.  For example, 'make install
-prefix=/alternate/directory' will choose an alternate location for all
+affected directory.  For example, ‘make install
+prefix=/alternate/directory’ will choose an alternate location for all
 directory configuration variables that were expressed in terms of
-'${prefix}'.  Any directories that were specified during 'configure',
-but not in terms of '${prefix}', must each be overridden at install time
+‘${prefix}’.  Any directories that were specified during ‘configure’,
+but not in terms of ‘${prefix}’, must each be overridden at install time
 for the entire installation to be relocated.  The approach of makefile
 variable overrides for each directory variable is required by the GNU
 Coding Standards, and ideally causes no recompilation.  However, some
@@ -179,190 +179,187 @@
 that end up requiring recompilation when using this method, particularly
 noticeable in packages that use GNU Libtool.
 
-   The second method involves providing the 'DESTDIR' variable.  For
-example, 'make install DESTDIR=/alternate/directory' will prepend
-'/alternate/directory' before all installation names.  The approach of
-'DESTDIR' overrides is not required by the GNU Coding Standards, and
+   The second method involves providing the ‘DESTDIR’ variable.  For
+example, ‘make install DESTDIR=/alternate/directory’ will prepend
+‘/alternate/directory’ before all installation names.  The approach of
+‘DESTDIR’ overrides is not required by the GNU Coding Standards, and
 does not work on platforms that have drive letters.  On the other hand,
 it does better at avoiding recompilation issues, and works well even
-when some directory options were not specified in terms of '${prefix}'
-at 'configure' time.
+when some directory options were not specified in terms of ‘${prefix}’
+at ‘configure’ time.
 
 Optional Features
 =================
 
    If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving 'configure' the
-option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
+with an extra prefix or suffix on their names by giving ‘configure’ the
+option ‘--program-prefix=PREFIX’ or ‘--program-suffix=SUFFIX’.
 
-   Some packages pay attention to '--enable-FEATURE' options to
-'configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to '--with-PACKAGE' options, where PACKAGE
-is something like 'gnu-as' or 'x' (for the X Window System).  The
-'README' should mention any '--enable-' and '--with-' options that the
-package recognizes.
-
-   For packages that use the X Window System, 'configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the 'configure' options '--x-includes=DIR' and
-'--x-libraries=DIR' to specify their locations.
+   Some packages pay attention to ‘--enable-FEATURE’ and
+‘--disable-FEATURE’ options to ‘configure’, where FEATURE indicates an
+optional part of the package.  They may also pay attention to
+‘--with-PACKAGE’ and ‘--without-PACKAGE’ options, where PACKAGE is
+something like ‘gnu-ld’.  ‘./configure --help’ should mention the
+‘--enable-...’ and ‘--with-...’ options that the package recognizes.
 
    Some packages offer the ability to configure how verbose the
-execution of 'make' will be.  For these packages, running './configure
---enable-silent-rules' sets the default to minimal output, which can be
-overridden with 'make V=1'; while running './configure
---disable-silent-rules' sets the default to verbose, which can be
-overridden with 'make V=0'.
-
-Particular systems
-==================
-
-   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU CC
-is not installed, it is recommended to use the following options in
-order to use an ANSI C compiler:
-
-     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
-
-and if that doesn't work, install pre-built binaries of GCC for HP-UX.
-
-   HP-UX 'make' updates targets which have the same timestamps as their
-prerequisites, which makes it generally unusable when shipped generated
-files such as 'configure' are involved.  Use GNU 'make' instead.
-
-   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its '<wchar.h>' header file.  The option '-nodtk' can be used as a
-workaround.  If GNU CC is not installed, it is therefore recommended to
-try
-
-     ./configure CC="cc"
-
-and if that doesn't work, try
-
-     ./configure CC="cc -nodtk"
-
-   On Solaris, don't put '/usr/ucb' early in your 'PATH'.  This
-directory contains several dysfunctional programs; working variants of
-these programs are available in '/usr/bin'.  So, if you need '/usr/ucb'
-in your 'PATH', put it _after_ '/usr/bin'.
-
-   On Haiku, software installed for all users goes in '/boot/common',
-not '/usr/local'.  It is recommended to use the following options:
-
-     ./configure --prefix=/boot/common
-
-Specifying the System Type
-==========================
-
-   There may be some features 'configure' cannot figure out
-automatically, but needs to determine by the type of machine the package
-will run on.  Usually, assuming the package is built to be run on the
-_same_ architectures, 'configure' can figure that out, but if it prints
-a message saying it cannot guess the machine type, give it the
-'--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as 'sun4', or a canonical name which has the form:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS
-     KERNEL-OS
-
-   See the file 'config.sub' for the possible values of each field.  If
-'config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
-   If you are _building_ compiler tools for cross-compiling, you should
-use the option '--target=TYPE' to select the type of system they will
-produce code for.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with '--host=TYPE'.
+execution of ‘make’ will be.  For these packages, running ‘./configure
+--enable-silent-rules’ sets the default to minimal output, which can be
+overridden with ‘make V=1’; while running ‘./configure
+--disable-silent-rules’ sets the default to verbose, which can be
+overridden with ‘make V=0’.
+
+Specifying a System Type
+========================
+
+   By default ‘configure’ builds for the current system.  To create
+binaries that can run on a different system type, specify a
+‘--host=TYPE’ option along with compiler variables that specify how to
+generate object code for TYPE.  For example, to create binaries intended
+to run on a 64-bit ARM processor:
+
+     ./configure --host=aarch64-linux-gnu \
+        CC=aarch64-linux-gnu-gcc \
+        CXX=aarch64-linux-gnu-g++
+
+If done on a machine that can execute these binaries (e.g., via
+‘qemu-aarch64’, ‘$QEMU_LD_PREFIX’, and Linux’s ‘binfmt_misc’
+capability), the build behaves like a native build.  Otherwise it is a
+cross-build: ‘configure’ will make cross-compilation guesses instead of
+running test programs, and ‘make check’ will not work.
+
+   A system type can either be a short name like ‘mingw64’, or a
+canonical name like ‘x86_64-pc-linux-gnu’.  Canonical names have the
+form CPU-COMPANY-SYSTEM where SYSTEM is either OS or KERNEL-OS.  To
+canonicalize and validate a system type, you can run the command
+‘config.sub’, which is often squirreled away in a subdirectory like
+‘build-aux’.  For example:
+
+     $ build-aux/config.sub arm64-linux
+     aarch64-unknown-linux-gnu
+     $ build-aux/config.sub riscv-lnx
+     Invalid configuration 'riscv-lnx': OS 'lnx' not recognized
+
+You can look at the ‘config.sub’ file to see which types are recognized.
+If the file is absent, this package does not need the system type.
+
+   If ‘configure’ fails with the diagnostic “cannot guess build type”.
+‘config.sub’ did not recognize your system’s type.  In this case, first
+fetch the newest versions of these files from the GNU config package
+(https://savannah.gnu.org/projects/config).  If that fixes things,
+please report it to the maintainers of the package containing
+‘configure’.  Otherwise, you can try the configure option ‘--build=TYPE’
+where TYPE comes close to your system type; also, please report the
+problem to <config-patches@gnu.org>.
+
+   For more details about configuring system types, see the Autoconf
+documentation.
 
 Sharing Defaults
 ================
 
-   If you want to set default values for 'configure' scripts to share,
-you can create a site shell script called 'config.site' that gives
-default values for variables like 'CC', 'cache_file', and 'prefix'.
-'configure' looks for 'PREFIX/share/config.site' if it exists, then
-'PREFIX/etc/config.site' if it exists.  Or, you can set the
-'CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all 'configure' scripts look for a site script.
+   If you want to set default values for ‘configure’ scripts to share,
+you can create a site shell script called ‘config.site’ that gives
+default values for variables like ‘CC’, ‘cache_file’, and ‘prefix’.
+‘configure’ looks for ‘PREFIX/share/config.site’ if it exists, then
+‘PREFIX/etc/config.site’ if it exists.  Or, you can set the
+‘CONFIG_SITE’ environment variable to the location of the site script.
+A warning: not all ‘configure’ scripts look for a site script.
 
 Defining Variables
 ==================
 
    Variables not defined in a site shell script can be set in the
-environment passed to 'configure'.  However, some packages may run
+environment passed to ‘configure’.  However, some packages may run
 configure again during the build, and the customized values of these
 variables may be lost.  In order to avoid this problem, you should set
-them in the 'configure' command line, using 'VAR=value'.  For example:
+them in the ‘configure’ command line, using ‘VAR=value’.  For example:
 
      ./configure CC=/usr/local2/bin/gcc
 
-causes the specified 'gcc' to be used as the C compiler (unless it is
+causes the specified ‘gcc’ to be used as the C compiler (unless it is
 overridden in the site shell script).
 
-Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
+Unfortunately, this technique does not work for ‘CONFIG_SHELL’ due to an
 Autoconf limitation.  Until the limitation is lifted, you can use this
 workaround:
 
      CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
 
-'configure' Invocation
+‘configure’ Invocation
 ======================
 
-   'configure' recognizes the following options to control how it
+   ‘configure’ recognizes the following options to control how it
 operates.
 
-'--help'
-'-h'
-     Print a summary of all of the options to 'configure', and exit.
+‘--help’
+‘-h’
+     Print a summary of all of the options to ‘configure’, and exit.
 
-'--help=short'
-'--help=recursive'
-     Print a summary of the options unique to this package's
-     'configure', and exit.  The 'short' variant lists options used only
-     in the top level, while the 'recursive' variant lists options also
+‘--help=short’
+‘--help=recursive’
+     Print a summary of the options unique to this package’s
+     ‘configure’, and exit.  The ‘short’ variant lists options used only
+     in the top level, while the ‘recursive’ variant lists options also
      present in any nested packages.
 
-'--version'
-'-V'
-     Print the version of Autoconf used to generate the 'configure'
+‘--version’
+‘-V’
+     Print the version of Autoconf used to generate the ‘configure’
      script, and exit.
 
-'--cache-file=FILE'
+‘--cache-file=FILE’
      Enable the cache: use and save the results of the tests in FILE,
-     traditionally 'config.cache'.  FILE defaults to '/dev/null' to
+     traditionally ‘config.cache’.  FILE defaults to ‘/dev/null’ to
      disable caching.
 
-'--config-cache'
-'-C'
-     Alias for '--cache-file=config.cache'.
-
-'--quiet'
-'--silent'
-'-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to '/dev/null' (any error
-     messages will still be shown).
+‘--config-cache’
+‘-C’
+     Alias for ‘--cache-file=config.cache’.
 
-'--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     'configure' can determine that directory automatically.
+‘--srcdir=DIR’
+     Look for the package’s source code in directory DIR.  Usually
+     ‘configure’ can determine that directory automatically.
 
-'--prefix=DIR'
-     Use DIR as the installation prefix.  *note Installation Names:: for
+‘--prefix=DIR’
+     Use DIR as the installation prefix.  See “Installation Names” for
      more details, including other options available for fine-tuning the
      installation locations.
 
-'--no-create'
-'-n'
+‘--host=TYPE’
+     Build binaries for system TYPE.  See “Specifying a System Type”.
+
+‘--enable-FEATURE’
+‘--disable-FEATURE’
+     Enable or disable the optional FEATURE.  See “Optional Features”.
+
+‘--with-PACKAGE’
+‘--without-PACKAGE’
+     Use or omit PACKAGE when building.  See “Optional Features”.
+
+‘--quiet’
+‘--silent’
+‘-q’
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to ‘/dev/null’ (any error
+     messages will still be shown).
+
+‘--no-create’
+‘-n’
      Run the configure checks, but stop before creating any output
      files.
 
-'configure' also accepts some other, not widely useful, options.  Run
-'configure --help' for more details.
+‘configure’ also recognizes several environment variables, and accepts
+some other, less widely useful, options.  Run ‘configure --help’ for
+more details.
+
+Copyright notice
+================
+
+   Copyright © 1994–1996, 1999–2002, 2004–2017, 2020–2024 Free Software
+Foundation, Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.

_service:tar_scm:automake-1.16.5.tar.xz/Makefile.am -> _service:tar_scm:automake-1.17.tar.xz/Makefile.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/Makefile.in -> _service:tar_scm:automake-1.17.tar.xz/Makefile.in Changed

@@ -1,7 +1,7 @@
-# Makefile.in generated by automake 1.16.5 from Makefile.am.
+# Makefile.in generated by automake 1.17 from Makefile.am.
 # @configure_input@
 
-# Copyright (C) 1994-2021 Free Software Foundation, Inc.
+# Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 # This Makefile.in is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -14,7 +14,7 @@
 
 @SET_MAKE@
 
-# Copyright (C) 1995-2021 Free Software Foundation, Inc.
+# Copyright (C) 1995-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -86,6 +86,8 @@
   test $$has_opt = yes
 am__make_dryrun = (target_option=n; $(am__make_running_with_option))
 am__make_keepgoing = (target_option=k; $(am__make_running_with_option))
+am__rm_f = rm -f $(am__rm_f_notfound)
+am__rm_rf = rm -rf $(am__rm_f_notfound)
 pkgdatadir = $(datadir)/@PACKAGE@
 pkgincludedir = $(includedir)/@PACKAGE@
 pkglibdir = $(libdir)/@PACKAGE@
@@ -106,7 +108,16 @@
 host_triplet = @host@
 subdir = .
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/configure.ac
+am__aclocal_m4_deps = $(top_srcdir)/m4/amversion.m4 \
+	$(top_srcdir)/m4/auxdir.m4 $(top_srcdir)/m4/cond.m4 \
+	$(top_srcdir)/m4/init.m4 $(top_srcdir)/m4/install-sh.m4 \
+	$(top_srcdir)/m4/lead-dot.m4 $(top_srcdir)/m4/missing.m4 \
+	$(top_srcdir)/m4/options.m4 $(top_srcdir)/m4/prog-cc-c-o.m4 \
+	$(top_srcdir)/m4/rmf.m4 $(top_srcdir)/m4/runlog.m4 \
+	$(top_srcdir)/m4/sanity.m4 $(top_srcdir)/m4/silent.m4 \
+	$(top_srcdir)/m4/strip.m4 $(top_srcdir)/m4/substnot.m4 \
+	$(top_srcdir)/m4/tar.m4 $(top_srcdir)/m4/xargsn.m4 \
+	$(top_srcdir)/configure.ac
 am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
 	$(ACLOCAL_M4)
 DIST_COMMON = $(srcdir)/Makefile.am $(top_srcdir)/configure \
@@ -143,10 +154,9 @@
   sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
   sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
 am__uninstall_files_from_dir = { \
-  test -z "$$files" \
-    || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
-    || { echo " ( cd '$$dir' && rm -f" $$files ")"; \
-         $(am__cd) "$$dir" && rm -f $$files; }; \
+  { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
+  || { echo " ( cd '$$dir' && rm -f" $$files ")"; \
+       $(am__cd) "$$dir" && echo $$files | $(am__xargs_n) 40 $(am__rm_f); }; \
   }
 am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(infodir)" \
 	"$(DESTDIR)$(man1dir)" "$(DESTDIR)$(amdir)" \
@@ -355,6 +365,7 @@
 # Default flags passed to test drivers.
 am__common_driver_flags = \
   --color-tests "$$am__color_tests" \
+  $$am__collect_skipped_logs \
   --enable-hard-errors "$$am__enable_hard_errors" \
   --expect-failure "$$am__expect_failure"
 # To be inserted before the command running the test.  Creates the
@@ -379,6 +390,11 @@
 elif test -f "$$f"; then dir=;				\
 else dir="$(srcdir)/"; fi;				\
 tst=$$dir$$f; log='$@'; 				\
+if test -n '$(IGNORE_SKIPPED_LOGS)'; then		\
+  am__collect_skipped_logs='--collect-skipped-logs no';	\
+else							\
+  am__collect_skipped_logs='';				\
+fi;							\
 if test -n '$(DISABLE_HARD_ERRORS)'; then		\
   am__enable_hard_errors=no; 				\
 else							\
@@ -449,20 +465,22 @@
 top_distdir = $(distdir)
 am__remove_distdir = \
   if test -d "$(distdir)"; then \
-    find "$(distdir)" -type d ! -perm -200 -exec chmod u+w {} ';' \
-      && rm -rf "$(distdir)" \
+    find "$(distdir)" -type d ! -perm -700 -exec chmod u+rwx {} ';' \
+      ; rm -rf "$(distdir)" \
       || { sleep 5 && rm -rf "$(distdir)"; }; \
   else :; fi
 am__post_remove_distdir = $(am__remove_distdir)
 DIST_ARCHIVES = $(distdir).tar.gz $(distdir).tar.xz
-GZIP_ENV = --best
+GZIP_ENV = -9
 DIST_TARGETS = dist-xz dist-gzip
 # Exists only to be overridden by the user if desired.
 AM_DISTCHECK_DVI_TARGET = dvi
 distuninstallcheck_listfiles = find . -type f -print
 am__distuninstallcheck_listfiles = $(distuninstallcheck_listfiles) \
   | sed 's|^\./|$(prefix)/|' | grep -v '$(infodir)/dir$$'
-distcleancheck_listfiles = find . -type f -print
+distcleancheck_listfiles = \
+  find . $ -type f -a \! \
+            \( -name .nfs* -o -name .smb* -o -name .__afs* $ \) -print
 ACLOCAL = @ACLOCAL@
 AMTAR = @AMTAR@
 AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
@@ -517,7 +535,7 @@
 LTLIBOBJS = @LTLIBOBJS@
 MAKEINFO = @MAKEINFO@
 MKDIR_P = @MKDIR_P@
-MODIFICATION_DELAY = @MODIFICATION_DELAY@
+MTIME_RESOLUTION = @MTIME_RESOLUTION@
 OBJEXT = @OBJEXT@
 PACKAGE = @PACKAGE@
 PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
@@ -554,8 +572,10 @@
 am_AUTORECONF = @am_AUTORECONF@
 am_AUTOUPDATE = @am_AUTOUPDATE@
 am__leading_dot = @am__leading_dot@
+am__rm_f_notfound = @am__rm_f_notfound@
 am__tar = @am__tar@
 am__untar = @am__untar@
+am__xargs_n = @am__xargs_n@
 amdir = @amdir@
 automake_acdir = @automake_acdir@
 bindir = @bindir@
@@ -616,7 +636,22 @@
 # Older files, kept mostly for historical interest.
 
 # Maintainer-specific files and scripts.
-# XXX: This script should be updated with 'fetch' target.
+
+# In automake, users generate man pages as part of a normal build from
+# release tarballs. This is ok because we also distribute the help2man
+# script, as given below.
+#
+# Autoconf handles this in an alternative way, of including the man
+# pages in the tarballs and thus not requiring help2man to be run by
+# users (q.v.). Neither is better or worse than the other.
+#
+# See the "Errors with distclean" node in the manual for more info.
+
+# XXX: The help2man script we include in the Automake distribution
+# should be updated with 'fetch' target, but isn't. Instead, you must
+# build help2man normally and copy it in manually. Keep the first line as:
+#   #!/usr/bin/perl -w
+# whatever it might have ended up as on your system.
 EXTRA_DIST = bootstrap GNUmakefile HACKING NEWS-2.0 PLANS \
 	contrib/tap-driver.pl contrib/check-html.am contrib/checklinkx \
 	contrib/multilib/README contrib/multilib/config-ml.in \
@@ -701,19 +736,19 @@
   doc/automake-$(APIVERSION).1
 
 update_mans = \
-  $(AM_V_GEN): \
-    && $(MKDIR_P) doc \
-    && ./pre-inst-env $(PERL) $(srcdir)/doc/help2man --output=$@
+    $(MKDIR_P) doc \
+    && AUTOMAKE_HELP2MAN=true ./pre-inst-env \
+       $(PERL) $(srcdir)/doc/help2man --output=$@ --info-page=automake \
+               --name="$${HELP2MAN_NAME}"
 
 checklinkx = $(top_srcdir)/contrib/checklinkx
-# that 4-second sleep seems to be what gnu.org likes.
+# that particular sleep seems to be what gnu.org likes.
 chlx_args = -v --sleep 8 #--exclude-url-file=/tmp/xf
 # Explanation of excludes:
 # - w3.org dtds, they are fine (and slow).
 # - mailto urls, they are always forbidden.
 # - vala, redirects to a Gnome subpage and returns 403 to us.
 # - cfortran, forbidden by site's robots.txt.
-# - search.cpan.org, gets
 # - debbugs.gnu.org/automake, forbidden by robots.txt.
 # - autoconf.html, forbidden by robots.txt (since served from savannah).
 # - https://fsf.org redirects to https://www.fsf.org and nothing to do
@@ -724,7 +759,6 @@
     -X 'mailto:.*' \
     -X 'https://www\.vala-project\.org/' \
     -X 'https://www-zeus\.desy\.de/~burow/cfortran/' \
-    -X 'http://xsearch\.cpan\.org/~mschwern/Test-Simple/lib/Test/More\.pm' \
     -X 'https://debbugs\.gnu\.org/automake' \
     -X 'https://www\.gnu\.org/software/autoconf/manual/autoconf\.html' \
     -X 'https://fsf\.org/'
@@ -874,6 +908,7 @@
   m4/options.m4 \
   m4/python.m4 \
   m4/prog-cc-c-o.m4 \
+  m4/rmf.m4 \
   m4/runlog.m4 \
   m4/sanity.m4 \
   m4/silent.m4 \
@@ -881,7 +916,8 @@
   m4/substnot.m4 \
   m4/tar.m4 \
   m4/upc.m4 \
-  m4/vala.m4
+  m4/vala.m4 \
+  m4/xargsn.m4
 
 dist_system_ac_DATA = m4/acdir/README
 automake_internal_acdir = $(automake_acdir)/internal
@@ -914,13 +950,13 @@
 # in case it is given with a relative name containing no slashes.
 
 # Ensure that the installed Automake perl modules are found when running 'installcheck' target
-AM_TESTS_ENVIRONMENT = for v in required am_test_protocol \
-	am_serial_tests am_test_prefer_config_shell \
-	am_original_AUTOMAKE am_original_ACLOCAL am_test_lib_sourced \
-	test_lib_sourced ; do eval test x"\$${$$v}" = x || unset $$v; \
-	done; stderr_fileno_=9; export stderr_fileno_; if test \
-	$(srcdir) != .; then \
-	PATH='$(abs_srcdir)/t/ax$(PATH_SEPARATOR)'$$PATH; fi; \
+AM_TESTS_ENVIRONMENT = for v in ACLOCAL AUTOCONF AUTOHEADER AUTOMAKE \
+	AUTOUPDATE required am_test_protocol am_serial_tests \
+	am_test_prefer_config_shell am_original_AUTOMAKE \
+	am_original_ACLOCAL am_test_lib_sourced test_lib_sourced ; do \
+	eval test x\"\$${$$v}\" = x || unset $$v; done; \
+	stderr_fileno_=9; export stderr_fileno_; if test $(srcdir) != \
+	.; then PATH='$(abs_srcdir)/t/ax$(PATH_SEPARATOR)'$$PATH; fi; \
 	PATH='$(abs_builddir)/t/ax$(PATH_SEPARATOR)'$$PATH; export \
 	PATH; if test "$${am_running_installcheck}" = yes; then \
 	PERL5LIB="$(DESTDIR)$(pkgvdatadir)/$${PERL5LIB:+$(PATH_SEPARATOR)}$$PERL5LIB"; \
@@ -929,7 +965,7 @@
 # the console if possible, so set up 'stderr_fileno_' properly.
 AM_TESTS_FD_REDIRECT = 9>&2
 
-# FIXME: this "expected failures" are in truth an hack used to
+# FIXME: These "expected failures" are a kludge used to
 # FIXME: to verify that some incorrect usages of our perl libraries
 # FIXME: raise an error.  We should find a cleaner way to check that.
 perl_fake_XFAIL_TESTS = \
@@ -940,6 +976,10 @@
 t/pm/Version2.pl \
 t/pm/Version3.pl
 
+
+# These must be separately/redundantly included in handwritten_TESTS
+# below.  Despite the redundancy, it seems cleaner to keep
+# handwritten_TESTS as a list of all such .sh tests.
 XFAIL_TESTS = \
 t/all.sh \
 t/cond17.sh \
@@ -948,6 +988,7 @@
 t/override-conditional-pr13940.sh \
 t/dist-pr109765.sh \
 t/instdir-cond2.sh \
+t/instdir-ltlib.sh \
 t/java-nobase.sh \
 t/objext-pr10128.sh \
 t/remake-timing-bug-pr8365.sh \
@@ -1073,6 +1114,7 @@
 t/ar3.sh \
 t/ar4.sh \
 t/ar5.sh \
+t/ar_override.sh \
 t/asm.sh \
 t/asm2.sh \
 t/asm3.sh \
@@ -1100,6 +1142,7 @@
 t/auxdir-misplaced.sh \
 t/auxdir-nonexistent.sh \
 t/auxdir-pr19311.sh \
+t/auxdir-subsubdir.sh \
 t/auxdir-unportable.tap \
 t/backcompat.sh \
 t/backcompat2.sh \
@@ -1177,7 +1220,9 @@
 t/comment9.sh \
 t/commen10.sh \
 t/commen11.sh \
+t/comment12.sh \
 t/comment-block.sh \
+t/comments-escaped-in-var.sh \
 t/comments-in-var-def.sh \
 t/compile.sh \
 t/compile2.sh \
@@ -1501,6 +1546,7 @@
 t/lex5.sh \
 t/lexcpp.sh \
 t/lexvpath.sh \
+t/lex-args.sh \
 t/lex-subobj-nodep.sh \
 t/lex-header.sh \
 t/lex-lib.sh \
@@ -1636,6 +1682,7 @@
 t/no-extra-makefile-code.sh \
 t/no-spurious-install-recursive.sh \
 t/nobase.sh \
+t/nobase-dist.sh \
 t/nobase-libtool.sh \
 t/nobase-python.sh \
 t/nobase-nodist.sh \
@@ -1722,6 +1769,7 @@
 t/parallel-tests-empty-testlogs.sh \
 t/parallel-tests-driver-install.sh \
 t/parallel-tests-no-color-in-log.sh \
+t/parallel-tests-without-skipped-logs.sh \
 t/parallel-tests-no-spurious-summary.sh \
 t/parallel-tests-exit-statuses.sh \
 t/parallel-tests-console-output.sh \
@@ -1780,6 +1828,7 @@
 t/pluseq9.sh \
 t/pluseq10.sh \
 t/pluseq11.sh \
+t/posixtarget.sh \
 t/posixsubst-data.sh \
 t/posixsubst-extradist.sh \
 t/posixsubst-ldadd.sh \
@@ -1829,6 +1878,7 @@
 t/py-compile-basedir.sh \
 t/py-compile-destdir.sh \
 t/py-compile-env.sh \
+t/py-compile-files.sh \
 t/py-compile-option-terminate.sh \
 t/py-compile-usage.sh \
 t/python.sh \
@@ -1845,6 +1895,7 @@
 t/python-vars.sh \
 t/python-virtualenv.sh \
 t/python-pr10995.sh \
+t/ranlib_override.sh \
 t/recurs-user.sh \
 t/recurs-user2.sh \
 t/recurs-user-deeply-nested.sh \
@@ -1922,6 +1973,7 @@
 t/seenc.sh \
 t/silent-c.sh \
 t/silent-cxx.sh \
+t/silent-defaults.sh \
 t/silent-lt.sh \
 t/silent-f77.sh \
 t/silent-f90.sh \
@@ -2136,6 +2188,8 @@
 t/txinfo-no-installinfo.sh \
 t/txinfo-no-repeated-targets.sh \
 t/txinfo-no-setfilename.sh \
+t/txinfo-no-setfilename-no-inputs.sh \
+t/txinfo-no-texi-but-texi-in.sh \
 t/txinfo-other-suffixes.sh \
 t/txinfo-override-infodeps.sh \
 t/txinfo-override-texinfo-tex.sh \
@@ -2178,6 +2232,7 @@
 t/vala-recursive-setup.sh \
 t/vala-vapi.sh \
 t/vala-vpath.sh \
+t/varempty.sh \
 t/vars.sh \
 t/vars3.sh \
 t/var-recurs.sh \
@@ -2552,7 +2607,7 @@
 	dir='$(DESTDIR)$(bindir)'; $(am__uninstall_files_from_dir)
 doc/$(am__dirstamp):
 	@$(MKDIR_P) doc
-	@: > doc/$(am__dirstamp)
+	@: >>doc/$(am__dirstamp)
 
 $(srcdir)/doc/automake.info: doc/automake.texi $(srcdir)/doc/version.texi $(doc_automake_TEXINFOS)
 	$(AM_V_MAKEINFO)restore=: && backupdir="$(am__leading_dot)am$$$$" && \
@@ -2579,13 +2634,13 @@
 doc/automake.dvi: doc/automake.texi $(srcdir)/doc/version.texi $(doc_automake_TEXINFOS) doc/$(am__dirstamp)
 	$(AM_V_TEXI2DVI)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
 	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I doc -I $(srcdir)/doc' \
-	$(TEXI2DVI) $(AM_V_texinfo) --build-dir=$(@:.dvi=.t2d) -o $@ $(AM_V_texidevnull) \
+	$(TEXI2DVI) $(AM_TEXI2FLAGS) -I doc -I $(srcdir)/doc $(AM_V_texinfo) --build-dir=$(@:.dvi=.t2d) -o $@ $(AM_V_texidevnull) \
 	`test -f 'doc/automake.texi' || echo '$(srcdir)/'`doc/automake.texi
 
 doc/automake.pdf: doc/automake.texi $(srcdir)/doc/version.texi $(doc_automake_TEXINFOS) doc/$(am__dirstamp)
 	$(AM_V_TEXI2PDF)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
 	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I doc -I $(srcdir)/doc' \
-	$(TEXI2PDF) $(AM_V_texinfo) --build-dir=$(@:.pdf=.t2p) -o $@ $(AM_V_texidevnull) \
+	$(TEXI2PDF) $(AM_TEXI2FLAGS) -I doc -I $(srcdir)/doc $(AM_V_texinfo) --build-dir=$(@:.pdf=.t2p) -o $@ $(AM_V_texidevnull) \
 	`test -f 'doc/automake.texi' || echo '$(srcdir)/'`doc/automake.texi
 
 doc/automake.html: doc/automake.texi $(srcdir)/doc/version.texi $(doc_automake_TEXINFOS) doc/$(am__dirstamp)
@@ -2644,13 +2699,13 @@
 doc/automake-history.dvi: doc/automake-history.texi $(doc_automake_history_TEXINFOS) doc/$(am__dirstamp)
 	$(AM_V_TEXI2DVI)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
 	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I doc -I $(srcdir)/doc' \
-	$(TEXI2DVI) $(AM_V_texinfo) --build-dir=$(@:.dvi=.t2d) -o $@ $(AM_V_texidevnull) \
+	$(TEXI2DVI) $(AM_TEXI2FLAGS) -I doc -I $(srcdir)/doc $(AM_V_texinfo) --build-dir=$(@:.dvi=.t2d) -o $@ $(AM_V_texidevnull) \
 	`test -f 'doc/automake-history.texi' || echo '$(srcdir)/'`doc/automake-history.texi
 
 doc/automake-history.pdf: doc/automake-history.texi $(doc_automake_history_TEXINFOS) doc/$(am__dirstamp)
 	$(AM_V_TEXI2PDF)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
 	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I doc -I $(srcdir)/doc' \
-	$(TEXI2PDF) $(AM_V_texinfo) --build-dir=$(@:.pdf=.t2p) -o $@ $(AM_V_texidevnull) \
+	$(TEXI2PDF) $(AM_TEXI2FLAGS) -I doc -I $(srcdir)/doc $(AM_V_texinfo) --build-dir=$(@:.pdf=.t2p) -o $@ $(AM_V_texidevnull) \
 	`test -f 'doc/automake-history.texi' || echo '$(srcdir)/'`doc/automake-history.texi
 
 doc/automake-history.html: doc/automake-history.texi $(doc_automake_history_TEXINFOS) doc/$(am__dirstamp)
@@ -2743,14 +2798,11 @@
 	done
 
 mostlyclean-aminfo:
-	-rm -rf doc/automake.t2d doc/automake.t2p doc/automake-history.t2d \
+	-$(am__rm_rf) doc/automake.t2d doc/automake.t2p doc/automake-history.t2d \
 	  doc/automake-history.t2p
 
 clean-aminfo:
-	-test -z "doc/automake.dvi doc/automake.pdf doc/automake.ps doc/automake.html \
-	  doc/automake-history.dvi doc/automake-history.pdf \
-	  doc/automake-history.ps doc/automake-history.html" \
-	|| rm -rf doc/automake.dvi doc/automake.pdf doc/automake.ps doc/automake.html \
+	-$(am__rm_rf) doc/automake.dvi doc/automake.pdf doc/automake.ps doc/automake.html \
 	  doc/automake-history.dvi doc/automake-history.pdf \
 	  doc/automake-history.ps doc/automake-history.html
 
@@ -3063,7 +3115,6 @@
 am--fnord $(TEST_LOGS) $(TEST_LOGS:.log=.trs): $(am__force_recheck)
 am--force-recheck:
 	@:
-
 $(TEST_SUITE_LOG): $(TEST_LOGS)
 	@$(am__set_TESTS_bases); \
 	am__f_ok () { test -f "$$1" && test -r "$$1"; }; \
@@ -3139,10 +3190,37 @@
 	  result_count $$1 "XPASS:" $$xpass "$$red"; \
 	  result_count $$1 "ERROR:" $$error "$$mgn"; \
 	}; \
+	output_system_information () \
+	{ \
+          echo;                                     \
+	  { uname -a | $(AWK) '{                    \
+  printf "System information (uname -a):";          \
+  for (i = 1; i < NF; ++i)                          \
+    {                                               \
+      if (i != 2)                                   \
+        printf " %s", $$i;                          \
+    }                                               \
+  printf "\n";                                      \
+}'; } 2>&1;                                         \
+	  if test -r /etc/os-release; then          \
+	    echo "Distribution information (/etc/os-release):"; \
+	    sed 8q /etc/os-release;                 \
+	  elif test -r /etc/issue; then             \
+	    echo "Distribution information (/etc/issue):";      \
+	    cat /etc/issue;                         \
+	  fi;                                       \
+	}; \
+	please_report () \
+	{ \
+echo "Some test(s) failed.  Please report this to $(PACKAGE_BUGREPORT),";    \
+echo "together with the test-suite.log file (gzipped) and your system";      \
+echo "information.  Thanks.";                                                \
+	}; \
 	{								\
 	  echo "$(PACKAGE_STRING): $(subdir)/$(TEST_SUITE_LOG)" |	\
 	    $(am__rst_title);						\
 	  create_testsuite_report --no-color;				\
+	  output_system_information;                                    \
 	  echo;								\
 	  echo ".. contents:: :depth: 2";				\
 	  echo;								\
@@ -3162,26 +3240,25 @@
 	create_testsuite_report --maybe-color;				\
 	echo "$$col$$br$$std";						\
 	if $$success; then :; else					\
-	  echo "$${col}See $(subdir)/$(TEST_SUITE_LOG)$${std}";		\
+	  echo "$${col}See $(subdir)/$(TEST_SUITE_LOG) for debugging.$${std}";\
 	  if test -n "$(PACKAGE_BUGREPORT)"; then			\
-	    echo "$${col}Please report to $(PACKAGE_BUGREPORT)$${std}";	\
+	    please_report | sed -e "s/^/$${col}/" -e s/'$$'/"$${std}"/; \
 	  fi;								\
 	  echo "$$col$$br$$std";					\
 	fi;								\
 	$$success || exit 1
 
 check-TESTS: 
-	@list='$(RECHECK_LOGS)';           test -z "$$list" || rm -f $$list
-	@list='$(RECHECK_LOGS:.log=.trs)'; test -z "$$list" || rm -f $$list
-	@test -z "$(TEST_SUITE_LOG)" || rm -f $(TEST_SUITE_LOG)
+	@$(am__rm_f) $(RECHECK_LOGS)
+	@$(am__rm_f) $(RECHECK_LOGS:.log=.trs)
+	@$(am__rm_f) $(TEST_SUITE_LOG)
 	@set +e; $(am__set_TESTS_bases); \
 	log_list=`for i in $$bases; do echo $$i.log; done`; \
-	trs_list=`for i in $$bases; do echo $$i.trs; done`; \
-	log_list=`echo $$log_list`; trs_list=`echo $$trs_list`; \
+	log_list=`echo $$log_list`; \
 	$(MAKE) $(AM_MAKEFLAGS) $(TEST_SUITE_LOG) TEST_LOGS="$$log_list"; \
 	exit $$?;
 recheck: all 
-	@test -z "$(TEST_SUITE_LOG)" || rm -f $(TEST_SUITE_LOG)
+	@$(am__rm_f) $(TEST_SUITE_LOG)
 	@set +e; $(am__set_TESTS_bases); \
 	bases=`for i in $$bases; do echo $$i; done \
 	         | $(am__list_recheck_tests)` || exit 1; \
@@ -3238,7 +3315,7 @@
 
 distdir-am: $(DISTFILES)
 	$(am__remove_distdir)
-	test -d "$(distdir)" || mkdir "$(distdir)"
+	$(AM_V_at)$(MKDIR_P) "$(distdir)"
 	@srcdirstrip=`echo "$(srcdir)" | sed 's/.^$$\\*/\\\\&/g'`; \
 	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/.^$$\\*/\\\\&/g'`; \
 	list='$(DISTFILES)'; \
@@ -3331,7 +3408,7 @@
 distcheck: dist
 	case '$(DIST_ARCHIVES)' in \
 	*.tar.gz*) \
-	  eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).tar.gz | $(am__untar) ;;\
+	  eval GZIP= gzip -dc $(distdir).tar.gz | $(am__untar) ;;\
 	*.tar.bz2*) \
 	  bzip2 -dc $(distdir).tar.bz2 | $(am__untar) ;;\
 	*.tar.lz*) \
@@ -3341,7 +3418,7 @@
 	*.tar.Z*) \
 	  uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
 	*.shar.gz*) \
-	  eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).shar.gz | unshar ;;\
+	  eval GZIP= gzip -dc $(distdir).shar.gz | unshar ;;\
 	*.zip*) \
 	  unzip $(distdir).zip ;;\
 	*.tar.zst*) \
@@ -3440,23 +3517,23 @@
 	    "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \
 	fi
 mostlyclean-generic:
-	-test -z "$(TEST_LOGS)" || rm -f $(TEST_LOGS)
-	-test -z "$(TEST_LOGS:.log=.trs)" || rm -f $(TEST_LOGS:.log=.trs)
-	-test -z "$(TEST_SUITE_LOG)" || rm -f $(TEST_SUITE_LOG)
+	-$(am__rm_f) $(TEST_LOGS)
+	-$(am__rm_f) $(TEST_LOGS:.log=.trs)
+	-$(am__rm_f) $(TEST_SUITE_LOG)
 
 clean-generic:
-	-test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
+	-$(am__rm_f) $(CLEANFILES)
 
 distclean-generic:
-	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-	-test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
-	-rm -f doc/$(am__dirstamp)
-	-test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES)
+	-$(am__rm_f) $(CONFIG_CLEAN_FILES)
+	-test . = "$(srcdir)" || $(am__rm_f) $(CONFIG_CLEAN_VPATH_FILES)
+	-$(am__rm_f) $(DISTCLEANFILES)
+	-$(am__rm_f) doc/$(am__dirstamp)
 
 maintainer-clean-generic:
 	@echo "This command is intended for maintainers to use"
 	@echo "it deletes files that may require special tools to rebuild."
-	-test -z "$(MAINTAINERCLEANFILES)" || rm -f $(MAINTAINERCLEANFILES)
+	-$(am__rm_f) $(MAINTAINERCLEANFILES)
 clean: clean-am
 
 clean-am: clean-aminfo clean-generic clean-local mostlyclean-am
@@ -3738,9 +3815,9 @@
 	  && echo ".so man1/$$f-$(APIVERSION).1" > $@
 
 doc/aclocal-$(APIVERSION).1: $(aclocal_script) lib/Automake/Config.pm
-	$(update_mans) aclocal-$(APIVERSION)
+	$(AM_V_GEN):; HELP2MAN_NAME="Generate aclocal.m4 by scanning configure.ac"; export HELP2MAN_NAME; $(update_mans) $(aclocal_script)
 doc/automake-$(APIVERSION).1: $(automake_script) lib/Automake/Config.pm
-	$(update_mans) automake-$(APIVERSION)
+	$(AM_V_GEN):; HELP2MAN_NAME="Generate Makefile.in files for configure from Makefile.am"; export HELP2MAN_NAME; $(update_mans) $(automake_script)
 .PHONY: checklinkx
 checklinkx:
 	$(checklinkx) $(chlx_args) $(chlx_excludes) $(chlx_file)
@@ -4131,7 +4208,7 @@
 
 # If two test scripts have the same basename, they will end up sharing
 # the same log file, leading to all sort of undefined and undesired
-# behaviours.
+# behaviors.
 check-no-repeated-test-name:
 	@LC_ALL=C; export LC_ALL; \
 	 lst='$(TEST_LOGS)'; for log in $$lst; do echo $$log; done \
@@ -4222,16 +4299,16 @@
 	       ($(am__cd) $(srcdir) && ls $$dir/*$$ext 2>/dev/null); \
 	     fi; \
 	   done; \
-	 done | sed 's,^\./,,' | sort | uniq >$(am__tfs); \
+	 done | sed 's,^\./,,' | sort -u >$(am__tfs); \
 	 if $$diff $(am__tmk) $(am__tfs) >$(am__tdf); then \
 	    result=0; \
+	    rm -f $(am__tmk) $(am__tfs) $(am__tdf); \
 	 else \
 	    echo '$@: list of tests in Makefile and on filesystem differ' >&2; \
 	    echo "+ $$diff in-makefile on-filesystem" >&2; \
 	    cat $(am__tdf) >&2; \
 	    result=1; \
 	 fi; \
-	 rm -f $(am__tmk) $(am__tfs) $(am__tdf); \
 	 exit $$result;
 
 .PHONY: clean-maintcheck-testslist-tmp
@@ -4257,6 +4334,7 @@
 clean-local: clean-local-check
 .PHONY: clean-local-check
 clean-local-check:
+	find . -type d ! -perm -700 -exec chmod u+rwx {} ';'
 	$(AM_V_GEN)$(PERL) $(srcdir)/t/ax/deltree.pl t/*.dir t/*/*.dir */t/*.dir
 
 # vim: ft=automake noet
@@ -4268,3 +4346,10 @@
 # Tell versions 3.59,3.63) of GNU make to not export all variables.
 # Otherwise a system limit (for SysV at least) may be exceeded.
 .NOEXPORT:
+
+# Tell GNU make to disable its built-in pattern rules.
+%:: %,v
+%:: RCS/%,v
+%:: RCS/%
+%:: s.%
+%:: SCCS/s.%

_service:tar_scm:automake-1.16.5.tar.xz/NEWS -> _service:tar_scm:automake-1.17.tar.xz/NEWS Changed

@@ -1,8 +1,155 @@
-For planned incompatibilities in a future Automake 2.0 release,
+For planned incompatibilities in a possible future Automake 2.0 release,
 please see NEWS-2.0 and start following the advice there now.
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+New in 1.17:
+
+* New features added
+
+  - AM_PATH_PYTHON will, after checking "python", prefer any Python 3
+    version (latest versions checked first) over any Python 2
+    version. If a specific version of Python 2 is still needed, the
+    $PYTHON variable should be set beforehand.
+
+  - AM_PATH_PYTHON will also search for Python versions 3.20 through 3.10.
+    It previously searched for 3.9 through 3.0. (bug#53530)
+
+  - RANLIB may be overridden on a per-target basis.
+
+  - AM_TEXI2FLAGS may be defined to pass extra flags to TEXI2DVI & TEXI2PDF.
+
+  - New option "posix" to emit the special target .POSIX for make.
+    (bug#55025, bug#67891)
+
+  - Systems with non-POSIX "rm -f" behavior are now supported, and the
+    prior intent to drop support for them has been reversed.
+    The ACCEPT_INFERIOR_RM_PROGRAM setting no longer exists.
+    (bug#10828)
+
+  - Variables using escaped \# will trigger portability warnings, but be
+    retained when appended.  GNU Make & BSD Makes are known to support it.
+    (bug#7610)
+
+  - GNU Make's default pattern rules are disabled, for speed and debugging.
+    (.SUFFIXES was already cleared.) (bug#64743)
+
+  - For Texinfo documents, if a .texi.in file exists, but no .texi, the
+    .texi.in will be read. Texinfo source files need not be present at
+    all, and if present, need not contain @setfilename. Then the file name
+    as given in the Makefile.am will be used.  If @setfilename is present,
+    it should be the basename of the Texinfo file, extended with .info.
+    (bug#54063)
+
+  - aclocal has a new option --aclocal-path to override $ACLOCAL_PATH.
+    (https://lists.gnu.org/archive/html/automake-patches/2022-01/msg00029.html)
+
+  - The missing script also supports autoreconf, autogen, and perl.
+    (https://lists.gnu.org/archive/html/automake-patches/2015-08/msg00000.html)
+
+  - test-suite.log now contains basic system information, and the
+    console message about bug reporting on failure has a bit more detail.
+    (bug#68746, bug#71421)
+
+  - When using the (default) "parallel" test driver, you can now omit the
+    output of skipped tests from test-suite.log by defining the
+    variable IGNORE_SKIPPED_LOGS to a non-empty value. (bug#71422)
+
+* Bugs fixed
+
+  - Generated file timestamp checks handle filesystems with subsecond
+    timestamp granularity dynamically, greatly speeding up the sleep
+    done by AC_OUTPUT when generating config.status (all packages) and
+    Automake's make check.
+    
+    However, this subsecond-mtime support requires an autom4te from
+    Autoconf 2.72 or later (or random test failures and other timing
+    problems may ensue), as well as a Perl, sleep program, make program,
+    and filesystem that all support subsecond resolution; otherwise, we
+    fall back to a two-second granularity, not even testing the (common)
+    1s case since that would induce a 2s delay for all configure scripts
+    in all packages on all systems that don't support subsecond mtimes.
+    
+    When everything is supported, a line "Features: subsecond-mtime" is
+    now printed by automake --version and autom4te --version. 
+    
+    To override this check and delay, e.g. to use 1 second:
+      am_cv_filesystem_timestamp_resolution=1
+      export am_cv_filesystem_timestamp_resolution
+      
+    (commit 720a11531,
+      https://lists.gnu.org/archive/html/automake-commit/2022-02/msg00009.html
+    then bug#60808, bug#64756, bug#67670, bug#68808, bug#71652,
+    history reviewed in
+      https://lists.gnu.org/archive/html/automake/2024-06/msg00054.html
+    and more info in surrounding threads.)
+
+  - The default value of $ARFLAGS is now "cr" instead of "cru", to better
+    support deterministic builds. (bug#20082)
+
+  - Automake's make dist now uses -9 instead of --best with gzip,
+    because Alpine gzip does not support --best. Also, GZIP_ENV is used
+    only for compression, not decompression, because of the same system.
+    (bug#68151)
+
+  - Dependency files are now empty, instead of "# dummy", for speed.
+    (https://lists.gnu.org/archive/html/automake/2022-05/msg00006.html)
+
+  - Compiling Python modules with Python 3.5+ uses multiple optimization
+    levels. (bug#38043)
+
+  - If the Python installation "scheme" is set to posix_local (Debian),
+    it is reset to either deb_system (if the prefix = /usr), or
+    posix_prefix (otherwise). (bug#54412, bug#64837)
+
+  - As a result of the Python scheme change, the installation directory
+    for Python files again defaults to "site-packages" under the usual
+    installation prefix, even on systems (generally Debian-based) that
+    would normally use the "dist-packages" subdirectory under
+    /usr/local.
+
+  - When compiling Emacs Lisp files, emacs is run with --no-site-file to
+    disable user config files that might hang or access the terminal;
+    and -Q is not used, since its support and behavior varies. (bug#58102)
+
+  - Emacs Lisp compilations respect silent make output.
+
+  - Automake no longer incorrectly warns that the POSIX make variables
+    $(*D) and the like are non-POSIX. Unfortunately, the make
+    implementations which do not correctly implement all the POSIX
+    variables are not detected, but this seems to have little impact
+    in practice. (bug#9587)
+
+  - Pass libtool tags OBJC and OBJCXX for the respective languages.
+    (bug#67539)
+
+  - distcleancheck ignores "silly rename" files (.nfs* .smb* .__afs*)
+    that can show up on network file systems.
+    (https://lists.gnu.org/archive/html/automake/2022-09/msg00002.html)
+
+  - Pass any options given to AM_PROG_LEX on to AC_PROG_LEX.
+    (bug#65600, bug#65730)
+
+  - aclocal: recognize ; as path separator on OS/2 and Windows. (bug#71534)
+
+  - Hash iterations with external effects now consistently sort keys.
+    (bug#25629, bug#46744)
+
+  - tests: avoid some declaration conflicts for lex et al. on SunOS.
+    (bug#34151 and others)
+
+  - tests: declare yyparse before use and use (void) parameter lists
+    instead of (), to placate C23. (bug#71425)
+
+  - Typos in code and other doc fixes. (bug#68003, bug#68004, et al.)
+
+* Obsolescence:
+
+  - py-compile no longer supports Python 0.x or 1.x versions.  Python 2.0,
+    released in 2000, is currently the minimum required version.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 New in 1.16.5:
 
 * Bugs fixed
@@ -297,7 +444,7 @@
         include $(srcdir)/fragment.am
         ...
 
-    If the use forgot to add data.txt and/or preproc.sh in the distribution
+    If the user forgot to add data.txt and/or preproc.sh in the distribution
     tarball, "make distcheck" would have erroneously succeeded!  This issue
     is now fixed.
 
@@ -385,7 +532,7 @@
   - The 'compile' script is now unconditionally required for all packages
     that perform C compilation (if you are using the '--add-missing'
     option, automake will fetch that script for you, so you shouldn't
-    need any explicit adjustment).  This new behaviour is needed to avoid
+    need any explicit adjustment).  This new behavior is needed to avoid
     obscure errors when the 'subdir-objects' option is used, and the
     compiler is an inferior one that doesn't grasp the combined use of
     both the "-c -o" options; see discussion about automake bug#13378 for
@@ -413,7 +560,7 @@
   - The AM_PROG_CC_C_O macro can still be called, albeit that should no
     longer be necessary. This macro is now just a thin wrapper around the
     Automake-enhanced AC_PROG_CC.  This means, among the other things,
-    that its behaviour is changed in three ways:
+    that its behavior is changed in three ways:
 
       1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
          macro behind the scenes.
@@ -738,7 +885,7 @@
   - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
     files in the same subdirectory; for example, byte-compiling of file
     'sub/foo.el' file will result in 'sub/foo.elc' rather than in
-    'foo.elc'.  This behaviour is backward-incompatible with older
+    'foo.elc'.  This behavior is backward-incompatible with older
     Automake versions, but it is more natural and more sane.  See also
     automake bug#7441.
 
@@ -795,7 +942,7 @@
   - The missing script has thus become useless as a (poor) way to work
     around the sketched-timestamps issues that can happen for projects
     that keep generated files committed in their VCS repository.  Such
-    projects are now encouraged to write a custom "fix-timestamps.sh"
+    projects are now encouraged to write a custom "fix-timestamp.sh"
     script to avoid such issues; a simple example is provided in the
     "CVS and generated files" chapter of the automake manual.
 
@@ -822,9 +969,8 @@
     include directories.  Formerly, one had to specify it with an explicit
     '-I' option to the 'aclocal' invocation.
 
-  - The special make variable ACLOCAL_AMFLAGS is deprecated; future
-    Automake versions will warn about its use, and later version will
-    remove support for it altogether.
+  - The special make variable ACLOCAL_AMFLAGS may be deprecated in
+    a future Automake major release.
 
 * The depcomp script:
 
@@ -832,7 +978,7 @@
 
   - Various internal refactorings.  They should cause no visible change,
     but the chance for regression is there anyway, so please report any
-    unexpected or suspicious behaviour.
+    unexpected or suspicious behavior.
 
   - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
     This should cause no problem, since icc 8.0 has been released in
@@ -914,7 +1060,7 @@
 
 * Miscellaneous changes:
 
-  - automake and aclocal no longer honours the 'perllibdir' environment
+  - automake and aclocal no longer honors the 'perllibdir' environment
     variable.  That had always been intended only as an hack required in
     the testsuite, not meant for any use beyond that.
 
@@ -950,7 +1096,7 @@
 * Miscellaneous changes:
 
   - The '.m4' files provided by Automake no longer define serial numbers.
-    This should cause no difference in the behaviour of aclocal though.
+    This should cause no difference in the behavior of aclocal though.
 
   - Some testsuite weaknesses and spurious failures have been fixed.
 
@@ -1223,7 +1369,7 @@
 
   - Slightly backward-incompatible change, relevant only for use of Yacc
     with C++: the extensions of the header files produced by the Yacc
-    rules are now modelled after the extension of the corresponding
+    rules are now modeled after the extension of the corresponding
     sources.  For example, yacc files named "foo.y++" and "bar.yy" will
     produce header files named "foo.h++" and "bar.hh" respectively, where
     they would have previously produced header files named simply "foo.h"
@@ -1574,12 +1720,12 @@
     and error out if `javadir' is undefined, instead of silently producing
     a broken Makefile.in.
 
-  - aclocal and automake now honour the configure-time definitions of
+  - aclocal and automake now honor the configure-time definitions of
     AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
 
   - The `install-info' recipe no longer tries to guess whether the
     `install-info' program is from Debian or from GNU, and adaptively
-    change its behaviour; this has proven to be frail and easy to
+    change its behavior; this has proven to be frail and easy to
     regress.
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -2719,7 +2865,7 @@
   - use `_dirstamp' when the file-system doesn't support `.dirstamp'
   - install/uninstall `*.i0-90-9'-style info files
   - more changes that affect only the Automake package (not its output)
-* Fix some incompatibilities with upcoming perl-5.10.
+* Fix some incompatibility with upcoming perl-5.10.
 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
   PACKAGE and VERSION.
 * depcomp fixes:
@@ -3102,7 +3248,7 @@
 
 -----
 
-Copyright (C) 1995-2021 Free Software Foundation, Inc.
+Copyright (C) 1995-2024 Free Software Foundation, Inc.
 
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by

_service:tar_scm:automake-1.16.5.tar.xz/NEWS-2.0 -> _service:tar_scm:automake-1.17.tar.xz/NEWS-2.0 Changed

@@ -1,18 +1,18 @@
-This file (NEWS-2.0) lists several incompatibilities planned for a
+This file (NEWS-2.0) lists incompatibility issues that may happen in a
 future Automake 2.0 release.
 
 However, the (few) current Automake maintainers have insufficient interest
 and energy to pursue the 2.0 release.  We have not even reviewed all
-existing bugs.  New maintainers are needed!  For more information about
-helping with Automake development:
+existing bugs.  New maintainers and developers are needed!  For more
+information about helping with Automake development:
 https://lists.gnu.org/archive/html/automake/2021-03/msg00018.html
 
-Therefore, there is no ETA for Automake 2.0, but it is not likely to be
+Therefore, there is no ETA for Automake 2.0, and it is not likely to be
 any time soon.  So moving these future issues to a separate file seemed
 warranted.  For more info, see the ./PLANS/ directory.
 
 
-* WARNING: Future backward-incompatibilities!
+* WARNING: Future backward-incompatibility!
 
   - Makefile recipes generated by Automake 2.0 will expect to use an
     'rm' program that doesn't complain when called without any non-option
@@ -31,7 +31,7 @@
     for Automake 2.0.
 
   - Automake 2.0 will require Autoconf 2.71 or later.  Exact
-    dependencies are unknowable at ths time.
+    dependencies are unknowable at this time.
 
   - Automake 2.0 will drop support for the long-deprecated 'configure.in'
     name for the Autoconf input file.  You are advised to start using the
@@ -39,8 +39,8 @@
 
   - The ACLOCAL_AMFLAGS special make variable will be fully deprecated in
     Automake 2.0: it will raise warnings in the "obsolete" category (but
-    still no hard error of course, for compatibilities with the many, many
-    packages that still relies on that variable).  You are advised to
+    still no hard error of course, for compatibility with the many, many
+    packages that still rely on that variable).  You are advised to
     start relying on the new Automake support for AC_CONFIG_MACRO_DIRS
     instead (which was introduced in Automake 1.13).
 
@@ -81,7 +81,7 @@
 
 -----
 
-Copyright (C) 1995-2021 Free Software Foundation, Inc.
+Copyright (C) 1995\(en2024 Free Software Foundation, Inc.
 
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by

_service:tar_scm:automake-1.16.5.tar.xz/PLANS/subdir-objects.txt -> _service:tar_scm:automake-1.17.tar.xz/PLANS/subdir-objects.txt Changed

@@ -1,7 +1,7 @@
 Summary
 -------
 
-We want to make the behaviour currently enabled by the 'subdir-objects'
+We want to make the behavior currently enabled by the 'subdir-objects'
 the default one, and in fact the *only* one, in Automake 2.0.
 See automake bug#13378: <https://debbugs.gnu.org/13378>.
 
@@ -15,12 +15,12 @@
 starting with commit 'user-dep-gen-branchpoint-56-g88b5959', and never
 made the default (likely to avoid backwards-compatibility issues).
 
-Since I believe the behaviour enabled by the 'subdir-objects' is the most
+Since I believe the behavior enabled by the 'subdir-objects' is the most
 useful one, and in fact the *only* natural one, I'd like to make it the
 only one available, simplifying the Automake implementation and APIs a
 little in the process.
 
-Alas, since this also means changing the default behaviour of Automake
+Alas, since this also means changing the default behavior of Automake
 ('subdir-objects' is not enabled by default, sadly), this means the
 transition path will be less smooth than I'd like.
 
@@ -58,8 +58,8 @@
 For automake 2.0
 ----------------
 
-Make the behaviour once activated by the 'subdir-object' option mandatory.
-With that change, we'll drop support for the "old" behaviour of having
+Make the behavior once activated by the 'subdir-object' option mandatory.
+With that change, we'll drop support for the "old" behavior of having
 object files derived from sources in a subdirectory being placed in the
 current directory rather than in that same subdirectory.

_service:tar_scm:automake-1.16.5.tar.xz/THANKS -> _service:tar_scm:automake-1.17.tar.xz/THANKS Changed

@@ -11,9 +11,11 @@
 Alan Modra                      amodra@bigpond.net.au
 Alex Hornby                     alex@anvil.co.uk
 Alex Unleashed                  unledev@gmail.com
+Alex Vong                       alexvong1995@gmail.com
+Alexander V. Lukyanov           lav@yars.free.net
 Alexander Mai                   st002279@hrzpub.tu-darmstadt.de
 Alexander Martens               alexander.martens@gtd.es
-Alexander V. Lukyanov           lav@yars.free.net
+Alexander Neumann               neumann@imt.uni-luebeck.de
 Alexander Turbov                zaufi@sendmail.ru
 Alexandre Duret-Lutz            duret_g@epita.fr
 Alexey Mahotkin                 alexm@hsys.msk.ru
@@ -38,7 +40,7 @@
 Assar Westerlund                assar@sics.se
 Axel Belinfante                 Axel.Belinfante@cs.utwente.nl
 Bas Wijnen                      shevek@fmf.nl
-Ben Pfaff                       blp@cs.standford.edu
+Ben Pfaff                       blp@cs.stanford.edu
 Benoit Sigoure                  tsuna@lrde.epita.fr
 Bernard Giroud                  bernard.giroud@creditlyonnais.ch
 Bernard Urban                   Bernard.Urban@meteo.fr
@@ -51,6 +53,7 @@
 Bob Proulx                      rwp@hprwp.fc.hp.com
 Bob Rossi                       bob@brasko.net
 Bobby Jack                      bobbykjack@yahoo.co.uk
+Bogdan                          bogdro_rep@gmx.us
 Boris Kolpackov                 boris@codesynthesis.com
 Braden N. McDaniel              braden@endoframe.com
 Brandon Black                   blblack@gmail.com
@@ -72,6 +75,7 @@
 Claudio Fontana                 sick_soul@yahoo.it
 Clifford Wolf                   clifford@clifford.at
 Colin Watson                    cjwatson@ubuntu.com
+Collin Funk                     collin.funk1@gmail.com
 Colomban Wendling               lists.ban@herbesfolles.org
 Dagobert Michelsen              dam@opencsw.org
 Daiki Ueno                      ueno@unixuser.org
@@ -80,7 +84,6 @@
 Daniel Jacobowitz               drow@false.org
 Daniel Kahn Gillmor             dkg@fifthhorseman.net
 Daniel Richard G.               skunk@iskunk.org
-Debarshi Ray                    rishi@gnu.org
 Dave Brolley                    brolley@redhat.com
 Dave Goodell                    goodell@mcs.anl.gov
 Dave Hart                       davehart@gmail.com
@@ -95,6 +98,7 @@
 David Wohlferd                  dw@limegreensocks.com
 David Zaroski                   cz253@cleveland.Freenet.Edu
 Dean Povey                      dpovey@wedgetail.com
+Debarshi Ray                    rishi@gnu.org
 Dennis J. Linse                 Dennis.J.Linse@SAIC.com
 Dennis Schridde                 devurandom@gmx.net
 Derek R. Price                  derek.price@openavenue.com
@@ -110,7 +114,6 @@
 Dmitry V. Levin                 ldv@altlinux.org
 Doug Evans                      devans@cygnus.com
 Duncan Gibson                   duncan@thermal.esa.int
-Dilyan Palauzov                 dilyan.palauzov@aegee.org
 Ed Hartnett                     ed@unidata.ucar.edu
 Eleftherios Gkioulekas          lf@amath.washington.edu
 Elena A. Vengerova              helen@oktetlabs.ru
@@ -137,6 +140,7 @@
 Francesco Salvestrini           salvestrini@gmail.com
 François Pinard                 pinard@iro.umontreal.ca
 Fred Fish                       fnf@ninemoons.com
+Frédéric Bérat                fberat@redhat.com
 Ganesan Rajagopal               rganesan@novell.com
 Garrett D'Amore                 garrett@qualcomm.com
 Garth Corral                    garthc@inktomi.com
@@ -164,10 +168,12 @@
 Hib Eris                        hib@hiberis.nl
 Hilko Bengen                    bengen@debian.org
 Holger Hans Peter Freyther      holger@freyther.de
+Hongxu Jia                      hongxu.jia@windriver.com
 Ian Lance Taylor                ian@cygnus.com
 Ignacy Gawedzki                 i@lri.fr
 Илья Н. Голубев                 gin@mo.msk.ru
 Imacat                          imacat@mail.imacat.idv.tw
+Ineiev                          ineiev@gnu.org
 Infirit                         infirit@gmail.com
 Inoue                           inoue@ainet.or.jp
 Jack Kelly                      jack@jackkelly.name
@@ -177,7 +183,7 @@
 James Henstridge                james@daa.com.au
 James R. Van Zandt              jrv@vanzandt.mv.com
 James Youngman                  jay@gnu.org
-Jan Engelhardt                  jengelh@medozas.de
+Jan Engelhardt                  jengelh@inai.de
 Janos Farkas                    chexum@shadow.banki.hu
 Jared Davis                     abiword@aiksaurus.com
 Jason DeVinney                  jasondevinney@gmail.com
@@ -207,9 +213,9 @@
 John Calcote                    john.calcote@gmail.com
 John F Trudeau                  JohnTrudeau@firsthealth.com
 John Pierce                     hawkfan@pyrotechnics.com
-John Ratliff                    autoconf@technoplaza.net
 John R. Cary                    cary@txcorp.com
 John W. Coomes                  jcoomes@eng.Sun.COM
+John Ratliff                    autoconf@technoplaza.net
 Jonathan L Peyton               jonathan.l.peyton@intel.com
 Jonathan Nieder                 jrnieder@gmail.com
 Joseph S. Myers                 joseph@codesourcery.com
@@ -244,7 +250,8 @@
 Libor Bukata                    libor.bukata@oracle.com
 Loulou Pouchet                  loulou@lrde.epita.fr
 Ludovic Courtès                 ludo@gnu.org
-Lukas Fleischer                        lfleischer@lfos.de
+Lukas Fleischer                 lfleischer@lfos.de
+Łukasz Stelmach              stlman@poczta.fm
 Luo Yi                          luoyi.ly@gmail.com
 Maciej Stachowiak               mstachow@mit.edu
 Maciej W. Rozycki               macro@ds2.pg.gda.pl
@@ -269,6 +276,7 @@
 Mathias Doreille                doreille@smr.ch
 Mathias Froehlich               M.Froehlich@science-computing.de
 Mathias Hasselmann              mathias.hasselmann@gmx.de
+Mathieu Lirzin                  mthl@gnu.org
 Matt Burgess                    matthew@linuxfromscratch.org
 Matt Leach                      mleach@cygnus.com
 Matthew D. Langston             langston@SLAC.Stanford.EDU
@@ -285,6 +293,7 @@
 Michael Hofmann                 mhofma@googlemail.com
 Michael Ploujnikov              ploujj@gmail.com
 Michael Zucchi                  notzed@gmail.com
+Michał Górny                    mgorny@gentoo.org
 Michel de Ruiter                mdruiter@cs.vu.nl
 Mike Castle                     dalgoda@ix.netcom.com
 Mike Frysinger                  vapier@gentoo.org
@@ -356,8 +365,8 @@
 Philipp A. Hartmann             philipp.hartmann@offis.de
 Пухальский Юрий Андреевич       pooh@cryptopro.ru
 Quentin Glidic                  sardemff7+gnu@sardemff7.net
-Rainer Orth                     ro@techfak.uni-bielefeld.de
 Rafael Laboissiere              laboissiere@psy.mpg.de
+Rainer Orth                     ro@techfak.uni-bielefeld.de
 Rainer Tammer                   tammer@tammer.net
 Raja R Harinath                 harinath@cs.umn.edu
 Ralf Corsepius                  ralf.corsepius@gmail.com
@@ -369,6 +378,7 @@
 Rich Wales                      richw@webcom.com
 Richard Boulton                 richard@tartarus.org
 Richard Dawe                    rich@phekda.freeserve.co.uk
+Richard Hopkins                 emacs@unbit.co.uk
 Richard W.M. Jones              rjones@redhat.com
 Rob Savoye                      rob@cygnus.com
 Robert Bihlmeyer                robbe@orcus.priv.at
@@ -399,8 +409,8 @@
 Sergey Vlasov                   vsu@mivlgu.murom.ru
 Seth Alves                      alves@hungry.com
 Shannon L. Brown                slbrow@sandia.gov
-Shuhei Amakawa                  sa264@cam.ac.uk
 Shigio Yamaguchi                shigio@tamacom.com
+Shuhei Amakawa                  sa264@cam.ac.uk
 Simon Josefsson                 jas@extundo.com
 Simon Richter                   sjr@debian.org
 Stefan Nordhausen               nordhaus@informatik.hu-berlin.de
@@ -424,7 +434,6 @@
 Thomas Morgan                   tmorgan@pobox.com
 Thomas Schwinge                 tschwinge@gnu.org
 Thomas Tanner                   tanner@ffii.org
-Toralf Förster                  toralf.foerster@gmx.de
 Tim Goodwin                     tjg@star.le.ac.uk
 Tim Landscheidt                 tim@tim-landscheidt.de
 Tim Mooney                      mooney@dogbert.cc.ndsu.NoDak.edu
@@ -432,9 +441,10 @@
 Tim Rice                        tim@multitalents.net
 Tim Van Holder                  tim.van.holder@pandora.be
 Tobias Hansen                   thansen@debian.org
-Toshio Kuratomi                 toshio@tiki-lounge.com
 Tom Epperly                     tepperly@llnl.gov
 Tom Rini                        tom_rini@mentor.com
+Toralf Förster                  toralf.foerster@gmx.de
+Toshio Kuratomi                 toshio@tiki-lounge.com
 Ulrich Drepper                  drepper@gnu.ai.mit.edu
 Ulrich Eckhardt                 eckhardt@satorlaser.com
 Václav Haisman                  V.Haisman@sh.cvut.cz
@@ -452,7 +462,8 @@
 William S Fulton                wsf@fultondesigns.co.uk
 Yann Droneaud                   ydroneaud@meuh.eu.org
 Younes Younes                   younes@cs.tu-berlin.de
-Zack Weinberg                   zackw@panix.com
+Yves Orton                      demerphq@gmail.com
+Zack Weinberg                   zack@owlfolio.org
 Zbigniew Jędrzejewski-Szmek     zbyszek@in.waw.pl
 Zoltan Rado                     z.rado@chello.hu

_service:tar_scm:automake-1.16.5.tar.xz/aclocal.m4 -> _service:tar_scm:automake-1.17.tar.xz/aclocal.m4 Changed

@@ -1,6 +1,6 @@
-# generated automatically by aclocal 1.16.5 -*- Autoconf -*-
+# generated automatically by aclocal 1.17 -*- Autoconf -*-
 
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -14,837 +14,26 @@
 m4_ifndef(AC_CONFIG_MACRO_DIRS, m4_defun(_AM_CONFIG_MACRO_DIRS, )m4_defun(AC_CONFIG_MACRO_DIRS, _AM_CONFIG_MACRO_DIRS($@)))
 m4_ifndef(AC_AUTOCONF_VERSION,
   m4_copy(m4_PACKAGE_VERSION, AC_AUTOCONF_VERSION))dnl
-m4_if(m4_defn(AC_AUTOCONF_VERSION), 2.71,,
-m4_warning(this file was generated for autoconf 2.71.
+m4_if(m4_defn(AC_AUTOCONF_VERSION), 2.72.24-c5b83,,
+m4_warning(this file was generated for autoconf 2.72.24-c5b83.
 You have another version of autoconf.  It may work, but is not guaranteed to.
 If you have problems, you may need to regenerate the build system entirely.
 To do so, use the procedure documented by the package, typically 'autoreconf'.))
 
-# Copyright (C) 2002-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_AUTOMAKE_VERSION(VERSION)
-# ----------------------------
-# Automake X.Y traces this macro to ensure aclocal.m4 has been
-# generated from the m4 files accompanying Automake X.Y.
-# (This private macro should not be called outside this file.)
-AC_DEFUN(AM_AUTOMAKE_VERSION,
-am__api_version='1.16'
-dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to
-dnl require some minimum version.  Point them to the right macro.
-m4_if($1, 1.16.5, ,
-      AC_FATAL(Do not call $0, use AM_INIT_AUTOMAKE($1).))dnl
-)
-
-# _AM_AUTOCONF_VERSION(VERSION)
-# -----------------------------
-# aclocal traces this macro to find the Autoconf version.
-# This is a private macro too.  Using m4_define simplifies
-# the logic in aclocal, which can simply ignore this definition.
-m4_define(_AM_AUTOCONF_VERSION, )
-
-# AM_SET_CURRENT_AUTOMAKE_VERSION
-# -------------------------------
-# Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced.
-# This function is AC_REQUIREd by AM_INIT_AUTOMAKE.
-AC_DEFUN(AM_SET_CURRENT_AUTOMAKE_VERSION,
-AM_AUTOMAKE_VERSION(1.16.5)dnl
-m4_ifndef(AC_AUTOCONF_VERSION,
-  m4_copy(m4_PACKAGE_VERSION, AC_AUTOCONF_VERSION))dnl
-_AM_AUTOCONF_VERSION(m4_defn(AC_AUTOCONF_VERSION)))
-
-# AM_AUX_DIR_EXPAND                                         -*- Autoconf -*-
-
-# Copyright (C) 2001-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# For projects using AC_CONFIG_AUX_DIR(foo), Autoconf sets
-# $ac_aux_dir to '$srcdir/foo'.  In other projects, it is set to
-# '$srcdir', '$srcdir/..', or '$srcdir/../..'.
-#
-# Of course, Automake must honor this variable whenever it calls a
-# tool from the auxiliary directory.  The problem is that $srcdir (and
-# therefore $ac_aux_dir as well) can be either absolute or relative,
-# depending on how configure is run.  This is pretty annoying, since
-# it makes $ac_aux_dir quite unusable in subdirectories: in the top
-# source directory, any form will work fine, but in subdirectories a
-# relative path needs to be adjusted first.
-#
-# $ac_aux_dir/missing
-#    fails when called from a subdirectory if $ac_aux_dir is relative
-# $top_srcdir/$ac_aux_dir/missing
-#    fails if $ac_aux_dir is absolute,
-#    fails when called from a subdirectory in a VPATH build with
-#          a relative $ac_aux_dir
-#
-# The reason of the latter failure is that $top_srcdir and $ac_aux_dir
-# are both prefixed by $srcdir.  In an in-source build this is usually
-# harmless because $srcdir is '.', but things will broke when you
-# start a VPATH build or use an absolute $srcdir.
-#
-# So we could use something similar to $top_srcdir/$ac_aux_dir/missing,
-# iff we strip the leading $srcdir from $ac_aux_dir.  That would be:
-#   am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*$.*$"`
-# and then we would define $MISSING as
-#   MISSING="\${SHELL} $am_aux_dir/missing"
-# This will work as long as MISSING is not called from configure, because
-# unfortunately $(top_srcdir) has no meaning in configure.
-# However there are other variables, like CC, which are often used in
-# configure, and could therefore not use this "fixed" $ac_aux_dir.
-#
-# Another solution, used here, is to always expand $ac_aux_dir to an
-# absolute PATH.  The drawback is that using absolute paths prevent a
-# configured tree to be moved without reconfiguration.
-
-AC_DEFUN(AM_AUX_DIR_EXPAND,
-AC_REQUIRE(AC_CONFIG_AUX_DIR_DEFAULT)dnl
-# Expand $ac_aux_dir to an absolute path.
-am_aux_dir=`cd "$ac_aux_dir" && pwd`
-)
-
-# AM_CONDITIONAL                                            -*- Autoconf -*-
-
-# Copyright (C) 1997-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_CONDITIONAL(NAME, SHELL-CONDITION)
-# -------------------------------------
-# Define a conditional.
-AC_DEFUN(AM_CONDITIONAL,
-AC_PREREQ(2.52)dnl
- m4_if($1, TRUE,  AC_FATAL($0: invalid condition: $1),
-       $1, FALSE, AC_FATAL($0: invalid condition: $1))dnl
-AC_SUBST($1_TRUE)dnl
-AC_SUBST($1_FALSE)dnl
-_AM_SUBST_NOTMAKE($1_TRUE)dnl
-_AM_SUBST_NOTMAKE($1_FALSE)dnl
-m4_define(_AM_COND_VALUE_$1, $2)dnl
-if $2; then
-  $1_TRUE=
-  $1_FALSE='#'
-else
-  $1_TRUE='#'
-  $1_FALSE=
-fi
-AC_CONFIG_COMMANDS_PRE(
-if test -z "${$1_TRUE}" && test -z "${$1_FALSE}"; then
-  AC_MSG_ERROR(conditional "$1" was never defined.
-Usually this means the macro was only invoked conditionally.)
-fi))
-
-# Do all the work for Automake.                             -*- Autoconf -*-
-
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This macro actually does too much.  Some checks are only needed if
-# your package does certain things.  But this isn't really a big deal.
-
-dnl Redefine AC_PROG_CC to automatically invoke _AM_PROG_CC_C_O.
-m4_define(AC_PROG_CC,
-m4_defn(AC_PROG_CC)
-_AM_PROG_CC_C_O
-)
-
-# AM_INIT_AUTOMAKE(PACKAGE, VERSION, NO-DEFINE)
-# AM_INIT_AUTOMAKE(OPTIONS)
-# -----------------------------------------------
-# The call with PACKAGE and VERSION arguments is the old style
-# call (pre autoconf-2.50), which is being phased out.  PACKAGE
-# and VERSION should now be passed to AC_INIT and removed from
-# the call to AM_INIT_AUTOMAKE.
-# We support both call styles for the transition.  After
-# the next Automake release, Autoconf can make the AC_INIT
-# arguments mandatory, and then we can depend on a new Autoconf
-# release and drop the old call support.
-AC_DEFUN(AM_INIT_AUTOMAKE,
-AC_PREREQ(2.65)dnl
-m4_ifdef(_$0_ALREADY_INIT,
-  m4_fatal($0 expanded multiple times
-m4_defn(_$0_ALREADY_INIT)),
-  m4_define(_$0_ALREADY_INIT, m4_expansion_stack))dnl
-dnl Autoconf wants to disallow AM_ names.  We explicitly allow
-dnl the ones we care about.
-m4_pattern_allow(^AM_A-Z+FLAGS$)dnl
-AC_REQUIRE(AM_SET_CURRENT_AUTOMAKE_VERSION)dnl
-AC_REQUIRE(AC_PROG_INSTALL)dnl
-if test "`cd $srcdir && pwd`" != "`pwd`"; then
-  # Use -I$(srcdir) only when $(srcdir) != ., so that make's output
-  # is not polluted with repeated "-I."
-  AC_SUBST(am__isrc, ' -I$(srcdir)')_AM_SUBST_NOTMAKE(am__isrc)dnl
-  # test to see if srcdir already configured
-  if test -f $srcdir/config.status; then
-    AC_MSG_ERROR(source directory already configured; run "make distclean" there first)
-  fi
-fi
-
-# test whether we have cygpath
-if test -z "$CYGPATH_W"; then
-  if (cygpath --version) >/dev/null 2>/dev/null; then
-    CYGPATH_W='cygpath -w'
-  else
-    CYGPATH_W=echo
-  fi
-fi
-AC_SUBST(CYGPATH_W)
-
-# Define the identity of the package.
-dnl Distinguish between old-style and new-style calls.
-m4_ifval($2,
-AC_DIAGNOSE(obsolete,
-             $0: two- and three-arguments forms are deprecated.)
-m4_ifval($3, _AM_SET_OPTION(no-define))dnl
- AC_SUBST(PACKAGE, $1)dnl
- AC_SUBST(VERSION, $2),
-_AM_SET_OPTIONS($1)dnl
-dnl Diagnose old-style AC_INIT with new-style AM_AUTOMAKE_INIT.
-m4_if(
-  m4_ifset(AC_PACKAGE_NAME, ok):m4_ifset(AC_PACKAGE_VERSION, ok),
-  ok:ok,,
-  m4_fatal(AC_INIT should be called with package and version arguments))dnl
- AC_SUBST(PACKAGE, 'AC_PACKAGE_TARNAME')dnl
- AC_SUBST(VERSION, 'AC_PACKAGE_VERSION'))dnl
-
-_AM_IF_OPTION(no-define,,
-AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE", Name of package)
- AC_DEFINE_UNQUOTED(VERSION, "$VERSION", Version number of package))dnl
-
-# Some tools Automake needs.
-AC_REQUIRE(AM_SANITY_CHECK)dnl
-AC_REQUIRE(AC_ARG_PROGRAM)dnl
-AM_MISSING_PROG(ACLOCAL, aclocal-${am__api_version})
-AM_MISSING_PROG(AUTOCONF, autoconf)
-AM_MISSING_PROG(AUTOMAKE, automake-${am__api_version})
-AM_MISSING_PROG(AUTOHEADER, autoheader)
-AM_MISSING_PROG(MAKEINFO, makeinfo)
-AC_REQUIRE(AM_PROG_INSTALL_SH)dnl
-AC_REQUIRE(AM_PROG_INSTALL_STRIP)dnl
-AC_REQUIRE(AC_PROG_MKDIR_P)dnl
-# For better backward compatibility.  To be removed once Automake 1.9.x
-# dies out for good.  For more background, see:
-# <https://lists.gnu.org/archive/html/automake/2012-07/msg00001.html>
-# <https://lists.gnu.org/archive/html/automake/2012-07/msg00014.html>
-AC_SUBST(mkdir_p, '$(MKDIR_P)')
-# We need awk for the "check" target (and possibly the TAP driver).  The
-# system "awk" is bad on some platforms.
-AC_REQUIRE(AC_PROG_AWK)dnl
-AC_REQUIRE(AC_PROG_MAKE_SET)dnl
-AC_REQUIRE(AM_SET_LEADING_DOT)dnl
-_AM_IF_OPTION(tar-ustar, _AM_PROG_TAR(ustar),
-	      _AM_IF_OPTION(tar-pax, _AM_PROG_TAR(pax),
-			     _AM_PROG_TAR(v7)))
-_AM_IF_OPTION(no-dependencies,,
-AC_PROVIDE_IFELSE(AC_PROG_CC,
-		  _AM_DEPENDENCIES(CC),
-		  m4_define(AC_PROG_CC,
-			     m4_defn(AC_PROG_CC)_AM_DEPENDENCIES(CC)))dnl
-AC_PROVIDE_IFELSE(AC_PROG_CXX,
-		  _AM_DEPENDENCIES(CXX),
-		  m4_define(AC_PROG_CXX,
-			     m4_defn(AC_PROG_CXX)_AM_DEPENDENCIES(CXX)))dnl
-AC_PROVIDE_IFELSE(AC_PROG_OBJC,
-		  _AM_DEPENDENCIES(OBJC),
-		  m4_define(AC_PROG_OBJC,
-			     m4_defn(AC_PROG_OBJC)_AM_DEPENDENCIES(OBJC)))dnl
-AC_PROVIDE_IFELSE(AC_PROG_OBJCXX,
-		  _AM_DEPENDENCIES(OBJCXX),
-		  m4_define(AC_PROG_OBJCXX,
-			     m4_defn(AC_PROG_OBJCXX)_AM_DEPENDENCIES(OBJCXX)))dnl
-)
-# Variables for tags utilities; see am/tags.am
-if test -z "$CTAGS"; then
-  CTAGS=ctags
-fi
-AC_SUBST(CTAGS)
-if test -z "$ETAGS"; then
-  ETAGS=etags
-fi
-AC_SUBST(ETAGS)
-if test -z "$CSCOPE"; then
-  CSCOPE=cscope
-fi
-AC_SUBST(CSCOPE)
-
-AC_REQUIRE(AM_SILENT_RULES)dnl
-dnl The testsuite driver may need to know about EXEEXT, so add the
-dnl 'am__EXEEXT' conditional if _AM_COMPILER_EXEEXT was seen.  This
-dnl macro is hooked onto _AC_COMPILER_EXEEXT early, see below.
-AC_CONFIG_COMMANDS_PRE(dnl
-m4_provide_if(_AM_COMPILER_EXEEXT,
-  AM_CONDITIONAL(am__EXEEXT, test -n "$EXEEXT")))dnl
-
-# POSIX will say in a future version that running "rm -f" with no argument
-# is OK; and we want to be able to make that assumption in our Makefile
-# recipes.  So use an aggressive probe to check that the usage we want is
-# actually supported "in the wild" to an acceptable degree.
-# See automake bug#10828.
-# To make any issue more visible, cause the running configure to be aborted
-# by default if the 'rm' program in use doesn't match our expectations; the
-# user can still override this though.
-if rm -f && rm -fr && rm -rf; then : OK; else
-  cat >&2 <<'END'
-Oops!
-
-Your 'rm' program seems unable to run without file operands specified
-on the command line, even when the '-f' option is present.  This is contrary
-to the behaviour of most rm programs out there, and not conforming with
-the upcoming POSIX standard: <http://austingroupbugs.net/view.php?id=542>
-
-Please tell bug-automake@gnu.org about your system, including the value
-of your $PATH and any error possibly output before this message.  This
-can help us improve future automake versions.
-
-END
-  if test x"$ACCEPT_INFERIOR_RM_PROGRAM" = x"yes"; then
-    echo 'Configuration will proceed anyway, since you have set the' >&2
-    echo 'ACCEPT_INFERIOR_RM_PROGRAM variable to "yes"' >&2
-    echo >&2
-  else
-    cat >&2 <<'END'
-Aborting the configuration process, to ensure you take notice of the issue.
-
-You can download and install GNU coreutils to get an 'rm' implementation
-that behaves properly: <https://www.gnu.org/software/coreutils/>.
-
-If you want to complete the configuration process using your problematic
-'rm' anyway, export the environment variable ACCEPT_INFERIOR_RM_PROGRAM
-to "yes", and re-run configure.
-
-END
-    AC_MSG_ERROR(Your 'rm' program is bad, sorry.)
-  fi
-fi
-dnl The trailing newline in this macro's definition is deliberate, for
-dnl backward compatibility and to allow trailing 'dnl'-style comments
-dnl after the AM_INIT_AUTOMAKE invocation. See automake bug#16841.
-)
-
-dnl Hook into '_AC_COMPILER_EXEEXT' early to learn its expansion.  Do not
-dnl add the conditional right here, as _AC_COMPILER_EXEEXT may be further
-dnl mangled by Autoconf and run in a shell conditional statement.
-m4_define(_AC_COMPILER_EXEEXT,
-m4_defn(_AC_COMPILER_EXEEXT)m4_provide(_AM_COMPILER_EXEEXT))
-
-# When config.status generates a header, we must update the stamp-h file.
-# This file resides in the same directory as the config header
-# that is generated.  The stamp files are numbered to have different names.
-
-# Autoconf calls _AC_AM_CONFIG_HEADER_HOOK (when defined) in the
-# loop where config.status creates the headers, so we can generate
-# our stamp files there.
-AC_DEFUN(_AC_AM_CONFIG_HEADER_HOOK,
-# Compute $1's index in $config_headers.
-_am_arg=$1
-_am_stamp_count=1
-for _am_header in $config_headers :; do
-  case $_am_header in
-    $_am_arg | $_am_arg:* )
-      break ;;
-    * )
-      _am_stamp_count=`expr $_am_stamp_count + 1` ;;
-  esac
-done
-echo "timestamp for $_am_arg" >`AS_DIRNAME("$_am_arg")`/stamp-h$_am_stamp_count)
-
-# Copyright (C) 2001-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_PROG_INSTALL_SH
-# ------------------
-# Define $install_sh.
-AC_DEFUN(AM_PROG_INSTALL_SH,
-AC_REQUIRE(AM_AUX_DIR_EXPAND)dnl
-if test x"${install_sh+set}" != xset; then
-  case $am_aux_dir in
-  *\ * | *\	*)
-    install_sh="\${SHELL} '$am_aux_dir/install-sh'" ;;
-  *)
-    install_sh="\${SHELL} $am_aux_dir/install-sh"
-  esac
-fi
-AC_SUBST(install_sh))
-
-# Copyright (C) 2003-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# Check whether the underlying file-system supports filenames
-# with a leading dot.  For instance MS-DOS doesn't.
-AC_DEFUN(AM_SET_LEADING_DOT,
-rm -rf .tst 2>/dev/null
-mkdir .tst 2>/dev/null
-if test -d .tst; then
-  am__leading_dot=.
-else
-  am__leading_dot=_
-fi
-rmdir .tst 2>/dev/null
-AC_SUBST(am__leading_dot))
-
-# Fake the existence of programs that GNU maintainers use.  -*- Autoconf -*-
-
-# Copyright (C) 1997-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_MISSING_PROG(NAME, PROGRAM)
-# ------------------------------
-AC_DEFUN(AM_MISSING_PROG,
-AC_REQUIRE(AM_MISSING_HAS_RUN)
-$1=${$1-"${am_missing_run}$2"}
-AC_SUBST($1))
-
-# AM_MISSING_HAS_RUN
-# ------------------
-# Define MISSING if not defined so far and test if it is modern enough.
-# If it is, set am_missing_run to use it, otherwise, to nothing.
-AC_DEFUN(AM_MISSING_HAS_RUN,
-AC_REQUIRE(AM_AUX_DIR_EXPAND)dnl
-AC_REQUIRE_AUX_FILE(missing)dnl
-if test x"${MISSING+set}" != xset; then
-  MISSING="\${SHELL} '$am_aux_dir/missing'"
-fi
-# Use eval to expand $SHELL
-if eval "$MISSING --is-lightweight"; then
-  am_missing_run="$MISSING "
-else
-  am_missing_run=
-  AC_MSG_WARN('missing' script is too old or missing)
-fi
-)
-
-# Helper functions for option handling.                     -*- Autoconf -*-
-
-# Copyright (C) 2001-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# _AM_MANGLE_OPTION(NAME)
-# -----------------------
-AC_DEFUN(_AM_MANGLE_OPTION,
-_AM_OPTION_m4_bpatsubst($1, ^a-zA-Z0-9_, _))
-
-# _AM_SET_OPTION(NAME)
-# --------------------
-# Set option NAME.  Presently that only means defining a flag for this option.
-AC_DEFUN(_AM_SET_OPTION,
-m4_define(_AM_MANGLE_OPTION($1), 1))
-
-# _AM_SET_OPTIONS(OPTIONS)
-# ------------------------
-# OPTIONS is a space-separated list of Automake options.
-AC_DEFUN(_AM_SET_OPTIONS,
-m4_foreach_w(_AM_Option, $1, _AM_SET_OPTION(_AM_Option)))
-
-# _AM_IF_OPTION(OPTION, IF-SET, IF-NOT-SET)
-# -------------------------------------------
-# Execute IF-SET if OPTION is set, IF-NOT-SET otherwise.
-AC_DEFUN(_AM_IF_OPTION,
-m4_ifset(_AM_MANGLE_OPTION($1), $2, $3))
-
-# Copyright (C) 1999-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# _AM_PROG_CC_C_O
-# ---------------
-# Like AC_PROG_CC_C_O, but changed for automake.  We rewrite AC_PROG_CC
-# to automatically call this.
-AC_DEFUN(_AM_PROG_CC_C_O,
-AC_REQUIRE(AM_AUX_DIR_EXPAND)dnl
-AC_REQUIRE_AUX_FILE(compile)dnl
-AC_LANG_PUSH(C)dnl
-AC_CACHE_CHECK(
-  whether $CC understands -c and -o together,
-  am_cv_prog_cc_c_o,
-  AC_LANG_CONFTEST(AC_LANG_PROGRAM())
-  # Make sure it works both with $CC and with simple cc.
-  # Following AC_PROG_CC_C_O, we do the test twice because some
-  # compilers refuse to overwrite an existing .o file with -o,
-  # though they will create one.
-  am_cv_prog_cc_c_o=yes
-  for am_i in 1 2; do
-    if AM_RUN_LOG($CC -c conftest.$ac_ext -o conftest2.$ac_objext) \
-         && test -f conftest2.$ac_objext; then
-      : OK
-    else
-      am_cv_prog_cc_c_o=no
-      break
-    fi
-  done
-  rm -f core conftest*
-  unset am_i)
-if test "$am_cv_prog_cc_c_o" != yes; then
-   # Losing compiler, so override with the script.
-   # FIXME: It is wrong to rewrite CC.
-   # But if we don't then we get into trouble of one sort or another.
-   # A longer-term fix would be to have automake use am__CC in this case,
-   # and then we could set am__CC="\$(top_srcdir)/compile \$(CC)"
-   CC="$am_aux_dir/compile $CC"
-fi
-AC_LANG_POP(C))
-
-# For backward compatibility.
-AC_DEFUN_ONCE(AM_PROG_CC_C_O, AC_REQUIRE(AC_PROG_CC))
-
-# Copyright (C) 2001-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_RUN_LOG(COMMAND)
-# -------------------
-# Run COMMAND, save the exit status in ac_status, and log it.
-# (This has been adapted from Autoconf's _AC_RUN_LOG macro.)
-AC_DEFUN(AM_RUN_LOG,
-{ echo "$as_me:$LINENO: $1" >&AS_MESSAGE_LOG_FD
-   ($1) >&AS_MESSAGE_LOG_FD 2>&AS_MESSAGE_LOG_FD
-   ac_status=$?
-   echo "$as_me:$LINENO: \$? = $ac_status" >&AS_MESSAGE_LOG_FD
-   (exit $ac_status); })
-
-# Check to make sure that the build environment is sane.    -*- Autoconf -*-
-
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_SANITY_CHECK
-# ---------------
-AC_DEFUN(AM_SANITY_CHECK,
-AC_MSG_CHECKING(whether build environment is sane)
-# Reject unsafe characters in $srcdir or the absolute working directory
-# name.  Accept space and tab only in the latter.
-am_lf='
-'
-case `pwd` in
-  *\\\"\#\$\&\'\`$am_lf*)
-    AC_MSG_ERROR(unsafe absolute working directory name);;
-esac
-case $srcdir in
-  *\\\"\#\$\&\'\`$am_lf\ \	*)
-    AC_MSG_ERROR(unsafe srcdir value: '$srcdir');;
-esac
-
-# Do 'set' in a subshell so we don't clobber the current shell's
-# arguments.  Must try -L first in case configure is actually a
-# symlink; some systems play weird games with the mod time of symlinks
-# (eg FreeBSD returns the mod time of the symlink's containing
-# directory).
-if (
-   am_has_slept=no
-   for am_try in 1 2; do
-     echo "timestamp, slept: $am_has_slept" > conftest.file
-     set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null`
-     if test "$*" = "X"; then
-	# -L didn't work.
-	set X `ls -t "$srcdir/configure" conftest.file`
-     fi
-     if test "$*" != "X $srcdir/configure conftest.file" \
-	&& test "$*" != "X conftest.file $srcdir/configure"; then
-
-	# If neither matched, then we have a broken ls.  This can happen
-	# if, for instance, CONFIG_SHELL is bash and it inherits a
-	# broken ls alias from the environment.  This has actually
-	# happened.  Such a system could not be considered "sane".
-	AC_MSG_ERROR(ls -t appears to fail.  Make sure there is not a broken
-  alias in your environment)
-     fi
-     if test "$2" = conftest.file || test $am_try -eq 2; then
-       break
-     fi
-     # Just in case.
-     sleep 1
-     am_has_slept=yes
-   done
-   test "$2" = conftest.file
-   )
-then
-   # Ok.
-   :
-else
-   AC_MSG_ERROR(newly created file is older than distributed files!
-Check your system clock)
-fi
-AC_MSG_RESULT(yes)
-# If we didn't sleep, we still need to ensure time stamps of config.status and
-# generated files are strictly newer.
-am_sleep_pid=
-if grep 'slept: no' conftest.file >/dev/null 2>&1; then
-  ( sleep 1 ) &
-  am_sleep_pid=$!
-fi
-AC_CONFIG_COMMANDS_PRE(
-  AC_MSG_CHECKING(that generated files are newer than configure)
-   if test -n "$am_sleep_pid"; then
-     # Hide warnings about reused PIDs.
-     wait $am_sleep_pid 2>/dev/null
-   fi
-   AC_MSG_RESULT(done))
-rm -f conftest.file
-)
-
-# Copyright (C) 2009-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_SILENT_RULES(DEFAULT)
-# --------------------------
-# Enable less verbose build rules; with the default set to DEFAULT
-# ("yes" being less verbose, "no" or empty being verbose).
-AC_DEFUN(AM_SILENT_RULES,
-AC_ARG_ENABLE(silent-rules, dnl
-AS_HELP_STRING(
-  --enable-silent-rules,
-  less verbose build output (undo: "make V=1"))
-AS_HELP_STRING(
-  --disable-silent-rules,
-  verbose build output (undo: "make V=0"))dnl
-)
-case $enable_silent_rules in @%:@ (((
-  yes) AM_DEFAULT_VERBOSITY=0;;
-   no) AM_DEFAULT_VERBOSITY=1;;
-    *) AM_DEFAULT_VERBOSITY=m4_if($1, yes, 0, 1);;
-esac
-dnl
-dnl A few 'make' implementations (e.g., NonStop OS and NextStep)
-dnl do not support nested variable expansions.
-dnl See automake bug#9928 and bug#10237.
-am_make=${MAKE-make}
-AC_CACHE_CHECK(whether $am_make supports nested variables,
-   am_cv_make_support_nested_variables,
-   if AS_ECHO('TRUE=$(BAR$(V))
-BAR0=false
-BAR1=true
-V=1
-am__doit:
-	@$(TRUE)
-.PHONY: am__doit') | $am_make -f - >/dev/null 2>&1; then
-  am_cv_make_support_nested_variables=yes
-else
-  am_cv_make_support_nested_variables=no
-fi)
-if test $am_cv_make_support_nested_variables = yes; then
-  dnl Using '$V' instead of '$(V)' breaks IRIX make.
-  AM_V='$(V)'
-  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
-else
-  AM_V=$AM_DEFAULT_VERBOSITY
-  AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY
-fi
-AC_SUBST(AM_V)dnl
-AM_SUBST_NOTMAKE(AM_V)dnl
-AC_SUBST(AM_DEFAULT_V)dnl
-AM_SUBST_NOTMAKE(AM_DEFAULT_V)dnl
-AC_SUBST(AM_DEFAULT_VERBOSITY)dnl
-AM_BACKSLASH='\'
-AC_SUBST(AM_BACKSLASH)dnl
-_AM_SUBST_NOTMAKE(AM_BACKSLASH)dnl
-)
-
-# Copyright (C) 2001-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# AM_PROG_INSTALL_STRIP
-# ---------------------
-# One issue with vendor 'install' (even GNU) is that you can't
-# specify the program used to strip binaries.  This is especially
-# annoying in cross-compiling environments, where the build's strip
-# is unlikely to handle the host's binaries.
-# Fortunately install-sh will honor a STRIPPROG variable, so we
-# always use install-sh in "make install-strip", and initialize
-# STRIPPROG with the value of the STRIP variable (set by the user).
-AC_DEFUN(AM_PROG_INSTALL_STRIP,
-AC_REQUIRE(AM_PROG_INSTALL_SH)dnl
-# Installed binaries are usually stripped using 'strip' when the user
-# run "make install-strip".  However 'strip' might not be the right
-# tool to use in cross-compilation environments, therefore Automake
-# will honor the 'STRIP' environment variable to overrule this program.
-dnl Don't test for $cross_compiling = yes, because it might be 'maybe'.
-if test "$cross_compiling" != no; then
-  AC_CHECK_TOOL(STRIP, strip, :)
-fi
-INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s"
-AC_SUBST(INSTALL_STRIP_PROGRAM))
-
-# Copyright (C) 2006-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# _AM_SUBST_NOTMAKE(VARIABLE)
-# ---------------------------
-# Prevent Automake from outputting VARIABLE = @VARIABLE@ in Makefile.in.
-# This macro is traced by Automake.
-AC_DEFUN(_AM_SUBST_NOTMAKE)
-
-# AM_SUBST_NOTMAKE(VARIABLE)
-# --------------------------
-# Public sister of _AM_SUBST_NOTMAKE.
-AC_DEFUN(AM_SUBST_NOTMAKE, _AM_SUBST_NOTMAKE($@))
-
-# Check how to create a tarball.                            -*- Autoconf -*-
-
-# Copyright (C) 2004-2021 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# _AM_PROG_TAR(FORMAT)
-# --------------------
-# Check how to create a tarball in format FORMAT.
-# FORMAT should be one of 'v7', 'ustar', or 'pax'.
-#
-# Substitute a variable $(am__tar) that is a command
-# writing to stdout a FORMAT-tarball containing the directory
-# $tardir.
-#     tardir=directory && $(am__tar) > result.tar
-#
-# Substitute a variable $(am__untar) that extract such
-# a tarball read from stdin.
-#     $(am__untar) < result.tar
-#
-AC_DEFUN(_AM_PROG_TAR,
-# Always define AMTAR for backward compatibility.  Yes, it's still used
-# in the wild :-(  We should find a proper way to deprecate it ...
-AC_SUBST(AMTAR, '$${TAR-tar}')
-
-# We'll loop over all known methods to create a tar archive until one works.
-_am_tools='gnutar m4_if($1, ustar, plaintar) pax cpio none'
-
-m4_if($1, v7,
-  am__tar='$${TAR-tar} chof - "$$tardir"' am__untar='$${TAR-tar} xf -',
-
-  m4_case($1,
-    ustar,
-     # The POSIX 1988 'ustar' format is defined with fixed-size fields.
-      # There is notably a 21 bits limit for the UID and the GID.  In fact,
-      # the 'pax' utility can hang on bigger UID/GID (see automake bug#8343
-      # and bug#13588).
-      am_max_uid=2097151 # 2^21 - 1
-      am_max_gid=$am_max_uid
-      # The $UID and $GID variables are not portable, so we need to resort
-      # to the POSIX-mandated id(1) utility.  Errors in the 'id' calls
-      # below are definitely unexpected, so allow the users to see them
-      # (that is, avoid stderr redirection).
-      am_uid=`id -u || echo unknown`
-      am_gid=`id -g || echo unknown`
-      AC_MSG_CHECKING(whether UID '$am_uid' is supported by ustar format)
-      if test $am_uid -le $am_max_uid; then
-         AC_MSG_RESULT(yes)
-      else
-         AC_MSG_RESULT(no)
-         _am_tools=none
-      fi
-      AC_MSG_CHECKING(whether GID '$am_gid' is supported by ustar format)
-      if test $am_gid -le $am_max_gid; then
-         AC_MSG_RESULT(yes)
-      else
-        AC_MSG_RESULT(no)
-        _am_tools=none
-      fi,
-
-  pax,
-    ,
-
-  m4_fatal(Unknown tar format))
-
-  AC_MSG_CHECKING(how to create a $1 tar archive)
-
-  # Go ahead even if we have the value already cached.  We do so because we
-  # need to set the values for the 'am__tar' and 'am__untar' variables.
-  _am_tools=${am_cv_prog_tar_$1-$_am_tools}
-
-  for _am_tool in $_am_tools; do
-    case $_am_tool in
-    gnutar)
-      for _am_tar in tar gnutar gtar; do
-        AM_RUN_LOG($_am_tar --version) && break
-      done
-      am__tar="$_am_tar --format=m4_if($1, pax, posix, $1) -chf - "'"$$tardir"'
-      am__tar_="$_am_tar --format=m4_if($1, pax, posix, $1) -chf - "'"$tardir"'
-      am__untar="$_am_tar -xf -"
-      ;;
-    plaintar)
-      # Must skip GNU tar: if it does not support --format= it doesn't create
-      # ustar tarball either.
-      (tar --version) >/dev/null 2>&1 && continue
-      am__tar='tar chf - "$$tardir"'
-      am__tar_='tar chf - "$tardir"'
-      am__untar='tar xf -'
-      ;;
-    pax)
-      am__tar='pax -L -x $1 -w "$$tardir"'
-      am__tar_='pax -L -x $1 -w "$tardir"'
-      am__untar='pax -r'
-      ;;
-    cpio)
-      am__tar='find "$$tardir" -print | cpio -o -H $1 -L'
-      am__tar_='find "$tardir" -print | cpio -o -H $1 -L'
-      am__untar='cpio -i -H $1 -d'
-      ;;
-    none)
-      am__tar=false
-      am__tar_=false
-      am__untar=false
-      ;;
-    esac
-
-    # If the value was cached, stop now.  We just wanted to have am__tar
-    # and am__untar set.
-    test -n "${am_cv_prog_tar_$1}" && break
-
-    # tar/untar a dummy directory, and stop if the command works.
-    rm -rf conftest.dir
-    mkdir conftest.dir
-    echo GrepMe > conftest.dir/file
-    AM_RUN_LOG(tardir=conftest.dir && eval $am__tar_ >conftest.tar)
-    rm -rf conftest.dir
-    if test -s conftest.tar; then
-      AM_RUN_LOG($am__untar <conftest.tar)
-      AM_RUN_LOG(cat conftest.dir/file)
-      grep GrepMe conftest.dir/file >/dev/null 2>&1 && break
-    fi
-  done
-  rm -rf conftest.dir
-
-  AC_CACHE_VAL(am_cv_prog_tar_$1, am_cv_prog_tar_$1=$_am_tool)
-  AC_MSG_RESULT($am_cv_prog_tar_$1))
-
-AC_SUBST(am__tar)
-AC_SUBST(am__untar)
-) # _AM_PROG_TAR
-
+m4_include(m4/amversion.m4)
+m4_include(m4/auxdir.m4)
+m4_include(m4/cond.m4)
+m4_include(m4/init.m4)
+m4_include(m4/install-sh.m4)
+m4_include(m4/lead-dot.m4)
+m4_include(m4/missing.m4)
+m4_include(m4/options.m4)
+m4_include(m4/prog-cc-c-o.m4)
+m4_include(m4/rmf.m4)
+m4_include(m4/runlog.m4)
+m4_include(m4/sanity.m4)
+m4_include(m4/silent.m4)
+m4_include(m4/strip.m4)
+m4_include(m4/substnot.m4)
+m4_include(m4/tar.m4)
+m4_include(m4/xargsn.m4)

_service:tar_scm:automake-1.16.5.tar.xz/bin/aclocal.in -> _service:tar_scm:automake-1.17.tar.xz/bin/aclocal.in Changed

@@ -1,7 +1,7 @@
 #!@PERL@
 # aclocal - create aclocal.m4 by scanning configure.ac      -*- perl -*-
 # @configure_input@
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -62,11 +62,12 @@
 # @user_includes can be augmented with -I or AC_CONFIG_MACRO_DIRS.
 # @automake_includes can be reset with the '--automake-acdir' option.
 # @system_includes can be augmented with the 'dirlist' file or the
-# ACLOCAL_PATH environment variable, and reset with the '--system-acdir'
-# option.
+# --aclocal-path option/ACLOCAL_PATH environment variable, and reset
+# with the '--system-acdir' option.
 my @user_includes = ();
 my @automake_includes = ('@datadir@/aclocal-' . $APIVERSION);
 my @system_includes = ('@datadir@/aclocal');
+my $aclocal_path = '';
 
 # Whether we should copy M4 file in $user_includes0.
 my $install = 0;
@@ -233,7 +234,7 @@
 # Check macros in acinclude.m4.  If one is not used, warn.
 sub check_acinclude ()
 {
-  foreach my $key (keys %map)
+  foreach my $key (sort keys %map)
     {
       # FIXME: should print line number of acinclude.m4.
       msg ('syntax', "macro '$key' defined in acinclude.m4 but never used")
@@ -802,7 +803,7 @@
 		   # Do not trace $1 for all other macros as we do
 		   # not need it and it might contains harmful
 		   # characters (like newlines).
-		   (map { "--trace='$_:\$f::\$n'" } (keys %macro_seen)));
+		   (map { "--trace='$_:\$f::\$n'" } (sort keys %macro_seen)));
 
   verb "running WARNINGS=$ENV{WARNINGS} $traces $configure_ac";
 
@@ -1031,6 +1032,8 @@
 
 Options:
       --automake-acdir=DIR  directory holding automake-provided m4 files
+      --aclocal-path=PATH   colon-separated list of directories to
+                              search for third-party local files
       --system-acdir=DIR    directory holding third-party system-wide files
       --diff=COMMAND      run COMMAND diff -u on M4 files that would be
                             changed (implies --install and --dry-run)
@@ -1044,12 +1047,41 @@
                               third-party m4 files, then exit
       --verbose             don't be silent
       --version             print version number, then exit
-  -W, --warnings=CATEGORY   report the warnings falling in CATEGORY
+  -W, --warnings=CATEGORY   report the warnings falling in CATEGORY,
+                              defaults to $WARNINGS
+
 EOF
 
   print Automake::ChannelDefs::usage (), "\n";
 
+  # This output depends on the current environment, and when generating the man
+  # pages during Automake compilation, the environment is set to local values.
+  # So don't include it in the installed man page.
+  if (!$ENV{AUTOMAKE_HELP2MAN}) {
+    my $aclocal_automake_dir_env = $ENV{"ACLOCAL_AUTOMAKE_DIR"} || "";
+    my $aclocal_path_env = $ENV{"ACLOCAL_PATH"} || "";
+    print <<"EOF";
+
+m4 search paths (in order):
+      user includes: @user_includes
+  automake includes: @automake_includes
+    system includes: @system_includes
+       aclocal path: $aclocal_path
+
+Environment variable settings, for reference:
+  \$ACLOCAL_AUTOMAKE_DIR:    $aclocal_automake_dir_env
+  \$ACLOCAL_PATH:            $aclocal_path_env
+EOF
+  }
+  # The above listing of paths is rather a mess.  Because we don't
+  # compute all paths before outputting the help, the aclocal paths and
+  # ac_config_macro_dirs are not added to the system includes.  And
+  # because we don't keep track separately of command line values given
+  # to -I and the other options, we can't report them separately from
+  # the environment variables.
+
   print <<'EOF';
+
 Report bugs to <@PACKAGE_BUGREPORT@>.
 GNU Automake home page: <@PACKAGE_URL@>.
 General help using GNU software: <https://www.gnu.org/gethelp/>.
@@ -1086,6 +1118,7 @@
      'version'		=> \&version,
      'system-acdir=s'	=> sub { shift; @system_includes = @_; },
      'automake-acdir=s'	=> sub { shift; @automake_includes = @_; },
+     'aclocal-path=s'   => sub { shift; $aclocal_path = $_0; },
      'diff:s'		=> \$diff_command,
      'dry-run'		=> \$dry_run,
      'force'		=> \$force_output,
@@ -1140,16 +1173,23 @@
     }
 }
 
-# Add any directory listed in the 'ACLOCAL_PATH' environment variable
-# to the list of system include directories.
+# Add any directory listed in $aclocal_path to the list of system
+# include directories.
 sub parse_ACLOCAL_PATH ()
 {
-  return if not defined $ENV{"ACLOCAL_PATH"};
+  return if not $aclocal_path;
+  
   # Directories in ACLOCAL_PATH should take precedence over system
   # directories, so we use unshift.  However, directories that
   # come first in ACLOCAL_PATH take precedence over directories
   # coming later, which is why the result of split is reversed.
-  foreach my $dir (reverse split /:/, $ENV{"ACLOCAL_PATH"})
+  
+  # OS/2 and Windows (but not Cygwin, etc.) use ; for the path separator.
+  # Possibly it would be cleaner to use path_sep from Config,
+  # but this seems simpler.
+  my $path_sep = $^O =~ /^(os2|mswin)/i ? ';' : ':';
+  
+  foreach my $dir (reverse split $path_sep, $aclocal_path)
     {
       unshift (@system_includes, $dir) if $dir ne '' && -d $dir;
     }
@@ -1166,10 +1206,12 @@
 
 @automake_includes = ($ENV{"ACLOCAL_AUTOMAKE_DIR"})
   if (exists $ENV{"ACLOCAL_AUTOMAKE_DIR"});
+$aclocal_path = ($ENV{"ACLOCAL_PATH"})
+  if (exists $ENV{"ACLOCAL_PATH"});
 
 parse_WARNINGS;		    # Parse the WARNINGS environment variable.
 parse_arguments;
-parse_ACLOCAL_PATH;
+parse_ACLOCAL_PATH;	    # Should come after parse arguments.
 $configure_ac = require_configure_ac;
 
 # We may have to rerun aclocal if some file have been installed, but
@@ -1209,7 +1251,7 @@
               "-I options nor AC_CONFIG_MACRO_DIR{,S} m4 macro(s)";
       }
 
-    last if write_aclocal ($output_file, keys %macro_traced);
+    last if write_aclocal ($output_file, sort keys %macro_traced);
     last if $dry_run;
   }
 check_acinclude;

_service:tar_scm:automake-1.16.5.tar.xz/bin/automake.in -> _service:tar_scm:automake-1.17.tar.xz/bin/automake.in Changed

@@ -1,7 +1,7 @@
 #!@PERL@
 # automake - create Makefile.in from Makefile.am            -*- perl -*-
 # @configure_input@
-# Copyright (C) 1994-2021 Free Software Foundation, Inc.
+# Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -739,6 +739,7 @@
 		   'compiler' => 'OBJCCOMPILE',
 		   'compile_flag' => '-c',
 		   'output_flag' => '-o',
+		   'libtool_flag' => 'OBJC',
 		   'lder' => 'OBJCLD',
 		   'ld' => '$(OBJC)',
 		   'pure' => 1,
@@ -757,6 +758,7 @@
 		   'compiler' => 'OBJCXXCOMPILE',
 		   'compile_flag' => '-c',
 		   'output_flag' => '-o',
+		   'libtool_flag' => 'OBJCXX',
 		   'lder' => 'OBJCXXLD',
 		   'ld' => '$(OBJCXX)',
 		   'pure' => 1,
@@ -1556,7 +1558,7 @@
     # suffix rule was learned), don't bother with the C stuff.  But if
     # anything else creeps in, then use it.
     my @languages_seen = map { $languages{$extension_map{$_}}->name }
-                             (keys %extension_seen);
+                             (sort keys %extension_seen);
     @languages_seen = uniq (@languages_seen);
     $needs_c = 1 if @languages_seen > 1;
     if ($need_link || $needs_c)
@@ -1841,7 +1843,7 @@
               else
                 {
                   # Since the next major version of automake (2.0) will
-                  # make the behaviour so far only activated with the
+                  # make the behavior so far only activated with the
                   # 'subdir-objects' option mandatory, it's better if we
                   # start warning users not using that option.
                   # As suggested by Peter Johansson, we strive to avoid
@@ -1864,7 +1866,7 @@
 behavior may change in a future Automake major version, with object
 files being placed in the same subdirectory as the corresponding sources.
 You are advised to start using 'subdir-objects' option throughout your
-project, to avoid future incompatibilities.
+project, to avoid future incompatibility.
 EOF
                 }
 	    }
@@ -2062,7 +2064,7 @@
 	# dependency code).
         # Properly flatten multiple adjacent slashes, as Solaris 10 make
         # might fail over them in an include statement.
-        # Leading double slashes may be special, as per Posix, so deal
+        # Leading double slashes may be special, as per POSIX, so deal
         # with them carefully.
         if ($lang && $lang->autodep ne 'no')
         {
@@ -2289,7 +2291,7 @@
 	       # Skip -dlopen and -dlpreopen; these are explicitly allowed
 	       # for Libtool libraries or programs.  (Actually we are a bit
 	       # lax here since this code also applies to non-libtool
-	       # libraries or programs, for which -dlopen and -dlopreopen
+	       # libraries or programs, for which -dlopen and -dlpreopen
 	       # are pure nonsense.  Diagnosing this doesn't seem very
 	       # important: the developer will quickly get complaints from
 	       # the linker.)
@@ -2561,7 +2563,7 @@
   @ltliblist = am_install_var ('ltlib', 'LTLIBRARIES',
 			       'noinst', 'lib', 'pkglib', 'check');
 
-  # Record duplications that may arise after canonicalization of the
+  # Record duplicates that may arise after canonicalization of the
   # base names, in order to prevent object file clashes in the presence
   # of target-specific *FLAGS
   my @targetlist = (@proglist, @liblist, @ltliblist);
@@ -2674,7 +2676,7 @@
     }
 
   define_variable ('AR', 'ar', INTERNAL);
-  define_variable ('ARFLAGS', 'cru', INTERNAL);
+  define_variable ('ARFLAGS', 'cr', INTERNAL);
   define_verbose_tagvar ('AR');
 
   foreach my $pair (@liblist)
@@ -2704,12 +2706,16 @@
       # Canonicalize names and check for misspellings.
       my $xlib = check_canonical_spelling ($onelib, '_LIBADD', '_SOURCES',
                                            '_OBJECTS', '_DEPENDENCIES',
-                                           '_AR');
+                                           '_AR', '_RANLIB');
 
       if (! var ($xlib . '_AR'))
 	{
 	  define_variable ($xlib . '_AR', '$(AR) $(ARFLAGS)', $where);
 	}
+      if (! var ($xlib . '_RANLIB'))
+	{
+	  define_variable ($xlib . '_RANLIB', '$(RANLIB)', $where);
+	}
 
       # Generate support for conditional object inclusion in
       # libraries.
@@ -3057,9 +3063,24 @@
 sub scan_texinfo_file
 {
   my ($filename) = @_;
+  my $orig_filename = $filename;
 
+  # If the source file doesn't exist, we'll fall back below.
+  if (! -e $filename)
+    {
+      if (-e ($filename . '.in'))
+        {
+          # $filename.texi.in exists: assume $filename.texi is generated
+          # and parse $filename.texi.in as the real input.
+          $filename .= '.in';
+        }
+      else
+        {
+          $filename = '/dev/null';
+        }
+    }
   my $texi = new Automake::XFile "< $filename";
-  verb "reading $filename";
+  verb "reading texinfo_file $filename";
 
   my ($outfile, $vfile);
   while ($_ = $texi->getline)
@@ -3071,6 +3092,18 @@
 	  # to use @setfilename...)
 	  next if $outfile;
 
+	  # Although we notice the @setfilename, and the rules are
+	  # adjusted to sort of use it, they don't actually work.
+	  # Specifically, if foo.texi contains @setfilename bar.info,
+	  # the generated .texi.info suffix rule will not run.
+	  #
+	  # Also, although we change the .info target to be bar.info,
+	  # the HTML(S) variable/etc. is not changed.
+	  #
+	  # Since @setfilename is optional nowadays, doesn't seem worth
+	  # the trouble to handle (which looks to be nontrivial).
+	  # https://bugs.gnu.org/54063
+
 	  $outfile = $1;
 	  if (index ($outfile, '.') < 0)
 	    {
@@ -3094,8 +3127,10 @@
 
   if (! $outfile)
     {
-      # Replace a .texi extension with .info
-      $outfile = basename($filename);
+      # If no explicit @setfilename, use the original filename as passed
+      # (not foo.texi.in or /dev/null) in the generated rules, while
+      # replacing any extension (presumably .texi) with .info.
+      $outfile = basename ($orig_filename);
       $outfile =~ s/\.^.+$//;
       $outfile .= '.info';
     }
@@ -3131,6 +3166,10 @@
   # but just remember that some logic deeper in Automake will not
   # output the same rule twice); while the later need to be output for
   # each Texinfo source.
+  #
+  # NB: The makeinfoflags is currently passed to makeinfo and texi2dvi, so
+  # make sure that it only utilizes compatible flags.  Best to stick to -I.
+  # Changing this requires updating lib/am/texibuild.am.
   my $generic;
   my $makeinfoflags;
   my $sdir = dirname $source;
@@ -3344,8 +3383,8 @@
       #     in the source-tree (when they are distributed, that is).
       #   * Keeping a fresher copy of distributed files in the
       #     build tree can be annoying during development because
-      #     - if the files is kept under CVS, you really want it
-      #       to be updated in the source tree
+      #     - if the files are kept under version control, you really
+      #        want them to be updated in the source tree, and
       #     - it is confusing that 'make distclean' does not erase
       #       all files in the build tree.
       #
@@ -3648,14 +3687,14 @@
       my $trans_mans = $have_trans || exists $trans_sections{$section};
       my (%notrans_this_sect, %trans_this_sect);
       my $expr = 'man' . $section . '_MANS';
-      foreach my $varname (keys %notrans_sect_vars)
+      foreach my $varname (keys %notrans_sect_vars) # sort keys not needed
 	{
 	  if ($varname =~ /$expr/)
 	    {
 	      $notrans_this_sect{$varname} = 1;
 	    }
 	}
-      foreach my $varname (keys %trans_sect_vars)
+      foreach my $varname (keys %trans_sect_vars) # sort keys not needed
 	{
 	  if ($varname =~ /$expr/)
 	    {
@@ -4723,12 +4762,7 @@
       prog_error 'invalid entry in %clean_files'
 	unless exists $rms{$when};
 
-      my $rm = "rm -f $file";
-      # If file is a variable, make sure when don't call 'rm -f' without args.
-      $rm ="test -z \"$file\" || $rm"
-	if ($file =~ /^\s*\$($.*$|\{.*\})\s*$/);
-
-      push @{$rms{$when}}, "\t-$rm\n";
+      push @{$rms{$when}}, "\t-\$(am__rm_f) $file\n";
     }
 
   $output_rules .= file_contents
@@ -4876,7 +4910,7 @@
     }
   # The "test driver" program, deputed to handle tests protocol used by
   # test scripts.  By default, it's assumed that no protocol is used, so
-  # we fall back to the old behaviour, implemented by the 'test-driver'
+  # we fall back to the old behavior, implemented by the 'test-driver'
   # auxiliary script.
   if (! var "${pfx}LOG_DRIVER")
     {
@@ -5408,8 +5442,9 @@
 	  error ($where,
 		 "version mismatch.  This is Automake $VERSION,\n" .
 		 "but the definition used by this AM_INIT_AUTOMAKE\n" .
-		 "comes from Automake $args1.  You should recreate\n" .
-		 "aclocal.m4 with aclocal and run automake again.\n",
+		 "comes from Automake $args1.  You should run\n" .
+		 "autoreconf -f (or otherwise erase all old files, run\n" .
+		 "aclocal to recreate aclocal.m4, and rerun automake).",
 		 # $? = 63 is used to indicate version mismatch to missing.
 		 exit_code => 63)
 	    if $VERSION ne $args1;
@@ -5587,9 +5622,10 @@
 	  if (-f 'aclocal.m4')
 	    {
 	      error ($seen_init_automake,
-		     "your implementation of AM_INIT_AUTOMAKE comes from " .
-		     "an\nold Automake version.  You should recreate " .
-		     "aclocal.m4\nwith aclocal and run automake again",
+                     "your implementation of AM_INIT_AUTOMAKE comes from\n" .
+                     "an old Automake version.  You should run\n" .
+                     "autoreconf -f (or otherwise erase all old files, run\n" .
+                     "aclocal to recreate aclocal.m4, and rerun automake).",
 		     # $? = 63 is used to indicate version mismatch to missing.
 		     exit_code => 63);
 	    }
@@ -5598,8 +5634,8 @@
 	      error ($seen_init_automake,
 		     "no proper implementation of AM_INIT_AUTOMAKE was " .
 		     "found,\nprobably because aclocal.m4 is missing.\n" .
-		     "You should run aclocal to create this file, then\n" .
-		     "run automake again");
+		     "You should run autoreconf -f (or aclocal to create\n" .
+		     "this file, then rerun automake).");
 	    }
 	}
     }
@@ -5772,7 +5808,7 @@
           my $base_c_file = basename $c_file;
           #
           # The -newer test here is checking "C file not older than Vala
-          # file" (not "C file newer than Vala file"; see
+          # file", rather than "C file newer than Vala file"; see
           # https://bugs.gnu.org/44772. The log message on the commit
           # misleadingly says "reversed".
           #
@@ -6431,7 +6467,7 @@
 # read_am_file ($AMFILE, $WHERE, $RELDIR)
 # ---------------------------------------
 # Read $AMFILE file name which is located in $RELDIR, and set up
-# global variables resetted by '&generate_makefile'.  Simultaneously
+# global variables reset by '&generate_makefile'.  Simultaneously
 # copy lines from $AMFILE into '$output_trailer', or define variables
 # as appropriate.
 #
@@ -7543,7 +7579,7 @@
     {
       push_dist_common ("$am_config_aux_dir/$file");
     }
-  # FIXME: another spacial case, for AC_LIBOBJ/AC_LIBSOURCE support.
+  # FIXME: another special case, for AC_LIBOBJ/AC_LIBSOURCE support.
   # We probably need some refactoring of this function and its callers,
   # to have a more explicit and systematic handling of all the special
   # cases; but, since there are only two of them, this is low-priority
@@ -7615,6 +7651,13 @@
   my ($where, $dir, $file) = @_;
 
   my $fullfile = "$dir/$file";
+  # In cases where $file is actually a subdir/filename, split the full path back
+  # into dir & file names.  The FileUtils (e.g. dir_has_case_matching_file) do
+  # not handle this scenario at all and expect $file to only be a filename.
+  # https://bugs.gnu.org/20300
+  $dir = dirname ($fullfile);
+  $file = basename ($fullfile);
+
   my $found_it = 0;
   my $dangling_sym = 0;
 
@@ -7890,7 +7933,7 @@
 
   $output_rules .= ("$dirstamp:\n"
 		    . "\t\@\$(MKDIR_P) $directory\n"
-		    . "\t\@: > $dirstamp\n");
+		    . "\t\@: >>$dirstamp\n");
 
   return $dirstamp;
 }
@@ -8087,6 +8130,13 @@
   my $output =
     "$output_vars$output_all$output_header$output_rules$output_trailer";
 
+  # The .POSIX special target must be the first non-comment line;
+  # otherwise, the behavior of "make" is unspecified by POSIX.
+  if (option 'posix')
+    {
+      $output =~ s/^((#.*)?\n)*/.POSIX:\n\n/;
+    }
+
   # Decide whether we must update the output file or not.
   # We have to update in the following situations.
   #  * $force_generation is set.
@@ -8225,16 +8275,20 @@
 
 sub version ()
 {
-  print <<EOF;
-automake (GNU $PACKAGE) $VERSION
-Copyright (C) $RELEASE_YEAR Free Software Foundation, Inc.
-License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl-2.0.html>
+  print "automake (GNU $PACKAGE) $VERSION\n";
+  print "Features: subsecond-mtime\n"
+      if $Automake::FileUtils::subsecond_mtime
+         && $Automake::FileUtils::subsecond_mtime; # avoid "once" warning
+  print "\nCopyright (C) $RELEASE_YEAR Free Software Foundation, Inc.";
+  print '
+License GPLv2+: GNU GPL version 2 or later
+  <https://gnu.org/licenses/gpl-2.0.html>
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.
 
-Written by Tom Tromey <tromey\@redhat.com>
-       and Alexandre Duret-Lutz <adl\@gnu.org>.
-EOF
+Written by Tom Tromey <tromey@redhat.com>
+       and Alexandre Duret-Lutz <adl@gnu.org>.
+';
   # --version always returns 0 per GNU standards.
   exit 0;
 }

_service:tar_scm:automake-1.16.5.tar.xz/bin/local.mk -> _service:tar_scm:automake-1.17.tar.xz/bin/local.mk Changed

_service:tar_scm:automake-1.16.5.tar.xz/bootstrap -> _service:tar_scm:automake-1.17.tar.xz/bootstrap Changed

_service:tar_scm:automake-1.16.5.tar.xz/configure -> _service:tar_scm:automake-1.17.tar.xz/configure Changed

@@ -1,11 +1,11 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for GNU Automake 1.16.5.
+# Generated by GNU Autoconf 2.72.24-c5b83 for GNU Automake 1.17.
 #
 # Report bugs to <bug-automake@gnu.org>.
 #
 #
-# Copyright (C) 1992-1996, 1998-2017, 2020-2021 Free Software Foundation,
+# Copyright (C) 1992-1996, 1998-2017, 2020-2024 Free Software Foundation,
 # Inc.
 #
 #
@@ -17,7 +17,6 @@
 
 # Be more Bourne compatible
 DUALCASE=1; export DUALCASE # for MKS sh
-as_nop=:
 if test ${ZSH_VERSION+y} && (emulate sh) >/dev/null 2>&1
 then :
   emulate sh
@@ -26,12 +25,13 @@
   # is contrary to our usage.  Disable this feature.
   alias -g '${1+"$@"}'='"$@"'
   setopt NO_GLOB_SUBST
-else $as_nop
-  case `(set -o) 2>/dev/null` in #(
+else case e in #(
+  e) case `(set -o) 2>/dev/null` in #(
   *posix*) :
     set -o posix ;; #(
   *) :
      ;;
+esac ;;
 esac
 fi
 
@@ -103,7 +103,7 @@
 
      ;;
 esac
-# We did not find ourselves, most probably we were run as `sh COMMAND'
+# We did not find ourselves, most probably we were run as 'sh COMMAND'
 # in which case we are not to be found in the path.
 if test "x$as_myself" = x; then
   as_myself=$0
@@ -133,15 +133,14 @@
 esac
 exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
 # Admittedly, this is quite paranoid, since all the known shells bail
-# out after a failed `exec'.
+# out after a failed 'exec'.
 printf "%s\n" "$0: could not re-execute with $CONFIG_SHELL" >&2
 exit 255
   fi
   # We don't want this to propagate to other subprocesses.
           { _as_can_reexec=; unset _as_can_reexec;}
 if test "x$CONFIG_SHELL" = x; then
-  as_bourne_compatible="as_nop=:
-if test \${ZSH_VERSION+y} && (emulate sh) >/dev/null 2>&1
+  as_bourne_compatible="if test \${ZSH_VERSION+y} && (emulate sh) >/dev/null 2>&1
 then :
   emulate sh
   NULLCMD=:
@@ -149,12 +148,13 @@
   # is contrary to our usage.  Disable this feature.
   alias -g '\${1+\"\$@\"}'='\"\$@\"'
   setopt NO_GLOB_SUBST
-else \$as_nop
-  case \`(set -o) 2>/dev/null\` in #(
+else case e in #(
+  e) case \`(set -o) 2>/dev/null\` in #(
   *posix*) :
     set -o posix ;; #(
   *) :
      ;;
+esac ;;
 esac
 fi
 "
@@ -172,8 +172,9 @@
 if ( set x; as_fn_ret_success y && test x = \"\$1\" )
 then :
 
-else \$as_nop
-  exitcode=1; echo positional parameters were not saved.
+else case e in #(
+  e) exitcode=1; echo positional parameters were not saved. ;;
+esac
 fi
 test x\$exitcode = x0 || exit 1
 blah=\$(echo \$(echo blah))
@@ -187,14 +188,15 @@
   if (eval "$as_required") 2>/dev/null
 then :
   as_have_required=yes
-else $as_nop
-  as_have_required=no
+else case e in #(
+  e) as_have_required=no ;;
+esac
 fi
   if test x$as_have_required = xyes && (eval "$as_suggested") 2>/dev/null
 then :
 
-else $as_nop
-  as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+else case e in #(
+  e) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
 as_found=false
 for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
 do
@@ -227,12 +229,13 @@
 if $as_found
 then :
 
-else $as_nop
-  if { test -f "$SHELL" || test -f "$SHELL.exe"; } &&
+else case e in #(
+  e) if { test -f "$SHELL" || test -f "$SHELL.exe"; } &&
 	      as_run=a "$SHELL" -c "$as_bourne_compatible""$as_required" 2>/dev/null
 then :
   CONFIG_SHELL=$SHELL as_have_required=yes
-fi
+fi ;;
+esac
 fi
 
 
@@ -254,7 +257,7 @@
 esac
 exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
 # Admittedly, this is quite paranoid, since all the known shells bail
-# out after a failed `exec'.
+# out after a failed 'exec'.
 printf "%s\n" "$0: could not re-execute with $CONFIG_SHELL" >&2
 exit 255
 fi
@@ -274,7 +277,8 @@
 $0: shell if you do have one."
   fi
   exit 1
-fi
+fi ;;
+esac
 fi
 fi
 SHELL=${CONFIG_SHELL-/bin/sh}
@@ -313,14 +317,6 @@
   as_fn_set_status $1
   exit $1
 } # as_fn_exit
-# as_fn_nop
-# ---------
-# Do nothing but, unlike ":", preserve the value of $?.
-as_fn_nop ()
-{
-  return $?
-}
-as_nop=as_fn_nop
 
 # as_fn_mkdir_p
 # -------------
@@ -389,11 +385,12 @@
   {
     eval $1+=\$2
   }'
-else $as_nop
-  as_fn_append ()
+else case e in #(
+  e) as_fn_append ()
   {
     eval $1=\$$1\$2
-  }
+  } ;;
+esac
 fi # as_fn_append
 
 # as_fn_arith ARG...
@@ -407,21 +404,14 @@
   {
     as_val=$(( $* ))
   }'
-else $as_nop
-  as_fn_arith ()
+else case e in #(
+  e) as_fn_arith ()
   {
     as_val=`expr "$@" || test $? -eq 1`
-  }
+  } ;;
+esac
 fi # as_fn_arith
 
-# as_fn_nop
-# ---------
-# Do nothing but, unlike ":", preserve the value of $?.
-as_fn_nop ()
-{
-  return $?
-}
-as_nop=as_fn_nop
 
 # as_fn_error STATUS ERROR LINENO LOG_FD
 # ----------------------------------------
@@ -495,6 +485,8 @@
     /$LINENO/=
   ' <$as_myself |
     sed '
+      t clear
+      :clear
       s/$LINENO.*/&-/
       t lineno
       b
@@ -543,7 +535,6 @@
 as_echo='printf %s\n'
 as_echo_n='printf %s'
 
-
 rm -f conf$$ conf$$.exe conf$$.file
 if test -d conf$$.dir; then
   rm -f conf$$.dir/conf$$.file
@@ -555,9 +546,9 @@
   if ln -s conf$$.file conf$$ 2>/dev/null; then
     as_ln_s='ln -s'
     # ... but there are two gotchas:
-    # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
-    # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
-    # In both cases, we have to default to `cp -pR'.
+    # 1) On MSYS, both 'ln -s file dir' and 'ln file dir' fail.
+    # 2) DJGPP < 2.04 has no symlinks; 'ln -s' creates a wrapper executable.
+    # In both cases, we have to default to 'cp -pR'.
     ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
       as_ln_s='cp -pR'
   elif ln conf$$.file conf$$ 2>/dev/null; then
@@ -582,10 +573,12 @@
 as_executable_p=as_fn_executable_p
 
 # Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%^_$as_cr_alnum%_%g'"
+as_sed_cpp="y%*$as_cr_letters%P$as_cr_LETTERS%;s%^_$as_cr_alnum%_%g"
+as_tr_cpp="eval sed '$as_sed_cpp'" # deprecated
 
 # Sed expression to map a string onto a valid variable name.
-as_tr_sh="eval sed 'y%*+%pp%;s%^_$as_cr_alnum%_%g'"
+as_sed_sh="y%*+%pp%;s%^_$as_cr_alnum%_%g"
+as_tr_sh="eval sed '$as_sed_sh'" # deprecated
 
 
 test -n "$DJDIR" || exec 7<&0 </dev/null
@@ -611,8 +604,8 @@
 # Identity of this package.
 PACKAGE_NAME='GNU Automake'
 PACKAGE_TARNAME='automake'
-PACKAGE_VERSION='1.16.5'
-PACKAGE_STRING='GNU Automake 1.16.5'
+PACKAGE_VERSION='1.17'
+PACKAGE_STRING='GNU Automake 1.17'
 PACKAGE_BUGREPORT='bug-automake@gnu.org'
 PACKAGE_URL='https://www.gnu.org/software/automake/'
 
@@ -654,10 +647,10 @@
 CC
 AM_TEST_RUNNER_SHELL
 am_candidate_sh
+MTIME_RESOLUTION
 FGREP
 EGREP
 GREP
-MODIFICATION_DELAY
 LN
 required_autoconf_version
 LEX
@@ -672,6 +665,8 @@
 pkgvdatadir
 APIVERSION
 RELEASE_YEAR
+am__xargs_n
+am__rm_f_notfound
 CSCOPE
 ETAGS
 CTAGS
@@ -893,7 +888,7 @@
     ac_useropt=`expr "x$ac_option" : 'x-*disable-$.*$'`
     # Reject names that are not valid shell variable names.
     expr "x$ac_useropt" : ".*^-+._$as_cr_alnum" >/dev/null &&
-      as_fn_error $? "invalid feature name: \`$ac_useropt'"
+      as_fn_error $? "invalid feature name: '$ac_useropt'"
     ac_useropt_orig=$ac_useropt
     ac_useropt=`printf "%s\n" "$ac_useropt" | sed 's/-+./_/g'`
     case $ac_user_opts in
@@ -919,7 +914,7 @@
     ac_useropt=`expr "x$ac_option" : 'x-*enable-$^=*$'`
     # Reject names that are not valid shell variable names.
     expr "x$ac_useropt" : ".*^-+._$as_cr_alnum" >/dev/null &&
-      as_fn_error $? "invalid feature name: \`$ac_useropt'"
+      as_fn_error $? "invalid feature name: '$ac_useropt'"
     ac_useropt_orig=$ac_useropt
     ac_useropt=`printf "%s\n" "$ac_useropt" | sed 's/-+./_/g'`
     case $ac_user_opts in
@@ -1132,7 +1127,7 @@
     ac_useropt=`expr "x$ac_option" : 'x-*with-$^=*$'`
     # Reject names that are not valid shell variable names.
     expr "x$ac_useropt" : ".*^-+._$as_cr_alnum" >/dev/null &&
-      as_fn_error $? "invalid package name: \`$ac_useropt'"
+      as_fn_error $? "invalid package name: '$ac_useropt'"
     ac_useropt_orig=$ac_useropt
     ac_useropt=`printf "%s\n" "$ac_useropt" | sed 's/-+./_/g'`
     case $ac_user_opts in
@@ -1148,7 +1143,7 @@
     ac_useropt=`expr "x$ac_option" : 'x-*without-$.*$'`
     # Reject names that are not valid shell variable names.
     expr "x$ac_useropt" : ".*^-+._$as_cr_alnum" >/dev/null &&
-      as_fn_error $? "invalid package name: \`$ac_useropt'"
+      as_fn_error $? "invalid package name: '$ac_useropt'"
     ac_useropt_orig=$ac_useropt
     ac_useropt=`printf "%s\n" "$ac_useropt" | sed 's/-+./_/g'`
     case $ac_user_opts in
@@ -1178,8 +1173,8 @@
   | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
     x_libraries=$ac_optarg ;;
 
-  -*) as_fn_error $? "unrecognized option: \`$ac_option'
-Try \`$0 --help' for more information"
+  -*) as_fn_error $? "unrecognized option: '$ac_option'
+Try '$0 --help' for more information"
     ;;
 
   *=*)
@@ -1187,7 +1182,7 @@
     # Reject names that are not valid shell variable names.
     case $ac_envvar in #(
       '' | 0-9* | *!_$as_cr_alnum* )
-      as_fn_error $? "invalid variable name: \`$ac_envvar'" ;;
+      as_fn_error $? "invalid variable name: '$ac_envvar'" ;;
     esac
     eval $ac_envvar=\$ac_optarg
     export $ac_envvar ;;
@@ -1237,7 +1232,7 @@
   as_fn_error $? "expected an absolute directory name for --$ac_var: $ac_val"
 done
 
-# There might be people who depend on the old broken behavior: `$host'
+# There might be people who depend on the old broken behavior: '$host'
 # used to hold the argument of --host etc.
 # FIXME: To remove some day.
 build=$build_alias
@@ -1305,7 +1300,7 @@
   test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
   as_fn_error $? "cannot find sources ($ac_unique_file) in $srcdir"
 fi
-ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
+ac_msg="sources are in $srcdir, but 'cd $srcdir' does not work"
 ac_abs_confdir=`(
 	cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error $? "$ac_msg"
 	pwd)`
@@ -1333,7 +1328,7 @@
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures GNU Automake 1.16.5 to adapt to many kinds of systems.
+'configure' configures GNU Automake 1.17 to adapt to many kinds of systems.
 
 Usage: $0 OPTION... VAR=VALUE...
 
@@ -1347,11 +1342,11 @@
       --help=short        display options specific to this package
       --help=recursive    display the short help of all the included packages
   -V, --version           display version information and exit
-  -q, --quiet, --silent   do not print \`checking ...' messages
+  -q, --quiet, --silent   do not print 'checking ...' messages
       --cache-file=FILE   cache test results in FILE disabled
-  -C, --config-cache      alias for \`--cache-file=config.cache'
+  -C, --config-cache      alias for '--cache-file=config.cache'
   -n, --no-create         do not create output files
-      --srcdir=DIR        find the sources in DIR configure dir or \`..'
+      --srcdir=DIR        find the sources in DIR configure dir or '..'
 
 Installation directories:
   --prefix=PREFIX         install architecture-independent files in PREFIX
@@ -1359,10 +1354,10 @@
   --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                           PREFIX
 
-By default, \`make install' will install all the files in
-\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc.  You can specify
-an installation prefix other than \`$ac_default_prefix' using \`--prefix',
-for instance \`--prefix=\$HOME'.
+By default, 'make install' will install all the files in
+'$ac_default_prefix/bin', '$ac_default_prefix/lib' etc.  You can specify
+an installation prefix other than '$ac_default_prefix' using '--prefix',
+for instance '--prefix=\$HOME'.
 
 For better control, use the options below.
 
@@ -1404,7 +1399,7 @@
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
-     short | recursive ) echo "Configuration of GNU Automake 1.16.5:";;
+     short | recursive ) echo "Configuration of GNU Automake 1.17:";;
    esac
   cat <<\_ACEOF
 
@@ -1444,7 +1439,7 @@
   GNU_GCJFLAGS
               GNU Java compiler flags
 
-Use these variables to override the choices made by `configure' or to help
+Use these variables to override the choices made by 'configure' or to help
 it to find libraries and programs with nonstandard names/locations.
 
 Report bugs to <bug-automake@gnu.org>.
@@ -1513,10 +1508,10 @@
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-GNU Automake configure 1.16.5
-generated by GNU Autoconf 2.71
+GNU Automake configure 1.17
+generated by GNU Autoconf 2.72.24-c5b83
 
-Copyright (C) 2021 Free Software Foundation, Inc.
+Copyright (C) 2024 Free Software Foundation, Inc.
 This configure script is free software; the Free Software Foundation
 gives unlimited permission to copy, distribute and modify it.
 _ACEOF
@@ -1555,11 +1550,12 @@
        } && test -s conftest.$ac_objext
 then :
   ac_retval=0
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
-	ac_retval=1
+	ac_retval=1 ;;
+esac
 fi
   eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
   as_fn_set_status $ac_retval
@@ -1594,11 +1590,12 @@
        } && test -s conftest.$ac_objext
 then :
   ac_retval=0
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
-	ac_retval=1
+	ac_retval=1 ;;
+esac
 fi
   eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
   as_fn_set_status $ac_retval
@@ -1633,11 +1630,12 @@
        } && test -s conftest.$ac_objext
 then :
   ac_retval=0
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
-	ac_retval=1
+	ac_retval=1 ;;
+esac
 fi
   eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
   as_fn_set_status $ac_retval
@@ -1672,11 +1670,12 @@
        } && test -s conftest.$ac_objext
 then :
   ac_retval=0
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
-	ac_retval=1
+	ac_retval=1 ;;
+esac
 fi
   eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
   as_fn_set_status $ac_retval
@@ -1706,8 +1705,8 @@
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by GNU Automake $as_me 1.16.5, which was
-generated by GNU Autoconf 2.71.  Invocation command line was
+It was created by GNU Automake $as_me 1.17, which was
+generated by GNU Autoconf 2.72.24-c5b83.  Invocation command line was
 
   $ $0$ac_configure_args_raw
 
@@ -1953,10 +1952,10 @@
 printf "%s\n" "$as_me: loading site script $ac_site_file" >&6;}
     sed 's/^/| /' "$ac_site_file" >&5
     . "$ac_site_file" \
-      || { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-printf "%s\n" "$as_me: error: in \`$ac_pwd':" >&2;}
+      || { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in '$ac_pwd':" >&5
+printf "%s\n" "$as_me: error: in '$ac_pwd':" >&2;}
 as_fn_error $? "failed to load site script $ac_site_file
-See \`config.log' for more details" "$LINENO" 5; }
+See 'config.log' for more details" "$LINENO" 5; }
   fi
 done
 
@@ -1977,14 +1976,107 @@
   >$cache_file
 fi
 
+# Test code for whether the C compiler supports C23 (global declarations)
+ac_c_conftest_c23_globals='
+/* Does the compiler advertise conformance to C17 or earlier?
+   Although GCC 14 does not do that, even with -std=gnu23,
+   it is close enough, and defines __STDC_VERSION == 202000L.  */
+#if !defined __STDC_VERSION__ || __STDC_VERSION__ <= 201710L
+# error "Compiler advertises conformance to C17 or earlier"
+#endif
+
+// Check alignas.
+char alignas (double) c23_aligned_as_double;
+char alignas (0) c23_no_special_alignment;
+extern char c23_aligned_as_int;
+char alignas (0) alignas (int) c23_aligned_as_int;
+
+// Check alignof.
+enum
+{
+  c23_int_alignment = alignof (int),
+  c23_int_array_alignment = alignof (int100),
+  c23_char_alignment = alignof (char)
+};
+static_assert (0 < -alignof (int), "alignof is signed");
+
+int function_with_unnamed_parameter (int) { return 0; }
+
+void c23_noreturn ();
+
+bool use_u8 = !u8"\xFF" == u8'\''x'\'';
+
+bool check_that_bool_works = true | false | !nullptr;
+#if !true
+# error "true does not work in #if"
+#endif
+#if false
+#elifdef __STDC_VERSION__
+#else
+# error "#elifdef does not work"
+#endif
+
+#ifndef __has_c_attribute
+# error "__has_c_attribute not defined"
+#endif
+
+#ifndef __has_include
+# error "__has_include not defined"
+#endif
+
+#define LPAREN() (
+#define FORTY_TWO(x) 42
+#define VA_OPT_TEST(r, x, ...) __VA_OPT__ (FORTY_TWO r x))
+static_assert (VA_OPT_TEST (LPAREN (), 0, <:-) == 42);
+
+static_assert (0b101010 == 42);
+static_assert (0B101010 == 42);
+static_assert (0xDEAD'\''BEEF == 3'\''735'\''928'\''559);
+static_assert (0.500'\''000'\''000 == 0.5);
+
+enum unsignedish : unsigned int { uione = 1 };
+static_assert (0 < -uione);
+
+#include <stddef.h>
+constexpr nullptr_t null_pointer = nullptr;
+
+#include <stdbit.h>
+static_assert (__STDC_ENDIAN_LITTLE__ != __STDC_ENDIAN_BIG__);
+
+static typeof (1 + 1L) two () { return 2; }
+static long int three () { return 3; }
+'
+
+# Test code for whether the C compiler supports C23 (body of main).
+ac_c_conftest_c23_main='
+  {
+    label_before_declaration:
+      int arr10 = {};
+      if (arr0)
+        goto label_before_declaration;
+      if (!arr0)
+        goto label_at_end_of_block;
+    label_at_end_of_block:
+  }
+  ok |= two != three;
+'
+
+# Test code for whether the C compiler supports C23 (complete).
+ac_c_conftest_c23_program="${ac_c_conftest_c23_globals}
+
+int
+main (int, char **)
+{
+  int ok = 0;
+  ${ac_c_conftest_c23_main}
+  return ok;
+}
+"
+
 # Test code for whether the C compiler supports C89 (global declarations)
 ac_c_conftest_c89_globals='
-/* Does the compiler advertise C89 conformance?
-   Do not test the value of __STDC__, because some compilers set it to 0
-   while being otherwise adequately conformant. */
-#if !defined __STDC__
-# error "Compiler does not advertise C89 conformance"
-#endif
+/* Do not test the value of __STDC__, because some compilers define it to 0
+   or do not define it, while otherwise adequately conforming.  */
 
 #include <stddef.h>
 #include <stdarg.h>
@@ -1992,9 +2084,7 @@
 /* Most of the following tests are stolen from RCS 5.7 src/conf.sh.  */
 struct buf { int x; };
 struct buf * (*rcsopen) (struct buf *, struct stat *, int);
-static char *e (p, i)
-     char **p;
-     int i;
+static char *e (char **p, int i)
 {
   return pi;
 }
@@ -2008,6 +2098,21 @@
   return s;
 }
 
+/* C89 style stringification. */
+#define noexpand_stringify(a) #a
+const char *stringified = noexpand_stringify(arbitrary+token=sequence);
+
+/* C89 style token pasting.  Exercises some of the corner cases that
+   e.g. old MSVC gets wrong, but not very hard. */
+#define noexpand_concat(a,b) a##b
+#define expand_concat(a,b) noexpand_concat(a,b)
+extern int vA;
+extern int vbee;
+#define aye A
+#define bee B
+int *pvA = &expand_concat(v,aye);
+int *pvbee = &noexpand_concat(v,bee);
+
 /* OSF 4.0 Compaq cc is some sort of almost-ANSI by default.  It has
    function prototypes and stuff, but not \xHH hex character constants.
    These do not provoke an error unfortunately, instead are silently treated
@@ -2035,16 +2140,19 @@
 
 # Test code for whether the C compiler supports C99 (global declarations)
 ac_c_conftest_c99_globals='
-// Does the compiler advertise C99 conformance?
+/* Does the compiler advertise C99 conformance? */
 #if !defined __STDC_VERSION__ || __STDC_VERSION__ < 199901L
 # error "Compiler does not advertise C99 conformance"
 #endif
 
+// See if C++-style comments work.
+
 #include <stdbool.h>
 extern int puts (const char *);
 extern int printf (const char *, ...);
 extern int dprintf (int, const char *, ...);
 extern void *malloc (size_t);
+extern void free (void *);
 
 // Check varargs macros.  These examples are taken from C99 6.10.3.5.
 // dprintf is used instead of fprintf to avoid needing to declare
@@ -2094,7 +2202,6 @@
 static inline int
 test_restrict (ccp restrict text)
 {
-  // See if C++-style comments work.
   // Iterate through items via the restricted pointer.
   // Also check for declarations in for loops.
   for (unsigned int i = 0; *(text+i) != '\''\0'\''; ++i)
@@ -2160,6 +2267,8 @@
   ia->datasize = 10;
   for (int i = 0; i < ia->datasize; ++i)
     ia->datai = i * 1.234;
+  // Work around memory leak warnings.
+  free (ia);
 
   // Check named initializers.
   struct named_init ni = {
@@ -2170,18 +2279,17 @@
 
   ni.number = 58;
 
-  int dynamic_arrayni.number;
-  dynamic_array0 = argv00;
-  dynamic_arrayni.number - 1 = 543;
+  // Do not test for VLAs, as some otherwise-conforming compilers lack them.
+  // C code should instead use __STDC_NO_VLA__; see Autoconf manual.
 
   // work around unused variable warnings
   ok |= (!success || bignum == 0LL || ubignum == 0uLL || newvar0 == '\''x'\''
-	 || dynamic_arrayni.number - 1 != 543);
+	 || ni.number != 58);
 '
 
 # Test code for whether the C compiler supports C11 (global declarations)
 ac_c_conftest_c11_globals='
-// Does the compiler advertise C11 conformance?
+/* Does the compiler advertise C11 conformance? */
 #if !defined __STDC_VERSION__ || __STDC_VERSION__ < 201112L
 # error "Compiler does not advertise C11 conformance"
 #endif
@@ -2285,222 +2393,6 @@
 }
 "
 
-# Test code for whether the C++ compiler supports C++98 (global declarations)
-ac_cxx_conftest_cxx98_globals='
-// Does the compiler advertise C++98 conformance?
-#if !defined __cplusplus || __cplusplus < 199711L
-# error "Compiler does not advertise C++98 conformance"
-#endif
-
-// These inclusions are to reject old compilers that
-// lack the unsuffixed header files.
-#include <cstdlib>
-#include <exception>
-
-// <cassert> and <cstring> are *not* freestanding headers in C++98.
-extern void assert (int);
-namespace std {
-  extern int strcmp (const char *, const char *);
-}
-
-// Namespaces, exceptions, and templates were all added after "C++ 2.0".
-using std::exception;
-using std::strcmp;
-
-namespace {
-
-void test_exception_syntax()
-{
-  try {
-    throw "test";
-  } catch (const char *s) {
-    // Extra parentheses suppress a warning when building autoconf itself,
-    // due to lint rules shared with more typical C programs.
-    assert (!(strcmp) (s, "test"));
-  }
-}
-
-template <typename T> struct test_template
-{
-  T const val;
-  explicit test_template(T t) : val(t) {}
-  template <typename U> T add(U u) { return static_cast<T>(u) + val; }
-};
-
-} // anonymous namespace
-'
-
-# Test code for whether the C++ compiler supports C++98 (body of main)
-ac_cxx_conftest_cxx98_main='
-  assert (argc);
-  assert (! argv0);
-{
-  test_exception_syntax ();
-  test_template<double> tt (2.0);
-  assert (tt.add (4) == 6.0);
-  assert (true && !false);
-}
-'
-
-# Test code for whether the C++ compiler supports C++11 (global declarations)
-ac_cxx_conftest_cxx11_globals='
-// Does the compiler advertise C++ 2011 conformance?
-#if !defined __cplusplus || __cplusplus < 201103L
-# error "Compiler does not advertise C++11 conformance"
-#endif
-
-namespace cxx11test
-{
-  constexpr int get_val() { return 20; }
-
-  struct testinit
-  {
-    int i;
-    double d;
-  };
-
-  class delegate
-  {
-  public:
-    delegate(int n) : n(n) {}
-    delegate(): delegate(2354) {}
-
-    virtual int getval() { return this->n; };
-  protected:
-    int n;
-  };
-
-  class overridden : public delegate
-  {
-  public:
-    overridden(int n): delegate(n) {}
-    virtual int getval() override final { return this->n * 2; }
-  };
-
-  class nocopy
-  {
-  public:
-    nocopy(int i): i(i) {}
-    nocopy() = default;
-    nocopy(const nocopy&) = delete;
-    nocopy & operator=(const nocopy&) = delete;
-  private:
-    int i;
-  };
-
-  // for testing lambda expressions
-  template <typename Ret, typename Fn> Ret eval(Fn f, Ret v)
-  {
-    return f(v);
-  }
-
-  // for testing variadic templates and trailing return types
-  template <typename V> auto sum(V first) -> V
-  {
-    return first;
-  }
-  template <typename V, typename... Args> auto sum(V first, Args... rest) -> V
-  {
-    return first + sum(rest...);
-  }
-}
-'
-
-# Test code for whether the C++ compiler supports C++11 (body of main)
-ac_cxx_conftest_cxx11_main='
-{
-  // Test auto and decltype
-  auto a1 = 6538;
-  auto a2 = 48573953.4;
-  auto a3 = "String literal";
-
-  int total = 0;
-  for (auto i = a3; *i; ++i) { total += *i; }
-
-  decltype(a2) a4 = 34895.034;
-}
-{
-  // Test constexpr
-  short sacxx11test::get_val() = { 0 };
-}
-{
-  // Test initializer lists
-  cxx11test::testinit il = { 4323, 435234.23544 };
-}
-{
-  // Test range-based for
-  int array = {9, 7, 13, 15, 4, 18, 12, 10, 5, 3,
-                 14, 19, 17, 8, 6, 20, 16, 2, 11, 1};
-  for (auto &x : array) { x += 23; }
-}
-{
-  // Test lambda expressions
-  using cxx11test::eval;
-  assert (eval ((int x) { return x*2; }, 21) == 42);
-  double d = 2.0;
-  assert (eval (&(double x) { return d += x; }, 3.0) == 5.0);
-  assert (d == 5.0);
-  assert (eval (=(double x) mutable { return d += x; }, 4.0) == 9.0);
-  assert (d == 5.0);
-}
-{
-  // Test use of variadic templates
-  using cxx11test::sum;
-  auto a = sum(1);
-  auto b = sum(1, 2);
-  auto c = sum(1.0, 2.0, 3.0);
-}
-{
-  // Test constructor delegation
-  cxx11test::delegate d1;
-  cxx11test::delegate d2();
-  cxx11test::delegate d3(45);
-}
-{
-  // Test override and final
-  cxx11test::overridden o1(55464);
-}
-{
-  // Test nullptr
-  char *c = nullptr;
-}
-{
-  // Test template brackets
-  test_template<::test_template<int>> v(test_template<int>(12));
-}
-{
-  // Unicode literals
-  char const *utf8 = u8"UTF-8 string \u2500";
-  char16_t const *utf16 = u"UTF-8 string \u2500";
-  char32_t const *utf32 = U"UTF-32 string \u2500";
-}
-'
-
-# Test code for whether the C compiler supports C++11 (complete).
-ac_cxx_conftest_cxx11_program="${ac_cxx_conftest_cxx98_globals}
-${ac_cxx_conftest_cxx11_globals}
-
-int
-main (int argc, char **argv)
-{
-  int ok = 0;
-  ${ac_cxx_conftest_cxx98_main}
-  ${ac_cxx_conftest_cxx11_main}
-  return ok;
-}
-"
-
-# Test code for whether the C compiler supports C++98 (complete).
-ac_cxx_conftest_cxx98_program="${ac_cxx_conftest_cxx98_globals}
-int
-main (int argc, char **argv)
-{
-  int ok = 0;
-  ${ac_cxx_conftest_cxx98_main}
-  return ok;
-}
-"
-
 
 # Auxiliary files required by this configure script.
 ac_aux_files="compile missing install-sh config.guess config.sub"
@@ -2580,8 +2472,9 @@
 if $as_found
 then :
 
-else $as_nop
-  as_fn_error $? "cannot find required auxiliary files:$ac_missing_aux_files" "$LINENO" 5
+else case e in #(
+  e) as_fn_error $? "cannot find required auxiliary files:$ac_missing_aux_files" "$LINENO" 5 ;;
+esac
 fi
 
 
@@ -2609,12 +2502,12 @@
   eval ac_new_val=\$ac_env_${ac_var}_value
   case $ac_old_set,$ac_new_set in
     set,)
-      { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
-printf "%s\n" "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
+      { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: '$ac_var' was set to '$ac_old_val' in the previous run" >&5
+printf "%s\n" "$as_me: error: '$ac_var' was set to '$ac_old_val' in the previous run" >&2;}
       ac_cache_corrupted=: ;;
     ,set)
-      { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was not set in the previous run" >&5
-printf "%s\n" "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
+      { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: '$ac_var' was not set in the previous run" >&5
+printf "%s\n" "$as_me: error: '$ac_var' was not set in the previous run" >&2;}
       ac_cache_corrupted=: ;;
     ,);;
     *)
@@ -2623,18 +2516,18 @@
 	ac_old_val_w=`echo x $ac_old_val`
 	ac_new_val_w=`echo x $ac_new_val`
 	if test "$ac_old_val_w" != "$ac_new_val_w"; then
-	  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' has changed since the previous run:" >&5
-printf "%s\n" "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
+	  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: '$ac_var' has changed since the previous run:" >&5
+printf "%s\n" "$as_me: error: '$ac_var' has changed since the previous run:" >&2;}
 	  ac_cache_corrupted=:
 	else
-	  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5
-printf "%s\n" "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
+	  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in '$ac_var' since the previous run:" >&5
+printf "%s\n" "$as_me: warning: ignoring whitespace changes in '$ac_var' since the previous run:" >&2;}
 	  eval $ac_var=\$ac_old_val
 	fi
-	{ printf "%s\n" "$as_me:${as_lineno-$LINENO}:   former value:  \`$ac_old_val'" >&5
-printf "%s\n" "$as_me:   former value:  \`$ac_old_val'" >&2;}
-	{ printf "%s\n" "$as_me:${as_lineno-$LINENO}:   current value: \`$ac_new_val'" >&5
-printf "%s\n" "$as_me:   current value: \`$ac_new_val'" >&2;}
+	{ printf "%s\n" "$as_me:${as_lineno-$LINENO}:   former value:  '$ac_old_val'" >&5
+printf "%s\n" "$as_me:   former value:  '$ac_old_val'" >&2;}
+	{ printf "%s\n" "$as_me:${as_lineno-$LINENO}:   current value: '$ac_new_val'" >&5
+printf "%s\n" "$as_me:   current value: '$ac_new_val'" >&2;}
       fi;;
   esac
   # Pass precious variables to config.status.
@@ -2650,11 +2543,11 @@
   fi
 done
 if $ac_cache_corrupted; then
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-printf "%s\n" "$as_me: error: in \`$ac_pwd':" >&2;}
+  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in '$ac_pwd':" >&5
+printf "%s\n" "$as_me: error: in '$ac_pwd':" >&2;}
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5
 printf "%s\n" "$as_me: error: changes in the environment can compromise the build" >&2;}
-  as_fn_error $? "run \`${MAKE-make} distclean' and/or \`rm $cache_file'
+  as_fn_error $? "run '${MAKE-make} distclean' and/or 'rm $cache_file'
 	    and start over" "$LINENO" 5
 fi
 ## -------------------- ##
@@ -2672,25 +2565,21 @@
 
 
 
+AM_DEFAULT_VERBOSITY=1
 # Check whether --enable-silent-rules was given.
 if test ${enable_silent_rules+y}
 then :
   enableval=$enable_silent_rules;
 fi
 
-case $enable_silent_rules in # (((
-  yes) AM_DEFAULT_VERBOSITY=0;;
-   no) AM_DEFAULT_VERBOSITY=1;;
-    *) AM_DEFAULT_VERBOSITY=0;;
-esac
 am_make=${MAKE-make}
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking whether $am_make supports nested variables" >&5
 printf %s "checking whether $am_make supports nested variables... " >&6; }
 if test ${am_cv_make_support_nested_variables+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if printf "%s\n" 'TRUE=$(BAR$(V))
+else case e in #(
+  e) if printf "%s\n" 'TRUE=$(BAR$(V))
 BAR0=false
 BAR1=true
 V=1
@@ -2700,20 +2589,16 @@
   am_cv_make_support_nested_variables=yes
 else
   am_cv_make_support_nested_variables=no
-fi
+fi ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_make_support_nested_variables" >&5
 printf "%s\n" "$am_cv_make_support_nested_variables" >&6; }
-if test $am_cv_make_support_nested_variables = yes; then
-    AM_V='$(V)'
-  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
-else
-  AM_V=$AM_DEFAULT_VERBOSITY
-  AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY
-fi
 AM_BACKSLASH='\'
 
 
+AM_DEFAULT_VERBOSITY=0
+
 
 
 
@@ -2726,15 +2611,16 @@
 if test ${ac_cv_build+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  ac_build_alias=$build_alias
+else case e in #(
+  e) ac_build_alias=$build_alias
 test "x$ac_build_alias" = x &&
   ac_build_alias=`$SHELL "${ac_aux_dir}config.guess"`
 test "x$ac_build_alias" = x &&
   as_fn_error $? "cannot guess build type; you must specify one" "$LINENO" 5
 ac_cv_build=`$SHELL "${ac_aux_dir}config.sub" $ac_build_alias` ||
   as_fn_error $? "$SHELL ${ac_aux_dir}config.sub $ac_build_alias failed" "$LINENO" 5
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_build" >&5
 printf "%s\n" "$ac_cv_build" >&6; }
@@ -2761,14 +2647,15 @@
 if test ${ac_cv_host+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test "x$host_alias" = x; then
+else case e in #(
+  e) if test "x$host_alias" = x; then
   ac_cv_host=$ac_cv_build
 else
   ac_cv_host=`$SHELL "${ac_aux_dir}config.sub" $host_alias` ||
     as_fn_error $? "$SHELL ${ac_aux_dir}config.sub $host_alias failed" "$LINENO" 5
 fi
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_host" >&5
 printf "%s\n" "$ac_cv_host" >&6; }
@@ -2807,7 +2694,7 @@
 am_AUTOUPDATE="${AUTOUPDATE-autoupdate}"
 
 
-am__api_version='1.16'
+am__api_version='1.17'
 
 
   # Find a good install program.  We prefer a C program (faster),
@@ -2830,8 +2717,8 @@
 if test ${ac_cv_path_install+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+else case e in #(
+  e) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
 for as_dir in $PATH
 do
   IFS=$as_save_IFS
@@ -2885,7 +2772,8 @@
 IFS=$as_save_IFS
 
 rm -rf conftest.one conftest.two conftest.dir
-
+ ;;
+esac
 fi
   if test ${ac_cv_path_install+y}; then
     INSTALL=$ac_cv_path_install
@@ -2908,6 +2796,165 @@
 
 test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
 
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking whether sleep supports fractional seconds" >&5
+printf %s "checking whether sleep supports fractional seconds... " >&6; }
+if test ${am_cv_sleep_fractional_seconds+y}
+then :
+  printf %s "(cached) " >&6
+else case e in #(
+  e) if sleep 0.001 2>/dev/null
+then :
+  am_cv_sleep_fractional_seconds=yes
+else case e in #(
+  e) am_cv_sleep_fractional_seconds=no ;;
+esac
+fi
+ ;;
+esac
+fi
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_sleep_fractional_seconds" >&5
+printf "%s\n" "$am_cv_sleep_fractional_seconds" >&6; }
+
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking filesystem timestamp resolution" >&5
+printf %s "checking filesystem timestamp resolution... " >&6; }
+if test ${am_cv_filesystem_timestamp_resolution+y}
+then :
+  printf %s "(cached) " >&6
+else case e in #(
+  e) # Default to the worst case.
+am_cv_filesystem_timestamp_resolution=2
+
+# Only try to go finer than 1 sec if sleep can do it.
+# Don't try 1 sec, because if 0.01 sec and 0.1 sec don't work,
+# - 1 sec is not much of a win compared to 2 sec, and
+# - it takes 2 seconds to perform the test whether 1 sec works.
+#
+# Instead, just use the default 2s on platforms that have 1s resolution,
+# accept the extra 1s delay when using $sleep in the Automake tests, in
+# exchange for not incurring the 2s delay for running the test for all
+# packages.
+#
+am_try_resolutions=
+if test "$am_cv_sleep_fractional_seconds" = yes; then
+  # Even a millisecond often causes a bunch of false positives,
+  # so just try a hundredth of a second. The time saved between .001 and
+  # .01 is not terribly consequential.
+  am_try_resolutions="0.01 0.1 $am_try_resolutions"
+fi
+
+# In order to catch current-generation FAT out, we must *modify* files
+# that already exist; the *creation* timestamp is finer.  Use names
+# that make ls -t sort them differently when they have equal
+# timestamps than when they have distinct timestamps, keeping
+# in mind that ls -t prints the *newest* file first.
+rm -f conftest.ts?
+: > conftest.ts1
+: > conftest.ts2
+: > conftest.ts3
+
+# Make sure ls -t actually works.  Do 'set' in a subshell so we don't
+# clobber the current shell's arguments. (Outer-level square brackets
+# are removed by m4; they're present so that m4 does not expand
+# <dollar><star>; be careful, easy to get confused.)
+if (
+     set X `ls -t conftest.ts12` &&
+     {
+       test "$*" != "X conftest.ts1 conftest.ts2" ||
+       test "$*" != "X conftest.ts2 conftest.ts1";
+     }
+); then :; else
+  # If neither matched, then we have a broken ls.  This can happen
+  # if, for instance, CONFIG_SHELL is bash and it inherits a
+  # broken ls alias from the environment.  This has actually
+  # happened.  Such a system could not be considered "sane".
+  printf "%s\n" ""Bad output from ls -t: \"`ls -t conftest.ts12`\""" >&5
+  { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in '$ac_pwd':" >&5
+printf "%s\n" "$as_me: error: in '$ac_pwd':" >&2;}
+as_fn_error $? "ls -t produces unexpected output.
+Make sure there is not a broken ls alias in your environment.
+See 'config.log' for more details" "$LINENO" 5; }
+fi
+
+for am_try_res in $am_try_resolutions; do
+  # Any one fine-grained sleep might happen to cross the boundary
+  # between two values of a coarser actual resolution, but if we do
+  # two fine-grained sleeps in a row, at least one of them will fall
+  # entirely within a coarse interval.
+  echo alpha > conftest.ts1
+  sleep $am_try_res
+  echo beta > conftest.ts2
+  sleep $am_try_res
+  echo gamma > conftest.ts3
+
+  # We assume that 'ls -t' will make use of high-resolution
+  # timestamps if the operating system supports them at all.
+  if (set X `ls -t conftest.ts?` &&
+      test "$2" = conftest.ts3 &&
+      test "$3" = conftest.ts2 &&
+      test "$4" = conftest.ts1); then
+    #
+    # Ok, ls -t worked. If we're at a resolution of 1 second, we're done,
+    # because we don't need to test make.
+    make_ok=true
+    if test $am_try_res != 1; then
+      # But if we've succeeded so far with a subsecond resolution, we
+      # have one more thing to check: make. It can happen that
+      # everything else supports the subsecond mtimes, but make doesn't;
+      # notably on macOS, which ships make 3.81 from 2006 (the last one
+      # released under GPLv2). https://bugs.gnu.org/68808
+      #
+      # We test $MAKE if it is defined in the environment, else "make".
+      # It might get overridden later, but our hope is that in practice
+      # it does not matter: it is the system "make" which is (by far)
+      # the most likely to be broken, whereas if the user overrides it,
+      # probably they did so with a better, or at least not worse, make.
+      # https://lists.gnu.org/archive/html/automake/2024-06/msg00051.html
+      #
+      # Create a Makefile (real tab character here):
+      rm -f conftest.mk
+      echo 'conftest.ts1: conftest.ts2' >conftest.mk
+      echo '	touch conftest.ts2' >>conftest.mk
+      #
+      # Now, running
+      #   touch conftest.ts1; touch conftest.ts2; make
+      # should touch ts1 because ts2 is newer. This could happen by luck,
+      # but most often, it will fail if make's support is insufficient. So
+      # test for several consecutive successes.
+      #
+      # (We reuse conftest.ts12 because we still want to modify existing
+      # files, not create new ones, per above.)
+      n=0
+      make=${MAKE-make}
+      until test $n -eq 3; do
+        echo one > conftest.ts1
+        sleep $am_try_res
+        echo two > conftest.ts2 # ts2 should now be newer than ts1
+        if $make -f conftest.mk | grep 'up to date' >/dev/null; then
+          make_ok=false
+          break # out of $n loop
+        fi
+        n=`expr $n + 1`
+      done
+    fi
+    #
+    if $make_ok; then
+      # Everything we know to check worked out, so call this resolution good.
+      am_cv_filesystem_timestamp_resolution=$am_try_res
+      break # out of $am_try_res loop
+    fi
+    # Otherwise, we'll go on to check the next resolution.
+  fi
+done
+rm -f conftest.ts?
+# (end _am_filesystem_timestamp_resolution)
+ ;;
+esac
+fi
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_filesystem_timestamp_resolution" >&5
+printf "%s\n" "$am_cv_filesystem_timestamp_resolution" >&6; }
+
+# This check should not be cached, as it may vary across builds of
+# different projects.
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking whether build environment is sane" >&5
 printf %s "checking whether build environment is sane... " >&6; }
 # Reject unsafe characters in $srcdir or the absolute working directory
@@ -2928,49 +2975,45 @@
 # symlink; some systems play weird games with the mod time of symlinks
 # (eg FreeBSD returns the mod time of the symlink's containing
 # directory).
-if (
-   am_has_slept=no
-   for am_try in 1 2; do
-     echo "timestamp, slept: $am_has_slept" > conftest.file
-     set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null`
-     if test "$*" = "X"; then
-	# -L didn't work.
-	set X `ls -t "$srcdir/configure" conftest.file`
-     fi
-     if test "$*" != "X $srcdir/configure conftest.file" \
-	&& test "$*" != "X conftest.file $srcdir/configure"; then
-
-	# If neither matched, then we have a broken ls.  This can happen
-	# if, for instance, CONFIG_SHELL is bash and it inherits a
-	# broken ls alias from the environment.  This has actually
-	# happened.  Such a system could not be considered "sane".
-	as_fn_error $? "ls -t appears to fail.  Make sure there is not a broken
-  alias in your environment" "$LINENO" 5
-     fi
-     if test "$2" = conftest.file || test $am_try -eq 2; then
-       break
-     fi
-     # Just in case.
-     sleep 1
-     am_has_slept=yes
-   done
-   test "$2" = conftest.file
-   )
-then
-   # Ok.
-   :
-else
-   as_fn_error $? "newly created file is older than distributed files!
+am_build_env_is_sane=no
+am_has_slept=no
+rm -f conftest.file
+for am_try in 1 2; do
+  echo "timestamp, slept: $am_has_slept" > conftest.file
+  if (
+    set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null`
+    if test "$*" = "X"; then
+      # -L didn't work.
+      set X `ls -t "$srcdir/configure" conftest.file`
+    fi
+    test "$2" = conftest.file
+  ); then
+    am_build_env_is_sane=yes
+    break
+  fi
+  # Just in case.
+  sleep "$am_cv_filesystem_timestamp_resolution"
+  am_has_slept=yes
+done
+
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_build_env_is_sane" >&5
+printf "%s\n" "$am_build_env_is_sane" >&6; }
+if test "$am_build_env_is_sane" = no; then
+  as_fn_error $? "newly created file is older than distributed files!
 Check your system clock" "$LINENO" 5
 fi
-{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-printf "%s\n" "yes" >&6; }
+
 # If we didn't sleep, we still need to ensure time stamps of config.status and
 # generated files are strictly newer.
 am_sleep_pid=
-if grep 'slept: no' conftest.file >/dev/null 2>&1; then
-  ( sleep 1 ) &
+if test -e conftest.file || grep 'slept: no' conftest.file >/dev/null 2>&1
+then :
+
+else case e in #(
+  e)   ( sleep "$am_cv_filesystem_timestamp_resolution" ) &
   am_sleep_pid=$!
+ ;;
+esac
 fi
 
 rm -f conftest.file
@@ -2981,7 +3024,7 @@
 test "$program_suffix" != NONE &&
   program_transform_name="s&\$&$program_suffix&;$program_transform_name"
 # Double any \ or $.
-# By default was `s,x,x', remove it if useless.
+# By default was 's,x,x', remove it if useless.
 ac_script='s/\\$/&&/g;s/;s,x,x,$//'
 program_transform_name=`printf "%s\n" "$program_transform_name" | sed "$ac_script"`
 
@@ -3024,8 +3067,8 @@
 if test ${ac_cv_prog_STRIP+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$STRIP"; then
+else case e in #(
+  e) if test -n "$STRIP"; then
   ac_cv_prog_STRIP="$STRIP" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -3047,7 +3090,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 STRIP=$ac_cv_prog_STRIP
 if test -n "$STRIP"; then
@@ -3069,8 +3113,8 @@
 if test ${ac_cv_prog_ac_ct_STRIP+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_STRIP"; then
+else case e in #(
+  e) if test -n "$ac_ct_STRIP"; then
   ac_cv_prog_ac_ct_STRIP="$ac_ct_STRIP" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -3092,7 +3136,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_STRIP=$ac_cv_prog_ac_ct_STRIP
 if test -n "$ac_ct_STRIP"; then
@@ -3128,8 +3173,8 @@
   if test ${ac_cv_path_mkdir+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+else case e in #(
+  e) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
 for as_dir in $PATH$PATH_SEPARATOR/opt/sfw/bin
 do
   IFS=$as_save_IFS
@@ -3143,7 +3188,7 @@
 	   as_fn_executable_p "$as_dir$ac_prog$ac_exec_ext" || continue
 	   case `"$as_dir$ac_prog$ac_exec_ext" --version 2>&1` in #(
 	     'mkdir ('*'coreutils) '* | \
-	     'BusyBox '* | \
+	     *'BusyBox '* | \
 	     'mkdir (fileutils) '4.1*)
 	       ac_cv_path_mkdir=$as_dir$ac_prog$ac_exec_ext
 	       break 3;;
@@ -3152,18 +3197,17 @@
        done
   done
 IFS=$as_save_IFS
-
+ ;;
+esac
 fi
 
   test -d ./--version && rmdir ./--version
   if test ${ac_cv_path_mkdir+y}; then
     MKDIR_P="$ac_cv_path_mkdir -p"
   else
-    # As a last resort, use the slow shell script.  Don't cache a
-    # value for MKDIR_P within a source directory, because that will
-    # break other packages using the cache if that directory is
-    # removed, or if the value is a relative name.
-    MKDIR_P="$ac_install_sh -d"
+    # As a last resort, use plain mkdir -p,
+    # in the hope it doesn't have the bugs of ancient mkdir.
+    MKDIR_P='mkdir -p'
   fi
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $MKDIR_P" >&5
@@ -3178,8 +3222,8 @@
 if test ${ac_cv_prog_AWK+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$AWK"; then
+else case e in #(
+  e) if test -n "$AWK"; then
   ac_cv_prog_AWK="$AWK" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -3201,7 +3245,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 AWK=$ac_cv_prog_AWK
 if test -n "$AWK"; then
@@ -3223,8 +3268,8 @@
 if eval test \${ac_cv_prog_make_${ac_make}_set+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat >conftest.make <<\_ACEOF
+else case e in #(
+  e) cat >conftest.make <<\_ACEOF
 SHELL = /bin/sh
 all:
 	@echo '@@@%%%=$(MAKE)=@@@%%%'
@@ -3236,7 +3281,8 @@
   *)
     eval ac_cv_prog_make_${ac_make}_set=no;;
 esac
-rm -f conftest.make
+rm -f conftest.make ;;
+esac
 fi
 if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
@@ -3257,6 +3303,43 @@
 fi
 rmdir .tst 2>/dev/null
 
+am__rm_f_notfound=
+if (rm -f && rm -fr && rm -rf) 2>/dev/null
+then :
+
+else case e in #(
+  e) am__rm_f_notfound='""' ;;
+esac
+fi
+
+
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking xargs -n works" >&5
+printf %s "checking xargs -n works... " >&6; }
+if test ${am_cv_xargs_n_works+y}
+then :
+  printf %s "(cached) " >&6
+else case e in #(
+  e) if test "`echo 1 2 3 | xargs -n2 echo`" = "1 2
+3"
+then :
+  am_cv_xargs_n_works=yes
+else case e in #(
+  e) am_cv_xargs_n_works=no ;;
+esac
+fi ;;
+esac
+fi
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_xargs_n_works" >&5
+printf "%s\n" "$am_cv_xargs_n_works" >&6; }
+if test "$am_cv_xargs_n_works" = yes
+then :
+  am__xargs_n='xargs -n'
+else case e in #(
+  e)   am__xargs_n='am__xargs_n () { shift; sed "s/ /\\n/g" | while read am__xargs_n_arg; do "" "$am__xargs_n_arg"; done; }'
+ ;;
+esac
+fi
+
 if test "`cd $srcdir && pwd`" != "`pwd`"; then
   # Use -I$(srcdir) only when $(srcdir) != ., so that make's output
   # is not polluted with repeated "-I."
@@ -3279,7 +3362,7 @@
 
 # Define the identity of the package.
  PACKAGE='automake'
- VERSION='1.16.5'
+ VERSION='1.17'
 
 
 # Some tools Automake needs.
@@ -3335,57 +3418,19 @@
 
 
 
-# POSIX will say in a future version that running "rm -f" with no argument
-# is OK; and we want to be able to make that assumption in our Makefile
-# recipes.  So use an aggressive probe to check that the usage we want is
-# actually supported "in the wild" to an acceptable degree.
-# See automake bug#10828.
-# To make any issue more visible, cause the running configure to be aborted
-# by default if the 'rm' program in use doesn't match our expectations; the
-# user can still override this though.
-if rm -f && rm -fr && rm -rf; then : OK; else
-  cat >&2 <<'END'
-Oops!
-
-Your 'rm' program seems unable to run without file operands specified
-on the command line, even when the '-f' option is present.  This is contrary
-to the behaviour of most rm programs out there, and not conforming with
-the upcoming POSIX standard: <http://austingroupbugs.net/view.php?id=542>
-
-Please tell bug-automake@gnu.org about your system, including the value
-of your $PATH and any error possibly output before this message.  This
-can help us improve future automake versions.
-
-END
-  if test x"$ACCEPT_INFERIOR_RM_PROGRAM" = x"yes"; then
-    echo 'Configuration will proceed anyway, since you have set the' >&2
-    echo 'ACCEPT_INFERIOR_RM_PROGRAM variable to "yes"' >&2
-    echo >&2
-  else
-    cat >&2 <<'END'
-Aborting the configuration process, to ensure you take notice of the issue.
-
-You can download and install GNU coreutils to get an 'rm' implementation
-that behaves properly: <https://www.gnu.org/software/coreutils/>.
-
-If you want to complete the configuration process using your problematic
-'rm' anyway, export the environment variable ACCEPT_INFERIOR_RM_PROGRAM
-to "yes", and re-run configure.
 
-END
-    as_fn_error $? "Your 'rm' program is bad, sorry." "$LINENO" 5
-  fi
-fi
+
+
 
 
 # Keep this on a line of its own, since it must be found and processed
 # by the 'update-copyright' rule in our Makefile.
-RELEASE_YEAR=2021
+RELEASE_YEAR=2024
 
 
 # The API version is the base version.  We must guarantee
 # compatibility for all releases with the same API version.
-APIVERSION=1.16
+APIVERSION=1.17
 
 
 pkgvdatadir="\${datadir}/$PACKAGE-$APIVERSION"
@@ -3425,8 +3470,8 @@
 if test ${ac_cv_path_PERL+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  case $PERL in
+else case e in #(
+  e) case $PERL in
   \\/* | ?:\\/*)
   ac_cv_path_PERL="$PERL" # Let the user override the test with a path.
   ;;
@@ -3451,6 +3496,7 @@
 IFS=$as_save_IFS
 
   ;;
+esac ;;
 esac
 fi
 PERL=$ac_cv_path_PERL
@@ -3463,9 +3509,17 @@
 fi
 
 
-if test -z "$PERL"; then
+case $PERL in
+ '')
    as_fn_error $? "perl not found" "$LINENO" 5
-fi
+   ;;
+ *' '* | *'	'*)
+  as_fn_error $? "The path to your Perl contains spaces or tabs.
+This would cause build failures later or unusable programs.
+Please use a path without spaces and try again." "$LINENO" 5
+  ;;
+esac
+
 # Save details about the selected perl interpreter in config.log.
 { echo "$as_me:$LINENO: $PERL --version" >&5
    ($PERL --version) >&5 2>&5
@@ -3473,7 +3527,7 @@
    echo "$as_me:$LINENO: \$? = $ac_status" >&5
    (exit $ac_status); }
 $PERL -e 'require 5.006;' || {
-   as_fn_error $? "perl 5.6 or better is required; perl 5.8.2 or better
+   as_fn_error $? "perl 5.6 or better is required; perl 5.10 or better
 is recommended.  If you have several perl versions
 installed, select the one Automake should use using
   ./configure PERL=/path/to/perl" "$LINENO" 5
@@ -3487,8 +3541,8 @@
 if test ${ac_cv_prog_TEX+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$TEX"; then
+else case e in #(
+  e) if test -n "$TEX"; then
   ac_cv_prog_TEX="$TEX" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -3510,7 +3564,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 TEX=$ac_cv_prog_TEX
 if test -n "$TEX"; then
@@ -3551,8 +3606,8 @@
 if test ${ac_cv_prog_YACC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$YACC"; then
+else case e in #(
+  e) if test -n "$YACC"; then
   ac_cv_prog_YACC="$YACC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -3574,7 +3629,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 YACC=$ac_cv_prog_YACC
 if test -n "$YACC"; then
@@ -3599,8 +3655,8 @@
 if test ${ac_cv_prog_LEX+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$LEX"; then
+else case e in #(
+  e) if test -n "$LEX"; then
   ac_cv_prog_LEX="$LEX" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -3622,7 +3678,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 LEX=$ac_cv_prog_LEX
 if test -n "$LEX"; then
@@ -3652,8 +3709,8 @@
 if test ${am_cv_autoconf_installed+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if { echo "$as_me:$LINENO: $am_AUTOCONF --version" >&5
+else case e in #(
+  e) if { echo "$as_me:$LINENO: $am_AUTOCONF --version" >&5
    ($am_AUTOCONF --version) >&5 2>&5
    ac_status=$?
    echo "$as_me:$LINENO: \$? = $ac_status" >&5
@@ -3662,7 +3719,8 @@
   am_cv_autoconf_installed=yes
 else
   am_cv_autoconf_installed=no
-fi
+fi ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_autoconf_installed" >&5
 printf "%s\n" "$am_cv_autoconf_installed" >&6; }
@@ -3676,8 +3734,8 @@
 if test ${am_cv_autoconf_works+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  mkdir conftest
+else case e in #(
+  e) mkdir conftest
 printf '%s\n' > conftest/conftest.ac \
   'AC''_INIT(smoke-test, 1)' \
   'AC''_OUTPUT'
@@ -3691,7 +3749,8 @@
 else
   am_cv_autoconf_works=no
 fi
-rm -rf conftest
+rm -rf conftest ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_autoconf_works" >&5
 printf "%s\n" "$am_cv_autoconf_works" >&6; }
@@ -3705,8 +3764,8 @@
 if test ${am_cv_autoconf_version+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  mkdir conftest
+else case e in #(
+  e) mkdir conftest
 printf '%s\n' > conftest/conftest.ac \
   'AC'"_PREREQ($required_autoconf_version)" \
   'AC''_INIT(smoke-test, 1)' \
@@ -3721,7 +3780,8 @@
 else
   am_cv_autoconf_version=no
 fi
-rm -rf conftest
+rm -rf conftest ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_autoconf_version" >&5
 printf "%s\n" "$am_cv_autoconf_version" >&6; }
@@ -3735,8 +3795,8 @@
 if test ${am_cv_prog_ln+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-
+else case e in #(
+  e)
 rm -f conftest conftest.file
 : >conftest.file
 if ln conftest.file conftest 2>/dev/null; then
@@ -3744,7 +3804,8 @@
 else
   am_cv_prog_ln='cp -p'
 fi
-rm -f conftest conftest.file
+rm -f conftest conftest.file ;;
+esac
 fi
 
 LN=$am_cv_prog_ln
@@ -3754,17 +3815,6 @@
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $result" >&5
 printf "%s\n" "$result" >&6; }
 
-# The amount we should wait after modifying files depends on the platform.
-# On Windows '95, '98 and ME, files modifications have 2-seconds
-# granularity and can be up to 3 seconds in the future w.r.t. the
-# system clock.  When it is important to ensure one file is older
-# than another we wait at least 5 seconds between creations.
-case $build in
-  *-pc-msdosdjgpp) MODIFICATION_DELAY=5;;
-  *)               MODIFICATION_DELAY=2;;
-esac
-
-
 ## ------------------------------------------- ##
 ##  Test for things needed by the test suite.  ##
 ## ------------------------------------------- ##
@@ -3774,8 +3824,8 @@
 if test ${ac_cv_path_GREP+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -z "$GREP"; then
+else case e in #(
+  e) if test -z "$GREP"; then
   ac_path_GREP_found=false
   # Loop through the user's path and test for each of PROGNAME-LIST
   as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -3794,9 +3844,10 @@
       as_fn_executable_p "$ac_path_GREP" || continue
 # Check for GNU ac_path_GREP and select it if it is found.
   # Check for GNU $ac_path_GREP
-case `"$ac_path_GREP" --version 2>&1` in
+case `"$ac_path_GREP" --version 2>&1` in #(
 *GNU*)
   ac_cv_path_GREP="$ac_path_GREP" ac_path_GREP_found=:;;
+#(
 *)
   ac_count=0
   printf %s 0123456789 >"conftest.in"
@@ -3831,7 +3882,8 @@
 else
   ac_cv_path_GREP=$GREP
 fi
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_GREP" >&5
 printf "%s\n" "$ac_cv_path_GREP" >&6; }
@@ -3843,8 +3895,8 @@
 if test ${ac_cv_path_EGREP+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if echo a | $GREP -E '(a|b)' >/dev/null 2>&1
+else case e in #(
+  e) if echo a | $GREP -E '(a|b)' >/dev/null 2>&1
    then ac_cv_path_EGREP="$GREP -E"
    else
      if test -z "$EGREP"; then
@@ -3866,9 +3918,10 @@
       as_fn_executable_p "$ac_path_EGREP" || continue
 # Check for GNU ac_path_EGREP and select it if it is found.
   # Check for GNU $ac_path_EGREP
-case `"$ac_path_EGREP" --version 2>&1` in
+case `"$ac_path_EGREP" --version 2>&1` in #(
 *GNU*)
   ac_cv_path_EGREP="$ac_path_EGREP" ac_path_EGREP_found=:;;
+#(
 *)
   ac_count=0
   printf %s 0123456789 >"conftest.in"
@@ -3904,20 +3957,23 @@
   ac_cv_path_EGREP=$EGREP
 fi
 
-   fi
+   fi ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_EGREP" >&5
 printf "%s\n" "$ac_cv_path_EGREP" >&6; }
  EGREP="$ac_cv_path_EGREP"
 
+         EGREP_TRADITIONAL=$EGREP
+ ac_cv_path_EGREP_TRADITIONAL=$EGREP
 
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for fgrep" >&5
 printf %s "checking for fgrep... " >&6; }
 if test ${ac_cv_path_FGREP+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if echo 'ab*c' | $GREP -F 'ab*c' >/dev/null 2>&1
+else case e in #(
+  e) if echo 'ab*c' | $GREP -F 'ab*c' >/dev/null 2>&1
    then ac_cv_path_FGREP="$GREP -F"
    else
      if test -z "$FGREP"; then
@@ -3939,9 +3995,10 @@
       as_fn_executable_p "$ac_path_FGREP" || continue
 # Check for GNU ac_path_FGREP and select it if it is found.
   # Check for GNU $ac_path_FGREP
-case `"$ac_path_FGREP" --version 2>&1` in
+case `"$ac_path_FGREP" --version 2>&1` in #(
 *GNU*)
   ac_cv_path_FGREP="$ac_path_FGREP" ac_path_FGREP_found=:;;
+#(
 *)
   ac_count=0
   printf %s 0123456789 >"conftest.in"
@@ -3977,7 +4034,8 @@
   ac_cv_path_FGREP=$FGREP
 fi
 
-   fi
+   fi ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_FGREP" >&5
 printf "%s\n" "$ac_cv_path_FGREP" >&6; }
@@ -3985,6 +4043,17 @@
 
 
 
+# The test suite needs to know the resolution of timestamps
+# supported by the filesystem hosting the build.  The value
+# will be acceptable to 'sleep' on this system.
+MTIME_RESOLUTION=$am_cv_filesystem_timestamp_resolution
+if test -z "$MTIME_RESOLUTION"; then
+  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: am_cv_filesystem_timestamp_resolution strangely not set; using 1" >&5
+printf "%s\n" "$as_me: am_cv_filesystem_timestamp_resolution strangely not set; using 1" >&6;}
+  MTIME_RESOLUTION=1
+fi
+
+
 
 
 
@@ -4027,7 +4096,6 @@
 
 am_bourne_compatible="# Be more Bourne compatible
 DUALCASE=1; export DUALCASE # for MKS sh
-as_nop=:
 if test \${ZSH_VERSION+y} && (emulate sh) >/dev/null 2>&1
 then :
   emulate sh
@@ -4036,12 +4104,13 @@
   # is contrary to our usage.  Disable this feature.
   alias -g '\${1+\"\$@\"}'='\"\$@\"'
   setopt NO_GLOB_SUBST
-else \$as_nop
-  case \`(set -o) 2>/dev/null\` in #(
+else case e in #(
+  e) case \`(set -o) 2>/dev/null\` in #(
   *posix*) :
     set -o posix ;; #(
   *) :
      ;;
+esac ;;
 esac
 fi
 
@@ -4049,8 +4118,8 @@
 if test ${ac_cv_AM_TEST_RUNNER_SHELL+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test "$AM_TEST_RUNNER_SHELL"; then
+else case e in #(
+  e) if test "$AM_TEST_RUNNER_SHELL"; then
     # Let the user override it.
     ac_cv_AM_TEST_RUNNER_SHELL=$AM_TEST_RUNNER_SHELL
   else
@@ -4066,8 +4135,8 @@
 if test ${ac_cv_path_am_candidate_sh+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  case $am_candidate_sh in
+else case e in #(
+  e) case $am_candidate_sh in
   \\/* | ?:\\/*)
   ac_cv_path_am_candidate_sh="$am_candidate_sh" # Let the user override the test with a path.
   ;;
@@ -4092,6 +4161,7 @@
 IFS=$as_save_IFS
 
   ;;
+esac ;;
 esac
 fi
 am_candidate_sh=$ac_cv_path_am_candidate_sh
@@ -4346,15 +4416,16 @@
       fi
     done
   fi
-  AM_TEST_RUNNER_SHELL=$ac_cv_AM_TEST_RUNNER_SHELL
+  AM_TEST_RUNNER_SHELL=$ac_cv_AM_TEST_RUNNER_SHELL ;;
+esac
 fi
 
 
 if test $AM_TEST_RUNNER_SHELL = no; then
-  { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-printf "%s\n" "$as_me: error: in \`$ac_pwd':" >&2;}
+  { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in '$ac_pwd':" >&5
+printf "%s\n" "$as_me: error: in '$ac_pwd':" >&2;}
 as_fn_error $? "no POSIX shell found that is good enough to be used in our testsuite
-See \`config.log' for more details" "$LINENO" 5; }
+See 'config.log' for more details" "$LINENO" 5; }
 else
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: will use $AM_TEST_RUNNER_SHELL as the testsuite shell" >&5
 printf "%s\n" "$as_me: will use $AM_TEST_RUNNER_SHELL as the testsuite shell" >&6;}
@@ -4396,6 +4467,9 @@
 
 
 
+
+
+
   am__failed=no
   while :; do
        ac_ext=c
@@ -4413,8 +4487,8 @@
 if test ${ac_cv_prog_CC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$CC"; then
+else case e in #(
+  e) if test -n "$CC"; then
   ac_cv_prog_CC="$CC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -4436,7 +4510,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 CC=$ac_cv_prog_CC
 if test -n "$CC"; then
@@ -4462,8 +4537,8 @@
 if test ${ac_cv_prog_ac_ct_CC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_CC"; then
+else case e in #(
+  e) if test -n "$ac_ct_CC"; then
   ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -4485,7 +4560,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_CC=$ac_cv_prog_ac_ct_CC
 if test -n "$ac_ct_CC"; then
@@ -4591,8 +4667,8 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
-# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
+  # Autoconf-2.13 could set the ac_cv_exeext variable to 'no'.
+# So ignore a value of 'no', otherwise this would lead to 'EXEEXT = no'
 # in a Makefile.  We should not override ac_cv_exeext if it was cached,
 # so that the user can short-circuit this test for compilers unknown to
 # Autoconf.
@@ -4612,7 +4688,7 @@
 	   ac_cv_exeext=`expr "$ac_file" : '^.*$\..*$'`
 	fi
 	# We set ac_cv_exeext here because the later test for it is not
-	# safe: cross compilers may not add the suffix if given an `-o'
+	# safe: cross compilers may not add the suffix if given an '-o'
 	# argument, so we may need to know it at that point already.
 	# Even if this section looks crufty: it has the advantage of
 	# actually working.
@@ -4623,8 +4699,9 @@
 done
 test "$ac_cv_exeext" = no && ac_cv_exeext=
 
-else $as_nop
-  ac_file=''
+else case e in #(
+  e) ac_file='' ;;
+esac
 fi
 if test -z "$ac_file"
 then :
@@ -4639,9 +4716,10 @@
   am__failed=yes
   break
 }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-printf "%s\n" "yes" >&6; }
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
+printf "%s\n" "yes" >&6; } ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for C compiler default output file name" >&5
 printf %s "checking for C compiler default output file name... " >&6; }
@@ -4665,10 +4743,10 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # If both `conftest.exe' and `conftest' are `present' (well, observable)
-# catch `conftest.exe'.  For instance with Cygwin, `ls conftest' will
-# work properly (i.e., refer to `conftest.exe'), while it won't with
-# `rm'.
+  # If both 'conftest.exe' and 'conftest' are 'present' (well, observable)
+# catch 'conftest.exe'.  For instance with Cygwin, 'ls conftest' will
+# work properly (i.e., refer to 'conftest.exe'), while it won't with
+# 'rm'.
 for ac_file in conftest.exe conftest conftest.*; do
   test -f "$ac_file" || continue
   case $ac_file in
@@ -4678,13 +4756,14 @@
     * ) break;;
   esac
 done
-else $as_nop
-   {
+else case e in #(
+  e)  {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot compute suffix of executables: cannot compile and link" >&5
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of executables: cannot compile and link" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
 rm -f conftest conftest$ac_cv_exeext
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
@@ -4700,6 +4779,8 @@
 main (void)
 {
 FILE *f = fopen ("conftest.out", "w");
+ if (!f)
+  return 1;
  return ferror (f) || fclose (f) != 0;
 
   ;
@@ -4741,9 +4822,9 @@
     else
 	 {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot run C compiled programs.
-If you meant to cross compile, use \`--host'." >&5
+If you meant to cross compile, use '--host'." >&5
 printf "%s\n" "$as_me: WARNING: cannot run C compiled programs.
-If you meant to cross compile, use \`--host'." >&2;}
+If you meant to cross compile, use '--host'." >&2;}
   am__failed=yes
   break
 }
@@ -4753,15 +4834,16 @@
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
 printf "%s\n" "$cross_compiling" >&6; }
 
-rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
+rm -f conftest.$ac_ext conftest$ac_cv_exeext \
+  conftest.o conftest.obj conftest.out
 ac_clean_files=$ac_clean_files_save
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
 printf %s "checking for suffix of object files... " >&6; }
 if test ${ac_cv_objext+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+else case e in #(
+  e) cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
 int
@@ -4793,8 +4875,8 @@
        break;;
   esac
 done
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
  {
@@ -4802,9 +4884,11 @@
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of object files: cannot compile" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
-rm -f conftest.$ac_cv_objext conftest.$ac_ext
+rm -f conftest.$ac_cv_objext conftest.$ac_ext ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
 printf "%s\n" "$ac_cv_objext" >&6; }
@@ -4815,8 +4899,8 @@
 if test ${ac_cv_c_compiler_gnu+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+else case e in #(
+  e) cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
 int
@@ -4833,12 +4917,14 @@
 if ac_fn_c_try_compile "$LINENO"
 then :
   ac_compiler_gnu=yes
-else $as_nop
-  ac_compiler_gnu=no
+else case e in #(
+  e) ac_compiler_gnu=no ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
 ac_cv_c_compiler_gnu=$ac_compiler_gnu
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_compiler_gnu" >&5
 printf "%s\n" "$ac_cv_c_compiler_gnu" >&6; }
@@ -4856,8 +4942,8 @@
 if test ${ac_cv_prog_cc_g+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  ac_save_c_werror_flag=$ac_c_werror_flag
+else case e in #(
+  e) ac_save_c_werror_flag=$ac_c_werror_flag
    ac_c_werror_flag=yes
    ac_cv_prog_cc_g=no
    CFLAGS="-g"
@@ -4875,8 +4961,8 @@
 if ac_fn_c_try_compile "$LINENO"
 then :
   ac_cv_prog_cc_g=yes
-else $as_nop
-  CFLAGS=""
+else case e in #(
+  e) CFLAGS=""
       cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
@@ -4891,8 +4977,8 @@
 if ac_fn_c_try_compile "$LINENO"
 then :
 
-else $as_nop
-  ac_c_werror_flag=$ac_save_c_werror_flag
+else case e in #(
+  e) ac_c_werror_flag=$ac_save_c_werror_flag
 	 CFLAGS="-g"
 	 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
@@ -4909,12 +4995,15 @@
 then :
   ac_cv_prog_cc_g=yes
 fi
-rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
+rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext ;;
+esac
 fi
-rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
+rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
-   ac_c_werror_flag=$ac_save_c_werror_flag
+   ac_c_werror_flag=$ac_save_c_werror_flag ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_g" >&5
 printf "%s\n" "$ac_cv_prog_cc_g" >&6; }
@@ -4936,19 +5025,68 @@
 ac_prog_cc_stdc=no
 if test x$ac_prog_cc_stdc = xno
 then :
+  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for $CC option to enable C23 features" >&5
+printf %s "checking for $CC option to enable C23 features... " >&6; }
+if test ${ac_cv_prog_cc_c23+y}
+then :
+  printf %s "(cached) " >&6
+else case e in #(
+  e) ac_cv_prog_cc_c23=no
+ac_save_CC=$CC
+cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+$ac_c_conftest_c23_program
+_ACEOF
+for ac_arg in '' -std=gnu23
+do
+  CC="$ac_save_CC $ac_arg"
+  if ac_fn_c_try_compile "$LINENO"
+then :
+  ac_cv_prog_cc_c23=$ac_arg
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.beam
+  test "x$ac_cv_prog_cc_c23" != "xno" && break
+done
+rm -f conftest.$ac_ext
+CC=$ac_save_CC ;;
+esac
+fi
+
+if test "x$ac_cv_prog_cc_c23" = xno
+then :
+  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
+printf "%s\n" "unsupported" >&6; }
+else case e in #(
+  e) if test "x$ac_cv_prog_cc_c23" = x
+then :
+  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
+printf "%s\n" "none needed" >&6; }
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c23" >&5
+printf "%s\n" "$ac_cv_prog_cc_c23" >&6; }
+     CC="$CC $ac_cv_prog_cc_c23" ;;
+esac
+fi
+  ac_cv_prog_cc_stdc=$ac_cv_prog_cc_c23
+  ac_prog_cc_stdc=c23 ;;
+esac
+fi
+fi
+if test x$ac_prog_cc_stdc = xno
+then :
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for $CC option to enable C11 features" >&5
 printf %s "checking for $CC option to enable C11 features... " >&6; }
 if test ${ac_cv_prog_cc_c11+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  ac_cv_prog_cc_c11=no
+else case e in #(
+  e) ac_cv_prog_cc_c11=no
 ac_save_CC=$CC
 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 $ac_c_conftest_c11_program
 _ACEOF
-for ac_arg in '' -std=gnu11
+for ac_arg in '' -std=gnu11 -std:c11
 do
   CC="$ac_save_CC $ac_arg"
   if ac_fn_c_try_compile "$LINENO"
@@ -4959,25 +5097,28 @@
   test "x$ac_cv_prog_cc_c11" != "xno" && break
 done
 rm -f conftest.$ac_ext
-CC=$ac_save_CC
+CC=$ac_save_CC ;;
+esac
 fi
 
 if test "x$ac_cv_prog_cc_c11" = xno
 then :
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
 printf "%s\n" "unsupported" >&6; }
-else $as_nop
-  if test "x$ac_cv_prog_cc_c11" = x
+else case e in #(
+  e) if test "x$ac_cv_prog_cc_c11" = x
 then :
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
 printf "%s\n" "none needed" >&6; }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c11" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c11" >&5
 printf "%s\n" "$ac_cv_prog_cc_c11" >&6; }
-     CC="$CC $ac_cv_prog_cc_c11"
+     CC="$CC $ac_cv_prog_cc_c11" ;;
+esac
 fi
   ac_cv_prog_cc_stdc=$ac_cv_prog_cc_c11
-  ac_prog_cc_stdc=c11
+  ac_prog_cc_stdc=c11 ;;
+esac
 fi
 fi
 if test x$ac_prog_cc_stdc = xno
@@ -4987,8 +5128,8 @@
 if test ${ac_cv_prog_cc_c99+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  ac_cv_prog_cc_c99=no
+else case e in #(
+  e) ac_cv_prog_cc_c99=no
 ac_save_CC=$CC
 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
@@ -5005,25 +5146,28 @@
   test "x$ac_cv_prog_cc_c99" != "xno" && break
 done
 rm -f conftest.$ac_ext
-CC=$ac_save_CC
+CC=$ac_save_CC ;;
+esac
 fi
 
 if test "x$ac_cv_prog_cc_c99" = xno
 then :
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
 printf "%s\n" "unsupported" >&6; }
-else $as_nop
-  if test "x$ac_cv_prog_cc_c99" = x
+else case e in #(
+  e) if test "x$ac_cv_prog_cc_c99" = x
 then :
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
 printf "%s\n" "none needed" >&6; }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c99" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c99" >&5
 printf "%s\n" "$ac_cv_prog_cc_c99" >&6; }
-     CC="$CC $ac_cv_prog_cc_c99"
+     CC="$CC $ac_cv_prog_cc_c99" ;;
+esac
 fi
   ac_cv_prog_cc_stdc=$ac_cv_prog_cc_c99
-  ac_prog_cc_stdc=c99
+  ac_prog_cc_stdc=c99 ;;
+esac
 fi
 fi
 if test x$ac_prog_cc_stdc = xno
@@ -5033,8 +5177,8 @@
 if test ${ac_cv_prog_cc_c89+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  ac_cv_prog_cc_c89=no
+else case e in #(
+  e) ac_cv_prog_cc_c89=no
 ac_save_CC=$CC
 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
@@ -5051,25 +5195,28 @@
   test "x$ac_cv_prog_cc_c89" != "xno" && break
 done
 rm -f conftest.$ac_ext
-CC=$ac_save_CC
+CC=$ac_save_CC ;;
+esac
 fi
 
 if test "x$ac_cv_prog_cc_c89" = xno
 then :
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
 printf "%s\n" "unsupported" >&6; }
-else $as_nop
-  if test "x$ac_cv_prog_cc_c89" = x
+else case e in #(
+  e) if test "x$ac_cv_prog_cc_c89" = x
 then :
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
 printf "%s\n" "none needed" >&6; }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c89" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c89" >&5
 printf "%s\n" "$ac_cv_prog_cc_c89" >&6; }
-     CC="$CC $ac_cv_prog_cc_c89"
+     CC="$CC $ac_cv_prog_cc_c89" ;;
+esac
 fi
   ac_cv_prog_cc_stdc=$ac_cv_prog_cc_c89
-  ac_prog_cc_stdc=c89
+  ac_prog_cc_stdc=c89 ;;
+esac
 fi
 fi
 
@@ -5090,8 +5237,8 @@
 if test ${am_cv_prog_cc_c_o+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+else case e in #(
+  e) cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
 int
@@ -5121,7 +5268,8 @@
     fi
   done
   rm -f core conftest*
-  unset am_i
+  unset am_i ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_prog_cc_c_o" >&5
 printf "%s\n" "$am_cv_prog_cc_c_o" >&6; }
@@ -5163,8 +5311,9 @@
 if test x"$GCC" = x"yes"
 then :
   am_CC_is_GNU=yes
-else $as_nop
-  am_CC_is_GNU=no
+else case e in #(
+  e) am_CC_is_GNU=no ;;
+esac
 fi
 
 # On case-insensitive file systems (seen e.g. on Cygwin and Mac OS X)
@@ -5173,11 +5322,13 @@
 # to a C++ compiler as expected (see automake bugs #11893 and #10766).
 # Similarly, we must avoid looking for 'RCC', as that can point to the
 # Qt4 "Resource Compiler": <http://doc.qt.digia.com/4.2/rcc.html>
+# And we avoid looking for 'KCC' as that can be a kerberos tool under
+# macOS systems.
 if test -f /bIn/rMdIr || test -f /uSr/bIn/rMdIr; then
   # Case-insensitive file system, don't look for CC.
-  am_CC= am_RCC=
+  am_CC= am_RCC= am_KCC=
 else
-  am_CC=CC am_RCC=RCC
+  am_CC=CC am_RCC=RCC am_KCC=KCC
 fi
 
 # The list of C++ compilers here has been copied, pasted and edited
@@ -5187,12 +5338,6 @@
 
 
 
-
-
-
-
-
-
   am__failed=no
   while :; do
      ac_ext=cpp
@@ -5205,7 +5350,7 @@
     CXX=$CCC
   else
     if test -n "$ac_tool_prefix"; then
-  for ac_prog in   aCC $am_CC FCC KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++
+  for ac_prog in   aCC $am_CC FCC $am_KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++ clang++
   do
     # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args.
 set dummy $ac_tool_prefix$ac_prog; ac_word=$2
@@ -5214,8 +5359,8 @@
 if test ${ac_cv_prog_CXX+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$CXX"; then
+else case e in #(
+  e) if test -n "$CXX"; then
   ac_cv_prog_CXX="$CXX" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -5237,7 +5382,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 CXX=$ac_cv_prog_CXX
 if test -n "$CXX"; then
@@ -5254,7 +5400,7 @@
 fi
 if test -z "$CXX"; then
   ac_ct_CXX=$CXX
-  for ac_prog in   aCC $am_CC FCC KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++
+  for ac_prog in   aCC $am_CC FCC $am_KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++ clang++
 do
   # Extract the first word of "$ac_prog", so it can be a program name with args.
 set dummy $ac_prog; ac_word=$2
@@ -5263,8 +5409,8 @@
 if test ${ac_cv_prog_ac_ct_CXX+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_CXX"; then
+else case e in #(
+  e) if test -n "$ac_ct_CXX"; then
   ac_cv_prog_ac_ct_CXX="$ac_ct_CXX" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -5286,7 +5432,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_CXX=$ac_cv_prog_ac_ct_CXX
 if test -n "$ac_ct_CXX"; then
@@ -5386,8 +5533,8 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
-# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
+  # Autoconf-2.13 could set the ac_cv_exeext variable to 'no'.
+# So ignore a value of 'no', otherwise this would lead to 'EXEEXT = no'
 # in a Makefile.  We should not override ac_cv_exeext if it was cached,
 # so that the user can short-circuit this test for compilers unknown to
 # Autoconf.
@@ -5407,7 +5554,7 @@
 	   ac_cv_exeext=`expr "$ac_file" : '^.*$\..*$'`
 	fi
 	# We set ac_cv_exeext here because the later test for it is not
-	# safe: cross compilers may not add the suffix if given an `-o'
+	# safe: cross compilers may not add the suffix if given an '-o'
 	# argument, so we may need to know it at that point already.
 	# Even if this section looks crufty: it has the advantage of
 	# actually working.
@@ -5418,8 +5565,9 @@
 done
 test "$ac_cv_exeext" = no && ac_cv_exeext=
 
-else $as_nop
-  ac_file=''
+else case e in #(
+  e) ac_file='' ;;
+esac
 fi
 if test -z "$ac_file"
 then :
@@ -5434,9 +5582,10 @@
   am__failed=yes
   break
 }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-printf "%s\n" "yes" >&6; }
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
+printf "%s\n" "yes" >&6; } ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for C++ compiler default output file name" >&5
 printf %s "checking for C++ compiler default output file name... " >&6; }
@@ -5460,10 +5609,10 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # If both `conftest.exe' and `conftest' are `present' (well, observable)
-# catch `conftest.exe'.  For instance with Cygwin, `ls conftest' will
-# work properly (i.e., refer to `conftest.exe'), while it won't with
-# `rm'.
+  # If both 'conftest.exe' and 'conftest' are 'present' (well, observable)
+# catch 'conftest.exe'.  For instance with Cygwin, 'ls conftest' will
+# work properly (i.e., refer to 'conftest.exe'), while it won't with
+# 'rm'.
 for ac_file in conftest.exe conftest conftest.*; do
   test -f "$ac_file" || continue
   case $ac_file in
@@ -5473,13 +5622,14 @@
     * ) break;;
   esac
 done
-else $as_nop
-   {
+else case e in #(
+  e)  {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot compute suffix of executables: cannot compile and link" >&5
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of executables: cannot compile and link" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
 rm -f conftest conftest$ac_cv_exeext
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
@@ -5495,6 +5645,8 @@
 main (void)
 {
 FILE *f = fopen ("conftest.out", "w");
+ if (!f)
+  return 1;
  return ferror (f) || fclose (f) != 0;
 
   ;
@@ -5536,9 +5688,9 @@
     else
 	 {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot run C++ compiled programs.
-If you meant to cross compile, use \`--host'." >&5
+If you meant to cross compile, use '--host'." >&5
 printf "%s\n" "$as_me: WARNING: cannot run C++ compiled programs.
-If you meant to cross compile, use \`--host'." >&2;}
+If you meant to cross compile, use '--host'." >&2;}
   am__failed=yes
   break
 }
@@ -5548,15 +5700,16 @@
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
 printf "%s\n" "$cross_compiling" >&6; }
 
-rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
+rm -f conftest.$ac_ext conftest$ac_cv_exeext \
+  conftest.o conftest.obj conftest.out
 ac_clean_files=$ac_clean_files_save
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
 printf %s "checking for suffix of object files... " >&6; }
 if test ${ac_cv_objext+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+else case e in #(
+  e) cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
 int
@@ -5588,8 +5741,8 @@
        break;;
   esac
 done
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
  {
@@ -5597,9 +5750,11 @@
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of object files: cannot compile" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
-rm -f conftest.$ac_cv_objext conftest.$ac_ext
+rm -f conftest.$ac_cv_objext conftest.$ac_ext ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
 printf "%s\n" "$ac_cv_objext" >&6; }
@@ -5610,8 +5765,8 @@
 if test ${ac_cv_cxx_compiler_gnu+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+else case e in #(
+  e) cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
 int
@@ -5628,12 +5783,14 @@
 if ac_fn_cxx_try_compile "$LINENO"
 then :
   ac_compiler_gnu=yes
-else $as_nop
-  ac_compiler_gnu=no
+else case e in #(
+  e) ac_compiler_gnu=no ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
 ac_cv_cxx_compiler_gnu=$ac_compiler_gnu
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
 printf "%s\n" "$ac_cv_cxx_compiler_gnu" >&6; }
@@ -5651,8 +5808,8 @@
 if test ${ac_cv_prog_cxx_g+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  ac_save_cxx_werror_flag=$ac_cxx_werror_flag
+else case e in #(
+  e) ac_save_cxx_werror_flag=$ac_cxx_werror_flag
    ac_cxx_werror_flag=yes
    ac_cv_prog_cxx_g=no
    CXXFLAGS="-g"
@@ -5670,8 +5827,8 @@
 if ac_fn_cxx_try_compile "$LINENO"
 then :
   ac_cv_prog_cxx_g=yes
-else $as_nop
-  CXXFLAGS=""
+else case e in #(
+  e) CXXFLAGS=""
       cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
@@ -5686,8 +5843,8 @@
 if ac_fn_cxx_try_compile "$LINENO"
 then :
 
-else $as_nop
-  ac_cxx_werror_flag=$ac_save_cxx_werror_flag
+else case e in #(
+  e) ac_cxx_werror_flag=$ac_save_cxx_werror_flag
 	 CXXFLAGS="-g"
 	 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
@@ -5704,12 +5861,15 @@
 then :
   ac_cv_prog_cxx_g=yes
 fi
-rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
+rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext ;;
+esac
 fi
-rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
+rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
-   ac_cxx_werror_flag=$ac_save_cxx_werror_flag
+   ac_cxx_werror_flag=$ac_save_cxx_werror_flag ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_g" >&5
 printf "%s\n" "$ac_cv_prog_cxx_g" >&6; }
@@ -5728,100 +5888,6 @@
     CXXFLAGS=
   fi
 fi
-ac_prog_cxx_stdcxx=no
-if test x$ac_prog_cxx_stdcxx = xno
-then :
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for $CXX option to enable C++11 features" >&5
-printf %s "checking for $CXX option to enable C++11 features... " >&6; }
-if test ${ac_cv_prog_cxx_11+y}
-then :
-  printf %s "(cached) " >&6
-else $as_nop
-  ac_cv_prog_cxx_11=no
-ac_save_CXX=$CXX
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h.  */
-$ac_cxx_conftest_cxx11_program
-_ACEOF
-for ac_arg in '' -std=gnu++11 -std=gnu++0x -std=c++11 -std=c++0x -qlanglvl=extended0x -AA
-do
-  CXX="$ac_save_CXX $ac_arg"
-  if ac_fn_cxx_try_compile "$LINENO"
-then :
-  ac_cv_prog_cxx_cxx11=$ac_arg
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.beam
-  test "x$ac_cv_prog_cxx_cxx11" != "xno" && break
-done
-rm -f conftest.$ac_ext
-CXX=$ac_save_CXX
-fi
-
-if test "x$ac_cv_prog_cxx_cxx11" = xno
-then :
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
-printf "%s\n" "unsupported" >&6; }
-else $as_nop
-  if test "x$ac_cv_prog_cxx_cxx11" = x
-then :
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
-printf "%s\n" "none needed" >&6; }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_cxx11" >&5
-printf "%s\n" "$ac_cv_prog_cxx_cxx11" >&6; }
-     CXX="$CXX $ac_cv_prog_cxx_cxx11"
-fi
-  ac_cv_prog_cxx_stdcxx=$ac_cv_prog_cxx_cxx11
-  ac_prog_cxx_stdcxx=cxx11
-fi
-fi
-if test x$ac_prog_cxx_stdcxx = xno
-then :
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for $CXX option to enable C++98 features" >&5
-printf %s "checking for $CXX option to enable C++98 features... " >&6; }
-if test ${ac_cv_prog_cxx_98+y}
-then :
-  printf %s "(cached) " >&6
-else $as_nop
-  ac_cv_prog_cxx_98=no
-ac_save_CXX=$CXX
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h.  */
-$ac_cxx_conftest_cxx98_program
-_ACEOF
-for ac_arg in '' -std=gnu++98 -std=c++98 -qlanglvl=extended -AA
-do
-  CXX="$ac_save_CXX $ac_arg"
-  if ac_fn_cxx_try_compile "$LINENO"
-then :
-  ac_cv_prog_cxx_cxx98=$ac_arg
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.beam
-  test "x$ac_cv_prog_cxx_cxx98" != "xno" && break
-done
-rm -f conftest.$ac_ext
-CXX=$ac_save_CXX
-fi
-
-if test "x$ac_cv_prog_cxx_cxx98" = xno
-then :
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
-printf "%s\n" "unsupported" >&6; }
-else $as_nop
-  if test "x$ac_cv_prog_cxx_cxx98" = x
-then :
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
-printf "%s\n" "none needed" >&6; }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_cxx98" >&5
-printf "%s\n" "$ac_cv_prog_cxx_cxx98" >&6; }
-     CXX="$CXX $ac_cv_prog_cxx_cxx98"
-fi
-  ac_cv_prog_cxx_stdcxx=$ac_cv_prog_cxx_cxx98
-  ac_prog_cxx_stdcxx=cxx98
-fi
-fi
-
 ac_ext=c
 ac_cpp='$CPP $CPPFLAGS'
 ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
@@ -5851,8 +5917,9 @@
 if test x"$GXX" = x"yes"
 then :
   am_CXX_is_GNU=yes
-else $as_nop
-  am_CXX_is_GNU=no
+else case e in #(
+  e) am_CXX_is_GNU=no ;;
+esac
 fi
 
 # The lists of Fortran compilers here has been copied, pasted and edited
@@ -5879,8 +5946,8 @@
 if test ${ac_cv_prog_FC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$FC"; then
+else case e in #(
+  e) if test -n "$FC"; then
   ac_cv_prog_FC="$FC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -5902,7 +5969,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 FC=$ac_cv_prog_FC
 if test -n "$FC"; then
@@ -5928,8 +5996,8 @@
 if test ${ac_cv_prog_ac_ct_FC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_FC"; then
+else case e in #(
+  e) if test -n "$ac_ct_FC"; then
   ac_cv_prog_ac_ct_FC="$ac_ct_FC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -5951,7 +6019,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_FC=$ac_cv_prog_ac_ct_FC
 if test -n "$ac_ct_FC"; then
@@ -6045,8 +6114,8 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
-# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
+  # Autoconf-2.13 could set the ac_cv_exeext variable to 'no'.
+# So ignore a value of 'no', otherwise this would lead to 'EXEEXT = no'
 # in a Makefile.  We should not override ac_cv_exeext if it was cached,
 # so that the user can short-circuit this test for compilers unknown to
 # Autoconf.
@@ -6066,7 +6135,7 @@
 	   ac_cv_exeext=`expr "$ac_file" : '^.*$\..*$'`
 	fi
 	# We set ac_cv_exeext here because the later test for it is not
-	# safe: cross compilers may not add the suffix if given an `-o'
+	# safe: cross compilers may not add the suffix if given an '-o'
 	# argument, so we may need to know it at that point already.
 	# Even if this section looks crufty: it has the advantage of
 	# actually working.
@@ -6077,8 +6146,9 @@
 done
 test "$ac_cv_exeext" = no && ac_cv_exeext=
 
-else $as_nop
-  ac_file=''
+else case e in #(
+  e) ac_file='' ;;
+esac
 fi
 if test -z "$ac_file"
 then :
@@ -6093,9 +6163,10 @@
   am__failed=yes
   break
 }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-printf "%s\n" "yes" >&6; }
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
+printf "%s\n" "yes" >&6; } ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for Fortran compiler default output file name" >&5
 printf %s "checking for Fortran compiler default output file name... " >&6; }
@@ -6119,10 +6190,10 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # If both `conftest.exe' and `conftest' are `present' (well, observable)
-# catch `conftest.exe'.  For instance with Cygwin, `ls conftest' will
-# work properly (i.e., refer to `conftest.exe'), while it won't with
-# `rm'.
+  # If both 'conftest.exe' and 'conftest' are 'present' (well, observable)
+# catch 'conftest.exe'.  For instance with Cygwin, 'ls conftest' will
+# work properly (i.e., refer to 'conftest.exe'), while it won't with
+# 'rm'.
 for ac_file in conftest.exe conftest conftest.*; do
   test -f "$ac_file" || continue
   case $ac_file in
@@ -6132,13 +6203,14 @@
     * ) break;;
   esac
 done
-else $as_nop
-   {
+else case e in #(
+  e)  {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot compute suffix of executables: cannot compile and link" >&5
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of executables: cannot compile and link" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
 rm -f conftest conftest$ac_cv_exeext
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
@@ -6189,9 +6261,9 @@
     else
 	 {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot run Fortran compiled programs.
-If you meant to cross compile, use \`--host'." >&5
+If you meant to cross compile, use '--host'." >&5
 printf "%s\n" "$as_me: WARNING: cannot run Fortran compiled programs.
-If you meant to cross compile, use \`--host'." >&2;}
+If you meant to cross compile, use '--host'." >&2;}
   am__failed=yes
   break
 }
@@ -6201,15 +6273,16 @@
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
 printf "%s\n" "$cross_compiling" >&6; }
 
-rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
+rm -f conftest.$ac_ext conftest$ac_cv_exeext \
+  conftest.o conftest.obj conftest.out
 ac_clean_files=$ac_clean_files_save
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
 printf %s "checking for suffix of object files... " >&6; }
 if test ${ac_cv_objext+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat > conftest.$ac_ext <<_ACEOF
+else case e in #(
+  e) cat > conftest.$ac_ext <<_ACEOF
       program main
 
       end
@@ -6235,8 +6308,8 @@
        break;;
   esac
 done
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
  {
@@ -6244,15 +6317,17 @@
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of object files: cannot compile" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
-rm -f conftest.$ac_cv_objext conftest.$ac_ext
+rm -f conftest.$ac_cv_objext conftest.$ac_ext ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
 printf "%s\n" "$ac_cv_objext" >&6; }
 OBJEXT=$ac_cv_objext
 ac_objext=$OBJEXT
-# If we don't use `.F' as extension, the preprocessor is not run on the
+# If we don't use '.F' as extension, the preprocessor is not run on the
 # input file.  (Note that this only needs to work for GNU compilers.)
 ac_save_ext=$ac_ext
 ac_ext=F
@@ -6261,8 +6336,8 @@
 if test ${ac_cv_fc_compiler_gnu+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat > conftest.$ac_ext <<_ACEOF
+else case e in #(
+  e) cat > conftest.$ac_ext <<_ACEOF
       program main
 #ifndef __GNUC__
        choke me
@@ -6273,12 +6348,14 @@
 if ac_fn_fc_try_compile "$LINENO"
 then :
   ac_compiler_gnu=yes
-else $as_nop
-  ac_compiler_gnu=no
+else case e in #(
+  e) ac_compiler_gnu=no ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
 ac_cv_fc_compiler_gnu=$ac_compiler_gnu
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_fc_compiler_gnu" >&5
 printf "%s\n" "$ac_cv_fc_compiler_gnu" >&6; }
@@ -6293,8 +6370,8 @@
 if test ${ac_cv_prog_fc_g+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  FCFLAGS=-g
+else case e in #(
+  e) FCFLAGS=-g
 cat > conftest.$ac_ext <<_ACEOF
       program main
 
@@ -6303,11 +6380,13 @@
 if ac_fn_fc_try_compile "$LINENO"
 then :
   ac_cv_prog_fc_g=yes
-else $as_nop
-  ac_cv_prog_fc_g=no
+else case e in #(
+  e) ac_cv_prog_fc_g=no ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_fc_g" >&5
 printf "%s\n" "$ac_cv_prog_fc_g" >&6; }
@@ -6361,8 +6440,9 @@
 if test x"$GFC" = x"yes"
 then :
   am_FC_is_GNU=yes
-else $as_nop
-  am_FC_is_GNU=no
+else case e in #(
+  e) am_FC_is_GNU=no ;;
+esac
 fi
 
 
@@ -6384,8 +6464,8 @@
 if test ${ac_cv_prog_F77+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$F77"; then
+else case e in #(
+  e) if test -n "$F77"; then
   ac_cv_prog_F77="$F77" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -6407,7 +6487,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 F77=$ac_cv_prog_F77
 if test -n "$F77"; then
@@ -6433,8 +6514,8 @@
 if test ${ac_cv_prog_ac_ct_F77+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_F77"; then
+else case e in #(
+  e) if test -n "$ac_ct_F77"; then
   ac_cv_prog_ac_ct_F77="$ac_ct_F77" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -6456,7 +6537,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_F77=$ac_cv_prog_ac_ct_F77
 if test -n "$ac_ct_F77"; then
@@ -6550,8 +6632,8 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
-# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
+  # Autoconf-2.13 could set the ac_cv_exeext variable to 'no'.
+# So ignore a value of 'no', otherwise this would lead to 'EXEEXT = no'
 # in a Makefile.  We should not override ac_cv_exeext if it was cached,
 # so that the user can short-circuit this test for compilers unknown to
 # Autoconf.
@@ -6571,7 +6653,7 @@
 	   ac_cv_exeext=`expr "$ac_file" : '^.*$\..*$'`
 	fi
 	# We set ac_cv_exeext here because the later test for it is not
-	# safe: cross compilers may not add the suffix if given an `-o'
+	# safe: cross compilers may not add the suffix if given an '-o'
 	# argument, so we may need to know it at that point already.
 	# Even if this section looks crufty: it has the advantage of
 	# actually working.
@@ -6582,8 +6664,9 @@
 done
 test "$ac_cv_exeext" = no && ac_cv_exeext=
 
-else $as_nop
-  ac_file=''
+else case e in #(
+  e) ac_file='' ;;
+esac
 fi
 if test -z "$ac_file"
 then :
@@ -6598,9 +6681,10 @@
   am__failed=yes
   break
 }
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-printf "%s\n" "yes" >&6; }
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
+printf "%s\n" "yes" >&6; } ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for Fortran 77 compiler default output file name" >&5
 printf %s "checking for Fortran 77 compiler default output file name... " >&6; }
@@ -6624,10 +6708,10 @@
   printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
   test $ac_status = 0; }
 then :
-  # If both `conftest.exe' and `conftest' are `present' (well, observable)
-# catch `conftest.exe'.  For instance with Cygwin, `ls conftest' will
-# work properly (i.e., refer to `conftest.exe'), while it won't with
-# `rm'.
+  # If both 'conftest.exe' and 'conftest' are 'present' (well, observable)
+# catch 'conftest.exe'.  For instance with Cygwin, 'ls conftest' will
+# work properly (i.e., refer to 'conftest.exe'), while it won't with
+# 'rm'.
 for ac_file in conftest.exe conftest conftest.*; do
   test -f "$ac_file" || continue
   case $ac_file in
@@ -6637,13 +6721,14 @@
     * ) break;;
   esac
 done
-else $as_nop
-   {
+else case e in #(
+  e)  {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot compute suffix of executables: cannot compile and link" >&5
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of executables: cannot compile and link" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
 rm -f conftest conftest$ac_cv_exeext
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
@@ -6694,9 +6779,9 @@
     else
 	 {
   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: cannot run Fortran 77 compiled programs.
-If you meant to cross compile, use \`--host'." >&5
+If you meant to cross compile, use '--host'." >&5
 printf "%s\n" "$as_me: WARNING: cannot run Fortran 77 compiled programs.
-If you meant to cross compile, use \`--host'." >&2;}
+If you meant to cross compile, use '--host'." >&2;}
   am__failed=yes
   break
 }
@@ -6706,15 +6791,16 @@
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
 printf "%s\n" "$cross_compiling" >&6; }
 
-rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
+rm -f conftest.$ac_ext conftest$ac_cv_exeext \
+  conftest.o conftest.obj conftest.out
 ac_clean_files=$ac_clean_files_save
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
 printf %s "checking for suffix of object files... " >&6; }
 if test ${ac_cv_objext+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat > conftest.$ac_ext <<_ACEOF
+else case e in #(
+  e) cat > conftest.$ac_ext <<_ACEOF
       program main
 
       end
@@ -6740,8 +6826,8 @@
        break;;
   esac
 done
-else $as_nop
-  printf "%s\n" "$as_me: failed program was:" >&5
+else case e in #(
+  e) printf "%s\n" "$as_me: failed program was:" >&5
 sed 's/^/| /' conftest.$ac_ext >&5
 
  {
@@ -6749,15 +6835,17 @@
 printf "%s\n" "$as_me: WARNING: cannot compute suffix of object files: cannot compile" >&2;}
   am__failed=yes
   break
-}
+}  ;;
+esac
 fi
-rm -f conftest.$ac_cv_objext conftest.$ac_ext
+rm -f conftest.$ac_cv_objext conftest.$ac_ext ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
 printf "%s\n" "$ac_cv_objext" >&6; }
 OBJEXT=$ac_cv_objext
 ac_objext=$OBJEXT
-# If we don't use `.F' as extension, the preprocessor is not run on the
+# If we don't use '.F' as extension, the preprocessor is not run on the
 # input file.  (Note that this only needs to work for GNU compilers.)
 ac_save_ext=$ac_ext
 ac_ext=F
@@ -6766,8 +6854,8 @@
 if test ${ac_cv_f77_compiler_gnu+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  cat > conftest.$ac_ext <<_ACEOF
+else case e in #(
+  e) cat > conftest.$ac_ext <<_ACEOF
       program main
 #ifndef __GNUC__
        choke me
@@ -6778,12 +6866,14 @@
 if ac_fn_f77_try_compile "$LINENO"
 then :
   ac_compiler_gnu=yes
-else $as_nop
-  ac_compiler_gnu=no
+else case e in #(
+  e) ac_compiler_gnu=no ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
 ac_cv_f77_compiler_gnu=$ac_compiler_gnu
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_f77_compiler_gnu" >&5
 printf "%s\n" "$ac_cv_f77_compiler_gnu" >&6; }
@@ -6798,8 +6888,8 @@
 if test ${ac_cv_prog_f77_g+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  FFLAGS=-g
+else case e in #(
+  e) FFLAGS=-g
 cat > conftest.$ac_ext <<_ACEOF
       program main
 
@@ -6808,11 +6898,13 @@
 if ac_fn_f77_try_compile "$LINENO"
 then :
   ac_cv_prog_f77_g=yes
-else $as_nop
-  ac_cv_prog_f77_g=no
+else case e in #(
+  e) ac_cv_prog_f77_g=no ;;
+esac
 fi
 rm -f core conftest.err conftest.$ac_objext conftest.beam conftest.$ac_ext
-
+ ;;
+esac
 fi
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_f77_g" >&5
 printf "%s\n" "$ac_cv_prog_f77_g" >&6; }
@@ -6866,8 +6958,9 @@
 if test x"$G77" = x"yes"
 then :
   am_F77_is_GNU=yes
-else $as_nop
-  am_F77_is_GNU=no
+else case e in #(
+  e) am_F77_is_GNU=no ;;
+esac
 fi
 
 # Some tests will need the GNU compilers.  Searching for them here would
@@ -6901,8 +6994,8 @@
 if test ${ac_cv_prog_GNU_CC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$GNU_CC"; then
+else case e in #(
+  e) if test -n "$GNU_CC"; then
   ac_cv_prog_GNU_CC="$GNU_CC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -6924,7 +7017,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 GNU_CC=$ac_cv_prog_GNU_CC
 if test -n "$GNU_CC"; then
@@ -6950,8 +7044,8 @@
 if test ${ac_cv_prog_ac_ct_GNU_CC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_GNU_CC"; then
+else case e in #(
+  e) if test -n "$ac_ct_GNU_CC"; then
   ac_cv_prog_ac_ct_GNU_CC="$ac_ct_GNU_CC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -6973,7 +7067,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_GNU_CC=$ac_cv_prog_ac_ct_GNU_CC
 if test -n "$ac_ct_GNU_CC"; then
@@ -7010,11 +7105,12 @@
    (exit $ac_status); }
 then :
 
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU C compiler" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU C compiler" >&5
 printf "%s\n" "$as_me: WARNING: botched installation for GNU C compiler" >&2;}
          { printf "%s\n" "$as_me:${as_lineno-$LINENO}: tests requiring the GNU C compiler will be skipped" >&5
-printf "%s\n" "$as_me: tests requiring the GNU C compiler will be skipped" >&6;}
+printf "%s\n" "$as_me: tests requiring the GNU C compiler will be skipped" >&6;} ;;
+esac
 fi
 fi
 
@@ -7037,8 +7133,8 @@
 if test ${ac_cv_prog_GNU_CXX+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$GNU_CXX"; then
+else case e in #(
+  e) if test -n "$GNU_CXX"; then
   ac_cv_prog_GNU_CXX="$GNU_CXX" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7060,7 +7156,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 GNU_CXX=$ac_cv_prog_GNU_CXX
 if test -n "$GNU_CXX"; then
@@ -7086,8 +7183,8 @@
 if test ${ac_cv_prog_ac_ct_GNU_CXX+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_GNU_CXX"; then
+else case e in #(
+  e) if test -n "$ac_ct_GNU_CXX"; then
   ac_cv_prog_ac_ct_GNU_CXX="$ac_ct_GNU_CXX" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7109,7 +7206,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_GNU_CXX=$ac_cv_prog_ac_ct_GNU_CXX
 if test -n "$ac_ct_GNU_CXX"; then
@@ -7146,11 +7244,12 @@
    (exit $ac_status); }
 then :
 
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU C++ compiler" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU C++ compiler" >&5
 printf "%s\n" "$as_me: WARNING: botched installation for GNU C++ compiler" >&2;}
          { printf "%s\n" "$as_me:${as_lineno-$LINENO}: tests requiring the GNU C++ compiler will be skipped" >&5
-printf "%s\n" "$as_me: tests requiring the GNU C++ compiler will be skipped" >&6;}
+printf "%s\n" "$as_me: tests requiring the GNU C++ compiler will be skipped" >&6;} ;;
+esac
 fi
 fi
 
@@ -7173,8 +7272,8 @@
 if test ${ac_cv_prog_GNU_FC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$GNU_FC"; then
+else case e in #(
+  e) if test -n "$GNU_FC"; then
   ac_cv_prog_GNU_FC="$GNU_FC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7196,7 +7295,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 GNU_FC=$ac_cv_prog_GNU_FC
 if test -n "$GNU_FC"; then
@@ -7222,8 +7322,8 @@
 if test ${ac_cv_prog_ac_ct_GNU_FC+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_GNU_FC"; then
+else case e in #(
+  e) if test -n "$ac_ct_GNU_FC"; then
   ac_cv_prog_ac_ct_GNU_FC="$ac_ct_GNU_FC" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7245,7 +7345,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_GNU_FC=$ac_cv_prog_ac_ct_GNU_FC
 if test -n "$ac_ct_GNU_FC"; then
@@ -7282,11 +7383,12 @@
    (exit $ac_status); }
 then :
 
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU Fortran compiler" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU Fortran compiler" >&5
 printf "%s\n" "$as_me: WARNING: botched installation for GNU Fortran compiler" >&2;}
          { printf "%s\n" "$as_me:${as_lineno-$LINENO}: tests requiring the GNU Fortran compiler will be skipped" >&5
-printf "%s\n" "$as_me: tests requiring the GNU Fortran compiler will be skipped" >&6;}
+printf "%s\n" "$as_me: tests requiring the GNU Fortran compiler will be skipped" >&6;} ;;
+esac
 fi
 fi
 
@@ -7309,8 +7411,8 @@
 if test ${ac_cv_prog_GNU_F77+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$GNU_F77"; then
+else case e in #(
+  e) if test -n "$GNU_F77"; then
   ac_cv_prog_GNU_F77="$GNU_F77" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7332,7 +7434,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 GNU_F77=$ac_cv_prog_GNU_F77
 if test -n "$GNU_F77"; then
@@ -7358,8 +7461,8 @@
 if test ${ac_cv_prog_ac_ct_GNU_F77+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_GNU_F77"; then
+else case e in #(
+  e) if test -n "$ac_ct_GNU_F77"; then
   ac_cv_prog_ac_ct_GNU_F77="$ac_ct_GNU_F77" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7381,7 +7484,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_GNU_F77=$ac_cv_prog_ac_ct_GNU_F77
 if test -n "$ac_ct_GNU_F77"; then
@@ -7418,11 +7522,12 @@
    (exit $ac_status); }
 then :
 
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU Fortran 77 compiler" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU Fortran 77 compiler" >&5
 printf "%s\n" "$as_me: WARNING: botched installation for GNU Fortran 77 compiler" >&2;}
         { printf "%s\n" "$as_me:${as_lineno-$LINENO}: tests requiring the GNU Fortran 77 compiler will be skipped" >&5
-printf "%s\n" "$as_me: tests requiring the GNU Fortran 77 compiler will be skipped" >&6;}
+printf "%s\n" "$as_me: tests requiring the GNU Fortran 77 compiler will be skipped" >&6;} ;;
+esac
 fi
 fi
 
@@ -7439,8 +7544,8 @@
 if test ${ac_cv_prog_GNU_GCJ+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$GNU_GCJ"; then
+else case e in #(
+  e) if test -n "$GNU_GCJ"; then
   ac_cv_prog_GNU_GCJ="$GNU_GCJ" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7462,7 +7567,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 GNU_GCJ=$ac_cv_prog_GNU_GCJ
 if test -n "$GNU_GCJ"; then
@@ -7488,8 +7594,8 @@
 if test ${ac_cv_prog_ac_ct_GNU_GCJ+y}
 then :
   printf %s "(cached) " >&6
-else $as_nop
-  if test -n "$ac_ct_GNU_GCJ"; then
+else case e in #(
+  e) if test -n "$ac_ct_GNU_GCJ"; then
   ac_cv_prog_ac_ct_GNU_GCJ="$ac_ct_GNU_GCJ" # Let the user override the test.
 else
 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
@@ -7511,7 +7617,8 @@
   done
 IFS=$as_save_IFS
 
-fi
+fi ;;
+esac
 fi
 ac_ct_GNU_GCJ=$ac_cv_prog_ac_ct_GNU_GCJ
 if test -n "$ac_ct_GNU_GCJ"; then
@@ -7547,11 +7654,12 @@
    (exit $ac_status); }
 then :
 
-else $as_nop
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU Java compiler" >&5
+else case e in #(
+  e) { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: botched installation for GNU Java compiler" >&5
 printf "%s\n" "$as_me: WARNING: botched installation for GNU Java compiler" >&2;}
         { printf "%s\n" "$as_me:${as_lineno-$LINENO}: tests requiring the GNU Java compiler will be skipped" >&5
-printf "%s\n" "$as_me: tests requiring the GNU Java compiler will be skipped" >&6;}
+printf "%s\n" "$as_me: tests requiring the GNU Java compiler will be skipped" >&6;} ;;
+esac
 fi
 fi
 
@@ -7584,8 +7692,8 @@
 # config.status only pays attention to the cache file if you give it
 # the --recheck option to rerun configure.
 #
-# `ac_cv_env_foo' variables (set or unset) will be overridden when
-# loading this file, other *unset* `ac_cv_foo' will be assigned the
+# 'ac_cv_env_foo' variables (set or unset) will be overridden when
+# loading this file, other *unset* 'ac_cv_foo' will be assigned the
 # following values.
 
 _ACEOF
@@ -7615,14 +7723,14 @@
   (set) 2>&1 |
     case $as_nl`(ac_space=' '; set) 2>&1` in #(
     *${as_nl}ac_space=\ *)
-      # `set' does not quote correctly, so add quotes: double-quote
+      # 'set' does not quote correctly, so add quotes: double-quote
       # substitution turns \\\\ into \\, and sed turns \\ into \.
       sed -n \
 	"s/'/'\\\\''/g;
 	  s/^\$_$as_cr_alnum*_cv__$as_cr_alnum*\$=\$.*\$/\\1='\\2'/p"
       ;; #(
     *)
-      # `set' quotes correctly as required by POSIX, so do not add quotes.
+      # 'set' quotes correctly as required by POSIX, so do not add quotes.
       sed -n "/^_$as_cr_alnum*_cv__$as_cr_alnum*=/p"
       ;;
     esac |
@@ -7686,9 +7794,7 @@
 t quote
 b any
 :quote
-s/	 `~#$^&*(){}\\|;'\''"<>?/\\&/g
-s/\/\\&/g
-s/\/\\&/g
+s/	 `~#$^&*(){}\\|;'\''"<>?/\\&/g
 s/\$/$$/g
 H
 :any
@@ -7719,6 +7825,18 @@
 LTLIBOBJS=$ac_ltlibobjs
 
 
+case $enable_silent_rules in # (((
+  yes) AM_DEFAULT_VERBOSITY=0;;
+   no) AM_DEFAULT_VERBOSITY=1;;
+esac
+if test $am_cv_make_support_nested_variables = yes; then
+    AM_V='$(V)'
+  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
+else
+  AM_V=$AM_DEFAULT_VERBOSITY
+  AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY
+fi
+
 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking that generated files are newer than configure" >&5
 printf %s "checking that generated files are newer than configure... " >&6; }
    if test -n "$am_sleep_pid"; then
@@ -7764,7 +7882,6 @@
 
 # Be more Bourne compatible
 DUALCASE=1; export DUALCASE # for MKS sh
-as_nop=:
 if test ${ZSH_VERSION+y} && (emulate sh) >/dev/null 2>&1
 then :
   emulate sh
@@ -7773,12 +7890,13 @@
   # is contrary to our usage.  Disable this feature.
   alias -g '${1+"$@"}'='"$@"'
   setopt NO_GLOB_SUBST
-else $as_nop
-  case `(set -o) 2>/dev/null` in #(
+else case e in #(
+  e) case `(set -o) 2>/dev/null` in #(
   *posix*) :
     set -o posix ;; #(
   *) :
      ;;
+esac ;;
 esac
 fi
 
@@ -7850,7 +7968,7 @@
 
      ;;
 esac
-# We did not find ourselves, most probably we were run as `sh COMMAND'
+# We did not find ourselves, most probably we were run as 'sh COMMAND'
 # in which case we are not to be found in the path.
 if test "x$as_myself" = x; then
   as_myself=$0
@@ -7879,7 +7997,6 @@
 } # as_fn_error
 
 
-
 # as_fn_set_status STATUS
 # -----------------------
 # Set $? to STATUS, without forking.
@@ -7919,11 +8036,12 @@
   {
     eval $1+=\$2
   }'
-else $as_nop
-  as_fn_append ()
+else case e in #(
+  e) as_fn_append ()
   {
     eval $1=\$$1\$2
-  }
+  } ;;
+esac
 fi # as_fn_append
 
 # as_fn_arith ARG...
@@ -7937,11 +8055,12 @@
   {
     as_val=$(( $* ))
   }'
-else $as_nop
-  as_fn_arith ()
+else case e in #(
+  e) as_fn_arith ()
   {
     as_val=`expr "$@" || test $? -eq 1`
-  }
+  } ;;
+esac
 fi # as_fn_arith
 
 
@@ -8024,9 +8143,9 @@
   if ln -s conf$$.file conf$$ 2>/dev/null; then
     as_ln_s='ln -s'
     # ... but there are two gotchas:
-    # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
-    # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
-    # In both cases, we have to default to `cp -pR'.
+    # 1) On MSYS, both 'ln -s file dir' and 'ln file dir' fail.
+    # 2) DJGPP < 2.04 has no symlinks; 'ln -s' creates a wrapper executable.
+    # In both cases, we have to default to 'cp -pR'.
     ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
       as_ln_s='cp -pR'
   elif ln conf$$.file conf$$ 2>/dev/null; then
@@ -8107,10 +8226,12 @@
 as_executable_p=as_fn_executable_p
 
 # Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%^_$as_cr_alnum%_%g'"
+as_sed_cpp="y%*$as_cr_letters%P$as_cr_LETTERS%;s%^_$as_cr_alnum%_%g"
+as_tr_cpp="eval sed '$as_sed_cpp'" # deprecated
 
 # Sed expression to map a string onto a valid variable name.
-as_tr_sh="eval sed 'y%*+%pp%;s%^_$as_cr_alnum%_%g'"
+as_sed_sh="y%*+%pp%;s%^_$as_cr_alnum%_%g"
+as_tr_sh="eval sed '$as_sed_sh'" # deprecated
 
 
 exec 6>&1
@@ -8125,8 +8246,8 @@
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by GNU Automake $as_me 1.16.5, which was
-generated by GNU Autoconf 2.71.  Invocation command line was
+This file was extended by GNU Automake $as_me 1.17, which was
+generated by GNU Autoconf 2.72.24-c5b83.  Invocation command line was
 
   CONFIG_FILES    = $CONFIG_FILES
   CONFIG_HEADERS  = $CONFIG_HEADERS
@@ -8154,7 +8275,7 @@
 
 cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
 ac_cs_usage="\
-\`$as_me' instantiates files and other configuration actions
+'$as_me' instantiates files and other configuration actions
 from templates according to the current configuration.  Unless the files
 and actions are specified as TAGs, all are instantiated by default.
 
@@ -8186,11 +8307,11 @@
 cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
 ac_cs_config='$ac_cs_config_escaped'
 ac_cs_version="\\
-GNU Automake config.status 1.16.5
-configured by $0, generated by GNU Autoconf 2.71,
+GNU Automake config.status 1.17
+configured by $0, generated by GNU Autoconf 2.72.24-c5b83,
   with options \\"\$ac_cs_config\\"
 
-Copyright (C) 2021 Free Software Foundation, Inc.
+Copyright (C) 2024 Free Software Foundation, Inc.
 This config.status script is free software; the Free Software Foundation
 gives unlimited permission to copy, distribute and modify it."
 
@@ -8250,8 +8371,8 @@
     ac_cs_silent=: ;;
 
   # This is an error.
-  -*) as_fn_error $? "unrecognized option: \`$1'
-Try \`$0 --help' for more information." ;;
+  -*) as_fn_error $? "unrecognized option: '$1'
+Try '$0 --help' for more information." ;;
 
   *) as_fn_append ac_config_targets " $1"
      ac_need_defaults=false ;;
@@ -8303,7 +8424,7 @@
     "GNUmakefile") CONFIG_LINKS="$CONFIG_LINKS GNUmakefile:GNUmakefile" ;;
     "pre-inst-env") CONFIG_FILES="$CONFIG_FILES pre-inst-env" ;;
 
-  *) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;;
+  *) as_fn_error $? "invalid argument: '$ac_config_target'" "$LINENO" 5;;
   esac
 done
 
@@ -8322,7 +8443,7 @@
 # creating and moving files from /tmp can sometimes cause problems.
 # Hook for its removal unless debugging.
 # Note that there is a small window in which the directory will not be cleaned:
-# after its creation but before its name has been assigned to `$tmp'.
+# after its creation but before its name has been assigned to '$tmp'.
 $debug ||
 {
   tmp= ac_tmp=
@@ -8346,7 +8467,7 @@
 
 # Set up the scripts for CONFIG_FILES section.
 # No need to generate them if there are no CONFIG_FILES.
-# This happens for instance with `./config.status config.h'.
+# This happens for instance with './config.status config.h'.
 if test -n "$CONFIG_FILES"; then
 
 
@@ -8512,7 +8633,7 @@
   esac
   case $ac_mode$ac_tag in
   :FHL*:*);;
-  :L* | :C*:*) as_fn_error $? "invalid tag \`$ac_tag'" "$LINENO" 5;;
+  :L* | :C*:*) as_fn_error $? "invalid tag '$ac_tag'" "$LINENO" 5;;
   :FH-) ac_tag=-:-;;
   :FH*) ac_tag=$ac_tag:$ac_tag.in;;
   esac
@@ -8534,19 +8655,19 @@
       -) ac_f="$ac_tmp/stdin";;
       *) # Look for the file first in the build tree, then in the source tree
 	 # (if the path is not absolute).  The absolute path cannot be DOS-style,
-	 # because $ac_f cannot contain `:'.
+	 # because $ac_f cannot contain ':'.
 	 test -f "$ac_f" ||
 	   case $ac_f in
 	   \\/$*) false;;
 	   *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
 	   esac ||
-	   as_fn_error 1 "cannot find input file: \`$ac_f'" "$LINENO" 5;;
+	   as_fn_error 1 "cannot find input file: '$ac_f'" "$LINENO" 5;;
       esac
       case $ac_f in *\'*) ac_f=`printf "%s\n" "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
       as_fn_append ac_file_inputs " '$ac_f'"
     done
 
-    # Let's still pretend it is `configure' which instantiates (i.e., don't
+    # Let's still pretend it is 'configure' which instantiates (i.e., don't
     # use $as_me), people would be surprised to read:
     #    /* config.h.  Generated by config.status.  */
     configure_input='Generated from '`
@@ -8679,7 +8800,7 @@
 esac
 _ACEOF
 
-# Neutralize VPATH when `$srcdir' = `.'.
+# Neutralize VPATH when '$srcdir' = '.'.
 # Shell code in configure.ac might set extrasub.
 # FIXME: do we really want to maintain this feature?
 cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
@@ -8710,9 +8831,9 @@
   { ac_out=`sed -n '/\${datarootdir}/p' "$ac_tmp/out"`; test -n "$ac_out"; } &&
   { ac_out=`sed -n '/^	 *datarootdir	 *:*=/p' \
       "$ac_tmp/out"`; test -z "$ac_out"; } &&
-  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir'
+  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable 'datarootdir'
 which seems to be undefined.  Please make sure it is defined" >&5
-printf "%s\n" "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
+printf "%s\n" "$as_me: WARNING: $ac_file contains a reference to the variable 'datarootdir'
 which seems to be undefined.  Please make sure it is defined" >&2;}
 
   rm -f "$ac_tmp/stdin"
@@ -8801,13 +8922,17 @@
 
 
 # Inform the user if this version of automake is a beta release or
-# a development snapshot.
-# According to HACKING, the version of a development snapshot should
-# end with an "odd" letter (a, c, ...), the version of a test release
-# should end wit an "even" letter (b, d, ...).
-
+# a development snapshot. Except, as of 1.17 (January 2024), don't bother.
+# Just call all pretests development snapshots.
+#
 am_stable_version_rx='1-9\.0-9+(\.0-9+)?'
-am_beta_version_rx="$am_stable_version_rxbdfhjlnprtvxz"
+
+# This won't match anything as of 1.17, since we switched to
+# .90-numbered test releases. But if we wanted to, according to HACKING,
+# the version of a development snapshot should end with an odd number
+# (91, 93, ...) and a beta release should end with an even number (90,
+# 92, ...).
+am_beta_version_rx="$am_stable_version_rxbdfhjlnprtvxz" # no match
 
 am_release_type=`printf "%s\n" "$PACKAGE_VERSION" | LC_ALL=C awk "
   /^$am_stable_version_rx$/ { print \"stable\"; exit(0); }
@@ -8818,10 +8943,11 @@
 test "$am_release_type" = stable || test "$silent" = yes || cat <<EOF
 
 WARNING: You are about to use a $am_release_type of automake.
-WARNING: It might easily suffer from new bugs or regressions.
+WARNING: It could well suffer from new bugs or regressions.
 WARNING: You are strongly advised not to use it in production code.
 
-Please report bugs, problems and feedback to <bug-automake@gnu.org>.
+Please report bugs, problems and feedback to <bug-automake@gnu.org>,
+since that is the whole point of a test release.
 EOF
 
 as_fn_exit 0

_service:tar_scm:automake-1.16.5.tar.xz/configure.ac -> _service:tar_scm:automake-1.17.tar.xz/configure.ac Changed

@@ -1,6 +1,6 @@
 # Process this file with autoconf to produce a configure script.
 
-# Copyright (C) 1995-2021 Free Software Foundation, Inc.
+# Copyright (C) 1995-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -16,7 +16,7 @@
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 AC_PREREQ(2.69)
-AC_INIT(GNU Automake, 1.16.5, bug-automake@gnu.org)
+AC_INIT(GNU Automake, 1.17, bug-automake@gnu.org)
 
 AC_CONFIG_SRCDIR(bin/automake.in)
 AC_CONFIG_AUX_DIR(lib)
@@ -44,12 +44,12 @@
 
 # Keep this on a line of its own, since it must be found and processed
 # by the 'update-copyright' rule in our Makefile.
-RELEASE_YEAR=2021
+RELEASE_YEAR=2024
 AC_SUBST(RELEASE_YEAR)
 
 # The API version is the base version.  We must guarantee
 # compatibility for all releases with the same API version.
-APIVERSION=1.16
+APIVERSION=1.17
 AC_SUBST(APIVERSION)
 
 AC_SUBST(pkgvdatadir, "\${datadir}/$PACKAGE-$APIVERSION")
@@ -68,14 +68,22 @@
 AC_PROG_LN_S
 
 AC_PATH_PROG(PERL, perl)
-if test -z "$PERL"; then
+case $PERL in
+ '')
    AC_MSG_ERROR(perl not found)
-fi
+   ;;
+ *' '* | *'	'*)
+  AC_MSG_ERROR(The path to your Perl contains spaces or tabs.
+This would cause build failures later or unusable programs.
+Please use a path without spaces and try again.)
+  ;;
+esac
+
 # Save details about the selected perl interpreter in config.log.
 AM_RUN_LOG($PERL --version)
 $PERL -e 'require 5.006;' || {
    AC_MSG_ERROR(
-perl 5.6 or better is required; perl 5.8.2 or better
+perl 5.6 or better is required; perl 5.10 or better
 is recommended.  If you have several perl versions
 installed, select the one Automake should use using
   ./configure PERL=/path/to/perl)
@@ -172,17 +180,6 @@
 test "x$am_cv_prog_ln" = xln && result=yes
 AC_MSG_RESULT($result)
 
-# The amount we should wait after modifying files depends on the platform.
-# On Windows '95, '98 and ME, files modifications have 2-seconds
-# granularity and can be up to 3 seconds in the future w.r.t. the
-# system clock.  When it is important to ensure one file is older
-# than another we wait at least 5 seconds between creations.
-case $build in
-  *-pc-msdosdjgpp) MODIFICATION_DELAY=5;;
-  *)               MODIFICATION_DELAY=2;;
-esac
-AC_SUBST(MODIFICATION_DELAY)
-
 ## ------------------------------------------- ##
 ##  Test for things needed by the test suite.  ##
 ## ------------------------------------------- ##
@@ -190,6 +187,16 @@
 AC_PROG_EGREP
 AC_PROG_FGREP
 
+# The test suite needs to know the resolution of timestamps
+# supported by the filesystem hosting the build.  The value
+# will be acceptable to 'sleep' on this system.
+MTIME_RESOLUTION=$am_cv_filesystem_timestamp_resolution
+if test -z "$MTIME_RESOLUTION"; then
+  AC_MSG_NOTICE(am_cv_filesystem_timestamp_resolution strangely not set; using 1)
+  MTIME_RESOLUTION=1
+fi
+AC_SUBST(MTIME_RESOLUTION)
+
 dnl FIXME: could we extract this in a simpler way through autoconf
 dnl FIXME: idioms or internals?
 AC_DEFUN(
@@ -388,7 +395,7 @@
 dnl available, as such a compiler is only required to run part of the
 dnl testsuite, not to build or install Automake.  Ditto for C++, Fortran
 dnl and Fortran 77 compilers.  Unfortunately, autoconf does not offer an
-dnl easy way to obtain this behaviour, so we'll need a few hacks.
+dnl easy way to obtain this behavior, so we'll need a few hacks.
 
 dnl We want the body of this macro to expand as a single shell statement,
 dnl thus we wrap it into { ... } brackets.
@@ -444,11 +451,13 @@
 # to a C++ compiler as expected (see automake bugs #11893 and #10766).
 # Similarly, we must avoid looking for 'RCC', as that can point to the
 # Qt4 "Resource Compiler": <http://doc.qt.digia.com/4.2/rcc.html>
+# And we avoid looking for 'KCC' as that can be a kerberos tool under
+# macOS systems.
 if test -f /bIn/rMdIr || test -f /uSr/bIn/rMdIr; then
   # Case-insensitive file system, don't look for CC.
-  am_CC= am_RCC=
+  am_CC= am_RCC= am_KCC=
 else
-  am_CC=CC am_RCC=RCC
+  am_CC=CC am_RCC=RCC am_KCC=KCC
 fi
 
 # The list of C++ compilers here has been copied, pasted and edited
@@ -456,7 +465,7 @@
 # Keep it in sync, or better again, find out a way to avoid this code
 # duplication.
 _AM_COMPILER_CAN_FAIL(AC_PROG_CXX(dnl
-  aCC $am_CC FCC KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++),
+  aCC $am_CC FCC $am_KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++ clang++),
   CXX=false; _AM_SKIP_COMP_TESTS(C++))
 
 AS_IF(test x"$GXX" = x"yes", am_CXX_is_GNU=yes, am_CXX_is_GNU=no)
@@ -583,13 +592,17 @@
 AC_OUTPUT
 
 # Inform the user if this version of automake is a beta release or
-# a development snapshot.
-# According to HACKING, the version of a development snapshot should
-# end with an "odd" letter (a, c, ...), the version of a test release
-# should end wit an "even" letter (b, d, ...).
-
+# a development snapshot. Except, as of 1.17 (January 2024), don't bother.
+# Just call all pretests development snapshots.
+#
 am_stable_version_rx='1-9\.0-9+(\.0-9+)?'
-am_beta_version_rx="$am_stable_version_rxbdfhjlnprtvxz"
+
+# This won't match anything as of 1.17, since we switched to
+# .90-numbered test releases. But if we wanted to, according to HACKING,
+# the version of a development snapshot should end with an odd number
+# (91, 93, ...) and a beta release should end with an even number (90,
+# 92, ...).
+am_beta_version_rx="$am_stable_version_rxbdfhjlnprtvxz" # no match
 
 am_release_type=`AS_ECHO("$PACKAGE_VERSION") | LC_ALL=C awk "
   /^$am_stable_version_rx$/ { print \"stable\"; exit(0); }
@@ -600,10 +613,11 @@
 test "$am_release_type" = stable || test "$silent" = yes || cat <<EOF
 
 WARNING: You are about to use a $am_release_type of automake.
-WARNING: It might easily suffer from new bugs or regressions.
+WARNING: It could well suffer from new bugs or regressions.
 WARNING: You are strongly advised not to use it in production code.
 
-Please report bugs, problems and feedback to <AC_PACKAGE_BUGREPORT>.
+Please report bugs, problems and feedback to <AC_PACKAGE_BUGREPORT>,
+since that is the whole point of a test release.
 EOF
 
 AS_EXIT(0)

_service:tar_scm:automake-1.16.5.tar.xz/contrib/check-html.am -> _service:tar_scm:automake-1.17.tar.xz/contrib/check-html.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/checklinkx -> _service:tar_scm:automake-1.17.tar.xz/contrib/checklinkx Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/multilib/config-ml.in -> _service:tar_scm:automake-1.17.tar.xz/contrib/multilib/config-ml.in Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/multilib/multi.m4 -> _service:tar_scm:automake-1.17.tar.xz/contrib/multilib/multi.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/multilib/multilib.am -> _service:tar_scm:automake-1.17.tar.xz/contrib/multilib/multilib.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/multilib/symlink-tree -> _service:tar_scm:automake-1.17.tar.xz/contrib/multilib/symlink-tree Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/t/help-multilib.sh -> _service:tar_scm:automake-1.17.tar.xz/contrib/t/help-multilib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/t/local.mk -> _service:tar_scm:automake-1.17.tar.xz/contrib/t/local.mk Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/t/multilib.sh -> _service:tar_scm:automake-1.17.tar.xz/contrib/t/multilib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/t/parallel-tests-html-recursive.sh -> _service:tar_scm:automake-1.17.tar.xz/contrib/t/parallel-tests-html-recursive.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/t/parallel-tests-html.sh -> _service:tar_scm:automake-1.17.tar.xz/contrib/t/parallel-tests-html.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/contrib/tap-driver.pl -> _service:tar_scm:automake-1.17.tar.xz/contrib/tap-driver.pl Changed

@@ -1,5 +1,5 @@
 #! /usr/bin/env perl
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -38,10 +38,10 @@
 
 my $USAGE = <<'END';
 Usage:
-  tap-driver --test-name=NAME --log-file=PATH --trs-file=PATH
-             --expect-failure={yes|no} --color-tests={yes|no}
-             --enable-hard-errors={yes|no} --ignore-exit
-             --diagnostic-string=STRING --merge|--no-merge
+  tap-driver --test-name NAME --log-file PATH --trs-file PATH
+             --expect-failure {yes|no} --color-tests {yes|no}
+             --enable-hard-errors {yes|no} --ignore-exit
+             --diagnostic-string STRING --merge|--no-merge
              --comments|--no-comments -- TEST-COMMAND
 The '--test-name', '--log-file' and '--trs-file' options are mandatory.
 END
@@ -198,14 +198,14 @@
   # Whether the test script should be re-run by "make recheck".
   sub must_recheck ()
   {
-    return grep { !/^(?:XFAIL|PASS|SKIP)$/ } (keys %test_results_seen);
+    return grep { !/^(?:XFAIL|PASS|SKIP)$/ } (sort keys %test_results_seen);
   }
 
   # Whether the content of the log file associated to this test should
   # be copied into the "global" test-suite.log.
   sub copy_in_global_log ()
   {
-    return grep { not $_ eq "PASS" } (keys %test_results_seen);
+    return grep { not $_ eq "PASS" } (sort keys %test_results_seen);
   }
 
   sub get_global_test_result ()

_service:tar_scm:automake-1.16.5.tar.xz/doc/amhello-1.0.tar.gz -> _service:tar_scm:automake-1.17.tar.xz/doc/amhello-1.0.tar.gz Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/amhello/Makefile.am -> _service:tar_scm:automake-1.17.tar.xz/doc/amhello/Makefile.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/amhello/README -> _service:tar_scm:automake-1.17.tar.xz/doc/amhello/README Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/amhello/configure.ac -> _service:tar_scm:automake-1.17.tar.xz/doc/amhello/configure.ac Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/amhello/src/Makefile.am -> _service:tar_scm:automake-1.17.tar.xz/doc/amhello/src/Makefile.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/amhello/src/main.c -> _service:tar_scm:automake-1.17.tar.xz/doc/amhello/src/main.c Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/automake-history.info -> _service:tar_scm:automake-1.17.tar.xz/doc/automake-history.info Changed

@@ -1,10 +1,10 @@
-This is automake-history.info, produced by makeinfo version 6.8 from
+This is automake-history.info, produced by makeinfo version 7.1 from
 automake-history.texi.
 
 This manual describes (part of) the history of GNU Automake, a program
 that creates GNU standards-compliant Makefiles from template files.
 
-   Copyright (C) 1995-2021 Free Software Foundation, Inc.
+   Copyright © 1995-2024 Free Software Foundation, Inc.
 
      Permission is granted to copy, distribute and/or modify this
      document under the terms of the GNU Free Documentation License,
@@ -27,7 +27,7 @@
 This manual describes (part of) the history of GNU Automake, a program
 that creates GNU standards-compliant Makefiles from template files.
 
-   Copyright (C) 1995-2021 Free Software Foundation, Inc.
+   Copyright © 1995-2024 Free Software Foundation, Inc.
 
      Permission is granted to copy, distribute and/or modify this
      document under the terms of the GNU Free Documentation License,
@@ -74,7 +74,7 @@
      started working on Automake (or AutoMake, as it was spelt then)
      this Monday.
 
-     The first version of the 'automake' script looks as follows.
+     The first version of the ‘automake’ script looks as follows.
 
           #!/bin/sh
 
@@ -93,7 +93,7 @@
           done
 
      From this you can already see that Automake will be about reading
-     '*.am' file and producing '*.in' files.  You cannot see anything
+     ‘*.am’ file and producing ‘*.in’ files.  You cannot see anything
      else, but if you also know that David is the one who created
      Autoconf two years before you can guess the rest.
 
@@ -101,11 +101,11 @@
      reported to work for GNU fileutils and GNU m4.
 
      The modus operandi is the one that is still used today: variable
-     assignments in 'Makefile.am' files trigger injections of precanned
-     'Makefile' fragments into the generated 'Makefile.in'.  The use of
-     'Makefile' fragments was inspired by the 4.4BSD 'make' and include
+     assignments in ‘Makefile.am’ files trigger injections of precanned
+     ‘Makefile’ fragments into the generated ‘Makefile.in’.  The use of
+     ‘Makefile’ fragments was inspired by the 4.4BSD ‘make’ and include
      files, however Automake aims to be portable and to conform to the
-     GNU standards for 'Makefile' variables and targets.
+     GNU standards for ‘Makefile’ variables and targets.
 
      At this point, the most recent release of Autoconf is version 1.11,
      and David is preparing to release Autoconf 2.0 in late October.  As
@@ -114,7 +114,7 @@
 1994-11-05 David MacKenzie's last commit.
 
      At this point Automake is a 200 line portable shell script, plus
-     332 lines of 'Makefile' fragments.  In the 'README', David states
+     332 lines of ‘Makefile’ fragments.  In the ‘README’, David states
      his ambivalence between "portable shell" and "more appropriate
      language":
 
@@ -142,7 +142,7 @@
      After one year of inactivity, Tom Tromey takes over the package.
      Tom was working on GNU cpio back then, and doing this just for fun,
      having trouble finding a project to contribute to.  So while
-     hacking he wanted to bring the 'Makefile.in' up to GNU standards.
+     hacking he wanted to bring the ‘Makefile.in’ up to GNU standards.
      This was hard, and one day he saw Automake on
      <ftp://alpha.gnu.org/>, grabbed it and tried it out.
 
@@ -166,9 +166,9 @@
      Besides introducing automatic dependency tracking (*note Dependency
      Tracking Evolution::), this version also supplies a 9-page manual.
 
-     At this time 'aclocal' and 'AM_INIT_AUTOMAKE' did not exist, so
+     At this time ‘aclocal’ and ‘AM_INIT_AUTOMAKE’ did not exist, so
      many things had to be done by hand.  For instance, here is what a
-     configure.in (this is the former name of the 'configure.ac' we use
+     configure.in (this is the former name of the ‘configure.ac’ we use
      today) must contain in order to use Automake 0.20:
 
           PACKAGE=cpio
@@ -180,41 +180,41 @@
           AC_ARG_PROGRAM
           AC_PROG_INSTALL
 
-     (Today all of the above is achieved by 'AC_INIT' and
-     'AM_INIT_AUTOMAKE'.)
+     (Today all of the above is achieved by ‘AC_INIT’ and
+     ‘AM_INIT_AUTOMAKE’.)
 
-     Here is how programs are specified in 'Makefile.am':
+     Here is how programs are specified in ‘Makefile.am’:
 
           PROGRAMS = hello
           hello_SOURCES = hello.c
 
-     This looks pretty much like what we do today, except the 'PROGRAMS'
-     variable has no directory prefix specifying where 'hello' should be
-     installed: all programs are installed in '$(bindir)'.
-     'LIBPROGRAMS' can be used to specify programs that must be built
-     but not installed (it is called 'noinst_PROGRAMS' nowadays).
+     This looks pretty much like what we do today, except the ‘PROGRAMS’
+     variable has no directory prefix specifying where ‘hello’ should be
+     installed: all programs are installed in ‘$(bindir)’.
+     ‘LIBPROGRAMS’ can be used to specify programs that must be built
+     but not installed (it is called ‘noinst_PROGRAMS’ nowadays).
 
-     Programs can be built conditionally using 'AC_SUBST'itutions:
+     Programs can be built conditionally using ‘AC_SUBST’itutions:
 
           PROGRAMS = @progs@
           AM_PROGRAMS = foo bar baz
 
-     ('AM_PROGRAMS' has since then been renamed to 'EXTRA_PROGRAMS'.)
+     (‘AM_PROGRAMS’ has since then been renamed to ‘EXTRA_PROGRAMS’.)
 
      Similarly scripts, static libraries, and data can be built and
-     installed using the 'LIBRARIES', 'SCRIPTS', and 'DATA' variables.
-     However 'LIBRARIES' were treated a bit specially in that Automake
-     did automatically supply the 'lib' and '.a' prefixes.  Therefore to
-     build 'libcpio.a', one had to write
+     installed using the ‘LIBRARIES’, ‘SCRIPTS’, and ‘DATA’ variables.
+     However ‘LIBRARIES’ were treated a bit specially in that Automake
+     did automatically supply the ‘lib’ and ‘.a’ prefixes.  Therefore to
+     build ‘libcpio.a’, one had to write
 
           LIBRARIES = cpio
           cpio_SOURCES = ...
 
-     Extra files to distribute must be listed in 'DIST_OTHER' (the
-     ancestor of 'EXTRA_DIST').  Also extra directories that are to be
-     distributed should appear in 'DIST_SUBDIRS', but the manual
+     Extra files to distribute must be listed in ‘DIST_OTHER’ (the
+     ancestor of ‘EXTRA_DIST’).  Also extra directories that are to be
+     distributed should appear in ‘DIST_SUBDIRS’, but the manual
      describes this as a temporary ugly hack (today extra directories
-     should also be listed in 'EXTRA_DIST', and 'DIST_SUBDIRS' is used
+     should also be listed in ‘EXTRA_DIST’, and ‘DIST_SUBDIRS’ is used
      for another purpose, *note Conditional Subdirectories:
      (automake)Conditional Subdirectories.).
 
@@ -227,10 +227,10 @@
      Automake.
 
      If you never used Perl 4, imagine Perl 5 without objects, without
-     'my' variables (only dynamically scoped 'local' variables), without
+     ‘my’ variables (only dynamically scoped ‘local’ variables), without
      function prototypes, with function calls that needs to be prefixed
-     with '&', etc.  Traces of this old style can still be found in
-     today's 'automake'.
+     with ‘&’, etc.  Traces of this old style can still be found in
+     today's ‘automake’.
 
 1995-11-28 Automake 0.22
 1995-11-29 Automake 0.23
@@ -241,12 +241,12 @@
 1995-12-10 Automake 0.25
 
      Releases are raining.  0.24 introduces the uniform naming scheme we
-     use today, i.e., 'bin_PROGRAMS' instead of 'PROGRAMS',
-     'noinst_LIBRARIES' instead of 'LIBLIBRARIES', etc.  (However
-     'EXTRA_PROGRAMS' does not exist yet, 'AM_PROGRAMS' is still in use;
-     and 'TEXINFOS' and 'MANS' still have no directory prefixes.)
+     use today, i.e., ‘bin_PROGRAMS’ instead of ‘PROGRAMS’,
+     ‘noinst_LIBRARIES’ instead of ‘LIBLIBRARIES’, etc.  (However
+     ‘EXTRA_PROGRAMS’ does not exist yet, ‘AM_PROGRAMS’ is still in use;
+     and ‘TEXINFOS’ and ‘MANS’ still have no directory prefixes.)
      Adding support for prefixes like that was one of the major ideas in
-     'automake'; it has lasted pretty well.
+     ‘automake’; it has lasted pretty well.
 
      AutoMake is renamed to Automake (Tom seems to recall it was
      François Pinard's doing).
@@ -271,28 +271,28 @@
 
 1996-01-13 Automake 0.28
 
-     Automake starts scanning 'configure.in' for 'LIBOBJS' support.
+     Automake starts scanning ‘configure.in’ for ‘LIBOBJS’ support.
      This is an important step because until this version Automake only
-     knew about the 'Makefile.am's it processed.  'configure.in' was
+     knew about the ‘Makefile.am’s it processed.  ‘configure.in’ was
      Autoconf's world and the link between Autoconf and Automake had to
-     be done by the 'Makefile.am' author.  For instance, if 'config.h'
-     was generated by 'configure', it was the package maintainer's
-     responsibility to define the 'CONFIG_HEADER' variable in each
-     'Makefile.am'.
+     be done by the ‘Makefile.am’ author.  For instance, if ‘config.h’
+     was generated by ‘configure’, it was the package maintainer's
+     responsibility to define the ‘CONFIG_HEADER’ variable in each
+     ‘Makefile.am’.
 
      Succeeding releases will rely more and more on scanning
-     'configure.in' to better automate the Autoconf integration.
+     ‘configure.in’ to better automate the Autoconf integration.
 
-     0.28 also introduces the 'AUTOMAKE_OPTIONS' variable and the
-     '--gnu' and '--gnits' options, the latter being stricter.
+     0.28 also introduces the ‘AUTOMAKE_OPTIONS’ variable and the
+     ‘--gnu’ and ‘--gnits’ options, the latter being stricter.
 
 1996-02-07 Automake 0.29
 
-     Thanks to 'configure.in' scanning, 'CONFIG_HEADER' is gone, and
-     rebuild rules for 'configure'-generated file are automatically
+     Thanks to ‘configure.in’ scanning, ‘CONFIG_HEADER’ is gone, and
+     rebuild rules for ‘configure’-generated file are automatically
      output.
 
-     'TEXINFOS' and 'MANS' converted to the uniform naming scheme.
+     ‘TEXINFOS’ and ‘MANS’ converted to the uniform naming scheme.
 
 1996-02-24 Automake 0.30
 
@@ -300,30 +300,30 @@
      cases will be added pretty regularly (*note Releases::), and this
      proved to be really helpful later on.
 
-     'EXTRA_PROGRAMS' finally replaces 'AM_PROGRAMS'.
+     ‘EXTRA_PROGRAMS’ finally replaces ‘AM_PROGRAMS’.
 
      All the third-party Autoconf macros, written mostly by François
      Pinard (and later Jim Meyering), are distributed in Automake's
-     hand-written 'aclocal.m4' file.  Package maintainers are expected
+     hand-written ‘aclocal.m4’ file.  Package maintainers are expected
      to extract the necessary macros from this file.  (In previous
      versions you had to copy and paste them from the manual...)
 
 1996-03-11 Automake 0.31
 
-     The test suite in 0.30 was run via a long 'check-local' rule.  Upon
+     The test suite in 0.30 was run via a long ‘check-local’ rule.  Upon
      Ulrich Drepper's suggestion, 0.31 makes it an Automake rule output
-     whenever the 'TESTS' variable is defined.
+     whenever the ‘TESTS’ variable is defined.
 
-     'DIST_OTHER' is renamed to 'EXTRA_DIST', and the 'check_' prefix is
+     ‘DIST_OTHER’ is renamed to ‘EXTRA_DIST’, and the ‘check_’ prefix is
      introduced.  The syntax is now the same as today.
 
 1996-03-15 Gordon Matzigkeit starts writing libtool.
 
 1996-04-27 Automake 0.32
 
-     '-hook' targets are introduced; an idea from Dieter Baron.
+     ‘-hook’ targets are introduced; an idea from Dieter Baron.
 
-     '*.info' files, which were output in the build directory are now
+     ‘*.info’ files, which were output in the build directory are now
      built in the source directory, because they are distributed.  It
      seems these files like to move back and forth as that will happen
      again in future versions.
@@ -332,22 +332,22 @@
 
      Gord Matzigkeit's main two contributions:
 
-        * very preliminary libtool support
-        * the distcheck rule
+        • very preliminary libtool support
+        • the distcheck rule
 
      Although they were very basic at this point, these are probably
      among the top features for Automake today.
 
-     Jim Meyering also provides the infamous 'jm_MAINTAINER_MODE', since
-     then renamed to 'AM_MAINTAINER_MODE' and abandoned by its author
+     Jim Meyering also provides the infamous ‘jm_MAINTAINER_MODE’, since
+     then renamed to ‘AM_MAINTAINER_MODE’ and abandoned by its author
      (*note maintainer-mode: (automake)maintainer-mode.).
 
 1996-05-28 Automake 1.0
 
-     After only six months of heavy development, the 'automake' script
-     is 3134 lines long, plus 973 lines of 'Makefile' fragments.  The
+     After only six months of heavy development, the ‘automake’ script
+     is 3134 lines long, plus 973 lines of ‘Makefile’ fragments.  The
      package has 30 pages of documentation, and 38 test cases.
-     'aclocal.m4' contains 4 macros.
+     ‘aclocal.m4’ contains 4 macros.
 
      From now on and until version 1.4, new releases will occur at a
      rate of about one a year.  1.1 did not exist, actually 1.1b to 1.1p
@@ -363,7 +363,7 @@
      stalled.  Roland McGrath has been working at the beginning of the
      year.  David comes back in November to release 2.12, but he won't
      touch Autoconf anymore after this year, and Autoconf then really
-     stagnates.  The desolate Autoconf 'ChangeLog' for 1997 lists only 7
+     stagnates.  The desolate Autoconf ‘ChangeLog’ for 1997 lists only 7
      commits.
 
 1997-02-28 <automake@gnu.ai.mit.edu> list alive
@@ -387,10 +387,10 @@
 
      Before that people were discussing Automake privately, on the Gnits
      mailing list (which is not public either), and less frequently on
-     'gnu.misc.discuss'.
+     ‘gnu.misc.discuss’.
 
-     'gnu.ai.mit.edu' is now 'gnu.org', in case you never noticed.  The
-     archives of the early years of the 'automake@gnu.org' list have
+     ‘gnu.ai.mit.edu’ is now ‘gnu.org’, in case you never noticed.  The
+     archives of the early years of the ‘automake@gnu.org’ list have
      been lost, so today it is almost impossible to find traces of
      discussions that occurred before 1999.  This has been annoying more
      than once, as such discussions can be useful to understand the
@@ -400,34 +400,34 @@
 1997-06-22 Automake 1.2
 
      Automake developments continues, and more and more new Autoconf
-     macros are required.  Distributing them in 'aclocal.m4' and
+     macros are required.  Distributing them in ‘aclocal.m4’ and
      requiring people to browse this file to extract the relevant macros
      becomes uncomfortable.  Ideally, some of them should be contributed
      to Autoconf so that they can be used directly, however Autoconf is
-     currently inactive.  Automake 1.2 consequently introduces 'aclocal'
-     ('aclocal' was actually started on 1996-07-28), a tool that
-     automatically constructs an 'aclocal.m4' file from a repository of
+     currently inactive.  Automake 1.2 consequently introduces ‘aclocal’
+     (‘aclocal’ was actually started on 1996-07-28), a tool that
+     automatically constructs an ‘aclocal.m4’ file from a repository of
      third-party macros.  Because Autoconf has stalled, Automake also
      becomes a kind of repository for such third-party macros, even
      macros completely unrelated to Automake (for instance macros that
      fix broken Autoconf macros).
 
      The 1.2 release contains 20 macros, including the
-     'AM_INIT_AUTOMAKE' macro that simplifies the creation of
-     'configure.in'.
+     ‘AM_INIT_AUTOMAKE’ macro that simplifies the creation of
+     ‘configure.in’.
 
-     Libtool is fully supported using '*_LTLIBRARIES'.
+     Libtool is fully supported using ‘*_LTLIBRARIES’.
 
      The missing script is introduced by François Pinard; it is meant to
-     be a better solution than 'AM_MAINTAINER_MODE' (*note
+     be a better solution than ‘AM_MAINTAINER_MODE’ (*note
      maintainer-mode: (automake)maintainer-mode.).
 
      Conditionals support was implemented by Ian Lance Taylor.  At the
      time, Tom and Ian were working on an internal project at Cygnus.
      They were using ILU, which is pretty similar to CORBA.  They wanted
-     to integrate ILU into their build, which was all 'configure'-based,
-     and Ian thought that adding conditionals to 'automake' was simpler
-     than doing all the work in 'configure' (which was the standard at
+     to integrate ILU into their build, which was all ‘configure’-based,
+     and Ian thought that adding conditionals to ‘automake’ was simpler
+     than doing all the work in ‘configure’ (which was the standard at
      the time).  So this was actually funded by Cygnus.
 
      This very useful but tricky feature will take a lot of time to
@@ -435,8 +435,8 @@
      primaries that have not been updated to support conditional
      definitions in Automake 1.9.)
 
-     The 'automake' script has almost doubled: 6089 lines of Perl, plus
-     1294 lines of 'Makefile' fragments.
+     The ‘automake’ script has almost doubled: 6089 lines of Perl, plus
+     1294 lines of ‘Makefile’ fragments.
 
 1997-07-08 Gordon Matzigkeit releases Libtool 1.0.
 
@@ -448,25 +448,25 @@
      Perl 5.004_04 is out, but fixes to support Perl 4 are still
      regularly submitted whenever Automake breaks it.
 
-1998-09-06 'sourceware.cygnus.com' is on-line.
+1998-09-06 ‘sourceware.cygnus.com’ is on-line.
 
      Sourceware was setup by Jason Molenda to host open source projects.
 
-1998-09-19 Automake CVS repository moved to 'sourceware.cygnus.com'
-1998-10-26 'sourceware.cygnus.com' announces it hosts Automake:
-     Automake is now hosted on 'sourceware.cygnus.com'.  It has a
+1998-09-19 Automake CVS repository moved to ‘sourceware.cygnus.com’
+1998-10-26 ‘sourceware.cygnus.com’ announces it hosts Automake:
+     Automake is now hosted on ‘sourceware.cygnus.com’.  It has a
      publicly accessible CVS repository.  This CVS repository is a copy
      of the one Tom was using on his machine, which in turn is based on
      a copy of the CVS repository of David MacKenzie.  This is why we
      still have to full source history.  (Automake was on Sourceware
      until 2007-10-29, when it moved to a git repository on
-     'savannah.gnu.org', but the Sourceware host had been renamed to
-     'sources.redhat.com'.)
+     ‘savannah.gnu.org’, but the Sourceware host had been renamed to
+     ‘sources.redhat.com’.)
 
      The oldest file in the administrative directory of the CVS
      repository that was created on Sourceware is dated 1998-09-19,
-     while the announcement that 'automake' and 'autoconf' had joined
-     'sourceware' was made on 1998-10-26.  They were among the first
+     while the announcement that ‘automake’ and ‘autoconf’ had joined
+     ‘sourceware’ was made on 1998-10-26.  They were among the first
      projects to be hosted there.
 
      The heedful reader will have noticed Automake was exactly 4 years
@@ -476,22 +476,22 @@
 
 1999-01-14 Automake 1.4
 
-     This release adds support for Fortran 77 and for the 'include'
-     statement.  Also, '+=' assignments are introduced, but it is still
+     This release adds support for Fortran 77 and for the ‘include’
+     statement.  Also, ‘+=’ assignments are introduced, but it is still
      quite easy to fool Automake when mixing this with conditionals.
 
      These two releases, Automake 1.4 and Autoconf 2.13 make a duo that
      will be used together for years.
 
-     'automake' is 7228 lines, plus 1591 lines of Makefile fragment, 20
+     ‘automake’ is 7228 lines, plus 1591 lines of Makefile fragment, 20
      macros (some 1.3 macros were finally contributed back to Autoconf),
      197 test cases, and 51 pages of documentation.
 
-1999-03-27 The 'user-dep-branch' is created on the CVS repository.
+1999-03-27 The ‘user-dep-branch’ is created on the CVS repository.
 
      This implements a new dependency tracking schemed that should be
      able to handle automatic dependency tracking using any compiler
-     (not just gcc) and any make (not just GNU 'make').  In addition,
+     (not just gcc) and any make (not just GNU ‘make’).  In addition,
      the new scheme should be more reliable than the old one, as
      dependencies are generated on the end user's machine.  Alexandre
      Oliva creates depcomp for this purpose.
@@ -499,7 +499,7 @@
      *Note Dependency Tracking Evolution::, for more details about the
      evolution of automatic dependency tracking in Automake.
 
-1999-11-21 The 'user-dep-branch' is merged into the main trunk.
+1999-11-21 The ‘user-dep-branch’ is merged into the main trunk.
 
      This was a huge problem since we also had patches going in on the
      trunk.  The merge took a long time and was very painful.
@@ -551,27 +551,27 @@
      mailing list was created in May.
 
      Year after year, Automake had drifted away from its initial design:
-     construct 'Makefile.in' by assembling various 'Makefile' fragments.
-     In 1.4, lots of 'Makefile' rules are being emitted at various
-     places in the 'automake' script itself; this does not help ensuring
+     construct ‘Makefile.in’ by assembling various ‘Makefile’ fragments.
+     In 1.4, lots of ‘Makefile’ rules are being emitted at various
+     places in the ‘automake’ script itself; this does not help ensuring
      a consistent treatment of these rules (for instance making sure
      that user-defined rules override Automake's own rules).  One of
      Akim's goal was moving all of these hard-coded rules to separate
-     'Makefile' fragments, so the logic could be centralized in a
-     'Makefile' fragment processor.
+     ‘Makefile’ fragments, so the logic could be centralized in a
+     ‘Makefile’ fragment processor.
 
      Another significant contribution of Akim is the interface with the
-     "trace" feature of Autoconf.  The way to scan 'configure.in' at
+     "trace" feature of Autoconf.  The way to scan ‘configure.in’ at
      this time was to read the file and grep the various macro of
      interest to Automake.  Doing so could break in many unexpected
-     ways; 'automake' could miss some definition (for instance
-     'AC_SUBST($1, $2)' where the arguments are known only when M4
+     ways; ‘automake’ could miss some definition (for instance
+     ‘AC_SUBST($1, $2)’ where the arguments are known only when M4
      is run), or conversely it could detect some macro that was not
      expanded (because it is called conditionally).  In the CVS version
-     of Autoconf, Akim had implemented the '--trace' option, which
+     of Autoconf, Akim had implemented the ‘--trace’ option, which
      provides accurate information about where macros are actually
      called and with what arguments.  Akim will equip Automake with a
-     second 'configure.in' scanner that uses this '--trace' interface.
+     second ‘configure.in’ scanner that uses this ‘--trace’ interface.
      Since it was not sensible to drop the Autoconf 2.13 compatibility
      yet, this experimental scanner was only used when an environment
      variable was set, the traditional grep-scanner being still the
@@ -604,47 +604,47 @@
 
      Gary continues his patch-release series.  These also add support
      for some new Autoconf 2.50 idioms.  Essentially, Autoconf now
-     advocates 'configure.ac' over 'configure.in', and it introduces a
-     new syntax for 'AC_OUTPUT'ing files.
+     advocates ‘configure.ac’ over ‘configure.in’, and it introduces a
+     new syntax for ‘AC_OUTPUT’ing files.
 
 2001-08-23 Automake 1.5
 
      A major and long-awaited release, that comes more than two years
      after 1.4.  It brings many changes, among which:
-        * The new dependency tracking scheme that uses 'depcomp'.  Aside
+        • The new dependency tracking scheme that uses ‘depcomp’.  Aside
           from the improvement on the dependency tracking itself (*note
           Dependency Tracking Evolution::), this also streamlines the
-          use of 'automake'-generated 'Makefile.in's as the
-          'Makefile.in's used during development are now the same as
-          those used in distributions.  Before that the 'Makefile.in's
-          generated for maintainers required GNU 'make' and GCC, they
-          were different from the portable 'Makefile' generated for
+          use of ‘automake’-generated ‘Makefile.in’s as the
+          ‘Makefile.in’s used during development are now the same as
+          those used in distributions.  Before that the ‘Makefile.in’s
+          generated for maintainers required GNU ‘make’ and GCC, they
+          were different from the portable ‘Makefile’ generated for
           distribution; this was causing some confusion.
 
-        * Support for per-target compilation flags.
+        • Support for per-target compilation flags.
 
-        * Support for reference to files in subdirectories in most
-          'Makefile.am' variables.
+        • Support for reference to files in subdirectories in most
+          ‘Makefile.am’ variables.
 
-        * Introduction of the 'dist_', 'nodist_', and 'nobase_'
+        • Introduction of the ‘dist_’, ‘nodist_’, and ‘nobase_’
           prefixes.
-        * Perl 4 support is finally dropped.
+        • Perl 4 support is finally dropped.
 
      1.5 did break several packages that worked with 1.4.  Enough so
      that Linux distributions could not easily install the new Automake
      version without breaking many of the packages for which they had to
-     run 'automake'.
+     run ‘automake’.
 
      Some of these breakages were effectively bugs that would eventually
      be fixed in the next release.  However, a lot of damage was caused
      by some changes made deliberately to render Automake stricter on
-     some setup we did consider bogus.  For instance, 'make distcheck'
-     was improved to check that 'make uninstall' did remove all the
-     files 'make install' installed, that 'make distclean' did not omit
+     some setup we did consider bogus.  For instance, ‘make distcheck’
+     was improved to check that ‘make uninstall’ did remove all the
+     files ‘make install’ installed, that ‘make distclean’ did not omit
      some file, and that a VPATH build would work even if the source
      directory was read-only.  Similarly, Automake now rejects multiple
      definitions of the same variable (because that would mix very badly
-     with conditionals), and '+=' assignments with no previous
+     with conditionals), and ‘+=’ assignments with no previous
      definition.  Because these changes all occurred suddenly after 1.4
      had been established for more than two years, it hurt users.
 
@@ -656,19 +656,18 @@
      This release introduced versioned installation (*note API
      Versioning: (automake)API Versioning.).  This was mainly pushed by
      Havoc Pennington, taking the GNOME source tree as motive: due to
-     incompatibilities between the autotools it's impossible for the
-     GNOME packages to switch to Autoconf 2.53 and Automake 1.5 all at
-     once, so they are currently stuck with Autoconf 2.13 and Automake
-     1.4.
+     incompatibility between the autotools it's impossible for the GNOME
+     packages to switch to Autoconf 2.53 and Automake 1.5 all at once,
+     so they are currently stuck with Autoconf 2.13 and Automake 1.4.
 
-     The idea was to call this version 'automake-1.6', call all its
-     bug-fix versions identically, and switch to 'automake-1.7' for the
+     The idea was to call this version ‘automake-1.6’, call all its
+     bug-fix versions identically, and switch to ‘automake-1.7’ for the
      next release that adds new features or changes some rules.  This
      scheme implies maintaining a bug-fix branch in addition to the
      development trunk, which means more work from the maintainer, but
      providing regular bug-fix releases proved to be really worthwhile.
 
-     Like 1.5, 1.6 also introduced a bunch of incompatibilities,
+     Like 1.5, 1.6 also introduced a bunch of incompatibility,
      intentional or not.  Perhaps the more annoying was the dependence
      on the newly released Autoconf 2.53.  Autoconf seemed to have
      stabilized enough since its explosive 2.50 release and included
@@ -691,7 +690,7 @@
      This one and those following will be handled by Alexandre
      Duret-Lutz.  Tom is still around, and will be there until about
      1.7, but his interest into Automake is drifting away towards
-     projects like 'gcj'.
+     projects like ‘gcj’.
 
      Alexandre has been using Automake since 2000, and started to
      contribute mostly on Akim's incitement (Akim and Alexandre have
@@ -711,7 +710,7 @@
 
 2002-09-25 Automake 1.7
 
-     This release switches to the new 'configure.ac' scanner Akim was
+     This release switches to the new ‘configure.ac’ scanner Akim was
      experimenting in 1.5.
 
 2002-10-16 Automake 1.7.1
@@ -734,29 +733,29 @@
      Marshall, one of the characters, is working on a computer virus
      that he has to modify before it gets into the wrong hands or
      something like that.  The screenshots you see do not show any
-     program code, they show a 'Makefile.in' generated by automake...
+     program code, they show a ‘Makefile.in’ generated by automake...
 
 2003-11-09 Automake 1.7.9
 
 2003-12-10 Automake 1.8
 
-     The most striking update is probably that of 'aclocal'.
+     The most striking update is probably that of ‘aclocal’.
 
-     'aclocal' now uses 'm4_include' in the produced 'aclocal.m4' when
+     ‘aclocal’ now uses ‘m4_include’ in the produced ‘aclocal.m4’ when
      the included macros are already distributed with the package (an
      idiom used in many packages), which reduces code duplication.  Many
      people liked that, but in fact this change was really introduced to
-     fix a bug in rebuild rules: 'Makefile.in' must be rebuilt whenever
-     a dependency of 'configure' changes, but all the 'm4' files
-     included in 'aclocal.m4' where unknown from 'automake'.  Now
-     'automake' can just trace the 'm4_include's to discover the
+     fix a bug in rebuild rules: ‘Makefile.in’ must be rebuilt whenever
+     a dependency of ‘configure’ changes, but all the ‘m4’ files
+     included in ‘aclocal.m4’ where unknown from ‘automake’.  Now
+     ‘automake’ can just trace the ‘m4_include’s to discover the
      dependencies.
 
-     'aclocal' also starts using the '--trace' Autoconf option in order
+     ‘aclocal’ also starts using the ‘--trace’ Autoconf option in order
      to discover used macros more accurately.  This will turn out to be
      very tricky (later releases will improve this) as people had
-     devised many ways to cope with the limitation of previous 'aclocal'
-     versions, notably using handwritten 'm4_include's: 'aclocal' must
+     devised many ways to cope with the limitation of previous ‘aclocal’
+     versions, notably using handwritten ‘m4_include’s: ‘aclocal’ must
      make sure not to redefine a rule that is already included by such
      statement.
 
@@ -777,7 +776,7 @@
 
      This release tries to simplify the compilation rules it outputs to
      reduce the size of the Makefile.  The complaint initially come from
-     the libgcj developers.  Their 'Makefile.in' generated with Automake
+     the libgcj developers.  Their ‘Makefile.in’ generated with Automake
      1.4 and custom build rules (1.4 did not support compiled Java) is
      250KB.  The one generated by 1.8 was over 9MB!  1.9 gets it down to
      1.2MB.
@@ -790,7 +789,7 @@
      Automake has ten years.  This chapter of the manual was initially
      written for this occasion.
 
-2007-10-29 Automake repository moves to 'savannah.gnu.org'
+2007-10-29 Automake repository moves to ‘savannah.gnu.org’
      and uses git as primary repository.
 
 &#x1f;
@@ -823,48 +822,48 @@
 -----------
 
 Our first attempt at automatic dependency tracking was based on the
-method recommended by GNU 'make'.  (*note Generating Prerequisites
+method recommended by GNU ‘make’.  (*note Generating Prerequisites
 Automatically: (make)Automatic Prerequisites.)
 
    This version worked by precomputing dependencies ahead of time.  For
-each source file, it had a special '.P' file that held the dependencies.
-There was a rule to generate a '.P' file by invoking the compiler
-appropriately.  All such '.P' files were included by the 'Makefile',
-thus implicitly becoming dependencies of 'Makefile'.
+each source file, it had a special ‘.P’ file that held the dependencies.
+There was a rule to generate a ‘.P’ file by invoking the compiler
+appropriately.  All such ‘.P’ files were included by the ‘Makefile’,
+thus implicitly becoming dependencies of ‘Makefile’.
 
 Bugs
 ----
 
 This approach had several critical bugs.
 
-   * The code to generate the '.P' file relied on 'gcc'.  (A limitation,
+   • The code to generate the ‘.P’ file relied on ‘gcc’.  (A limitation,
      not technically a bug.)
-   * The dependency tracking mechanism itself relied on GNU 'make'.  (A
+   • The dependency tracking mechanism itself relied on GNU ‘make’.  (A
      limitation, not technically a bug.)
-   * Because each '.P' file was a dependency of 'Makefile', this meant
-     that dependency tracking was done eagerly by 'make'.  For instance,
-     'make clean' would cause all the dependency files to be updated,
+   • Because each ‘.P’ file was a dependency of ‘Makefile’, this meant
+     that dependency tracking was done eagerly by ‘make’.  For instance,
+     ‘make clean’ would cause all the dependency files to be updated,
      and then immediately removed.  This eagerness also caused problems
      with some configurations; if a certain source file could not be
      compiled on a given architecture for some reason, dependency
      tracking would fail, aborting the entire build.
-   * As dependency tracking was done as a pre-pass, compile times were
+   • As dependency tracking was done as a pre-pass, compile times were
      doubled-the compiler had to be run twice per source file.
-   * 'make dist' re-ran 'automake' to generate a 'Makefile' that did not
+   • ‘make dist’ re-ran ‘automake’ to generate a ‘Makefile’ that did not
      have automatic dependency tracking (and that was thus portable to
-     any version of 'make').  In order to do this portably, Automake had
+     any version of ‘make’).  In order to do this portably, Automake had
      to scan the dependency files and remove any reference that was to a
      source file not in the distribution.  This process was error-prone.
-     Also, if 'make dist' was run in an environment where some object
+     Also, if ‘make dist’ was run in an environment where some object
      file had a dependency on a source file that was only conditionally
-     created, Automake would generate a 'Makefile' that referred to a
+     created, Automake would generate a ‘Makefile’ that referred to a
      file that might not appear in the end user's build.  A special,
      hacky mechanism was required to work around this.
 
 Historical Note
 ---------------
 
-The code generated by Automake is often inspired by the 'Makefile' style
+The code generated by Automake is often inspired by the ‘Makefile’ style
 of a particular author.  In the case of the first implementation of
 dependency tracking, I believe the impetus and inspiration was Jim
 Meyering.  (I could be mistaken.  If you know otherwise feel free to
@@ -885,9 +884,9 @@
 approach.  In particular we were most concerned with eliminating the
 weird rebuilding effect associated with make clean.
 
-   In this approach, the '.P' files were included using the '-include'
-command, which let us create these files lazily.  This avoided the 'make
-clean' problem.
+   In this approach, the ‘.P’ files were included using the ‘-include’
+command, which let us create these files lazily.  This avoided the ‘make
+clean’ problem.
 
    We only computed dependencies when a file was actually compiled.
 This avoided the performance penalty associated with scanning each file
@@ -899,23 +898,23 @@
 Bugs
 ----
 
-   * This approach also relied on the existence of 'gcc' and GNU 'make'.
+   • This approach also relied on the existence of ‘gcc’ and GNU ‘make’.
      (A limitation, not technically a bug.)
-   * Dependency tracking was still done by the developer, so the
+   • Dependency tracking was still done by the developer, so the
      problems from the first implementation relating to massaging of
-     dependencies by 'make dist' were still in effect.
-   * This implementation suffered from the "deleted header file"
-     problem.  Suppose a lazily-created '.P' file includes a dependency
+     dependencies by ‘make dist’ were still in effect.
+   • This implementation suffered from the "deleted header file"
+     problem.  Suppose a lazily-created ‘.P’ file includes a dependency
      on a given header file, like this:
 
           maude.o: maude.c something.h
 
-     Now suppose that you remove 'something.h' and update 'maude.c' so
-     that this include is no longer needed.  If you run 'make', you will
-     get an error because there is no way to create 'something.h'.
+     Now suppose that you remove ‘something.h’ and update ‘maude.c’ so
+     that this include is no longer needed.  If you run ‘make’, you will
+     get an error because there is no way to create ‘something.h’.
 
      We fixed this problem in a later release by further massaging the
-     output of 'gcc' to include a dummy dependency for each header file.
+     output of ‘gcc’ to include a dummy dependency for each header file.
 
 &#x1f;
 File: automake-history.info,  Node: Dependencies for the User,  Next: Techniques for Dependencies,  Prev: Dependencies As Side Effects,  Up: Dependency Tracking Evolution
@@ -926,11 +925,11 @@
 Description
 -----------
 
-The bugs associated with 'make dist', over time, became a real problem.
+The bugs associated with ‘make dist’, over time, became a real problem.
 Packages using Automake were being built on a large number of platforms,
 and were becoming increasingly complex.  Broken dependencies were
-distributed in "portable" 'Makefile.in's, leading to user complaints.
-Also, the requirement for 'gcc' and GNU 'make' was a constant source of
+distributed in "portable" ‘Makefile.in’s, leading to user complaints.
+Also, the requirement for ‘gcc’ and GNU ‘make’ was a constant source of
 bug reports.  The next implementation of dependency tracking aimed to
 remove these problems.
 
@@ -945,17 +944,17 @@
 let us abstract away differences between dependency tracking methods for
 compilers.  For instance, some compilers cannot generate dependencies as
 a side effect of compilation.  In this case we simply have the script
-run the compiler twice.  Currently our wrapper script ('depcomp') knows
+run the compiler twice.  Currently our wrapper script (‘depcomp’) knows
 about twelve different compilers (including a "compiler" that simply
-invokes 'makedepend' and then the real compiler, which is assumed to be
+invokes ‘makedepend’ and then the real compiler, which is assumed to be
 a standard Unix-like C compiler with no way to do dependency tracking).
 
 Bugs
 ----
 
-   * Running a wrapper script for each compilation slows down the build.
-   * Many users don't really care about precise dependencies.
-   * This implementation, like every other automatic dependency tracking
+   • Running a wrapper script for each compilation slows down the build.
+   • Many users don't really care about precise dependencies.
+   • This implementation, like every other automatic dependency tracking
      scheme in common use today (indeed, every one we've ever heard of),
      suffers from the "duplicated new header" bug.
 
@@ -982,7 +981,7 @@
      in Java.)  This problem is easy to fix, by modifying dependency
      generators to record every probe, instead of every successful open.
 
-   * Since Automake generates dependencies as a side effect of
+   • Since Automake generates dependencies as a side effect of
      compilation, there is a bootstrapping problem when header files are
      generated by running a program.  The problem is that, the first
      time the build is done, there is no way by default to know that the
@@ -992,7 +991,7 @@
      This was also a problem in the previous dependency tracking
      implementation.
 
-     The current fix is to use 'BUILT_SOURCES' to list built headers
+     The current fix is to use ‘BUILT_SOURCES’ to list built headers
      (*note Sources: (automake)Sources.).  This causes them to be built
      before any other build rules are run.  This is unsatisfactory as a
      general solution, however in practice it seems sufficient for most
@@ -1003,19 +1002,19 @@
    In GCC 3.0, we managed to convince the maintainers to add special
 command-line options to help Automake more efficiently do its job.  We
 hoped this would let us avoid the use of a wrapper script when
-Automake's automatic dependency tracking was used with 'gcc'.
+Automake's automatic dependency tracking was used with ‘gcc’.
 
    Unfortunately, this code doesn't quite do what we want.  In
 particular, it removes the dependency file if the compilation fails;
 we'd prefer that it instead only touch the file in any way if the
 compilation succeeds.
 
-   Nevertheless, since Automake 1.7, when a recent 'gcc' is detected at
-'configure' time, we inline the dependency-generation code and do not
-use the 'depcomp' wrapper script.  This makes compilations faster for
+   Nevertheless, since Automake 1.7, when a recent ‘gcc’ is detected at
+‘configure’ time, we inline the dependency-generation code and do not
+use the ‘depcomp’ wrapper script.  This makes compilations faster for
 those using this compiler (probably our primary user base).  The
 counterpart is that because we have to encode two compilation rules in
-'Makefile' (with or without 'depcomp'), the produced 'Makefile's are
+‘Makefile’ (with or without ‘depcomp’), the produced ‘Makefile’s are
 larger.
 
 &#x1f;
@@ -1027,10 +1026,10 @@
 There are actually several ways for a build tool like Automake to cause
 tools to generate dependencies.
 
-'makedepend'
+‘makedepend’
      This was a commonly-used method in the past.  The idea is to run a
      special program over the source and have it generate dependency
-     information.  Traditional implementations of 'makedepend' are not
+     information.  Traditional implementations of ‘makedepend’ are not
      completely precise; ordinarily they were conservative and
      discovered too many dependencies.
 The tool
@@ -1042,15 +1041,15 @@
 The file system
      It is possible to write a special file system that tracks opens,
      reads, writes, etc, and then feed this information back to the
-     build tool.  'clearmake' does this.  This is a very powerful
+     build tool.  ‘clearmake’ does this.  This is a very powerful
      technique, as it doesn't require cooperation from the tool.
      Unfortunately it is also very difficult to implement and also not
      practical in the general case.
-'LD_PRELOAD'
+‘LD_PRELOAD’
      Rather than use the file system, one could write a special library
-     to intercept 'open' and other syscalls.  This technique is also
+     to intercept ‘open’ and other syscalls.  This technique is also
      quite powerful, but unfortunately it is not portable enough for use
-     in 'automake'.
+     in ‘automake’.
 
 * Menu:
 
@@ -1065,7 +1064,7 @@
 
 We think that every compilation tool ought to be able to generate
 dependencies as a side effect of compilation.  Furthermore, at least
-while 'make'-based tools are nearly universally in use (at least in the
+while ‘make’-based tools are nearly universally in use (at least in the
 free software community), the tool itself should generate dummy
 dependencies for header files, to avoid the deleted header file bug.
 Finally, the tool should generate a dependency for each probe, instead
@@ -1089,19 +1088,19 @@
 3 Release Statistics
 ********************
 
-The following table (inspired by 'perlhist(1)') quantifies the evolution
+The following table (inspired by ‘perlhist(1)’) quantifies the evolution
 of Automake using these metrics:
 
 Date, Rel
      The date and version of the release.
 am
-     The number of lines of the 'automake' script.
+     The number of lines of the ‘automake’ script.
 acl
-     The number of lines of the 'aclocal' script.
+     The number of lines of the ‘aclocal’ script.
 pm
-     The number of lines of the 'Perl' supporting modules.
-'*.am'
-     The number of lines of the 'Makefile' fragments.  The number in
+     The number of lines of the ‘Perl’ supporting modules.
+‘*.am’
+     The number of lines of the ‘Makefile’ fragments.  The number in
      parentheses is the number of files.
 m4
      The number of lines (and files) of Autoconf macros.
@@ -1111,7 +1110,7 @@
      The number of test cases in the test suite.  Of those, the number
      in parentheses is the number of generated test cases.
 
-Date         Rel      am     acl    pm     '*.am'      m4          doc   t
+Date         Rel      am     acl    pm     ‘*.am’      m4          doc   t
 ------------------------------------------------------------------------------------
 1994-09-19   CVS      141                  299 (24)
 1994-11-05   CVS      208                  332 (28)
@@ -1190,7 +1189,7 @@
 
                      Version 1.3, 3 November 2008
 
-     Copyright (C) 2000-2021 Free Software Foundation, Inc.
+     Copyright © 2000-2024 Free Software Foundation, Inc.
      <https://fsf.org/>
 
      Everyone is permitted to copy and distribute verbatim copies
@@ -1199,7 +1198,7 @@
   0. PREAMBLE
 
      The purpose of this License is to make a manual, textbook, or other
-     functional and useful document "free" in the sense of freedom: to
+     functional and useful document “free” in the sense of freedom: to
      assure everyone the effective freedom to copy and redistribute it,
      with or without modifying it, either commercially or
      noncommercially.  Secondarily, this License preserves for the
@@ -1667,18 +1666,18 @@
 
 &#x1f;
 Tag Table:
-Node: Top&#x7f;854
-Node: Timeline&#x7f;2388
-Node: Dependency Tracking Evolution&#x7f;33849
-Node: First Take on Dependencies&#x7f;34691
-Node: Dependencies As Side Effects&#x7f;37349
-Node: Dependencies for the User&#x7f;39408
-Node: Techniques for Dependencies&#x7f;44438
-Node: Recommendations for Tool Writers&#x7f;46136
-Node: Future Directions for Dependencies&#x7f;46855
-Node: Releases&#x7f;47325
-Node: Copying This Manual&#x7f;52712
-Node: GNU Free Documentation License&#x7f;52939
+Node: Top&#x7f;853
+Node: Timeline&#x7f;2386
+Node: Dependency Tracking Evolution&#x7f;34540
+Node: First Take on Dependencies&#x7f;35382
+Node: Dependencies As Side Effects&#x7f;38130
+Node: Dependencies for the User&#x7f;40243
+Node: Techniques for Dependencies&#x7f;45337
+Node: Recommendations for Tool Writers&#x7f;47059
+Node: Future Directions for Dependencies&#x7f;47782
+Node: Releases&#x7f;48252
+Node: Copying This Manual&#x7f;53667
+Node: GNU Free Documentation License&#x7f;53894
 &#x1f;
 End Tag Table

_service:tar_scm:automake-1.16.5.tar.xz/doc/automake-history.texi -> _service:tar_scm:automake-1.17.tar.xz/doc/automake-history.texi Changed

@@ -10,7 +10,7 @@
 This manual describes (part of) the history of GNU Automake, a program
 that creates GNU standards-compliant Makefiles from template files.
 
-Copyright @copyright{} 1995--2021 Free Software Foundation, Inc.
+Copyright @copyright{} 1995--2024 Free Software Foundation, Inc.
 
 @quotation
 Permission is granted to copy, distribute and/or modify this document
@@ -688,7 +688,7 @@
 This release introduced versioned installation (@pxref{API Versioning, ,
 API Versioning, automake, GNU Automake}). This was mainly pushed by
 Havoc Pennington, taking the GNOME source tree as motive: due to
-incompatibilities between the autotools it's impossible for the GNOME
+incompatibility between the autotools it's impossible for the GNOME
 packages to switch to Autoconf 2.53 and Automake 1.5 all at once, so
 they are currently stuck with Autoconf 2.13 and Automake 1.4.
 
@@ -699,7 +699,7 @@
 development trunk, which means more work from the maintainer, but
 providing regular bug-fix releases proved to be really worthwhile.
 
-Like 1.5, 1.6 also introduced a bunch of incompatibilities, intentional or
+Like 1.5, 1.6 also introduced a bunch of incompatibility, intentional or
 not.  Perhaps the more annoying was the dependence on the newly
 released Autoconf 2.53.  Autoconf seemed to have stabilized enough
 since its explosive 2.50 release and included changes required to fix

_service:tar_scm:automake-1.16.5.tar.xz/doc/automake.info -> _service:tar_scm:automake-1.17.tar.xz/doc/automake.info Changed

@@ -1,18 +1,17 @@
-This is automake.info, produced by makeinfo version 6.8 from
+This is automake.info, produced by makeinfo version 7.1 from
 automake.texi.
 
-This manual is for GNU Automake (version 1.16.5, 1 October 2021), a
-program that creates GNU standards-compliant Makefiles from template
-files.
+This manual is for GNU Automake (version 1.17, 12 July 2024), a program
+that creates GNU standards-compliant Makefiles from template files.
 
-   Copyright © 1995–2021 Free Software Foundation, Inc.
+   Copyright © 1995-2024 Free Software Foundation, Inc.
 
      Permission is granted to copy, distribute and/or modify this
      document under the terms of the GNU Free Documentation License,
      Version 1.3 or any later version published by the Free Software
      Foundation; with no Invariant Sections, with no Front-Cover texts,
      and with no Back-Cover Texts.  A copy of the license is included in
-     the section entitled “GNU Free Documentation License.”
+     the section entitled "GNU Free Documentation License."
 
 INFO-DIR-SECTION Software development
 START-INFO-DIR-ENTRY
@@ -27,215 +26,226 @@
 
 &#x1f;
 Indirect:
-automake.info-1: 1083
-automake.info-2: 301994
+automake.info-1: 1073
+automake.info-2: 307943
 &#x1f;
 Tag Table:
 (Indirect)
-Node: Top&#x7f;1083
-Node: Introduction&#x7f;14520
-Ref: Introduction-Footnote-1&#x7f;15929
-Node: Autotools Introduction&#x7f;16088
-Node: GNU Build System&#x7f;17470
-Node: Use Cases&#x7f;20218
-Node: Basic Installation&#x7f;22346
-Node: Standard Targets&#x7f;25932
-Node: Standard Directory Variables&#x7f;27535
-Node: Standard Configuration Variables&#x7f;29392
-Node: config.site&#x7f;30751
-Node: VPATH Builds&#x7f;32177
-Node: Two-Part Install&#x7f;36235
-Node: Cross-Compilation&#x7f;38679
-Node: Renaming&#x7f;41645
-Node: DESTDIR&#x7f;42803
-Node: Preparing Distributions&#x7f;44985
-Node: Dependency Tracking&#x7f;47355
-Node: Nested Packages&#x7f;49463
-Node: Why Autotools&#x7f;50979
-Node: Hello World&#x7f;52621
-Ref: amhello Explained&#x7f;53043
-Node: Creating amhello&#x7f;53215
-Node: amhello's configure.ac Setup Explained&#x7f;58570
-Node: amhello's Makefile.am Setup Explained&#x7f;63491
-Node: Generalities&#x7f;67191
-Node: General Operation&#x7f;67885
-Node: Strictness&#x7f;71309
-Ref: Gnits&#x7f;71443
-Node: Uniform&#x7f;75343
-Node: Length Limitations&#x7f;80240
-Node: Canonicalization&#x7f;82551
-Node: User Variables&#x7f;83623
-Node: Auxiliary Programs&#x7f;85113
-Node: Examples&#x7f;89050
-Node: Complete&#x7f;89920
-Node: true&#x7f;92025
-Node: automake Invocation&#x7f;94516
-Ref: Invoking automake&#x7f;94671
-Node: configure&#x7f;103286
-Node: Requirements&#x7f;104215
-Node: Optional&#x7f;109453
-Node: aclocal Invocation&#x7f;119196
-Ref: Invoking aclocal&#x7f;119357
-Node: aclocal Options&#x7f;122395
-Node: Macro Search Path&#x7f;126105
-Ref: ACLOCAL_PATH&#x7f;130479
-Node: Extending aclocal&#x7f;132049
-Node: Local Macros&#x7f;135748
-Node: Serials&#x7f;139731
-Node: Future of aclocal&#x7f;144951
-Node: Macros&#x7f;147301
-Node: Public Macros&#x7f;147842
-Ref: Modernize AM_INIT_AUTOMAKE invocation&#x7f;149465
-Node: Obsolete Macros&#x7f;153947
-Node: Private Macros&#x7f;155289
-Node: Directories&#x7f;156739
-Node: Subdirectories&#x7f;158334
-Node: Conditional Subdirectories&#x7f;161726
-Node: SUBDIRS vs DIST_SUBDIRS&#x7f;163407
-Node: Subdirectories with AM_CONDITIONAL&#x7f;165045
-Node: Subdirectories with AC_SUBST&#x7f;166239
-Node: Unconfigured Subdirectories&#x7f;167066
-Node: Alternative&#x7f;170524
-Node: Subpackages&#x7f;172711
-Node: Programs&#x7f;176066
-Node: A Program&#x7f;177608
-Node: Program Sources&#x7f;178331
-Node: Linking&#x7f;180236
-Node: Conditional Sources&#x7f;183880
-Node: Conditional Programs&#x7f;186808
-Node: A Library&#x7f;188698
-Node: A Shared Library&#x7f;191375
-Node: Libtool Concept&#x7f;192379
-Node: Libtool Libraries&#x7f;194469
-Node: Conditional Libtool Libraries&#x7f;196203
-Node: Conditional Libtool Sources&#x7f;198660
-Node: Libtool Convenience Libraries&#x7f;200047
-Node: Libtool Modules&#x7f;203474
-Node: Libtool Flags&#x7f;204790
-Node: LTLIBOBJS&#x7f;206701
-Node: Libtool Issues&#x7f;207336
-Node: Error required file ltmain.sh not found&#x7f;207677
-Node: Objects created both with libtool and without&#x7f;208898
-Node: Program and Library Variables&#x7f;210814
-Node: Default _SOURCES&#x7f;222974
-Node: LIBOBJS&#x7f;225451
-Node: Program Variables&#x7f;230678
-Node: Yacc and Lex&#x7f;234223
-Node: Linking Multiple Yacc Parsers&#x7f;238439
-Node: C++ Support&#x7f;240252
-Node: Objective C Support&#x7f;241114
-Node: Objective C++ Support&#x7f;242070
-Node: Unified Parallel C Support&#x7f;243075
-Node: Assembly Support&#x7f;244053
-Node: Fortran 77 Support&#x7f;245225
-Ref: Fortran 77 Support-Footnote-1&#x7f;246892
-Node: Preprocessing Fortran 77&#x7f;247095
-Node: Compiling Fortran 77 Files&#x7f;247699
-Node: Mixing Fortran 77 With C and C++&#x7f;248311
-Ref: Mixing Fortran 77 With C and C++-Footnote-1&#x7f;250634
-Node: How the Linker is Chosen&#x7f;250942
-Node: Fortran 9x Support&#x7f;252481
-Node: Compiling Fortran 9x Files&#x7f;253509
-Node: Java Support with gcj&#x7f;254145
-Node: Vala Support&#x7f;255626
-Node: Support for Other Languages&#x7f;257899
-Node: Dependencies&#x7f;258607
-Node: EXEEXT&#x7f;260494
-Node: Other Objects&#x7f;262734
-Node: Scripts&#x7f;263316
-Node: Headers&#x7f;266175
-Node: Data&#x7f;267970
-Node: Sources&#x7f;268655
-Node: Built Sources Example&#x7f;271660
-Node: Other GNU Tools&#x7f;278832
-Node: Emacs Lisp&#x7f;279361
-Node: gettext&#x7f;281458
-Node: Libtool&#x7f;282146
-Node: Java&#x7f;282405
-Node: Python&#x7f;285064
-Node: Documentation&#x7f;290297
-Node: Texinfo&#x7f;290601
-Node: Man Pages&#x7f;297786
-Node: Install&#x7f;301994
-Node: Basics of Installation&#x7f;302689
-Node: The Two Parts of Install&#x7f;304219
-Node: Extending Installation&#x7f;305759
-Node: Staged Installs&#x7f;306523
-Node: Install Rules for the User&#x7f;307936
-Node: Clean&#x7f;308494
-Node: Dist&#x7f;310666
-Node: Basics of Distribution&#x7f;311170
-Node: Fine-grained Distribution Control&#x7f;315343
-Node: The dist Hook&#x7f;316270
-Node: Checking the Distribution&#x7f;318800
-Node: The Types of Distributions&#x7f;326107
-Node: Tests&#x7f;329260
-Node: Generalities about Testing&#x7f;330456
-Node: Simple Tests&#x7f;333396
-Node: Scripts-based Testsuites&#x7f;333777
-Ref: Testsuite progress on console&#x7f;336150
-Ref: Simple tests and color-tests&#x7f;338243
-Node: Testsuite Environment Overrides&#x7f;340365
-Node: Serial Test Harness&#x7f;342964
-Node: Parallel Test Harness&#x7f;345054
-Ref: Basics of test metadata&#x7f;345560
-Node: Custom Test Drivers&#x7f;354653
-Node: Overview of Custom Test Drivers Support&#x7f;354944
-Node: Declaring Custom Test Drivers&#x7f;357996
-Node: API for Custom Test Drivers&#x7f;359418
-Node: Command-line arguments for test drivers&#x7f;360190
-Node: Log files generation and test results recording&#x7f;362904
-Node: Testsuite progress output&#x7f;367119
-Node: Using the TAP test protocol&#x7f;368541
-Node: Introduction to TAP&#x7f;368903
-Node: Use TAP with the Automake test harness&#x7f;370687
-Node: Incompatibilities with other TAP parsers and drivers&#x7f;376110
-Node: Links and external resources on TAP&#x7f;377511
-Node: DejaGnu Tests&#x7f;379103
-Node: Install Tests&#x7f;381231
-Node: Rebuilding&#x7f;381541
-Node: Options&#x7f;385635
-Node: Options generalities&#x7f;385936
-Node: List of Automake options&#x7f;387717
-Ref: tar-formats&#x7f;395124
-Node: Miscellaneous&#x7f;398637
-Node: Tags&#x7f;398982
-Node: Suffixes&#x7f;402178
-Node: Include&#x7f;403810
-Node: Conditionals&#x7f;405545
-Node: Usage of Conditionals&#x7f;406403
-Node: Limits of Conditionals&#x7f;409761
-Node: Silencing Make&#x7f;410946
-Node: Make verbosity&#x7f;411302
-Ref: Make verbosity-Footnote-1&#x7f;412624
-Node: Tricks For Silencing Make&#x7f;412698
-Node: Automake Silent Rules&#x7f;415205
-Node: Not Enough&#x7f;422183
-Node: Extending&#x7f;422639
-Node: Third-Party Makefiles&#x7f;427673
-Node: Distributing&#x7f;434732
-Node: API Versioning&#x7f;435381
-Node: Upgrading&#x7f;438086
-Node: FAQ&#x7f;440131
-Node: CVS&#x7f;441255
-Node: maintainer-mode&#x7f;449691
-Node: Wildcards&#x7f;453866
-Node: Limitations on File Names&#x7f;457304
-Node: Errors with distclean&#x7f;459934
-Node: Flag Variables Ordering&#x7f;464876
-Node: Renamed Objects&#x7f;472885
-Node: Per-Object Flags&#x7f;474480
-Node: Multiple Outputs&#x7f;477490
-Node: Hard-Coded Install Paths&#x7f;489834
-Node: Debugging Make Rules&#x7f;494978
-Ref: Debugging Make Rules-Footnote-1&#x7f;497124
-Node: Reporting Bugs&#x7f;497302
-Node: Copying This Manual&#x7f;498940
-Node: GNU Free Documentation License&#x7f;499170
-Node: Indices&#x7f;524474
-Node: Macro Index&#x7f;524763
-Node: Variable Index&#x7f;530613
-Node: General Index&#x7f;563584
+Node: Top&#x7f;1073
+Node: Introduction&#x7f;14929
+Ref: Introduction-Footnote-1&#x7f;16338
+Node: Autotools Introduction&#x7f;16495
+Node: GNU Build System&#x7f;17871
+Node: Use Cases&#x7f;20619
+Node: Basic Installation&#x7f;22747
+Node: Standard Targets&#x7f;26329
+Node: Standard Directory Variables&#x7f;27930
+Node: Standard Configuration Variables&#x7f;29787
+Node: config.site&#x7f;31146
+Node: VPATH Builds&#x7f;32572
+Node: Two-Part Install&#x7f;36630
+Node: Cross-Compilation&#x7f;39072
+Node: Renaming&#x7f;42038
+Node: DESTDIR&#x7f;43194
+Node: Preparing Distributions&#x7f;45374
+Node: Dependency Tracking&#x7f;47744
+Node: Nested Packages&#x7f;49852
+Node: Why Autotools&#x7f;51366
+Node: Hello World&#x7f;53008
+Ref: amhello Explained&#x7f;53430
+Node: Creating amhello&#x7f;53602
+Node: amhello's configure.ac Setup Explained&#x7f;59403
+Node: amhello's Makefile.am Setup Explained&#x7f;64320
+Node: Generalities&#x7f;68018
+Node: General Operation&#x7f;68712
+Node: Strictness&#x7f;72130
+Ref: Gnits&#x7f;72264
+Node: Uniform&#x7f;76169
+Node: Length Limitations&#x7f;81062
+Node: Canonicalization&#x7f;83371
+Node: User Variables&#x7f;84443
+Node: Auxiliary Programs&#x7f;85924
+Node: Examples&#x7f;89859
+Node: Complete&#x7f;90729
+Node: true&#x7f;92812
+Node: automake Invocation&#x7f;95296
+Ref: Invoking automake&#x7f;95497
+Node: configure&#x7f;104107
+Node: Requirements&#x7f;105034
+Node: Optional&#x7f;110270
+Node: aclocal Invocation&#x7f;120017
+Ref: Invoking aclocal&#x7f;120222
+Node: aclocal Options&#x7f;123519
+Node: Macro Search Path&#x7f;127882
+Ref: dirlist&#x7f;129741
+Ref: ACLOCAL_PATH&#x7f;132084
+Node: Extending aclocal&#x7f;134001
+Node: Local Macros&#x7f;137653
+Node: Serials&#x7f;141434
+Node: Future of aclocal&#x7f;146673
+Node: Macros&#x7f;148922
+Node: Public Macros&#x7f;149463
+Ref: Modernize AM_INIT_AUTOMAKE invocation&#x7f;151082
+Node: Obsolete Macros&#x7f;155616
+Node: Private Macros&#x7f;156958
+Node: Directories&#x7f;158404
+Node: Subdirectories&#x7f;159993
+Node: Conditional Subdirectories&#x7f;163385
+Node: SUBDIRS vs DIST_SUBDIRS&#x7f;165062
+Node: Subdirectories with AM_CONDITIONAL&#x7f;166700
+Node: Subdirectories with AC_SUBST&#x7f;167890
+Node: Unconfigured Subdirectories&#x7f;168717
+Node: Alternative&#x7f;172175
+Node: Subpackages&#x7f;174354
+Node: Programs&#x7f;177699
+Node: A Program&#x7f;179239
+Node: Program Sources&#x7f;179962
+Node: Linking&#x7f;181861
+Node: Conditional Sources&#x7f;185503
+Node: Conditional Programs&#x7f;188425
+Node: A Library&#x7f;190313
+Node: A Shared Library&#x7f;192989
+Node: Libtool Concept&#x7f;193991
+Node: Libtool Libraries&#x7f;196007
+Node: Conditional Libtool Libraries&#x7f;197741
+Node: Conditional Libtool Sources&#x7f;200202
+Node: Libtool Convenience Libraries&#x7f;201589
+Node: Libtool Modules&#x7f;205020
+Node: Libtool Flags&#x7f;206338
+Node: LTLIBOBJS&#x7f;208252
+Node: Libtool Issues&#x7f;208887
+Node: Error required file ltmain.sh not found&#x7f;209309
+Node: Libtool library used but LIBTOOL is undefined&#x7f;210582
+Node: Objects created both with libtool and without&#x7f;213888
+Node: Program and Library Variables&#x7f;215806
+Node: Default _SOURCES&#x7f;228157
+Node: LIBOBJS&#x7f;230634
+Node: Program Variables&#x7f;235861
+Node: Yacc and Lex&#x7f;239400
+Node: Linking Multiple Yacc Parsers&#x7f;243617
+Node: C++ Support&#x7f;245501
+Node: Objective C Support&#x7f;246361
+Node: Objective C++ Support&#x7f;247315
+Node: Unified Parallel C Support&#x7f;248318
+Node: Assembly Support&#x7f;249294
+Node: Fortran 77 Support&#x7f;250466
+Ref: Fortran 77 Support-Footnote-1&#x7f;252129
+Node: Preprocessing Fortran 77&#x7f;252332
+Node: Compiling Fortran 77 Files&#x7f;252936
+Node: Mixing Fortran 77 With C and C++&#x7f;253548
+Ref: Mixing Fortran 77 With C and C++-Footnote-1&#x7f;255869
+Node: How the Linker is Chosen&#x7f;256177
+Node: Fortran 9x Support&#x7f;257714
+Node: Compiling Fortran 9x Files&#x7f;258740
+Node: Java Support with gcj&#x7f;259376
+Node: Vala Support&#x7f;260857
+Node: Support for Other Languages&#x7f;263344
+Node: Dependencies&#x7f;264052
+Node: EXEEXT&#x7f;266611
+Node: Other Objects&#x7f;268848
+Node: Scripts&#x7f;269430
+Node: Headers&#x7f;272289
+Node: Data&#x7f;274080
+Node: Sources&#x7f;274794
+Node: Built Sources Example&#x7f;277781
+Node: Other GNU Tools&#x7f;284931
+Node: Emacs Lisp&#x7f;285460
+Node: gettext&#x7f;287557
+Node: Libtool&#x7f;288245
+Node: Java&#x7f;288504
+Node: Python&#x7f;291159
+Node: Supported Python versions&#x7f;296946
+Node: Documentation&#x7f;298266
+Node: Texinfo&#x7f;298514
+Node: Man Pages&#x7f;307943
+Node: Install&#x7f;311068
+Node: Basics of Installation&#x7f;311763
+Node: The Two Parts of Install&#x7f;313293
+Node: Extending Installation&#x7f;314832
+Node: Staged Installs&#x7f;315596
+Node: Install Rules for the User&#x7f;317009
+Node: Clean&#x7f;317559
+Node: Dist&#x7f;319727
+Node: Basics of Distribution&#x7f;320231
+Node: Fine-grained Distribution Control&#x7f;325018
+Node: The dist Hook&#x7f;325945
+Node: Checking the Distribution&#x7f;328473
+Node: DISTCHECK_CONFIGURE_FLAGS&#x7f;330323
+Node: distcheck-hook&#x7f;332012
+Node: dvi and distcheck&#x7f;332940
+Node: distcleancheck&#x7f;333965
+Node: distuninstallcheck&#x7f;335786
+Node: Errors with distclean&#x7f;336800
+Node: The Types of Distributions&#x7f;342715
+Node: Tests&#x7f;345958
+Node: Generalities about Testing&#x7f;347154
+Node: Simple Tests&#x7f;350081
+Node: Scripts-based Testsuites&#x7f;350462
+Ref: Testsuite progress on console&#x7f;352827
+Ref: Simple tests and color-tests&#x7f;354920
+Node: Testsuite Environment Overrides&#x7f;357036
+Node: Serial Test Harness&#x7f;359633
+Node: Parallel Test Harness&#x7f;361712
+Ref: Basics of test metadata&#x7f;362218
+Node: Custom Test Drivers&#x7f;371488
+Node: Overview of Custom Test Drivers Support&#x7f;371779
+Node: Declaring Custom Test Drivers&#x7f;374819
+Node: API for Custom Test Drivers&#x7f;376241
+Node: Command-line arguments for test drivers&#x7f;377013
+Ref: Command-line arguments for test drivers-Footnote-1&#x7f;379966
+Node: Log files generation and test results recording&#x7f;380337
+Node: Testsuite progress output&#x7f;384543
+Node: Using the TAP test protocol&#x7f;385959
+Node: Introduction to TAP&#x7f;386319
+Node: Use TAP with the Automake test harness&#x7f;388095
+Node: Incompatibility with other TAP parsers and drivers&#x7f;393496
+Node: Links and external resources on TAP&#x7f;394890
+Node: DejaGnu Tests&#x7f;396476
+Node: Install Tests&#x7f;398600
+Node: Rebuilding&#x7f;398910
+Node: Options&#x7f;403002
+Node: Options generalities&#x7f;403301
+Node: List of Automake options&#x7f;405082
+Ref: tar-formats&#x7f;412710
+Node: Miscellaneous&#x7f;416223
+Node: Tags&#x7f;416566
+Node: Suffixes&#x7f;419762
+Node: Include&#x7f;421585
+Node: Conditionals&#x7f;423442
+Node: Usage of Conditionals&#x7f;424300
+Node: Limits of Conditionals&#x7f;428182
+Node: Silencing Make&#x7f;429367
+Node: Make verbosity&#x7f;429773
+Ref: Make verbosity-Footnote-1&#x7f;431165
+Node: Tricks For Silencing Make&#x7f;431239
+Node: Automake Silent Rules&#x7f;433728
+Node: Unsilencing Automake&#x7f;441143
+Node: Not Enough&#x7f;442397
+Node: Extending&#x7f;442851
+Node: Third-Party Makefiles&#x7f;447881
+Node: Distributing&#x7f;454930
+Node: API Versioning&#x7f;455573
+Node: Upgrading&#x7f;458268
+Node: FAQ&#x7f;460311
+Node: Version Control&#x7f;461365
+Ref: CVS&#x7f;461529
+Node: maintainer-mode&#x7f;469670
+Node: Wildcards&#x7f;473846
+Node: Limitations on File Names&#x7f;477288
+Node: Flag Variables Ordering&#x7f;479914
+Node: Renamed Objects&#x7f;487917
+Node: Per-Object Flags&#x7f;489508
+Node: Multiple Outputs&#x7f;492518
+Node: Hard-Coded Install Paths&#x7f;504555
+Node: Debugging Make Rules&#x7f;509698
+Ref: Debugging Make Rules-Footnote-1&#x7f;511872
+Node: Reporting Bugs&#x7f;512048
+Node: Copying This Manual&#x7f;513684
+Node: GNU Free Documentation License&#x7f;513914
+Node: Indices&#x7f;539015
+Node: Macro Index&#x7f;539304
+Node: Variable Index&#x7f;545227
+Node: General Index&#x7f;578779
 &#x1f;
 End Tag Table

_service:tar_scm:automake-1.16.5.tar.xz/doc/automake.info-1 -> _service:tar_scm:automake-1.17.tar.xz/doc/automake.info-1 Changed

@@ -1,18 +1,17 @@
-This is automake.info, produced by makeinfo version 6.8 from
+This is automake.info, produced by makeinfo version 7.1 from
 automake.texi.
 
-This manual is for GNU Automake (version 1.16.5, 1 October 2021), a
-program that creates GNU standards-compliant Makefiles from template
-files.
+This manual is for GNU Automake (version 1.17, 12 July 2024), a program
+that creates GNU standards-compliant Makefiles from template files.
 
-   Copyright © 1995–2021 Free Software Foundation, Inc.
+   Copyright © 1995-2024 Free Software Foundation, Inc.
 
      Permission is granted to copy, distribute and/or modify this
      document under the terms of the GNU Free Documentation License,
      Version 1.3 or any later version published by the Free Software
      Foundation; with no Invariant Sections, with no Front-Cover texts,
      and with no Back-Cover Texts.  A copy of the license is included in
-     the section entitled “GNU Free Documentation License.”
+     the section entitled "GNU Free Documentation License."
 
 INFO-DIR-SECTION Software development
 START-INFO-DIR-ENTRY
@@ -31,22 +30,21 @@
 GNU Automake
 ************
 
-This manual is for GNU Automake (version 1.16.5, 1 October 2021), a
-program that creates GNU standards-compliant Makefiles from template
-files.
+This manual is for GNU Automake (version 1.17, 12 July 2024), a program
+that creates GNU standards-compliant Makefiles from template files.
 
-   Copyright © 1995–2021 Free Software Foundation, Inc.
+   Copyright © 1995-2024 Free Software Foundation, Inc.
 
      Permission is granted to copy, distribute and/or modify this
      document under the terms of the GNU Free Documentation License,
      Version 1.3 or any later version published by the Free Software
      Foundation; with no Invariant Sections, with no Front-Cover texts,
      and with no Back-Cover Texts.  A copy of the license is included in
-     the section entitled “GNU Free Documentation License.”
+     the section entitled "GNU Free Documentation License."
 
 * Menu:
 
-* Introduction::                Automake’s purpose
+* Introduction::                Automake's purpose
 * Autotools Introduction::      An Introduction to the Autotools
 * Generalities::                General ideas
 * Examples::                    Some example packages
@@ -62,7 +60,7 @@
 * Dist::                        What goes in a distribution
 * Tests::                       Support for test suites
 * Rebuilding::                  Automatic rebuilding of Makefile
-* Options::                     Changing Automake’s behavior
+* Options::                     Changing Automake's behavior
 * Miscellaneous::               Miscellaneous rules
 * Include::                     Including extra files in an Automake template
 * Conditionals::                Conditionals
@@ -75,7 +73,7 @@
 * Copying This Manual::         How to make copies of this manual
 * Indices::                     Indices of variables, macros, and concepts
 
- — The Detailed Node Listing —
+ -- The Detailed Node Listing --
 
 An Introduction to the Autotools
 
@@ -128,14 +126,14 @@
 * aclocal Invocation::          Auto-generating aclocal.m4
 * Macros::                      Autoconf macros supplied with Automake
 
-Auto-generating aclocal.m4
+Auto-generating aclocal.m4: Invoking ‘aclocal’
 
 * aclocal Options::             Options supported by aclocal
 * Macro Search Path::           How aclocal finds .m4 files
 * Extending aclocal::           Writing your own aclocal macros
 * Local Macros::                Organizing local macros
 * Serials::                     Serial lines in Autoconf macros
-* Future of aclocal::           aclocal’s scheduled death
+* Future of aclocal::           aclocal's scheduled death
 
 Autoconf macros supplied with Automake
 
@@ -177,7 +175,7 @@
 * Fortran 9x Support::          Compiling Fortran 9x sources
 * Java Support with gcj::       Compiling Java sources using gcj
 * Vala Support::                Compiling Vala sources
-* Support for Other Languages::  Compiling other languages
+* Support for Other Languages:: Compiling other languages
 * Dependencies::                Automatic dependency tracking
 * EXEEXT::                      Support for executable extensions
 
@@ -198,11 +196,12 @@
 * Libtool Modules::             Building Libtool Modules
 * Libtool Flags::               Using _LIBADD, _LDFLAGS, and _LIBTOOLFLAGS
 * LTLIBOBJS::                   Using $(LTLIBOBJS) and $(LTALLOCA)
-* Libtool Issues::              Common Issues Related to Libtool’s Use
+* Libtool Issues::              Common Issues Related to Libtool's Use
 
-Common Issues Related to Libtool’s Use
+Common Issues Related to Libtool's Use
 
 * Error required file ltmain.sh not found::  The need to run libtoolize
+* Libtool library used but LIBTOOL is undefined::  test releases and libtoolize
 * Objects created both with libtool and without::  Avoid a specific build race
 
 Yacc and Lex support
@@ -242,10 +241,14 @@
 * Java::                        Java bytecode compilation (deprecated)
 * Python::                      Python
 
+Python
+
+* Supported Python versions::
+
 Building documentation
 
-* Texinfo::                     Texinfo
-* Man Pages::                   Man pages
+* Texinfo::
+* Man Pages::
 
 What Gets Installed
 
@@ -263,6 +266,15 @@
 * Checking the Distribution::   ‘make distcheck’ explained
 * The Types of Distributions::  A variety of formats and compression methods
 
+Checking the Distribution
+
+* DISTCHECK_CONFIGURE_FLAGS::  Overriding configure flags in distcheck.
+* distcheck-hook::             Running commands after distcheck.
+* dvi and distcheck::          Overriding the distcheck doc target.
+* distcleancheck::             Handling files not cleaned.
+* distuninstallcheck::         Overriding the uninstall check.
+* Errors with distclean::
+
 Support for test suites
 
 * Generalities about Testing::  Concepts and terminology about testing
@@ -298,10 +310,10 @@
 
 * Introduction to TAP::
 * Use TAP with the Automake test harness::
-* Incompatibilities with other TAP parsers and drivers::
+* Incompatibility with other TAP parsers and drivers::
 * Links and external resources on TAP::
 
-Changing Automake’s Behavior
+Changing Automake's Behavior
 
 * Options generalities::        Semantics of Automake option
 * List of Automake options::    A comprehensive list of Automake options
@@ -321,25 +333,25 @@
 * Make verbosity::              Make is verbose by default
 * Tricks For Silencing Make::   Standard and generic ways to silence make
 * Automake Silent Rules::       How Automake can help in silencing make
+* Unsilencing Automake::        Showing commands.
 
-When Automake Isn’t Enough
+When Automake Isn't Enough
 
 * Extending::                   Adding new rules or overriding existing ones.
 * Third-Party Makefiles::       Integrating Non-Automake ‘Makefile’s.
 
 Frequently Asked Questions about Automake
 
-* CVS::                         CVS and generated files
+* Version Control::             Version control and generated files
 * maintainer-mode::             missing and AM_MAINTAINER_MODE
-* Wildcards::                   Why doesn’t Automake support wildcards?
+* Wildcards::                   Why doesn't Automake support wildcards?
 * Limitations on File Names::   Limitations on source and installed file names
-* Errors with distclean::       Files left in build directory after distclean
 * Flag Variables Ordering::     CFLAGS vs. AM_CFLAGS vs. mumble_CFLAGS
 * Renamed Objects::             Why are object files sometimes renamed?
 * Per-Object Flags::            How to simulate per-object flags?
 * Multiple Outputs::            Writing rules for tools with many output files
 * Hard-Coded Install Paths::    Installing to hard-coded locations
-* Debugging Make Rules::        Strategies when things don’t work as expected
+* Debugging Make Rules::        Strategies when things don't work as expected
 * Reporting Bugs::              Feedback on bugs and feature requests
 
 Copying This Manual
@@ -389,7 +401,7 @@
 
    (1) These variables are also called “make macros” in Make
 terminology, however in this manual we reserve the term “macro” for
-Autoconf’s macros.
+Autoconf's macros.
 
 &#x1f;
 File: automake.info,  Node: Autotools Introduction,  Next: Generalities,  Prev: Introduction,  Up: Top
@@ -398,18 +410,18 @@
 **********************************
 
 If you are new to Automake, maybe you know that it is part of a set of
-tools called _The Autotools_.  Maybe you’ve already delved into a
+tools called _The Autotools_.  Maybe you've already delved into a
 package full of files named ‘configure’, ‘configure.ac’, ‘Makefile.in’,
 ‘Makefile.am’, ‘aclocal.m4’, ..., some of them claiming to be _generated
 by_ Autoconf or Automake.  But the exact purpose of these files and
 their relations is probably fuzzy.  The goal of this chapter is to
 introduce you to this machinery, to show you how it works and how
-powerful it is.  If you’ve never installed or seen such a package, do
+powerful it is.  If you've never installed or seen such a package, do
 not worry: this chapter will walk you through it.
 
    If you need some teaching material, more illustrations, or a less
 ‘automake’-centered continuation, some slides for this introduction are
-available in Alexandre Duret-Lutz’s Autotools Tutorial
+available in Alexandre Duret-Lutz's Autotools Tutorial
 (https://www.lrde.epita.fr/~adl/autotools.html).  This chapter is the
 written version of the first part of his tutorial.
 
@@ -554,7 +566,7 @@
 are constructed in place, in the source tree; we will see later how this
 can be changed.
 
-   ‘make check’ causes the package’s tests to be run.  This step is not
+   ‘make check’ causes the package's tests to be run.  This step is not
 mandatory, but it is often good to make sure the programs that have been
 built behave as they should, before you decide to install them.  Our
 example does not contain any tests, so running ‘make check’ is a no-op.
@@ -579,7 +591,7 @@
 tree.  Conversely, some packages are set up so that ‘make installcheck’
 will run the very same tests as ‘make check’, only on different files
 (non-installed vs. installed).  It can make a difference, for instance
-when the source tree’s layout is different from that of the
+when the source tree's layout is different from that of the
 installation.  Furthermore it may help to diagnose an incomplete
 installation.
 
@@ -607,7 +619,7 @@
      Build programs, libraries, documentation, etc. (same as ‘make’).
 ‘make install’
      Install what needs to be installed, copying the files from the
-     package’s tree to system-wide directories.
+     package's tree to system-wide directories.
 ‘make install-strip’
      Same as ‘make install’, then strip debugging symbols.  Some users
      like to trade space for useful bug reports...
@@ -856,7 +868,7 @@
 host.
 
    The GNU Build System also supports networked setups where part of the
-installed files should be shared amongst multiple hosts.  It does so by
+installed files should be shared among multiple hosts.  It does so by
 distinguishing architecture-dependent files from
 architecture-independent files, and providing two ‘Makefile’ targets to
 install each of these classes of files.
@@ -978,7 +990,7 @@
 especially convenient when installing a GNU package on a system that
 already has a proprietary implementation you do not want to overwrite.
 For instance, you may want to install GNU ‘tar’ as ‘gtar’ so you can
-distinguish it from your vendor’s ‘tar’.
+distinguish it from your vendor's ‘tar’.
 
    This can be done using one of these three ‘configure’ options.
 
@@ -1005,7 +1017,7 @@
 2.2.10 Building Binary Packages Using DESTDIR
 ---------------------------------------------
 
-The GNU Build System’s ‘make install’ and ‘make uninstall’ interface
+The GNU Build System's ‘make install’ and ‘make uninstall’ interface
 does not exactly fit the needs of a system administrator who has to
 deploy and upgrade packages on lots of hosts.  In other words, the GNU
 Build System does not replace a package manager.
@@ -1037,7 +1049,7 @@
      ./usr/share/doc/amhello/README
 
    After this example, ‘amhello-1.0-i686.tar.gz’ is ready to be
-uncompressed in ‘/’ on many hosts.  (Using ‘`cat ../files.lst`’ instead
+decompressed in ‘/’ on many hosts.  (Using ‘`cat ../files.lst`’ instead
 of ‘.’ as argument for ‘tar’ avoids entries for each subdirectory in the
 archive: we would not like ‘tar’ to restore the modification time of
 ‘/’, ‘/usr/’, etc.)
@@ -1149,7 +1161,7 @@
 2.2.13 Nested Packages
 ----------------------
 
-Although nesting packages isn’t something we would recommend to someone
+Although nesting packages isn't something we would recommend to someone
 who is discovering the Autotools, it is a nice feature worthy of mention
 in this small advertising tour.
 
@@ -1305,7 +1317,7 @@
 that ‘autoreconf’ created four other files: ‘configure’, ‘config.h.in’,
 ‘Makefile.in’, and ‘src/Makefile.in’.  The latter three files are
 templates that will be adapted to the system by ‘configure’ under the
-names ‘config.h’, ‘Makefile’, and ‘src/Makefile’.  Let’s do this:
+names ‘config.h’, ‘Makefile’, and ‘src/Makefile’.  Let's do this:
 
      ~/amhello % ./configure
      checking for a BSD-compatible install... /usr/bin/install -c
@@ -1347,25 +1359,36 @@
      amhello-1.0.tar.gz
      =============================================
 
-   Note that running ‘autoreconf’ is only needed initially when the GNU
-Build System does not exist.  When you later change some instructions in
-a ‘Makefile.am’ or ‘configure.ac’, the relevant part of the build system
+   Running ‘autoreconf’ is only needed initially, when the GNU Build
+System does not exist.  When you later change some instructions in a
+‘Makefile.am’ or ‘configure.ac’, the relevant part of the build system
 will be regenerated automatically when you execute ‘make’.
 
-   ‘autoreconf’ is a script that calls ‘autoconf’, ‘automake’, and a
-bunch of other commands in the right order.  If you are beginning with
-these tools, it is not important to figure out in which order all of
-these tools should be invoked and why.  However, because Autoconf and
-Automake have separate manuals, the important point to understand is
-that ‘autoconf’ is in charge of creating ‘configure’ from
-‘configure.ac’, while ‘automake’ is in charge of creating ‘Makefile.in’s
-from ‘Makefile.am’s and ‘configure.ac’.  This should at least direct you
-to the right manual when seeking answers.
+   ‘autoreconf’ is a script that calls ‘autoconf’, ‘automake’, and
+related commands in the right order.  If you are beginning with these
+tools, it is not important to figure out in which order all of these
+tools should be invoked and why.  (But for the curious: the basic idea
+is to run:
+
+  1. ‘aclocal’ (*note aclocal Invocation::),
+  2. ‘autoconf’ (*note (autoconf)::),
+  3. (if needed) ‘autoheader’ (part of the Autoconf distribution), and
+  4. ‘automake’ (*note automake Invocation::).
+
+If needed, tools related to Gettext (*note (gettext)::) and Libtool
+(*note (libtool)::) are also invoked at different points.  Thus, as you
+can see, using ‘autoreconf’ is quite a bit more convenient.
+
+   Nevertheless, because Autoconf and Automake have separate manuals, an
+essential idea to understand is that Autoconf is in charge of creating
+‘configure’ from ‘configure.ac’, while Automake is in charge of creating
+‘Makefile.in’s from ‘Makefile.am’s and ‘configure.ac’.  This should at
+least direct you to the right manual when seeking answers.
 
 &#x1f;
 File: automake.info,  Node: amhello's configure.ac Setup Explained,  Next: amhello's Makefile.am Setup Explained,  Prev: Creating amhello,  Up: Hello World
 
-2.4.2 ‘amhello’’s ‘configure.ac’ Setup Explained
+2.4.2 ‘amhello’'s ‘configure.ac’ Setup Explained
 ------------------------------------------------
 
 Let us begin with the contents of ‘configure.ac’.
@@ -1397,7 +1420,7 @@
 version number, and a contact address for bug-reports about the package
 (this address is output at the end of ‘./configure --help’, for
 instance).  When adapting this setup to your own package, by all means
-please do not blindly copy Automake’s address: use the mailing list of
+please do not blindly copy Automake's address: use the mailing list of
 your package, or your own mail address.
 
    The argument to ‘AM_INIT_AUTOMAKE’ is a list of options for
@@ -1460,7 +1483,7 @@
 &#x1f;
 File: automake.info,  Node: amhello's Makefile.am Setup Explained,  Prev: amhello's configure.ac Setup Explained,  Up: Hello World
 
-2.4.3 ‘amhello’’s ‘Makefile.am’ Setup Explained
+2.4.3 ‘amhello’'s ‘Makefile.am’ Setup Explained
 -----------------------------------------------
 
 We now turn to ‘src/Makefile.am’.  This file contains Automake
@@ -1583,11 +1606,12 @@
 variable definitions.
 
    Generally, Automake is not particularly smart in the parsing of
-unusual Makefile constructs, so you’re advised to avoid fancy constructs
-or “creative” use of whitespace.  For example, <TAB> characters cannot
-be used between a target name and the following “‘:’” character, and
-variable assignments shouldn’t be indented with <TAB> characters.  Also,
-using more complex macros in target names can cause trouble:
+unusual ‘Makefile’ constructs, so you're advised to avoid fancy
+constructs or "creative" use of whitespace.  For example, <TAB>
+characters cannot be used between a target name and the following "‘:’"
+character, and variable assignments shouldn't be indented with <TAB>
+characters.  Also, using more complex macros in target names can cause
+trouble:
 
      % cat Makefile.am
      $(FOO:=x): bar
@@ -1635,7 +1659,7 @@
 does make some effort to accommodate those who wish to use it, but do
 not want to use all the GNU conventions.
 
-   To this end, Automake supports three levels of “strictness”—how
+   To this end, Automake supports three levels of “strictness”--how
 stringently Automake should enforce conformance with GNU conventions.
 Each strictness level can be selected using an option of the same name;
 see *note Options::.
@@ -1671,7 +1695,7 @@
 
      Future versions of Automake may, at this level of strictness,
      require certain non-standard GNU tools to be available to
-     maintainer-only Makefile rules.  For instance, in the future
+     maintainer-only ‘Makefile’ rules.  For instance, in the future
      ‘pathchk’ (*note (coreutils)pathchk invocation::) may be required
      to run ‘make dist’.
 
@@ -1769,12 +1793,13 @@
 to override the check if you need to).  Automake will also diagnose
 obvious misspellings in directory names.
 
-   Sometimes the standard directories—even as augmented by Automake—are
-not enough.  In particular it is sometimes useful, for clarity, to
-install objects in a subdirectory of some predefined directory.  To this
-end, Automake allows you to extend the list of possible installation
-directories.  A given prefix (e.g., ‘zar’) is valid if a variable of the
-same name with ‘dir’ appended is defined (e.g., ‘zardir’).
+   Sometimes the standard directories--even as augmented by
+Automake--are not enough.  In particular it is sometimes useful, for
+clarity, to install objects in a subdirectory of some predefined
+directory.  To this end, Automake allows you to extend the list of
+possible installation directories.  A given prefix (e.g., ‘zar’) is
+valid if a variable of the same name with ‘dir’ appended is defined
+(e.g., ‘zardir’).
 
    For instance, the following snippet will install ‘file.xml’ into
 ‘$(datadir)/xml’.
@@ -1817,7 +1842,7 @@
 ‘TEXINFOS’.
 
    Some primaries also allow additional prefixes that control other
-aspects of ‘automake’’s behavior.  The currently defined prefixes are
+aspects of ‘automake’'s behavior.  The currently defined prefixes are
 ‘dist_’, ‘nodist_’, ‘nobase_’, and ‘notrans_’.  These prefixes are
 explained later (*note Program and Library Variables::) (*note Man
 Pages::).
@@ -1862,7 +1887,7 @@
 can happen with above ‘$(data_DATA)’ lists, it limits the amount of
 arguments passed to external commands.
 
-   Unfortunately, some systems’ ‘make’ commands may prepend ‘VPATH’
+   Unfortunately, some systems' ‘make’ commands may prepend ‘VPATH’
 prefixes like ‘${srcdir}/’ to file names from the source tree
 automatically (*note Automatic Rule Rewriting: (autoconf)Automatic Rule
 Rewriting.).  In this case, the user may have to switch to use GNU Make,
@@ -1903,7 +1928,7 @@
 ===================================
 
 Some ‘Makefile’ variables are reserved by the GNU Coding Standards for
-the use of the “user”—the person building the package.  For instance,
+the use of the "user"--the person building the package.  For instance,
 ‘CFLAGS’ is one such variable.
 
    Sometimes package developers are tempted to set user variables such
@@ -1917,10 +1942,10 @@
    To get around this problem, Automake introduces an automake-specific
 shadow variable for each user flag variable.  (Shadow variables are not
 introduced for variables like ‘CC’, where they would make no sense.)
-The shadow variable is named by prepending ‘AM_’ to the user variable’s
+The shadow variable is named by prepending ‘AM_’ to the user variable's
 name.  For instance, the shadow variable for ‘YFLAGS’ is ‘AM_YFLAGS’.
-The package maintainer—that is, the author(s) of the ‘Makefile.am’ and
-‘configure.ac’ files—may adjust these shadow variables however
+The package maintainer--that is, the author(s) of the ‘Makefile.am’ and
+‘configure.ac’ files--may adjust these shadow variables however
 necessary.
 
    *Note Flag Variables Ordering::, for more discussion about these
@@ -1981,7 +2006,7 @@
 
 ‘missing’
      This wraps a number of programs that are typically only required by
-     maintainers.  If the program in question doesn’t exist, or seems
+     maintainers.  If the program in question doesn't exist, or seems
      too old, ‘missing’ will print an informative warning before failing
      out, to provide the user with more context and information.
 
@@ -2044,8 +2069,8 @@
 4.1 A simple example, start to finish
 =====================================
 
-Let’s suppose you just finished writing ‘zardoz’, a program to make your
-head float from vortex to vortex.  You’ve been using Autoconf to provide
+Let's suppose you just finished writing ‘zardoz’, a program to make your
+head float from vortex to vortex.  You've been using Autoconf to provide
 a portability framework, but your ‘Makefile.in’s have been ad-hoc.  You
 want to make them bulletproof, so you turn to Automake.
 
@@ -2057,12 +2082,12 @@
      AM_INIT_AUTOMAKE
      ...
 
-   Since your program doesn’t have any complicating factors (e.g., it
-doesn’t use ‘gettext’, it doesn’t want to build a shared library),
-you’re done with this part.  That was easy!
+   Since your program doesn't have any complicating factors (e.g., it
+doesn't use ‘gettext’, it doesn't want to build a shared library),
+you're done with this part.  That was easy!
 
-   Now you must regenerate ‘configure’.  But to do that, you’ll need to
-tell ‘autoconf’ how to find the new macro you’ve used.  The easiest way
+   Now you must regenerate ‘configure’.  But to do that, you'll need to
+tell ‘autoconf’ how to find the new macro you've used.  The easiest way
 to do this is to use the ‘aclocal’ program to generate your ‘aclocal.m4’
 for you.  But wait... maybe you already have an ‘aclocal.m4’, because
 you had to write some hairy macros for your program.  The ‘aclocal’
@@ -2077,7 +2102,7 @@
 ‘zardoz’ is a user program, you want to install it where the rest of the
 user programs go: ‘bindir’.  Additionally, ‘zardoz’ has some Texinfo
 documentation.  Your ‘configure.ac’ script uses ‘AC_REPLACE_FUNCS’, so
-you need to link against ‘$(LIBOBJS)’.  So here’s what you’d write:
+you need to link against ‘$(LIBOBJS)’.  So here's what you'd write:
 
      bin_PROGRAMS = zardoz
      zardoz_SOURCES = main.c head.c float.c vortex9.c gun.c
@@ -2086,7 +2111,7 @@
      info_TEXINFOS = zardoz.texi
 
    Now you can run ‘automake --add-missing’ to generate your
-‘Makefile.in’ and grab any auxiliary files you might need, and you’re
+‘Makefile.in’ and grab any auxiliary files you might need, and you're
 done!
 
 &#x1f;
@@ -2116,14 +2141,14 @@
 ‘true’.  The ‘true.o: true.c’ rule supplied by the above ‘Makefile.am’,
 will override the Automake generated rule to build ‘true.o’.
 
-   ‘false_SOURCES’ is defined to be empty—that way no implicit value is
+   ‘false_SOURCES’ is defined to be empty--that way no implicit value is
 substituted.  Because we have not listed the source of ‘false’, we have
 to tell Automake how to link the program.  This is the purpose of the
 ‘false_LDADD’ line.  A ‘false_DEPENDENCIES’ variable, holding the
 dependencies of the ‘false’ target will be automatically generated by
 Automake from the content of ‘false_LDADD’.
 
-   The above rules won’t work if your compiler doesn’t accept both ‘-c’
+   The above rules won't work if your compiler doesn't accept both ‘-c’
 and ‘-o’.  The simplest fix for this is to introduce a bogus dependency
 (to avoid problems with a parallel ‘make’):
 
@@ -2134,7 +2159,7 @@
              $(COMPILE) -DEXIT_CODE=1 -c true.c && mv true.o false.o
 
    As it turns out, there is also a much easier way to do this same
-task.  Some of the above technique is useful enough that we’ve kept the
+task.  Some of the above technique is useful enough that we've kept the
 example in the manual.  However if you were to build ‘true’ and ‘false’
 in real life, you would probably use per-program compilation flags, like
 so:
@@ -2155,8 +2180,8 @@
 &#x1f;
 File: automake.info,  Node: automake Invocation,  Next: configure,  Prev: Examples,  Up: Top
 
-5 Creating a ‘Makefile.in’
-**************************
+5 Creating a ‘Makefile.in’: Invoking ‘automake’
+***********************************************
 
 To create all the ‘Makefile.in’s for a package, run the ‘automake’
 program in the top level directory, with no arguments.  ‘automake’ will
@@ -2166,7 +2191,7 @@
 what constitutes a package; it assumes that a package has only one
 ‘configure.ac’, at the top.  If your package has multiple
 ‘configure.ac’s, then you must run ‘automake’ in each directory holding
-a ‘configure.ac’.  (Alternatively, you may rely on Autoconf’s
+a ‘configure.ac’.  (Alternatively, you may rely on Autoconf's
 ‘autoreconf’, which is able to recurse your package tree and run
 ‘automake’ where appropriate.)
 
@@ -2184,9 +2209,9 @@
 dependencies (i.e., ‘aclocal.m4’ and any included file), therefore
 ‘autoconf’ must be in your ‘PATH’.  If there is an ‘AUTOCONF’ variable
 in your environment it will be used instead of ‘autoconf’; this allows
-you to select a particular version of Autoconf.  By the way, don’t
+you to select a particular version of Autoconf.  By the way, don't
 misunderstand this paragraph: ‘automake’ runs ‘autoconf’ to *scan* your
-‘configure.ac’; this won’t build ‘configure’ and you still have to run
+‘configure.ac’; this won't build ‘configure’ and you still have to run
 ‘autoconf’ yourself for this purpose.
 
    ‘automake’ accepts the following options:
@@ -2205,7 +2230,7 @@
 
      Many of the potentially-missing files are common scripts whose
      location may be specified via the ‘AC_CONFIG_AUX_DIR’ macro.
-     Therefore, ‘AC_CONFIG_AUX_DIR’’s setting affects whether a file is
+     Therefore, ‘AC_CONFIG_AUX_DIR’'s setting affects whether a file is
      considered missing, and where the missing file is added (*note
      Optional::).
 
@@ -2217,8 +2242,8 @@
      installation directory.  This is typically used for debugging.
 
      The environment variable ‘AUTOMAKE_LIBDIR’ provides another way to
-     set the directory containing Automake data files.  However
-     ‘--libdir’ takes precedence over it.
+     set the directory containing Automake data files.  The ‘--libdir’
+     option takes precedence over it.
 
 ‘--print-libdir’
      Print the path of the installation directory containing
@@ -2358,7 +2383,7 @@
 6 Scanning ‘configure.ac’, using ‘aclocal’
 ******************************************
 
-Automake scans the package’s ‘configure.ac’ to determine certain
+Automake scans the package's ‘configure.ac’ to determine certain
 information about the package.  Some ‘autoconf’ macros are required and
 some variables must be defined in ‘configure.ac’.  Automake will also
 use information from ‘configure.ac’ to further tailor its output.
@@ -2456,7 +2481,7 @@
      hold later when ‘configure’ is run, and it cannot use the shell
      variable ‘$file’ in a ‘Makefile’.  However, if you make reference
      to ‘$file’ as ‘${file}’ (i.e., in a way that is compatible with
-     ‘make’’s syntax) and furthermore use ‘AC_SUBST’ to ensure that
+     ‘make’'s syntax) and furthermore use ‘AC_SUBST’ to ensure that
      ‘${file}’ is meaningful in a ‘Makefile’, then ‘automake’ will be
      able to use ‘${file}’ to generate all of these rules.  For
      instance, here is how the Automake package itself generates
@@ -2535,7 +2560,7 @@
      corresponding to the current ‘Makefile.am’.  For the rest, the
      standard location is the first one of ‘.’, ‘..’, or ‘../..’
      (relative to the top source directory) that provides any one of the
-     helper scripts.  *Note Finding ‘configure’ Input: (autoconf)Input.
+     helper scripts.  *Note Finding 'configure' Input: (autoconf)Input.
 
      Required files from ‘AC_CONFIG_AUX_DIR’ are automatically
      distributed, even if there is no ‘Makefile.am’ in this directory.
@@ -2619,6 +2644,7 @@
      Particular Program Checks: (autoconf)Particular Programs.
 
 ‘AC_PROG_LIBTOOL’
+‘LT_INIT’
      Automake will turn on processing for ‘libtool’ (*note Introduction:
      (libtool)Top.).
 
@@ -2665,7 +2691,7 @@
 ‘AM_GNU_GETTEXT’
      This macro is required for packages that use GNU gettext (*note
      gettext::).  It is distributed with gettext.  If Automake sees this
-     macro it ensures that the package meets some of gettext’s
+     macro it ensures that the package meets some of gettext's
      requirements.
 
 ‘AM_GNU_GETTEXT_INTL_SUBDIR’
@@ -2676,7 +2702,7 @@
 ‘AM_MAINTAINER_MODE(DEFAULT-MODE)’
      This macro adds an ‘--enable-maintainer-mode’ option to
      ‘configure’.  If this is used, ‘automake’ will cause
-     “maintainer-only” rules to be turned off by default in the
+     "maintainer-only" rules to be turned off by default in the
      generated ‘Makefile.in’s, unless DEFAULT-MODE is ‘enable’.  This
      macro defines the ‘MAINTAINER_MODE’ conditional, which you can use
      in your own ‘Makefile.am’.  *Note maintainer-mode::.
@@ -2704,8 +2730,8 @@
 &#x1f;
 File: automake.info,  Node: aclocal Invocation,  Next: Macros,  Prev: Optional,  Up: configure
 
-6.3 Auto-generating aclocal.m4
-==============================
+6.3 Auto-generating aclocal.m4: Invoking ‘aclocal’
+==================================================
 
 Automake includes a number of Autoconf macros that can be used in your
 package (*note Macros::); some of them are required by Automake in
@@ -2732,27 +2758,34 @@
 by ‘aclocal’, use ‘##’ as the comment leader.
 
    When a file selected by ‘aclocal’ is located in a subdirectory
-specified as a relative search path with ‘aclocal’’s ‘-I’ argument,
+specified as a relative search path with ‘aclocal’'s ‘-I’ argument,
 ‘aclocal’ assumes the file belongs to the package and uses ‘m4_include’
 instead of copying it into ‘aclocal.m4’.  This makes the package
-smaller, eases dependency tracking, and cause the file to be distributed
-automatically.  (*Note Local Macros::, for an example.)  Any macro that
-is found in a system-wide directory or via an absolute search path will
-be copied.  So use ‘-I `pwd`/reldir’ instead of ‘-I reldir’ whenever
-some relative directory should be considered outside the package.
+smaller, eases dependency tracking, and causes the file to be
+distributed automatically.  (*Note Local Macros::, for an example.)  Any
+macro that is found in a system-wide directory or via an absolute search
+path will be copied.  So use ‘-I `pwd`/reldir’ instead of ‘-I reldir’
+whenever a relative directory should be considered to be outside the
+package.
 
    The contents of ‘acinclude.m4’, if this file exists, are also
-automatically included in ‘aclocal.m4’.  We recommend against using
-‘acinclude.m4’ in new packages (*note Local Macros::).
+automatically included in ‘aclocal.m4’.  We mostly recommend against
+using ‘acinclude.m4’ in new packages (*note Local Macros::).
 
    While computing ‘aclocal.m4’, ‘aclocal’ runs ‘autom4te’ (*note Using
 ‘Autom4te’: (autoconf)Using autom4te.) in order to trace the macros that
 are used, and omit from ‘aclocal.m4’ all macros that are mentioned but
 otherwise unexpanded (this can happen when a macro is called
-conditionally).  ‘autom4te’ is expected to be in the ‘PATH’, just as
+conditionally).  ‘autom4te’ is expected to be in the ‘PATH’, just like
 ‘autoconf’.  Its location can be overridden using the ‘AUTOM4TE’
 environment variable.
 
+   In practice it is usually simpler to run ‘autoreconf’ instead of
+worrying about the required order of the various tools (*note Using
+‘autoreconf’: (autoconf)autoreconf Invocation.).
+
+   This section explains the details of ‘aclocal’.
+
 * Menu:
 
 * aclocal Options::             Options supported by aclocal
@@ -2760,7 +2793,7 @@
 * Extending aclocal::           Writing your own aclocal macros
 * Local Macros::                Organizing local macros
 * Serials::                     Serial lines in Autoconf macros
-* Future of aclocal::           aclocal’s scheduled death
+* Future of aclocal::           aclocal's scheduled death
 
 &#x1f;
 File: automake.info,  Node: aclocal Options,  Next: Macro Search Path,  Up: aclocal Invocation
@@ -2771,12 +2804,25 @@
 ‘aclocal’ accepts the following options:
 
 ‘--automake-acdir=DIR’
-     Look for the automake-provided macro files in DIR instead of in the
+     Look for Automake-provided macro files in DIR instead of in the
      installation directory.  This is typically used for debugging.
 
-     The environment variable ‘ACLOCAL_AUTOMAKE_DIR’ provides another
-     way to set the directory containing automake-provided macro files.
-     However ‘--automake-acdir’ takes precedence over it.
+     If this option is not specified, the value of the environment
+     variable ‘ACLOCAL_AUTOMAKE_DIR’, if set, is used to set the
+     directory containing Automake-provided macro files.  Otherwise an
+     install-time default is used.
+
+‘--aclocal-path=PATH’
+     Look for local third-party macro files (and the special ‘dirlist’
+     file, *note dirlist::) along PATH (a colon-separated list of
+     directories) instead of in the installation directory.  (This can
+     be used for building against alternative system roots ("sysroots")
+     for finding headers and libraries.)
+
+     If this option is not specified, the value of the environment
+     variable ‘ACLOCAL_PATH’, if set, is used to set the search path
+     containing local third-party macro files.  Otherwise an
+     install-time default is used.
 
 ‘--system-acdir=DIR’
      Look for the system-wide third-party macro files (and the special
@@ -2793,7 +2839,7 @@
      ‘--install’.
 
 ‘--help’
-     Print a summary of the command line options and exit.
+     Print a summary of the command line options and exit successfully.
 
 ‘-I DIR’
      Add the directory DIR to the list of directories searched for ‘.m4’
@@ -2801,8 +2847,8 @@
 
 ‘--install’
      Install system-wide third-party macros into the first directory
-     specified with ‘-I DIR’ instead of copying them in the output file.
-     Note that this will happen also if DIR is an absolute path.
+     specified with ‘-I DIR’ instead of copying them into the output
+     file.  This is also done if DIR is an absolute path.
 
      When this option is used, and only when this option is used,
      ‘aclocal’ will also honor ‘#serial NUMBER’ lines that appear in
@@ -2816,44 +2862,44 @@
      one of its dependencies is younger.
 
      This option forces the update of ‘aclocal.m4’ (or the file
-     specified with ‘--output’ below) and only this file, it has
-     absolutely no influence on files that may need to be installed by
-     ‘--install’.
+     specified with ‘--output’ below) and only this file; it has no
+     influence on files that may need to be installed by ‘--install’.
 
 ‘--output=FILE’
      Cause the output to be put into FILE instead of ‘aclocal.m4’.
 
 ‘--print-ac-dir’
-     Prints the name of the directory that ‘aclocal’ will search to find
+     Print the name of the directory that ‘aclocal’ will search to find
      third-party ‘.m4’ files.  When this option is given, normal
      processing is suppressed.  This option was used _in the past_ by
      third-party packages to determine where to install ‘.m4’ macro
      files, but _this usage is today discouraged_, since it causes
-     ‘$(prefix)’ not to be thoroughly honored (which violates the GNU
-     Coding Standards), and similar semantics can be better obtained
-     with the ‘ACLOCAL_PATH’ environment variable; *note Extending
-     aclocal::.
+     ‘$(prefix)’ not to be thoroughly honored (violating the GNU Coding
+     Standards).  And similar semantics can be better obtained with the
+     ‘ACLOCAL_PATH’ environment variable (*note Extending aclocal::).
 
 ‘--verbose’
-     Print the names of the files it examines.
+     Print the names of files examined.
 
 ‘--version’
-     Print the version number of Automake and exit.
+     Print the version number of Automake and exit successfully.
 
 ‘-W CATEGORY’
 ‘--warnings=CATEGORY’
-     Output warnings falling in CATEGORY.  CATEGORY can be one of:
+     Output warnings falling in CATEGORY, one of:
      ‘syntax’
           dubious syntactic constructs, underquoted macros, unused
           macros, etc.
      ‘unsupported’
-          unknown macros
+          unknown macros.
      ‘all’
-          all the warnings, this is the default
+          all the warnings; this is the default.
      ‘none’
-          turn off all the warnings
+          turn off all the warnings.
+     ‘no-CATEGORY’
+          turn off warnings in CATEGORY.
      ‘error’
-          treat warnings as errors
+          treat warnings as errors.
 
      All warnings are output by default.
 
@@ -2876,33 +2922,32 @@
 
 ‘ACDIR’
      This directory is intended for third party ‘.m4’ files, and is
-     configured when ‘automake’ itself is built.  This is
+     configured when ‘automake’ itself is built.  It is
      ‘@datadir@/aclocal/’, which typically expands to
      ‘${prefix}/share/aclocal/’.  To find the compiled-in value of
      ACDIR, use the ‘--print-ac-dir’ option (*note aclocal Options::).
 
-   As an example, suppose that ‘automake-1.11.2’ was configured with
+   For example, suppose that Automake 1.11.2 was configured with
 ‘--prefix=/usr/local’.  Then, the search path would be:
 
   1. ‘/usr/local/share/aclocal-1.11.2/’
   2. ‘/usr/local/share/aclocal/’
 
    The paths for the ACDIR and ACDIR-APIVERSION directories can be
-changed respectively through aclocal options ‘--system-acdir’ and
-‘--automake-acdir’ (*note aclocal Options::).  Note however that these
-options are only intended for use by the internal Automake test suite,
-or for debugging under highly unusual situations; they are not
-ordinarily needed by end-users.
+changed respectively through the ‘aclocal’ options ‘--system-acdir’ and
+‘--automake-acdir’ (*note aclocal Options::).  These options are not
+ordinarily needed by end-users; they're mainly intended for use by the
+Automake test suite, or for debugging.
 
-   As explained in (*note aclocal Options::), there are several options
-that can be used to change or extend this search path.
+   As also listed in (*note aclocal Options::), several other options
+can be used to change or extend the macro search path.
 
 Modifying the Macro Search Path: ‘-I DIR’
 .........................................
 
-Any extra directories specified using ‘-I’ options (*note aclocal
-Options::) are _prepended_ to this search list.  Thus, ‘aclocal -I /foo
--I /bar’ results in the following search path:
+Any directories specified using ‘-I’ options (*note aclocal Options::)
+are _prepended_ to this search list.  Thus, ‘aclocal -I /foo -I /bar’
+results in the following search path:
 
   1. ‘/foo’
   2. ‘/bar’
@@ -2912,7 +2957,7 @@
 Modifying the Macro Search Path: ‘dirlist’
 ..........................................
 
-There is a third mechanism for customizing the search path.  If a
+There is a third mechanism for customizing the search path: if a
 ‘dirlist’ file exists in ACDIR, then that file is assumed to contain a
 list of directory patterns, one per line.  ‘aclocal’ expands these
 patterns to directory names, and adds them to the search list _after_
@@ -2934,75 +2979,77 @@
   4. ACDIR
   5. ‘/test1’
   6. ‘/test2’
-
-and all directories with path names starting with ‘/test3’.
+  7. all directories with path names starting with ‘/test3’.
 
    If the ‘--system-acdir=DIR’ option is used, then ‘aclocal’ will
-search for the ‘dirlist’ file in DIR; but remember the warnings above
-against the use of ‘--system-acdir’.
+search for the ‘dirlist’ file in that DIR.
 
-   ‘dirlist’ is useful in the following situation: suppose that
-‘automake’ version ‘1.11.2’ is installed with ‘--prefix=/usr’ by the
-system vendor.  Thus, the default search directories are
+   ‘dirlist’ is useful in the following situation: suppose that Automake
+1.11.2 is installed with ‘--prefix=/usr’ by the system vendor.  Thus,
+the default search directories are
 
   1. ‘/usr/share/aclocal-1.11/’
   2. ‘/usr/share/aclocal/’
 
    However, suppose further that many packages have been manually
-installed on the system, with $prefix=/usr/local, as is typical.  In
-that case, many of these “extra” ‘.m4’ files are in
-‘/usr/local/share/aclocal’.  The only way to force ‘/usr/bin/aclocal’ to
-find these “extra” ‘.m4’ files is to always call ‘aclocal -I
-/usr/local/share/aclocal’.  This is inconvenient.  With ‘dirlist’, one
-may create a file ‘/usr/share/aclocal/dirlist’ containing only the
-single line
+installed on the system, with ‘$prefix=/usr/local’, as is typical.  In
+that case, many of these "extra" ‘.m4’ files are in
+‘/usr/local/share/aclocal’.  Without ‘dirlist’, the only way to force
+‘/usr/bin/aclocal’ to find these "extra" ‘.m4’ files is to always call
+‘aclocal -I /usr/local/share/aclocal’.  This is inconvenient.  With
+‘dirlist’, one can create a file ‘/usr/share/aclocal/dirlist’ containing
+the single line
 
      /usr/local/share/aclocal
 
-   Now, the “default” search path on the affected system is
+   Now, the "default" search path on the affected system is
 
   1. ‘/usr/share/aclocal-1.11/’
   2. ‘/usr/share/aclocal/’
   3. ‘/usr/local/share/aclocal/’
 
-without the need for ‘-I’ options; ‘-I’ options can be reserved for
-project-specific needs (‘my-source-dir/m4/’), rather than using them to
-work around local system-dependent tool installation directories.
+This way, ‘-I’ options can be reserved for project-specific needs
+(‘my-source-dir/m4/’), rather than using them to work around local
+system-dependent tool installation directories.
 
    Similarly, ‘dirlist’ can be handy if you have installed a local copy
 of Automake in your account and want ‘aclocal’ to look for macros
 installed at other places on the system.
 
-Modifying the Macro Search Path: ‘ACLOCAL_PATH’
-...............................................
+Modifying the Macro Search Path: ‘--aclocal-path’/‘ACLOCAL_PATH’
+................................................................
 
-The fourth and last mechanism to customize the macro search path is also
-the simplest.  Any directory included in the colon-separated environment
-variable ‘ACLOCAL_PATH’ is added to the search path and takes precedence
-over system directories (including those found via ‘dirlist’), with the
-exception of the versioned directory ACDIR-APIVERSION (*note Macro
-Search Path::).  However, directories passed via ‘-I’ will take
-precedence over directories in ‘ACLOCAL_PATH’.
-
-   Also note that, if the ‘--install’ option is used, any ‘.m4’ file
-containing a required macro that is found in a directory listed in
-‘ACLOCAL_PATH’ will be installed locally.  In this case, serial numbers
-in ‘.m4’ are honored too, *note Serials::.
-
-   Conversely to ‘dirlist’, ‘ACLOCAL_PATH’ is useful if you are using a
-global copy of Automake and want ‘aclocal’ to look for macros somewhere
-under your home directory.
+The fourth and last mechanism to customize the macro search path: any
+directory included in the colon-separated path given to the
+‘--aclocal-path’ command-line option, or (if the option is not
+specified) in the ‘ACLOCAL_PATH’ environment variable, is added to the
+search path.  These directories take precedence over system directories,
+including those found via ‘dirlist’, with the exception of the versioned
+directory ACDIR-APIVERSION (*note Macro Search Path::).  However,
+directories passed via ‘-I’ will take precedence over directories in
+‘--aclocal-path’/‘ACLOCAL_PATH’.
+
+   If the ‘--install’ option is used, any ‘.m4’ file containing a
+required macro that is found in a directory listed in
+‘--aclocal-path’/‘ACLOCAL_PATH’ will be installed locally.  In this
+case, serial numbers in ‘.m4’ are honored too (*note Serials::).
+
+   ‘--aclocal-path’/‘ACLOCAL_PATH’ is useful if you are using a global
+copy of Automake and want ‘aclocal’ to look for macros somewhere under
+your home directory.  This is more or less the opposite of ‘dirlist’.
 
-Planned future incompatibilities
-................................
+Possible future incompatibility in ‘aclocal’
+............................................
 
 The order in which the directories in the macro search path are
-currently looked up is confusing and/or suboptimal in various aspects,
-and is probably going to be changed in the future Automake release.  In
-particular, directories in ‘ACLOCAL_PATH’ and ‘ACDIR’ might end up
-taking precedence over ‘ACDIR-APIVERSION’, and directories in
-‘ACDIR/dirlist’ might end up taking precedence over ‘ACDIR’.  _This is a
-possible future incompatibility!_
+currently looked up is confusing and/or suboptimal in various aspects.
+In particular, directories in ‘--aclocal-path’/‘ACLOCAL_PATH’ and
+‘ACDIR’ might end up taking precedence over ‘ACDIR-APIVERSION’, and
+directories in ‘ACDIR/dirlist’ might end up taking precedence over
+‘ACDIR’.  There are no definite plans to change the current behavior,
+but if bug reports show the need (so please report issues), the default
+might need to be changed, and the current behavior retained as an
+option.
 
 &#x1f;
 File: automake.info,  Node: Extending aclocal,  Next: Local Macros,  Prev: Macro Search Path,  Up: aclocal Invocation
@@ -3010,17 +3057,17 @@
 6.3.3 Writing your own aclocal macros
 -------------------------------------
 
-The ‘aclocal’ program doesn’t have any built-in knowledge of any macros,
-so it is easy to extend it with your own macros.
+The ‘aclocal’ program doesn't have built-in knowledge of any macros.
+You can extend it with your own macros.
 
-   This can be used by libraries that want to supply their own Autoconf
+   Libraries, for example, usually want to supply their own Autoconf
 macros for use by other programs.  For instance, the ‘gettext’ library
 supplies a macro ‘AM_GNU_GETTEXT’ that should be used by any package
 using ‘gettext’.  When the library is installed, it installs this macro
 so that ‘aclocal’ will find it.
 
-   A macro file’s name should end in ‘.m4’.  Such files should be
-installed in ‘$(datadir)/aclocal’.  This is as simple as writing:
+   A macro file's name should end in ‘.m4’.  Such files should be
+installed in ‘$(datadir)/aclocal’.  This can be done with:
 
      aclocaldir = $(datadir)/aclocal
      aclocal_DATA = mymacro.m4 myothermacro.m4
@@ -3028,29 +3075,29 @@
 Please do use ‘$(datadir)/aclocal’, and not something based on the
 result of ‘aclocal --print-ac-dir’ (*note Hard-Coded Install Paths::,
 for arguments).  It might also be helpful to suggest to the user to add
-the ‘$(datadir)/aclocal’ directory to his ‘ACLOCAL_PATH’ variable (*note
-ACLOCAL_PATH::) so that ‘aclocal’ will find the ‘.m4’ files installed by
-your package automatically.
+the ‘$(datadir)/aclocal’ directory to their ‘ACLOCAL_PATH’ variable
+(*note ACLOCAL_PATH::) so that ‘aclocal’ will find the ‘.m4’ files
+installed by your package automatically.
 
-   A file of macros should be a series of properly quoted ‘AC_DEFUN’’s
-(*note (autoconf)Macro Definitions::).  The ‘aclocal’ programs also
+   A file of macros should be a series of properly quoted ‘AC_DEFUN’'s
+(*note (autoconf)Macro Definitions::).  The ‘aclocal’ program also
 understands ‘AC_REQUIRE’ (*note (autoconf)Prerequisite Macros::), so it
 is safe to put each macro in a separate file.  Each file should have no
-side effects but macro definitions.  Especially, any call to ‘AC_PREREQ’
-should be done inside the defined macro, not at the beginning of the
-file.
+side effects except for defining the macro(s).  In particular, any call
+to ‘AC_PREREQ’ should be done inside the defined macro, not at the
+beginning of the file.
 
    Starting with Automake 1.8, ‘aclocal’ warns about all underquoted
 calls to ‘AC_DEFUN’.  We realize this annoys some people, because
 ‘aclocal’ was not so strict in the past and many third party macros are
 underquoted; and we have to apologize for this temporary inconvenience.
-The reason we have to be stricter is that a future implementation of
-‘aclocal’ (*note Future of aclocal::) will have to temporarily include
-all of these third party ‘.m4’ files, maybe several times, even
-including files that end up not being needed.  Doing so should alleviate
-many problems of the current implementation; however, it requires a
-stricter style from macro authors.  Hopefully it is easy to revise the
-existing macros.  For instance,
+The reason we have to be stricter is that a possible future
+implementation of ‘aclocal’ (*note Future of aclocal::) will have to
+temporarily include all of these third party ‘.m4’ files, maybe several
+times, even including files that end up not being needed.  Doing so
+should alleviate many problems of the current implementation; however,
+it requires a stricter style from macro authors.  Hopefully it is easy
+to revise the existing macros.  For instance,
 
      # bad style
      AC_PREREQ(2.68)
@@ -3069,18 +3116,18 @@
      AX_BAR
      )
 
-   Wrapping the ‘AC_PREREQ’ call inside the macro ensures that Autoconf
-2.68 will not be required if ‘AX_FOOBAR’ is not used.  Most importantly,
-quoting the first argument of ‘AC_DEFUN’ allows the macro to be
-redefined or included twice (otherwise this first argument would be
-expanded during the second definition).  For consistency we like to
-quote even arguments such as ‘2.68’ that do not require it.
+   Wrapping the ‘AC_PREREQ(2.68)’ call inside the macro ensures that
+the Autoconf 2.68 will not be a prerequisite if ‘AX_FOOBAR’ is not used.
+Most importantly, quoting the first argument of ‘AC_DEFUN’ allows the
+macro to be redefined or included twice (otherwise this first argument
+would be expanded during the second definition).  For consistency we
+like to quote even arguments such as ‘2.68’ that do not require it.
 
    If you have been directed here by the ‘aclocal’ diagnostic but are
 not the maintainer of the implicated macro, you will want to contact the
-maintainer of that macro.  Please make sure you have the latest version
-of the macro and that the problem hasn’t already been reported before
-doing so: people tend to work faster when they aren’t flooded by mails.
+maintainer of that macro.  Please try to make sure you have the latest
+version of the macro and that the problem hasn't already been reported
+before doing so.
 
    Another situation where ‘aclocal’ is commonly used is to manage
 macros that are used locally by the package; *note Local Macros::.
@@ -3100,19 +3147,19 @@
    The first possibility (the historical practice) is to list all your
 macros in ‘acinclude.m4’.  This file will be included in ‘aclocal.m4’
 when you run ‘aclocal’, and its macro(s) will henceforth be visible to
-‘autoconf’.  However if it contains numerous macros, it will rapidly
+‘autoconf’.  However, if it contains numerous macros, it will rapidly
 become difficult to maintain, and it will be almost impossible to share
 macros between packages.
 
-   The second possibility, which we do recommend, is to write each macro
-in its own file and gather all these files in a directory.  This
-directory is usually called ‘m4/’.  Then it’s enough to update
-‘configure.ac’ by adding a proper call to ‘AC_CONFIG_MACRO_DIRS’:
+   The second possibility, which we recommend, is to write each macro in
+its own file and gather all these files in a directory.  This directory
+is usually called ‘m4/’.  Then you can update ‘configure.ac’ by adding a
+proper call to ‘AC_CONFIG_MACRO_DIRS’:
 
      AC_CONFIG_MACRO_DIRS(m4)
 
    ‘aclocal’ will then take care of automatically adding ‘m4/’ to its
-search path for m4 files.
+search path for M4 files.
 
    When ‘aclocal’ is run, it will build an ‘aclocal.m4’ that
 ‘m4_include’s any file from ‘m4/’ that defines a required macro.  Macros
@@ -3124,21 +3171,21 @@
 package if they want to work on it.  In fact, this distribution happens
 automatically because all ‘m4_include’d files are distributed.
 
-   However there is no consensus on the distribution of third-party
-macros that your package may use.  Many libraries install their own
-macro in the system-wide ‘aclocal’ directory (*note Extending
-aclocal::).  For instance, Guile ships with a file called ‘guile.m4’
-that contains the macro ‘GUILE_FLAGS’ that can be used to define setup
-compiler and linker flags appropriate for using Guile.  Using
-‘GUILE_FLAGS’ in ‘configure.ac’ will cause ‘aclocal’ to copy ‘guile.m4’
-into ‘aclocal.m4’, but as ‘guile.m4’ is not part of the project, it will
-not be distributed.  Technically, that means a user who needs to rebuild
-‘aclocal.m4’ will have to install Guile first.  This is probably OK, if
-Guile already is a requirement to build the package.  However, if Guile
-is only an optional feature, or if your package might run on
-architectures where Guile cannot be installed, this requirement will
-hinder development.  An easy solution is to copy such third-party macros
-in your local ‘m4/’ directory so they get distributed.
+   There is no consensus on the distribution of third-party macros that
+your package may use.  Many libraries install their own macro in the
+system-wide ‘aclocal’ directory (*note Extending aclocal::).  For
+instance, Guile ships with a file called ‘guile.m4’ that contains the
+macro ‘GUILE_FLAGS’ that can be used to define compiler and linker flags
+appropriate for using Guile.  Using ‘GUILE_FLAGS’ in ‘configure.ac’ will
+cause ‘aclocal’ to copy ‘guile.m4’ into ‘aclocal.m4’, but as ‘guile.m4’
+is not part of the project, it will not be distributed.  Technically,
+that means a user who needs to rebuild ‘aclocal.m4’ will have to install
+Guile first.  This is probably OK, if Guile already is a requirement to
+build the package.  However, if Guile is only an optional feature, or if
+your package might run on architectures where Guile cannot be installed,
+this requirement will hinder development.  An easy solution is to copy
+such third-party macros in your local ‘m4/’ directory so they get
+distributed.
 
    Since Automake 1.10, ‘aclocal’ offers the option ‘--install’ to copy
 these system-wide third-party macros in your local macro directory,
@@ -3154,15 +3201,9 @@
 new macro, this macro will be installed in your ‘m4/’ automatically.
 Another one is that serial numbers (*note Serials::) can be used to
 update the macros in your source tree automatically when new system-wide
-versions are installed.  A serial number should be a single line of the
-form
-
-     #serial NNN
-
-where NNN contains only digits and dots.  It should appear in the M4
-file before any macro definition.  It is a good practice to maintain a
-serial number for each macro you distribute, even if you do not use the
-‘--install’ option of ‘aclocal’: this allows other people to use it.
+versions are installed.  It is good practice to maintain a serial number
+for each macro you distribute, even if you do not use the ‘--install’
+option of ‘aclocal’: this allows other people to use it.
 
 &#x1f;
 File: automake.info,  Node: Serials,  Next: Future of aclocal,  Prev: Local Macros,  Up: aclocal Invocation
@@ -3171,17 +3212,17 @@
 --------------------
 
 Because third-party macros defined in ‘*.m4’ files are naturally shared
-between multiple projects, some people like to version them.  This makes
-it easier to tell which of two M4 files is newer.  Since at least 1996,
-the tradition is to use a ‘#serial’ line for this.
+between multiple projects, people like to version them.  This makes it
+easier to tell which of two M4 files is newer.  Since at least 1996, the
+convention is to use a ‘#serial’ line for this.
 
-   A serial number should be a single line of the form
+   Such a serial number should be a single line of the form
 
      # serial VERSION
 
 where VERSION is a version number containing only digits and dots.
 Usually people use a single integer, and they increment it each time
-they change the macro (hence the name of “serial”).  Such a line should
+they change the macro (hence the name of "serial").  Such a line should
 appear in the M4 file before any macro definition.
 
    The ‘#’ must be the first character on the line, and it is OK to have
@@ -3190,19 +3231,22 @@
      #serial VERSION GARBAGE
 
    Normally these serial numbers are completely ignored by ‘aclocal’ and
-‘autoconf’, like any genuine comment.  However when using ‘aclocal’’s
+‘autoconf’, like any genuine comment.  However when using ‘aclocal’'s
 ‘--install’ feature, these serial numbers will modify the way ‘aclocal’
 selects the macros to install in the package: if two files with the same
 basename exist in your search path, and if at least one of them uses a
 ‘#serial’ line, ‘aclocal’ will ignore the file that has the older
 ‘#serial’ line (or the file that has none).
 
-   Note that a serial number applies to a whole M4 file, not to any
-macro it contains.  A file can contain multiple macros, but only one
-serial.
+   A serial number applies to a whole M4 file, not to any macro it
+contains.  A file can contain multiple macros, but only one serial
+number.
+
+Serial Number Example
+.....................
 
-   Here is a use case that illustrates the use of ‘--install’ and its
-interaction with serial numbers.  Let’s assume we maintain a package
+Here is a use case that illustrates the use of ‘--install’ and its
+interaction with serial numbers.  Let's assume we maintain a package
 called MyPackage, the ‘configure.ac’ of which requires a third-party
 macro ‘AX_THIRD_PARTY’ defined in ‘/usr/share/aclocal/thirdparty.m4’ as
 follows:
@@ -3248,7 +3292,7 @@
 system-wide file in case of equal serial numbers.
 
    Now suppose the system-wide third-party macro is changed.  This can
-happen if the package installing this macro is updated.  Let’s suppose
+happen if the package installing this macro is updated.  Let's suppose
 the new macro has serial number 2.  The next time ‘aclocal --install’ is
 run the situation is the following:
 
@@ -3271,12 +3315,12 @@
 can run ‘aclocal --diff’ to review the changes ‘aclocal --install’ would
 perform on these macros.
 
-   Finally, note that the ‘--force’ option of ‘aclocal’ has absolutely
-no effect on the files installed by ‘--install’.  For instance, if you
-have modified your local macros, do not expect ‘--install --force’ to
-replace the local macros by their system-wide versions.  If you want to
-do so, simply erase the local macros you want to revert, and run
-‘aclocal --install’.
+   Finally, note that the ‘--force’ option of ‘aclocal’ has no effect on
+the files installed by ‘--install’.  For instance, if you have modified
+your local macros, do not expect ‘--install --force’ to replace the
+local macros by their system-wide versions.  If you want to do so,
+simply erase the local macros you want to revert, and run ‘aclocal
+--install’.
 
 &#x1f;
 File: automake.info,  Node: Future of aclocal,  Prev: Serials,  Up: aclocal Invocation
@@ -3286,42 +3330,40 @@
 
 Ideally, ‘aclocal’ should not be part of Automake.  Automake should
 focus on generating ‘Makefile’s; dealing with M4 macros is more
-Autoconf’s job.  The fact that some people install Automake just to use
-‘aclocal’, but do not use ‘automake’ otherwise is an indication of how
+Autoconf's job.  The fact that some people install Automake just to use
+‘aclocal’, but do not use Automake otherwise, is an indication of how
 that feature is misplaced.
 
-   The new implementation will probably be done slightly differently.
+   A new implementation would probably be done slightly differently.
 For instance, it could enforce the ‘m4/’-style layout discussed in *note
 Local Macros::.
 
-   We have no idea when and how this will happen.  This has been
-discussed several times in the past, but someone still has to commit to
-that non-trivial task.
-
-   From the user point of view, ‘aclocal’’s removal might turn out to be
-painful.  There is a simple precaution that you may take to make that
-switch more seamless: never call ‘aclocal’ yourself.  Keep this guy
-under the exclusive control of ‘autoreconf’ and Automake’s rebuild
-rules.  Hopefully you won’t need to worry about things breaking; when
-‘aclocal’ disappears, because everything will have been taken care of.
-If otherwise you used to call ‘aclocal’ directly yourself or from some
-script, you will quickly notice the change.
-
-   Many packages come with a script called ‘bootstrap’ or ‘autogen.sh’,
-that will just call ‘aclocal’, ‘libtoolize’, ‘gettextize’ or
-‘autopoint’, ‘autoconf’, ‘autoheader’, and ‘automake’ in the right
-order.  In fact, this is precisely what ‘autoreconf’ can do for you.  If
-your package has such a ‘bootstrap’ or ‘autogen.sh’ script, consider
-using ‘autoreconf’.  That should simplify its logic a lot (less things
-to maintain, all to the good), it’s even likely you will not need the
-script anymore, and more to the point you will not call ‘aclocal’
-directly anymore.
+   We do not know when or whether this will happen.  It has been
+discussed several times, but someone still has to commit to executing
+this non-trivial task.
+
+   From the user's point of view, ‘aclocal’'s removal might turn out to
+be painful.  There is a simple precaution that you may take to make that
+switch more seamless: never call ‘aclocal’ yourself.  Keep its
+invocation under the exclusive control of ‘autoreconf’ and Automake's
+rebuild rules.  Hopefully you won't need to worry about things breaking;
+when ‘aclocal’ disappears, because everything will have been taken care
+of.  If otherwise you used to call ‘aclocal’ directly yourself or from
+some script, you will quickly notice the change.
+
+   Many packages come with a script called ‘bootstrap’ or ‘autogen.sh’
+that calls ‘aclocal’, ‘libtoolize’, ‘gettextize’ or ‘autopoint’,
+‘autoconf’, ‘autoheader’, and ‘automake’ in the right order.  In fact,
+this is precisely what ‘autoreconf’ can do for you.  If your package has
+such a ‘bootstrap’ or ‘autogen.sh’ script, consider using ‘autoreconf’.
+That should simplify its logic (all to the good), and more to the point
+you will not call ‘aclocal’ directly anymore.
 
    For the time being, third-party packages should continue to install
 public macros into ‘/usr/share/aclocal/’.  If ‘aclocal’ is replaced by
 another tool it might make sense to rename the directory, but supporting
-‘/usr/share/aclocal/’ for backward compatibility should be easy provided
-all macros are properly written (*note Extending aclocal::).
+‘/usr/share/aclocal/’ for backward compatibility should be feasible,
+provided all macros are properly written (*note Extending aclocal::).
 
 &#x1f;
 File: automake.info,  Node: Macros,  Prev: aclocal Invocation,  Up: configure
@@ -3358,9 +3400,9 @@
      ‘AM_INIT_AUTOMAKE(PACKAGE, VERSION, NO-DEFINE)’.  In this form,
      there are two required arguments: the package and the version
      number.  This usage is mostly obsolete because the PACKAGE and
-     VERSION can be obtained from Autoconf’s ‘AC_INIT’ macro.  However,
+     VERSION can be obtained from Autoconf's ‘AC_INIT’ macro.  However,
      differently from what happens for ‘AC_INIT’ invocations, this
-     ‘AM_INIT_AUTOMAKE’ invocation supports shell variables’ expansions
+     ‘AM_INIT_AUTOMAKE’ invocation supports shell variables' expansions
      in the ‘PACKAGE’ and ‘VERSION’ arguments (which otherwise defaults,
      respectively, to the ‘PACKAGE_TARNAME’ and ‘PACKAGE_VERSION’
      defined via the ‘AC_INIT’ invocation; *note The ‘AC_INIT’ macro:
@@ -3381,7 +3423,7 @@
           AC_CONFIG_SRCDIR(src/foo.c)
           AM_INIT_AUTOMAKE
 
-     Note that if you’re upgrading your ‘configure.ac’ from an earlier
+     Note that if you're upgrading your ‘configure.ac’ from an earlier
      version of Automake, it is not always correct to simply move the
      package and version arguments from ‘AM_INIT_AUTOMAKE’ directly to
      ‘AC_INIT’, as in the example above.  The first argument to
@@ -3389,18 +3431,18 @@
      Automake’), not the tarball name (e.g., ‘automake’) that you used
      to pass to ‘AM_INIT_AUTOMAKE’.  Autoconf tries to derive a tarball
      name from the package name, which should work for most but not all
-     package names.  (If it doesn’t work for yours, you can use the
+     package names.  (If it doesn't work for yours, you can use the
      four-argument form of ‘AC_INIT’ to provide the tarball name
      explicitly).
 
-     By default this macro ‘AC_DEFINE’’s ‘PACKAGE’ and ‘VERSION’.  This
+     By default this macro ‘AC_DEFINE’'s ‘PACKAGE’ and ‘VERSION’.  This
      can be avoided by passing the ‘no-define’ option (*note List of
      Automake options::):
           AM_INIT_AUTOMAKE(no-define ...)
 
 ‘AM_PATH_LISPDIR’
      Searches for the program ‘emacs’, and, if found, sets the output
-     variable ‘lispdir’ to the full path to Emacs’ site-lisp directory.
+     variable ‘lispdir’ to the full path to Emacs' site-lisp directory.
 
      Note that this test assumes the ‘emacs’ found to be a version that
      supports Emacs Lisp (such as GNU Emacs or XEmacs).  Other emacsen
@@ -3408,9 +3450,9 @@
      start up in interactive mode, requiring ‘C-x C-c’ to exit, which is
      hardly obvious for a non-emacs user).  In most cases, however, you
      should be able to use ‘C-c’ to kill the test.  In order to avoid
-     problems, you can set ‘EMACS’ to “no” in the environment, or use
+     problems, you can set ‘EMACS’ to "no" in the environment, or use
      the ‘--with-lispdir’ option to ‘configure’ to explicitly set the
-     correct path (if you’re sure you have an ‘emacs’ that supports
+     correct path (if you're sure you have an ‘emacs’ that supports
      Emacs Lisp).
 
 ‘AM_PROG_AR(ACT-IF-FAIL)’
@@ -3432,10 +3474,11 @@
      checks itself, and thus the explicit use of ‘AM_PROG_CC_C_O’ should
      no longer be required.
 
-‘AM_PROG_LEX’
+‘AM_PROG_LEX(OPTIONS)’
      Like ‘AC_PROG_LEX’ (*note Particular Program Checks:
      (autoconf)Particular Programs.), but uses the ‘missing’ script on
      systems that do not have ‘lex’.  HP-UX 10 is one such system.
+     OPTIONS are passed directly to ‘AC_PROG_LEX’.
 
 ‘AM_PROG_GCJ’
      This macro finds the ‘gcj’ program or causes an error.  It sets
@@ -3510,12 +3553,12 @@
 ‘AM_SET_DEPDIR’
 ‘AM_DEP_TRACK’
 ‘AM_OUTPUT_DEPENDENCY_COMMANDS’
-     These macros are used to implement Automake’s automatic dependency
+     These macros are used to implement Automake's automatic dependency
      tracking scheme.  They are called automatically by Automake when
      required, and there should be no need to invoke them manually.
 
 ‘AM_MAKE_INCLUDE’
-     This macro is used to discover how the user’s ‘make’ handles
+     This macro is used to discover how the user's ‘make’ handles
      ‘include’ statements.  This macro is automatically invoked when
      needed; there should be no need to invoke it manually.
 
@@ -3542,7 +3585,7 @@
 
    In larger projects, it is common to organize files in different
 directories, in a tree.  For example, there could be a directory for the
-program’s source, one for the testsuite, and one for the documentation;
+program's source, one for the testsuite, and one for the documentation;
 or, for very large projects, there could be one directory per program,
 per library or per module.
 
@@ -3550,11 +3593,11 @@
 recursively, employing _make recursion_: each directory contains its own
 ‘Makefile’, and when ‘make’ is run from the top-level directory, it
 enters each subdirectory in turn, and invokes there a new ‘make’
-instance to build the directory’s contents.
+instance to build the directory's contents.
 
    Because this approach is very widespread, Automake offers built-in
 support for it.  However, it is worth noting that the use of make
-recursion has its own serious issues and drawbacks, and that it’s well
+recursion has its own serious issues and drawbacks, and that it's well
 possible to have packages with a multi directory layout that make little
 or no use of such recursion (examples of such packages are GNU Bison and
 GNU Automake itself); see also the *note Alternative:: section below.
@@ -3620,7 +3663,7 @@
    In addition to the built-in recursive targets defined by Automake
 (‘all’, ‘check’, etc.), the developer can also define his own recursive
 targets.  That is done by passing the names of such targets as arguments
-to the m4 macro ‘AM_EXTRA_RECURSIVE_TARGETS’ in ‘configure.ac’.
+to the M4 macro ‘AM_EXTRA_RECURSIVE_TARGETS’ in ‘configure.ac’.
 Automake generates rules to handle the recursion for such targets; and
 the developer can define real actions for them by defining corresponding
 ‘-local’ targets.
@@ -3653,7 +3696,7 @@
 in the case of GNU Inetutils, you want to only build a subset of the
 entire package.
 
-   To illustrate how this works, let’s assume we have two directories,
+   To illustrate how this works, let's assume we have two directories,
 ‘src/’ and ‘opt/’.  ‘src/’ should always be built, but we want to decide
 in ‘configure’ whether ‘opt/’ will be built or not.  (For this example
 we will assume that ‘opt/’ should be built when the variable ‘$want_opt’
@@ -3671,7 +3714,7 @@
 Automake conditionals (*note Conditionals::) or use Autoconf ‘AC_SUBST’
 variables (*note Setting Output Variables: (autoconf)Setting Output
 Variables.).  Using Automake conditionals is the preferred solution.
-Before we illustrate these two possibilities, let’s introduce
+Before we illustrate these two possibilities, let's introduce
 ‘DIST_SUBDIRS’.
 
 * Menu:
@@ -3740,8 +3783,8 @@
    As you can see, running ‘make’ will rightly recurse into ‘src/’ and
 maybe ‘opt/’.
 
-   As you can’t see, running ‘make dist’ will recurse into both ‘src/’
-and ‘opt/’ directories because ‘make dist’, unlike ‘make all’, doesn’t
+   As you can't see, running ‘make dist’ will recurse into both ‘src/’
+and ‘opt/’ directories because ‘make dist’, unlike ‘make all’, doesn't
 use the ‘SUBDIRS’ variable.  It uses the ‘DIST_SUBDIRS’ variable.
 
    In this case Automake will define ‘DIST_SUBDIRS = src opt’
@@ -3847,10 +3890,10 @@
 7.3 An Alternative Approach to Subdirectories
 =============================================
 
-If you’ve ever read Peter Miller’s excellent paper, ‘Recursive Make
+If you've ever read Peter Miller's excellent paper, ‘Recursive Make
 Considered Harmful’, the preceding sections on the use of make recursion
-will probably come as unwelcome advice.  For those who haven’t read the
-paper, Miller’s main thesis is that recursive ‘make’ invocations are
+will probably come as unwelcome advice.  For those who haven't read the
+paper, Miller's main thesis is that recursive ‘make’ invocations are
 both slow and error-prone.
 
    Automake is intended to have sufficient cross-directory support to
@@ -3904,15 +3947,15 @@
 
    These other packages should just appear as subdirectories of their
 parent package.  They must be listed in ‘SUBDIRS’ like other ordinary
-directories.  However the subpackage’s ‘Makefile’s should be output by
-its own ‘configure’ script, not by the parent’s ‘configure’.  This is
+directories.  However the subpackage's ‘Makefile’s should be output by
+its own ‘configure’ script, not by the parent's ‘configure’.  This is
 achieved using the ‘AC_CONFIG_SUBDIRS’ Autoconf macro (*note
 AC_CONFIG_SUBDIRS: (autoconf)Subdirectories.).
 
    Here is an example package for an ‘arm’ program that links with a
 ‘hand’ library that is a nested package in subdirectory ‘hand/’.
 
-   ‘arm’’s ‘configure.ac’:
+   ‘arm’'s ‘configure.ac’:
 
      AC_INIT(arm, 1.0)
      AC_CONFIG_AUX_DIR(.)
@@ -3923,7 +3966,7 @@
      AC_CONFIG_SUBDIRS(hand)
      AC_OUTPUT
 
-   ‘arm’’s ‘Makefile.am’:
+   ‘arm’'s ‘Makefile.am’:
 
      # Build the library in the hand subdirectory first.
      SUBDIRS = hand
@@ -3936,7 +3979,7 @@
      # link with the hand library.
      arm_LDADD = hand/libhand.a
 
-   Now here is ‘hand’’s ‘hand/configure.ac’:
+   Now here is ‘hand’'s ‘hand/configure.ac’:
 
      AC_INIT(hand, 1.2)
      AC_CONFIG_AUX_DIR(.)
@@ -3986,7 +4029,7 @@
 8 Building Programs and Libraries
 *********************************
 
-A large part of Automake’s functionality is dedicated to making it easy
+A large part of Automake's functionality is dedicated to making it easy
 to build programs and libraries.
 
 * Menu:
@@ -4055,7 +4098,7 @@
    Associated with each program are several assisting variables that are
 named after the program.  These variables are all optional, and have
 reasonable defaults.  Each variable, its use, and default is spelled out
-below; we use the “hello” example throughout.
+below; we use the "hello" example throughout.
 
    The variable ‘hello_SOURCES’ is used to specify which source files
 get built into an executable:
@@ -4073,7 +4116,7 @@
 ‘_SOURCES’ definition.
 
    Header files listed in a ‘_SOURCES’ definition will be included in
-the distribution but otherwise ignored.  In case it isn’t obvious, you
+the distribution but otherwise ignored.  In case it isn't obvious, you
 should not include the header file generated by ‘configure’ in a
 ‘_SOURCES’ variable; this file should not be distributed.  Lex (‘.l’)
 and Yacc (‘.y’) files can also be listed; see *note Yacc and Lex::.
@@ -4100,7 +4143,7 @@
    For instance, in GNU cpio, ‘pax’, ‘cpio’ and ‘mt’ are linked against
 the library ‘libcpio.a’.  However, ‘rmt’ is built in the same directory,
 and has no such link requirement.  Also, ‘mt’ and ‘rmt’ are only built
-on certain architectures.  Here is what cpio’s ‘src/Makefile.am’ looks
+on certain architectures.  Here is what cpio's ‘src/Makefile.am’ looks
 like (abridged):
 
      bin_PROGRAMS = cpio pax $(MT)
@@ -4161,10 +4204,10 @@
 8.1.3 Conditional compilation of sources
 ----------------------------------------
 
-You can’t put a configure substitution (e.g., ‘@FOO@’ or ‘$(FOO)’ where
+You can't put a configure substitution (e.g., ‘@FOO@’ or ‘$(FOO)’ where
 ‘FOO’ is defined via ‘AC_SUBST’) into a ‘_SOURCES’ variable.  The reason
 for this is a bit hard to explain, but suffice to say that it simply
-won’t work.  Automake will give an error if you try to do this.
+won't work.  Automake will give an error if you try to do this.
 
    Fortunately there are two other ways to achieve the same result.  One
 is to use configure substitutions in ‘_LDADD’ variables, the other is to
@@ -4219,7 +4262,7 @@
    In this case, ‘configure.ac’ should set up the ‘LINUX’ conditional
 using ‘AM_CONDITIONAL’ (*note Conditionals::).
 
-   When using conditionals like this you don’t need to use the ‘EXTRA_’
+   When using conditionals like this you don't need to use the ‘EXTRA_’
 variable, because Automake will examine the contents of each variable to
 construct the complete list of source files.
 
@@ -4270,7 +4313,7 @@
 ................................................
 
 You can also use Automake conditionals (*note Conditionals::) to select
-programs to be built.  In this case you don’t have to worry about
+programs to be built.  In this case you don't have to worry about
 ‘$(EXEEXT)’ or ‘EXTRA_PROGRAMS’.
 
      bin_PROGRAMS = cpio pax
@@ -4292,7 +4335,7 @@
 ‘libdir’ or ‘pkglibdir’.
 
    *Note A Shared Library::, for information on how to build shared
-libraries using libtool and the ‘LTLIBRARIES’ primary.
+libraries using Libtool and the ‘LTLIBRARIES’ primary.
 
    Each ‘_LIBRARIES’ variable is a list of the libraries to be built.
 For instance, to create a library named ‘libcpio.a’, but not install it,
@@ -4323,11 +4366,10 @@
 You should call ‘AC_PROG_RANLIB’ from your ‘configure.ac’ to define
 ‘RANLIB’ (Automake will complain otherwise).  You should also call
 ‘AM_PROG_AR’ to define ‘AR’, in order to support unusual archivers such
-as Microsoft lib.  ‘ARFLAGS’ will default to ‘cru’; you can override
-this variable by setting it in your ‘Makefile.am’ or by ‘AC_SUBST’ing it
-from your ‘configure.ac’.  You can override the ‘AR’ variable by
-defining a per-library ‘maude_AR’ variable (*note Program and Library
-Variables::).
+as Microsoft lib.  ‘ARFLAGS’ will default to ‘cr’; you can override this
+variable by setting it in your ‘Makefile.am’ or by ‘AC_SUBST’ing it from
+your ‘configure.ac’.  You can override the ‘AR’ variable by defining a
+per-library ‘maude_AR’ variable (*note Program and Library Variables::).
 
    Be careful when selecting library components conditionally.  Because
 building an empty library is not portable, you should ensure that any
@@ -4364,7 +4406,7 @@
 * Libtool Modules::             Building Libtool Modules
 * Libtool Flags::               Using _LIBADD, _LDFLAGS, and _LIBTOOLFLAGS
 * LTLIBOBJS::                   Using $(LTLIBOBJS) and $(LTALLOCA)
-* Libtool Issues::              Common Issues Related to Libtool’s Use
+* Libtool Issues::              Common Issues Related to Libtool's Use
 
 &#x1f;
 File: automake.info,  Node: Libtool Concept,  Next: Libtool Libraries,  Up: A Shared Library
@@ -4378,32 +4420,31 @@
 library, or maybe both.  Their exact nature cannot be determined until
 ‘./configure’ is run: not all platforms support all kinds of libraries,
 and users can explicitly select which libraries should be built.
-(However the package’s maintainers can tune the default; *note The
+(However the package's maintainers can tune the default; *note The
 ‘LT_INIT’ macro: (libtool)LT_INIT.)
 
    Because object files for shared and static libraries must be compiled
-differently, libtool is also used during compilation.  Object files
-built by libtool are called “libtool objects”: these are files using the
+differently, Libtool is also used during compilation.  Object files
+built by Libtool are called “libtool objects”: these are files using the
 ‘.lo’ suffix.  Libtool libraries are built from these libtool objects.
 
    You should not assume anything about the structure of ‘.la’ or ‘.lo’
-files and how libtool constructs them: this is libtool’s concern, and
-the last thing one wants is to learn about libtool’s guts.  However the
-existence of these files matters, because they are used as targets and
-dependencies in ‘Makefile’s’ rules when building libtool libraries.
-There are situations where you may have to refer to these, for instance
-when expressing dependencies for building source files conditionally
-(*note Conditional Libtool Sources::).
+files and how Libtool constructs them; this is Libtool's concern.
+However, the existence of these files matters, because they are used as
+targets and dependencies in ‘Makefile’ rules when building Libtool
+libraries.  There are situations where you may have to refer to these,
+for instance when expressing dependencies for building source files
+conditionally (*note Conditional Libtool Sources::).
 
    People considering writing a plug-in system, with dynamically loaded
-modules, should look into ‘libltdl’: libtool’s dlopening library (*note
+modules, should look into ‘libltdl’: Libtool's dlopening library (*note
 Using libltdl: (libtool)Using libltdl.).  This offers a portable
-dlopening facility to load libtool libraries dynamically, and can also
+dlopening facility to load Libtool libraries dynamically, and can also
 achieve static linking where unavoidable.
 
-   Before we discuss how to use libtool with Automake in detail, it
-should be noted that the libtool manual also has a section about how to
-use Automake with libtool (*note Using Automake with Libtool:
+   Before we discuss how to use Libtool with Automake in detail, it
+should be noted that the Libtool manual also has a section about how to
+use Automake with Libtool (*note Using Automake with Libtool:
 (libtool)Using Automake.).
 
 &#x1f;
@@ -4412,8 +4453,8 @@
 8.3.2 Building Libtool Libraries
 --------------------------------
 
-Automake uses libtool to build libraries declared with the ‘LTLIBRARIES’
-primary.  Each ‘_LTLIBRARIES’ variable is a list of libtool libraries to
+Automake uses Libtool to build libraries declared with the ‘LTLIBRARIES’
+primary.  Each ‘_LTLIBRARIES’ variable is a list of Libtool libraries to
 build.  For instance, to create a libtool library named ‘libgettext.la’,
 and install it in ‘libdir’, write:
 
@@ -4446,7 +4487,7 @@
      hello_LDADD = libgettext.la
 
 Whether ‘hello’ is statically or dynamically linked with ‘libgettext.la’
-is not yet known: this will depend on the configuration of libtool and
+is not yet known: this will depend on the configuration of Libtool and
 the capabilities of the host.
 
 &#x1f;
@@ -4460,12 +4501,12 @@
 using Autoconf ‘AC_SUBST’itutions.
 
    The important implementation detail you have to be aware of is that
-the place where a library will be installed matters to libtool: it needs
+the place where a library will be installed matters to Libtool: it needs
 to be indicated _at link-time_ using the ‘-rpath’ option.
 
    For libraries whose destination directory is known when Automake
 runs, Automake will automatically supply the appropriate ‘-rpath’ option
-to libtool.  This is the case for libraries listed explicitly in some
+to ‘libtool’.  This is the case for libraries listed explicitly in some
 installable ‘_LTLIBRARIES’ variables such as ‘lib_LTLIBRARIES’.
 
    However, for libraries determined at configure time (and thus
@@ -4492,7 +4533,7 @@
 
    Here is how the same ‘Makefile.am’ would look using Automake
 conditionals named ‘WANT_LIBFOO’ and ‘WANT_LIBBAR’.  Now Automake is
-able to compute the ‘-rpath’ setting itself, because it’s clear that
+able to compute the ‘-rpath’ setting itself, because it's clear that
 both libraries will end up in ‘$(libdir)’ if they are installed.
 
      lib_LTLIBRARIES =
@@ -4546,14 +4587,14 @@
 8.3.5 Libtool Convenience Libraries
 -----------------------------------
 
-Sometimes you want to build libtool libraries that should not be
+Sometimes you want to build Libtool libraries that should not be
 installed.  These are called “libtool convenience libraries” and are
 typically used to encapsulate many sublibraries, later gathered into one
 big installed library.
 
    Libtool convenience libraries are declared by directory-less
 variables such as ‘noinst_LTLIBRARIES’, ‘check_LTLIBRARIES’, or even
-‘EXTRA_LTLIBRARIES’.  Unlike installed libtool libraries they do not
+‘EXTRA_LTLIBRARIES’.  Unlike installed Libtool libraries they do not
 need an ‘-rpath’ flag at link time (this is in fact the only
 difference).
 
@@ -4561,11 +4602,11 @@
 built.  Those listed in ‘check_LTLIBRARIES’ are built only upon ‘make
 check’.  Finally, libraries listed in ‘EXTRA_LTLIBRARIES’ are never
 built explicitly: Automake outputs rules to build them, but if the
-library does not appear as a Makefile dependency anywhere it won’t be
+library does not appear as a ‘Makefile’ dependency anywhere it won't be
 built (this is why ‘EXTRA_LTLIBRARIES’ is used for conditional
 compilation).
 
-   Here is a sample setup merging libtool convenience libraries from
+   Here is a sample setup merging Libtool convenience libraries from
 subdirectories into one main ‘libtop.la’ library.
 
      # -- Top-level Makefile.am --
@@ -4628,18 +4669,18 @@
 8.3.6 Libtool Modules
 ---------------------
 
-These are libtool libraries meant to be dlopened.  They are indicated to
-libtool by passing ‘-module’ at link-time.
+These are Libtool libraries meant to be dlopened.  They are indicated to
+‘libtool’ by passing ‘-module’ at link-time.
 
      pkglib_LTLIBRARIES = mymodule.la
      mymodule_la_SOURCES = doit.c
      mymodule_la_LDFLAGS = -module
 
-   Ordinarily, Automake requires that a library’s name start with ‘lib’.
+   Ordinarily, Automake requires that a library's name start with ‘lib’.
 However, when building a dynamically loadable module you might wish to
 use a "nonstandard" name.  Automake will not complain about such
 nonstandard names if it knows the library being built is a libtool
-module, i.e., if ‘-module’ explicitly appears in the library’s
+module, i.e., if ‘-module’ explicitly appears in the library's
 ‘_LDFLAGS’ variable (or in the common ‘AM_LDFLAGS’ variable when no
 per-library ‘_LDFLAGS’ variable is defined).
 
@@ -4663,8 +4704,8 @@
 (‘.la’) to add to LIBRARY.
 
    The ‘LIBRARY_LDFLAGS’ variable is the place to list additional
-libtool linking flags, such as ‘-version-info’, ‘-static’, and a lot
-more.  *Note Link mode: (libtool)Link mode.
+‘libtool’ linking flags, such as ‘-version-info’, ‘-static’, and a lot
+more.  *Note (libtool)Link mode::.
 
    The ‘libtool’ command has two kinds of options: mode-specific options
 and generic options.  Mode-specific options such as the aforementioned
@@ -4679,7 +4720,7 @@
    If ‘LIBRARY_LIBTOOLFLAGS’ is not defined, then the variable
 ‘AM_LIBTOOLFLAGS’ is used instead.
 
-   These flags are passed to libtool after the ‘--tag=TAG’ option
+   These flags are passed to ‘libtool’ after the ‘--tag=TAG’ option
 computed by Automake (if any), so ‘LIBRARY_LIBTOOLFLAGS’ (or
 ‘AM_LIBTOOLFLAGS’) is a good place to override or supplement the
 ‘--tag=TAG’ setting.
@@ -4709,22 +4750,23 @@
 &#x1f;
 File: automake.info,  Node: Libtool Issues,  Prev: LTLIBOBJS,  Up: A Shared Library
 
-8.3.9 Common Issues Related to Libtool’s Use
+8.3.9 Common Issues Related to Libtool's Use
 --------------------------------------------
 
 * Menu:
 
-* Error required file ltmain.sh not found::  The need to run libtoolize
+* Error required file ltmain.sh not found::        The need to run libtoolize
+* Libtool library used but LIBTOOL is undefined::  aclocal and test releases
 * Objects created both with libtool and without::  Avoid a specific build race
 
 &#x1f;
-File: automake.info,  Node: Error required file ltmain.sh not found,  Next: Objects created both with libtool and without,  Up: Libtool Issues
+File: automake.info,  Node: Error required file ltmain.sh not found,  Next: Libtool library used but LIBTOOL is undefined,  Up: Libtool Issues
 
-8.3.9.1 Error: ‘required file `./ltmain.sh' not found’
-......................................................
+8.3.9.1 Error: ‘required file './ltmain.sh' not found’--‘libtoolize’ needed
+...........................................................................
 
 Libtool comes with a tool called ‘libtoolize’ that will install
-libtool’s supporting files into a package.  Running this command will
+Libtool's supporting files into a package.  Running this command will
 install ‘ltmain.sh’.  You should execute it before ‘aclocal’ and
 ‘automake’.
 
@@ -4733,25 +4775,94 @@
 Therefore old build scripts do not call ‘libtoolize’.
 
    Since Automake 1.6, it has been decided that running ‘libtoolize’ was
-none of Automake’s business.  Instead, that functionality has been moved
+not Automake's business.  Instead, that functionality has been moved
 into the ‘autoreconf’ command (*note Using ‘autoreconf’:
-(autoconf)autoreconf Invocation.).  If you do not want to remember what
-to run and when, just learn the ‘autoreconf’ command.  Hopefully,
-replacing existing ‘bootstrap’ or ‘autogen.sh’ scripts by a call to
-‘autoreconf’ should also free you from any similar incompatible change
-in the future.
+(autoconf)autoreconf Invocation.).  The ‘autoreconf’ command saves you
+from having to figure out which infrastructure scripts to run in what
+order.  Augmenting existing ‘bootstrap’ or ‘autogen.sh’ scripts with a
+call to ‘autoreconf’ should also free you from any similar incompatible
+change in the future.
+
+&#x1f;
+File: automake.info,  Node: Libtool library used but LIBTOOL is undefined,  Next: Objects created both with libtool and without,  Prev: Error required file ltmain.sh not found,  Up: Libtool Issues
+
+8.3.9.2 Error: ‘Libtool library used but 'LIBTOOL' is undefined’--‘libtoolize’ redux
+....................................................................................
+
+This error message results from Automake seeing Libtool being used in
+‘Makefile.am’, but the ‘LIBTOOL’ variable is not defined.  There are two
+common reasons for this.  First, ‘LT_INIT’ is missing from
+‘configure.ac’; it can simply be added.
+
+   The second reason is more complicated: if you've installed Automake
+under a separate prefix, Automake cannot know where to find the
+‘LT_INIT’ macro.  Automake looks in the ‘aclocal.m4’ file, which is
+generated by the ‘aclocal’ command (*note aclocal Invocation::).  But
+since the default search paths for ‘aclocal’ are based on where it is
+installed (*note Macro Search Path::), if Automake is installed in one
+place (e.g., because it's for a test release), and Libtool in another
+(e.g., for general system use), ‘libtool.m4’ won't be found by ‘aclocal’
+and thus ‘LT_INIT’ won't be defined.
+
+   The best solution is to run ‘libtoolize’ in the tree that is using
+the separately-installed Automake.  That will copy ‘libtool.m4’ and the
+other Libtool M4 files and scripts into your package, including
+‘ltmain.sh’ (see previous section).  If you have subpackages that use
+Libtool independently, you'll need to run ‘libtoolize’ in each of them.
+*Note (libtool)Invoking libtoolize::.
+
+   The ‘libtoolize’ output suggests using an ‘m4’ subdirectory:
+
+     libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS(m4)' to configure.ac,
+     libtoolize: and rerunning libtoolize and aclocal.
+     libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
+
+   For purposes of Libtool and Automake, however, an m4 subdirectory is
+required, not just something to consider.  Without having the Libtool M4
+files in the local package, ‘aclocal’ will (frustratingly) report the
+same ‘Libtool library used but ...’ error.  (The name of the
+subdirectory for the M4 files can be anything, but ‘m4’ is by far the
+most common convention.)
+
+   Here is a concrete example.  Suppose you've installed a test release
+of Automake (thank you) with ‘--prefix=/tmp/amtest’, and thus put
+‘/tmp/amtest/bin’ first in your ‘PATH’.  You already have Libtool
+installed under ‘/usr/local/gnu’.  Then, your Libtool-using package will
+fail to bootstrap, with the error:
+
+     Makefile.am:161: error: Libtool library used but 'LIBTOOL' is undefined
+     ...
+
+   You can resolve this by ensuring your ‘configure.ac’ includes these
+lines (after the ‘AM_INIT_AUTOMAKE’):
+
+     AC_CONFIG_MACRO_DIRS(m4)
+     AM_PROG_AR
+     LT_INIT
+
+and then running:
+
+     libtoolize
+     autoreconf
+
+To summarize, the ‘libtoolize’ (from the system directory) copies
+‘libtool.m4’ and the other Libtool support files into your package.  The
+subsequent ‘autoreconf’ then runs ‘aclocal’ (under the test prefix)
+which can now find ‘LT_INIT’.
+
+   (For more discussion of this, see <https://bugs.gnu.org/71847>.
 
 &#x1f;
-File: automake.info,  Node: Objects created both with libtool and without,  Prev: Error required file ltmain.sh not found,  Up: Libtool Issues
+File: automake.info,  Node: Objects created both with libtool and without,  Prev: Libtool library used but LIBTOOL is undefined,  Up: Libtool Issues
 
-8.3.9.2 Objects ‘created with both libtool and without’
+8.3.9.3 Objects ‘created with both libtool and without’
 .......................................................
 
-Sometimes, the same source file is used both to build a libtool library
+Sometimes, the same source file is used both to build a Libtool library
 and to build another non-libtool target (be it a program or another
 library).
 
-   Let’s consider the following ‘Makefile.am’.
+   Let's consider the following ‘Makefile.am’.
 
      bin_PROGRAMS = prog
      prog_SOURCES = prog.c foo.c ...
@@ -4760,12 +4871,12 @@
      libfoo_la_SOURCES = foo.c ...
 
 (In this trivial case the issue could be avoided by linking ‘libfoo.la’
-with ‘prog’ instead of listing ‘foo.c’ in ‘prog_SOURCES’.  But let’s
+with ‘prog’ instead of listing ‘foo.c’ in ‘prog_SOURCES’.  But let's
 assume we want to keep ‘prog’ and ‘libfoo.la’ separate.)
 
    Technically, it means that we should build ‘foo.$(OBJEXT)’ for
 ‘prog’, and ‘foo.lo’ for ‘libfoo.la’.  The problem is that in the course
-of creating ‘foo.lo’, libtool may erase (or replace) ‘foo.$(OBJEXT)’,
+of creating ‘foo.lo’, Libtool may erase (or replace) ‘foo.$(OBJEXT)’,
 and this cannot be avoided.
 
    Therefore, when Automake detects this situation it will complain with
@@ -4799,9 +4910,9 @@
 such variables for each library.  The canonical name of the program (or
 library) is used as a base for naming these variables.
 
-   In the list below, we use the name “maude” to refer to the program or
+   In the list below, we use the name "maude" to refer to the program or
 library.  In your ‘Makefile.am’ you would replace this with the
-canonical name of your program.  This list also refers to “maude” as a
+canonical name of your program.  This list also refers to "maude" as a
 program, but in general the same rules apply for both static and dynamic
 libraries; the documentation below notes situations where programs and
 libraries differ.
@@ -4811,7 +4922,7 @@
      compiled to build the program.  These files are added to the
      distribution by default.  When building the program, Automake will
      cause each source file to be compiled to a single ‘.o’ file (or
-     ‘.lo’ when using libtool).  Normally these object files are named
+     ‘.lo’ when using Libtool).  Normally these object files are named
      after the source file, but other factors can change this.  If a
      file in the ‘_SOURCES’ variable has an unrecognized extension,
      Automake will do one of two things with it.  If a suffix rule
@@ -4853,7 +4964,7 @@
      _statically_.  For one thing, this is the only way Automake has of
      knowing what sort of language support a given ‘Makefile.in’
      requires.  (There are other, more obscure reasons for this
-     limitation as well.)  This means that, for example, you can’t put a
+     limitation as well.)  This means that, for example, you can't put a
      configure substitution like ‘@my_sources@’ into a ‘_SOURCES’
      variable.  If you intend to conditionally compile source files and
      use ‘configure’ to substitute the appropriate object names into,
@@ -4874,13 +4985,18 @@
      SGI C++ compiler likes this variable set like so:
           libmaude_a_AR = $(CXX) -ar -o
 
+‘maude_RANLIB’
+     A static library's index is updated by default by invoking
+     ‘$(RANLIB)’ followed by the name of the library.  You can override
+     this by setting the ‘_RANLIB’ variable.
+
 ‘maude_LIBADD’
      Extra objects can be added to a _library_ using the ‘_LIBADD’
      variable.  For instance, this should be used for objects determined
      by ‘configure’ (*note A Library::).
 
-     In the case of libtool libraries, ‘maude_LIBADD’ can also refer to
-     other libtool libraries.
+     In the case of Libtool libraries, ‘maude_LIBADD’ can also refer to
+     other Libtool libraries.
 
 ‘maude_LDADD’
      Extra objects (‘*.$(OBJEXT)’) and libraries (‘*.a’, ‘*.la’) can be
@@ -4912,7 +5028,7 @@
 ‘maude_LIBTOOLFLAGS’
      This variable is used to pass extra options to ‘libtool’.  It
      overrides the ‘AM_LIBTOOLFLAGS’ variable.  These options are output
-     before ‘libtool’’s ‘--mode=MODE’ option, so they should not be
+     before ‘libtool’'s ‘--mode=MODE’ option, so they should not be
      mode-specific options (those belong to the compiler or linker
      flags).  *Note Libtool Flags::.
 
@@ -4995,7 +5111,7 @@
      When using a per-target compilation flag, Automake will choose a
      different name for the intermediate object files.  Ordinarily a
      file like ‘sample.c’ will be compiled to produce ‘sample.o’.
-     However, if the program’s ‘_CFLAGS’ variable is set, then the
+     However, if the program's ‘_CFLAGS’ variable is set, then the
      object file will be named, for instance, ‘maude-sample.o’.  (See
      also *note Renamed Objects::.)
 
@@ -5014,7 +5130,7 @@
 ‘maude_SHORTNAME’
      On some platforms the allowable file names are very short.  In
      order to support these systems and per-target compilation flags at
-     the same time, Automake allows you to set a “short name” that will
+     the same time, Automake allows you to set a "short name" that will
      influence how intermediate object files are named.  For instance,
      in the following example,
 
@@ -5229,7 +5345,7 @@
      separate variable that is also passed to every compilation that
      invokes the C preprocessor.  In particular it generates ‘-I.’,
      ‘-I$(srcdir)’, and a ‘-I’ pointing to the directory holding
-     ‘config.h’ (if you’ve used ‘AC_CONFIG_HEADERS’).  You can disable
+     ‘config.h’ (if you've used ‘AC_CONFIG_HEADERS’).  You can disable
      the default ‘-I’ options using the ‘nostdinc’ option.
 
      When a file to be included is generated during the build and not
@@ -5270,7 +5386,7 @@
 ‘LINK’
      This is the command used to link a C program.  It already includes
      ‘-o $@’ and the usual variable references (for instance, ‘CFLAGS’);
-     it takes as “arguments” the names of the object files and libraries
+     it takes as "arguments" the names of the object files and libraries
      to link in.  This variable is not used when the linker is
      overridden with a per-target ‘_LINK’ variable or per-target flags
      cause Automake to define such a ‘_LINK’ variable.
@@ -5301,10 +5417,11 @@
 extensions ‘.l’, ‘.ll’, ‘.l++’, ‘.lxx’, and ‘.lpp’ are recognized.
 
    You should never explicitly mention the intermediate (C or C++) file
-in any ‘SOURCES’ variable; only list the source file.
+in any ‘SOURCES’ variable (except ‘BUILT_SOURCES’, see below); only list
+the source file.
 
    The intermediate files generated by ‘yacc’ (or ‘lex’) will be
-included in any distribution that is made.  That way the user doesn’t
+included in any distribution that is made.  That way the user doesn't
 need to have ‘yacc’ or ‘lex’.
 
    If a Yacc source file is seen, then your ‘configure.ac’ must define
@@ -5320,17 +5437,17 @@
 Automake knows what this means and will automatically adjust its rules
 to update and distribute the header file built by ‘yacc -d’.  Caveat:
 ‘automake’ recognizes ‘-d’ in ‘AM_YFLAGS’ only if it is not clustered
-with other options; for example, it won’t be recognized if ‘AM_YFLAGS’
+with other options; for example, it won't be recognized if ‘AM_YFLAGS’
 is ‘-dt’, but it will be if ‘AM_YFLAGS’ is ‘-d -t’ or ‘-t -d’.
 
    What Automake cannot guess, though, is where this header will be
 used: it is up to you to ensure the header gets built before it is first
 used.  Typically this is necessary in order for dependency tracking to
 work when the header is included by another file.  The common solution
-is listing the header file in ‘BUILT_SOURCES’ (*note Sources::) as
-follows.
+is listing the header file, and the corresponding C file, in
+‘BUILT_SOURCES’ (*note Sources::) as follows.
 
-     BUILT_SOURCES = parser.h
+     BUILT_SOURCES = parser.h parser.c
      AM_YFLAGS = -d
      bin_PROGRAMS = foo
      foo_SOURCES = ... parser.y ...
@@ -5353,22 +5470,22 @@
 Auxiliary Programs::).  This program is used by the build rules to
 rename the output of these tools, and makes it possible to include
 multiple ‘yacc’ (or ‘lex’) source files in a single directory.  This is
-necessary because Yacc’s output file name is fixed, and a parallel make
+necessary because Yacc's output file name is fixed, and a parallel make
 could invoke more than one instance of ‘yacc’ simultaneously.
 
 * Menu:
 
 * Linking Multiple Yacc Parsers::
 
-8.8.1 Linking Multiple Yacc Parsers
------------------------------------
-
 &#x1f;
 File: automake.info,  Node: Linking Multiple Yacc Parsers,  Up: Yacc and Lex
 
+8.8.1 Linking Multiple Yacc Parsers
+-----------------------------------
+
 For ‘yacc’, simply managing locking as with ‘ylwrap’ is insufficient.
 The output of ‘yacc’ always uses the same symbol names internally, so it
-isn’t possible to link two ‘yacc’ parsers into the same executable.
+isn't possible to link two ‘yacc’ parsers into the same executable.
 
    We recommend using the following renaming hack used in ‘gdb’:
      #define yymaxdepth c_maxdepth
@@ -5440,7 +5557,7 @@
      Any flags to pass to the C++ compiler.
 
 ‘AM_CXXFLAGS’
-     The maintainer’s variant of ‘CXXFLAGS’.
+     The maintainer's variant of ‘CXXFLAGS’.
 
 ‘CXXCOMPILE’
      The command used to compile a C++ source file.  The file name is
@@ -5472,7 +5589,7 @@
      Any flags to pass to the Objective C compiler.
 
 ‘AM_OBJCFLAGS’
-     The maintainer’s variant of ‘OBJCFLAGS’.
+     The maintainer's variant of ‘OBJCFLAGS’.
 
 ‘OBJCCOMPILE’
      The command used to compile an Objective C source file.  The file
@@ -5504,7 +5621,7 @@
      Any flags to pass to the Objective C++ compiler.
 
 ‘AM_OBJCXXFLAGS’
-     The maintainer’s variant of ‘OBJCXXFLAGS’.
+     The maintainer's variant of ‘OBJCXXFLAGS’.
 
 ‘OBJCXXCOMPILE’
      The command used to compile an Objective C++ source file.  The file
@@ -5535,7 +5652,7 @@
      Any flags to pass to the Unified Parallel C compiler.
 
 ‘AM_UPCFLAGS’
-     The maintainer’s variant of ‘UPCFLAGS’.
+     The maintainer's variant of ‘UPCFLAGS’.
 
 ‘UPCCOMPILE’
      The command used to compile a Unified Parallel C source file.  The
@@ -5592,13 +5709,13 @@
      Any flags to pass to the Fortran 77 compiler.
 
 ‘AM_FFLAGS’
-     The maintainer’s variant of ‘FFLAGS’.
+     The maintainer's variant of ‘FFLAGS’.
 
 ‘RFLAGS’
      Any flags to pass to the Ratfor compiler.
 
 ‘AM_RFLAGS’
-     The maintainer’s variant of ‘RFLAGS’.
+     The maintainer's variant of ‘RFLAGS’.
 
 ‘F77COMPILE’
      The command used to compile a Fortran 77 source file.  The file
@@ -5709,7 +5826,7 @@
      libfoo_la_LIBADD   = $(FLIBS)
 
    In this case, Automake will insist that ‘AC_F77_LIBRARY_LDFLAGS’ is
-mentioned in ‘configure.ac’.  Also, if ‘$(FLIBS)’ hadn’t been mentioned
+mentioned in ‘configure.ac’.  Also, if ‘$(FLIBS)’ hadn't been mentioned
 in ‘foo_LDADD’ and ‘libfoo_la_LIBADD’, then Automake would have issued a
 warning.
 
@@ -5746,7 +5863,7 @@
 
    For example, if Fortran 77, C and C++ source code is compiled into a
 program, then the C++ linker will be used.  In this case, if the C or
-Fortran 77 linkers required any special libraries that weren’t included
+Fortran 77 linkers required any special libraries that weren't included
 by the C++ linker, then they must be manually added to an ‘_LDADD’ or
 ‘_LIBADD’ variable by the user writing the ‘Makefile.am’.
 
@@ -5784,7 +5901,7 @@
      Any flags to pass to the Fortran 9x compiler.
 
 ‘AM_FCFLAGS’
-     The maintainer’s variant of ‘FCFLAGS’.
+     The maintainer's variant of ‘FCFLAGS’.
 
 ‘FCCOMPILE’
      The command used to compile a Fortran 9x source file.  The file
@@ -5859,9 +5976,8 @@
 8.17 Vala Support
 =================
 
-Automake provides initial support for Vala
-(<https://www.vala-project.org/>).  This requires valac version 0.7.0 or
-later, and currently requires the user to use GNU ‘make’.
+Automake supports Vala (<https://vala.dev/>).  Vala support requires the
+user to use GNU ‘make’.
 
      foo_SOURCES = foo.vala bar.vala zardoz.c
 
@@ -5870,6 +5986,11 @@
 distributed.  The end user does not need to have a Vala compiler
 installed.
 
+   Because all C files must be generated, and the Vala compiler compiles
+all the ‘.vala’ files for a target at once, it is not possible to add
+files to a ‘_SOURCES’ variable that cannot be compiled together; for
+example, alternative platform-specific definitions of the same methods.
+
    Automake ships with an Autoconf macro called ‘AM_PROG_VALAC’ that
 will locate the Vala compiler and optionally check its version number.
 
@@ -5898,7 +6019,7 @@
      Additional arguments for the Vala compiler.
 
 ‘AM_VALAFLAGS’
-     The maintainer’s variant of ‘VALAFLAGS’.
+     The maintainer's variant of ‘VALAFLAGS’.
 
           lib_LTLIBRARIES = libfoo.la
           libfoo_la_SOURCES = foo.vala
@@ -5935,23 +6056,23 @@
 changes (*note Dependency Tracking::).
 
    Automake always uses complete dependencies for a compilation,
-including system headers.  Automake’s model is that dependency
+including system headers.  Automake's model is that dependency
 computation should be a side effect of the build.  To this end,
 dependencies are computed by running all compilations through a special
 wrapper program called ‘depcomp’.  ‘depcomp’ understands how to coax
 many different C and C++ compilers into generating dependency
 information in the format it requires.  ‘automake -a’ will install
-‘depcomp’ into your source tree for you.  If ‘depcomp’ can’t figure out
+‘depcomp’ into your source tree for you.  If ‘depcomp’ can't figure out
 how to properly invoke your compiler, dependency tracking will simply be
 disabled for your build.
 
    Experience with earlier versions of Automake (*note Dependency
 Tracking Evolution: (automake-history)Dependency Tracking Evolution.)
 taught us that it is not reliable to generate dependencies only on the
-maintainer’s system, as configurations vary too much.  So instead
+maintainer's system, as configurations vary too much.  So instead
 Automake implements dependency tracking at build time.
 
-   Automatic dependency tracking can be suppressed by putting
+   This automatic dependency tracking can be suppressed by putting
 ‘no-dependencies’ in the variable ‘AUTOMAKE_OPTIONS’, or passing
 ‘no-dependencies’ as an argument to ‘AM_INIT_AUTOMAKE’ (this should be
 the preferred way).  Or, you can invoke ‘automake’ with the ‘-i’ option.
@@ -5960,6 +6081,24 @@
    The person building your package also can choose to disable
 dependency tracking by configuring with ‘--disable-dependency-tracking’.
 
+   If, as the package maintainer, you wish to conditionalize your
+‘Makefile.am’ according to whether dependency tracking is enabled, the
+best way is to define your own conditional in ‘configure.ac’ according
+to the shell variable ‘$enable_dependency_tracking’ (all
+‘--enable’/‘--disable’ options are available as shell variables; *note
+(autoconf)Package Options::):
+
+     AM_CONDITIONAL(NO_DEP_TRACKING,
+                    test x"$enable_dependency_tracking" = x"no")
+
+   And then in your ‘Makefile.am’:
+
+     if NO_DEP_TRACKING
+     # stuff to do when dependency tracking is disabled
+     else
+     # stuff to do when it's enabled
+     endif
+
 &#x1f;
 File: automake.info,  Node: EXEEXT,  Prev: Dependencies,  Up: Programs
 
@@ -5972,7 +6111,7 @@
 ‘foo’.
 
    Automake provides mostly-transparent support for this.  Unfortunately
-_mostly_ doesn’t yet mean _fully_.  Until the English dictionary is
+_mostly_ doesn't yet mean _fully_.  Until the English dictionary is
 revised, you will have to assist Automake if your package must support
 those platforms.
 
@@ -5999,7 +6138,7 @@
 care to add ‘$(EXEEXT)’ when constructing the output variable.
 
    Sometimes maintainers like to write an explicit link rule for their
-program.  Without executable extension support, this is easy—you simply
+program.  Without executable extension support, this is easy--you simply
 write a rule whose target is the name of the program.  However, when
 executable extension support is enabled, you must instead add the
 ‘$(EXEEXT)’ suffix.
@@ -6130,7 +6269,7 @@
 be installed.  Headers used by programs or convenience libraries are not
 installed.  The ‘noinst_HEADERS’ variable can be used for such headers.
 However, when the header belongs to a single convenience library or
-program, we recommend listing it in the program’s or library’s
+program, we recommend listing it in the program's or library's
 ‘_SOURCES’ variable (*note Program Sources::) instead of in
 ‘noinst_HEADERS’.  This is clearer for the ‘Makefile.am’ reader.
 ‘noinst_HEADERS’ would be the right variable to use in a directory
@@ -6155,8 +6294,9 @@
 Automake supports the installation of miscellaneous data files using the
 ‘DATA’ family of variables.
 
-   Such data can be installed in the directories ‘datadir’,
-‘sysconfdir’, ‘sharedstatedir’, ‘localstatedir’, or ‘pkgdatadir’.
+   Such data can be installed in the directories ‘datadir’, ‘docdir’,
+‘lispdir’, ‘sysconfdir’, ‘sharedstatedir’, ‘localstatedir’, or
+‘pkgdatadir’.
 
    By default, data files are _not_ included in a distribution.  Of
 course, you can use the ‘dist_’ prefix to change this on a per-variable
@@ -6172,7 +6312,7 @@
 9.4 Built Sources
 =================
 
-Because Automake’s automatic dependency tracking works as a side-effect
+Because Automake's automatic dependency tracking works as a side-effect
 of compilation (*note Dependencies::) there is a bootstrap issue: a
 target should not be compiled before its dependencies are made, but
 these dependencies are unknown until the target is first compiled.
@@ -6182,14 +6322,14 @@
 that ‘foo.c’ includes ‘foo.h’.  When it first compiles ‘foo.o’, ‘make’
 only knows that ‘foo.o’ depends on ‘foo.c’.  As a side-effect of this
 compilation ‘depcomp’ records the ‘foo.h’ dependency so that following
-invocations of ‘make’ will honor it.  In these conditions, it’s clear
-there is no problem: either ‘foo.o’ doesn’t exist and has to be built
+invocations of ‘make’ will honor it.  In these conditions, it's clear
+there is no problem: either ‘foo.o’ doesn't exist and has to be built
 (regardless of the dependencies), or accurate dependencies exist and
 they can be used to decide whether ‘foo.o’ should be rebuilt.
 
-   It’s a different story if ‘foo.h’ doesn’t exist by the first ‘make’
+   It's a different story if ‘foo.h’ doesn't exist by the first ‘make’
 run.  For instance, there might be a rule to build ‘foo.h’.  This time
-‘file.o’’s build will fail because the compiler can’t find ‘foo.h’.
+‘file.o’'s build will fail because the compiler can't find ‘foo.h’.
 ‘make’ failed to trigger the rule to build ‘foo.h’ first by lack of
 dependency information.
 
@@ -6207,9 +6347,9 @@
    ‘BUILT_SOURCES’ is a bit of a misnomer, as any file which must be
 created early in the build process can be listed in this variable.
 Moreover, all built sources do not necessarily have to be listed in
-‘BUILT_SOURCES’.  For instance, a generated ‘.c’ file doesn’t need to
+‘BUILT_SOURCES’.  For instance, a generated ‘.c’ file doesn't need to
 appear in ‘BUILT_SOURCES’ (unless it is included by another source),
-because it’s a known dependency of the associated object.
+because it's a known dependency of the associated object.
 
    To emphasize, ‘BUILT_SOURCES’ is honored only by ‘make all’, ‘make
 check’, ‘make install’, and ‘make install-exec’ (and ‘make dist’).  This
@@ -6236,7 +6376,7 @@
 ‘bindir.h’ defines the preprocessor macro ‘bindir’ to the value of the
 ‘make’ variable ‘bindir’ (inherited from ‘configure’).
 
-   We suggest several implementations below.  It’s not meant to be an
+   We suggest several implementations below.  It's not meant to be an
 exhaustive listing of all ways to handle built sources, but it will give
 you a few ideas if you encounter this issue.
 
@@ -6256,7 +6396,7 @@
      bindir.h: Makefile
              echo '#define bindir "$(bindir)"' >$@
 
-   This setup doesn’t work, because Automake doesn’t know that ‘foo.c’
+   This setup doesn't work, because Automake doesn't know that ‘foo.c’
 includes ‘bindir.h’.  Remember, automatic dependency tracking works as a
 side-effect of compilation, so the dependencies of ‘foo.o’ will be known
 only after ‘foo.o’ has been compiled (*note Dependencies::).  The
@@ -6338,7 +6478,7 @@
      bindir.h: Makefile
              echo '#define bindir "$(bindir)"' >$@
 
-   You don’t have to list _all_ the dependencies of ‘foo.o’ explicitly,
+   You don't have to list _all_ the dependencies of ‘foo.o’ explicitly,
 only those that might need to be built.  If a dependency already exists,
 it will not hinder the first compilation and will be recorded by the
 normal dependency tracking code.  (After this first compilation, the
@@ -6351,14 +6491,14 @@
 overwrite your rules (it assumes you know better than it).
 ‘foo.$(OBJEXT): bindir.h’ supersedes any rule Automake may want to
 output to build ‘foo.$(OBJEXT)’.  It happens to work in this case
-because Automake doesn’t have to output any ‘foo.$(OBJEXT):’ target: it
+because Automake doesn't have to output any ‘foo.$(OBJEXT):’ target: it
 relies on a suffix rule instead (i.e., ‘.c.$(OBJEXT):’).  Always check
 the generated ‘Makefile.in’ if you do this.
 
 Build ‘bindir.h’ from ‘configure’
 .................................
 
-It’s possible to define this preprocessor macro from ‘configure’, either
+It's possible to define this preprocessor macro from ‘configure’, either
 in ‘config.h’ (*note Defining Directories: (autoconf)Defining
 Directories.), or by processing a ‘bindir.h.in’ file using
 ‘AC_CONFIG_FILES’ (*note Configuration Actions: (autoconf)Configuration
@@ -6374,7 +6514,7 @@
      bin_PROGRAMS = foo
      foo_SOURCES = foo.c
 
-   However, it’s not always possible to build sources from ‘configure’,
+   However, it's not always possible to build sources from ‘configure’,
 especially when these sources are generated by a tool that needs to be
 built first.
 
@@ -6391,8 +6531,8 @@
      bindir.c: Makefile
              echo 'const char bindir = "$(bindir)";' >$@
 
-   ‘bindir.h’ contains just the variable’s declaration and doesn’t need
-to be built, so it won’t cause any trouble.  ‘bindir.o’ is always
+   ‘bindir.h’ contains just the variable's declaration and doesn't need
+to be built, so it won't cause any trouble.  ‘bindir.o’ is always
 dependent on ‘bindir.c’, so ‘bindir.c’ will get built first.
 
 Which is best?
@@ -6404,7 +6544,7 @@
    You cannot use ‘BUILT_SOURCES’ if the ability to run ‘make foo’ on a
 clean tree is important to you.
 
-   You won’t add explicit dependencies if you are leery of overriding an
+   You won't add explicit dependencies if you are leery of overriding an
 Automake rule by mistake.
 
    Building files from ‘./configure’ is not always possible, neither is
@@ -6512,7 +6652,7 @@
 to native machine code; *note Java Support with gcj::).  Note however
 that _the interface and most features described here are deprecated_.
 Future Automake releases will strive to provide a better and cleaner
-interface, which however _won’t be backward-compatible_; the present
+interface, which however _won't be backward-compatible_; the present
 interface will probably be removed altogether some time after the
 introduction of the new interface (if that ever materializes).  In any
 case, the current ‘JAVA’ primary features are frozen and will no longer
@@ -6530,7 +6670,7 @@
 
    Currently Automake enforces the restriction that only one ‘_JAVA’
 primary can be used in a given ‘Makefile.am’.  The reason for this
-restriction is that, in general, it isn’t possible to know which
+restriction is that, in general, it isn't possible to know which
 ‘.class’ files were generated from which ‘.java’ files, so it would be
 impossible to know which files to install where.  For instance, a
 ‘.java’ file can define multiple classes; the resulting ‘.class’ file
@@ -6640,7 +6780,7 @@
      ‘--with-python_exec_prefix’ set them to an explicit value.
 
      The ‘configure’ option ‘--with-python-sys-prefix’ set them to the
-     values of Python’s ‘sys.prefix’ and ‘sys.exec_prefix’ variables.
+     values of Python's ‘sys.prefix’ and ‘sys.exec_prefix’ variables.
      These often differ from ‘${prefix}’ and ‘${exec_prefix}’, e.g., on
      platforms such as Mac OS x (where Python is usually installed as a
      Framework).
@@ -6651,8 +6791,16 @@
      building Python extensions.
 
 ‘pythondir’
-     The directory name for the ‘site-packages’ subdirectory of the
-     standard Python install tree.
+     The subdirectory of the Python install tree in which to install
+     Python scripts.  By default this is, on all systems,
+     ‘$PYTHON_PREFIX/lib/pythonVERSION/site-packages’, where
+     ‘$PYTHON_PREFIX’ is described above, and VERSION is the Python
+     version.  (For those knowledgeable about Python installation
+     details: systems generally have their own Python installation
+     scheme, such as ‘posix_local’ on Debian and related (as of
+     Python 3.10), which ends up using a directory named
+     ‘dist-packages’; Automake uses the ‘posix_prefix’ scheme and
+     ‘site-packages’.)
 
 ‘pkgpythondir’
      This is the directory under ‘pythondir’ that is named after the
@@ -6681,6 +6829,62 @@
 (autoconf)Installation Directory Variables.).  See also *note Hard-Coded
 Install Paths::.
 
+* Menu:
+
+* Supported Python versions::
+
+&#x1f;
+File: automake.info,  Node: Supported Python versions,  Up: Python
+
+10.5.1 Supported versions
+-------------------------
+
+Automake guarantees releases will support all Python versions that are
+still supported by the Python project at the time of the Automake
+release.  Support for EOL versions of Python are not guaranteed, but
+will be considered as long as it is not onerous to do so, and there are
+large supported distros including them.  If you need to support older
+Python versions, please use a previous Automake release.
+
+   Here are the current support plans.
+
+Version     Status
+--------------------------
+0.x         Not
+            supported
+1.x         Not
+            supported
+2.0-2.6     Untested,
+            but should
+            work
+2.7         Supported
+            (until Apr
+            2026)
+3.0-3.3     Untested,
+            but should
+            work
+3.4         Supported
+            (until Apr
+            2022)
+3.5         Supported
+            (until Apr
+            2024)
+3.6         Supported
+            (until Apr
+            2028)
+3.7         Supported
+            (until Apr
+            2028)
+3.8         Supported
+            (until Apr
+            2030)
+3.9         Supported
+            (until Apr
+            2030)
+3.10        Supported
+            (until Apr
+            2030)
+
 &#x1f;
 File: automake.info,  Node: Documentation,  Next: Install,  Prev: Other GNU Tools,  Up: Top
 
@@ -6691,8 +6895,8 @@
 
 * Menu:
 
-* Texinfo::                     Texinfo
-* Man Pages::                   Man pages
+* Texinfo::
+* Man Pages::
 
 &#x1f;
 File: automake.info,  Node: Texinfo,  Next: Man Pages,  Up: Documentation
@@ -6719,6 +6923,27 @@
 rather than in the ‘builddir’.  This can be changed with the
 ‘info-in-builddir’ option.
 
+   If the Texinfo sources are in a subdirectory relative to the
+Makefile, then ‘-I’ flags for the subdirectory, both in the source
+directory and in the build directory, will automatically be added.
+There is no need to specify these in ‘$(MAKEINFO)’, ‘$(MAKEINFOFLAGS)’,
+etc.
+
+   If a Texinfo source file contains an ‘@setfilename’ directive, and
+its argument has extension ‘.info’ (or no extension, but this is
+discouraged), that argument should be the same as the basename of the
+Texinfo file, extended with ‘.info’.  The Make rules generated by
+Automake assume this, and will not work if the ‘@setfilename’ is for
+some other name.
+
+   If a Texinfo source ‘foo.texi’ is not present, but ‘foo.texi.in’
+exists, Texinfo will read that ‘.texi.in’ file for ‘@setfilename’ and
+‘@include version.texi’ (described below).
+
+   Texinfo source files need not be present at all, and if present, need
+not contain ‘@setfilename’.  Then the file name given in the Makefile.am
+will be used.
+
    Other documentation formats can be built on request by ‘make dvi’,
 ‘make ps’, ‘make pdf’ and ‘make html’, and they can be installed with
 ‘make install-dvi’, ‘make install-ps’, ‘make install-pdf’ and ‘make
@@ -6729,10 +6954,11 @@
    All of these targets can be extended using ‘-local’ rules (*note
 Extending::).
 
-   If the ‘.texi’ file ‘@include’s ‘version.texi’, then that file will
-be automatically generated.  The file ‘version.texi’ defines four
-Texinfo flags you can reference using ‘@value{EDITION}’,
-‘@value{VERSION}’, ‘@value{UPDATED}’, and ‘@value{UPDATED-MONTH}’.
+   If a ‘.texi’ file ‘@include’s ‘version.texi’ (actually any file named
+‘vers...texi’, then that file will be automatically generated.  The file
+‘version.texi’ defines four Texinfo flags you can reference using
+‘@value{EDITION}’, ‘@value{VERSION}’, ‘@value{UPDATED}’, and
+‘@value{UPDATED-MONTH}’.
 
 ‘EDITION’
 ‘VERSION’
@@ -6753,7 +6979,7 @@
    If you have multiple Texinfo files, and you want to use the
 ‘version.texi’ feature, then you have to have a separate version file
 for each Texinfo file.  Automake will treat any include in a Texinfo
-file that matches ‘vers*.texi’ just as an automatically generated
+file that matches ‘vers*.texi’ just like an automatically generated
 version file.
 
    Often an Info file depends on more than one ‘.texi’ file.  For
@@ -6767,7 +6993,7 @@
    By default, Automake requires the file ‘texinfo.tex’ to appear in the
 same directory as the ‘Makefile.am’ file that lists the ‘.texi’ files.
 If you used ‘AC_CONFIG_AUX_DIR’ in ‘configure.ac’ (*note Finding
-‘configure’ Input: (autoconf)Input.), then ‘texinfo.tex’ is looked for
+'configure' Input: (autoconf)Input.), then ‘texinfo.tex’ is looked for
 there.  In both cases, ‘automake’ then supplies ‘texinfo.tex’ if
 ‘--add-missing’ is given, and takes care of its distribution.  However,
 if you set the ‘TEXINFO_TEX’ variable (see below), it overrides the
@@ -6811,11 +7037,13 @@
 
 ‘AM_MAKEINFOFLAGS’
 ‘AM_MAKEINFOHTMLFLAGS’
+‘AM_TEXI2FLAGS’
      Maintainer flags passed to each ‘makeinfo’ invocation.  Unlike
      ‘MAKEINFOFLAGS’, these variables are meant to be defined by
      maintainers in ‘Makefile.am’.  ‘$(AM_MAKEINFOFLAGS)’ is passed to
-     ‘makeinfo’ when building ‘.info’ files; and
-     ‘$(AM_MAKEINFOHTMLFLAGS)’ is used when building ‘.html’ files.
+     ‘makeinfo’ when building ‘.info’ files; ‘$(AM_MAKEINFOHTMLFLAGS)’
+     is used when building ‘.html’ files; and ‘$(AM_TEXI2FLAGS)’ is used
+     when building ‘.dvi’ and ‘.pdf’ files.
 
      For instance, the following setting can be used to obtain one
      single ‘.html’ file per manual, without node separators.
@@ -6848,72 +7076,3 @@
 
           TEXINFO_TEX = ../doc/texinfo.tex
 
-&#x1f;
-File: automake.info,  Node: Man Pages,  Prev: Texinfo,  Up: Documentation
-
-11.2 Man Pages
-==============
-
-A package can also include man pages (but see the GNU standards on this
-matter, *note (standards)Man Pages::.)  Man pages are declared using the
-‘MANS’ primary.  Generally the ‘man_MANS’ variable is used.  Man pages
-are automatically installed in the correct subdirectory of ‘mandir’,
-based on the file extension.
-
-   File extensions such as ‘.1c’ are handled by looking for the valid
-part of the extension and using that to determine the correct
-subdirectory of ‘mandir’.  Valid section names are the digits ‘0’
-through ‘9’, and the letters ‘l’ and ‘n’.
-
-   Sometimes developers prefer to name a man page something like
-‘foo.man’ in the source, and then rename it to have the correct suffix,
-for example ‘foo.1’, when installing the file.  Automake also supports
-this mode.  For a valid section named SECTION, there is a corresponding
-directory named ‘manSECTIONdir’, and a corresponding ‘_MANS’ variable.
-Files listed in such a variable are installed in the indicated section.
-If the file already has a valid suffix, then it is installed as-is;
-otherwise the file suffix is changed to match the section.
-
-   For instance, consider this example:
-     man1_MANS = rename.man thesame.1 alsothesame.1c
-
-In this case, ‘rename.man’ will be renamed to ‘rename.1’ when installed,
-but the other files will keep their names.
-
-   By default, man pages are installed by ‘make install’.  However,
-since the GNU project does not require man pages, many maintainers do
-not expend effort to keep the man pages up to date.  In these cases, the
-‘no-installman’ option will prevent the man pages from being installed
-by default.  The user can still explicitly install them via ‘make
-install-man’.
-
-   For fast installation, with many files it is preferable to use
-‘manSECTION_MANS’ over ‘man_MANS’ as well as files that do not need to
-be renamed.
-
-   Man pages are not currently considered to be source, because it is
-not uncommon for man pages to be automatically generated.  Therefore
-they are not automatically included in the distribution.  However, this
-can be changed by use of the ‘dist_’ prefix.  For instance here is how
-to distribute and install the two man pages of GNU ‘cpio’ (which
-includes both Texinfo documentation and man pages):
-
-     dist_man_MANS = cpio.1 mt.1
-
-   The ‘nobase_’ prefix is meaningless for man pages and is disallowed.
-
-   Executables and manpages may be renamed upon installation (*note
-Renaming::).  For manpages this can be avoided by use of the ‘notrans_’
-prefix.  For instance, suppose an executable ‘foo’ allowing to access a
-library function ‘foo’ from the command line.  The way to avoid renaming
-of the ‘foo.3’ manpage is:
-
-     man_MANS = foo.1
-     notrans_man_MANS = foo.3
-
-   ‘notrans_’ must be specified first when used in conjunction with
-either ‘dist_’ or ‘nodist_’ (*note Fine-grained Distribution Control::).
-For instance:
-
-     notrans_dist_man3_MANS = bar.3
-

_service:tar_scm:automake-1.16.5.tar.xz/doc/automake.info-2 -> _service:tar_scm:automake-1.17.tar.xz/doc/automake.info-2 Changed

@@ -1,18 +1,17 @@
-This is automake.info, produced by makeinfo version 6.8 from
+This is automake.info, produced by makeinfo version 7.1 from
 automake.texi.
 
-This manual is for GNU Automake (version 1.16.5, 1 October 2021), a
-program that creates GNU standards-compliant Makefiles from template
-files.
+This manual is for GNU Automake (version 1.17, 12 July 2024), a program
+that creates GNU standards-compliant Makefiles from template files.
 
-   Copyright © 1995–2021 Free Software Foundation, Inc.
+   Copyright © 1995-2024 Free Software Foundation, Inc.
 
      Permission is granted to copy, distribute and/or modify this
      document under the terms of the GNU Free Documentation License,
      Version 1.3 or any later version published by the Free Software
      Foundation; with no Invariant Sections, with no Front-Cover texts,
      and with no Back-Cover Texts.  A copy of the license is included in
-     the section entitled “GNU Free Documentation License.”
+     the section entitled "GNU Free Documentation License."
 
 INFO-DIR-SECTION Software development
 START-INFO-DIR-ENTRY
@@ -26,6 +25,75 @@
 END-INFO-DIR-ENTRY
 
 &#x1f;
+File: automake.info,  Node: Man Pages,  Prev: Texinfo,  Up: Documentation
+
+11.2 Man Pages
+==============
+
+A package can also include man pages (but see the GNU standards on this
+matter, *note (standards)Man Pages::.)  Man pages are declared using the
+‘MANS’ primary.  Generally the ‘man_MANS’ variable is used.  Man pages
+are automatically installed in the correct subdirectory of ‘mandir’,
+based on the file extension.
+
+   File extensions such as ‘.1c’ are handled by looking for the valid
+part of the extension and using that to determine the correct
+subdirectory of ‘mandir’.  Valid section names are the digits ‘0’
+through ‘9’, and the letters ‘l’ and ‘n’.
+
+   Sometimes developers prefer to name a man page something like
+‘foo.man’ in the source, and then rename it to have the correct suffix,
+for example ‘foo.1’, when installing the file.  Automake also supports
+this mode.  For a valid section named SECTION, there is a corresponding
+directory named ‘manSECTIONdir’, and a corresponding ‘_MANS’ variable.
+Files listed in such a variable are installed in the indicated section.
+If the file already has a valid suffix, then it is installed as-is;
+otherwise the file suffix is changed to match the section.
+
+   For instance, consider this example:
+     man1_MANS = rename.man thesame.1 alsothesame.1c
+
+In this case, ‘rename.man’ will be renamed to ‘rename.1’ when installed,
+but the other files will keep their names.
+
+   By default, man pages are installed by ‘make install’.  However,
+since the GNU project does not require man pages, many maintainers do
+not expend effort to keep the man pages up to date.  In these cases, the
+‘no-installman’ option will prevent the man pages from being installed
+by default.  The user can still explicitly install them via ‘make
+install-man’.
+
+   For fast installation, with many files it is preferable to use
+‘manSECTION_MANS’ over ‘man_MANS’ as well as files that do not need to
+be renamed.
+
+   Man pages are not currently considered to be source, because it is
+not uncommon for man pages to be automatically generated.  Therefore
+they are not automatically included in the distribution.  However, this
+can be changed by use of the ‘dist_’ prefix.  For instance here is how
+to distribute and install the two man pages of GNU ‘cpio’ (which
+includes both Texinfo documentation and man pages):
+
+     dist_man_MANS = cpio.1 mt.1
+
+   The ‘nobase_’ prefix is meaningless for man pages and is disallowed.
+
+   Executables and manpages may be renamed upon installation (*note
+Renaming::).  For manpages this can be avoided by use of the ‘notrans_’
+prefix.  For instance, suppose an executable ‘foo’ allowing to access a
+library function ‘foo’ from the command line.  The way to avoid renaming
+of the ‘foo.3’ manpage is:
+
+     man_MANS = foo.1
+     notrans_man_MANS = foo.3
+
+   ‘notrans_’ must be specified first when used in conjunction with
+either ‘dist_’ or ‘nodist_’ (*note Fine-grained Distribution Control::).
+For instance:
+
+     notrans_dist_man3_MANS = bar.3
+
+&#x1f;
 File: automake.info,  Node: Install,  Next: Clean,  Prev: Documentation,  Up: Top
 
 12 What Gets Installed
@@ -89,8 +157,8 @@
 
 Automake generates separate ‘install-data’ and ‘install-exec’ rules, in
 case the installer is installing on multiple machines that share
-directory structure—these targets allow the machine-independent parts to
-be installed only once.  ‘install-exec’ installs platform-dependent
+directory structure--these targets allow the machine-independent parts
+to be installed only once.  ‘install-exec’ installs platform-dependent
 files, and ‘install-data’ installs platform-independent files.  The
 ‘install’ target depends on both of these targets.  While Automake tries
 to automatically segregate objects into the correct category, the
@@ -171,7 +239,7 @@
 and ‘install-strip’.
 
    Automake supports ‘uninstall-local’ and ‘uninstall-hook’.  There is
-no notion of separate uninstalls for “exec” and “data”, as these
+no notion of separate uninstalls for "exec" and "data", as these
 features would not provide additional functionality.
 
    Note that ‘uninstall’ is not meant as a replacement for a real
@@ -211,8 +279,8 @@
      clean-local-check:
              -rm -rf testSubDir
 
-   As the GNU Standards aren’t always explicit as to which files should
-be removed by which rule, we’ve adopted a heuristic that we believe was
+   As the GNU Standards aren't always explicit as to which files should
+be removed by which rule, we've adopted a heuristic that we believe was
 first formulated by François Pinard:
 
    • If ‘make’ built it, and it is commonly something that one would
@@ -257,13 +325,26 @@
 automatically defined by either the ‘AC_INIT’ invocation or by a
 _deprecated_ two-arguments invocation of the ‘AM_INIT_AUTOMAKE’ macro
 (see *note Public Macros:: for how these variables get their values,
-from either defaults or explicit values—it’s slightly trickier than one
+from either defaults or explicit values--it's slightly trickier than one
 would expect).  More precisely, the gzipped ‘tar’ file is named
 ‘${PACKAGE}-${VERSION}.tar.gz’.
 
-   You can set the environment variable ‘TAR’ to override the tar
-program used; it defaults to ‘tar’.  *Note The Types of Distributions::,
-for how to generate other kinds of archives.
+   You can set the environment (or ‘Makefile.am’) variable ‘TAR’ to
+override the tar program used; it defaults to ‘tar’.  *Note The Types of
+Distributions::, for how to generate other kinds of archives.
+
+   With GNU tar, you can also set the environment (or ‘Makefile.am’)
+variable ‘TAR_OPTIONS’ to pass options to ‘tar’.  One common case for
+this is wanting to avoid using the local user's uid and gid in the tar
+file, or the uid being larger than is supported by the tar format (not
+uncommon nowadays).  This can be done with, for example>
+
+     TAR_OPTIONS = --owner=0 --group=0
+     export TAR_OPTIONS
+
+The ‘export’ (a GNU make feature) is necessary to pass the variable in
+the environment to the ‘tar’ invocation.  (For more discussion, see
+<https://bugs.gnu.org/19615>.)
 
    For the most part, the files to distribute are automatically found by
 Automake:
@@ -392,7 +473,7 @@
 absolute path; do not assume a particular form.
 
    ‘$(top_distdir)’ always points to the root directory of the
-distributed tree.  At the top level it’s equal to ‘$(distdir)’.  In the
+distributed tree.  At the top level it's equal to ‘$(distdir)’.  In the
 ‘foo/’ subdirectory ‘top_distdir = ../$(PACKAGE)-$(VERSION)’.
 ‘$(top_distdir)’ can also be either a relative or absolute path.
 
@@ -410,10 +491,9 @@
 that a given distribution will actually work.  Simplifying a bit, we can
 say this rule first makes a distribution, and then, _operating from it_,
 takes the following steps (in this order):
-   • tries to do a ‘VPATH’ build (*note VPATH Builds::), with the
-     ‘srcdir’ and all its content made _read-only_;
-   • tries to make the printable documentation, if any (with ‘make
-     dvi’),
+   • does a ‘VPATH’ build (*note VPATH Builds::), with the ‘srcdir’ and
+     all its content made _read-only_;
+   • makes the printable documentation (with ‘make dvi’), if any,
    • runs the test suite (with ‘make check’) on this fresh build;
    • installs the package in a temporary directory (with ‘make
      install’), and runs the test suite on the resulting installation
@@ -427,38 +507,71 @@
 exact location and the exact structure of such a directory (where the
 read-only sources are placed, how the temporary build and install
 directories are named and how deeply they are nested, etc.)  is to be
-considered an implementation detail, which can change at any time; so do
-not rely on it.
+considered an implementation detail, which can change at any time, so
+please do not rely on it.
 
-DISTCHECK_CONFIGURE_FLAGS
--------------------------
+* Menu:
+
+* DISTCHECK_CONFIGURE_FLAGS::  Overriding configure flags in distcheck.
+* distcheck-hook::             Running commands after distcheck.
+* dvi and distcheck::          Overriding the distcheck doc target.
+* distcleancheck::             Handling files not cleaned.
+* distuninstallcheck::         Overriding the uninstall check.
+* Errors with distclean::
+
+&#x1f;
+File: automake.info,  Node: DISTCHECK_CONFIGURE_FLAGS,  Next: distcheck-hook,  Up: Checking the Distribution
+
+14.4.1 ‘DISTCHECK_CONFIGURE_FLAGS’
+----------------------------------
 
 Building the package involves running ‘./configure’.  If you need to
 supply additional flags to ‘configure’, define them in the
 ‘AM_DISTCHECK_CONFIGURE_FLAGS’ variable in your top-level ‘Makefile.am’.
 The user can still extend or override the flags provided there by
 defining the ‘DISTCHECK_CONFIGURE_FLAGS’ variable, on the command line
-when invoking ‘make’.  It’s worth noting that ‘make distcheck’ needs
+when invoking ‘make’.  It's worth noting that ‘make distcheck’ needs
 complete control over the ‘configure’ options ‘--srcdir’ and ‘--prefix’,
 so those options cannot be overridden by ‘AM_DISTCHECK_CONFIGURE_FLAGS’
 nor by ‘DISTCHECK_CONFIGURE_FLAGS’.
 
-   Also note that developers are encouraged to strive to make their code
-buildable without requiring any special configure option; thus, in
-general, you shouldn’t define ‘AM_DISTCHECK_CONFIGURE_FLAGS’.  However,
-there might be few scenarios in which the use of this variable is
-justified.  GNU ‘m4’ offers an example.  GNU ‘m4’ configures by default
-with its experimental and seldom used "changeword" feature disabled; so
-in this case it is useful to have ‘make distcheck’ run configure with
-the ‘--with-changeword’ option, to ensure that the code for changeword
-support still compiles correctly.  GNU ‘m4’ also employs the
-‘AM_DISTCHECK_CONFIGURE_FLAGS’ variable to stress-test the use of
+   Developers are encouraged to strive to make their code buildable
+without requiring any special configure option; thus, in general, you
+shouldn't define ‘AM_DISTCHECK_CONFIGURE_FLAGS’.  GNU ‘m4’ offers an
+example of when its use is justified, however.  GNU ‘m4’ configures by
+default with its experimental and seldom used ‘changeword’ feature
+disabled; so in this case it is useful to have ‘make distcheck’ run
+configure with the ‘--with-changeword’ option, to ensure that the code
+for changeword support still compiles correctly.  GNU ‘m4’ also employs
+the ‘AM_DISTCHECK_CONFIGURE_FLAGS’ variable to stress-test the use of
 ‘--program-prefix=g’, since at one point the ‘m4’ build system had a bug
 where ‘make installcheck’ was wrongly assuming it could blindly test
-"‘m4’", rather than the just-installed "‘gm4’".
+‘m4’, rather than the just-installed ‘gm4’.
 
-dvi and distcheck
------------------
+&#x1f;
+File: automake.info,  Node: distcheck-hook,  Next: dvi and distcheck,  Prev: DISTCHECK_CONFIGURE_FLAGS,  Up: Checking the Distribution
+
+14.4.2 ‘distcheck-hook’
+-----------------------
+
+If the ‘distcheck-hook’ rule is defined in your top-level ‘Makefile.am’,
+then it will be invoked by ‘distcheck’ after the new distribution has
+been unpacked, but before the unpacked copy is configured and built.
+Your ‘distcheck-hook’ can do almost anything, though as always caution
+is advised.  Generally this hook is used to check for potential
+distribution errors not caught by the standard mechanism.
+
+   ‘distcheck-hook’, as well as ‘AM_DISTCHECK_CONFIGURE_FLAGS’ and
+‘DISTCHECK_CONFIGURE_FLAGS’, are not honored in a subpackage
+‘Makefile.am’, but the flags from ‘AM_DISTCHECK_CONFIGURE_FLAGS’ and
+‘DISTCHECK_CONFIGURE_FLAGS’ are passed down to the ‘configure’ script of
+the subpackage.
+
+&#x1f;
+File: automake.info,  Node: dvi and distcheck,  Next: distcleancheck,  Prev: distcheck-hook,  Up: Checking the Distribution
+
+14.4.3 ‘dvi’ and ‘distcheck’
+----------------------------
 
 Ordinarily, ‘make distcheck’ runs ‘make dvi’.  It does nothing if the
 distribution contains no Texinfo sources.  If the distribution does
@@ -467,7 +580,7 @@
 
    However, you may wish to test the manual by producing ‘pdf’ (e.g., if
 your manual uses images in formats other than ‘eps’), ‘html’ (if you
-don’t have TeX at all), some other format, or just skip the test
+don't have TeX at all), some other format, or just skip the test
 entirely (not recommended).  You can change the target that is run by
 setting the variable ‘AM_DISTCHECK_DVI_TARGET’ in your ‘Makefile.am’;
 for example,
@@ -477,59 +590,51 @@
    To make ‘dvi’ into a do-nothing target, see the example for
 ‘EMPTY_AUTOMAKE_TARGETS’ in *note Third-Party Makefiles::.
 
-distcheck-hook
---------------
-
-If the ‘distcheck-hook’ rule is defined in your top-level ‘Makefile.am’,
-then it will be invoked by ‘distcheck’ after the new distribution has
-been unpacked, but before the unpacked copy is configured and built.
-Your ‘distcheck-hook’ can do almost anything, though as always caution
-is advised.  Generally this hook is used to check for potential
-distribution errors not caught by the standard mechanism.  Note that
-‘distcheck-hook’ as well as ‘AM_DISTCHECK_CONFIGURE_FLAGS’ and
-‘DISTCHECK_CONFIGURE_FLAGS’ are not honored in a subpackage
-‘Makefile.am’, but the flags from ‘AM_DISTCHECK_CONFIGURE_FLAGS’ and
-‘DISTCHECK_CONFIGURE_FLAGS’ are passed down to the ‘configure’ script of
-the subpackage.
+&#x1f;
+File: automake.info,  Node: distcleancheck,  Next: distuninstallcheck,  Prev: dvi and distcheck,  Up: Checking the Distribution
 
-distcleancheck
---------------
+14.4.4 ‘distcleancheck’
+-----------------------
 
-Speaking of potential distribution errors, ‘distcheck’ also ensures that
-the ‘distclean’ rule actually removes all built files.  This is done by
-running ‘make distcleancheck’ at the end of the ‘VPATH’ build.  By
-default, ‘distcleancheck’ will run ‘distclean’ and then make sure the
-build tree has been emptied by running ‘$(distcleancheck_listfiles)’.
-Usually this check will find generated files that you forgot to add to
-the ‘DISTCLEANFILES’ variable (*note Clean::).
+‘distcheck’ ensures that the ‘distclean’ rule actually removes all built
+files.  This is done by running ‘make distcleancheck’ at the end of the
+‘VPATH’ build.  By default, ‘distcleancheck’ will run ‘distclean’ and
+then make sure the build tree has been emptied by running the value of
+the variable ‘$(distcleancheck_listfiles)’.  Often this check will find
+generated files that you forgot to add to the ‘DISTCLEANFILES’ variable
+(*note Clean::).
 
    The ‘distcleancheck’ behavior should be OK for most packages,
 otherwise you have the possibility to override the definition of either
 the ‘distcleancheck’ rule, or the ‘$(distcleancheck_listfiles)’
-variable.  For instance, to disable ‘distcleancheck’ completely, add the
-following rule to your top-level ‘Makefile.am’:
+variable.  For instance, to disable ‘distcleancheck’ completely (not
+recommended), add the following rule to your top-level ‘Makefile.am’:
 
      distcleancheck:
              @:
 
    If you want ‘distcleancheck’ to ignore built files that have not been
-cleaned because they are also part of the distribution, add the
-following definition instead:
+cleaned because they are also part of the distribution, make the
+following definition:
 
      distcleancheck_listfiles = \
        find . -type f -exec sh -c 'test -f $(srcdir)/$$1 || echo $$1' \
             sh '{}' ';'
 
-   The above definition is not the default because it’s usually an error
+   The above definition is not the default because it's usually an error
 if your Makefiles cause some distributed files to be rebuilt when the
-user builds the package.  (Think about the user missing the tool
-required to build the file; or if the required tool is built by your
-package, consider the cross-compilation case where it can’t be run.)
-There is an entry in the FAQ about this (*note Errors with distclean::);
-make sure you read it before playing with ‘distcleancheck_listfiles’.
+user builds the package: consider the user missing the tool required to
+build the file; or if the required tool is built by your package,
+consider the cross-compilation case where it can't be run.
 
-distuninstallcheck
-------------------
+   Please see the (following) section *note Errors with distclean::
+before playing with ‘distcleancheck_listfiles’.
+
+&#x1f;
+File: automake.info,  Node: distuninstallcheck,  Next: Errors with distclean,  Prev: distcleancheck,  Up: Checking the Distribution
+
+14.4.5 ‘distuninstallcheck’
+---------------------------
 
 ‘distcheck’ also checks that the ‘uninstall’ rule works properly, both
 for ordinary and ‘DESTDIR’ builds.  It does this by invoking ‘make
@@ -539,17 +644,157 @@
 
    By default, the checking is done by the ‘distuninstallcheck’ rule,
 and the list of files in the install tree is generated by
-‘$(distuninstallcheck_listfiles)’ (this is a variable whose value is a
-shell command to run that prints the list of files to stdout).
+‘$(distuninstallcheck_listfiles)’.  The value of the latter variable is
+taken to be a shell command to run that prints the list of files to
+stdout.
 
    Either of these can be overridden to modify the behavior of
-‘distcheck’.  For instance, to disable this check completely, you would
-write:
+‘distcheck’.  For instance, to disable this check completely (not
+recommended), you would write:
 
      distuninstallcheck:
              @:
 
 &#x1f;
+File: automake.info,  Node: Errors with distclean,  Prev: distuninstallcheck,  Up: Checking the Distribution
+
+14.4.6 Errors with ‘distclean’
+------------------------------
+
+As explained in the section above (*note Checking the Distribution::),
+‘make distcheck’ attempts to build and check your package for errors.
+One such error you might see is:
+
+     ERROR: files left in build directory after distclean:
+
+The file(s) left in the build directory after ‘make distclean’ has run
+are listed after this error message.  This can happen in two ways:
+
+   • files that were forgotten to be distclean-ed;
+   • distributed files that are erroneously rebuilt.
+
+   In the first case of simple left-over files not intended to be
+distributed, the fix is to include them for cleaning (*note Clean::);
+this is straightforward and doesn't need more explanation.
+
+   The second case, however, is not always easy to understand and fix,
+so let's proceed with an example.  Suppose our package contains a
+program for which we want to build a man page using ‘help2man’.  GNU
+‘help2man’ produces simple manual pages from the ‘--help’ and
+‘--version’ output of other commands (*note (help2man)::).  Because we
+don't want to force our users to install ‘help2man’, we distribute the
+generated man page using the following setup.
+
+     # This Makefile.am is bogus.
+     bin_PROGRAMS = foo
+     foo_SOURCES = foo.c
+     dist_man_MANS = foo.1
+
+     foo.1: foo$(EXEEXT)
+             help2man --output=foo.1 ./foo$(EXEEXT)
+
+   This will effectively distribute the man page.  However, ‘make
+distcheck’ will fail with:
+
+     ERROR: files left in build directory after distclean:
+     ./foo.1
+
+   Why was ‘foo.1’ rebuilt?  Because although distributed, ‘foo.1’
+depends on a non-distributed built file: ‘foo$(EXEEXT)’.  ‘foo$(EXEEXT)’
+is built by the user, so it will always appear to be newer than the
+distributed ‘foo.1’.
+
+   In other words, ‘make distcheck’ caught an inconsistency in our
+package.  Our intent was to distribute ‘foo.1’ so users do not need to
+install ‘help2man’, but since this rule causes this file to be always
+rebuilt, users _do_ need ‘help2man’.  Either we should ensure that
+‘foo.1’ is not rebuilt by users, or there is no point in distributing
+‘foo.1’.
+
+   More generally, the rule is that distributed files should never
+depend on non-distributed built files.  If you distribute something
+generated, distribute all its sources.
+
+   One way to fix the above example, while still distributing ‘foo.1’,
+is to not depend on ‘foo$(EXEEXT)’, but instead on relevant source
+files.  For instance, assuming ‘foo --version’ and ‘foo --help’ do not
+change unless ‘foo.c’ or ‘configure.ac’ change, we could write the
+following ‘Makefile.am’:
+
+     bin_PROGRAMS = foo
+     foo_SOURCES = foo.c
+     dist_man_MANS = foo.1
+
+     foo.1: foo.c $(top_srcdir)/configure.ac
+             $(MAKE) $(AM_MAKEFLAGS) foo$(EXEEXT)
+             help2man --output=foo.1 ./foo$(EXEEXT)
+
+   This way, ‘foo.1’ will not get rebuilt every time ‘foo$(EXEEXT)’
+changes.  The ‘make’ call makes sure ‘foo$(EXEEXT)’ is up-to-date before
+‘help2man’.
+
+   Another step towards ensuring this would be to use separate
+directories for binaries and man pages, and set ‘SUBDIRS’ so that
+binaries are built before man pages.  Unfortunately, this alone is, in
+general, not sufficient.  In order to avoid to avoid concurrency bugs,
+it may be necessary to include wrappers; this is done by GNU Autoconf,
+as mentioned below.
+
+   We could also decide not to distribute ‘foo.1’.  In this case it's
+fine to have ‘foo.1’ dependent upon ‘foo$(EXEEXT)’, since both will have
+to be rebuilt.  However, it might be impossible to build the package in
+a cross-compilation, because building ‘foo.1’ involves an _execution_ of
+‘foo$(EXEEXT)’.  The exception would be if ‘foo’ is a
+platform-independent script, such as ‘help2man’.
+
+   Another context where such errors are common is when distributed
+files are built by tools that are built by the package.  The pattern is
+similar:
+
+     distributed-file: built-tools distributed-sources
+             build-command
+
+should be changed to
+
+     distributed-file: distributed-sources
+             $(MAKE) $(AM_MAKEFLAGS) built-tools
+             build-command
+
+or you could choose not to distribute ‘distributed-file’, if
+cross-compilation does not matter.
+
+   The points made through these examples are worth summarizing:
+
+   • Distributed files should never depend upon non-distributed built
+     files.
+
+   • Distributed files should be distributed with all their
+     dependencies.
+
+   • If a file is _intended_ to be rebuilt by users, then there is no
+     point in distributing it.
+
+   Real-world examples for ‘help2man’:
+
+   • Autoconf takes the approach described above, including man pages in
+     its releases.  A wrapper for each script is needed to avoid
+     concurrency problems.  See its source file ‘autoconf/man/local.mk’,
+     which has a good discussion of the necessary additional details.
+
+   • Automake itself takes another approach: it does _not_ include man
+     pages in distributions; thus, every user generates them when
+     building from the release tarballs.  This is ok (only) because
+     Automake also includes a copy of the ‘help2man’ script, which is
+     plausible because ‘help2man’ is small, self-contained, and
+     platform-independent.  See the source file ‘automake/doc/local.mk’.
+
+   If you're desperate, it's possible to disable this check completely
+by setting ‘distcleancheck_listfiles’ (*note distcleancheck::).  Make
+sure you understand the reason why ‘make distcheck’ complains first.
+‘distcleancheck_listfiles’ is a way to _hide_ errors, not to fix them.
+You can always do better.
+
+&#x1f;
 File: automake.info,  Node: The Types of Distributions,  Prev: Checking the Distribution,  Up: Dist
 
 14.5 The Types of Distributions
@@ -561,9 +806,10 @@
 ‘dist-gzip’
      Generate a ‘gzip’ tar archive of the distribution.  This is the
      only format enabled by default.  By default, this rule makes ‘gzip’
-     use a compression option of ‘--best’.  To make it use a different
-     one, set the ‘GZIP_ENV’ environment variable.  For example, ‘make
-     dist-gzip GZIP_ENV=-7’.
+     use a compression option of ‘-9’ (more widely supported than
+     ‘--best’).  To make it use a different one, set the ‘GZIP_ENV’
+     environment variable.  For example, ‘make dist-gzip GZIP_ENV=-7’.
+     ‘GZIP_ENV’ is not used when decompressing.
 
 ‘dist-bzip2’
      Generate a ‘bzip2’ tar archive of the distribution.  bzip2 archives
@@ -656,7 +902,7 @@
    The minimal unit of testing is usually called _test case_, or simply
 _test_.  How a test case is defined or delimited, and even what exactly
 _constitutes_ a test case, depends heavily on the testing paradigm
-and/or framework in use, so we won’t attempt any more precise
+and/or framework in use, so we won't attempt any more precise
 definition.  The set of the test cases for a given program or system
 constitutes its _testsuite_.
 
@@ -665,11 +911,11 @@
 analyzes their outcomes, and reports or registers these outcomes
 appropriately.  Again, the details of how this is accomplished (and how
 the developer and user can influence it or interface with it) varies
-wildly, and we’ll attempt no precise definition.
+wildly, and we'll attempt no precise definition.
 
    A test is said to _pass_ when it can determine that the condition or
-behaviour it means to verify holds, and is said to _fail_ when it can
-determine that such condition of behaviour does _not_ hold.
+behavior it means to verify holds, and is said to _fail_ when it can
+determine that such condition of behavior does _not_ hold.
 
    Sometimes, tests can rely on non-portable tools or prerequisites, or
 simply make no sense on a given system (for example, a test checking a
@@ -681,8 +927,8 @@
 reported though, so that the user will be aware that not all of the
 testsuite has been run.
 
-   It’s not uncommon, especially during early development stages, that
-some tests fail for known reasons, and that the developer doesn’t want
+   It's not uncommon, especially during early development stages, that
+some tests fail for known reasons, and that the developer doesn't want
 to tackle these failures immediately (this is especially true when the
 failing tests deal with corner cases).  In this situation, the better
 policy is to declare that each of those failures is an _expected
@@ -691,8 +937,8 @@
 special kind of failure called _unexpected pass_ (or _xpass_).
 
    Many testing environments and frameworks distinguish between test
-failures and hard errors.  As we’ve seen, a test failure happens when
-some invariant or expected behaviour of the software under test is not
+failures and hard errors.  As we've seen, a test failure happens when
+some invariant or expected behavior of the software under test is not
 met.  A _hard error_ happens when e.g., the set-up of a test case
 scenario fails, or when some other unexpected or highly undesirable
 condition is encountered (for example, the program under test
@@ -718,9 +964,9 @@
 
 If the special variable ‘TESTS’ is defined, its value is taken to be a
 list of programs or scripts to run in order to do the testing.  Under
-the appropriate circumstances, it’s possible for ‘TESTS’ to list also
+the appropriate circumstances, it's possible for ‘TESTS’ to list also
 data files to be passed to one or more test scripts defined by different
-means (the so-called “log compilers”, *note Parallel Test Harness::).
+means (the so-called "log compilers", *note Parallel Test Harness::).
 
    Test scripts can be executed serially or concurrently.  Automake
 supports both these kinds of test execution, with the parallel test
@@ -731,7 +977,7 @@
    By default, only the exit statuses of the test scripts are considered
 when determining the testsuite outcome.  But Automake allows also the
 use of more complex test protocols, either standard (*note Using the TAP
-test protocol::) or custom (*note Custom Test Drivers::).  You can’t
+test protocol::) or custom (*note Custom Test Drivers::).  You can't
 enable such protocols when the serial harness is used, though.  In the
 rest of this section we are going to concentrate mostly on protocol-less
 tests, since we cover test protocols in a later section (again, *note
@@ -799,7 +1045,7 @@
 test results and the summary are colored appropriately.  The developer
 and the user can disable colored output by setting the ‘make’ variable
 ‘AM_COLOR_TESTS=no’; the user can in addition force colored output even
-without a connecting terminal with ‘AM_COLOR_TESTS=always’.  It’s also
+without a connecting terminal with ‘AM_COLOR_TESTS=always’.  It's also
 worth noting that some ‘make’ implementations, when used in parallel
 mode, have slightly different semantics (*note (autoconf)Parallel
 make::), which can break the automatic detection of a connection to a
@@ -816,7 +1062,7 @@
 
    Automake ensures that each file listed in ‘TESTS’ is built before it
 is run; you can list both source and derived programs (or scripts) in
-‘TESTS’; the generated rule will look both in ‘srcdir’ and ‘‘..’’.  For
+‘TESTS’; the generated rule will look both in ‘srcdir’ and '‘..’'.  For
 instance, you might want to run a C program as a test.  To do this you
 would list its name in ‘TESTS’ and also in ‘check_PROGRAMS’, and then
 specify it as you would any other program.
@@ -856,7 +1102,7 @@
 close-on-exec flag on file descriptors opened with the ‘exec’ builtin,
 thus rendering an idiom like ‘AM_TESTS_ENVIRONMENT = exec 9>&2;’
 ineffectual.  This issue also affects some Bourne shells, such as the
-HP-UX’s ‘/bin/sh’.
+HP-UX's ‘/bin/sh’.
 
      AM_TESTS_ENVIRONMENT = \
      ## Some environment initializations are kept in a separate shell
@@ -896,7 +1142,7 @@
 --------------------------------------------------
 
 First, note that today the use of this harness is strongly discouraged
-in favour of the parallel test harness (*note Parallel Test Harness::).
+in favor of the parallel test harness (*note Parallel Test Harness::).
 Still, there are a _few_ situations when the advantages offered by the
 parallel harness are irrelevant, and when test concurrency can even
 cause tricky problems.  In those cases, it might make sense to still use
@@ -905,8 +1151,8 @@
 
    The serial test harness is enabled by the Automake option
 ‘serial-tests’.  It operates by simply running the tests serially, one
-at the time, without any I/O redirection.  It’s up to the user to
-implement logging of tests’ output, if that’s required or desired.
+at the time, without any I/O redirection.  It's up to the user to
+implement logging of tests' output, if that's required or desired.
 
    For historical and implementation reasons, the ‘AM_TESTS_ENVIRONMENT’
 variable is _not_ supported by this harness (it will be silently ignored
@@ -919,14 +1165,14 @@
      TESTS_ENVIRONMENT = $(PERL) -Mstrict -w
      TESTS = foo.pl bar.pl baz.pl
 
-It’s important to note that the use of ‘TESTS_ENVIRONMENT’ endorsed here
+It's important to note that the use of ‘TESTS_ENVIRONMENT’ endorsed here
 would be _invalid_ with the parallel harness.  That harness provides a
 more elegant way to achieve the same effect, with the further benefit of
 freeing the ‘TESTS_ENVIRONMENT’ variable for the user (*note Parallel
 Test Harness::).
 
    Another, less serious limitation of the serial harness is that it
-doesn’t distinguish between simple failures and hard errors; this is for
+doesn't distinguish between simple failures and hard errors; this is for
 historical reasons, and might be fixed in future Automake versions.
 
 &#x1f;
@@ -935,7 +1181,7 @@
 15.2.3 Parallel Test Harness
 ----------------------------
 
-By default, Automake generated a parallel (concurrent) test harness.  It
+By default, Automake generates a parallel (concurrent) test harness.  It
 features automatic collection of the test scripts output in ‘.log’
 files, concurrent execution of tests with ‘make -j’, specification of
 inter-test dependencies, lazy reruns of tests that have not completed in
@@ -944,7 +1190,7 @@
    The parallel test harness operates by defining a set of ‘make’ rules
 that run the test scripts listed in ‘TESTS’, and, for each such script,
 save its output in a corresponding ‘.log’ file and its results (and
-other “metadata”, *note API for Custom Test Drivers::) in a
+other "metadata", *note API for Custom Test Drivers::) in a
 corresponding ‘.trs’ (as in Test ReSults) file.  The ‘.log’ file will
 contain all the output emitted by the test on its standard output and
 its standard error.  The ‘.trs’ file will contain, among the other
@@ -953,7 +1199,10 @@
    The parallel test harness will also create a summary log file,
 ‘TEST_SUITE_LOG’, which defaults to ‘test-suite.log’ and requires a
 ‘.log’ suffix.  This file depends upon all the ‘.log’ and ‘.trs’ files
-created for the test scripts listed in ‘TESTS’.
+created for the test scripts listed in ‘TESTS’.  It contains the output
+of all tests that failed, encountered a hard error, succeeded
+unexpectedly, or--unless the variable ‘IGNORE_SKIPPED_LOGS’ is set to a
+non-empty value--were skipped.
 
    As with the serial harness above, by default one status line is
 printed per completed test, and a short summary after the suite has
@@ -981,7 +1230,7 @@
 listed in ‘TEST_EXTENSIONS’.
 
    For tests that match an extension ‘.EXT’ listed in ‘TEST_EXTENSIONS’,
-you can provide a custom “test runner” using the variable
+you can provide a custom "test runner" using the variable
 ‘EXT_LOG_COMPILER’ (note the upper-case extension) and pass options in
 ‘AM_EXT_LOG_FLAGS’ and allow the user to pass options in
 ‘EXT_LOG_FLAGS’.  It will cause all tests with this extension to be
@@ -1003,7 +1252,7 @@
 ‘baz.log’, respectively.  The ‘foo.trs’, ‘bar.trs’ and ‘baz.trs’ files
 will be automatically produced as a side-effect.
 
-   It’s important to note that, differently from what we’ve seen for the
+   It's important to note that, differently from what we've seen for the
 serial test harness (*note Serial Test Harness::), the
 ‘AM_TESTS_ENVIRONMENT’ and ‘TESTS_ENVIRONMENT’ variables _cannot_ be
 used to define a custom test runner; the ‘LOG_COMPILER’ and ‘LOG_FLAGS’
@@ -1025,7 +1274,7 @@
 
           env TESTS="foo.test bar.test" make -e check
 
-     If you’re using a recursive make setup, you’ll probably also need
+     If you're using a recursive make setup, you'll probably also need
      to override ‘SUBDIRS’:
 
           env TESTS="foo.test bar.test" make -e check SUBDIRS=
@@ -1146,28 +1395,28 @@
 ‘.log’ and ‘.trs’ files associated to these test runs, and to display
 the test results on the console.  It is responsibility of the author of
 the test driver to ensure that it implements all the above steps
-meaningfully and correctly; Automake isn’t and can’t be of any help
+meaningfully and correctly; Automake isn't and can't be of any help
 here.  On the other hand, the Automake-provided code for testsuite
 summary generation offers support for test drivers allowing several test
 results per test script, if they take care to register such results
 properly (*note Log files generation and test results recording::).
 
-   The exact details of how test scripts’ results are to be determined
+   The exact details of how test scripts' results are to be determined
 and analyzed is left to the individual drivers.  Some drivers might only
 consider the test script exit status (this is done for example by the
 default test driver used by the parallel test harness, described in the
 previous section).  Other drivers might implement more complex and
 advanced test protocols, which might require them to parse and interpret
-the output emitted by the test script they’re running (examples of such
+the output emitted by the test script they're running (examples of such
 protocols are TAP and SubUnit).
 
-   It’s very important to note that, even when using custom test
+   It's very important to note that, even when using custom test
 drivers, most of the infrastructure described in the previous section
 about the parallel harness remains in place; this includes:
 
    • list of test scripts defined in ‘TESTS’, and overridable at runtime
      through the redefinition of ‘TESTS’ or ‘TEST_LOGS’;
-   • concurrency through the use of ‘make’’s option ‘-j’;
+   • concurrency through the use of ‘make’'s option ‘-j’;
    • per-test ‘.log’ and ‘.trs’ files, and generation of a summary
      ‘.log’ file from them;
    • ‘recheck’ target, ‘RECHECK_LOGS’ variable, and lazy reruns of
@@ -1244,35 +1493,39 @@
 It is _mandatory_ that it understands all of them (even if the exact
 interpretation of the associated semantics can legitimately change
 between a test driver and another, and even be a no-op in some drivers).
+Options are separated from their arguments by whitespace.(1)
 
 Here is the list of options:
 
-‘--test-name=NAME’
+‘--test-name NAME’
      The name of the test, with VPATH prefix (if any) removed.  This can
      have a suffix and a directory component (as in e.g.,
      ‘sub/foo.test’), and is mostly meant to be used in console reports
      about testsuite advancements and results (*note Testsuite progress
      output::).
-‘--log-file=PATH.log’
+‘--log-file PATH.log’
      The ‘.log’ file the test driver must create (*note Basics of test
      metadata::).  If it has a directory component (as in e.g.,
      ‘sub/foo.log’), the test harness will ensure that such directory
      exists _before_ the test driver is called.
-‘--trs-file=PATH.trs’
+‘--trs-file PATH.trs’
      The ‘.trs’ file the test driver must create (*note Basics of test
      metadata::).  If it has a directory component (as in e.g.,
      ‘sub/foo.trs’), the test harness will ensure that such directory
      exists _before_ the test driver is called.
-‘--color-tests={yes|no}’
+‘--color-tests {yes|no}’
      Whether the console output should be colorized or not (*note Simple
      tests and color-tests::, to learn when this option gets activated
-     and when it doesn’t).
-‘--expect-failure={yes|no}’
+     and when it doesn't).
+‘--collect-skipped-logs {yes|no}’
+     Whether to include the logs of skipped tests in the global
+     ‘test-suite.log’ file.
+‘--expect-failure {yes|no}’
      Whether the tested program is expected to fail.
-‘--enable-hard-errors={yes|no}’
-     Whether “hard errors” in the tested program should be treated
+‘--enable-hard-errors {yes|no}’
+     Whether "hard errors" in the tested program should be treated
      differently from normal failures or not (the default should be
-     ‘yes’).  The exact meaning of “hard error” is highly dependent from
+     ‘yes’).  The exact meaning of "hard error" is highly dependent from
      the test protocols or conventions in use.
 ‘--’
      Explicitly terminate the list of options.
@@ -1281,11 +1534,21 @@
 to be run, and all the following ones are command-line options and
 arguments for this program.
 
-   Note that the exact semantics attached to the ‘--color-tests’,
-‘--expect-failure’ and ‘--enable-hard-errors’ options are left up to the
-individual test drivers.  Still, having a behaviour compatible or at
-least similar to that provided by the default driver is advised, as that
-would offer a better consistency and a more pleasant user experience.
+   Exact semantics attached to the ‘--color-tests’,
+‘--collect-skipped-logs’, ‘--expect-failure’, and ‘--enable-hard-errors’
+options are left up to the individual test drivers.  Still, having a
+behavior compatible or at least similar to that provided by the default
+driver is advised, as that results in better consistency and thus a more
+pleasant user experience.
+
+   ---------- Footnotes ----------
+
+   (1) Regrettably, older versions of this manual stated that option
+arguments should be joined to their options with a ‘=’ character, rather
+than passed as in the following argument word as shown here.  The syntax
+with ‘=’ has never been accepted by the test drivers supplied with
+Automake, and has never been produced by ‘Makefile’s generated by
+Automake.
 
 &#x1f;
 File: automake.info,  Node: Log files generation and test results recording,  Next: Testsuite progress output,  Prev: Command-line arguments for test drivers,  Up: API for Custom Test Drivers
@@ -1306,7 +1569,7 @@
 custom reStructuredText fields.  This metadata is expected to be
 employed in various ways by the parallel test harness; for example, to
 count the test results when printing the testsuite summary, or to decide
-which tests to re-run upon ‘make recheck’.  Unrecognized metadata in a
+which tests to rerun upon ‘make recheck’.  Unrecognized metadata in a
 ‘.trs’ file is currently ignored by the harness, but this might change
 in the future.  The list of currently recognized metadata follows.
 
@@ -1328,7 +1591,7 @@
      If this field is present and defined to ‘no’, then the
      corresponding test script will _not_ be run upon a ‘make recheck’.
      What happens when two or more ‘:recheck:’ fields are present in the
-     same ‘.trs’ file is undefined behaviour.
+     same ‘.trs’ file is undefined behavior.
 
 ‘:copy-in-global-log:’
      If this field is present and defined to ‘no’, then the content of
@@ -1338,21 +1601,21 @@
      also be just a waste of space in normal situations, e.g., when a
      test script is successful.  What happens when two or more
      ‘:copy-in-global-log:’ fields are present in the same ‘.trs’ file
-     is undefined behaviour.
+     is undefined behavior.
 
 ‘:test-global-result:’
      This is used to declare the "global result" of the script.
      Currently, the value of this field is needed only to be reported
      (more or less verbatim) in the generated global log file
-     ‘$(TEST_SUITE_LOG)’, so it’s quite free-form.  For example, a test
+     ‘$(TEST_SUITE_LOG)’, so it's quite free-form.  For example, a test
      script which runs 10 test cases, 6 of which pass and 4 of which are
      skipped, could reasonably have a ‘PASS/SKIP’ value for this field,
      while a test script which runs 19 successful tests and one failed
      test could have an ‘ALMOST PASSED’ value.  What happens when two or
      more ‘:test-global-result:’ fields are present in the same ‘.trs’
-     file is undefined behaviour.
+     file is undefined behavior.
 
-Let’s see a small example.  Assume a ‘.trs’ file contains the following
+Let's see a small example.  Assume a ‘.trs’ file contains the following
 lines:
 
      :test-result: PASS server starts
@@ -1363,7 +1626,7 @@
      :test-result: SKIP HTTPS request (TLS library wasn't available)
      :test-result: PASS server stops
 
-Then the corresponding test script will be re-run by ‘make check’, will
+Then the corresponding test script will be rerun by ‘make check’, will
 contribute with _five_ test results to the testsuite summary (three of
 these tests being successful, one failed, and one skipped), and the
 content of the corresponding ‘.log’ file will _not_ be copied into the
@@ -1389,11 +1652,11 @@
 
    Remember that consistency is good; so, if possible, try to be
 consistent with the output of the built-in Automake test drivers,
-providing a similar “look & feel”.  In particular, the testsuite
+providing a similar "look & feel".  In particular, the testsuite
 progress output should be colorized when the ‘--color-tests’ is passed
 to the driver.  On the other end, if you are using a known and
 widespread test protocol with well-established implementations, being
-consistent with those implementations’ output might be a good idea too.
+consistent with those implementations' output might be a good idea too.
 
 &#x1f;
 File: automake.info,  Node: Using the TAP test protocol,  Next: DejaGnu Tests,  Prev: Custom Test Drivers,  Up: Tests
@@ -1405,7 +1668,7 @@
 
 * Introduction to TAP::
 * Use TAP with the Automake test harness::
-* Incompatibilities with other TAP parsers and drivers::
+* Incompatibility with other TAP parsers and drivers::
 * Links and external resources on TAP::
 
 &#x1f;
@@ -1416,8 +1679,8 @@
 
 TAP, the Test Anything Protocol, is a simple text-based interface
 between testing modules or programs and a test harness.  The tests (also
-called “TAP producers” in this context) write test results in a simple
-format on standard output; a test harness (also called “TAP consumer”)
+called "TAP producers" in this context) write test results in a simple
+format on standard output; a test harness (also called "TAP consumer")
 will parse and interpret these results, and properly present them to the
 user, and/or register them for later analysis.  The exact details of how
 this is accomplished can vary among different test harnesses.  The
@@ -1443,14 +1706,14 @@
 in their testsuite.
 
 &#x1f;
-File: automake.info,  Node: Use TAP with the Automake test harness,  Next: Incompatibilities with other TAP parsers and drivers,  Prev: Introduction to TAP,  Up: Using the TAP test protocol
+File: automake.info,  Node: Use TAP with the Automake test harness,  Next: Incompatibility with other TAP parsers and drivers,  Prev: Introduction to TAP,  Up: Using the TAP test protocol
 
 15.4.2 Use TAP with the Automake test harness
 ---------------------------------------------
 
 Currently, the TAP driver that comes with Automake requires some by-hand
-steps on the developer’s part (this situation should hopefully be
-improved in future Automake versions).  You’ll have to grab the
+steps on the developer's part (this situation should hopefully be
+improved in future Automake versions).  You'll have to grab the
 ‘tap-driver.sh’ script from the Automake distribution by hand, copy it
 in your source tree, and use the Automake support for third-party test
 drivers to instruct the harness to use the ‘tap-driver.sh’ script and
@@ -1475,7 +1738,7 @@
 ‘--no-comments’
      Revert the effects of ‘--comments’.
 ‘--merge’
-     Instruct the test driver to merge the test scripts’ standard error
+     Instruct the test driver to merge the test scripts' standard error
      into their standard output.  This is necessary if you want to
      ensure that diagnostics from the test scripts are displayed in the
      correct order relative to test results; this can be of great help
@@ -1485,17 +1748,17 @@
      standard error looks like a test result.
 ‘--no-merge’
      Revert the effects of ‘--merge’.
-‘--diagnostic-string=STRING’
+‘--diagnostic-string STRING’
      Change the string that introduces TAP diagnostics from the default
-     value of “‘#’” to ‘STRING’.  This can be useful if your TAP-based
+     value of "‘#’" to ‘STRING’.  This can be useful if your TAP-based
      test scripts produce verbose output on which they have limited
      control (because, say, the output comes from other tools invoked in
      the scripts), and it might contain text that gets spuriously
      interpreted as TAP diagnostics: such an issue can be solved by
      redefining the string that activates TAP diagnostics to a value you
-     know won’t appear by chance in the tests’ output.  Note however
-     that this feature is non-standard, as the “official” TAP protocol
-     does not allow for such a customization; so don’t use it if you can
+     know won't appear by chance in the tests' output.  Note however
+     that this feature is non-standard, as the "official" TAP protocol
+     does not allow for such a customization; so don't use it if you can
      avoid it.
 
 Here is an example of how the TAP driver can be set up and used.
@@ -1570,31 +1833,32 @@
      exit status: 0
 
 &#x1f;
-File: automake.info,  Node: Incompatibilities with other TAP parsers and drivers,  Next: Links and external resources on TAP,  Prev: Use TAP with the Automake test harness,  Up: Using the TAP test protocol
+File: automake.info,  Node: Incompatibility with other TAP parsers and drivers,  Next: Links and external resources on TAP,  Prev: Use TAP with the Automake test harness,  Up: Using the TAP test protocol
 
-15.4.3 Incompatibilities with other TAP parsers and drivers
------------------------------------------------------------
+15.4.3 Incompatibility with other TAP parsers and drivers
+---------------------------------------------------------
 
 For implementation or historical reasons, the TAP driver and harness as
-implemented by Automake have some minor incompatibilities with the
+implemented by Automake have some minor compatibility issues with the
 mainstream versions, which you should be aware of.
 
-   • A ‘Bail out!’ directive doesn’t stop the whole testsuite, but only
-     the test script it occurs in.  This doesn’t follow TAP
+   • A ‘Bail out!’ directive doesn't stop the whole testsuite, but only
+     the test script it occurs in.  This doesn't follow TAP
      specifications, but on the other hand it maximizes compatibility
-     (and code sharing) with the “hard error” concept of the default
+     (and code sharing) with the "hard error" concept of the default
      testsuite driver.
    • The ‘version’ and ‘pragma’ directives are not supported.
    • The ‘--diagnostic-string’ option of our driver allows modification
      of the string that introduces TAP diagnostics from the default
-     value of “‘#’”.  The standard TAP protocol currently has no way to
+     value of "‘#’".  The standard TAP protocol currently has no way to
      allow this, so if you use it your diagnostic will be lost to more
      compliant tools like ‘prove’ and ‘Test::Harness’
    • And there are probably some other small and yet undiscovered
-     incompatibilities, especially in corner cases or with rare usages.
+     compatibility issues, especially in corner cases or with rare
+     usages.
 
 &#x1f;
-File: automake.info,  Node: Links and external resources on TAP,  Prev: Incompatibilities with other TAP parsers and drivers,  Up: Using the TAP test protocol
+File: automake.info,  Node: Links and external resources on TAP,  Prev: Incompatibility with other TAP parsers and drivers,  Up: Using the TAP test protocol
 
 15.4.4 Links and external resources on TAP
 ------------------------------------------
@@ -1610,7 +1874,7 @@
      distribution of ‘perl’ and ‘Test::Harness’
      (https://metacpan.org/pod/distribution/Test-Harness/lib/Test/Harness.pm).
    • The TAP wiki (https://testanything.org/).
-   • A “gentle introduction” to testing for Perl coders:
+   • A "gentle introduction" to testing for Perl coders:
      ‘Test::Tutorial’
      (https://metacpan.org/pod/distribution/Test-Simple/lib/Test/Tutorial.pod).
    •  ‘Test::Simple’
@@ -1646,7 +1910,7 @@
 not take into account host and target names.
 
    The contents of the variable ‘RUNTESTFLAGS’ are passed to the
-‘runtest’ invocation.  This is considered a “user variable” (*note User
+‘runtest’ invocation.  This is considered a "user variable" (*note User
 Variables::).  If you need to set ‘runtest’ flags in ‘Makefile.am’, you
 can use ‘AM_RUNTESTFLAGS’ instead.
 
@@ -1738,7 +2002,7 @@
 (listing ‘version.sh’ in ‘CONFIG_STATUS_DEPENDENCIES’, and distributing
 this file is up to the user), and that it uses the obsolete form of
 ‘AC_INIT’ and ‘AM_INIT_AUTOMAKE’.  Upgrading to the new syntax is not
-straightforward, because shell variables are not allowed in ‘AC_INIT’’s
+straightforward, because shell variables are not allowed in ‘AC_INIT’'s
 arguments.  We recommend that ‘version.sh’ be replaced by an M4 file
 that is included by ‘configure.ac’:
 
@@ -1765,7 +2029,7 @@
 &#x1f;
 File: automake.info,  Node: Options,  Next: Miscellaneous,  Prev: Rebuilding,  Up: Top
 
-17 Changing Automake’s Behavior
+17 Changing Automake's Behavior
 *******************************
 
 * Menu:
@@ -1885,24 +2149,24 @@
 
 ‘no-dependencies’
      This is similar to using ‘--ignore-deps’ on the command line, but
-     is useful for those situations where you don’t have the necessary
+     is useful for those situations where you don't have the necessary
      bits to make automatic dependency tracking work (*note
      Dependencies::).  In this case the effect is to effectively disable
      automatic dependency tracking.
 
 ‘no-dist’
-     Don’t emit any code related to ‘dist’ target.  This is useful when
+     Don't emit any code related to ‘dist’ target.  This is useful when
      a package has its own method for making distributions.
 
 ‘no-dist-built-sources’
-     Don’t build ‘BUILT_SOURCES’ as part of ‘dist’.  This option can be
+     Don't build ‘BUILT_SOURCES’ as part of ‘dist’.  This option can be
      set if building the distribution only requires the source files,
-     and doesn’t compile anything as a side-effect.  The default is for
+     and doesn't compile anything as a side-effect.  The default is for
      ‘$(distdir)’ to depend on ‘$(BUILT_SOURCES)’ because it is common,
      at least among GNU packages, to want to build the program to
      generate man pages with ‘help2man’ (*note Errors with distclean::).
      Admittedly the default behavior should perhaps be to omit the
-     dependency, but to preserve compatibility, we don’t want to change
+     dependency, but to preserve compatibility, we don't want to change
      it now.
 
 ‘no-dist-gzip’
@@ -1935,9 +2199,14 @@
      are ordinarily automatically provided by Automake.
 
 ‘no-texinfo.tex’
-     Don’t require ‘texinfo.tex’, even if there are texinfo files in
+     Don't require ‘texinfo.tex’, even if there are texinfo files in
      this directory.
 
+‘posix’
+     Generate the special target ‘.POSIX’ as the first non-comment line
+     in the ‘Makefile.in’ files.  This alters the behavior of the ‘make’
+     program.  *Note make: (The GNU Make Manual)Special targets.
+
 ‘serial-tests’
      Enable the older serial test suite harness for ‘TESTS’ (*note
      Serial Test Harness::, for more information).
@@ -1961,7 +2230,7 @@
 
      Make the ‘installcheck’ rule check that installed scripts and
      programs support the ‘--help’ and ‘--version’ options.  This also
-     provides a basic check that the program’s run-time dependencies are
+     provides a basic check that the program's run-time dependencies are
      satisfied after installation.
 
      In a few situations, programs (or scripts) have to be exempted from
@@ -2059,7 +2328,7 @@
 18 Miscellaneous Rules
 **********************
 
-There are a few rules and variables that didn’t fit anywhere else.
+There are a few rules and variables that didn't fit anywhere else.
 
 * Menu:
 
@@ -2174,6 +2443,10 @@
 the generated suffixes list, followed by Automake generated suffixes not
 already in the list.
 
+   Automake disables the Make program's built-in rules with a
+‘.SUFFIXES:’ rule, and then adds whatever suffixes are necessary.
+Automake also disables GNU Make's built-in pattern rules.
+
 &#x1f;
 File: automake.info,  Node: Include,  Next: Conditionals,  Prev: Miscellaneous,  Up: Top
 
@@ -2198,7 +2471,7 @@
    Note that if a fragment is included inside a conditional, then the
 condition applies to the entire contents of that fragment.
 
-   Makefile fragments included this way are always distributed because
+   ‘Makefile’ fragments included this way are always distributed because
 they are needed to rebuild ‘Makefile.in’.
 
    Inside a fragment, the construct ‘%reldir%’ is replaced with the
@@ -2208,11 +2481,17 @@
 synonym for ‘%reldir%’, and ‘%C%’ is a synonym for ‘%canon_reldir%’.
 
    A special feature is that if the fragment is in the same directory as
-the base ‘Makefile.am’ (i.e., ‘%reldir%’ is ‘.’), then ‘%reldir%’ and
-‘%canon_reldir%’ will expand to the empty string as well as eat, if
-present, a following slash or underscore respectively.
+the base ‘Makefile.am’ (i.e., ‘%reldir%’ is ‘.’), then:
 
-   Thus, a makefile fragment might look like this:
+‘%reldir%’
+     together with a following slash expands to the empty string,
+     otherwise it expands to a dot;
+
+‘%canon_reldir%’
+     together with a following underscore expands to the empty string,
+     otherwise it expands to an underscore.
+
+   Thus, a ‘Makefile’ fragment might look like this:
 
      bin_PROGRAMS += %reldir%/mumble
      %canon_reldir%_mumble_SOURCES = %reldir%/one.c
@@ -2261,6 +2540,15 @@
      run.  If ‘AM_CONDITIONAL’ is run conditionally (e.g., in a shell
      ‘if’ statement), then the result will confuse ‘automake’.
 
+     For portability, it is best to use shell operators ‘&&’ and ‘||’
+     and parentheses, when constructing a compound CONDITION using the
+     ‘test’ command, and not the ‘-a’ and ‘-o’ options and parentheses
+     as options to ‘test’, all of which have been marked obsolescent by
+     POSIX
+     (<https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html#tag_20_128_161>).
+     The name ‘test’ is also more portable than ‘’.  *Note
+     (autoconf)Limitations of Builtins::.
+
    Conditionals typically depend upon options that the user provides to
 the ‘configure’ script.  Here is an example of how to write a
 conditional that is true if the user uses the ‘--enable-debug’ option.
@@ -2316,7 +2604,7 @@
      cause ‘automake’ to output the rules for the respective files only
      for the given condition.
 
-   ‘AM_COND_IF’ macros may be nested when m4 quotation is used properly
+   ‘AM_COND_IF’ macros may be nested when M4 quotation is used properly
 (*note (autoconf)M4 Quotation::).
 
    Here is an example of how to define a conditional config file:
@@ -2376,6 +2664,7 @@
 * Make verbosity::              Make is verbose by default
 * Tricks For Silencing Make::   Standard and generic ways to silence make
 * Automake Silent Rules::       How Automake can help in silencing make
+* Unsilencing Automake::        Showing commands.
 
 &#x1f;
 File: automake.info,  Node: Make verbosity,  Next: Tricks For Silencing Make,  Up: Silencing Make
@@ -2384,9 +2673,9 @@
 ===============================
 
 Normally, when executing the set of rules associated with a target,
-‘make’ prints each rule before it is executed.  This behaviour, while
-having been in place for a long time, and being even mandated by the
-POSIX standard, starkly violates the “silence is golden” UNIX
+‘make’ prints each rule before it is executed.  This behavior, despite
+having been in place since the beginning of ‘make’, and being mandated
+by the POSIX standard, starkly violates the "silence is golden" UNIX
 principle(1):
 
      When a program has nothing interesting or surprising to say, it
@@ -2394,16 +2683,18 @@
      unobtrusively, with a minimum of fuss and bother.  Silence is
      golden.
 
-   In fact, while such verbosity of ‘make’ can theoretically be useful
-to track bugs and understand reasons of failures right away, it can also
-hide warning and error messages from ‘make’-invoked tools, drowning them
-in a flood of uninteresting and seldom useful messages, and thus
-allowing them to go easily undetected.
-
-   This problem can be very annoying, especially for developers, who
-usually know quite well what’s going on behind the scenes, and for whom
-the verbose output from ‘make’ ends up being mostly noise that hampers
-the easy detection of potentially important warning messages.
+   The traditional verbosity of ‘make’ is understandable, as it is
+useful, often necessary, in order to understand reasons of failures.
+However, it can also hide warning and error messages from ‘make’-invoked
+tools, drowning them in uninteresting and seldom useful messages, and
+thus allowing them to easily go undetected.
+
+   This can be quite problematic, especially for developers, who usually
+know quite well what's going on behind the scenes, and for whom the
+verbose output from ‘make’ ends up being mostly noise that hampers the
+easy detection of potentially important warning messages.
+
+   So Automake provides some support for silencing ‘make’.
 
    ---------- Footnotes ----------
 
@@ -2415,9 +2706,9 @@
 21.2 Standard and generic ways to silence Make
 ==============================================
 
-Here we describe some common idioms/tricks to obtain a quieter make
+Here we describe some common idioms/tricks to obtain a quieter ‘make’
 output, with their relative advantages and drawbacks.  In the next
-section (*note Automake Silent Rules::) we’ll see how Automake can help
+section (*note Automake Silent Rules::) we'll see how Automake can help
 in this respect, providing more elaborate and flexible idioms.
 
    • ‘make -s’
@@ -2428,18 +2719,18 @@
      The ‘-s’ flag is mandated by POSIX, universally supported, and its
      purpose and function are easy to understand.
 
-     But it also has its serious limitations too.  First of all, it
-     embodies an “all or nothing” strategy, i.e., either everything is
-     silenced, or nothing is; this lack of granularity can sometimes be
-     a fatal flaw.  Moreover, when the ‘-s’ flag is used, the ‘make’
-     output might turn out to be too terse; in case of errors, the user
-     won’t be able to easily see what rule or command have caused them,
-     or even, in case of tools with poor error reporting, what the
-     errors were!
+     But it also has serious limitations.  First of all, it embodies an
+     "all or nothing" strategy, i.e., either everything is silenced, or
+     nothing is; in practice, this lack of granularity makes it
+     unsuitable as a general solution.  When the ‘-s’ flag is used, the
+     ‘make’ output might turn out to be too terse; in case of errors,
+     the user won't be able to easily see what rule or command have
+     caused them, or even, in case of tools with poor error reporting,
+     what the errors were.
 
    • ‘make >/dev/null || make’
 
-     Apparently, this perfectly obeys the “silence is golden” rule:
+     Apparently, this perfectly obeys the "silence is golden" rule:
      warnings from stderr are passed through, output reporting is done
      only in case of error, and in that case it should provide a
      verbose-enough report to allow an easy determination of the error
@@ -2447,7 +2738,7 @@
 
      However, calling ‘make’ two times in a row might hide errors
      (especially intermittent ones), or subtly change the expected
-     semantics of the ‘make’ calls — these things can clearly make
+     semantics of the ‘make’ calls--these things can clearly make
      debugging and error assessment very difficult.
 
    • ‘make --no-print-directory’
@@ -2455,23 +2746,23 @@
      This is GNU ‘make’ specific.  When called with the
      ‘--no-print-directory’ option, GNU ‘make’ will disable printing of
      the working directory by invoked sub-‘make’s (the well-known
-     “Entering/Leaving directory ...” messages).  This helps to decrease
+     "Entering/Leaving directory ..." messages).  This helps to decrease
      the verbosity of the output, but experience has shown that it can
      also often render debugging considerably harder in projects using
      deeply-nested ‘make’ recursion.
 
-     As an aside, notice that the ‘--no-print-directory’ option is
-     automatically activated if the ‘-s’ flag is used.
+     As an aside, the ‘--no-print-directory’ option is automatically
+     activated if the ‘-s’ flag is used.
 
 &#x1f;
-File: automake.info,  Node: Automake Silent Rules,  Prev: Tricks For Silencing Make,  Up: Silencing Make
+File: automake.info,  Node: Automake Silent Rules,  Next: Unsilencing Automake,  Prev: Tricks For Silencing Make,  Up: Silencing Make
 
 21.3 How Automake can help in silencing Make
 ============================================
 
 The tricks and idioms for silencing ‘make’ described in the previous
-section can be useful from time to time, but we’ve seen that they all
-have their serious drawbacks and limitations.  That’s why automake
+section can be useful from time to time, but we've seen that they all
+have their serious drawbacks and limitations.  That's why automake
 provides support for a more advanced and flexible way of obtaining
 quieter output from ‘make’ (for most rules at least).
 
@@ -2511,8 +2802,8 @@
      test -z "foo" || rm -f foo
      rm -f *.o
 
-     Silent rules enabled: the output is minimal but informative.  In
-     particular, the warnings from the compiler stick out very clearly.
+     Silent rules enabled: the output is minimal but informative.
+     The warnings from the compiler stick out very clearly.
      % make V=0 CFLAGS=-Wall
        CC     main.o
      main.c: In function ‘main’:
@@ -2522,8 +2813,8 @@
      func.c:4:3: warning: ‘i’ used uninitialized in this function
        CCLD   foo
 
-   Also, in projects using ‘libtool’, the use of silent rules can
-automatically enable the ‘libtool’’s ‘--silent’ option:
+   Also, in projects using Libtool, the use of silent rules can
+automatically enable ‘libtool’'s ‘--silent’ option:
 
      % cat Makefile.am
      lib_LTLIBRARIES = libx.la
@@ -2551,36 +2842,40 @@
    • Passing ‘--enable-silent-rules’ to ‘configure’ will cause build
      rules to be less verbose; the option ‘--disable-silent-rules’ will
      cause normal verbose output.
+
    • At ‘make’ run time, the default chosen at ‘configure’ time may be
      overridden: ‘make V=1’ will produce verbose output, ‘make V=0’ less
      verbose output.
 
-   Note that silent rules are _disabled_ by default; the user must
-enable them explicitly at either ‘configure’ run time or at ‘make’ run
-time.  We think that this is a good policy, since it provides the casual
-user with enough information to prepare a good bug report in case
-anything breaks.
-
-   Still, notwithstanding the rationales above, developers who wants to
-make silent rules enabled by default in their own packages can do so by
-calling ‘AM_SILENT_RULES(yes)’ in ‘configure.ac’.
-
-   Users who prefer to have silent rules enabled by default can edit
-their ‘config.site’ file to make the variable ‘enable_silent_rules’
-default to ‘yes’.  This should still allow disabling silent rules at
-‘configure’ time and at ‘make’ time.
-
-   For portability to different ‘make’ implementations, package authors
-are advised to not set the variable ‘V’ inside the ‘Makefile.am’ file,
-to allow the user to override the value for subdirectories as well.
-
-   To work at its best, the current implementation of this feature
-normally uses nested variable expansion ‘$(VAR1$(V))’, a ‘Makefile’
-feature that is not required by POSIX 2008 but is widely supported in
-practice.  On the rare ‘make’ implementations that do not support nested
-variable expansion, whether rules are silent is always determined at
-configure time, and cannot be overridden at make time.  Future versions
-of POSIX are likely to require nested variable expansion, so this minor
+     Unfortunately, if ‘V’ is assigned a value other than 0 or 1, errors
+     will result.  This is problematic when a third-party program or
+     library is built in the same tree and also uses the make variable
+     ‘V’, with different values.  The best workaround is probably to set
+     ‘AM_V_P=true’ (or similar), either on the make command line or in
+     the ‘V’-using project's ‘Makefile.am’.  (For more discussion, see
+     <https://bugs.gnu.org/20077>.)
+
+   Silent rules are _disabled_ by default; the user must enable them
+explicitly at either ‘configure’ run time or at ‘make’ run time.  We
+think that this is a good policy, since it provides the casual user with
+enough information to prepare a good bug report in case anything breaks.
+
+   Notwithstanding those rationales, developers who want to enable
+silent rules by default in their own packages can do so by calling
+‘AM_SILENT_RULES(yes)’ in ‘configure.ac’.
+
+   Analogously, users who prefer to have silent rules enabled by default
+for everything on their system can edit their ‘config.site’ file to make
+the variable ‘enable_silent_rules’ default to ‘yes’.  This still allows
+disabling silent rules at ‘configure’ time and at ‘make’ time.
+
+   To work best, the current implementation of this feature normally
+uses nested variable expansion ‘$(VAR1$(V))’, a ‘Makefile’ feature that
+is not required by POSIX 2008 but is widely supported in practice.  On
+the rare ‘make’ implementations that do not support nested variable
+expansion, whether rules are silent is always determined at configure
+time, and cannot be overridden at make time.  Future versions of POSIX
+are likely to require nested variable expansion, so this minor
 limitation should go away with time.
 
    To extend the silent mode to your own rules, you have a few choices:
@@ -2594,16 +2889,20 @@
    • You can silence a recipe unconditionally with ‘@’, and then use the
      predefined variable ‘AM_V_P’ to know whether make is being run in
      silent or verbose mode; adjust the verbose information your recipe
-     displays accordingly:
+     displays accordingly.  For example:
 
           generate-headers:
-                          ... commands defining a shell variable '$headers' ...; \
+                  @set -e; \
+                  ... commands defining shell variable '$headers' ...; \
                   if $(AM_V_P); then set -x; else echo " GEN   headers"; fi; \
                   rm -f $$headers && generate-header --flags $$headers
 
+     ‘AM_V_P’ is (must be) always set to a simple command, not needing
+     shell quoting, typically either ‘:’ or ‘true’ or ‘false’.
+
    • You can add your own variables, so strings of your own choice are
      shown.  The following snippet shows how you would define your own
-     equivalent of ‘AM_V_GEN’:
+     equivalent of ‘AM_V_GEN’, say a string ‘PKG-GEN’:
 
           pkg_verbose = $(pkg_verbose_@AM_V@)
           pkg_verbose_ = $(pkg_verbose_@AM_DEFAULT_V@)
@@ -2612,14 +2911,40 @@
           foo: foo.in
                   $(pkg_verbose)cp $(srcdir)/foo.in $@
 
-   As a final note, observe that, even when silent rules are enabled,
-the ‘--no-print-directory’ option is still required with GNU ‘make’ if
-the “Entering/Leaving directory ...” messages are to be disabled.
+   Even when silent rules are enabled, the ‘--no-print-directory’ option
+is still required with GNU ‘make’ if the "Entering/Leaving directory
+..." messages are to be elided.
+
+&#x1f;
+File: automake.info,  Node: Unsilencing Automake,  Prev: Automake Silent Rules,  Up: Silencing Make
+
+21.4 Unsilencing Automake
+=========================
+
+With the ‘AM_SILENT_RULES’ macro described in the previous section,
+Automake does a good job reducing ‘make’ output to a bare minimum.
+Sometimes you want to see more than that, especially when debugging.
+Let's summarize ways to get more information out of Automake packages:
+
+   • Running ‘make V=1’ will produce generally verbose output.
+
+   • Adding ‘AM_V_GEN= AM_V_at=’ will unsilence more rules.  Thus, in
+     all: ‘make V=1 AM_V_GEN= AM_V_at=’.
+
+   • Even this will not unsilence everything.  To see the real truth of
+     what gets executed, resort to GNU Make's debugging feature: ‘make
+     --debug=p ... OTHERARGS ...’.  This reports every command being
+     run, ignoring the ‘@’ prefix on rules (which is what silences
+     them).  In the case of Automake, these commands are generally
+     complex shell constructs, and you'll want to track down the source
+     files in Automake to actually understand them; but at least you'll
+     have the text to search for.  You may wish to include other
+     debugging options.  *Note (make)Options Summary::.
 
 &#x1f;
 File: automake.info,  Node: Not Enough,  Next: Distributing,  Prev: Silencing Make,  Up: Top
 
-22 When Automake Isn’t Enough
+22 When Automake Isn't Enough
 *****************************
 
 In some situations, where Automake is not up to one task, one has to
@@ -2679,7 +3004,7 @@
 ‘maintainer-clean’).
 
    Note that there are no ‘uninstall-exec-local’ or
-‘uninstall-data-local’ targets; just use ‘uninstall-local’.  It doesn’t
+‘uninstall-data-local’ targets; just use ‘uninstall-local’.  It doesn't
 make sense to uninstall just data or just executables.
 
    For instance, here is one way to erase a subdirectory during ‘make
@@ -2697,7 +3022,7 @@
 there is no way to be sure of that.
 
    In contrast, some rules also have a way to run another rule, called a
-“hook”; hooks are always executed after the main rule’s work is done.
+“hook”; hooks are always executed after the main rule's work is done.
 The hook is named after the principal target, with ‘-hook’ appended.
 The targets allowing hooks are ‘install-data’, ‘install-exec’,
 ‘uninstall’, ‘dist’, and ‘distcheck’.
@@ -2818,10 +3143,10 @@
 rules (*note Conditional Subdirectories::).
 
    Usually, many of these rules are irrelevant to the third-party
-subproject, but they are required for the whole package to work.  It’s
+subproject, but they are required for the whole package to work.  It's
 OK to have a rule that does nothing, so if you are integrating a
 third-party project with no documentation or tag support, you could
-simply augment its ‘Makefile’ as follows:
+augment its ‘Makefile’ as follows:
 
      EMPTY_AUTOMAKE_TARGETS = dvi pdf ps info html tags ctags
      .PHONY: $(EMPTY_AUTOMAKE_TARGETS)
@@ -2842,7 +3167,7 @@
 Directories.).  The necessary substitutions: ‘@srcdir@’, ‘@top_srcdir@’,
 and ‘@top_builddir@’ are defined by ‘configure’ when it processes a
 ‘Makefile’ (*note Preset Output Variables: (autoconf)Preset Output
-Variables.); they are not computed by the Makefile like the
+Variables.); they are not computed by the ‘Makefile’ like the
 aforementioned ‘$(distdir)’ and ‘$(top_distdir)’ variables.
 
    It is sometimes inconvenient to modify a third-party ‘Makefile’ to
@@ -2868,9 +3193,9 @@
 
    A similar idea that does not use ‘include’ is to write a proxy
 ‘Makefile’ that dispatches rules to the real ‘Makefile’, either with
-‘$(MAKE) -f Makefile.real $(AM_MAKEFLAGS) target’ (if it’s OK to rename
+‘$(MAKE) -f Makefile.real $(AM_MAKEFLAGS) target’ (if it's OK to rename
 the original ‘Makefile’) or with ‘cd subdir && $(MAKE) $(AM_MAKEFLAGS)
-target’ (if it’s OK to store the subdirectory project one directory
+target’ (if it's OK to store the subdirectory project one directory
 deeper).  The good news is that this proxy ‘Makefile’ can be generated
 with Automake.  All we need are ‘-local’ targets (*note Extending::)
 that perform the dispatch.  Of course the other Automake features are
@@ -2897,8 +3222,8 @@
 
    Pushing this idea to the extreme, it is also possible to ignore the
 subproject build system and build everything from this proxy
-‘Makefile.am’.  This might sound very sensible if you need VPATH builds
-but the subproject does not support them.
+‘Makefile.am’.  This might well be sensible if you need VPATH builds but
+the subproject does not support them.
 
 &#x1f;
 File: automake.info,  Node: Distributing,  Next: API Versioning,  Prev: Not Enough,  Up: Top
@@ -2907,9 +3232,9 @@
 ******************************
 
 Automake places no restrictions on the distribution of the resulting
-‘Makefile.in’s.  We still encourage software authors to distribute their
-work under terms like those of the GPL, but doing so is not required to
-use Automake.
+‘Makefile.in’s.  We encourage software authors to distribute their work
+under terms like those of the GPL, but doing so is not required to use
+Automake.
 
    Some of the files that can be automatically installed via the
 ‘--add-missing’ switch do fall under the GPL.  However, these also have
@@ -2923,7 +3248,7 @@
 **************************
 
 New Automake releases usually include bug fixes and new features.
-Unfortunately they may also introduce new bugs and incompatibilities.
+Unfortunately they may also introduce new bugs and incompatibility.
 This makes four reasons why a package may require a particular Automake
 version.
 
@@ -2940,8 +3265,8 @@
 Furthermore, ‘Makefile’s generated by Automake 1.6 will use
 ‘automake-1.6’ explicitly in their rebuild rules.
 
-   The number ‘1.6’ in ‘automake-1.6’ is Automake’s API version, not
-Automake’s version.  If a bug fix release is made, for instance Automake
+   The number ‘1.6’ in ‘automake-1.6’ is Automake's API version, not
+Automake's version.  If a bug fix release is made, for instance Automake
 1.6.1, the API version will remain 1.6.  This means that a package that
 works with Automake 1.6 should also work with 1.6.1; after all, this is
 what people expect from bug fix releases.
@@ -2963,10 +3288,10 @@
 What is in the API
 ==================
 
-Automake’s programming interface is not easy to define.  Basically it
+Automake's programming interface is not easy to define.  Basically it
 should include at least all *documented* variables and targets that a
 ‘Makefile.am’ author can use, any behavior associated with them (e.g.,
-the places where ‘-hook’’s are run), the command line interface of
+the places where ‘-hook’'s are run), the command line interface of
 ‘automake’ and ‘aclocal’, ...
 
 What is not in the API
@@ -3027,7 +3352,7 @@
 
    Before upgrading to a new major release, it is a good idea to read
 the file ‘NEWS’.  This file lists all changes between releases: new
-features, obsolete constructs, known incompatibilities, and workarounds.
+features, obsolete constructs, known incompatibility, and workarounds.
 
 &#x1f;
 File: automake.info,  Node: FAQ,  Next: Copying This Manual,  Prev: Upgrading,  Up: Top
@@ -3040,31 +3365,30 @@
 
 * Menu:
 
-* CVS::                         CVS and generated files
+* Version Control::             Version control and generated files
 * maintainer-mode::             missing and AM_MAINTAINER_MODE
-* Wildcards::                   Why doesn’t Automake support wildcards?
+* Wildcards::                   Why doesn't Automake support wildcards?
 * Limitations on File Names::   Limitations on source and installed file names
-* Errors with distclean::       Files left in build directory after distclean
 * Flag Variables Ordering::     CFLAGS vs. AM_CFLAGS vs. mumble_CFLAGS
 * Renamed Objects::             Why are object files sometimes renamed?
 * Per-Object Flags::            How to simulate per-object flags?
 * Multiple Outputs::            Writing rules for tools with many output files
 * Hard-Coded Install Paths::    Installing to hard-coded locations
-* Debugging Make Rules::        Strategies when things don’t work as expected
+* Debugging Make Rules::        Strategies when things don't work as expected
 * Reporting Bugs::              Feedback on bugs and feature requests
 
 &#x1f;
-File: automake.info,  Node: CVS,  Next: maintainer-mode,  Up: FAQ
+File: automake.info,  Node: Version Control,  Next: maintainer-mode,  Up: FAQ
 
-26.1 CVS and generated files
-============================
+26.1 Version control and generated files
+========================================
 
 Background: distributed generated Files
 ---------------------------------------
 
 Packages made with Autoconf and Automake ship with some generated files
 like ‘configure’ or ‘Makefile.in’.  These files were generated on the
-developer’s machine and are distributed so that end-users do not have to
+developer's machine and are distributed so that end-users do not have to
 install the maintainer tools required to rebuild them.  Other generated
 files like Lex scanners, Yacc parsers, or Info documentation are usually
 distributed on similar grounds.
@@ -3076,43 +3400,38 @@
 ‘configure.ac’.
 
    As generated files shipped in packages are up-to-date, and because
-‘tar’ preserves times-tamps, these rebuild rules are not triggered when
-a user unpacks and builds a package.
+‘tar’ preserves timestamps, these rebuild rules are not triggered when a
+user unpacks and builds a package.
 
-Background: CVS and Timestamps
-------------------------------
+Background: Version Control and Timestamps
+------------------------------------------
 
-Unless you use CVS keywords (in which case files must be updated at
-commit time), CVS preserves timestamp during ‘cvs commit’ and ‘cvs
-import -d’ operations.
-
-   When you check out a file using ‘cvs checkout’ its timestamp is set
-to that of the revision that is being checked out.
-
-   However, during ‘cvs update’, files will have the date of the update,
-not the original timestamp of this revision.  This is meant to make sure
-that ‘make’ notices that sources files have been updated.
+Typically when you update files with version control commands, working
+files will have the timestamp of your update, not the original timestamp
+of the commit.  This is meant to make sure that ‘make’ notices that
+source files have been updated.
 
    This timestamp shift is troublesome when both sources and generated
-files are kept under CVS.  Because CVS processes files in lexical order,
-‘configure.ac’ will appear newer than ‘configure’ after a ‘cvs update’
-that updates both files, even if ‘configure’ was newer than
-‘configure.ac’ when it was checked in.  Calling ‘make’ will then trigger
-a spurious rebuild of ‘configure’.
-
-Living with CVS in Autoconfiscated Projects
--------------------------------------------
-
-There are basically two clans amongst maintainers: those who keep all
-distributed files under CVS, including generated files, and those who
-keep generated files _out_ of CVS.
-
-All Files in CVS
-................
-
-   • The CVS repository contains all distributed files so you know
-     exactly what is distributed, and you can check out any prior
-     version entirely.
+files are kept under version control.  Because version control commands
+often process files in lexical order, ‘configure.ac’ will appear newer
+than ‘configure’ after a version control command that updates both
+files, even if ‘configure’ was newer than ‘configure.ac’ when it was
+committed.  Calling ‘make’ will then trigger a spurious rebuild of
+‘configure’.
+
+Living with Version Control in Autoconfiscated Projects
+-------------------------------------------------------
+
+There are basically two clans among maintainers: those who keep all
+distributed files under version control, including generated files, and
+those who keep generated files _out_ of version control.
+
+All Files under Version Control
+...............................
+
+   • The repository contains all distributed files so you know exactly
+     what is distributed, and you can check out any prior version
+     entirely.
 
    • Maintainers can see how generated files evolve (for instance, you
      can see what happens to your ‘Makefile.in’s when you upgrade
@@ -3121,64 +3440,59 @@
    • Users do not need Autotools to build a check-out of the project; it
      works just like a released tarball.
 
-   • If users use ‘cvs update’ to update their copy, instead of ‘cvs
-     checkout’ to fetch a fresh one, timestamps will be inaccurate.
-     Some rebuild rules will be triggered and attempt to run developer
-     tools such as ‘autoconf’ or ‘automake’.
+   • If users use version control to update their copy, timestamps will
+     likely be inaccurate.  Some rebuild rules will be triggered and
+     attempt to run developer tools such as ‘autoconf’ or ‘automake’.
 
      Calls to such tools are all wrapped into a call to the ‘missing’
      script discussed later (*note maintainer-mode::), so that the user
      will see more descriptive warnings about missing or out-of-date
      tools, and possible suggestions about how to obtain them, rather
-     than just some “command not found” error, or (worse) some obscure
+     than just some "command not found" error, or (worse) some obscure
      message from some older version of the required tool they happen to
      have installed.
 
      Maintainers interested in keeping their package buildable from a
-     CVS checkout even for those users that lack maintainer-specific
-     tools might want to provide a helper script (or to enhance their
-     existing bootstrap script) to fix the timestamps after a ‘cvs
-     update’ or a ‘git checkout’, to prevent spurious rebuilds.  In case
-     of a project committing the Autotools-generated files, as well as
-     the generated ‘.info’ files, such a script might look something
-     like this:
+     checkout even for those users that lack maintainer-specific tools
+     might want to provide a helper script (or to enhance their existing
+     bootstrap script) to fix the timestamps after a checkout, to
+     prevent spurious rebuilds.  In case of a project committing the
+     Autotools-generated files, as well as the generated ‘.info’ files,
+     such a script might look something like this:
 
           #!/bin/sh
-          # fix-timestamp.sh: prevents useless rebuilds after "cvs update"
+          # fix-timestamp.sh: Prevent useless rebuilds after "git pull".
           sleep 1
           # aclocal-generated aclocal.m4 depends on locally-installed
-          # '.m4' macro files, as well as on 'configure.ac'
+          # '.m4' macro files, as well as on 'configure.ac'.
           touch aclocal.m4
           sleep 1
-          # autoconf-generated configure depends on aclocal.m4 and on
-          # configure.ac
-          touch configure
-          # so does autoheader-generated config.h.in
-          touch config.h.in
-          # and all the automake-generated Makefile.in files
-          touch `find . -name Makefile.in -print`
-          # finally, the makeinfo-generated '.info' files depend on the
-          # corresponding '.texi' files
-          touch doc/*.info
+          # autoconf-generated 'configure' and autoheader-generated
+          # config.h.in both depend on aclocal.m4 and on configure.ac.
+          touch configure config.h.in
+          # Automake-generated Makefile.in files depend on Makefile.am,
+          # and makeinfo-generated '.info' files depend on the
+          # corresponding '.texi' files.
+          touch $(git ls-files '*/Makefile.in' '*.info')
 
    • In distributed development, developers are likely to have different
      versions of the maintainer tools installed.  In this case rebuilds
-     triggered by timestamp lossage will lead to spurious changes to
-     generated files.  There are several solutions to this:
+     triggered by clock skew can lead to spurious changes to generated
+     files.  There are several solutions to this:
 
         • All developers should use the same versions, so that the
-          rebuilt files are identical to files in CVS.  (This starts to
-          be difficult when each project you work on uses different
-          versions.)
+          rebuilt files are identical to files in the repository.  (This
+          becomes difficult when different projects on which you are
+          working use different versions.)
         • Or people use a script to fix the timestamp after a checkout
           (the GCC folks have such a script).
-        • Or ‘configure.ac’ uses ‘AM_MAINTAINER_MODE’, which will
-          disable all of these rebuild rules by default.  This is
-          further discussed in *note maintainer-mode::.
+        • Or ‘configure.ac’ uses ‘AM_MAINTAINER_MODE’, which disables
+          all of these rebuild rules by default.  This is further
+          discussed in *note maintainer-mode::.
 
    • Although we focused on spurious rebuilds, the converse can also
-     happen.  CVS’s timestamp handling can also let you think an
-     out-of-date file is up-to-date.
+     happen.  Version control timestamp handling can also let you think
+     an out-of-date file is up-to-date.
 
      For instance, suppose a developer has modified ‘Makefile.am’ and
      has rebuilt ‘Makefile.in’, and then decides to do a last-minute
@@ -3186,28 +3500,29 @@
      (without rebuilding ‘Makefile.in’ to account for the change).
 
      This last change to ‘Makefile.am’ makes the copy of ‘Makefile.in’
-     out-of-date.  Since CVS processes files alphabetically, when
-     another developer ‘cvs update’s his or her tree, ‘Makefile.in’ will
-     happen to be newer than ‘Makefile.am’.  This other developer will
-     not see that ‘Makefile.in’ is out-of-date.
-
-Generated Files out of CVS
-..........................
-
-One way to get CVS and ‘make’ working peacefully is to never store
-generated files in CVS, i.e., do not CVS-control files that are
-‘Makefile’ targets (also called _derived_ files).
+     out-of-date.  Assuming version control processes files
+     alphabetically, when another developer updates their tree,
+     ‘Makefile.in’ will happen to be newer than ‘Makefile.am’.  This
+     other developer will not see that ‘Makefile.in’ is out-of-date.
+
+Generated Files out of Version Control
+......................................
+
+One way to get version control and ‘make’ working peacefully is to never
+store generated files in version control, i.e., do not version-control
+files that are ‘Makefile’ targets (also called _derived_ files).
 
    This way developers are not annoyed by changes to generated files.
 It does not matter if they all have different versions (assuming they
 are compatible, of course).  And finally, timestamps are not lost;
-changes to sources files can’t be missed as in the
+changes to source files can't be missed as in the
 ‘Makefile.am’/‘Makefile.in’ example discussed earlier.
 
-   The drawback is that the CVS repository is not an exact copy of what
-is distributed and that users now need to install various development
+   The drawback is that the repository does not contain some files that
+are is distributed, so builders now need to install various development
 tools (maybe even specific versions) before they can build a checkout.
-But, after all, CVS’s job is versioning, not distribution.
+But, after all, the job of version control is versioning, not
+distribution.
 
    Allowing developers to use different versions of their tools can also
 hide bugs during distributed development.  Indeed, developers will be
@@ -3215,7 +3530,7 @@
 generated files that will be released.  The developer who prepares the
 tarball might be using a version of the tool that produces bogus output
 (for instance a non-portable C file), something other developers could
-have noticed if they weren’t using their own versions of this tool.
+have noticed if they weren't using their own versions of this tool.
 
 Third-party Files
 -----------------
@@ -3226,13 +3541,13 @@
 ‘autopoint’ (from Gettext) or ‘libtoolize’ (from Libtool), will install
 or update files in your package.
 
-   These files, whether they are kept under CVS or not, raise similar
-concerns about version mismatch between developers’ tools.  The Gettext
-manual has a section about this; see *note Integrating with Version
-Control Systems: (gettext)Version Control Issues.
+   These files, whether they are kept under version control or not,
+raise similar concerns about version mismatch between developers' tools.
+The Gettext manual has a section about this; see *note Integrating with
+Version Control Systems: (gettext)Version Control Issues.
 
 &#x1f;
-File: automake.info,  Node: maintainer-mode,  Next: Wildcards,  Prev: CVS,  Up: FAQ
+File: automake.info,  Node: maintainer-mode,  Next: Wildcards,  Prev: Version Control,  Up: FAQ
 
 26.2 ‘missing’ and ‘AM_MAINTAINER_MODE’
 =======================================
@@ -3244,7 +3559,7 @@
 designed to warn users if a maintainer tool is required but missing.
 Typical maintainer tools are ‘autoconf’, ‘automake’, ‘bison’, etc.
 Because files generated by these tools are shipped with the other
-sources of a package, these tools shouldn’t be required during a user
+sources of a package, these tools shouldn't be required during a user
 build and they are not checked for in ‘configure’.
 
    However, if for some reason a rebuild rule is triggered and involves
@@ -3256,9 +3571,9 @@
 will warn the user if it detects that a maintainer tool it attempted to
 use seems too old (be warned that diagnosing this correctly is typically
 more difficult than detecting missing tools, and requires cooperation
-from the tool itself, so it won’t always work).
+from the tool itself, so it won't always work).
 
-   If the required tool is installed, ‘missing’ will run it and won’t
+   If the required tool is installed, ‘missing’ will run it and won't
 attempt to continue after failures.  This is correct behavior during
 development: developers love fixing failures.  However, users with
 missing or too old maintainer tools may get an error when the rebuild
@@ -3284,8 +3599,8 @@
 ‘configure’.
 
    People use ‘AM_MAINTAINER_MODE’ either because they do not want their
-users (or themselves) annoyed by timestamp lossage (*note CVS::), or
-because they simply can’t stand the rebuild rules and prefer running
+users (or themselves) annoyed by clock skew (*note Version Control::),
+or because they simply can't stand the rebuild rules and prefer running
 maintainer tools explicitly.
 
    ‘AM_MAINTAINER_MODE’ also allows you to disable some custom build
@@ -3296,27 +3611,27 @@
 against this ‘AM_MAINTAINER_MODE’ macro.  Most of them relate to
 insecurity.  By removing dependencies you get non-dependable builds:
 changes to source files can have no effect on generated files and this
-can be very confusing when unnoticed.  He adds that security shouldn’t
+can be very confusing when unnoticed.  He adds that security shouldn't
 be reserved to maintainers (what ‘--enable-maintainer-mode’ suggests),
 on the contrary.  If one user has to modify a ‘Makefile.am’, then either
 ‘Makefile.in’ should be updated or a warning should be output (this is
 what Automake uses ‘missing’ for) but the last thing you want is that
-nothing happens and the user doesn’t notice it (this is what happens
+nothing happens and the user doesn't notice it (this is what happens
 when rebuild rules are disabled by ‘AM_MAINTAINER_MODE’).
 
    Jim Meyering, the inventor of the ‘AM_MAINTAINER_MODE’ macro, was
-swayed by François’ arguments, and got rid of ‘AM_MAINTAINER_MODE’ in
+swayed by François' arguments, and got rid of ‘AM_MAINTAINER_MODE’ in
 all of his packages.
 
    Still many people continue to use ‘AM_MAINTAINER_MODE’, because it
 helps them working on projects where all files are kept under version
-control, and because ‘missing’ isn’t enough if you have the wrong
+control, and because ‘missing’ isn't enough if you have the wrong
 version of the tools.
 
 &#x1f;
 File: automake.info,  Node: Wildcards,  Next: Limitations on File Names,  Prev: maintainer-mode,  Up: FAQ
 
-26.3 Why doesn’t Automake support wildcards?
+26.3 Why doesn't Automake support wildcards?
 ============================================
 
 Developers are lazy.  They would often like to use wildcards in
@@ -3324,19 +3639,19 @@
 ‘Makefile.am’s every time they add, delete, or rename a file.
 
    There are several objections to this:
-   • When using CVS (or similar) developers need to remember they have
-     to run ‘cvs add’ or ‘cvs rm’ anyway.  Updating ‘Makefile.am’
-     accordingly quickly becomes a reflex.
-
-     Conversely, if your application doesn’t compile because you forgot
-     to add a file in ‘Makefile.am’, it will help you remember to ‘cvs
-     add’ it.
+   • When using version control, developers need to remember they have
+     to add or remove files from version control anyway.  Updating
+     ‘Makefile.am’ accordingly quickly becomes a reflex.
+
+     Conversely, if your application doesn't compile because you forgot
+     to add a file in ‘Makefile.am’, it will help you remember to add
+     the file to version control.
 
    • Using wildcards makes it easy to distribute files by mistake.  For
      instance, some code a developer is experimenting with (a test case,
      say) that should not be part of the distribution.
 
-   • Using wildcards it’s easy to omit some files by mistake.  For
+   • Using wildcards it's easy to omit some files by mistake.  For
      instance, one developer creates a new file, uses it in many places,
      but forgets to commit it.  Another developer then checks out the
      incomplete project and is able to run ‘make dist’ successfully,
@@ -3347,14 +3662,14 @@
      e.g., NetBSD ‘make’ will not expand globs such as ‘*’ in
      prerequisites of a target.
 
-   • Finally, it’s quite hard to _forget_ to add a file to
+   • Finally, it's quite hard to _forget_ to add a file to
      ‘Makefile.am’: files that are not listed in ‘Makefile.am’ are not
-     compiled or installed, so you can’t even test them.
+     compiled or installed, so you can't even test them.
 
    Still, these are philosophical objections, and as such you may
 disagree, or find enough value in wildcards to dismiss all of them.
 Before you start writing a patch against Automake to teach it about
-wildcards, let’s see the main technical issue: portability.
+wildcards, let's see the main technical issue: portability.
 
    Although ‘$(wildcard ...)’ works with GNU ‘make’, it is not portable
 to other ‘make’ implementations.
@@ -3366,15 +3681,15 @@
 to run ‘automake’ each time they add, delete, or rename files.
 
    Compared to editing ‘Makefile.am’, this is a very small gain.  Sure,
-it’s easier and faster to type ‘automake; make’ than to type ‘emacs
+it's easier and faster to type ‘automake; make’ than to type ‘emacs
 Makefile.am; make’.  But nobody bothered enough to write a patch to add
 support for this syntax.  Some people use scripts to generate file lists
 in ‘Makefile.am’ or in separate ‘Makefile’ fragments.
 
-   Even if you don’t care about portability, and are tempted to use
+   Even if you don't care about portability, and are tempted to use
 ‘$(wildcard ...)’ anyway because you target only GNU Make, you should
 know there are many places where Automake needs to know exactly which
-files should be processed.  As Automake doesn’t know how to expand
+files should be processed.  As Automake doesn't know how to expand
 ‘$(wildcard ...)’, you cannot use it in these places.  ‘$(wildcard ...)’
 is a black box comparable to ‘AC_SUBST’ed variables as far Automake is
 concerned.
@@ -3383,7 +3698,7 @@
 ‘-Wportability’ flag.
 
 &#x1f;
-File: automake.info,  Node: Limitations on File Names,  Next: Errors with distclean,  Prev: Wildcards,  Up: FAQ
+File: automake.info,  Node: Limitations on File Names,  Next: Flag Variables Ordering,  Prev: Wildcards,  Up: FAQ
 
 26.4 Limitations on File Names
 ==============================
@@ -3394,7 +3709,7 @@
 
    Most operating systems prohibit the use of the null byte in file
 names, and reserve ‘/’ as a directory separator.  Also, they require
-that file names are properly encoded for the user’s locale.  Automake is
+that file names are properly encoded for the user's locale.  Automake is
 subject to these limits.
 
    Portable packages should limit themselves to POSIX file names.  These
@@ -3403,7 +3718,7 @@
 begin with ‘-’.
 
    Portable POSIX file names cannot contain components that exceed a
-14-byte limit, but nowadays it’s normally safe to assume the
+14-byte limit, but nowadays it's normally safe to assume the
 more-generous XOPEN limit of 255 bytes.  POSIX limits file names to 255
 bytes (XOPEN allows 1023 bytes), but you may want to limit a source
 tarball to file names of 99 bytes to avoid interoperability problems
@@ -3423,7 +3738,7 @@
      newline " # $ ' `
 
    should not appear in the names of install directories.  For example,
-the operand of ‘configure’’s ‘--prefix’ option should not contain these
+the operand of ‘configure’'s ‘--prefix’ option should not contain these
 characters.
 
    Build directories suffer the same limitations as install directories,
@@ -3442,134 +3757,16 @@
 limits of DOS file systems.
 
 &#x1f;
-File: automake.info,  Node: Errors with distclean,  Next: Flag Variables Ordering,  Prev: Limitations on File Names,  Up: FAQ
-
-26.5 Errors with distclean
-==========================
-
-This is a diagnostic you might encounter while running ‘make distcheck’.
-
-   As explained in *note Checking the Distribution::, ‘make distcheck’
-attempts to build and check your package for errors like this one.
-
-   ‘make distcheck’ will perform a ‘VPATH’ build of your package (*note
-VPATH Builds::), and then call ‘make distclean’.  Files left in the
-build directory after ‘make distclean’ has run are listed after this
-error.
-
-   This diagnostic covers two kinds of errors:
-
-   • files that are forgotten by distclean;
-   • distributed files that are erroneously rebuilt.
-
-   The former left-over files are not distributed, so the fix is to mark
-them for cleaning (*note Clean::); this is obvious and doesn’t deserve
-more explanation.
-
-   The latter bug is not always easy to understand and fix, so let’s
-proceed with an example.  Suppose our package contains a program for
-which we want to build a man page using ‘help2man’.  GNU ‘help2man’
-produces simple manual pages from the ‘--help’ and ‘--version’ output of
-other commands (*note Overview: (help2man)Top.).  Because we don’t want
-to force our users to install ‘help2man’, we decide to distribute the
-generated man page using the following setup.
-
-     # This Makefile.am is bogus.
-     bin_PROGRAMS = foo
-     foo_SOURCES = foo.c
-     dist_man_MANS = foo.1
-
-     foo.1: foo$(EXEEXT)
-             help2man --output=foo.1 ./foo$(EXEEXT)
-
-   This will effectively distribute the man page.  However, ‘make
-distcheck’ will fail with:
-
-     ERROR: files left in build directory after distclean:
-     ./foo.1
-
-   Why was ‘foo.1’ rebuilt?  Because although distributed, ‘foo.1’
-depends on a non-distributed built file: ‘foo$(EXEEXT)’.  ‘foo$(EXEEXT)’
-is built by the user, so it will always appear to be newer than the
-distributed ‘foo.1’.
-
-   ‘make distcheck’ caught an inconsistency in our package.  Our intent
-was to distribute ‘foo.1’ so users do not need to install ‘help2man’,
-however since this rule causes this file to be always rebuilt, users
-_do_ need ‘help2man’.  Either we should ensure that ‘foo.1’ is not
-rebuilt by users, or there is no point in distributing ‘foo.1’.
-
-   More generally, the rule is that distributed files should never
-depend on non-distributed built files.  If you distribute something
-generated, distribute its sources.
-
-   One way to fix the above example, while still distributing ‘foo.1’,
-is to not depend on ‘foo$(EXEEXT)’.  For instance, assuming ‘foo
---version’ and ‘foo --help’ do not change unless ‘foo.c’ or
-‘configure.ac’ change, we could write the following ‘Makefile.am’:
-
-     bin_PROGRAMS = foo
-     foo_SOURCES = foo.c
-     dist_man_MANS = foo.1
-
-     foo.1: foo.c $(top_srcdir)/configure.ac
-             $(MAKE) $(AM_MAKEFLAGS) foo$(EXEEXT)
-             help2man --output=foo.1 ./foo$(EXEEXT)
-
-   This way, ‘foo.1’ will not get rebuilt every time ‘foo$(EXEEXT)’
-changes.  The ‘make’ call makes sure ‘foo$(EXEEXT)’ is up-to-date before
-‘help2man’.  Another way to ensure this would be to use separate
-directories for binaries and man pages, and set ‘SUBDIRS’ so that
-binaries are built before man pages.
-
-   We could also decide not to distribute ‘foo.1’.  In this case it’s
-fine to have ‘foo.1’ dependent upon ‘foo$(EXEEXT)’, since both will have
-to be rebuilt.  However, it would be impossible to build the package in
-a cross-compilation, because building ‘foo.1’ involves an _execution_ of
-‘foo$(EXEEXT)’.
-
-   Another context where such errors are common is when distributed
-files are built by tools that are built by the package.  The pattern is
-similar:
-
-     distributed-file: built-tools distributed-sources
-             build-command
-
-should be changed to
-
-     distributed-file: distributed-sources
-             $(MAKE) $(AM_MAKEFLAGS) built-tools
-             build-command
-
-or you could choose not to distribute ‘distributed-file’, if
-cross-compilation does not matter.
-
-   The points made through these examples are worth a summary:
-
-   • Distributed files should never depend upon non-distributed built
-     files.
-   • Distributed files should be distributed with all their
-     dependencies.
-   • If a file is _intended_ to be rebuilt by users, then there is no
-     point in distributing it.
-
-   For desperate cases, it’s always possible to disable this check by
-setting ‘distcleancheck_listfiles’ as documented in *note Checking the
-Distribution::.  Make sure you do understand the reason why ‘make
-distcheck’ complains before you do this.  ‘distcleancheck_listfiles’ is
-a way to _hide_ errors, not to fix them.  You can always do better.
-
-&#x1f;
-File: automake.info,  Node: Flag Variables Ordering,  Next: Renamed Objects,  Prev: Errors with distclean,  Up: FAQ
+File: automake.info,  Node: Flag Variables Ordering,  Next: Renamed Objects,  Prev: Limitations on File Names,  Up: FAQ
 
-26.6 Flag Variables Ordering
+26.5 Flag Variables Ordering
 ============================
 
      What is the difference between ‘AM_CFLAGS’, ‘CFLAGS’, and
      ‘mumble_CFLAGS’?
 
      Why does ‘automake’ output ‘CPPFLAGS’ after
-     ‘AM_CPPFLAGS’ on compile lines?  Shouldn’t it be the converse?
+     ‘AM_CPPFLAGS’ on compile lines?  Shouldn't it be the converse?
 
      My ‘configure’ adds some warning flags into ‘CXXFLAGS’.  In
      one ‘Makefile.am’ I would like to append a new flag, however if I
@@ -3613,13 +3810,13 @@
 variable for target ‘bar’).
 
    The difference between ‘mumble_CPPFLAGS’ and ‘AM_CPPFLAGS’ being
-clear enough, let’s focus on ‘CPPFLAGS’.  ‘CPPFLAGS’ is a user variable,
+clear enough, let's focus on ‘CPPFLAGS’.  ‘CPPFLAGS’ is a user variable,
 i.e., a variable that users are entitled to modify in order to compile
 the package.  This variable, like many others, is documented at the end
 of the output of ‘configure --help’.
 
    For instance, someone who needs to add ‘/home/my/usr/include’ to the
-C compiler’s search path would configure a package with
+C compiler's search path would configure a package with
 
      ./configure CPPFLAGS='-I /home/my/usr/include'
 
@@ -3642,7 +3839,7 @@
 ‘CXXFLAGS=-O0’ to supersede any other switch from ‘AM_CXXFLAGS’ or
 ‘mumble_CXXFLAGS’.
 
-   It’s true that not all options to all programs can be overridden.  So
+   It's true that not all options to all programs can be overridden.  So
 in general, users could conceivably want to place options at arbitrary
 places in the command line, but Automake does not support this.  It
 would be difficult to make such generality comprehensible.  Being able
@@ -3654,7 +3851,7 @@
 
      CPPFLAGS = -DDATADIR=\"$(datadir)\" @CPPFLAGS@
 
-is erroneous.  Although this preserves ‘configure’’s value of
+is erroneous.  Although this preserves ‘configure’'s value of
 ‘CPPFLAGS’, the definition of ‘DATADIR’ will disappear if a user
 attempts to override ‘CPPFLAGS’ from the ‘make’ command line.
 
@@ -3735,7 +3932,7 @@
 &#x1f;
 File: automake.info,  Node: Renamed Objects,  Next: Per-Object Flags,  Prev: Flag Variables Ordering,  Up: FAQ
 
-26.7 Why are object files sometimes renamed?
+26.6 Why are object files sometimes renamed?
 ============================================
 
 This happens when per-target compilation flags are used.  Object files
@@ -3755,11 +3952,11 @@
 ‘automake’ outputs rules to build two different objects:
 ‘true-generic.o’ and ‘false-generic.o’.
 
-   Automake doesn’t actually determine whether source files are shared
+   Automake doesn't actually determine whether source files are shared
 to decide if it must rename objects.  It just renames all objects of a
 target as soon as it sees that per-target compilation flags are used.
 
-   It’s OK to share object files when per-target compilation flags are
+   It's OK to share object files when per-target compilation flags are
 not used.  For instance, ‘true’ and ‘false’ will both use ‘version.o’ in
 the following example.
 
@@ -3774,7 +3971,7 @@
 &#x1f;
 File: automake.info,  Node: Per-Object Flags,  Next: Multiple Outputs,  Prev: Renamed Objects,  Up: FAQ
 
-26.8 Per-Object Flags Emulation
+26.7 Per-Object Flags Emulation
 ===============================
 
      One of my source files needs to be compiled with different flags.  How
@@ -3836,13 +4033,19 @@
 &#x1f;
 File: automake.info,  Node: Multiple Outputs,  Next: Hard-Coded Install Paths,  Prev: Per-Object Flags,  Up: FAQ
 
-26.9 Handling Tools that Produce Many Outputs
+26.8 Handling Tools that Produce Many Outputs
 =============================================
 
 This section describes a ‘make’ idiom that can be used when a tool
 produces multiple output files.  It is not specific to Automake and can
 be used in ordinary ‘Makefile’s.
 
+   First, however: GNU ‘make’ is able to express rules with multiple
+output files using pattern rules (*note Pattern Rule Examples:
+(make)Pattern Examples.).  We do not discuss pattern rules here because
+they are not portable, but if you're able to assume GNU ‘make’, they are
+typically more convenient than any of the below approaches.
+
    Suppose we have a program called ‘foo’ that will read one file called
 ‘data.foo’ and produce two files named ‘data.c’ and ‘data.h’.  We want
 to write a ‘Makefile’ rule that captures this one-to-two dependency.
@@ -3875,30 +4078,13 @@
    • Another case is when the dependency (here ‘data.foo’) is (or
      depends upon) a phony target.
 
-   A solution that works with parallel ‘make’ but not with phony
-dependencies is the following:
+   Ideally, we want a scheme that will support any number of output
+files, and that works with parallel ‘make’ invocations, and that does
+nothing when ‘make -n’ is run.  It is apparently not possible to achieve
+a perfect solution.  Even an acceptable solution for the majority of
+cases gets complicated, so we will take it step by step.
 
-     data.c data.h: data.foo
-             foo data.foo
-     data.h: data.c
-
-The above rules are equivalent to
-
-     data.c: data.foo
-             foo data.foo
-     data.h: data.foo data.c
-             foo data.foo
-
-therefore a parallel ‘make’ will have to serialize the builds of
-‘data.c’ and ‘data.h’, and will detect that the second is no longer
-needed once the first is over.
-
-   Using this pattern is probably enough for most cases.  However it
-does not scale easily to more output files (in this scheme all output
-files must be totally ordered by the dependency relation), so we will
-explore a more complicated solution.
-
-   Another idea is to write the following:
+   One idea is to write the following:
 
      # There is still a problem with this one.
      data.c: data.foo
@@ -3918,6 +4104,7 @@
    What we need is a rule that forces a rebuild when ‘data.h’ is
 missing.  Here it is:
 
+     # More or less works, but not easy to generalize.
      data.c: data.foo
              foo data.foo
      data.h: data.c
@@ -3927,6 +4114,7 @@
 
    It is tempting to use a single test as follows:
 
+     # This breaks make -n.
      data.h: data.c
      ## Recover from the removal of $@
              @if test -f $@; then :; else \
@@ -3936,7 +4124,7 @@
 
 but that would break ‘make -n’: at least GNU ‘make’ and Solaris ‘make’
 execute recipes containing the ‘$(MAKE)’ string even when they are
-running in dry mode.  So if we didn’t break the recipe above in two
+running in dry mode.  So if we didn't break the recipe above in two
 invocations, the file ‘data.c’ would be removed even upon ‘make -n’.
 Not nice.
 
@@ -3954,14 +4142,13 @@
              @test -f $@ || rm -f data.c
              @test -f $@ || $(MAKE) $(AM_MAKEFLAGS) data.c
 
-   However there are now three minor problems in this setup.  One is
-related to the timestamp ordering of ‘data.h’, ‘data.w’, ‘data.x’, and
-‘data.c’.  Another one is a race condition if a parallel ‘make’ attempts
-to run multiple instances of the recover block at once.  Finally, the
-recursive rule breaks ‘make -n’ when run with GNU ‘make’ (as well as
-some other ‘make’ implementations), as it may remove ‘data.h’ even when
-it should not (*note How the ‘MAKE’ Variable Works: (make)MAKE
-Variable.).
+   However there are now three problems in this setup.  One is related
+to the timestamp ordering of ‘data.h’, ‘data.w’, ‘data.x’, and ‘data.c’.
+A second is a race condition if a parallel ‘make’ attempts to run
+multiple instances of the recover block at once.  Finally, the recursive
+rule breaks ‘make -n’ when run with GNU ‘make’ (as well as some other
+‘make’ implementations), as it may remove ‘data.h’ even when it should
+not (*note How the ‘MAKE’ Variable Works: (make)MAKE Variable.).
 
    Let us deal with the first problem.  ‘foo’ outputs four files, but we
 do not know in which order these files are created.  Suppose that
@@ -3984,7 +4171,7 @@
              @test -f $@ || $(MAKE) $(AM_MAKEFLAGS) data.c
 
    Another solution is to use a different and dedicated file as witness,
-rather than using any of ‘foo’’s outputs.
+rather than using any of ‘foo’'s outputs.
 
      data.stamp: data.foo data.bar
              @rm -f data.tmp
@@ -4116,17 +4303,11 @@
                fi; \
              fi
 
-   For completeness it should be noted that GNU ‘make’ is able to
-express rules with multiple output files using pattern rules (*note
-Pattern Rule Examples: (make)Pattern Examples.).  We do not discuss
-pattern rules here because they are not portable, but they can be
-convenient in packages that assume GNU ‘make’.
-
 &#x1f;
 File: automake.info,  Node: Hard-Coded Install Paths,  Next: Debugging Make Rules,  Prev: Multiple Outputs,  Up: FAQ
 
-26.10 Installing to Hard-Coded Locations
-========================================
+26.9 Installing to Hard-Coded Locations
+=======================================
 
      My package needs to install some configuration file.  I tried to use
      the following rule, but ‘make distcheck’ fails.  Why?
@@ -4174,7 +4355,7 @@
 variables to match their site conventions.
 
    Installing files that should be used by another package is slightly
-more involved.  Let’s take an example and assume you want to install a
+more involved.  Let's take an example and assume you want to install a
 shared library that is a Python extension module.  If you ask Python
 where to install the library, it will answer something like this:
 
@@ -4186,8 +4367,8 @@
 non-root users will not be able to install the package; hence distcheck
 fails.
 
-   Let’s do better.  The ‘sysconfig.get_python_lib()’ function accepts a
-third argument that will replace Python’s installation prefix.
+   Let's do better.  The ‘sysconfig.get_python_lib()’ function accepts a
+third argument that will replace Python's installation prefix.
 
      % python -c 'from distutils import sysconfig;
                   print sysconfig.get_python_lib(1,0,"${exec_prefix}")'
@@ -4200,7 +4381,7 @@
    • non-root users can install your package too; they will have the
      extension module in a place that is not searched by Python but they
      can work around this using environment variables (and if you
-     installed scripts that use this shared library, it’s easy to tell
+     installed scripts that use this shared library, it's easy to tell
      Python where to look in the beginning of your script, so the script
      works in both cases).
 
@@ -4213,7 +4394,7 @@
 here is how ‘AM_PATH_LISPDIR’ (*note Emacs Lisp::) computes
 ‘$(lispdir)’:
 
-     $EMACS -batch -Q -eval '(while load-path
+     $EMACS -batch -no-site-file -eval '(while load-path
        (princ (concat (car load-path) "\n"))
        (setq load-path (cdr load-path)))' >conftest.out
      lispdir=`sed -n
@@ -4232,24 +4413,25 @@
 appropriately.
 
    The emacs case looks complicated because it processes a list and
-expects two possible layouts; otherwise it’s easy, and the benefits for
+expects two possible layouts; otherwise it's easy, and the benefits for
 non-root users are worth the extra ‘sed’ invocation.
 
 &#x1f;
 File: automake.info,  Node: Debugging Make Rules,  Next: Reporting Bugs,  Prev: Hard-Coded Install Paths,  Up: FAQ
 
-26.11 Debugging Make Rules
+26.10 Debugging Make Rules
 ==========================
 
 The rules and dependency trees generated by ‘automake’ can get rather
-complex, and leave the developer head-scratching when things don’t work
+complex, and leave the developer head-scratching when things don't work
 as expected.  Besides the debug options provided by the ‘make’ command
-(*note (make)Options Summary::), here’s a couple of further hints for
+(*note (make)Options Summary::), here's a couple of further hints for
 debugging makefiles generated by ‘automake’ effectively:
 
    • If less verbose output has been enabled in the package with the use
-     of silent rules (*note Automake Silent Rules::), you can use ‘make
-     V=1’ to see the commands being executed.
+     of silent rules (*note Automake Silent Rules::), you'll probably
+     want undo that and see the actual commands being run: *note
+     Unsilencing Automake::.
 
    • ‘make -n’ can help show what would be done without actually doing
      it.  However, this _still executes_ commands prefixed with ‘+’,
@@ -4257,9 +4439,9 @@
      ‘$(MAKE)’ or ‘${MAKE}’ (*note (make)Instead of Execution::).
      Typically, this is helpful to show what recursive rules would do,
      but it means that, in your own rules, you should not mix such
-     recursion with actions that change any files.(1)  Furthermore, note
-     that GNU ‘make’ will update prerequisites for the ‘Makefile’ file
-     itself even with ‘-n’ (*note (make)Remaking Makefiles::).
+     recursion with actions that change any files.(1)  Furthermore, GNU
+     ‘make’ will update prerequisites for the ‘Makefile’ file itself
+     even with ‘-n’ (*note (make)Remaking Makefiles::).
 
    • ‘make SHELL="/bin/bash -vx"’ can help debug complex rules.  *Note
      (autoconf)The Make Macro SHELL::, for some portability quirks
@@ -4277,14 +4459,14 @@
 
    ---------- Footnotes ----------
 
-   (1) Automake’s ‘dist’ and ‘distcheck’ rules had a bug in this regard
+   (1) Automake's ‘dist’ and ‘distcheck’ rules had a bug in this regard
 in that they created directories even with ‘-n’, but this has been fixed
 in Automake 1.11.
 
 &#x1f;
 File: automake.info,  Node: Reporting Bugs,  Prev: Debugging Make Rules,  Up: FAQ
 
-26.12 Reporting Bugs
+26.11 Reporting Bugs
 ====================
 
 Most nontrivial software has bugs.  Automake is no exception.  We cannot
@@ -4312,7 +4494,7 @@
 email to <bug-automake@gnu.org>.  This will then open a new bug in the
 bug tracker (https://debbugs.gnu.org/automake).  Be sure to include the
 versions of Autoconf and Automake that you use and the kind of system
-you’re on.  Ideally, post a minimal ‘Makefile.am’ and ‘configure.ac’
+you're on.  Ideally, post a minimal ‘Makefile.am’ and ‘configure.ac’
 that reproduces the problem you encounter.  If you have encountered test
 suite failures, please attach the ‘test-suite.log’ file.
 
@@ -4334,7 +4516,7 @@
 
                      Version 1.3, 3 November 2008
 
-     Copyright © 2000–2021 Free Software Foundation, Inc.
+     Copyright © 2000-2024 Free Software Foundation, Inc.
      <https://fsf.org/>
 
      Everyone is permitted to copy and distribute verbatim copies
@@ -4350,7 +4532,7 @@
      author and publisher a way to get credit for their work, while not
      being considered responsible for modifications made by others.
 
-     This License is a kind of “copyleft”, which means that derivative
+     This License is a kind of "copyleft", which means that derivative
      works of the document must themselves be free in the same sense.
      It complements the GNU General Public License, which is a copyleft
      license designed for free software.
@@ -4371,18 +4553,18 @@
      be distributed under the terms of this License.  Such a notice
      grants a world-wide, royalty-free license, unlimited in duration,
      to use that work under the conditions stated herein.  The
-     “Document”, below, refers to any such manual or work.  Any member
-     of the public is a licensee, and is addressed as “you”.  You accept
+     "Document", below, refers to any such manual or work.  Any member
+     of the public is a licensee, and is addressed as "you".  You accept
      the license if you copy, modify or distribute the work in a way
      requiring permission under copyright law.
 
-     A “Modified Version” of the Document means any work containing the
+     A "Modified Version" of the Document means any work containing the
      Document or a portion of it, either copied verbatim, or with
      modifications and/or translated into another language.
 
-     A “Secondary Section” is a named appendix or a front-matter section
+     A "Secondary Section" is a named appendix or a front-matter section
      of the Document that deals exclusively with the relationship of the
-     publishers or authors of the Document to the Document’s overall
+     publishers or authors of the Document to the Document's overall
      subject (or to related matters) and contains nothing that could
      fall directly within that overall subject.  (Thus, if the Document
      is in part a textbook of mathematics, a Secondary Section may not
@@ -4391,7 +4573,7 @@
      of legal, commercial, philosophical, ethical or political position
      regarding them.
 
-     The “Invariant Sections” are certain Secondary Sections whose
+     The "Invariant Sections" are certain Secondary Sections whose
      titles are designated, as being those of Invariant Sections, in the
      notice that says that the Document is released under this License.
      If a section does not fit the above definition of Secondary then it
@@ -4399,13 +4581,13 @@
      contain zero Invariant Sections.  If the Document does not identify
      any Invariant Sections then there are none.
 
-     The “Cover Texts” are certain short passages of text that are
+     The "Cover Texts" are certain short passages of text that are
      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
      that says that the Document is released under this License.  A
      Front-Cover Text may be at most 5 words, and a Back-Cover Text may
      be at most 25 words.
 
-     A “Transparent” copy of the Document means a machine-readable copy,
+     A "Transparent" copy of the Document means a machine-readable copy,
      represented in a format whose specification is available to the
      general public, that is suitable for revising the document
      straightforwardly with generic text editors or (for images composed
@@ -4417,7 +4599,7 @@
      been arranged to thwart or discourage subsequent modification by
      readers is not Transparent.  An image format is not Transparent if
      used for any substantial amount of text.  A copy that is not
-     “Transparent” is called “Opaque”.
+     "Transparent" is called "Opaque".
 
      Examples of suitable formats for Transparent copies include plain
      ASCII without markup, Texinfo input format, LaTeX input format,
@@ -4430,23 +4612,23 @@
      the machine-generated HTML, PostScript or PDF produced by some word
      processors for output purposes only.
 
-     The “Title Page” means, for a printed book, the title page itself,
+     The "Title Page" means, for a printed book, the title page itself,
      plus such following pages as are needed to hold, legibly, the
      material this License requires to appear in the title page.  For
-     works in formats which do not have any title page as such, “Title
-     Page” means the text near the most prominent appearance of the
-     work’s title, preceding the beginning of the body of the text.
+     works in formats which do not have any title page as such, "Title
+     Page" means the text near the most prominent appearance of the
+     work's title, preceding the beginning of the body of the text.
 
-     The “publisher” means any person or entity that distributes copies
+     The "publisher" means any person or entity that distributes copies
      of the Document to the public.
 
-     A section “Entitled XYZ” means a named subunit of the Document
+     A section "Entitled XYZ" means a named subunit of the Document
      whose title either is precisely XYZ or contains XYZ in parentheses
      following text that translates XYZ in another language.  (Here XYZ
      stands for a specific section name mentioned below, such as
-     “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.)
-     To “Preserve the Title” of such a section when you modify the
-     Document means that it remains a section “Entitled XYZ” according
+     "Acknowledgements", "Dedications", "Endorsements", or "History".)
+     To "Preserve the Title" of such a section when you modify the
+     Document means that it remains a section "Entitled XYZ" according
      to this definition.
 
      The Document may include Warranty Disclaimers next to the notice
@@ -4476,7 +4658,7 @@
 
      If you publish printed copies (or copies in media that commonly
      have printed covers) of the Document, numbering more than 100, and
-     the Document’s license notice requires Cover Texts, you must
+     the Document's license notice requires Cover Texts, you must
      enclose the copies in covers that carry, clearly and legibly, all
      these Cover Texts: Front-Cover Texts on the front cover, and
      Back-Cover Texts on the back cover.  Both covers must also clearly
@@ -4548,15 +4730,15 @@
           the Addendum below.
 
        G. Preserve in that license notice the full lists of Invariant
-          Sections and required Cover Texts given in the Document’s
+          Sections and required Cover Texts given in the Document's
           license notice.
 
        H. Include an unaltered copy of this License.
 
-       I. Preserve the section Entitled “History”, Preserve its Title,
+       I. Preserve the section Entitled "History", Preserve its Title,
           and add to it an item stating at least the title, year, new
           authors, and publisher of the Modified Version as given on the
-          Title Page.  If there is no section Entitled “History” in the
+          Title Page.  If there is no section Entitled "History" in the
           Document, create one stating the title, year, authors, and
           publisher of the Document as given on its Title Page, then add
           an item describing the Modified Version as stated in the
@@ -4566,12 +4748,12 @@
           for public access to a Transparent copy of the Document, and
           likewise the network locations given in the Document for
           previous versions it was based on.  These may be placed in the
-          “History” section.  You may omit a network location for a work
+          "History" section.  You may omit a network location for a work
           that was published at least four years before the Document
           itself, or if the original publisher of the version it refers
           to gives permission.
 
-       K. For any section Entitled “Acknowledgements” or “Dedications”,
+       K. For any section Entitled "Acknowledgements" or "Dedications",
           Preserve the Title of the section, and preserve in the section
           all the substance and tone of each of the contributor
           acknowledgements and/or dedications given therein.
@@ -4580,11 +4762,11 @@
           in their text and in their titles.  Section numbers or the
           equivalent are not considered part of the section titles.
 
-       M. Delete any section Entitled “Endorsements”.  Such a section
+       M. Delete any section Entitled "Endorsements".  Such a section
           may not be included in the Modified Version.
 
        N. Do not retitle any existing section to be Entitled
-          “Endorsements” or to conflict in title with any Invariant
+          "Endorsements" or to conflict in title with any Invariant
           Section.
 
        O. Preserve any Warranty Disclaimers.
@@ -4593,15 +4775,15 @@
      appendices that qualify as Secondary Sections and contain no
      material copied from the Document, you may at your option designate
      some or all of these sections as invariant.  To do this, add their
-     titles to the list of Invariant Sections in the Modified Version’s
+     titles to the list of Invariant Sections in the Modified Version's
      license notice.  These titles must be distinct from any other
      section titles.
 
-     You may add a section Entitled “Endorsements”, provided it contains
+     You may add a section Entitled "Endorsements", provided it contains
      nothing but endorsements of your Modified Version by various
-     parties—for example, statements of peer review or that the text has
-     been approved by an organization as the authoritative definition of
-     a standard.
+     parties--for example, statements of peer review or that the text
+     has been approved by an organization as the authoritative
+     definition of a standard.
 
      You may add a passage of up to five words as a Front-Cover Text,
      and a passage of up to 25 words as a Back-Cover Text, to the end of
@@ -4639,10 +4821,10 @@
      combined work.
 
      In the combination, you must combine any sections Entitled
-     “History” in the various original documents, forming one section
-     Entitled “History”; likewise combine any sections Entitled
-     “Acknowledgements”, and any sections Entitled “Dedications”.  You
-     must delete all sections Entitled “Endorsements.”
+     "History" in the various original documents, forming one section
+     Entitled "History"; likewise combine any sections Entitled
+     "Acknowledgements", and any sections Entitled "Dedications".  You
+     must delete all sections Entitled "Endorsements."
 
   6. COLLECTIONS OF DOCUMENTS
 
@@ -4663,16 +4845,16 @@
 
      A compilation of the Document or its derivatives with other
      separate and independent documents or works, in or on a volume of a
-     storage or distribution medium, is called an “aggregate” if the
+     storage or distribution medium, is called an "aggregate" if the
      copyright resulting from the compilation is not used to limit the
-     legal rights of the compilation’s users beyond what the individual
+     legal rights of the compilation's users beyond what the individual
      works permit.  When the Document is included in an aggregate, this
      License does not apply to the other works in the aggregate which
      are not themselves derivative works of the Document.
 
      If the Cover Text requirement of section 3 is applicable to these
      copies of the Document, then if the Document is less than one half
-     of the entire aggregate, the Document’s Cover Texts may be placed
+     of the entire aggregate, the Document's Cover Texts may be placed
      on covers that bracket the Document within the aggregate, or the
      electronic equivalent of covers if the Document is in electronic
      form.  Otherwise they must appear on printed covers that bracket
@@ -4694,8 +4876,8 @@
      this License or a notice or disclaimer, the original version will
      prevail.
 
-     If a section in the Document is Entitled “Acknowledgements”,
-     “Dedications”, or “History”, the requirement (section 4) to
+     If a section in the Document is Entitled "Acknowledgements",
+     "Dedications", or "History", the requirement (section 4) to
      Preserve its Title (section 1) will typically require changing the
      actual title.
 
@@ -4736,7 +4918,7 @@
 
      Each version of the License is given a distinguishing version
      number.  If the Document specifies that a particular numbered
-     version of this License “or any later version” applies to it, you
+     version of this License "or any later version" applies to it, you
      have the option of following the terms and conditions either of
      that specified version or of any later version that has been
      published (not as a draft) by the Free Software Foundation.  If the
@@ -4744,29 +4926,29 @@
      choose any version ever published (not as a draft) by the Free
      Software Foundation.  If the Document specifies that a proxy can
      decide which future versions of this License can be used, that
-     proxy’s public statement of acceptance of a version permanently
+     proxy's public statement of acceptance of a version permanently
      authorizes you to choose that version for the Document.
 
   11. RELICENSING
 
-     “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any
+     "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
      World Wide Web server that publishes copyrightable works and also
      provides prominent facilities for anybody to edit those works.  A
      public wiki that anybody can edit is an example of such a server.
-     A “Massive Multiauthor Collaboration” (or “MMC”) contained in the
+     A "Massive Multiauthor Collaboration" (or "MMC") contained in the
      site means any set of copyrightable works thus published on the MMC
      site.
 
-     “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0
+     "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
      license published by Creative Commons Corporation, a not-for-profit
      corporation with a principal place of business in San Francisco,
      California, as well as future copyleft versions of that license
      published by that same organization.
 
-     “Incorporate” means to publish or republish a Document, in whole or
+     "Incorporate" means to publish or republish a Document, in whole or
      in part, as part of another Document.
 
-     An MMC is “eligible for relicensing” if it is licensed under this
+     An MMC is "eligible for relicensing" if it is licensed under this
      License, and if all works that were first published under this
      License somewhere other than this MMC, and subsequently
      incorporated in whole or in part into the MMC, (1) had no cover
@@ -4793,7 +4975,7 @@
        Free Documentation License''.
 
    If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the “with...Texts.” line with this:
+Texts, replace the "with...Texts." line with this:
 
          with the Invariant Sections being LIST THEIR TITLES, with
          the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -4837,7 +5019,7 @@
 * AC_CONFIG_AUX_DIR <1>:                 Subpackages.         (line   6)
 * AC_CONFIG_FILES:                       Requirements.        (line  15)
 * AC_CONFIG_FILES <1>:                   Basics of Distribution.
-                                                              (line  26)
+                                                              (line  39)
 * AC_CONFIG_HEADERS:                     Optional.            (line  50)
 * AC_CONFIG_LIBOBJ_DIR:                  Optional.            (line  46)
 * AC_CONFIG_LIBOBJ_DIR <1>:              LIBOBJS.             (line  51)
@@ -4860,54 +5042,55 @@
 * AC_PROG_F77:                           Optional.            (line 104)
 * AC_PROG_FC:                            Optional.            (line 119)
 * AC_PROG_LEX:                           Public Macros.       (line  94)
-* AC_PROG_LEX <1>:                       Optional.            (line 134)
+* AC_PROG_LEX <1>:                       Optional.            (line 135)
 * AC_PROG_LIBTOOL:                       Optional.            (line 124)
 * AC_PROG_OBJC:                          Optional.            (line  96)
 * AC_PROG_OBJCXX:                        Optional.            (line 100)
 * AC_PROG_RANLIB:                        Optional.            (line  88)
-* AC_PROG_YACC:                          Optional.            (line 128)
-* AC_REQUIRE_AUX_FILE:                   Optional.            (line 138)
-* AC_SUBST:                              Optional.            (line 146)
-* AM_CONDITIONAL:                        Optional.            (line 159)
+* AC_PROG_YACC:                          Optional.            (line 129)
+* AC_REQUIRE_AUX_FILE:                   Optional.            (line 139)
+* AC_SUBST:                              Optional.            (line 147)
+* AM_COND_IF:                            Optional.            (line 163)
+* AM_COND_IF <1>:                        Usage of Conditionals.
+                                                              (line  75)
+* AM_COND_IF <2>:                        Usage of Conditionals.
+                                                              (line  79)
+* AM_CONDITIONAL:                        Optional.            (line 160)
 * AM_CONDITIONAL <1>:                    Usage of Conditionals.
                                                               (line   6)
 * AM_CONDITIONAL <2>:                    Usage of Conditionals.
                                                               (line   9)
-* AM_COND_IF:                            Optional.            (line 162)
-* AM_COND_IF <1>:                        Usage of Conditionals.
-                                                              (line  66)
-* AM_COND_IF <2>:                        Usage of Conditionals.
-                                                              (line  70)
 * AM_DEP_TRACK:                          Private Macros.      (line  14)
-* AM_GNU_GETTEXT:                        Optional.            (line 168)
-* AM_GNU_GETTEXT_INTL_SUBDIR:            Optional.            (line 174)
+* AM_GNU_GETTEXT:                        Optional.            (line 169)
+* AM_GNU_GETTEXT_INTL_SUBDIR:            Optional.            (line 175)
 * AM_INIT_AUTOMAKE:                      Requirements.        (line   6)
 * AM_INIT_AUTOMAKE <1>:                  Public Macros.       (line   7)
 * AM_MAINTAINER_MODE:                    Rebuilding.          (line   9)
 * AM_MAINTAINER_MODE <1>:                maintainer-mode.     (line  38)
-* AM_MAINTAINER_MODE(DEFAULT-MODE):    Optional.            (line 179)
+* AM_MAINTAINER_MODE(DEFAULT-MODE):    Optional.            (line 180)
 * AM_MAKE_INCLUDE:                       Private Macros.      (line  20)
-* AM_MISSING_PROG:                       Public Macros.       (line 110)
+* AM_MISSING_PROG:                       Public Macros.       (line 111)
 * AM_OUTPUT_DEPENDENCY_COMMANDS:         Private Macros.      (line  15)
 * AM_PATH_LISPDIR:                       Public Macros.       (line  60)
 * AM_PATH_PYTHON:                        Python.              (line  28)
 * AM_PROG_AR:                            Public Macros.       (line  75)
 * AM_PROG_AS:                            Public Macros.       (line  82)
 * AM_PROG_CC_C_O:                        Public Macros.       (line  87)
-* AM_PROG_GCJ:                           Public Macros.       (line  99)
+* AM_PROG_GCJ:                           Public Macros.       (line 100)
 * AM_PROG_INSTALL_STRIP:                 Private Macros.      (line  25)
 * AM_PROG_LEX:                           Public Macros.       (line  94)
 * AM_PROG_MKDIR_P:                       Obsolete Macros.     (line  14)
-* AM_PROG_UPC:                           Public Macros.       (line 104)
-* AM_PROG_VALAC:                         Vala Support.        (line  20)
+* AM_PROG_UPC:                           Public Macros.       (line 105)
+* AM_PROG_VALAC:                         Vala Support.        (line  24)
 * AM_SANITY_CHECK:                       Private Macros.      (line  30)
 * AM_SET_DEPDIR:                         Private Macros.      (line  13)
-* AM_SILENT_RULES:                       Public Macros.       (line 118)
-* AM_SUBST_NOTMAKE(VAR):                 Optional.            (line 187)
-* AM_WITH_DMALLOC:                       Public Macros.       (line 122)
+* AM_SILENT_RULES:                       Public Macros.       (line 119)
+* AM_SUBST_NOTMAKE(VAR):                 Optional.            (line 188)
+* AM_WITH_DMALLOC:                       Public Macros.       (line 123)
+* LT_INIT:                               Optional.            (line 125)
 * m4_include:                            Basics of Distribution.
-                                                              (line  30)
-* m4_include <1>:                        Optional.            (line 197)
+                                                              (line  43)
+* m4_include <1>:                        Optional.            (line 198)
 
 &#x1f;
 File: automake.info,  Node: Variable Index,  Next: General Index,  Prev: Macro Index,  Up: Indices
@@ -4923,15 +5106,15 @@
 * _LIBRARIES:                            A Library.           (line   6)
 * _LISP:                                 Emacs Lisp.          (line   6)
 * _LOG_COMPILE:                          Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * _LOG_COMPILER:                         Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * _LOG_DRIVER:                           Declaring Custom Test Drivers.
                                                               (line   6)
 * _LOG_DRIVER_FLAGS:                     Declaring Custom Test Drivers.
                                                               (line   6)
 * _LOG_FLAGS:                            Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * _LTLIBRARIES:                          Libtool Libraries.   (line   6)
 * _MANS:                                 Man Pages.           (line   6)
 * _PROGRAMS:                             Uniform.             (line  11)
@@ -4942,8 +5125,9 @@
 * _SOURCES <1>:                          Program Sources.     (line  33)
 * _SOURCES <2>:                          Default _SOURCES.    (line   6)
 * _TEXINFOS:                             Texinfo.             (line   6)
-* _TEXINFOS <1>:                         Texinfo.             (line  65)
+* _TEXINFOS <1>:                         Texinfo.             (line  87)
 * ACLOCAL_AUTOMAKE_DIR:                  aclocal Options.     (line  12)
+* ACLOCAL_PATH:                          aclocal Options.     (line  24)
 * ALLOCA:                                LTLIBOBJS.           (line   6)
 * ALLOCA <1>:                            LIBOBJS.             (line   6)
 * AM_CCASFLAGS:                          Assembly Support.    (line  10)
@@ -4955,59 +5139,61 @@
 * AM_CXXFLAGS:                           C++ Support.         (line  22)
 * AM_DEFAULT_SOURCE_EXT:                 Default _SOURCES.    (line   6)
 * AM_DEFAULT_V:                          Automake Silent Rules.
-                                                              (line 120)
+                                                              (line 124)
 * AM_DEFAULT_VERBOSITY:                  Automake Silent Rules.
-                                                              (line 120)
-* AM_DISTCHECK_CONFIGURE_FLAGS:          Checking the Distribution.
-                                                              (line  30)
+                                                              (line 124)
+* AM_DISTCHECK_CONFIGURE_FLAGS:          DISTCHECK_CONFIGURE_FLAGS.
+                                                              (line   6)
+* AM_DISTCHECK_DVI_TARGET:               dvi and distcheck.   (line  11)
 * AM_ETAGSFLAGS:                         Tags.                (line  27)
 * AM_EXT_LOG_DRIVER_FLAGS:               Declaring Custom Test Drivers.
                                                               (line   6)
 * AM_EXT_LOG_FLAGS:                      Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * AM_FCFLAGS:                            Fortran 9x Support.  (line  22)
 * AM_FFLAGS:                             Fortran 77 Support.  (line  22)
 * AM_GCJFLAGS:                           Java Support with gcj.
                                                               (line  26)
 * AM_INSTALLCHECK_STD_OPTIONS_EXEMPT:    List of Automake options.
-                                                              (line 150)
+                                                              (line 155)
 * AM_JAVACFLAGS:                         Java.                (line  44)
 * AM_LDFLAGS:                            Linking.             (line  10)
 * AM_LDFLAGS <1>:                        Program Variables.   (line  59)
-* AM_LFLAGS:                             Yacc and Lex.        (line  65)
+* AM_LFLAGS:                             Yacc and Lex.        (line  66)
 * AM_LIBTOOLFLAGS:                       Libtool Flags.       (line   6)
 * AM_LOG_DRIVER_FLAGS:                   Declaring Custom Test Drivers.
                                                               (line   6)
 * AM_LOG_FLAGS:                          Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * AM_MAKEFLAGS:                          Subdirectories.      (line  29)
-* AM_MAKEINFOFLAGS:                      Texinfo.             (line 115)
-* AM_MAKEINFOHTMLFLAGS:                  Texinfo.             (line 116)
+* AM_MAKEINFOFLAGS:                      Texinfo.             (line 137)
+* AM_MAKEINFOHTMLFLAGS:                  Texinfo.             (line 138)
 * AM_OBJCFLAGS:                          Objective C Support. (line  22)
 * AM_OBJCXXFLAGS:                        Objective C++ Support.
                                                               (line  22)
 * AM_RFLAGS:                             Fortran 77 Support.  (line  28)
 * AM_RUNTESTFLAGS:                       DejaGnu Tests.       (line  24)
-* AM_TESTSUITE_SUMMARY_HEADER:           Scripts-based Testsuites.
-                                                              (line  69)
 * AM_TESTS_ENVIRONMENT:                  Testsuite Environment Overrides.
                                                               (line   6)
 * AM_TESTS_FD_REDIRECT:                  Testsuite Environment Overrides.
                                                               (line  14)
+* AM_TESTSUITE_SUMMARY_HEADER:           Scripts-based Testsuites.
+                                                              (line  69)
+* AM_TEXI2FLAGS:                         Texinfo.             (line 139)
 * AM_UPCFLAGS:                           Unified Parallel C Support.
                                                               (line  21)
-* AM_UPDATE_INFO_DIR:                    Texinfo.             (line  92)
+* AM_UPDATE_INFO_DIR:                    Texinfo.             (line 114)
 * AM_V:                                  Automake Silent Rules.
-                                                              (line 120)
-* AM_VALAFLAGS:                          Vala Support.        (line  44)
+                                                              (line 124)
 * AM_V_at:                               Automake Silent Rules.
-                                                              (line 120)
+                                                              (line 124)
 * AM_V_GEN:                              Automake Silent Rules.
-                                                              (line 120)
-* AM_YFLAGS:                             Yacc and Lex.        (line  37)
+                                                              (line 124)
+* AM_VALAFLAGS:                          Vala Support.        (line  48)
+* AM_YFLAGS:                             Yacc and Lex.        (line  38)
 * AR:                                    Public Macros.       (line  75)
 * AUTOCONF:                              automake Invocation. (line  28)
-* AUTOM4TE:                              aclocal Invocation.  (line  44)
+* AUTOM4TE:                              aclocal Invocation.  (line  45)
 * AUTOMAKE_JOBS:                         automake Invocation. (line 195)
 * AUTOMAKE_LIBDIR:                       automake Invocation. (line  64)
 * AUTOMAKE_OPTIONS:                      Public Macros.       (line  10)
@@ -5021,14 +5207,14 @@
 * BUILT_SOURCES, and dist target:        List of Automake options.
                                                               (line  81)
 * BZIP2:                                 The Types of Distributions.
-                                                              (line  17)
+                                                              (line  18)
 * CC:                                    Program Variables.   (line  12)
 * CCAS:                                  Public Macros.       (line  82)
 * CCAS <1>:                              Assembly Support.    (line  10)
 * CCASFLAGS:                             Public Macros.       (line  82)
 * CCASFLAGS <1>:                         Assembly Support.    (line  10)
 * CFLAGS:                                Program Variables.   (line  12)
-* check_:                                Uniform.             (line  95)
+* check_:                                Uniform.             (line  96)
 * check_LTLIBRARIES:                     Libtool Convenience Libraries.
                                                               (line   6)
 * check_PROGRAMS:                        Program Sources.     (line   6)
@@ -5039,23 +5225,23 @@
 * CLASSPATH_ENV:                         Java.                (line  53)
 * CLEANFILES:                            Clean.               (line  13)
 * COMPILE:                               Program Variables.   (line  55)
-* CONFIGURE_DEPENDENCIES:                Rebuilding.          (line  12)
 * CONFIG_STATUS_DEPENDENCIES:            Rebuilding.          (line  12)
+* CONFIGURE_DEPENDENCIES:                Rebuilding.          (line  12)
 * CPPFLAGS:                              Program Variables.   (line  12)
 * CPPFLAGS <1>:                          Assembly Support.    (line  10)
 * CSCOPE:                                Tags.                (line  57)
-* CSCOPEFLAGS:                           Tags.                (line  57)
 * CSCOPE_ARGS:                           Tags.                (line  57)
+* CSCOPEFLAGS:                           Tags.                (line  57)
 * CTAGS:                                 Tags.                (line  43)
-* CTAGSFLAGS:                            Tags.                (line  43)
 * CTAGS_ARGS:                            Tags.                (line  43)
+* CTAGSFLAGS:                            Tags.                (line  43)
 * CXX:                                   C++ Support.         (line  16)
 * CXXCOMPILE:                            C++ Support.         (line  25)
 * CXXFLAGS:                              C++ Support.         (line  19)
 * CXXLINK:                               C++ Support.         (line  29)
 * CXXLINK <1>:                           How the Linker is Chosen.
                                                               (line  12)
-* DATA:                                  Uniform.             (line 101)
+* DATA:                                  Uniform.             (line 102)
 * DATA <1>:                              Data.                (line   7)
 * data_DATA:                             Data.                (line   9)
 * DEFS:                                  Program Variables.   (line  12)
@@ -5064,20 +5250,6 @@
 * DESTDIR <1>:                           Staged Installs.     (line   6)
 * DISABLE_HARD_ERRORS:                   Scripts-based Testsuites.
                                                               (line  32)
-* DISTCHECK_CONFIGURE_FLAGS:             Checking the Distribution.
-                                                              (line  30)
-* distcleancheck_listfiles:              Checking the Distribution.
-                                                              (line  92)
-* distcleancheck_listfiles <1>:          Errors with distclean.
-                                                              (line 112)
-* DISTCLEANFILES:                        Clean.               (line  13)
-* DISTCLEANFILES <1>:                    Checking the Distribution.
-                                                              (line  92)
-* distdir:                               The dist Hook.       (line  34)
-* distdir <1>:                           Third-Party Makefiles.
-                                                              (line  25)
-* distuninstallcheck_listfiles:          Checking the Distribution.
-                                                              (line 128)
 * dist_:                                 Alternative.         (line  28)
 * dist_ <1>:                             Fine-grained Distribution Control.
                                                               (line   6)
@@ -5086,34 +5258,46 @@
 * DIST_SUBDIRS:                          Subdirectories with AM_CONDITIONAL.
                                                               (line  25)
 * DIST_SUBDIRS <1>:                      Basics of Distribution.
-                                                              (line  73)
-* DVIPS:                                 Texinfo.             (line 141)
+                                                              (line  86)
+* DISTCHECK_CONFIGURE_FLAGS:             DISTCHECK_CONFIGURE_FLAGS.
+                                                              (line   6)
+* distcleancheck_listfiles:              distcleancheck.      (line   6)
+* distcleancheck_listfiles <1>:          Errors with distclean.
+                                                              (line 133)
+* DISTCLEANFILES:                        Clean.               (line  13)
+* DISTCLEANFILES <1>:                    distcleancheck.      (line   6)
+* distdir:                               The dist Hook.       (line  34)
+* distdir <1>:                           Third-Party Makefiles.
+                                                              (line  25)
+* distuninstallcheck_listfiles:          distuninstallcheck.  (line   6)
+* doc_DATA:                              Data.                (line   9)
+* DVIPS:                                 Texinfo.             (line 165)
 * EMACS:                                 Public Macros.       (line  60)
 * EMPTY_AUTOMAKE_TARGETS:                Third-Party Makefiles.
                                                               (line  88)
 * ETAGS:                                 Tags.                (line  27)
-* ETAGSFLAGS:                            Tags.                (line  27)
 * ETAGS_ARGS:                            Tags.                (line  27)
+* ETAGSFLAGS:                            Tags.                (line  27)
 * EXPECT:                                DejaGnu Tests.       (line  19)
-* EXTRA_DIST:                            Basics of Distribution.
-                                                              (line  60)
-* EXTRA_maude_DEPENDENCIES:              Linking.             (line  41)
-* EXTRA_maude_DEPENDENCIES <1>:          Program and Library Variables.
-                                                              (line 129)
-* EXTRA_maude_SOURCES:                   Program and Library Variables.
-                                                              (line  60)
-* EXTRA_PROGRAMS:                        Conditional Programs.
-                                                              (line  15)
 * EXT_LOG_COMPILE:                       Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * EXT_LOG_COMPILER:                      Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * EXT_LOG_DRIVER:                        Declaring Custom Test Drivers.
                                                               (line   6)
 * EXT_LOG_DRIVER_FLAGS:                  Declaring Custom Test Drivers.
                                                               (line   6)
 * EXT_LOG_FLAGS:                         Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
+* EXTRA_DIST:                            Basics of Distribution.
+                                                              (line  73)
+* EXTRA_maude_DEPENDENCIES:              Linking.             (line  41)
+* EXTRA_maude_DEPENDENCIES <1>:          Program and Library Variables.
+                                                              (line 134)
+* EXTRA_maude_SOURCES:                   Program and Library Variables.
+                                                              (line  60)
+* EXTRA_PROGRAMS:                        Conditional Programs.
+                                                              (line  15)
 * F77:                                   Fortran 77 Support.  (line  16)
 * F77COMPILE:                            Fortran 77 Support.  (line  31)
 * F77LINK:                               How the Linker is Chosen.
@@ -5128,8 +5312,8 @@
 * FLIBS:                                 Mixing Fortran 77 With C and C++.
                                                               (line  21)
 * FLINK:                                 Fortran 77 Support.  (line  35)
-* GCJ:                                   Public Macros.       (line  99)
-* GCJFLAGS:                              Public Macros.       (line  99)
+* GCJ:                                   Public Macros.       (line 100)
+* GCJFLAGS:                              Public Macros.       (line 100)
 * GCJFLAGS <1>:                          Java Support with gcj.
                                                               (line  16)
 * GCJLINK:                               How the Linker is Chosen.
@@ -5137,107 +5321,112 @@
 * GTAGS_ARGS:                            Tags.                (line  62)
 * GZIP_ENV:                              The Types of Distributions.
                                                               (line  10)
-* HEADERS:                               Uniform.             (line 101)
+* HEADERS:                               Uniform.             (line 102)
 * host_triplet:                          Optional.            (line  14)
-* INCLUDES:                              Program Variables.   (line  44)
+* IGNORE_SKIPPED_LOGS:                   Parallel Test Harness.
+                                                              (line  21)
 * include_HEADERS:                       Headers.             (line   6)
+* INCLUDES:                              Program Variables.   (line  44)
 * info_TEXINFOS:                         Texinfo.             (line   6)
-* JAVA:                                  Uniform.             (line 101)
+* JAVA:                                  Uniform.             (line 102)
 * JAVAC:                                 Java.                (line  37)
 * JAVACFLAGS:                            Java.                (line  40)
 * JAVAROOT:                              Java.                (line  49)
 * LDADD:                                 Linking.             (line  10)
 * LDFLAGS:                               Program Variables.   (line  12)
-* LFLAGS:                                Yacc and Lex.        (line  65)
+* LFLAGS:                                Yacc and Lex.        (line  66)
+* lib_LIBRARIES:                         A Library.           (line   6)
+* lib_LTLIBRARIES:                       Libtool Libraries.   (line   6)
 * libexec_PROGRAMS:                      Program Sources.     (line   6)
 * libexec_SCRIPTS:                       Scripts.             (line  18)
 * LIBOBJS:                               Optional.            (line  75)
 * LIBOBJS <1>:                           LTLIBOBJS.           (line   6)
 * LIBOBJS <2>:                           LIBOBJS.             (line   6)
-* LIBRARIES:                             Uniform.             (line 101)
+* LIBRARIES:                             Uniform.             (line 102)
 * LIBS:                                  Program Variables.   (line  12)
 * LIBTOOLFLAGS:                          Libtool Flags.       (line   6)
-* lib_LIBRARIES:                         A Library.           (line   6)
-* lib_LTLIBRARIES:                       Libtool Libraries.   (line   6)
 * LINK:                                  Program Variables.   (line  64)
 * LINK <1>:                              How the Linker is Chosen.
                                                               (line  17)
-* LISP:                                  Uniform.             (line 101)
-* lispdir:                               Public Macros.       (line  60)
+* LISP:                                  Uniform.             (line 102)
+* lisp_DATA:                             Data.                (line   9)
 * lisp_LISP:                             Emacs Lisp.          (line   6)
+* lispdir:                               Public Macros.       (line  60)
 * localstate_DATA:                       Data.                (line   9)
 * LOG_COMPILE:                           Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * LOG_COMPILER:                          Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * LOG_DRIVER:                            Declaring Custom Test Drivers.
                                                               (line   6)
 * LOG_DRIVER_FLAGS:                      Declaring Custom Test Drivers.
                                                               (line   6)
 * LOG_FLAGS:                             Parallel Test Harness.
-                                                              (line  51)
+                                                              (line  54)
 * LTALLOCA:                              LTLIBOBJS.           (line   6)
 * LTALLOCA <1>:                          LIBOBJS.             (line   6)
 * LTLIBOBJS:                             LTLIBOBJS.           (line   6)
 * LTLIBOBJS <1>:                         LIBOBJS.             (line   6)
-* LTLIBRARIES:                           Uniform.             (line 101)
+* LTLIBRARIES:                           Uniform.             (line 102)
 * LZIP_OPT:                              The Types of Distributions.
-                                                              (line  23)
+                                                              (line  24)
 * MAINTAINERCLEANFILES:                  Clean.               (line  13)
 * MAKE:                                  Subdirectories.      (line  29)
-* MAKEINFO:                              Texinfo.             (line  99)
-* MAKEINFOFLAGS:                         Texinfo.             (line 109)
-* MAKEINFOHTML:                          Texinfo.             (line 105)
-* MANS:                                  Uniform.             (line 101)
+* MAKEINFO:                              Texinfo.             (line 121)
+* MAKEINFOFLAGS:                         Texinfo.             (line 131)
+* MAKEINFOHTML:                          Texinfo.             (line 127)
 * man_MANS:                              Man Pages.           (line   6)
+* MANS:                                  Uniform.             (line 102)
 * maude_AR:                              Program and Library Variables.
                                                               (line  76)
 * maude_CCASFLAGS:                       Program and Library Variables.
-                                                              (line 183)
+                                                              (line 188)
 * maude_CFLAGS:                          Program and Library Variables.
-                                                              (line 184)
+                                                              (line 189)
 * maude_CPPFLAGS:                        Program and Library Variables.
-                                                              (line 185)
+                                                              (line 190)
 * maude_CXXFLAGS:                        Program and Library Variables.
-                                                              (line 186)
+                                                              (line 191)
 * maude_DEPENDENCIES:                    Linking.             (line  41)
 * maude_DEPENDENCIES <1>:                Program and Library Variables.
-                                                              (line 128)
+                                                              (line 133)
 * maude_FFLAGS:                          Program and Library Variables.
-                                                              (line 187)
+                                                              (line 192)
 * maude_GCJFLAGS:                        Program and Library Variables.
-                                                              (line 188)
+                                                              (line 193)
 * maude_LDADD:                           Linking.             (line  17)
 * maude_LDADD <1>:                       Program and Library Variables.
-                                                              (line  94)
+                                                              (line  99)
 * maude_LDFLAGS:                         Linking.             (line  37)
 * maude_LDFLAGS <1>:                     Program and Library Variables.
-                                                              (line 114)
+                                                              (line 119)
 * maude_LFLAGS:                          Program and Library Variables.
-                                                              (line 189)
+                                                              (line 194)
 * maude_LIBADD:                          A Library.           (line  26)
 * maude_LIBADD <1>:                      Program and Library Variables.
-                                                              (line  86)
+                                                              (line  91)
 * maude_LIBTOOLFLAGS:                    Libtool Flags.       (line   6)
 * maude_LIBTOOLFLAGS <1>:                Program and Library Variables.
-                                                              (line 121)
+                                                              (line 126)
 * maude_LINK:                            Program and Library Variables.
-                                                              (line 164)
+                                                              (line 169)
 * maude_OBJCFLAGS:                       Program and Library Variables.
-                                                              (line 190)
+                                                              (line 195)
 * maude_OBJCXXFLAGS:                     Program and Library Variables.
-                                                              (line 191)
+                                                              (line 196)
+* maude_RANLIB:                          Program and Library Variables.
+                                                              (line  86)
 * maude_RFLAGS:                          Program and Library Variables.
-                                                              (line 192)
+                                                              (line 197)
 * maude_SHORTNAME:                       Program and Library Variables.
-                                                              (line 223)
+                                                              (line 228)
 * maude_SOURCES:                         Program and Library Variables.
                                                               (line  18)
 * maude_UPCFLAGS:                        Program and Library Variables.
-                                                              (line 193)
+                                                              (line 198)
 * maude_YFLAGS:                          Program and Library Variables.
-                                                              (line 194)
-* MISSING:                               Public Macros.       (line 110)
+                                                              (line 199)
+* MISSING:                               Public Macros.       (line 111)
 * MKDIR_P:                               Obsolete Macros.     (line  14)
 * mkdir_p:                               Obsolete Macros.     (line  14)
 * MOSTLYCLEANFILES:                      Clean.               (line  13)
@@ -5245,7 +5434,7 @@
 * nodist_:                               Alternative.         (line  28)
 * nodist_ <1>:                           Fine-grained Distribution Control.
                                                               (line   6)
-* noinst_:                               Uniform.             (line  90)
+* noinst_:                               Uniform.             (line  91)
 * noinst_HEADERS:                        Headers.             (line   6)
 * noinst_HEADERS <1>:                    Headers.             (line  23)
 * noinst_LIBRARIES:                      A Library.           (line   6)
@@ -5274,45 +5463,45 @@
 * oldinclude_HEADERS:                    Headers.             (line   6)
 * PACKAGE:                               Basics of Distribution.
                                                               (line   6)
-* pkgdatadir:                            Uniform.             (line  19)
 * pkgdata_DATA:                          Data.                (line   9)
 * pkgdata_SCRIPTS:                       Scripts.             (line  18)
-* pkgincludedir:                         Uniform.             (line  19)
+* pkgdatadir:                            Uniform.             (line  19)
 * pkginclude_HEADERS:                    Headers.             (line   6)
+* pkgincludedir:                         Uniform.             (line  19)
+* pkglib_LIBRARIES:                      A Library.           (line   6)
+* pkglib_LTLIBRARIES:                    Libtool Libraries.   (line   6)
 * pkglibdir:                             Uniform.             (line  19)
-* pkglibexecdir:                         Uniform.             (line  19)
 * pkglibexec_PROGRAMS:                   Program Sources.     (line   6)
 * pkglibexec_SCRIPTS:                    Scripts.             (line  18)
-* pkglib_LIBRARIES:                      A Library.           (line   6)
-* pkglib_LTLIBRARIES:                    Libtool Libraries.   (line   6)
-* pkgpyexecdir:                          Python.              (line 109)
-* pkgpythondir:                          Python.              (line  95)
+* pkglibexecdir:                         Uniform.             (line  19)
+* pkgpyexecdir:                          Python.              (line 117)
+* pkgpythondir:                          Python.              (line 103)
 * PROGRAMS:                              Uniform.             (line  17)
-* PROGRAMS <1>:                          Uniform.             (line 101)
-* pyexecdir:                             Python.              (line 100)
-* PYTHON:                                Uniform.             (line 101)
+* PROGRAMS <1>:                          Uniform.             (line 102)
+* pyexecdir:                             Python.              (line 108)
+* PYTHON:                                Uniform.             (line 102)
 * PYTHON <1>:                            Python.              (line  56)
-* pythondir:                             Python.              (line  91)
 * PYTHON_EXEC_PREFIX:                    Python.              (line  73)
 * PYTHON_PLATFORM:                       Python.              (line  86)
 * PYTHON_PREFIX:                         Python.              (line  72)
 * PYTHON_VERSION:                        Python.              (line  68)
+* pythondir:                             Python.              (line  91)
 * RECHECK_LOGS:                          Parallel Test Harness.
-                                                              (line 127)
+                                                              (line 130)
 * RFLAGS:                                Fortran 77 Support.  (line  25)
 * RUNTEST:                               DejaGnu Tests.       (line  19)
 * RUNTESTDEFAULTFLAGS:                   DejaGnu Tests.       (line  14)
 * RUNTESTFLAGS:                          DejaGnu Tests.       (line  24)
 * sbin_PROGRAMS:                         Program Sources.     (line   6)
 * sbin_SCRIPTS:                          Scripts.             (line  18)
-* SCRIPTS:                               Uniform.             (line 101)
+* SCRIPTS:                               Uniform.             (line 102)
 * SCRIPTS <1>:                           Scripts.             (line   9)
 * sharedstate_DATA:                      Data.                (line   9)
 * SOURCES:                               Program Sources.     (line  33)
 * SOURCES <1>:                           Default _SOURCES.    (line   6)
 * SUBDIRS:                               Subdirectories.      (line   8)
 * SUBDIRS <1>:                           Basics of Distribution.
-                                                              (line  73)
+                                                              (line  86)
 * SUFFIXES:                              Suffixes.            (line   6)
 * sys.exec_prefix Python variable:       Python.              (line  74)
 * sys.platform Python variable:          Python.              (line  87)
@@ -5322,28 +5511,30 @@
 * TAGS_DEPENDENCIES:                     Tags.                (line  37)
 * TAR:                                   Basics of Distribution.
                                                               (line  16)
+* TAR_OPTIONS:                           Basics of Distribution.
+                                                              (line  20)
 * target_triplet:                        Optional.            (line  14)
+* TEST_EXTENSIONS:                       Parallel Test Harness.
+                                                              (line  37)
+* TEST_LOGS:                             Parallel Test Harness.
+                                                              (line  37)
+* TEST_SUITE_LOG:                        Parallel Test Harness.
+                                                              (line  21)
 * TESTS:                                 Scripts-based Testsuites.
                                                               (line 104)
 * TESTS <1>:                             Parallel Test Harness.
                                                               (line  12)
 * TESTS_ENVIRONMENT:                     Testsuite Environment Overrides.
                                                               (line   6)
-* TEST_EXTENSIONS:                       Parallel Test Harness.
-                                                              (line  34)
-* TEST_LOGS:                             Parallel Test Harness.
-                                                              (line  34)
-* TEST_SUITE_LOG:                        Parallel Test Harness.
-                                                              (line  12)
-* TEXI2DVI:                              Texinfo.             (line 132)
-* TEXI2PDF:                              Texinfo.             (line 137)
-* TEXINFOS:                              Uniform.             (line 101)
-* TEXINFOS <1>:                          Texinfo.             (line  65)
-* TEXINFO_TEX:                           Texinfo.             (line 145)
+* TEXI2DVI:                              Texinfo.             (line 156)
+* TEXI2PDF:                              Texinfo.             (line 161)
+* TEXINFO_TEX:                           Texinfo.             (line 169)
+* TEXINFOS:                              Uniform.             (line 102)
+* TEXINFOS <1>:                          Texinfo.             (line  87)
 * top_distdir:                           The dist Hook.       (line  34)
 * top_distdir <1>:                       Third-Party Makefiles.
                                                               (line  25)
-* UPC:                                   Public Macros.       (line 104)
+* UPC:                                   Public Macros.       (line 105)
 * UPC <1>:                               Unified Parallel C Support.
                                                               (line  15)
 * UPCCOMPILE:                            Unified Parallel C Support.
@@ -5355,26 +5546,26 @@
 * UPCLINK <1>:                           How the Linker is Chosen.
                                                               (line  16)
 * V:                                     Automake Silent Rules.
-                                                              (line  88)
-* VALAC:                                 Vala Support.        (line  37)
-* VALAFLAGS:                             Vala Support.        (line  41)
+                                                              (line  89)
+* VALAC:                                 Vala Support.        (line  41)
+* VALAFLAGS:                             Vala Support.        (line  45)
 * VERBOSE:                               Parallel Test Harness.
-                                                              (line  26)
+                                                              (line  29)
 * VERSION:                               Basics of Distribution.
                                                               (line   6)
 * WARNINGS:                              automake Invocation. (line 187)
-* WARNINGS <1>:                          aclocal Options.     (line  95)
-* WITH_DMALLOC:                          Public Macros.       (line 122)
+* WARNINGS <1>:                          aclocal Options.     (line 108)
+* WITH_DMALLOC:                          Public Macros.       (line 123)
 * XFAIL_TESTS:                           Scripts-based Testsuites.
                                                               (line  32)
 * XZ_OPT:                                The Types of Distributions.
-                                                              (line  30)
-* YACC:                                  Optional.            (line 129)
-* YFLAGS:                                Yacc and Lex.        (line  37)
+                                                              (line  31)
+* YACC:                                  Optional.            (line 130)
+* YFLAGS:                                Yacc and Lex.        (line  38)
 * ZSTD_CLEVEL:                           The Types of Distributions.
-                                                              (line  41)
+                                                              (line  42)
 * ZSTD_OPT:                              The Types of Distributions.
-                                                              (line  41)
+                                                              (line  42)
 
 &#x1f;
 File: automake.info,  Node: General Index,  Prev: Variable Index,  Up: Indices
@@ -5385,28 +5576,46 @@
 &#x0;&#x8;index&#x0;&#x8;
 * Menu:
 
-* ## (special Automake comment):         General Operation.   (line  68)
-* #serial syntax:                        Serials.             (line   6)
-* $(LIBOBJS) and empty libraries:        LIBOBJS.             (line  72)
-* +=:                                    General Operation.   (line  24)
+* _DATA primary, defined:                Data.                (line   6)
+* _DEPENDENCIES, defined:                Linking.             (line  41)
+* _HEADERS primary, defined:             Headers.             (line   6)
+* _JAVA primary, defined:                Java.                (line   6)
+* _LDFLAGS, defined:                     Linking.             (line  37)
+* _LDFLAGS, libtool:                     Libtool Flags.       (line   6)
+* _LIBADD, libtool:                      Libtool Flags.       (line   6)
+* _LIBRARIES primary, defined:           A Library.           (line   6)
+* _LIBTOOLFLAGS, libtool:                Libtool Flags.       (line   6)
+* _LISP primary, defined:                Emacs Lisp.          (line   6)
+* _LTLIBRARIES primary, defined:         Libtool Libraries.   (line   6)
+* _MANS primary, defined:                Man Pages.           (line   6)
+* _PROGRAMS primary variable:            Uniform.             (line  11)
+* _PYTHON primary, defined:              Python.              (line   6)
+* _SCRIPTS primary, defined:             Scripts.             (line   6)
+* _SOURCES and header files:             Program Sources.     (line  39)
+* _SOURCES primary, defined:             Program Sources.     (line  32)
+* _SOURCES, default:                     Default _SOURCES.    (line   6)
+* _SOURCES, empty:                       Default _SOURCES.    (line  44)
+* _TEXINFOS primary, defined:            Texinfo.             (line   6)
+* --aclocal-path:                        aclocal Options.     (line  18)
+* --aclocal-path <1>:                    Macro Search Path.   (line 113)
 * --add-missing:                         automake Invocation. (line  41)
 * --always-make GNU Make option:         Rebuilding.          (line  77)
 * --automake-acdir:                      aclocal Options.     (line   9)
 * --build=BUILD:                         Cross-Compilation.   (line  14)
 * --copy:                                automake Invocation. (line  75)
-* --diff:                                aclocal Options.     (line  22)
+* --diff:                                aclocal Options.     (line  35)
 * --disable-dependency-tracking:         Dependency Tracking. (line  33)
-* --disable-maintainer-mode:             Optional.            (line 180)
+* --disable-maintainer-mode:             Optional.            (line 181)
 * --disable-silent-rules:                Automake Silent Rules.
                                                               (line  85)
-* --dry-run:                             aclocal Options.     (line  27)
+* --dry-run:                             aclocal Options.     (line  40)
 * --enable-debug, example:               Usage of Conditionals.
-                                                              (line  21)
+                                                              (line  30)
 * --enable-dependency-tracking:          Dependency Tracking. (line  43)
-* --enable-maintainer-mode:              Optional.            (line 180)
+* --enable-maintainer-mode:              Optional.            (line 181)
 * --enable-silent-rules:                 Automake Silent Rules.
                                                               (line  85)
-* --force:                               aclocal Options.     (line  49)
+* --force:                               aclocal Options.     (line  62)
 * --force-missing:                       automake Invocation. (line  80)
 * --foreign:                             Strictness.          (line  51)
 * --foreign <1>:                         automake Invocation. (line  86)
@@ -5415,61 +5624,55 @@
 * --gnu:                                 Strictness.          (line  18)
 * --gnu <1>:                             automake Invocation. (line  94)
 * --help:                                automake Invocation. (line  98)
-* --help <1>:                            aclocal Options.     (line  31)
+* --help <1>:                            aclocal Options.     (line  44)
 * --help check:                          List of Automake options.
-                                                              (line 144)
+                                                              (line 149)
 * --help=recursive:                      Nested Packages.     (line  30)
 * --host=HOST:                           Cross-Compilation.   (line  16)
 * --include-deps:                        automake Invocation. (line 106)
-* --install:                             aclocal Options.     (line  38)
+* --install:                             aclocal Options.     (line  51)
 * --libdir:                              automake Invocation. (line  61)
 * --no-force:                            automake Invocation. (line 111)
-* --output:                              aclocal Options.     (line  59)
+* --output:                              aclocal Options.     (line  71)
 * --output-dir:                          automake Invocation. (line 118)
 * --prefix:                              Standard Directory Variables.
                                                               (line  33)
-* --print-ac-dir:                        aclocal Options.     (line  62)
+* --print-ac-dir:                        aclocal Options.     (line  74)
 * --print-libdir:                        automake Invocation. (line  69)
 * --program-prefix=PREFIX:               Renaming.            (line  16)
 * --program-suffix=SUFFIX:               Renaming.            (line  18)
 * --program-transform-name=PROGRAM:      Renaming.            (line  20)
-* --system-acdir:                        aclocal Options.     (line  17)
+* --system-acdir:                        aclocal Options.     (line  30)
 * --target=TARGET:                       Cross-Compilation.   (line  55)
 * --verbose:                             automake Invocation. (line 125)
-* --verbose <1>:                         aclocal Options.     (line  73)
+* --verbose <1>:                         aclocal Options.     (line  84)
 * --version:                             automake Invocation. (line 129)
-* --version <1>:                         aclocal Options.     (line  76)
+* --version <1>:                         aclocal Options.     (line  87)
 * --version check:                       List of Automake options.
-                                                              (line 144)
+                                                              (line 149)
 * --warnings:                            automake Invocation. (line 133)
-* --warnings <1>:                        aclocal Options.     (line  80)
-* --with-dmalloc:                        Public Macros.       (line 122)
-* --with-python-sys-prefix:              Python.              (line  74)
+* --warnings <1>:                        aclocal Options.     (line  91)
+* --with-dmalloc:                        Public Macros.       (line 123)
 * --with-python_exec_prefix:             Python.              (line  74)
 * --with-python_prefix:                  Python.              (line  74)
+* --with-python-sys-prefix:              Python.              (line  74)
 * -a:                                    automake Invocation. (line  41)
 * -c:                                    automake Invocation. (line  74)
 * -f:                                    automake Invocation. (line  79)
 * -hook targets:                         Extending.           (line  66)
 * -i:                                    automake Invocation. (line 102)
-* -I:                                    aclocal Options.     (line  34)
+* -I:                                    aclocal Options.     (line  47)
 * -l and LDADD:                          Linking.             (line  70)
 * -local targets:                        Extending.           (line  37)
 * -module, libtool:                      Libtool Modules.     (line   6)
 * -o:                                    automake Invocation. (line 118)
 * -v:                                    automake Invocation. (line 125)
 * -W:                                    automake Invocation. (line 133)
-* -W <1>:                                aclocal Options.     (line  80)
+* -W <1>:                                aclocal Options.     (line  91)
 * -Wall:                                 amhello's configure.ac Setup Explained.
                                                               (line  38)
 * -Werror:                               amhello's configure.ac Setup Explained.
                                                               (line  38)
-* .la suffix, defined:                   Libtool Concept.     (line   6)
-* .log files:                            Parallel Test Harness.
-                                                              (line  12)
-* .pyc, .pyo files:                      Python.              (line  15)
-* .trs files:                            Parallel Test Harness.
-                                                              (line  12)
 * :copy-in-global-log::                  Log files generation and test results recording.
                                                               (line  44)
 * :recheck::                             Log files generation and test results recording.
@@ -5478,42 +5681,34 @@
                                                               (line  54)
 * :test-result::                         Log files generation and test results recording.
                                                               (line  24)
-* _DATA primary, defined:                Data.                (line   6)
-* _DEPENDENCIES, defined:                Linking.             (line  41)
-* _HEADERS primary, defined:             Headers.             (line   6)
-* _JAVA primary, defined:                Java.                (line   6)
-* _LDFLAGS, defined:                     Linking.             (line  37)
-* _LDFLAGS, libtool:                     Libtool Flags.       (line   6)
-* _LIBADD, libtool:                      Libtool Flags.       (line   6)
-* _LIBRARIES primary, defined:           A Library.           (line   6)
-* _LIBTOOLFLAGS, libtool:                Libtool Flags.       (line   6)
-* _LISP primary, defined:                Emacs Lisp.          (line   6)
-* _LTLIBRARIES primary, defined:         Libtool Libraries.   (line   6)
-* _MANS primary, defined:                Man Pages.           (line   6)
-* _PROGRAMS primary variable:            Uniform.             (line  11)
-* _PYTHON primary, defined:              Python.              (line   6)
-* _SCRIPTS primary, defined:             Scripts.             (line   6)
-* _SOURCES and header files:             Program Sources.     (line  39)
-* _SOURCES primary, defined:             Program Sources.     (line  32)
-* _SOURCES, default:                     Default _SOURCES.    (line   6)
-* _SOURCES, empty:                       Default _SOURCES.    (line  44)
-* _TEXINFOS primary, defined:            Texinfo.             (line   6)
+* .la suffix, defined:                   Libtool Concept.     (line   6)
+* .log files:                            Parallel Test Harness.
+                                                              (line  12)
+* .pyc, .pyo files:                      Python.              (line  15)
+* .texi.in file, read:                   Texinfo.             (line  38)
+* .trs files:                            Parallel Test Harness.
+                                                              (line  12)
+* @setfilename Texinfo directive:        Texinfo.             (line  31)
+* ## (special Automake comment):         General Operation.   (line  69)
+* #serial syntax:                        Serials.             (line   6)
+* +=:                                    General Operation.   (line  24)
+* $(LIBOBJS) and empty libraries:        LIBOBJS.             (line  72)
+* AC_CONFIG_FILES, conditional:          Usage of Conditionals.
+                                                              (line  88)
+* AC_SUBST and SUBDIRS:                  Subdirectories with AC_SUBST.
+                                                              (line   6)
 * acinclude.m4, defined:                 Complete.            (line  23)
 * aclocal and serial numbers:            Serials.             (line   6)
 * aclocal program, introduction:         Complete.            (line  23)
 * aclocal search path:                   Macro Search Path.   (line   6)
-* aclocal’s scheduled death:             Future of aclocal.   (line   6)
+* ACLOCAL_PATH:                          Macro Search Path.   (line 113)
 * aclocal, extending:                    Extending aclocal.   (line   6)
 * aclocal, Invocation:                   aclocal Invocation.  (line   6)
 * aclocal, Invoking:                     aclocal Invocation.  (line   6)
 * aclocal, Options:                      aclocal Options.     (line   6)
 * aclocal, using:                        configure.           (line   6)
 * aclocal.m4, preexisting:               Complete.            (line  23)
-* ACLOCAL_PATH:                          Macro Search Path.   (line 116)
-* AC_CONFIG_FILES, conditional:          Usage of Conditionals.
-                                                              (line  79)
-* AC_SUBST and SUBDIRS:                  Subdirectories with AC_SUBST.
-                                                              (line   6)
+* aclocal's scheduled death:             Future of aclocal.   (line   6)
 * Adding new SUFFIXES:                   Suffixes.            (line   6)
 * all:                                   Standard Targets.    (line  16)
 * all <1>:                               Extending.           (line  41)
@@ -5521,9 +5716,6 @@
 * ALLOCA, and Libtool:                   LTLIBOBJS.           (line   6)
 * ALLOCA, example:                       LIBOBJS.             (line   6)
 * ALLOCA, special handling:              LIBOBJS.             (line   6)
-* amhello-1.0.tar.gz, creation:          Hello World.         (line   6)
-* amhello-1.0.tar.gz, location:          Use Cases.           (line   6)
-* amhello-1.0.tar.gz, use cases:         Use Cases.           (line   6)
 * AM_CCASFLAGS and CCASFLAGS:            Flag Variables Ordering.
                                                               (line  20)
 * AM_CFLAGS and CFLAGS:                  Flag Variables Ordering.
@@ -5558,12 +5750,15 @@
                                                               (line  20)
 * AM_YFLAGS and YFLAGS:                  Flag Variables Ordering.
                                                               (line  20)
+* amhello-1.0.tar.gz, creation:          Hello World.         (line   6)
+* amhello-1.0.tar.gz, location:          Use Cases.           (line   6)
+* amhello-1.0.tar.gz, use cases:         Use Cases.           (line   6)
 * Append operator:                       General Operation.   (line  24)
 * ar-lib:                                Auxiliary Programs.  (line  16)
 * ARG_MAX:                               Length Limitations.  (line   6)
 * autogen.sh and autoreconf:             Error required file ltmain.sh not found.
                                                               (line   6)
-* autom4te:                              aclocal Invocation.  (line  44)
+* autom4te:                              aclocal Invocation.  (line  45)
 * Automake constraints:                  Introduction.        (line  21)
 * automake options:                      automake Invocation. (line  37)
 * Automake parser, limitations of:       General Operation.   (line  33)
@@ -5573,7 +5768,7 @@
                                                               (line  88)
 * automake, invocation:                  automake Invocation. (line   6)
 * automake, invoking:                    automake Invocation. (line   6)
-* Automake, recursive operation:         General Operation.   (line  58)
+* Automake, recursive operation:         General Operation.   (line  59)
 * Automatic dependency tracking:         Dependencies.        (line  11)
 * Automatic linker selection:            How the Linker is Chosen.
                                                               (line   6)
@@ -5594,8 +5789,9 @@
 * Bugs, reporting:                       Reporting Bugs.      (line   6)
 * build tree and source tree:            VPATH Builds.        (line   6)
 * BUILT_SOURCES, defined:                Sources.             (line  27)
+* built-in suffix and pattern rules, disabled: Suffixes.      (line  44)
 * bzip2:                                 The Types of Distributions.
-                                                              (line  17)
+                                                              (line  18)
 * C++ support:                           C++ Support.         (line   6)
 * canonicalizing Automake variables:     Canonicalization.    (line   6)
 * CCASFLAGS and AM_CCASFLAGS:            Flag Variables Ordering.
@@ -5607,11 +5803,11 @@
 * check:                                 Standard Targets.    (line  31)
 * check <1>:                             Tests.               (line   6)
 * check <2>:                             Extending.           (line  41)
+* check_ primary prefix, definition:     Uniform.             (line  96)
+* check_PROGRAMS example:                Default _SOURCES.    (line  28)
 * check-local:                           Extending.           (line  41)
 * check-news:                            List of Automake options.
                                                               (line  15)
-* check_ primary prefix, definition:     Uniform.             (line  95)
-* check_PROGRAMS example:                Default _SOURCES.    (line  28)
 * clean:                                 Standard Targets.    (line  27)
 * clean <1>:                             Extending.           (line  41)
 * clean-local:                           Clean.               (line  15)
@@ -5619,7 +5815,7 @@
 * Colorized testsuite output:            Scripts-based Testsuites.
                                                               (line  85)
 * command line length limit:             Length Limitations.  (line   6)
-* Comment, special to Automake:          General Operation.   (line  68)
+* Comment, special to Automake:          General Operation.   (line  69)
 * Compilation of Java to bytecode:       Java.                (line   6)
 * Compilation of Java to native code:    Java Support with gcj.
                                                               (line   6)
@@ -5628,9 +5824,10 @@
                                                               (line  20)
 * Complete example:                      Complete.            (line   6)
 * compress:                              The Types of Distributions.
-                                                              (line  57)
+                                                              (line  58)
 * Conditional example, --enable-debug:   Usage of Conditionals.
-                                                              (line  21)
+                                                              (line  30)
+* Conditional for dependency tracking:   Dependencies.        (line  37)
 * conditional libtool libraries:         Conditional Libtool Libraries.
                                                               (line   6)
 * Conditional programs:                  Conditional Programs.
@@ -5648,7 +5845,7 @@
                                                               (line   6)
 * Configuration, basics:                 Basic Installation.  (line   6)
 * Configure substitutions in TESTS:      Parallel Test Harness.
-                                                              (line  46)
+                                                              (line  49)
 * configure.ac, Hello World:             amhello's configure.ac Setup Explained.
                                                               (line   6)
 * configure.ac, scanning:                configure.           (line   6)
@@ -5662,19 +5859,16 @@
                                                               (line  20)
 * cross-compilation:                     Cross-Compilation.   (line   6)
 * cross-compilation example:             Cross-Compilation.   (line  25)
-* CVS and generated files:               CVS.                 (line  50)
-* CVS and third-party files:             CVS.                 (line 167)
-* CVS and timestamps:                    CVS.                 (line  29)
 * CXXFLAGS and AM_CXXFLAGS:              Flag Variables Ordering.
                                                               (line  20)
 * DATA primary, defined:                 Data.                (line   6)
 * debug build, example:                  VPATH Builds.        (line  48)
 * debugging rules:                       Debugging Make Rules.
                                                               (line   6)
-* default source, Libtool modules example: Default _SOURCES.  (line  38)
-* default verbosity for silent rules:    Automake Silent Rules.
-                                                              (line  92)
 * default _SOURCES:                      Default _SOURCES.    (line   6)
+* default source, libtool modules example: Default _SOURCES.  (line  38)
+* default verbosity for silent rules:    Automake Silent Rules.
+                                                              (line 101)
 * definitions, conflicts:                Extending.           (line  14)
 * dejagnu:                               DejaGnu Tests.       (line  19)
 * dejagnu <1>:                           List of Automake options.
@@ -5685,20 +5879,24 @@
                                                               (line   6)
 * Dependency tracking:                   Dependency Tracking. (line   6)
 * Dependency tracking <1>:               Dependencies.        (line  11)
-* Dependency tracking, disabling:        Dependencies.        (line  36)
+* Dependency tracking, disabling:        Dependencies.        (line  34)
 * directory variables:                   Standard Directory Variables.
                                                               (line   6)
-* dirlist:                               Macro Search Path.   (line  52)
-* Disabling dependency tracking:         Dependencies.        (line  37)
+* dirlist:                               Macro Search Path.   (line  51)
+* Disabling dependency tracking:         Dependencies.        (line  34)
 * Disabling hard errors:                 Scripts-based Testsuites.
                                                               (line  32)
 * dist:                                  Standard Targets.    (line  35)
 * dist <1>:                              Basics of Distribution.
                                                               (line   6)
+* dist_ and nobase_:                     Alternative.         (line  28)
+* dist_ and notrans_:                    Man Pages.           (line  63)
+* DIST_SUBDIRS, explained:               SUBDIRS vs DIST_SUBDIRS.
+                                                              (line   6)
 * dist-all:                              The Types of Distributions.
-                                                              (line  62)
+                                                              (line  63)
 * dist-bzip2:                            The Types of Distributions.
-                                                              (line  17)
+                                                              (line  18)
 * dist-bzip2 <1>:                        List of Automake options.
                                                               (line  23)
 * dist-bzip2 <2>:                        List of Automake options.
@@ -5708,37 +5906,38 @@
 * dist-hook:                             The dist Hook.       (line   6)
 * dist-hook <1>:                         Extending.           (line  66)
 * dist-lzip:                             The Types of Distributions.
-                                                              (line  23)
+                                                              (line  24)
 * dist-lzip <1>:                         List of Automake options.
                                                               (line  26)
 * dist-lzip <2>:                         List of Automake options.
                                                               (line  26)
+* dist-packages Python directory:        Python.              (line  92)
 * dist-shar:                             The Types of Distributions.
-                                                              (line  51)
+                                                              (line  52)
 * dist-shar <1>:                         List of Automake options.
                                                               (line  40)
 * dist-shar <2>:                         List of Automake options.
                                                               (line  38)
 * dist-tarZ:                             The Types of Distributions.
-                                                              (line  57)
+                                                              (line  58)
 * dist-tarZ <1>:                         List of Automake options.
                                                               (line  45)
 * dist-tarZ <2>:                         List of Automake options.
                                                               (line  43)
 * dist-xz:                               The Types of Distributions.
-                                                              (line  30)
+                                                              (line  31)
 * dist-xz <1>:                           List of Automake options.
                                                               (line  29)
 * dist-xz <2>:                           List of Automake options.
                                                               (line  29)
 * dist-zip:                              The Types of Distributions.
-                                                              (line  37)
+                                                              (line  38)
 * dist-zip <1>:                          List of Automake options.
                                                               (line  32)
 * dist-zip <2>:                          List of Automake options.
                                                               (line  32)
 * dist-zstd:                             The Types of Distributions.
-                                                              (line  41)
+                                                              (line  42)
 * dist-zstd <1>:                         List of Automake options.
                                                               (line  35)
 * dist-zstd <2>:                         List of Automake options.
@@ -5749,57 +5948,48 @@
 * distcheck better than dist:            Preparing Distributions.
                                                               (line  10)
 * distcheck example:                     Creating amhello.    (line 100)
-* distcheck-hook:                        Checking the Distribution.
-                                                              (line  77)
+* distcheck-hook:                        distcheck-hook.      (line   6)
 * distclean:                             Standard Targets.    (line  29)
-* distclean <1>:                         Extending.           (line  41)
-* distclean <2>:                         Errors with distclean.
-                                                              (line   6)
-* distclean, diagnostic:                 Errors with distclean.
+* distclean <1>:                         Errors with distclean.
                                                               (line   6)
+* distclean <2>:                         Extending.           (line  41)
 * distclean-local:                       Clean.               (line  15)
 * distclean-local <1>:                   Extending.           (line  41)
-* distcleancheck:                        Checking the Distribution.
-                                                              (line  92)
+* distclean, diagnostic:                 Errors with distclean.
+                                                              (line   6)
+* distcleancheck:                        distcleancheck.      (line   6)
 * distdir:                               Third-Party Makefiles.
                                                               (line  25)
 * Distinction between errors and failures in testsuites: Generalities about Testing.
                                                               (line  48)
 * Distributions, preparation:            Preparing Distributions.
                                                               (line   6)
-* distuninstallcheck:                    Checking the Distribution.
-                                                              (line 128)
-* dist_ and nobase_:                     Alternative.         (line  28)
-* dist_ and notrans_:                    Man Pages.           (line  63)
-* DIST_SUBDIRS, explained:               SUBDIRS vs DIST_SUBDIRS.
-                                                              (line   6)
-* dmalloc, support for:                  Public Macros.       (line 122)
+* distuninstallcheck:                    distuninstallcheck.  (line   6)
+* dmalloc, support for:                  Public Macros.       (line 123)
 * do-nothing Automake targets:           Third-Party Makefiles.
                                                               (line  88)
-* dvi:                                   Texinfo.             (line  25)
-* dvi <1>:                               Checking the Distribution.
-                                                              (line  57)
+* dvi:                                   Texinfo.             (line  46)
+* dvi <1>:                               dvi and distcheck.   (line   6)
 * dvi <2>:                               Extending.           (line  41)
 * DVI output using Texinfo:              Texinfo.             (line   6)
 * dvi-local:                             Extending.           (line  41)
-* EDITION Texinfo flag:                  Texinfo.             (line  35)
+* EDITION Texinfo flag:                  Texinfo.             (line  56)
 * else:                                  Usage of Conditionals.
-                                                              (line  36)
+                                                              (line  45)
+* empty _SOURCES:                        Default _SOURCES.    (line  44)
 * empty Automake targets:                Third-Party Makefiles.
                                                               (line  88)
-* Empty libraries:                       A Library.           (line  48)
+* Empty libraries:                       A Library.           (line  47)
 * Empty libraries and $(LIBOBJS):        LIBOBJS.             (line  72)
-* empty _SOURCES:                        Default _SOURCES.    (line  44)
 * endif:                                 Usage of Conditionals.
-                                                              (line  36)
-* eps images:                            Checking the Distribution.
-                                                              (line  60)
+                                                              (line  45)
+* eps images, and distcheck:             dvi and distcheck.   (line  11)
 * Example conditional --enable-debug:    Usage of Conditionals.
-                                                              (line  21)
+                                                              (line  30)
 * Example conditional AC_CONFIG_FILES:   Usage of Conditionals.
-                                                              (line  79)
+                                                              (line  88)
 * Example Hello World:                   Hello World.         (line   6)
-* Example of recursive operation:        General Operation.   (line  58)
+* Example of recursive operation:        General Operation.   (line  59)
 * Example of shared libraries:           Libtool Libraries.   (line   6)
 * Example, EXTRA_PROGRAMS:               Uniform.             (line  36)
 * Example, false and true:               true.                (line   6)
@@ -5821,10 +6011,10 @@
 * Extension, executable:                 EXEEXT.              (line   6)
 * Extra files distributed with Automake: automake Invocation. (line  39)
 * EXTRA_, prepending:                    Uniform.             (line  29)
+* EXTRA_prog_SOURCES, defined:           Conditional Sources. (line  18)
 * EXTRA_PROGRAMS, defined:               Uniform.             (line  36)
 * EXTRA_PROGRAMS, defined <1>:           Conditional Programs.
                                                               (line  15)
-* EXTRA_prog_SOURCES, defined:           Conditional Sources. (line  18)
 * false Example:                         true.                (line   6)
 * FCFLAGS and AM_FCFLAGS:                Flag Variables Ordering.
                                                               (line  20)
@@ -5836,7 +6026,7 @@
 * filename-length-max=99:                List of Automake options.
                                                               (line  48)
 * Files distributed with Automake:       automake Invocation. (line  39)
-* First line of Makefile.am:             General Operation.   (line  74)
+* First line of Makefile.am:             General Operation.   (line  75)
 * Flag variables, ordering:              Flag Variables Ordering.
                                                               (line   6)
 * Flag Variables, Ordering:              Flag Variables Ordering.
@@ -5856,8 +6046,8 @@
 * Fortran 9x support:                    Fortran 9x Support.  (line   6)
 * GCJFLAGS and AM_GCJFLAGS:              Flag Variables Ordering.
                                                               (line  20)
-* generated files and CVS:               CVS.                 (line  50)
-* generated files, distributed:          CVS.                 (line   9)
+* generated files and version control:   Version Control.     (line  45)
+* generated files, distributed:          Version Control.     (line   9)
 * Gettext support:                       gettext.             (line   6)
 * git-dist:                              General Operation.   (line  12)
 * git-dist, non-standard example:        General Operation.   (line  12)
@@ -5873,6 +6063,7 @@
 * GNU Coding Standards:                  GNU Build System.    (line  29)
 * GNU Gettext support:                   gettext.             (line   6)
 * GNU Make extensions:                   General Operation.   (line  20)
+* GNU Make, required by Vala:            Vala Support.        (line   6)
 * GNU Makefile standards:                Introduction.        (line  12)
 * gnu strictness:                        Strictness.          (line  18)
 * GNUmakefile including Makefile:        Third-Party Makefiles.
@@ -5885,22 +6076,24 @@
 * HEADERS primary, defined:              Headers.             (line   6)
 * HEADERS, installation directories:     Headers.             (line   6)
 * Hello World example:                   Hello World.         (line   6)
+* help2man:                              Errors with distclean.
+                                                              (line  22)
 * help2man, and dist target:             List of Automake options.
                                                               (line  81)
 * hook targets:                          Extending.           (line  66)
 * HP-UX 10, lex problems:                Public Macros.       (line  94)
-* html:                                  Texinfo.             (line  25)
+* html:                                  Texinfo.             (line  46)
 * html <1>:                              Extending.           (line  41)
 * HTML output using Texinfo:             Texinfo.             (line   6)
 * html-local:                            Extending.           (line  41)
 * id:                                    Tags.                (line  45)
 * if:                                    Usage of Conditionals.
-                                                              (line  36)
+                                                              (line  45)
 * include:                               Basics of Distribution.
-                                                              (line  30)
+                                                              (line  43)
 * include <1>:                           Include.             (line   6)
 * include, distribution:                 Basics of Distribution.
-                                                              (line  30)
+                                                              (line  43)
 * Including Makefile fragment:           Include.             (line   6)
 * indentation in Makefile.am:            General Operation.   (line  33)
 * info:                                  List of Automake options.
@@ -5915,8 +6108,6 @@
 * install <2>:                           Extending.           (line  41)
 * Install hook:                          Extending Installation.
                                                               (line  15)
-* Install, two parts of:                 The Two Parts of Install.
-                                                              (line  14)
 * install-data:                          Two-Part Install.    (line  16)
 * install-data <1>:                      The Two Parts of Install.
                                                               (line  14)
@@ -5925,7 +6116,7 @@
 * install-data-local:                    Extending Installation.
                                                               (line   9)
 * install-data-local <1>:                Extending.           (line  41)
-* install-dvi:                           Texinfo.             (line  25)
+* install-dvi:                           Texinfo.             (line  46)
 * install-dvi <1>:                       Extending.           (line  41)
 * install-dvi-local:                     Extending.           (line  41)
 * install-exec:                          Two-Part Install.    (line  16)
@@ -5936,29 +6127,31 @@
 * install-exec-local:                    Extending Installation.
                                                               (line   9)
 * install-exec-local <1>:                Extending.           (line  41)
-* install-html:                          Texinfo.             (line  25)
+* install-html:                          Texinfo.             (line  46)
 * install-html <1>:                      Extending.           (line  41)
 * install-html-local:                    Extending.           (line  41)
-* install-info:                          Texinfo.             (line  85)
+* install-info:                          Texinfo.             (line 107)
 * install-info <1>:                      List of Automake options.
                                                               (line 108)
 * install-info <2>:                      Extending.           (line  41)
-* install-info target:                   Texinfo.             (line  85)
+* install-info target:                   Texinfo.             (line 107)
 * install-info-local:                    Extending.           (line  41)
 * install-man:                           Man Pages.           (line  32)
 * install-man <1>:                       List of Automake options.
                                                               (line 114)
 * install-man target:                    Man Pages.           (line  32)
-* install-pdf:                           Texinfo.             (line  25)
+* install-pdf:                           Texinfo.             (line  46)
 * install-pdf <1>:                       Extending.           (line  41)
 * install-pdf-local:                     Extending.           (line  41)
-* install-ps:                            Texinfo.             (line  25)
+* install-ps:                            Texinfo.             (line  46)
 * install-ps <1>:                        Extending.           (line  41)
 * install-ps-local:                      Extending.           (line  41)
 * install-sh:                            Auxiliary Programs.  (line  46)
 * install-strip:                         Standard Targets.    (line  21)
 * install-strip <1>:                     Install Rules for the User.
                                                               (line   7)
+* Install, two parts of:                 The Two Parts of Install.
+                                                              (line  14)
 * Installation directories, extending list: Uniform.          (line  56)
 * Installation support:                  Install.             (line   6)
 * Installation, basics:                  Basic Installation.  (line   6)
@@ -5986,26 +6179,30 @@
 * Java to native code, compilation:      Java Support with gcj.
                                                               (line   6)
 * lazy test execution:                   Parallel Test Harness.
-                                                              (line 127)
+                                                              (line 130)
 * LDADD and -l:                          Linking.             (line  70)
 * LDFLAGS and AM_LDFLAGS:                Flag Variables Ordering.
                                                               (line  20)
 * lex problems with HP-UX 10:            Public Macros.       (line  94)
-* lex, multiple lexers:                  Yacc and Lex.        (line  73)
+* lex, multiple lexers:                  Yacc and Lex.        (line  74)
 * LFLAGS and AM_LFLAGS:                  Flag Variables Ordering.
                                                               (line  20)
-* libltdl, introduction:                 Libtool Concept.     (line  29)
+* libltdl, introduction:                 Libtool Concept.     (line  28)
 * LIBOBJS, and Libtool:                  LTLIBOBJS.           (line   6)
 * LIBOBJS, example:                      LIBOBJS.             (line   6)
 * LIBOBJS, special handling:             LIBOBJS.             (line   6)
 * LIBRARIES primary, defined:            A Library.           (line   6)
 * libtool convenience libraries:         Libtool Convenience Libraries.
                                                               (line   6)
+* LIBTOOL is undefined:                  Libtool library used but LIBTOOL is undefined.
+                                                              (line   6)
 * libtool libraries, conditional:        Conditional Libtool Libraries.
                                                               (line   6)
+* Libtool library used but LIBTOOL is undefined: Libtool library used but LIBTOOL is undefined.
+                                                              (line   6)
 * libtool library, definition:           Libtool Concept.     (line   6)
 * libtool modules:                       Libtool Modules.     (line   6)
-* Libtool modules, default source example: Default _SOURCES.  (line  38)
+* libtool modules, default source example: Default _SOURCES.  (line  38)
 * libtool, introduction:                 Libtool Concept.     (line   6)
 * LIBTOOLFLAGS and AM_LIBTOOLFLAGS:      Flag Variables Ordering.
                                                               (line  20)
@@ -6017,7 +6214,7 @@
 * Linking Fortran 77 with C and C++:     Mixing Fortran 77 With C and C++.
                                                               (line   6)
 * Linking multiple yacc parsers:         Linking Multiple Yacc Parsers.
-                                                              (line   3)
+                                                              (line   6)
 * LISP primary, defined:                 Emacs Lisp.          (line   6)
 * LN_S example:                          Extending.           (line  86)
 * local targets:                         Extending.           (line  37)
@@ -6027,9 +6224,9 @@
 * ltmain.sh not found:                   Error required file ltmain.sh not found.
                                                               (line   6)
 * lzip:                                  The Types of Distributions.
-                                                              (line  23)
+                                                              (line  24)
 * m4_include, distribution:              Basics of Distribution.
-                                                              (line  30)
+                                                              (line  43)
 * Macro search path:                     Macro Search Path.   (line   6)
 * macro serial numbers:                  Serials.             (line   6)
 * Macros Automake recognizes:            Optional.            (line   6)
@@ -6042,24 +6239,24 @@
                                                               (line   6)
 * make distclean, diagnostic:            Errors with distclean.
                                                               (line   6)
-* make distcleancheck:                   Checking the Distribution.
-                                                              (line  92)
-* make distuninstallcheck:               Checking the Distribution.
-                                                              (line 128)
+* make distcleancheck:                   distcleancheck.      (line   6)
+* make distuninstallcheck:               distuninstallcheck.  (line   6)
 * make install support:                  Install.             (line   6)
 * make installcheck, testing --help and --version: List of Automake options.
-                                                              (line 144)
-* Make rules, overriding:                General Operation.   (line  46)
-* Make targets, overriding:              General Operation.   (line  46)
+                                                              (line 149)
+* Make rules, overriding:                General Operation.   (line  47)
+* Make targets, overriding:              General Operation.   (line  47)
 * Makefile fragment, including:          Include.             (line   6)
-* Makefile.am, first line:               General Operation.   (line  74)
+* Makefile.am, first line:               General Operation.   (line  75)
 * Makefile.am, Hello World:              amhello's Makefile.am Setup Explained.
                                                               (line   6)
 * Man page renaming, avoiding:           Man Pages.           (line  54)
+* man pages, generating and distributing: Errors with distclean.
+                                                              (line  22)
 * MANS primary, defined:                 Man Pages.           (line   6)
 * many outputs, rules with:              Multiple Outputs.    (line   6)
 * mdate-sh:                              Auxiliary Programs.  (line  50)
-* mdate-sh <1>:                          Texinfo.             (line  35)
+* mdate-sh <1>:                          Texinfo.             (line  56)
 * MinGW cross-compilation example:       Cross-Compilation.   (line  25)
 * missing program:                       Auxiliary Programs.  (line  54)
 * missing, purpose:                      maintainer-mode.     (line   9)
@@ -6077,9 +6274,9 @@
 * mostlyclean-local <1>:                 Extending.           (line  41)
 * multiple configurations, example:      VPATH Builds.        (line  48)
 * Multiple configure.ac files:           automake Invocation. (line   6)
-* Multiple lex lexers:                   Yacc and Lex.        (line  73)
+* Multiple lex lexers:                   Yacc and Lex.        (line  74)
 * multiple outputs, rules with:          Multiple Outputs.    (line   6)
-* Multiple yacc parsers:                 Yacc and Lex.        (line  73)
+* Multiple yacc parsers:                 Yacc and Lex.        (line  74)
 * Nested packages:                       Nested Packages.     (line   6)
 * Nesting packages:                      Subpackages.         (line   6)
 * no-define:                             Public Macros.       (line  54)
@@ -6098,10 +6295,10 @@
                                                               (line  92)
 * no-exeext:                             List of Automake options.
                                                               (line  95)
-* no-installinfo:                        Texinfo.             (line  85)
+* no-installinfo:                        Texinfo.             (line 107)
 * no-installinfo <1>:                    List of Automake options.
                                                               (line 105)
-* no-installinfo option:                 Texinfo.             (line  85)
+* no-installinfo option:                 Texinfo.             (line 107)
 * no-installman:                         Man Pages.           (line  32)
 * no-installman <1>:                     List of Automake options.
                                                               (line 111)
@@ -6114,7 +6311,7 @@
 * nobase_ prefix:                        Alternative.         (line  22)
 * nodist_ and nobase_:                   Alternative.         (line  28)
 * nodist_ and notrans_:                  Man Pages.           (line  63)
-* noinst_ primary prefix, definition:    Uniform.             (line  90)
+* noinst_ primary prefix, definition:    Uniform.             (line  91)
 * Non-GNU packages:                      Strictness.          (line   6)
 * Non-standard targets:                  General Operation.   (line  12)
 * nostdinc:                              List of Automake options.
@@ -6133,9 +6330,9 @@
 * obsolete macros:                       Obsolete Macros.     (line   6)
 * optimized build, example:              VPATH Builds.        (line  48)
 * Option, --warnings=CATEGORY:           List of Automake options.
-                                                              (line 228)
+                                                              (line 233)
 * Option, -WCATEGORY:                    List of Automake options.
-                                                              (line 228)
+                                                              (line 233)
 * Option, check-news:                    List of Automake options.
                                                               (line  15)
 * Option, dejagnu:                       List of Automake options.
@@ -6176,7 +6373,7 @@
                                                               (line  92)
 * Option, no-exeext:                     List of Automake options.
                                                               (line  95)
-* Option, no-installinfo:                Texinfo.             (line  85)
+* Option, no-installinfo:                Texinfo.             (line 107)
 * Option, no-installinfo <1>:            List of Automake options.
                                                               (line 105)
 * Option, no-installman:                 Man Pages.           (line  32)
@@ -6187,32 +6384,34 @@
 * Option, nostdinc:                      List of Automake options.
                                                               (line 117)
 * Option, parallel-tests:                List of Automake options.
-                                                              (line 129)
+                                                              (line 134)
+* Option, posix:                         List of Automake options.
+                                                              (line 125)
 * Option, readme-alpha:                  List of Automake options.
-                                                              (line 135)
+                                                              (line 140)
 * Option, serial-tests:                  List of Automake options.
-                                                              (line 125)
+                                                              (line 130)
 * Option, tar-pax:                       List of Automake options.
-                                                              (line 174)
+                                                              (line 179)
 * Option, tar-ustar:                     List of Automake options.
-                                                              (line 174)
+                                                              (line 179)
 * Option, tar-v7:                        List of Automake options.
-                                                              (line 174)
+                                                              (line 179)
 * Option, VERSION:                       List of Automake options.
-                                                              (line 223)
-* Option, warnings:                      List of Automake options.
                                                               (line 228)
+* Option, warnings:                      List of Automake options.
+                                                              (line 233)
 * Options, aclocal:                      aclocal Options.     (line   6)
 * Options, automake:                     automake Invocation. (line  37)
 * Options, std-options:                  List of Automake options.
-                                                              (line 144)
+                                                              (line 149)
 * Options, subdir-objects:               List of Automake options.
-                                                              (line 165)
+                                                              (line 170)
 * Ordering flag variables:               Flag Variables Ordering.
                                                               (line   6)
-* Overriding make rules:                 General Operation.   (line  46)
-* Overriding make targets:               General Operation.   (line  46)
-* Overriding make variables:             General Operation.   (line  51)
+* Overriding make rules:                 General Operation.   (line  47)
+* Overriding make targets:               General Operation.   (line  47)
+* Overriding make variables:             General Operation.   (line  52)
 * overriding rules:                      Extending.           (line  26)
 * overriding semantics:                  Extending.           (line  26)
 * Overriding testsuite environment:      Testsuite Environment Overrides.
@@ -6224,21 +6423,24 @@
                                                               (line   6)
 * Parallel build trees:                  VPATH Builds.        (line   6)
 * parallel-tests:                        List of Automake options.
-                                                              (line 129)
+                                                              (line 134)
 * Path stripping, avoiding:              Alternative.         (line  22)
+* pattern rules of GNU Make, disabled:   Suffixes.            (line  44)
 * pax format:                            List of Automake options.
-                                                              (line 174)
-* pdf:                                   Texinfo.             (line  25)
+                                                              (line 179)
+* pdf:                                   Texinfo.             (line  46)
 * pdf <1>:                               Extending.           (line  41)
 * PDF output using Texinfo:              Texinfo.             (line   6)
 * pdf-local:                             Extending.           (line  41)
 * Per-object flags, emulated:            Per-Object Flags.    (line   6)
 * per-target compilation flags, defined: Program and Library Variables.
-                                                              (line 195)
+                                                              (line 200)
 * pkgdatadir, defined:                   Uniform.             (line  19)
 * pkgincludedir, defined:                Uniform.             (line  19)
 * pkglibdir, defined:                    Uniform.             (line  19)
 * pkglibexecdir, defined:                Uniform.             (line  19)
+* posix:                                 List of Automake options.
+                                                              (line 125)
 * Preparing distributions:               Preparing Distributions.
                                                               (line   6)
 * Preprocessing Fortran 77:              Preprocessing Fortran 77.
@@ -6256,16 +6458,16 @@
 * Primary variable, SCRIPTS:             Scripts.             (line   6)
 * Primary variable, SOURCES:             Program Sources.     (line  32)
 * Primary variable, TEXINFOS:            Texinfo.             (line   6)
+* prog_LDADD, defined:                   Linking.             (line  12)
 * PROGRAMS primary variable:             Uniform.             (line  11)
 * Programs, auxiliary:                   Auxiliary Programs.  (line   6)
 * PROGRAMS, bindir:                      Program Sources.     (line   6)
 * Programs, conditional:                 Conditional Programs.
                                                               (line   6)
 * Programs, renaming during installation: Renaming.           (line   6)
-* prog_LDADD, defined:                   Linking.             (line  12)
 * Proxy Makefile for third-party packages: Third-Party Makefiles.
                                                               (line 131)
-* ps:                                    Texinfo.             (line  25)
+* ps:                                    Texinfo.             (line  46)
 * ps <1>:                                Extending.           (line  41)
 * PS output using Texinfo:               Texinfo.             (line   6)
 * ps-local:                              Extending.           (line  41)
@@ -6276,13 +6478,13 @@
 * read-only source tree:                 VPATH Builds.        (line  91)
 * README-alpha:                          Strictness.          (line  78)
 * readme-alpha:                          List of Automake options.
-                                                              (line 135)
+                                                              (line 140)
 * rebuild rules:                         Rebuilding.          (line   6)
-* rebuild rules <1>:                     CVS.                 (line   9)
+* rebuild rules <1>:                     Version Control.     (line   9)
 * recheck:                               Parallel Test Harness.
-                                                              (line 139)
+                                                              (line 142)
 * Recognized macros by Automake:         Optional.            (line   6)
-* Recursive operation of Automake:       General Operation.   (line  58)
+* Recursive operation of Automake:       General Operation.   (line  59)
 * recursive targets and third-party Makefiles: Third-Party Makefiles.
                                                               (line  15)
 * Register test case result:             Log files generation and test results recording.
@@ -6314,13 +6516,13 @@
 * SCRIPTS, installation directories:     Scripts.             (line  18)
 * Selecting the linker automatically:    How the Linker is Chosen.
                                                               (line   6)
-* serial number and --install:           aclocal Options.     (line  42)
+* serial number and --install:           aclocal Options.     (line  55)
 * serial numbers in macros:              Serials.             (line   6)
 * serial-tests:                          List of Automake options.
-                                                              (line 125)
+                                                              (line 130)
 * serial-tests, Using:                   Serial Test Harness. (line   6)
 * shar:                                  The Types of Distributions.
-                                                              (line  51)
+                                                              (line  52)
 * Shared libraries, support for:         A Shared Library.    (line   6)
 * Silencing make:                        Silencing Make.      (line   6)
 * Silent make:                           Silencing Make.      (line   6)
@@ -6333,10 +6535,10 @@
 * source tree and build tree:            VPATH Builds.        (line   6)
 * source tree, read-only:                VPATH Builds.        (line  91)
 * SOURCES primary, defined:              Program Sources.     (line  32)
-* Special Automake comment:              General Operation.   (line  68)
+* Special Automake comment:              General Operation.   (line  69)
 * Staged installation:                   DESTDIR.             (line  14)
 * std-options:                           List of Automake options.
-                                                              (line 144)
+                                                              (line 149)
 * Strictness, command line:              automake Invocation. (line  37)
 * Strictness, defined:                   Strictness.          (line  10)
 * Strictness, foreign:                   Strictness.          (line  51)
@@ -6344,7 +6546,7 @@
 * Strictness, gnu:                       Strictness.          (line  18)
 * su, before make install:               Basic Installation.  (line  49)
 * subdir-objects:                        List of Automake options.
-                                                              (line 165)
+                                                              (line 170)
 * Subdirectories, building conditionally: Conditional Subdirectories.
                                                               (line   6)
 * Subdirectories, configured conditionally: Unconfigured Subdirectories.
@@ -6364,6 +6566,7 @@
 * Subpackages <1>:                       Subpackages.         (line   6)
 * suffix .la, defined:                   Libtool Concept.     (line   6)
 * suffix .lo, defined:                   Libtool Concept.     (line  15)
+* suffix rules of Make, disabled:        Suffixes.            (line  44)
 * SUFFIXES, adding:                      Suffixes.            (line   6)
 * Support for C++:                       C++ Support.         (line   6)
 * Support for Fortran 77:                Fortran 77 Support.  (line   6)
@@ -6380,14 +6583,14 @@
 * tags:                                  Tags.                (line   9)
 * TAGS support:                          Tags.                (line   6)
 * tar formats:                           List of Automake options.
-                                                              (line 174)
+                                                              (line 179)
 * tar-pax:                               List of Automake options.
-                                                              (line 174)
+                                                              (line 179)
 * tar-ustar:                             List of Automake options.
-                                                              (line 174)
+                                                              (line 179)
 * tar-v7:                                List of Automake options.
-                                                              (line 174)
-* Target, install-info:                  Texinfo.             (line  85)
+                                                              (line 179)
+* Target, install-info:                  Texinfo.             (line 107)
 * Target, install-man:                   Man Pages.           (line  32)
 * targets, making into no-op:            Third-Party Makefiles.
                                                               (line  88)
@@ -6417,17 +6620,18 @@
                                                               (line  18)
 * Testsuite progress on console:         Scripts-based Testsuites.
                                                               (line  45)
-* Texinfo flag, EDITION:                 Texinfo.             (line  35)
-* Texinfo flag, UPDATED:                 Texinfo.             (line  35)
-* Texinfo flag, UPDATED-MONTH:           Texinfo.             (line  35)
-* Texinfo flag, VERSION:                 Texinfo.             (line  35)
+* Texinfo flag, EDITION:                 Texinfo.             (line  56)
+* Texinfo flag, UPDATED:                 Texinfo.             (line  56)
+* Texinfo flag, UPDATED-MONTH:           Texinfo.             (line  56)
+* Texinfo flag, VERSION:                 Texinfo.             (line  56)
+* Texinfo support:                       Texinfo.             (line   6)
 * texinfo.tex:                           Auxiliary Programs.  (line  77)
-* texinfo.tex <1>:                       Texinfo.             (line  70)
+* texinfo.tex <1>:                       Texinfo.             (line  92)
 * TEXINFOS primary, defined:             Texinfo.             (line   6)
-* third-party files and CVS:             CVS.                 (line 167)
+* third-party files and version control: Version Control.     (line 158)
 * Third-party packages, interfacing with: Third-Party Makefiles.
                                                               (line   6)
-* timestamps and CVS:                    CVS.                 (line  29)
+* timestamps and version control:        Version Control.     (line  29)
 * Transforming program names:            Renaming.            (line   6)
 * trees, source vs. build:               VPATH Builds.        (line   6)
 * true Example:                          true.                (line   6)
@@ -6446,24 +6650,31 @@
 * uninstall-hook:                        Extending.           (line  66)
 * uninstall-local:                       Extending.           (line  41)
 * Unit tests:                            Parallel Test Harness.
-                                                              (line 163)
+                                                              (line 166)
 * Unpacking:                             Basic Installation.  (line  27)
+* unsilencing Automake:                  Unsilencing Automake.
+                                                              (line   6)
 * UPCFLAGS and AM_UPCFLAGS:              Flag Variables Ordering.
                                                               (line  20)
-* UPDATED Texinfo flag:                  Texinfo.             (line  35)
-* UPDATED-MONTH Texinfo flag:            Texinfo.             (line  35)
+* UPDATED Texinfo flag:                  Texinfo.             (line  56)
+* UPDATED-MONTH Texinfo flag:            Texinfo.             (line  56)
 * Use Cases for the GNU Build System:    Use Cases.           (line   6)
 * user variables:                        User Variables.      (line   6)
 * Using aclocal:                         configure.           (line   6)
 * ustar format:                          List of Automake options.
-                                                              (line 174)
+                                                              (line 179)
 * v7 tar format:                         List of Automake options.
-                                                              (line 174)
-* Vala Support:                          Vala Support.        (line   6)
+                                                              (line 179)
+* Vala support:                          Vala Support.        (line   6)
 * variables, conflicting:                Extending.           (line  14)
-* Variables, overriding:                 General Operation.   (line  51)
+* Variables, overriding:                 General Operation.   (line  52)
 * variables, reserved for the user:      User Variables.      (line   6)
-* VERSION Texinfo flag:                  Texinfo.             (line  35)
+* verbose output from Automake:          Unsilencing Automake.
+                                                              (line   6)
+* version control and generated files:   Version Control.     (line  45)
+* version control and third-party files: Version Control.     (line 158)
+* version control and timestamps:        Version Control.     (line  29)
+* VERSION Texinfo flag:                  Texinfo.             (line  56)
 * VERSION, prevent definition:           Public Macros.       (line  54)
 * version.m4, example:                   Rebuilding.          (line  12)
 * version.sh, example:                   Rebuilding.          (line  12)
@@ -6476,15 +6687,15 @@
 * xpass:                                 Generalities about Testing.
                                                               (line  39)
 * xz:                                    The Types of Distributions.
-                                                              (line  30)
-* yacc, multiple parsers:                Yacc and Lex.        (line  73)
+                                                              (line  31)
+* yacc, multiple parsers:                Yacc and Lex.        (line  74)
 * YFLAGS and AM_YFLAGS:                  Flag Variables Ordering.
                                                               (line  20)
 * ylwrap:                                Auxiliary Programs.  (line  85)
-* ylwrap <1>:                            Yacc and Lex.        (line  73)
+* ylwrap <1>:                            Yacc and Lex.        (line  74)
 * zardoz example:                        Complete.            (line  35)
 * zip:                                   The Types of Distributions.
-                                                              (line  37)
+                                                              (line  38)
 * zstd:                                  The Types of Distributions.
-                                                              (line  41)
+                                                              (line  42)

_service:tar_scm:automake-1.16.5.tar.xz/doc/automake.texi -> _service:tar_scm:automake-1.17.tar.xz/doc/automake.texi Changed

@@ -25,7 +25,7 @@
 @value{UPDATED}), a program that creates GNU standards-compliant
 Makefiles from template files.
 
-Copyright @copyright{} 1995--2021 Free Software Foundation, Inc.
+Copyright @copyright{} 1995--2024 Free Software Foundation, Inc.
 
 @quotation
 Permission is granted to copy, distribute and/or modify this document
@@ -181,7 +181,7 @@
 * aclocal Invocation::          Auto-generating aclocal.m4
 * Macros::                      Autoconf macros supplied with Automake
 
-Auto-generating aclocal.m4
+Auto-generating aclocal.m4: Invoking @command{aclocal}
 
 * aclocal Options::             Options supported by aclocal
 * Macro Search Path::           How aclocal finds .m4 files
@@ -230,7 +230,7 @@
 * Fortran 9x Support::          Compiling Fortran 9x sources
 * Java Support with gcj::       Compiling Java sources using gcj
 * Vala Support::                Compiling Vala sources
-* Support for Other Languages::  Compiling other languages
+* Support for Other Languages:: Compiling other languages
 * Dependencies::                Automatic dependency tracking
 * EXEEXT::                      Support for executable extensions
 
@@ -256,6 +256,7 @@
 Common Issues Related to Libtool's Use
 
 * Error required file ltmain.sh not found::  The need to run libtoolize
+* Libtool library used but LIBTOOL is undefined::  test releases and libtoolize
 * Objects created both with libtool and without::  Avoid a specific build race
 
 Yacc and Lex support
@@ -295,10 +296,14 @@
 * Java::                        Java bytecode compilation (deprecated)
 * Python::                      Python
 
+Python
+
+* Supported Python versions::
+
 Building documentation
 
-* Texinfo::                     Texinfo
-* Man Pages::                   Man pages
+* Texinfo::
+* Man Pages::
 
 What Gets Installed
 
@@ -316,6 +321,15 @@
 * Checking the Distribution::   @samp{make distcheck} explained
 * The Types of Distributions::  A variety of formats and compression methods
 
+Checking the Distribution
+
+* DISTCHECK_CONFIGURE_FLAGS::  Overriding configure flags in distcheck.
+* distcheck-hook::             Running commands after distcheck.
+* dvi and distcheck::          Overriding the distcheck doc target.
+* distcleancheck::             Handling files not cleaned.
+* distuninstallcheck::         Overriding the uninstall check.
+* Errors with distclean::
+
 Support for test suites
 
 * Generalities about Testing::  Concepts and terminology about testing
@@ -351,7 +365,7 @@
 
 * Introduction to TAP::
 * Use TAP with the Automake test harness::
-* Incompatibilities with other TAP parsers and drivers::
+* Incompatibility with other TAP parsers and drivers::
 * Links and external resources on TAP::
 
 Changing Automake's Behavior
@@ -374,6 +388,7 @@
 * Make verbosity::              Make is verbose by default
 * Tricks For Silencing Make::   Standard and generic ways to silence make
 * Automake Silent Rules::       How Automake can help in silencing make
+* Unsilencing Automake::        Showing commands.
 
 When Automake Isn't Enough
 
@@ -382,11 +397,10 @@
 
 Frequently Asked Questions about Automake
 
-* CVS::                         CVS and generated files
+* Version Control::             Version control and generated files
 * maintainer-mode::             missing and AM_MAINTAINER_MODE
 * Wildcards::                   Why doesn't Automake support wildcards?
 * Limitations on File Names::   Limitations on source and installed file names
-* Errors with distclean::       Files left in build directory after distclean
 * Flag Variables Ordering::     CFLAGS vs.@: AM_CFLAGS vs.@: mumble_CFLAGS
 * Renamed Objects::             Why are object files sometimes renamed?
 * Per-Object Flags::            How to simulate per-object flags?
@@ -984,7 +998,7 @@
 each host.
 
 The GNU Build System also supports networked setups where part of the
-installed files should be shared amongst multiple hosts.  It does so
+installed files should be shared among multiple hosts.  It does so
 by distinguishing architecture-dependent files from
 architecture-independent files, and providing two @file{Makefile}
 targets to install each of these classes of files.
@@ -1200,7 +1214,7 @@
 @end example
 
 After this example, @code{amhello-1.0-i686.tar.gz} is ready to be
-uncompressed in @file{/} on many hosts.  (Using @code{`cat ../files.lst`}
+decompressed in @file{/} on many hosts.  (Using @code{`cat ../files.lst`}
 instead of @samp{.} as argument for @command{tar} avoids entries for
 each subdirectory in the archive: we would not like @command{tar} to
 restore the modification time of @file{/}, @file{/usr/}, etc.)
@@ -1571,23 +1585,38 @@
 =============================================
 @end example
 
-Note that running @command{autoreconf} is only needed initially when
+Running @command{autoreconf} is only needed initially, when
 the GNU Build System does not exist.  When you later change some
 instructions in a @file{Makefile.am} or @file{configure.ac}, the
 relevant part of the build system will be regenerated automatically
 when you execute @command{make}.
 
 @command{autoreconf} is a script that calls @command{autoconf},
-@command{automake}, and a bunch of other commands in the right order.
-If you are beginning with these tools, it is not important to figure
-out in which order all of these tools should be invoked and why.  However,
-because Autoconf and Automake have separate manuals, the important
-point to understand is that @command{autoconf} is in charge of
-creating @file{configure} from @file{configure.ac}, while
-@command{automake} is in charge of creating @file{Makefile.in}s from
-@file{Makefile.am}s and @file{configure.ac}.  This should at least
-direct you to the right manual when seeking answers.
+@command{automake}, and related commands in the right order.  If you
+are beginning with these tools, it is not important to figure out in
+which order all of these tools should be invoked and why. (But for the
+curious: the basic idea is to run:
+
+@enumerate
+@item @command{aclocal} (@pxref{aclocal Invocation}),
+@item @command{autoconf} (@pxref{,,,autoconf, The Autoconf Manual}),
+@item (if needed) @command{autoheader} (part of the
+Autoconf distribution), and
+@item @command{automake} (@pxref{automake Invocation}).
+@end enumerate
 
+@noindent
+If needed, tools related to Gettext (@pxref{,,,gettext, GNU gettext
+utilities}) and Libtool (@pxref{,,,libtool, The Libtool Manual}) are also
+invoked at different points.  Thus, as you can see, using
+@command{autoreconf} is quite a bit more convenient.
+
+Nevertheless, because Autoconf and Automake have separate manuals, an
+essential idea to understand is that Autoconf is in charge of creating
+@file{configure} from @file{configure.ac}, while Automake is in charge
+of creating @file{Makefile.in}s from @file{Makefile.am}s and
+@file{configure.ac}.  This should at least direct you to the right
+manual when seeking answers.
 
 @node amhello's configure.ac Setup Explained
 @subsection @code{amhello}'s @file{configure.ac} Setup Explained
@@ -1840,7 +1869,7 @@
 @cindex Automake parser, limitations of
 @cindex indentation in Makefile.am
 Generally, Automake is not particularly smart in the parsing of unusual
-Makefile constructs, so you're advised to avoid fancy constructs or
+@file{Makefile} constructs, so you're advised to avoid fancy constructs or
 ``creative'' use of whitespace.
 @c Keep this in sync with doc-parsing-buglets-tabs.sh
 For example, @key{TAB} characters cannot be used between a target name
@@ -1971,7 +2000,7 @@
 
 Future versions of Automake may, at this level of strictness, require
 certain non-standard GNU tools to be available to maintainer-only
-Makefile rules.  For instance, in the future @command{pathchk}
+@file{Makefile} rules.  For instance, in the future @command{pathchk}
 (@pxref{pathchk invocation,,, coreutils, GNU Coreutils})
 may be required to run @samp{make dist}.
 
@@ -2584,7 +2613,7 @@
 @file{true-true.o}. (The name of the object files rarely matters.)
 
 @node automake Invocation
-@chapter Creating a @file{Makefile.in}
+@chapter Creating a @file{Makefile.in}: Invoking @command{automake}
 @c This node used to be named "Invoking automake".  This @anchor
 @c allows old links to still work.
 @anchor{Invoking automake}
@@ -2670,8 +2699,8 @@
 
 @vindex AUTOMAKE_LIBDIR
 The environment variable @env{AUTOMAKE_LIBDIR} provides another way to
-set the directory containing Automake data files.  However
-@option{--libdir} takes precedence over it.
+set the directory containing Automake data files.  The
+@option{--libdir} option takes precedence over it.
 
 @item --print-libdir
 @opindex --print-libdir
@@ -3152,6 +3181,7 @@
 Programs, , Particular Program Checks, autoconf, The Autoconf Manual}.
 
 @item AC_PROG_LIBTOOL
+@itemx LT_INIT
 Automake will turn on processing for @command{libtool} (@pxref{Top, ,
 Introduction, libtool, The Libtool Manual}).
 
@@ -3246,8 +3276,8 @@
 @end ftable
 
 @node aclocal Invocation
-@section Auto-generating aclocal.m4
-@c This node used to be named "Invoking automake".  This @anchor
+@section Auto-generating aclocal.m4: Invoking @command{aclocal}
+@c This node used to be named "Invoking aclocal".  This @anchor
 @c allows old links to still work.
 @anchor{Invoking aclocal}
 
@@ -3288,14 +3318,14 @@
 argument, @command{aclocal} assumes the file belongs to the package
 and uses @code{m4_include} instead of copying it into
 @file{aclocal.m4}.  This makes the package smaller, eases dependency
-tracking, and cause the file to be distributed automatically.
+tracking, and causes the file to be distributed automatically.
 (@xref{Local Macros}, for an example.)  Any macro that is found in a
 system-wide directory or via an absolute search path will be copied.
 So use @samp{-I `pwd`/reldir} instead of @samp{-I reldir} whenever
-some relative directory should be considered outside the package.
+a relative directory should be considered to be outside the package.
 
 The contents of @file{acinclude.m4}, if this file exists, are also
-automatically included in @file{aclocal.m4}.  We recommend against
+automatically included in @file{aclocal.m4}.  We mostly recommend against
 using @file{acinclude.m4} in new packages (@pxref{Local Macros}).
 
 @vindex AUTOM4TE
@@ -3306,9 +3336,16 @@
 used, and omit from @file{aclocal.m4} all macros that are mentioned
 but otherwise unexpanded (this can happen when a macro is called
 conditionally).  @command{autom4te} is expected to be in the
-@env{PATH}, just as @command{autoconf}.  Its location can be
+@env{PATH}, just like @command{autoconf}.  Its location can be
 overridden using the @env{AUTOM4TE} environment variable.
 
+In practice it is usually simpler to run @command{autoreconf} instead
+of worrying about the required order of the various tools
+(@pxref{autoreconf Invocation, , Using @command{autoreconf}, autoconf,
+The Autoconf Manual}).
+
+This section explains the details of @command{aclocal}.
+
 @menu
 * aclocal Options::             Options supported by aclocal
 * Macro Search Path::           How aclocal finds .m4 files
@@ -3329,13 +3366,28 @@
 @table @code
 @item --automake-acdir=@var{dir}
 @opindex --automake-acdir
-Look for the automake-provided macro files in @var{dir} instead of
+Look for Automake-provided macro files in @var{dir} instead of
 in the installation directory.  This is typically used for debugging.
 
 @vindex ACLOCAL_AUTOMAKE_DIR
-The environment variable @env{ACLOCAL_AUTOMAKE_DIR} provides another
-way to set the directory containing automake-provided macro files.
-However @option{--automake-acdir} takes precedence over it.
+If this option is not specified, the value of the environment variable
+@env{ACLOCAL_AUTOMAKE_DIR}, if set, is used to set the directory
+containing Automake-provided macro files.  Otherwise an install-time
+default is used.
+
+@item --aclocal-path=@var{path}
+@opindex --aclocal-path
+Look for local third-party macro files (and the special @file{dirlist}
+file, @pxref{dirlist}) along @var{path} (a colon-separated list of
+directories) instead of in the installation directory.  (This can be
+used for building against alternative system roots (``sysroots'') for
+finding headers and libraries.)
+
+@vindex ACLOCAL_PATH
+If this option is not specified, the value of the environment variable
+@env{ACLOCAL_PATH}, if set, is used to set the search path containing
+local third-party macro files. Otherwise an install-time default is
+used.
 
 @item --system-acdir=@var{dir}
 @opindex --system-acdir
@@ -3356,7 +3408,7 @@
 
 @item --help
 @opindex --help
-Print a summary of the command line options and exit.
+Print a summary of the command line options and exit successfully.
 
 @item -I @var{dir}
 @opindex -I
@@ -3366,10 +3418,10 @@
 @item --install
 @opindex --install
 Install system-wide third-party macros into the first directory
-specified with @samp{-I @var{dir}} instead of copying them in the
+specified with @samp{-I @var{dir}} instead of copying them into the
 output file.
 @c Keep in sync with aclocal-install-absdir.sh
-Note that this will happen also if @var{dir} is an absolute path.
+This is also done if @var{dir} is an absolute path.
 
 @cindex serial number and @option{--install}
 When this option is used, and only when this option is used,
@@ -3385,8 +3437,8 @@
 of its dependencies is younger.
 
 This option forces the update of @file{aclocal.m4} (or the file
-specified with @file{--output} below) and only this file, it has
-absolutely no influence on files that may need to be installed by
+specified with @file{--output} below) and only this file; it has no
+influence on files that may need to be installed by
 @option{--install}.
 
 @item --output=@var{file}
@@ -3395,40 +3447,42 @@
 
 @item --print-ac-dir
 @opindex --print-ac-dir
-Prints the name of the directory that @command{aclocal} will search to
+Print the name of the directory that @command{aclocal} will search to
 find third-party @file{.m4} files.  When this option is given, normal
 processing is suppressed.  This option was used @emph{in the past} by
 third-party packages to determine where to install @file{.m4} macro
 files, but @emph{this usage is today discouraged}, since it causes
-@samp{$(prefix)} not to be thoroughly honored (which violates the
-GNU Coding Standards), and similar semantics can be better obtained
-with the @env{ACLOCAL_PATH} environment variable; @pxref{Extending aclocal}.
+@samp{$(prefix)} not to be thoroughly honored (violating the GNU
+Coding Standards). And similar semantics can be better obtained with
+the @env{ACLOCAL_PATH} environment variable (@pxref{Extending
+aclocal}).
 
 @item --verbose
 @opindex --verbose
-Print the names of the files it examines.
+Print the names of files examined.
 
 @item --version
 @opindex --version
-Print the version number of Automake and exit.
+Print the version number of Automake and exit successfully.
 
 @item -W CATEGORY
 @item --warnings=@var{category}
 @opindex -W
 @opindex --warnings
-Output warnings falling in @var{category}.  @var{category} can be
-one of:
+Output warnings falling in @var{category}, one of:
 @table @code
 @item syntax
 dubious syntactic constructs, underquoted macros, unused macros, etc.
 @item unsupported
-unknown macros
+unknown macros.
 @item all
-all the warnings, this is the default
+all the warnings; this is the default.
 @item none
-turn off all the warnings
+turn off all the warnings.
+@item no-@var{category}
+turn off warnings in @var{category}.
 @item error
-treat warnings as errors
+treat warnings as errors.
 @end table
 
 All warnings are output by default.
@@ -3456,14 +3510,14 @@
 
 @item @var{acdir}
 This directory is intended for third party @file{.m4} files, and is
-configured when @command{automake} itself is built.  This is
+configured when @command{automake} itself is built.  It is
 @file{@@datadir@@/aclocal/}, which typically
 expands to @file{$@{prefix@}/share/aclocal/}.  To find the compiled-in
 value of @var{acdir}, use the @option{--print-ac-dir} option
 (@pxref{aclocal Options}).
 @end table
 
-As an example, suppose that @command{automake-1.11.2} was configured with
+For example, suppose that Automake 1.11.2 was configured with
 @option{--prefix=@-/usr/local}.  Then, the search path would be:
 
 @enumerate
@@ -3471,20 +3525,20 @@
 @item @file{/usr/local/share/aclocal/}
 @end enumerate
 
-The paths for the @var{acdir} and @var{acdir-APIVERSION} directories can
-be changed respectively through aclocal options @option{--system-acdir}
-and @option{--automake-acdir} (@pxref{aclocal Options}).  Note however
-that these options are only intended for use by the internal Automake
-test suite, or for debugging under highly unusual situations; they are
-not ordinarily needed by end-users.
+The paths for the @var{acdir} and @var{acdir-APIVERSION} directories
+can be changed respectively through the @command{aclocal} options
+@option{--system-acdir} and @option{--automake-acdir} (@pxref{aclocal
+Options}).  These options are not ordinarily needed by end-users;
+they're mainly intended for use by the Automake test suite, or for
+debugging.
 
-As explained in (@pxref{aclocal Options}), there are several options that
-can be used to change or extend this search path.
+As also listed in (@pxref{aclocal Options}), several other options can
+be used to change or extend the macro search path.
 
 @subsubheading Modifying the Macro Search Path: @samp{-I @var{dir}}
 
-Any extra directories specified using @option{-I} options
-(@pxref{aclocal Options}) are @emph{prepended} to this search list.  Thus,
+Any directories specified using @option{-I} options (@pxref{aclocal
+Options}) are @emph{prepended} to this search list.  Thus,
 @samp{aclocal -I /foo -I /bar} results in the following search path:
 
 @enumerate
@@ -3494,15 +3548,17 @@
 @item @var{acdir}
 @end enumerate
 
+@anchor{dirlist}
 @subsubheading Modifying the Macro Search Path: @file{dirlist}
 @cindex @file{dirlist}
 
-There is a third mechanism for customizing the search path.  If a
-@file{dirlist} file exists in @var{acdir}, then that file is assumed to
-contain a list of directory patterns, one per line.  @command{aclocal}
-expands these patterns to directory names, and adds them to the search
-list @emph{after} all other directories.  @file{dirlist} entries may
-use shell wildcards such as @samp{*}, @samp{?}, or @code{...}.
+There is a third mechanism for customizing the search path: if a
+@file{dirlist} file exists in @var{acdir}, then that file is assumed
+to contain a list of directory patterns, one per line.
+@command{aclocal} expands these patterns to directory names, and adds
+them to the search list @emph{after} all other directories.
+@file{dirlist} entries may use shell wildcards such as @samp{*},
+@samp{?}, or @code{...}.
 
 For example, suppose
 @file{@var{acdir}/dirlist} contains the following:
@@ -3525,20 +3581,16 @@
 @item @var{acdir}
 @item @code{/test1}
 @item @code{/test2}
+@item all directories with path names starting with @code{/test3}.
 @end enumerate
 
-@noindent
-and all directories with path names starting with @code{/test3}.
-
 If the @option{--system-acdir=@var{dir}} option is used, then
-@command{aclocal} will search for the @file{dirlist} file in
-@var{dir}; but remember the warnings  above against the use of
-@option{--system-acdir}.
+@command{aclocal} will search for the @file{dirlist} file in that
+@var{dir}.
 
 @file{dirlist} is useful in the following situation: suppose that
-@command{automake} version @code{1.11.2} is installed with
-@samp{--prefix=/usr} by the system vendor.  Thus, the default search
-directories are
+Automake 1.11.2 is installed with @samp{--prefix=/usr} by the system
+vendor.  Thus, the default search directories are
 
 @c @code looks better than @file here
 @enumerate
@@ -3547,13 +3599,14 @@
 @end enumerate
 
 However, suppose further that many packages have been manually
-installed on the system, with $prefix=/usr/local, as is typical.  In
-that case, many of these ``extra'' @file{.m4} files are in
-@file{/usr/local/share/aclocal}.  The only way to force
-@file{/usr/bin/aclocal} to find these ``extra'' @file{.m4} files is to
-always call @samp{aclocal -I /usr/local/share/aclocal}.  This is
-inconvenient.  With @file{dirlist}, one may create a file
-@file{/usr/share/aclocal/dirlist} containing only the single line
+installed on the system, with @code{$prefix=/usr/local}, as is
+typical.  In that case, many of these ``extra'' @file{.m4} files are
+in @file{/usr/local/share/aclocal}.  Without @file{dirlist}, the only
+way to force @file{/usr/bin/aclocal} to find these ``extra''
+@file{.m4} files is to always call @samp{aclocal -I
+/usr/local/share/aclocal}.  This is inconvenient.  With
+@file{dirlist}, one can create a file
+@file{/usr/share/aclocal/dirlist} containing the single line
 
 @example
 /usr/local/share/aclocal
@@ -3569,50 +3622,56 @@
 @end enumerate
 
 @noindent
-without the need for @option{-I} options; @option{-I} options can be reserved
-for project-specific needs (@file{my-source-dir/m4/}), rather than
-using them to work around local system-dependent tool installation
-directories.
+This way, @option{-I} options can be reserved for project-specific
+needs (@file{my-source-dir/m4/}), rather than using them to work
+around local system-dependent tool installation directories.
 
 Similarly, @file{dirlist} can be handy if you have installed a local
 copy of Automake in your account and want @command{aclocal} to look for
 macros installed at other places on the system.
 
 @anchor{ACLOCAL_PATH}
-@subsubheading Modifying the Macro Search Path: @file{ACLOCAL_PATH}
+@subsubheading Modifying the Macro Search Path: @option{--aclocal-path}/@file{ACLOCAL_PATH}
+@opindex @option{--aclocal-path}
 @cindex @env{ACLOCAL_PATH}
 
-The fourth and last mechanism to customize the macro search path is
-also the simplest.  Any directory included in the colon-separated
-environment variable @env{ACLOCAL_PATH} is added to the search path
+The fourth and last mechanism to customize the macro search path: any
+directory included in the colon-separated path given to the
+@option{--aclocal-path} command-line option, or (if the option is not
+specified) in the @env{ACLOCAL_PATH} environment variable, is added to
+the search path.
 @c Keep in sync with aclocal-path-precedence.sh
-and takes precedence over system directories (including those found via
-@file{dirlist}), with the exception of the versioned directory
-@var{acdir-APIVERSION} (@pxref{Macro Search Path}).  However, directories
-passed via @option{-I} will take precedence over directories in
-@env{ACLOCAL_PATH}.
-
-@c Keep in sync with aclocal-path-installed.sh
-Also note that, if the @option{--install} option is used, any @file{.m4}
-file containing a required macro that is found in a directory listed in
-@env{ACLOCAL_PATH} will be installed locally.
-@c Keep in sync with aclocal-path-installed-serial.sh
-In this case, serial numbers in @file{.m4} are honored too,
-@pxref{Serials}.
-
-Conversely to @file{dirlist}, @env{ACLOCAL_PATH} is useful if you are
-using a global copy of Automake and want @command{aclocal} to look for
-macros somewhere under your home directory.
-
-@subsubheading Planned future incompatibilities
-
-The order in which the directories in the macro search path are currently
-looked up is confusing and/or suboptimal in various aspects, and is
-probably going to be changed in the future Automake release.  In
-particular, directories in @env{ACLOCAL_PATH} and @file{@var{acdir}}
+These directories take precedence over system directories, including
+those found via @file{dirlist}, with the exception of the versioned
+directory @var{acdir-APIVERSION} (@pxref{Macro Search Path}).
+However, directories passed via @option{-I} will take precedence over
+directories in @option{--aclocal-path}/@env{ACLOCAL_PATH}.
+
+@c Keep in sync with aclocal-path-install.sh
+If the @option{--install} option is used, any @file{.m4} file
+containing a required macro that is found in a directory listed in
+@option{--aclocal-path}/@env{ACLOCAL_PATH} will be installed locally.
+@c Keep in sync with aclocal-path-install-serial.sh
+In this case, serial numbers in @file{.m4} are honored too
+(@pxref{Serials}).
+
+@option{--aclocal-path}/@env{ACLOCAL_PATH} is useful if you are using
+a global copy of Automake and want @command{aclocal} to look for
+macros somewhere under your home directory. This is more or less the
+opposite of @file{dirlist}.
+
+@subsubheading Possible future incompatibility in @command{aclocal}
+
+The order in which the directories in the macro search path are
+currently looked up is confusing and/or suboptimal in various aspects.
+In particular, directories in
+@option{--aclocal-path}/@env{ACLOCAL_PATH} and @file{@var{acdir}}
 might end up taking precedence over @file{@var{acdir-APIVERSION}}, and
-directories in @file{@var{acdir}/dirlist} might end up taking precedence
-over @file{@var{acdir}}.  @emph{This is a possible future incompatibility!}
+directories in @file{@var{acdir}/dirlist} might end up taking
+precedence over @file{@var{acdir}}.  There are no definite plans to
+change the current behavior, but if bug reports show the need (so
+please report issues), the default might need to be changed, and the
+current behavior retained as an option.
 
 @node Extending aclocal
 @subsection Writing your own aclocal macros
@@ -3620,17 +3679,17 @@
 @cindex @command{aclocal}, extending
 @cindex Extending @command{aclocal}
 
-The @command{aclocal} program doesn't have any built-in knowledge of any
-macros, so it is easy to extend it with your own macros.
+The @command{aclocal} program doesn't have built-in knowledge of any
+macros. You can extend it with your own macros.
 
-This can be used by libraries that want to supply their own Autoconf
+Libraries, for example, usually want to supply their own Autoconf
 macros for use by other programs.  For instance, the @command{gettext}
 library supplies a macro @code{AM_GNU_GETTEXT} that should be used by
-any package using @command{gettext}.  When the library is installed, it
-installs this macro so that @command{aclocal} will find it.
+any package using @command{gettext}.  When the library is installed,
+it installs this macro so that @command{aclocal} will find it.
 
 A macro file's name should end in @file{.m4}.  Such files should be
-installed in @file{$(datadir)/aclocal}.  This is as simple as writing:
+installed in @file{$(datadir)/aclocal}.  This can be done with:
 
 @c Keep in sync with primary-prefix-couples-documented-valid.sh
 @example
@@ -3642,19 +3701,19 @@
 Please do use @file{$(datadir)/aclocal}, and not something based on
 the result of @samp{aclocal --print-ac-dir} (@pxref{Hard-Coded Install
 Paths}, for arguments).  It might also be helpful to suggest to
-the user to add the @file{$(datadir)/aclocal} directory to his
+the user to add the @file{$(datadir)/aclocal} directory to their
 @env{ACLOCAL_PATH} variable (@pxref{ACLOCAL_PATH}) so that
 @command{aclocal} will find the @file{.m4} files installed by your
 package automatically.
 
 A file of macros should be a series of properly quoted
 @code{AC_DEFUN}'s (@pxref{Macro Definitions, , , autoconf, The
-Autoconf Manual}).  The @command{aclocal} programs also understands
+Autoconf Manual}).  The @command{aclocal} program also understands
 @code{AC_REQUIRE} (@pxref{Prerequisite Macros, , , autoconf, The
 Autoconf Manual}), so it is safe to put each macro in a separate file.
-Each file should have no side effects but macro definitions.
-Especially, any call to @code{AC_PREREQ} should be done inside the
-defined macro, not at the beginning of the file.
+Each file should have no side effects except for defining the
+macro(s).  In particular, any call to @code{AC_PREREQ} should be done
+inside the defined macro, not at the beginning of the file.
 
 @cindex underquoted @code{AC_DEFUN}
 @acindex AC_DEFUN
@@ -3665,13 +3724,13 @@
 people, because @command{aclocal} was not so strict in the past and
 many third party macros are underquoted; and we have to apologize for
 this temporary inconvenience.  The reason we have to be stricter is
-that a future implementation of @command{aclocal} (@pxref{Future of
-aclocal}) will have to temporarily include all of these third party
-@file{.m4} files, maybe several times, even including files that end
-up not being needed.  Doing so should alleviate many problems of the
-current implementation; however, it requires a stricter style from
-macro authors.  Hopefully it is easy to revise the existing macros.
-For instance,
+that a possible future implementation of @command{aclocal}
+(@pxref{Future of aclocal}) will have to temporarily include all of
+these third party @file{.m4} files, maybe several times, even
+including files that end up not being needed.  Doing so should
+alleviate many problems of the current implementation; however, it
+requires a stricter style from macro authors.  Hopefully it is easy to
+revise the existing macros.  For instance,
 
 @example
 # bad style
@@ -3695,20 +3754,19 @@
 )
 @end example
 
-Wrapping the @code{AC_PREREQ} call inside the macro ensures that
-Autoconf 2.68 will not be required if @code{AX_FOOBAR} is not used.
-Most importantly, quoting the first argument of @code{AC_DEFUN} allows
-the macro to be redefined or included twice (otherwise this first
-argument would be expanded during the second definition).  For
-consistency we like to quote even arguments such as @code{2.68} that
-do not require it.
+Wrapping the @code{AC_PREREQ(2.68)} call inside the macro ensures
+that the Autoconf 2.68 will not be a prerequisite if @code{AX_FOOBAR}
+is not used.  Most importantly, quoting the first argument of
+@code{AC_DEFUN} allows the macro to be redefined or included twice
+(otherwise this first argument would be expanded during the second
+definition).  For consistency we like to quote even arguments such as
+@code{2.68} that do not require it.
 
 If you have been directed here by the @command{aclocal} diagnostic but
 are not the maintainer of the implicated macro, you will want to
-contact the maintainer of that macro.  Please make sure you have the
-latest version of the macro and that the problem hasn't already been
-reported before doing so: people tend to work faster when they aren't
-flooded by mails.
+contact the maintainer of that macro.  Please try to make sure you
+have the latest version of the macro and that the problem hasn't
+already been reported before doing so.
 
 Another situation where @command{aclocal} is commonly used is to
 manage macros that are used locally by the package; @ref{Local
@@ -3726,26 +3784,27 @@
 The first possibility (the historical practice) is to list all your
 macros in @file{acinclude.m4}.  This file will be included in
 @file{aclocal.m4} when you run @command{aclocal}, and its macro(s) will
-henceforth be visible to @command{autoconf}.  However if it contains
+henceforth be visible to @command{autoconf}.  However, if it contains
 numerous macros, it will rapidly become difficult to maintain, and it
 will be almost impossible to share macros between packages.
 
-The second possibility, which we do recommend, is to write each macro
-in its own file and gather all these files in a directory.  This
-directory is usually called @file{m4/}.  Then it's enough to update
-@file{configure.ac} by adding a proper call to @code{AC_CONFIG_MACRO_DIRS}:
+The second possibility, which we recommend, is to write each macro in
+its own file and gather all these files in a directory.  This
+directory is usually called @file{m4/}.  Then you can update
+@file{configure.ac} by adding a proper call to
+@code{AC_CONFIG_MACRO_DIRS}:
 
 @example
 AC_CONFIG_MACRO_DIRS(m4)
 @end example
 
 @command{aclocal} will then take care of automatically adding @file{m4/}
-to its search path for m4 files.
+to its search path for M4 files.
 
-When @samp{aclocal} is run, it will build an @file{aclocal.m4}
-that @code{m4_include}s any file from @file{m4/} that defines a
-required macro.  Macros not found locally will still be searched in
-system-wide directories, as explained in @ref{Macro Search Path}.
+When @command{aclocal} is run, it will build an @file{aclocal.m4} that
+@code{m4_include}s any file from @file{m4/} that defines a required
+macro.  Macros not found locally will still be searched in system-wide
+directories, as explained in @ref{Macro Search Path}.
 
 Custom macros should be distributed for the same reason that
 @file{configure.ac} is: so that other people have all the sources of
@@ -3753,23 +3812,22 @@
 happens automatically because all @code{m4_include}d files are
 distributed.
 
-However there is no consensus on the distribution of third-party
-macros that your package may use.  Many libraries install their own
-macro in the system-wide @command{aclocal} directory (@pxref{Extending
-aclocal}).  For instance, Guile ships with a file called
-@file{guile.m4} that contains the macro @code{GUILE_FLAGS} that can
-be used to define setup compiler and linker flags appropriate for
-using Guile.  Using @code{GUILE_FLAGS} in @file{configure.ac} will
-cause @command{aclocal} to copy @file{guile.m4} into
-@file{aclocal.m4}, but as @file{guile.m4} is not part of the project,
-it will not be distributed.  Technically, that means a user who
-needs to rebuild @file{aclocal.m4} will have to install Guile first.
-This is probably OK, if Guile already is a requirement to build the
-package.  However, if Guile is only an optional feature, or if your
-package might run on architectures where Guile cannot be installed,
-this requirement will hinder development.  An easy solution is to copy
-such third-party macros in your local @file{m4/} directory so they get
-distributed.
+There is no consensus on the distribution of third-party macros that
+your package may use.  Many libraries install their own macro in the
+system-wide @command{aclocal} directory (@pxref{Extending aclocal}).
+For instance, Guile ships with a file called @file{guile.m4} that
+contains the macro @code{GUILE_FLAGS} that can be used to define
+compiler and linker flags appropriate for using Guile.  Using
+@code{GUILE_FLAGS} in @file{configure.ac} will cause @command{aclocal}
+to copy @file{guile.m4} into @file{aclocal.m4}, but as @file{guile.m4}
+is not part of the project, it will not be distributed.  Technically,
+that means a user who needs to rebuild @file{aclocal.m4} will have to
+install Guile first.  This is probably OK, if Guile already is a
+requirement to build the package.  However, if Guile is only an
+optional feature, or if your package might run on architectures where
+Guile cannot be installed, this requirement will hinder development.
+An easy solution is to copy such third-party macros in your local
+@file{m4/} directory so they get distributed.
 
 Since Automake 1.10, @command{aclocal} offers the option @code{--install}
 to copy these system-wide third-party macros in your local macro directory,
@@ -3785,19 +3843,10 @@
 and depend on a new macro, this macro will be installed in your
 @file{m4/} automatically.  Another one is that serial numbers
 (@pxref{Serials}) can be used to update the macros in your source tree
-automatically when new system-wide versions are installed.  A serial
-number should be a single line of the form
-
-@example
-#serial @var{nnn}
-@end example
-
-@noindent
-where @var{nnn} contains only digits and dots.  It should appear in
-the M4 file before any macro definition.  It is a good practice to
-maintain a serial number for each macro you distribute, even if you do
-not use the @option{--install} option of @command{aclocal}: this allows
-other people to use it.
+automatically when new system-wide versions are installed. It is good
+practice to maintain a serial number for each macro you distribute,
+even if you do not use the @option{--install} option of
+@command{aclocal}: this allows other people to use it.
 
 
 @node Serials
@@ -3808,11 +3857,11 @@
 @cindex @command{aclocal} and serial numbers
 
 Because third-party macros defined in @file{*.m4} files are naturally
-shared between multiple projects, some people like to version them.
-This makes it easier to tell which of two M4 files is newer.  Since at
-least 1996, the tradition is to use a @samp{#serial} line for this.
+shared between multiple projects, people like to version them.  This
+makes it easier to tell which of two M4 files is newer.  Since at
+least 1996, the convention is to use a @samp{#serial} line for this.
 
-A serial number should be a single line of the form
+Such a serial number should be a single line of the form
 
 @example
 # serial @var{version}
@@ -3840,9 +3889,11 @@
 @samp{#serial} line, @command{aclocal} will ignore the file that has
 the older @samp{#serial} line (or the file that has none).
 
-Note that a serial number applies to a whole M4 file, not to any macro
-it contains.  A file can contain multiple macros, but only one
-serial.
+A serial number applies to a whole M4 file, not to any macro it
+contains.  A file can contain multiple macros, but only one serial
+number.
+
+@subsubheading Serial Number Example
 
 Here is a use case that illustrates the use of @option{--install} and
 its interaction with serial numbers.  Let's assume we maintain a
@@ -3942,8 +3993,8 @@
 macro, you can run @samp{aclocal --diff} to review the changes
 @samp{aclocal --install} would perform on these macros.
 
-Finally, note that the @option{--force} option of @command{aclocal} has
-absolutely no effect on the files installed by @option{--install}.  For
+Finally, note that the @option{--force} option of @command{aclocal}
+has no effect on the files installed by @option{--install}.  For
 instance, if you have modified your local macros, do not expect
 @option{--install --force} to replace the local macros by their
 system-wide versions.  If you want to do so, simply erase the local
@@ -3957,46 +4008,43 @@
 Ideally, @command{aclocal} should not be part of Automake.  Automake
 should focus on generating @file{Makefile}s; dealing with M4 macros is
 more Autoconf's job.  The fact that some people install Automake just
-to use @command{aclocal}, but do not use @command{automake} otherwise
-is an indication of how that feature is misplaced.
+to use @command{aclocal}, but do not use Automake otherwise, is an
+indication of how that feature is misplaced.
 
-The new implementation will probably be done slightly differently.
-For instance, it could enforce the @file{m4/}-style layout discussed in
+A new implementation would probably be done slightly differently.  For
+instance, it could enforce the @file{m4/}-style layout discussed in
 @ref{Local Macros}.
 
-We have no idea when and how this will happen.  This has been
-discussed several times in the past, but someone still has to commit
-to that non-trivial task.
+We do not know when or whether this will happen.  It has been
+discussed several times, but someone still has to commit to executing
+this non-trivial task.
 
-From the user point of view, @command{aclocal}'s removal might turn
+From the user's point of view, @command{aclocal}'s removal might turn
 out to be painful.  There is a simple precaution that you may take to
 make that switch more seamless: never call @command{aclocal} yourself.
-Keep this guy under the exclusive control of @command{autoreconf} and
-Automake's rebuild rules.  Hopefully you won't need to worry about
-things breaking; when @command{aclocal} disappears, because everything
-will have been taken care of.  If otherwise you used to call
-@command{aclocal} directly yourself or from some script, you will
-quickly notice the change.
+Keep its invocation under the exclusive control of
+@command{autoreconf} and Automake's rebuild rules.  Hopefully you
+won't need to worry about things breaking; when @command{aclocal}
+disappears, because everything will have been taken care of.  If
+otherwise you used to call @command{aclocal} directly yourself or from
+some script, you will quickly notice the change.
 
 Many packages come with a script called @file{bootstrap} or
-@file{autogen.sh}, that will just call @command{aclocal},
-@command{libtoolize}, @command{gettextize} or @command{autopoint},
-@command{autoconf}, @command{autoheader}, and @command{automake} in
-the right order.  In fact, this is precisely what @command{autoreconf}
-can do for you.  If your package has such a @file{bootstrap} or
-@file{autogen.sh} script, consider using @command{autoreconf}.  That
-should simplify its logic a lot (less things to maintain, all to the
-good), it's even likely you will not need the script anymore, and more
-to the point you will not call @command{aclocal} directly anymore.
+@file{autogen.sh} that calls @command{aclocal}, @command{libtoolize},
+@command{gettextize} or @command{autopoint}, @command{autoconf},
+@command{autoheader}, and @command{automake} in the right order.  In
+fact, this is precisely what @command{autoreconf} can do for you.  If
+your package has such a @file{bootstrap} or @file{autogen.sh} script,
+consider using @command{autoreconf}.  That should simplify its logic
+(all to the good), and more to the point you will not call
+@command{aclocal} directly anymore.
 
 For the time being, third-party packages should continue to install
 public macros into @file{/usr/share/aclocal/}.  If @command{aclocal}
 is replaced by another tool it might make sense to rename the
 directory, but supporting @file{/usr/share/aclocal/} for backward
-compatibility should be easy provided all macros are properly written
-(@pxref{Extending aclocal}).
-
-
+compatibility should be feasible, provided all macros are properly
+written (@pxref{Extending aclocal}).
 
 @node Macros
 @section Autoconf macros supplied with Automake
@@ -4018,7 +4066,7 @@
 
 @table @code
 
-@item AM_INIT_AUTOMAKE(OPTIONS)
+@item AM_INIT_AUTOMAKE(@var{options})
 @acindex AM_INIT_AUTOMAKE
 Runs many macros required for proper operation of the generated Makefiles.
 
@@ -4129,7 +4177,7 @@
 checks itself, and thus the explicit use of @code{AM_PROG_CC_C_O}
 should no longer be required.
 
-@item AM_PROG_LEX
+@item AM_PROG_LEX(@var{options})
 @acindex AM_PROG_LEX
 @acindex AC_PROG_LEX
 @cindex HP-UX 10, @command{lex} problems
@@ -4137,7 +4185,8 @@
 Like @code{AC_PROG_LEX} (@pxref{Particular Programs, , Particular
 Program Checks, autoconf, The Autoconf Manual}), but uses the
 @command{missing} script on systems that do not have @command{lex}.
-HP-UX 10 is one such system.
+HP-UX 10 is one such system. @var{options} are passed directly to
+@code{AC_PROG_LEX}.
 
 @item AM_PROG_GCJ
 @acindex AM_PROG_GCJ
@@ -4358,7 +4407,7 @@
 In addition to the built-in recursive targets defined by Automake
 (@code{all}, @code{check}, etc.), the developer can also define his
 own recursive targets.  That is done by passing the names of such
-targets as arguments to the m4 macro @code{AM_EXTRA_RECURSIVE_TARGETS}
+targets as arguments to the M4 macro @code{AM_EXTRA_RECURSIVE_TARGETS}
 in @file{configure.ac}.  Automake generates rules to handle the
 recursion for such targets; and the developer can define real actions
 for them by defining corresponding @code{-local} targets.
@@ -5140,7 +5189,7 @@
 @code{libdir} or @code{pkglibdir}.
 
 @xref{A Shared Library}, for information on how to build shared
-libraries using libtool and the @code{LTLIBRARIES} primary.
+libraries using Libtool and the @code{LTLIBRARIES} primary.
 
 Each @code{_LIBRARIES} variable is a list of the libraries to be built.
 For instance, to create a library named @file{libcpio.a}, but not install
@@ -5179,7 +5228,7 @@
 @code{RANLIB} (Automake will complain otherwise).  You should also
 call @code{AM_PROG_AR} to define @code{AR}, in order to support unusual
 archivers such as Microsoft lib.  @code{ARFLAGS} will default to
-@code{cru}; you can override this variable by setting it in your
+@code{cr}; you can override this variable by setting it in your
 @file{Makefile.am} or by @code{AC_SUBST}ing it from your
 @file{configure.ac}.  You can override the @code{AR} variable by
 defining a per-library @code{maude_AR} variable (@pxref{Program and
@@ -5246,17 +5295,16 @@
 
 @cindex suffix @file{.lo}, defined
 Because object files for shared and static libraries must be compiled
-differently, libtool is also used during compilation.  Object files
-built by libtool are called @dfn{libtool objects}: these are files
+differently, Libtool is also used during compilation.  Object files
+built by Libtool are called @dfn{libtool objects}: these are files
 using the @file{.lo} suffix.  Libtool libraries are built from these
 libtool objects.
 
 You should not assume anything about the structure of @file{.la} or
-@file{.lo} files and how libtool constructs them: this is libtool's
-concern, and the last thing one wants is to learn about libtool's
-guts.  However the existence of these files matters, because they are
-used as targets and dependencies in @file{Makefile}s' rules when
-building libtool libraries.  There are situations where you may have
+@file{.lo} files and how Libtool constructs them; this is Libtool's
+concern. However, the existence of these files matters, because they
+are used as targets and dependencies in @file{Makefile} rules when
+building Libtool libraries.  There are situations where you may have
 to refer to these, for instance when expressing dependencies for
 building source files conditionally (@pxref{Conditional Libtool
 Sources}).
@@ -5264,14 +5312,14 @@
 @cindex @file{libltdl}, introduction
 
 People considering writing a plug-in system, with dynamically loaded
-modules, should look into @file{libltdl}: libtool's dlopening library
+modules, should look into @file{libltdl}: Libtool's dlopening library
 (@pxref{Using libltdl, , Using libltdl, libtool, The Libtool Manual}).
-This offers a portable dlopening facility to load libtool libraries
+This offers a portable dlopening facility to load Libtool libraries
 dynamically, and can also achieve static linking where unavoidable.
 
-Before we discuss how to use libtool with Automake in detail, it
-should be noted that the libtool manual also has a section about how
-to use Automake with libtool (@pxref{Using Automake, , Using Automake
+Before we discuss how to use Libtool with Automake in detail, it
+should be noted that the Libtool manual also has a section about how
+to use Automake with Libtool (@pxref{Using Automake, , Using Automake
 with Libtool, libtool, The Libtool Manual}).
 
 @node Libtool Libraries
@@ -5285,9 +5333,9 @@
 @vindex pkglib_LTLIBRARIES
 @vindex _LTLIBRARIES
 
-Automake uses libtool to build libraries declared with the
+Automake uses Libtool to build libraries declared with the
 @code{LTLIBRARIES} primary.  Each @code{_LTLIBRARIES} variable is a
-list of libtool libraries to build.  For instance, to create a libtool
+list of Libtool libraries to build.  For instance, to create a libtool
 library named @file{libgettext.la}, and install it in @code{libdir},
 write:
 
@@ -5329,7 +5377,7 @@
 @noindent
 Whether @file{hello} is statically or dynamically linked with
 @file{libgettext.la} is not yet known: this will depend on the
-configuration of libtool and the capabilities of the host.
+configuration of Libtool and the capabilities of the host.
 
 
 @node Conditional Libtool Libraries
@@ -5342,14 +5390,14 @@
 conditionals or using Autoconf @code{AC_SUBST}itutions.
 
 The important implementation detail you have to be aware of is that
-the place where a library will be installed matters to libtool: it
+the place where a library will be installed matters to Libtool: it
 needs to be indicated @emph{at link-time} using the @option{-rpath}
 option.
 
 For libraries whose destination directory is known when Automake runs,
 Automake will automatically supply the appropriate @option{-rpath}
-option to libtool.  This is the case for libraries listed explicitly in
-some installable @code{_LTLIBRARIES} variables such as
+option to @command{libtool}.  This is the case for libraries listed
+explicitly in some installable @code{_LTLIBRARIES} variables such as
 @code{lib_LTLIBRARIES}.
 
 However, for libraries determined at configure time (and thus
@@ -5444,14 +5492,14 @@
 @vindex noinst_LTLIBRARIES
 @vindex check_LTLIBRARIES
 
-Sometimes you want to build libtool libraries that should not be
+Sometimes you want to build Libtool libraries that should not be
 installed.  These are called @dfn{libtool convenience libraries} and
 are typically used to encapsulate many sublibraries, later gathered
 into one big installed library.
 
 Libtool convenience libraries are declared by directory-less variables
 such as @code{noinst_LTLIBRARIES}, @code{check_LTLIBRARIES}, or even
-@code{EXTRA_LTLIBRARIES}.  Unlike installed libtool libraries they do
+@code{EXTRA_LTLIBRARIES}.  Unlike installed Libtool libraries they do
 not need an @option{-rpath} flag at link time (this is in fact the only
 difference).
 
@@ -5459,11 +5507,11 @@
 built.  Those listed in @code{check_LTLIBRARIES} are built only upon
 @samp{make check}.  Finally, libraries listed in
 @code{EXTRA_LTLIBRARIES} are never built explicitly: Automake outputs
-rules to build them, but if the library does not appear as a Makefile
+rules to build them, but if the library does not appear as a @file{Makefile}
 dependency anywhere it won't be built (this is why
 @code{EXTRA_LTLIBRARIES} is used for conditional compilation).
 
-Here is a sample setup merging libtool convenience libraries from
+Here is a sample setup merging Libtool convenience libraries from
 subdirectories into one main @file{libtop.la} library.
 
 @c Keep in sync with ltconv.sh
@@ -5535,8 +5583,8 @@
 @cindex libtool modules
 @cindex @option{-module}, libtool
 
-These are libtool libraries meant to be dlopened.  They are
-indicated to libtool by passing @option{-module} at link-time.
+These are Libtool libraries meant to be dlopened.  They are
+indicated to @command{libtool} by passing @option{-module} at link-time.
 
 @example
 pkglib_LTLIBRARIES = mymodule.la
@@ -5575,9 +5623,9 @@
 files) or libtool libraries (@file{.la}) to add to @var{library}.
 
 The @samp{@var{library}_LDFLAGS} variable is the place to list
-additional libtool linking flags, such as @option{-version-info},
-@option{-static}, and a lot more.  @xref{Link mode, , Link mode,
-libtool, The Libtool Manual}.
+additional @command{libtool} linking flags, such as
+@option{-version-info}, @option{-static}, and a lot more.  @xref{Link
+mode,,, libtool, The Libtool Manual}.
 
 The @command{libtool} command has two kinds of options: mode-specific
 options and generic options.  Mode-specific options such as the
@@ -5593,8 +5641,8 @@
 If @samp{@var{library}_LIBTOOLFLAGS} is not defined, then the variable
 @code{AM_LIBTOOLFLAGS} is used instead.
 
-These flags are passed to libtool after the @option{--tag=@var{tag}}
-option computed by Automake (if any), so
+These flags are passed to @command{libtool} after the
+@option{--tag=@var{tag}} option computed by Automake (if any), so
 @samp{@var{library}_LIBTOOLFLAGS} (or @code{AM_LIBTOOLFLAGS}) is a
 good place to override or supplement the @option{--tag=@var{tag}}
 setting.
@@ -5632,12 +5680,13 @@
 @subsection Common Issues Related to Libtool's Use
 
 @menu
-* Error required file ltmain.sh not found::  The need to run libtoolize
+* Error required file ltmain.sh not found::        The need to run libtoolize
+* Libtool library used but LIBTOOL is undefined::  aclocal and test releases
 * Objects created both with libtool and without::  Avoid a specific build race
 @end menu
 
 @node Error required file ltmain.sh not found
-@subsubsection Error: @samp{required file `./ltmain.sh' not found}
+@subsubsection Error: @samp{required file './ltmain.sh' not found}---@command{libtoolize} needed
 @cindex @file{ltmain.sh} not found
 @cindex @command{libtoolize}, no longer run by @command{automake}
 @cindex @command{libtoolize} and @command{autoreconf}
@@ -5646,7 +5695,7 @@
 @cindex @file{autogen.sh} and @command{autoreconf}
 
 Libtool comes with a tool called @command{libtoolize} that will
-install libtool's supporting files into a package.  Running this
+install Libtool's supporting files into a package.  Running this
 command will install @file{ltmain.sh}.  You should execute it before
 @command{aclocal} and @command{automake}.
 
@@ -5656,19 +5705,100 @@
 @command{libtoolize}.
 
 Since Automake 1.6, it has been decided that running
-@command{libtoolize} was none of Automake's business.  Instead, that
+@command{libtoolize} was not Automake's business.  Instead, that
 functionality has been moved into the @command{autoreconf} command
 (@pxref{autoreconf Invocation, , Using @command{autoreconf}, autoconf,
-The Autoconf Manual}).  If you do not want to remember what to run and
-when, just learn the @command{autoreconf} command.  Hopefully,
-replacing existing @file{bootstrap} or @file{autogen.sh} scripts by
-a call to @command{autoreconf} should also free you from any similar
-incompatible change in the future.
+The Autoconf Manual}).  The @command{autoreconf} command saves you
+from having to figure out which infrastructure scripts to run in what
+order.  Augmenting existing @file{bootstrap} or @file{autogen.sh}
+scripts with a call to @command{autoreconf} should also free you from
+any similar incompatible change in the future.
+
+@node Libtool library used but LIBTOOL is undefined
+@subsubsection Error: @samp{Libtool library used but 'LIBTOOL' is undefined}---@command{libtoolize} redux
+@cindex Libtool library used but @samp{LIBTOOL} is undefined
+@cindex @samp{LIBTOOL} is undefined
+
+This error message results from Automake seeing Libtool being used in
+@file{Makefile.am}, but the @code{LIBTOOL} variable is not defined.
+There are two common reasons for this.  First, @code{LT_INIT} is
+missing from @file{configure.ac}; it can simply be added.
+
+The second reason is more complicated: if you've installed Automake
+under a separate prefix, Automake cannot know where to find the
+@code{LT_INIT} macro.  Automake looks in the @file{aclocal.m4} file,
+which is generated by the @command{aclocal} command (@pxref{aclocal
+Invocation}). But since the default search paths for @command{aclocal}
+are based on where it is installed (@pxref{Macro Search Path}), if
+Automake is installed in one place (e.g., because it's for a test
+release), and Libtool in another (e.g., for general system use),
+@file{libtool.m4} won't be found by @command{aclocal} and thus
+@code{LT_INIT} won't be defined.
+
+The best solution is to run @command{libtoolize} in the tree that is
+using the separately-installed Automake.  That will copy 
+@file{libtool.m4} and the other Libtool M4 files and scripts into your
+package, including @file{ltmain.sh} (see previous section).  If you
+have subpackages that use Libtool independently, you'll need to run
+@command{libtoolize} in each of them. @xref{Invoking libtoolize,,,
+libtool, The Libtool Manual}.
+
+The @command{libtoolize} output suggests using an @file{m4} subdirectory:
+
+@example
+libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS(m4)' to configure.ac,
+libtoolize: and rerunning libtoolize and aclocal.
+libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
+@end example
+
+For purposes of Libtool and Automake, however, an m4 subdirectory is
+required, not just something to consider.  Without having the Libtool
+M4 files in the local package, @command{aclocal} will (frustratingly)
+report the same @samp{Libtool library used but ...} error.  (The name
+of the subdirectory for the M4 files can be anything, but @samp{m4} is
+by far the most common convention.)
+
+Here is a concrete example.  Suppose you've installed a test
+release of Automake (thank you) with @code{--prefix=/tmp/amtest}, and
+thus put @code{/tmp/amtest/bin} first in your @env{PATH}.  You already
+have Libtool installed under @code{/usr/local/gnu}.  Then, your
+Libtool-using package will fail to bootstrap, with the error:
+
+@example
+Makefile.am:161: error: Libtool library used but 'LIBTOOL' is undefined
+...
+@end example
+
+You can resolve this by ensuring your @file{configure.ac} includes
+these lines (after the @code{AM_INIT_AUTOMAKE}):
+
+@example
+AC_CONFIG_MACRO_DIRS(m4)
+AM_PROG_AR
+LT_INIT
+@end example
+
+@noindent
+and then running:
+
+@example
+libtoolize
+autoreconf
+@end example
+
+@noindent
+To summarize, the @command{libtoolize} (from the system directory)
+copies @file{libtool.m4} and the other Libtool support files into your
+package. The subsequent @command{autoreconf} then runs
+@command{aclocal} (under the test prefix) which can now find
+@code{LT_INIT}.
+
+(For more discussion of this, see @url{https://bugs.gnu.org/71847}.
 
 @node Objects created both with libtool and without
 @subsubsection Objects @samp{created with both libtool and without}
 
-Sometimes, the same source file is used both to build a libtool
+Sometimes, the same source file is used both to build a Libtool
 library and to build another non-libtool target (be it a program or
 another library).
 
@@ -5690,7 +5820,7 @@
 
 Technically, it means that we should build @file{foo.$(OBJEXT)} for
 @file{prog}, and @file{foo.lo} for @file{libfoo.la}.  The problem is
-that in the course of creating @file{foo.lo}, libtool may erase (or
+that in the course of creating @file{foo.lo}, Libtool may erase (or
 replace) @file{foo.$(OBJEXT)}, and this cannot be avoided.
 
 Therefore, when Automake detects this situation it will complain
@@ -5741,7 +5871,7 @@
 compiled to build the program.  These files are added to the
 distribution by default.  When building the program, Automake will cause
 each source file to be compiled to a single @file{.o} file (or
-@file{.lo} when using libtool).  Normally these object files are named
+@file{.lo} when using Libtool).  Normally these object files are named
 after the source file, but other factors can change this.  If a file in
 the @code{_SOURCES} variable has an unrecognized extension, Automake
 will do one of two things with it.  If a suffix rule exists for turning
@@ -5811,13 +5941,18 @@
 libmaude_a_AR = $(CXX) -ar -o
 @end example
 
+@item maude_RANLIB
+A static library's index is updated by default by invoking @samp{$(RANLIB)}
+followed by the name of the library.  You can override this by setting the
+@code{_RANLIB} variable.
+
 @item maude_LIBADD
 Extra objects can be added to a @emph{library} using the @code{_LIBADD}
 variable.  For instance, this should be used for objects determined by
 @command{configure} (@pxref{A Library}).
 
-In the case of libtool libraries, @code{maude_LIBADD} can also refer
-to other libtool libraries.
+In the case of Libtool libraries, @code{maude_LIBADD} can also refer
+to other Libtool libraries.
 
 @item maude_LDADD
 Extra objects (@file{*.$(OBJEXT)}) and libraries (@file{*.a},
@@ -6040,8 +6175,8 @@
 Without the last line, they will be built from @file{test1.c},
 @file{test2.c}, and @file{test3.c}.
 
-@cindex Libtool modules, default source example
-@cindex default source, Libtool modules example
+@cindex libtool modules, default source example
+@cindex default source, libtool modules example
 Another case where this is convenient is building many Libtool modules
 (@file{module@var{n}.la}), each defined in its own file
 (@file{module@var{n}.c}).
@@ -6322,7 +6457,8 @@
 @file{.lpp} are recognized.
 
 You should never explicitly mention the intermediate (C or C++) file
-in any @code{SOURCES} variable; only list the source file.
+in any @code{SOURCES} variable (except @code{BUILT_SOURCES}, see below);
+only list the source file.
 
 The intermediate files generated by @command{yacc} (or @command{lex})
 will be included in any distribution that is made.  That way the user
@@ -6352,11 +6488,11 @@
 it is up to you to ensure the header gets built before it is first
 used.  Typically this is necessary in order for dependency tracking to
 work when the header is included by another file.  The common solution
-is listing the header file in @code{BUILT_SOURCES} (@pxref{Sources})
-as follows.
+is listing the header file, and the corresponding C file, in
+@code{BUILT_SOURCES} (@pxref{Sources}) as follows.
 
 @example
-BUILT_SOURCES = parser.h
+BUILT_SOURCES = parser.h parser.c
 AM_YFLAGS = -d
 bin_PROGRAMS = foo
 foo_SOURCES = @dots{} parser.y @dots{}
@@ -6398,8 +6534,8 @@
 * Linking Multiple Yacc Parsers::
 @end menu
 
-@subsection Linking Multiple Yacc Parsers
 @node Linking Multiple Yacc Parsers
+@subsection Linking Multiple Yacc Parsers
 
 @cindex Linking multiple @command{yacc} parsers
 
@@ -6975,24 +7111,29 @@
 
 
 @node Vala Support
-@comment  node-name,  next,  previous,  up
 @section Vala Support
 
-@cindex Vala Support
+@cindex Vala support
 @cindex Support for Vala
+@cindex GNU Make, required by Vala
 
-Automake provides initial support for Vala
-(@uref{https://www.vala-project.org/}).
-This requires valac version 0.7.0 or later, and currently requires
-the user to use GNU @command{make}.
+Automake supports Vala (@uref{https://vala.dev/}).
+Vala support requires the user to use GNU @command{make}.
 
 @example
 foo_SOURCES = foo.vala bar.vala zardoz.c
 @end example
 
 Any @file{.vala} file listed in a @code{_SOURCES} variable will be
-compiled into C code by the Vala compiler. The generated @file{.c} files
-are distributed. The end user does not need to have a Vala compiler installed.
+compiled into C code by the Vala compiler.  The generated @file{.c}
+files are distributed. The end user does not need to have a Vala
+compiler installed.
+
+Because all C files must be generated, and the Vala compiler compiles
+all the @file{.vala} files for a target at once, it is not possible to
+add files to a @code{_SOURCES} variable that cannot be compiled
+together; for example, alternative platform-specific definitions of
+the same methods.
 
 Automake ships with an Autoconf macro called @code{AM_PROG_VALAC}
 that will locate the Vala compiler and optionally check its version
@@ -7085,7 +7226,7 @@
 only on the maintainer's system, as configurations vary too much.  So
 instead Automake implements dependency tracking at build time.
 
-Automatic dependency tracking can be suppressed by putting
+This automatic dependency tracking can be suppressed by putting
 @option{no-dependencies} in the variable @code{AUTOMAKE_OPTIONS}, or
 passing @option{no-dependencies} as an argument to @code{AM_INIT_AUTOMAKE}
 (this should be the preferred way).  Or, you can invoke @command{automake}
@@ -7094,12 +7235,34 @@
 @vindex AUTOMAKE_OPTIONS
 @opindex no-dependencies
 
+@cindex Disabling dependency tracking
+@cindex Dependency tracking, disabling
 The person building your package also can choose to disable dependency
 tracking by configuring with @option{--disable-dependency-tracking}.
 
-@cindex Disabling dependency tracking
-@cindex Dependency tracking, disabling
+@cindex Conditional for dependency tracking
+If, as the package maintainer, you wish to conditionalize your
+@code{Makefile.am} according to whether dependency tracking is
+enabled, the best way is to define your own conditional in
+@code{configure.ac} according to the shell variable
+@code{$enable_dependency_tracking} (all
+@code{--enable}/@code{--disable} options are available as shell
+variables; @pxref{Package Options, , , autoconf, The Autoconf Manual}):
+
+@example
+AM_CONDITIONAL(NO_DEP_TRACKING,
+               test x"$enable_dependency_tracking" = x"no")
+@end example
 
+And then in your @code{Makefile.am}:
+
+@example
+if NO_DEP_TRACKING
+# stuff to do when dependency tracking is disabled
+else
+# stuff to do when it's enabled
+endif
+@end example
 
 @node EXEEXT
 @section Support for executable extensions
@@ -7349,14 +7512,16 @@
 @vindex DATA
 
 @vindex data_DATA
+@vindex doc_DATA
+@vindex lisp_DATA
 @vindex sysconf_DATA
 @vindex sharedstate_DATA
 @vindex localstate_DATA
 @vindex pkgdata_DATA
 
 Such data can be installed in the directories @code{datadir},
-@code{sysconfdir}, @code{sharedstatedir}, @code{localstatedir}, or
-@code{pkgdatadir}.
+@code{docdir}, @code{lispdir}, @code{sysconfdir}, @code{sharedstatedir},
+@code{localstatedir}, or @code{pkgdatadir}.
 
 By default, data files are @emph{not} included in a distribution.  Of
 course, you can use the @code{dist_} prefix to change this on a
@@ -7468,7 +7633,7 @@
 The symptom is as follows.
 
 @example
-% make
+% @kbd{make}
 source='foo.c' object='foo.o' libtool=no \
 depfile='.deps/foo.Po' tmpdepfile='.deps/foo.TPo' \
 depmode=gcc /bin/sh ./depcomp \
@@ -7503,7 +7668,7 @@
 See how @file{bindir.h} gets built first:
 
 @example
-% make
+% @kbd{make}
 echo '#define bindir "/usr/local/bin"' >bindir.h
 make  all-am
 make1: Entering directory `/home/adl/tmp'
@@ -7520,12 +7685,12 @@
 if you try to run @samp{make foo} explicitly:
 
 @example
-% make clean
+% @kbd{make clean}
 test -z "bindir.h" || rm -f bindir.h
 test -z "foo" || rm -f foo
 rm -f *.o
-% : > .deps/foo.Po # Suppress previously recorded dependencies
-% make foo
+% @kbd{: > .deps/foo.Po} # Suppress previously recorded dependencies
+% @kbd{make foo}
 source='foo.c' object='foo.o' libtool=no \
 depfile='.deps/foo.Po' tmpdepfile='.deps/foo.TPo' \
 depmode=gcc /bin/sh ./depcomp \
@@ -7927,8 +8092,18 @@
 
 @item pythondir
 @cindex @file{site-packages} Python directory
-The directory name for the @file{site-packages} subdirectory of the
-standard Python install tree.
+@cindex @file{dist-packages} Python directory
+The subdirectory of the Python install tree in which to install Python
+scripts. By default this is, on all systems,
+@file{$PYTHON_PREFIX/lib/python@var{version}/site-packages}, where
+@code{$PYTHON_PREFIX} is described above, and @var{version} is the
+Python version.  (For those knowledgeable about Python installation
+details: systems generally have their own Python installation scheme,
+such as @code{posix_local} on Debian and related (as of
+Python@tie{}3.10), which ends up using a directory named
+@file{dist-packages}; Automake uses the @code{posix_prefix} scheme and
+@file{site-packages}.)
+@c https://bugs.gnu.org/54412 et al.
 
 @item pkgpythondir
 This is the directory under @code{pythondir} that is named after the
@@ -7962,6 +8137,59 @@
 Variables, autoconf, The Autoconf Manual}).  See also @ref{Hard-Coded
 Install Paths}.
 
+@menu
+* Supported Python versions::
+@end menu
+
+@node Supported Python versions
+@subsection Supported versions
+
+Automake guarantees releases will support all Python versions that are still
+supported by the Python project at the time of the Automake release.  Support
+for EOL versions of Python are not guaranteed, but will be considered as long
+as it is not onerous to do so, and there are large supported distros including
+them.  If you need to support older Python versions, please use a previous
+Automake release.
+
+Here are the current support plans.
+
+@multitable {2.0 -- 3.5} {Unsupported}
+@headitem Version @tab Status
+@item 0.x
+@tab Not supported
+@item 1.x
+@tab Not supported
+@item 2.0--2.6
+@tab Untested, but should work
+@item 2.7
+@c Debian Bullseye goes EOL in Apr 2026.
+@tab Supported (until Apr 2026)
+@item 3.0--3.3
+@tab Untested, but should work
+@item 3.4
+@c Ubuntu Trusty goes EOL in Apr 2022.
+@tab Supported (until Apr 2022)
+@item 3.5
+@c Ubuntu Xenial goes EOL in Apr 2024.
+@tab Supported (until Apr 2024)
+@item 3.6
+@c Ubuntu Bionic goes EOL in Apr 2028.
+@tab Supported (until Apr 2028)
+@item 3.7
+@c Debian Buster goes EOL in Apr 2024.
+@c But should support at least as long as previous Python version?
+@tab Supported (until Apr 2028)
+@item 3.8
+@c Ubuntu Focal goes EOL in Apr 2030
+@tab Supported (until Apr 2030)
+@item 3.9
+@c Debian Bullseye goes EOL in Apr 2026.
+@c But should support at least as long as previous Python version?
+@tab Supported (until Apr 2030)
+@item 3.10
+@c But should support at least as long as previous Python version?
+@tab Supported (until Apr 2030)
+@end multitable
 
 @node Documentation
 @chapter Building documentation
@@ -7969,14 +8197,15 @@
 Currently Automake provides support for Texinfo and man pages.
 
 @menu
-* Texinfo::                     Texinfo
-* Man Pages::                   Man pages
+* Texinfo::
+* Man Pages::
 @end menu
 
 
 @node Texinfo
 @section Texinfo
 
+@cindex Texinfo support
 @cindex @code{_TEXINFOS} primary, defined
 @cindex @code{TEXINFOS} primary, defined
 @cindex Primary variable, @code{TEXINFOS}
@@ -8007,6 +8236,29 @@
 rather than in the @code{builddir}.  This can be changed with the
 @option{info-in-builddir} option.
 
+If the Texinfo sources are in a subdirectory relative to the Makefile, then
+@code{-I} flags for the subdirectory, both in the source directory and in the
+build directory, will automatically be added.  There is no need to specify
+these in @samp{$(MAKEINFO)}, @samp{$(MAKEINFOFLAGS)}, etc.
+
+@cindex @samp{@@setfilename} Texinfo directive
+If a Texinfo source file contains an @samp{@@setfilename} directive,
+and its argument has extension @samp{.info} (or no extension, but this
+is discouraged), that argument should be the same as the basename of
+the Texinfo file, extended with @samp{.info}.  The Make rules
+generated by Automake assume this, and will not work if the
+@samp{@@setfilename} is for some other name.
+
+@cindex @file{.texi.in} file, read
+If a Texinfo source @samp{foo.texi} is not present, but
+@file{foo.texi.in} exists, Texinfo will read that @file{.texi.in} file
+for @code{@@setfilename} and @code{@@include version.texi} (described
+below).
+
+Texinfo source files need not be present at all, and if present, need
+not contain @code{@@setfilename}.  Then the file name given in the
+Makefile.am will be used.
+
 @trindex dvi
 @trindex html
 @trindex pdf
@@ -8038,11 +8290,12 @@
 
 @cindex @file{mdate-sh}
 
-If the @file{.texi} file @code{@@include}s @file{version.texi}, then
-that file will be automatically generated.  The file @file{version.texi}
-defines four Texinfo flags you can reference using
-@code{@@value@{EDITION@}}, @code{@@value@{VERSION@}},
-@code{@@value@{UPDATED@}}, and @code{@@value@{UPDATED-MONTH@}}.
+If a @file{.texi} file @code{@@include}s @file{version.texi} (actually
+any file named @file{vers...texi}, then that file will be
+automatically generated.  The file @file{version.texi} defines four
+Texinfo flags you can reference using @code{@@value@{EDITION@}},
+@code{@@value@{VERSION@}}, @code{@@value@{UPDATED@}}, and
+@code{@@value@{UPDATED-MONTH@}}.
 
 @table @code
 @item EDITION
@@ -8066,7 +8319,7 @@
 If you have multiple Texinfo files, and you want to use the
 @file{version.texi} feature, then you have to have a separate version
 file for each Texinfo file.  Automake will treat any include in a
-Texinfo file that matches @file{vers*.texi} just as an automatically
+Texinfo file that matches @file{vers*.texi} just like an automatically
 generated version file.
 
 Often an Info file depends on more than one @file{.texi} file.  For
@@ -8143,12 +8396,14 @@
 
 @item AM_MAKEINFOFLAGS
 @itemx AM_MAKEINFOHTMLFLAGS
+@itemx AM_TEXI2FLAGS
 Maintainer flags passed to each @command{makeinfo} invocation.  Unlike
 @code{MAKEINFOFLAGS}, these variables are meant to be defined by
 maintainers in @file{Makefile.am}.  @samp{$(AM_MAKEINFOFLAGS)} is
-passed to @code{makeinfo} when building @file{.info} files; and
+passed to @code{makeinfo} when building @file{.info} files;
 @samp{$(AM_MAKEINFOHTMLFLAGS)} is used when building @file{.html}
-files.
+files; and @samp{$(AM_TEXI2FLAGS)} is used when building @file{.dvi} and
+@file{.pdf} files.
 
 @c Keep in sync with txinfo-many-output-formats.sh
 For instance, the following setting can be used to obtain one single
@@ -8555,12 +8810,30 @@
 
 @c See automake #9822.
 @vindex TAR
-You can set the environment variable @code{TAR} to override the tar
-program used; it defaults to @code{tar}.  @xref{The Types of
-Distributions}, for how to generate other kinds of archives.
+You can set the environment (or @code{Makefile.am}) variable @code{TAR}
+to override the tar program used; it defaults to @code{tar}.
+@xref{The Types of Distributions}, for how to generate other kinds of
+archives.
+
+@vindex TAR_OPTIONS
+With GNU tar, you can also set the environment (or @code{Makefile.am})
+variable @code{TAR_OPTIONS} to pass options to @code{tar}.  One common
+case for this is wanting to avoid using the local user's uid and gid
+in the tar file, or the uid being larger than is supported by the tar
+format (not uncommon nowadays). This can be done with, for example>
 
-For the most part, the files to distribute are automatically found by
-Automake:
+@example
+TAR_OPTIONS = --owner=0 --group=0
+export TAR_OPTIONS
+@end example
+
+@noindent
+The @code{export} (a GNU make feature) is necessary to pass the
+variable in the environment to the @code{tar} invocation.
+(For more discussion, see @url{https://bugs.gnu.org/19615}.)
+
+For the most part, the files to distribute are automatically
+found by Automake:
 
 @itemize @bullet
 @item
@@ -8741,10 +9014,10 @@
 @emph{operating from it}, takes the following steps (in this order):
 @itemize
 @item
-tries to do a @code{VPATH} build (@pxref{VPATH Builds}), with the
+does a @code{VPATH} build (@pxref{VPATH Builds}), with the
 @code{srcdir} and all its content made @emph{read-only};
 @item
-tries to make the printable documentation, if any (with @command{make dvi}),
+makes the printable documentation (with @command{make dvi}), if any,
 @item
 runs the test suite (with @command{make check}) on this fresh build;
 @item
@@ -8763,12 +9036,23 @@
 exact location and the exact structure of such a directory (where the
 read-only sources are placed, how the temporary build and install
 directories are named and how deeply they are nested, etc.) is to be
-considered an implementation detail, which can change at any time; so
-do not rely on it.
+considered an implementation detail, which can change at any time, so
+please do not rely on it.
+
+@menu
+* DISTCHECK_CONFIGURE_FLAGS::  Overriding configure flags in distcheck.
+* distcheck-hook::             Running commands after distcheck.
+* dvi and distcheck::          Overriding the distcheck doc target.
+* distcleancheck::             Handling files not cleaned.
+* distuninstallcheck::         Overriding the uninstall check.
+* Errors with distclean::
+@end menu
 
+@node DISTCHECK_CONFIGURE_FLAGS
+@subsection @code{DISTCHECK_CONFIGURE_FLAGS}
 @vindex AM_DISTCHECK_CONFIGURE_FLAGS
 @vindex DISTCHECK_CONFIGURE_FLAGS
-@subheading DISTCHECK_CONFIGURE_FLAGS
+
 Building the package involves running @samp{./configure}.  If you need
 to supply additional flags to @command{configure}, define them in the
 @code{AM_DISTCHECK_CONFIGURE_FLAGS} variable in your top-level
@@ -8782,31 +9066,52 @@
 @code{AM_DISTCHECK_CONFIGURE_FLAGS} nor by
 @code{DISTCHECK_CONFIGURE_FLAGS}.
 
-Also note that developers are encouraged to strive to make their code
-buildable without requiring any special configure option; thus, in
-general, you shouldn't define @code{AM_DISTCHECK_CONFIGURE_FLAGS}.
-However, there might be few scenarios in which the use of this variable
-is justified.
-GNU @command{m4} offers an example.  GNU @command{m4} configures by
-default with its experimental and seldom used "changeword" feature
-disabled; so in this case it is useful to have @command{make distcheck}
-run configure with the @option{--with-changeword} option, to ensure that
-the code for changeword support still compiles correctly.
-GNU @command{m4} also employs the @code{AM_DISTCHECK_CONFIGURE_FLAGS}
-variable to stress-test the use of @option{--program-prefix=g}, since at
-one point the @command{m4} build system had a bug where @command{make
-installcheck} was wrongly assuming it could blindly test "@command{m4}",
-rather than the just-installed "@command{gm4}".
+Developers are encouraged to strive to make their code buildable
+without requiring any special configure option; thus, in general, you
+shouldn't define @code{AM_DISTCHECK_CONFIGURE_FLAGS}.  GNU
+@command{m4} offers an example of when its use is justified, however.
+GNU @command{m4} configures by default with its experimental and
+seldom used @samp{changeword} feature disabled; so in this case it is
+useful to have @command{make distcheck} run configure with the
+@option{--with-changeword} option, to ensure that the code for
+changeword support still compiles correctly.  GNU @command{m4} also
+employs the @code{AM_DISTCHECK_CONFIGURE_FLAGS} variable to
+stress-test the use of @option{--program-prefix=g}, since at one point
+the @command{m4} build system had a bug where @command{make
+installcheck} was wrongly assuming it could blindly test @samp{m4},
+rather than the just-installed @samp{gm4}.
+
+@node distcheck-hook
+@subsection @code{distcheck-hook}
+@trindex distcheck-hook
+
+If the @code{distcheck-hook} rule is defined in your top-level
+@file{Makefile.am}, then it will be invoked by @code{distcheck} after
+the new distribution has been unpacked, but before the unpacked copy
+is configured and built.  Your @code{distcheck-hook} can do almost
+anything, though as always caution is advised.  Generally this hook is
+used to check for potential distribution errors not caught by the
+standard mechanism.
+
+@code{distcheck-hook}, as well as @code{AM_DISTCHECK_CONFIGURE_FLAGS}
+and @code{DISTCHECK_CONFIGURE_FLAGS}, are not honored in a subpackage
+@file{Makefile.am}, but the flags from
+@code{AM_DISTCHECK_CONFIGURE_FLAGS} and
+@code{DISTCHECK_CONFIGURE_FLAGS} are passed down to the
+@command{configure} script of the subpackage.
 
+@node dvi and distcheck
+@subsection @code{dvi} and @code{distcheck}
 @trindex dvi
-@subheading dvi and distcheck
-@cindex @code{eps} images
+
 Ordinarily, @command{make distcheck} runs @command{make dvi}.  It does
 nothing if the distribution contains no Texinfo sources.  If the
 distribution does contain a Texinfo manual, by default the @code{dvi}
 target will run @TeX{} to make sure it can be successfully processed
 (@pxref{Texinfo}).
 
+@vindex AM_DISTCHECK_DVI_TARGET
+@cindex @code{eps} images, and @code{distcheck}
 However, you may wish to test the manual by producing @code{pdf}
 (e.g., if your manual uses images in formats other than @code{eps}),
 @code{html} (if you don't have @TeX{} at all), some other format, or
@@ -8822,41 +9127,28 @@
 To make @code{dvi} into a do-nothing target, see the example for
 @code{EMPTY_AUTOMAKE_TARGETS} in @ref{Third-Party Makefiles}.
 
-@trindex distcheck-hook
-@subheading distcheck-hook
-If the @code{distcheck-hook} rule is defined in your top-level
-@file{Makefile.am}, then it will be invoked by @code{distcheck} after
-the new distribution has been unpacked, but before the unpacked copy
-is configured and built.  Your @code{distcheck-hook} can do almost
-anything, though as always caution is advised.  Generally this hook is
-used to check for potential distribution errors not caught by the
-standard mechanism.  Note that @code{distcheck-hook} as well as
-@code{AM_DISTCHECK_CONFIGURE_FLAGS} and @code{DISTCHECK_CONFIGURE_FLAGS}
-are not honored in a subpackage @file{Makefile.am}, but the flags from
-@code{AM_DISTCHECK_CONFIGURE_FLAGS} and @code{DISTCHECK_CONFIGURE_FLAGS}
-are passed down to the @command{configure} script of the subpackage.
-
+@node distcleancheck
+@subsection @code{distcleancheck}
 @cindex @samp{make distcleancheck}
 @trindex distcleancheck
 @vindex DISTCLEANFILES
 @vindex distcleancheck_listfiles
 
-@subheading distcleancheck
-Speaking of potential distribution errors, @code{distcheck} also
-ensures that the @code{distclean} rule actually removes all built
-files.  This is done by running @samp{make distcleancheck} at the end of
-the @code{VPATH} build.  By default, @code{distcleancheck} will run
-@code{distclean} and then make sure the build tree has been emptied by
-running @samp{$(distcleancheck_listfiles)}.  Usually this check will
-find generated files that you forgot to add to the @code{DISTCLEANFILES}
+@code{distcheck} ensures that the @code{distclean} rule actually
+removes all built files.  This is done by running @samp{make
+distcleancheck} at the end of the @code{VPATH} build.  By default,
+@code{distcleancheck} will run @code{distclean} and then make sure the
+build tree has been emptied by running the value of the variable
+@samp{$(distcleancheck_listfiles)}.  Often this check will find
+generated files that you forgot to add to the @code{DISTCLEANFILES}
 variable (@pxref{Clean}).
 
 The @code{distcleancheck} behavior should be OK for most packages,
 otherwise you have the possibility to override the definition of
 either the @code{distcleancheck} rule, or the
 @samp{$(distcleancheck_listfiles)} variable.  For instance, to disable
-@code{distcleancheck} completely, add the following rule to your
-top-level @file{Makefile.am}:
+@code{distcleancheck} completely (not recommended), add the following
+rule to your top-level @file{Makefile.am}:
 
 @example
 distcleancheck:
@@ -8864,49 +9156,222 @@
 @end example
 
 If you want @code{distcleancheck} to ignore built files that have not
-been cleaned because they are also part of the distribution, add the
-following definition instead:
+been cleaned because they are also part of the distribution, make the
+following definition:
 
-@c Keep in sync with distcleancheck.sh
+@c Keep in sync with t/distcleancheck.sh.
 @example
 distcleancheck_listfiles = \
   find . -type f -exec sh -c 'test -f $(srcdir)/$$1 || echo $$1' \
        sh '@{@}' ';'
 @end example
 
-The above definition is not the default because it's usually an error if
-your Makefiles cause some distributed files to be rebuilt when the user
-builds the package.  (Think about the user missing the tool required to
-build the file; or if the required tool is built by your package,
-consider the cross-compilation case where it can't be run.)  There is
-an entry in the FAQ about this (@pxref{Errors with distclean}); make
-sure you read it before playing with @code{distcleancheck_listfiles}.
+The above definition is not the default because it's usually an error
+if your Makefiles cause some distributed files to be rebuilt when the
+user builds the package: consider the user missing the tool required
+to build the file; or if the required tool is built by your package,
+consider the cross-compilation case where it can't be run.
+
+Please see the (following) section @ref{Errors with distclean} before
+playing with @code{distcleancheck_listfiles}.
 
+@node distuninstallcheck
+@subsection @code{distuninstallcheck}
 @cindex @samp{make distuninstallcheck}
 @trindex distuninstallcheck
 @vindex distuninstallcheck_listfiles
 
-@subheading distuninstallcheck
 @code{distcheck} also checks that the @code{uninstall} rule works
 properly, both for ordinary and @code{DESTDIR} builds.  It does this
 by invoking @samp{make uninstall}, and then it checks the install tree
 to see if any files are left over.  This check will make sure that you
 correctly coded your @code{uninstall}-related rules.
 
-By default, the checking is done by the @code{distuninstallcheck} rule,
-and the list of files in the install tree is generated by
-@samp{$(distuninstallcheck_listfiles)} (this is a variable whose value is
-a shell command to run that prints the list of files to stdout).
+By default, the checking is done by the @code{distuninstallcheck}
+rule, and the list of files in the install tree is generated by
+@samp{$(distuninstallcheck_listfiles)}. The value of the latter
+variable is taken to be a shell command to run that prints the list of
+files to stdout.
 
 Either of these can be overridden to modify the behavior of
-@code{distcheck}.  For instance, to disable this check completely, you
-would write:
+@code{distcheck}.  For instance, to disable this check completely (not
+recommended), you would write:
 
 @example
 distuninstallcheck:
         @@:
 @end example
 
+@node Errors with distclean
+@subsection Errors with @code{distclean}
+@cindex @code{distclean}, diagnostic
+@cindex @samp{make distclean}, diagnostic
+@cindex dependencies and distributed files
+@trindex distclean
+
+As explained in the section above (@pxref{Checking the Distribution}),
+@samp{make distcheck} attempts to build and check your package for
+errors. One such error you might see is:
+
+@example
+ERROR: files left in build directory after distclean:
+@end example
+
+@noindent The file(s) left in the build directory after @samp{make distclean}
+has run are listed after this error message. This can happen in two
+ways:
+
+@itemize @bullet
+@item files that were forgotten to be distclean-ed;
+@item distributed files that are erroneously rebuilt.
+@end itemize
+
+In the first case of simple left-over files not intended to be
+distributed, the fix is to include them for cleaning (@pxref{Clean});
+this is straightforward and doesn't need more explanation.
+
+@cmindex help2man
+@cindex man pages, generating and distributing
+The second case, however, is not always easy to understand and fix, so
+let's proceed with an example.  Suppose our package contains a program
+for which we want to build a man page using @command{help2man}.  GNU
+@command{help2man} produces simple manual pages from the
+@option{--help} and @option{--version} output of other commands
+(@pxref{,,,help2man, The Help2man Manual}).  Because we don't want to
+force our users to install @command{help2man}, we distribute the
+generated man page using the following setup.
+
+@example
+# This Makefile.am is bogus.
+bin_PROGRAMS = foo
+foo_SOURCES = foo.c
+dist_man_MANS = foo.1
+
+foo.1: foo$(EXEEXT)
+        help2man --output=foo.1 ./foo$(EXEEXT)
+@end example
+
+This will effectively distribute the man page.  However,
+@samp{make distcheck} will fail with:
+
+@example
+ERROR: files left in build directory after distclean:
+./foo.1
+@end example
+
+Why was @file{foo.1} rebuilt?  Because although distributed,
+@file{foo.1} depends on a non-distributed built file:
+@file{foo$(EXEEXT)}.  @file{foo$(EXEEXT)} is built by the user, so it
+will always appear to be newer than the distributed @file{foo.1}.
+
+In other words, @samp{make distcheck} caught an inconsistency in our
+package.  Our intent was to distribute @file{foo.1} so users do not
+need to install @command{help2man}, but since this rule causes this
+file to be always rebuilt, users @emph{do} need @command{help2man}.
+Either we should ensure that @file{foo.1} is not rebuilt by users, or
+there is no point in distributing @file{foo.1}.
+
+More generally, the rule is that distributed files should never depend
+on non-distributed built files.  If you distribute something
+generated, distribute all its sources.
+
+One way to fix the above example, while still distributing
+@file{foo.1}, is to not depend on @file{foo$(EXEEXT)}, but instead on
+relevant source files.  For instance, assuming @command{foo --version}
+and @command{foo --help} do not change unless @file{foo.c} or
+@file{configure.ac} change, we could write the following
+@file{Makefile.am}:
+
+@example
+bin_PROGRAMS = foo
+foo_SOURCES = foo.c
+dist_man_MANS = foo.1
+
+foo.1: foo.c $(top_srcdir)/configure.ac
+        $(MAKE) $(AM_MAKEFLAGS) foo$(EXEEXT)
+        help2man --output=foo.1 ./foo$(EXEEXT)
+@end example
+
+This way, @file{foo.1} will not get rebuilt every time
+@file{foo$(EXEEXT)} changes.  The @command{make} call makes sure
+@file{foo$(EXEEXT)} is up-to-date before @command{help2man}.
+
+Another step towards ensuring this would be to use separate
+directories for binaries and man pages, and set @code{SUBDIRS} so that
+binaries are built before man pages.  Unfortunately, this alone is, in
+general, not sufficient. In order to avoid to avoid concurrency bugs,
+it may be necessary to include wrappers; this is done by GNU Autoconf,
+as mentioned below.
+
+We could also decide not to distribute @file{foo.1}.  In this case
+it's fine to have @file{foo.1} dependent upon @file{foo$(EXEEXT)},
+since both will have to be rebuilt.  However, it might be impossible
+to build the package in a cross-compilation, because building
+@file{foo.1} involves an @emph{execution} of @file{foo$(EXEEXT)}.  The
+exception would be if @file{foo} is a platform-independent script,
+such as @command{help2man}.
+
+Another context where such errors are common is when distributed files
+are built by tools that are built by the package.  The pattern is
+similar:
+
+@example
+distributed-file: built-tools distributed-sources
+        build-command
+@end example
+
+@noindent
+should be changed to
+
+@example
+distributed-file: distributed-sources
+        $(MAKE) $(AM_MAKEFLAGS) built-tools
+        build-command
+@end example
+
+@noindent
+or you could choose not to distribute @file{distributed-file}, if
+cross-compilation does not matter.
+
+The points made through these examples are worth summarizing:
+
+@cartouche
+@itemize
+@item Distributed files should never depend upon non-distributed built files.
+
+@item Distributed files should be distributed with all their dependencies.
+
+@item If a file is @emph{intended} to be rebuilt by users, then there
+is no point in distributing it.
+@end itemize
+@end cartouche
+
+Real-world examples for @code{help2man}:
+
+@itemize
+@item
+Autoconf takes the approach described above, including man pages in
+its releases. A wrapper for each script is needed to avoid concurrency
+problems.  See its source file @code{autoconf/man/local.mk}, which has
+a good discussion of the necessary additional details.
+
+@item
+Automake itself takes another approach: it does @emph{not} include man
+pages in distributions; thus, every user generates them when building
+from the release tarballs.  This is ok (only) because Automake also
+includes a copy of the @command{help2man} script, which is plausible
+because @command{help2man} is small, self-contained, and
+platform-independent.  See the source file
+@code{automake/doc/local.mk}.
+@end itemize
+
+@vrindex distcleancheck_listfiles
+If you're desperate, it's possible to disable this check completely by
+setting @code{distcleancheck_listfiles} (@pxref{distcleancheck}).
+Make sure you understand the reason why @samp{make distcheck}
+complains first.  @code{distcleancheck_listfiles} is a way to
+@emph{hide} errors, not to fix them.  You can always do better.
+
 @node The Types of Distributions
 @section The Types of Distributions
 
@@ -8918,11 +9383,14 @@
 @trindex dist-gzip
 @cmindex gzip
 @vindex GZIP_ENV
+@c See https://bugs.gnu.org/68151 about using -9 instead of --best.
 Generate a @samp{gzip} tar archive of the distribution.  This is the
 only format enabled by default.  By default, this rule makes
-@command{gzip} use a compression option of @option{--best}.  To make
+@command{gzip} use a compression option of @option{-9} (more widely
+supported than @option{--best}).  To make
 it use a different one, set the @env{GZIP_ENV} environment variable.
-For example, @samp{make dist-gzip GZIP_ENV=-7}.
+For example, @samp{make dist-gzip GZIP_ENV=-7}. @env{GZIP_ENV} is not
+used when decompressing.
 
 @item @code{dist-bzip2}
 @trindex dist-bzip2
@@ -9056,8 +9524,8 @@
 @cindex test pass
 @cindex test failure
 A test is said to @emph{pass} when it can determine that the condition or
-behaviour it means to verify holds, and is said to @emph{fail} when it can
-determine that such condition of behaviour does @emph{not} hold.
+behavior it means to verify holds, and is said to @emph{fail} when it can
+determine that such condition of behavior does @emph{not} hold.
 
 @cindex test skip
 Sometimes, tests can rely on non-portable tools or prerequisites, or
@@ -9089,7 +9557,7 @@
 @cindex Distinction between errors and failures in testsuites
 Many testing environments and frameworks distinguish between test failures
 and hard errors.  As we've seen, a test failure happens when some invariant
-or expected behaviour of the software under test is not met.  A @emph{hard
+or expected behavior of the software under test is not met.  A @emph{hard
 error} happens when e.g., the set-up of a test case scenario fails, or when
 some other unexpected or highly undesirable condition is encountered (for
 example, the program under test experiences a segmentation fault).
@@ -9328,7 +9796,7 @@
 @cindex @option{serial-tests}, Using
 
 First, note that today the use of this harness is strongly discouraged in
-favour of the parallel test harness (@pxref{Parallel Test Harness}).
+favor of the parallel test harness (@pxref{Parallel Test Harness}).
 Still, there are a @emph{few} situations when the advantages offered by
 the parallel harness are irrelevant, and when test concurrency can
 even cause tricky problems.  In those cases, it might make sense to
@@ -9368,14 +9836,13 @@
 @node Parallel Test Harness
 @subsection Parallel Test Harness
 
-By default, Automake generated a parallel (concurrent) test harness.  It
+By default, Automake generates a parallel (concurrent) test harness.  It
 features automatic collection of the test scripts output in @file{.log}
 files, concurrent execution of tests with @code{make -j}, specification
 of inter-test dependencies, lazy reruns of tests that have not completed
 in a prior run, and hard errors for exceptional failures.
 
 @anchor{Basics of test metadata}
-@vindex TEST_SUITE_LOG
 @vindex TESTS
 @cindex @file{.log} files
 @cindex @file{.trs} files
@@ -9394,10 +9861,15 @@
 contain, among the other things, the results of the test cases run by
 the script.
 
+@vindex TEST_SUITE_LOG
+@vindex IGNORE_SKIPPED_LOGS
 The parallel test harness will also create a summary log file,
 @code{TEST_SUITE_LOG}, which defaults to @file{test-suite.log} and requires
 a @file{.log} suffix.  This file depends upon all the @file{.log} and
 @file{.trs} files created for the test scripts listed in @code{TESTS}.
+It contains the output of all tests that failed, encountered a hard error,
+succeeded unexpectedly, or---unless the variable @code{IGNORE_SKIPPED_LOGS}
+is set to a non-empty value---were skipped.
 
 @vindex VERBOSE
 As with the serial harness above, by default one status line is printed
@@ -9753,37 +10225,47 @@
 @subsubsection Command-line arguments for test drivers
 
 A custom driver can rely on various command-line options and arguments
-being passed to it automatically by the Automake-generated test harness.
-It is @emph{mandatory} that it understands all of them (even if the exact
-interpretation of the associated semantics can legitimately change
-between a test driver and another, and even be a no-op in some drivers).
+being passed to it automatically by the Automake-generated test
+harness.  It is @emph{mandatory} that it understands all of them (even
+if the exact interpretation of the associated semantics can
+legitimately change between a test driver and another, and even be a
+no-op in some drivers).  Options are separated from their arguments by
+whitespace.@footnote{Regrettably, older versions of this manual stated
+that option arguments should be joined to their options with a
+@code{=} character, rather than passed as in the following argument
+word as shown here.  The syntax with @code{=} has never been accepted
+by the test drivers supplied with Automake, and has never been
+produced by @file{Makefile}s generated by Automake.}
 
 @noindent
 Here is the list of options:
 
 @table @option
-@item --test-name=@var{NAME}
+@item --test-name @var{NAME}
 The name of the test, with VPATH prefix (if any) removed.  This can have a
 suffix and a directory component (as in e.g., @file{sub/foo.test}), and is
 mostly meant to be used in console reports about testsuite advancements and
 results (@pxref{Testsuite progress output}).
-@item --log-file=@file{@var{PATH}.log}
+@item --log-file @file{@var{PATH}.log}
 The @file{.log} file the test driver must create (@pxref{Basics of
 test metadata}).  If it has a directory component (as in e.g.,
 @file{sub/foo.log}), the test harness will ensure that such directory
 exists @emph{before} the test driver is called.
-@item --trs-file=@file{@var{PATH}.trs}
+@item --trs-file @file{@var{PATH}.trs}
 The @file{.trs} file the test driver must create (@pxref{Basics of
 test metadata}).  If it has a directory component (as in e.g.,
 @file{sub/foo.trs}), the test harness will ensure that such directory
 exists @emph{before} the test driver is called.
-@item --color-tests=@{yes|no@}
+@item --color-tests @{yes|no@}
 Whether the console output should be colorized or not (@pxref{Simple
 tests and color-tests}, to learn when this option gets activated and
 when it doesn't).
-@item --expect-failure=@{yes|no@}
+@item --collect-skipped-logs @{yes|no@}
+Whether to include the logs of skipped tests in the global
+@file{test-suite.log} file.
+@item --expect-failure @{yes|no@}
 Whether the tested program is expected to fail.
-@item --enable-hard-errors=@{yes|no@}
+@item --enable-hard-errors @{yes|no@}
 Whether ``hard errors'' in the tested program should be treated differently
 from normal failures or not (the default should be @code{yes}).  The exact
 meaning of ``hard error'' is highly dependent from the test protocols or
@@ -9797,12 +10279,12 @@
 be run, and all the following ones are command-line options and arguments
 for this program.
 
-Note that the exact semantics attached to the @option{--color-tests},
-@option{--expect-failure} and @option{--enable-hard-errors} options are
-left up to the individual test drivers.  Still, having a behaviour
-compatible or at least similar to that provided by the default driver
-is advised, as that would offer a better consistency and a more pleasant
-user experience.
+Exact semantics attached to the @option{--color-tests},
+@option{--collect-skipped-logs}, @option{--expect-failure}, and
+@option{--enable-hard-errors} options are left up to the individual
+test drivers.  Still, having a behavior compatible or at least similar
+to that provided by the default driver is advised, as that results
+in better consistency and thus a more pleasant user experience.
 
 @node Log files generation and test results recording
 @subsubsection Log files generation and test results recording
@@ -9820,7 +10302,7 @@
 of custom reStructuredText fields.  This metadata is expected to be
 employed in various ways by the parallel test harness; for example, to
 count the test results when printing the testsuite summary, or to decide
-which tests to re-run upon @command{make recheck}.  Unrecognized metadata
+which tests to rerun upon @command{make recheck}.  Unrecognized metadata
 in a @file{.trs} file is currently ignored by the harness, but this might
 change in the future. The list of currently recognized metadata follows.
 
@@ -9854,7 +10336,7 @@
 If this field is present and defined to @code{no}, then the corresponding
 test script will @emph{not} be run upon a @command{make recheck}.  What
 happens when two or more @code{:recheck:} fields are present in the same
-@file{.trs} file is undefined behaviour.
+@file{.trs} file is undefined behavior.
 
 @c Keep in sync with 'test-metadata-global-log.sh'.
 @item @code{:copy-in-global-log:}
@@ -9866,7 +10348,7 @@
 it can be useful in debugging and analysis of bug report, it can also be
 just a waste of space in normal situations, e.g., when a test script is
 successful.  What happens when two or more @code{:copy-in-global-log:}
-fields are present in the same @file{.trs} file is undefined behaviour.
+fields are present in the same @file{.trs} file is undefined behavior.
 
 @c Keep in sync with 'test-metadata-global-result.sh'.
 @item @code{:test-global-result:}
@@ -9880,7 +10362,7 @@
 a @code{PASS/SKIP} value for this field, while a test script which runs
 19 successful tests and one failed test could have an @code{ALMOST
 PASSED} value.  What happens when two or more @code{:test-global-result:}
-fields are present in the same @file{.trs} file is undefined behaviour.
+fields are present in the same @file{.trs} file is undefined behavior.
 @end table
 
 @noindent
@@ -9898,7 +10380,7 @@
 @end example
 
 @noindent
-Then the corresponding test script will be re-run by @command{make check},
+Then the corresponding test script will be rerun by @command{make check},
 will contribute with @emph{five} test results to the testsuite summary
 (three of these tests being successful, one failed, and one skipped), and
 the content of the corresponding @file{.log} file will @emph{not} be
@@ -9933,7 +10415,7 @@
 @menu
 * Introduction to TAP::
 * Use TAP with the Automake test harness::
-* Incompatibilities with other TAP parsers and drivers::
+* Incompatibility with other TAP parsers and drivers::
 * Links and external resources on TAP::
 @end menu
 
@@ -10009,7 +10491,7 @@
 looks like a test result.
 @item --no-merge
 Revert the effects of @option{--merge}.
-@item --diagnostic-string=@var{STRING}
+@item --diagnostic-string @var{STRING}
 Change the string that introduces TAP diagnostics from the default value
 of ``@code{#}'' to @code{@var{STRING}}.  This can be useful if your
 TAP-based test scripts produce verbose output on which they have limited
@@ -10098,11 +10580,11 @@
 exit status: 0
 @end example
 
-@node Incompatibilities with other TAP parsers and drivers
-@subsection Incompatibilities with other TAP parsers and drivers
+@node Incompatibility with other TAP parsers and drivers
+@subsection Incompatibility with other TAP parsers and drivers
 
 For implementation or historical reasons, the TAP driver and harness as
-implemented by Automake have some minor incompatibilities with the
+implemented by Automake have some minor compatibility issues with the
 mainstream versions, which you should be aware of.
 
 @itemize @bullet
@@ -10121,7 +10603,7 @@
 compliant tools like @command{prove} and @code{Test::Harness}
 @item
 And there are probably some other small and yet undiscovered
-incompatibilities, especially in corner cases or with rare usages.
+compatibility issues, especially in corner cases or with rare usages.
 @end itemize
 
 @node Links and external resources on TAP
@@ -10573,6 +11055,14 @@
 Don't require @file{texinfo.tex}, even if there are texinfo files in
 this directory.
 
+@item @option{posix}
+@cindex Option, @option{posix}
+@opindex posix
+Generate the special target @code{.POSIX} as the first non-comment
+line in the @file{Makefile.in} files.  This alters the behavior of the
+@code{make} program.  @xref{Special targets,, make, The GNU Make
+Manual}.
+
 @item @option{serial-tests}
 @cindex Option, @option{serial-tests}
 @opindex serial-tests
@@ -10873,6 +11363,14 @@
 @code{SUFFIXES} go at the start of the generated suffixes list, followed
 by Automake generated suffixes not already in the list.
 
+@c https://bugs.gnu.org/64743.
+@cindex built-in suffix and pattern rules, disabled
+@cindex suffix rules of Make, disabled
+@cindex pattern rules of GNU Make, disabled
+Automake disables the Make program's built-in rules with a
+@code{.SUFFIXES:} rule, and then adds whatever suffixes are
+necessary.  Automake also disables GNU Make's built-in pattern rules.
+
 @node Include
 @chapter Include
 
@@ -10880,7 +11378,7 @@
 @cindex Including @file{Makefile} fragment
 @cindex @file{Makefile} fragment, including
 
-Automake supports an @code{include} directive that  can be used to
+Automake supports an @code{include} directive that can be used to
 include other @file{Makefile} fragments when @command{automake} is run.
 Note that these fragments are read and interpreted by @command{automake},
 not by @command{make}.  As with conditionals, @command{make} has no idea that
@@ -10900,7 +11398,7 @@
 Note that if a fragment is included inside a conditional, then the
 condition applies to the entire contents of that fragment.
 
-Makefile fragments included this way are always distributed because
+@file{Makefile} fragments included this way are always distributed because
 they are needed to rebuild @file{Makefile.in}.
 
 Inside a fragment, the construct @code{%reldir%} is replaced with the
@@ -10911,12 +11409,20 @@
 is a synonym for @code{%canon_reldir%}.
 
 A special feature is that if the fragment is in the same directory as
-the base @file{Makefile.am} (i.e., @code{%reldir%} is @code{.}), then
-@code{%reldir%} and @code{%canon_reldir%} will expand to the empty
-string as well as eat, if present, a following slash or underscore
-respectively.
+the base @file{Makefile.am} (i.e., @code{%reldir%} is @code{.}), then:
+
+@table @code
+@item %reldir%
+together with a following slash expands to the empty string, otherwise
+it expands to a dot;
+
+@item %canon_reldir%
+together with a following underscore expands to the empty string, otherwise
+it expands to an underscore.
+
+@end table
 
-Thus, a makefile fragment might look like this:
+Thus, a @file{Makefile} fragment might look like this:
 
 @example
 bin_PROGRAMS += %reldir%/mumble
@@ -10965,6 +11471,16 @@
 time @command{configure} is run.  If @code{AM_CONDITIONAL} is run
 conditionally (e.g., in a shell @code{if} statement), then the result
 will confuse @command{automake}.
+
+For portability, it is best to use shell operators @code{&&} and
+@code{||} and parentheses, when constructing a compound
+@var{condition} using the @command{test} command, and not the
+@code{-a} and @code{-o} options and parentheses as options to
+@command{test}, all of which have been marked obsolescent by POSIX
+(@url{https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html#tag_20_128_161}).
+The name @code{test} is also more portable than @code{}.
+@xref{Limitations of Builtins, ,, autoconf, The Autoconf Manual}.
+
 @end defmac
 
 @cindex @option{--enable-debug}, example
@@ -11041,7 +11557,7 @@
 files only for the given condition.
 @end defmac
 
-@code{AM_COND_IF} macros may be nested when m4 quotation is used
+@code{AM_COND_IF} macros may be nested when M4 quotation is used
 properly (@pxref{M4 Quotation, ,, autoconf, The Autoconf Manual}).
 
 @cindex Example conditional @code{AC_CONFIG_FILES}
@@ -11112,16 +11628,17 @@
 * Make verbosity::              Make is verbose by default
 * Tricks For Silencing Make::   Standard and generic ways to silence make
 * Automake Silent Rules::       How Automake can help in silencing make
+* Unsilencing Automake::        Showing commands.
 @end menu
 
 @node Make verbosity
 @section Make is verbose by default
 
 Normally, when executing the set of rules associated with a target,
-@command{make} prints each rule before it is executed.  This behaviour,
-while having been in place for a long time, and being even mandated by
-the POSIX standard, starkly violates the ``silence is golden'' UNIX
-principle@footnote{See also
+@command{make} prints each rule before it is executed.  This behavior,
+despite having been in place since the beginning of @command{make},
+and being mandated by the POSIX standard, starkly violates the
+``silence is golden'' UNIX principle@footnote{See also
 @uref{http://catb.org/~esr/writings/taoup/html/ch11s09.html}.}:
 
 @quotation
@@ -11130,24 +11647,28 @@
 with a minimum of fuss and bother.  Silence is golden.
 @end quotation
 
-In fact, while such verbosity of @command{make} can theoretically be
-useful to track bugs and understand reasons of failures right away, it
-can also hide warning and error messages from @command{make}-invoked
-tools, drowning them in a flood of uninteresting and seldom useful
-messages, and thus allowing them to go easily undetected.
+The traditional verbosity of @command{make} is understandable, as it
+is useful, often necessary, in order to understand reasons of
+failures. However, it can also hide warning and error messages from
+@command{make}-invoked tools, drowning them in uninteresting and
+seldom useful messages, and thus allowing them to easily go
+undetected.
 
-This problem can be very annoying, especially for developers, who usually
+This can be quite problematic, especially for developers, who usually
 know quite well what's going on behind the scenes, and for whom the
-verbose output from @command{make} ends up being mostly noise that hampers
-the easy detection of potentially important warning messages.
+verbose output from @command{make} ends up being mostly noise that
+hampers the easy detection of potentially important warning messages.
+
+So Automake provides some support for silencing @command{make}.
 
 @node Tricks For Silencing Make
 @section Standard and generic ways to silence Make
 
-Here we describe some common idioms/tricks to obtain a quieter make
-output, with their relative advantages and drawbacks.  In the next
-section (@ref{Automake Silent Rules}) we'll see how Automake can help
-in this respect, providing more elaborate and flexible idioms.
+Here we describe some common idioms/tricks to obtain a quieter
+@command{make} output, with their relative advantages and drawbacks.
+In the next section (@ref{Automake Silent Rules}) we'll see how
+Automake can help in this respect, providing more elaborate and
+flexible idioms.
 
 @itemize @bullet
 
@@ -11159,13 +11680,14 @@
 The @option{-s} flag is mandated by POSIX, universally supported, and
 its purpose and function are easy to understand.
 
-But it also has its serious limitations too.  First of all, it embodies
-an ``all or nothing'' strategy, i.e., either everything is silenced, or
-nothing is; this lack of granularity can sometimes be a fatal flaw.
-Moreover, when the @option{-s} flag is used, the @command{make} output
-might turn out to be too terse; in case of errors, the user won't
-be able to easily see what rule or command have caused them, or even,
-in case of tools with poor error reporting, what the errors were!
+But it also has serious limitations.  First of all, it embodies an
+``all or nothing'' strategy, i.e., either everything is silenced, or
+nothing is; in practice, this lack of granularity makes it unsuitable
+as a general solution.  When the @option{-s} flag is used, the
+@command{make} output might turn out to be too terse; in case of
+errors, the user won't be able to easily see what rule or command have
+caused them, or even, in case of tools with poor error reporting, what
+the errors were.
 
 @item @command{make >/dev/null || make}
 
@@ -11175,8 +11697,8 @@
 an easy determination of the error location and causes.
 
 However, calling @command{make} two times in a row might hide errors
-(especially intermittent ones), or subtly change the expected semantics
-of the @command{make} calls --- these things can clearly make
+(especially intermittent ones), or subtly change the expected
+semantics of the @command{make} calls---these things can clearly make
 debugging and error assessment very difficult.
 
 @item @command{make --no-print-directory}
@@ -11184,13 +11706,13 @@
 This is GNU @command{make} specific.  When called with the
 @option{--no-print-directory} option, GNU @command{make} will disable
 printing of the working directory by invoked sub-@command{make}s (the
-well-known ``@i{Entering/Leaving directory ...}'' messages).  This helps
-to decrease the verbosity of the output, but experience has shown that
-it can also often render debugging considerably harder in projects using
-deeply-nested @command{make} recursion.
+well-known ``@i{Entering/Leaving directory @dots{}}'' messages).  This
+helps to decrease the verbosity of the output, but experience has
+shown that it can also often render debugging considerably harder in
+projects using deeply-nested @command{make} recursion.
 
-As an aside, notice that the @option{--no-print-directory} option is
-automatically activated if the @option{-s} flag is used.
+As an aside, the @option{--no-print-directory} option is automatically
+activated if the @option{-s} flag is used.
 
 @c TODO: Other tricks?
 @c TODO: Maybe speak about the @code{.SILENT} target?
@@ -11245,8 +11767,8 @@
 test -z "foo" || rm -f foo
 rm -f *.o
 
-@i{Silent rules enabled: the output is minimal but informative.  In
-particular, the warnings from the compiler stick out very clearly.}
+@i{Silent rules enabled: the output is minimal but informative.
+The warnings from the compiler stick out very clearly.}
 % @kbd{make V=0 CFLAGS=-Wall}
   CC     main.o
 main.c: In function ‘main’:
@@ -11258,8 +11780,8 @@
 @end example
 
 @cindex silent rules and libtool
-Also, in projects using @command{libtool}, the use of silent rules can
-automatically enable the @command{libtool}'s @option{--silent} option:
+Also, in projects using Libtool, the use of silent rules can
+automatically enable @command{libtool}'s @option{--silent} option:
 
 @example
 % @kbd{cat Makefile.am}
@@ -11294,43 +11816,48 @@
 Passing @option{--enable-silent-rules} to @command{configure} will cause
 build rules to be less verbose; the option @option{--disable-silent-rules}
 will cause normal verbose output.
+
 @item
 @vindex @code{V}
 At @command{make} run time, the default chosen at @command{configure}
 time may be overridden: @code{make V=1} will produce verbose output,
 @code{make V=0} less verbose output.
+
+Unfortunately, if @code{V} is assigned a value other than 0 or 1,
+errors will result.  This is problematic when a third-party program or
+library is built in the same tree and also uses the make variable
+@code{V}, with different values.  The best workaround is probably to
+set @code{AM_V_P=true} (or similar), either on the make command line
+or in the @code{V}-using project's @code{Makefile.am}.  (For more
+discussion, see @url{https://bugs.gnu.org/20077}.)
 @end itemize
 
 @cindex default verbosity for silent rules
-Note that silent rules are @emph{disabled} by default; the user must
-enable them explicitly at either @command{configure} run time or at
-@command{make} run time.  We think that this is a good policy, since
-it provides the casual user with enough information to prepare a good
-bug report in case anything breaks.
-
-Still, notwithstanding the rationales above, developers who wants to
-make silent rules enabled by default in their own packages can do so
-by calling @code{AM_SILENT_RULES(yes)} in @file{configure.ac}.
+Silent rules are @emph{disabled} by default; the user must enable them
+explicitly at either @command{configure} run time or at @command{make}
+run time.  We think that this is a good policy, since it provides the
+casual user with enough information to prepare a good bug report in
+case anything breaks.
+
+Notwithstanding those rationales, developers who want to enable silent
+rules by default in their own packages can do so by calling
+@code{AM_SILENT_RULES(yes)} in @file{configure.ac}.
 
 @c Keep in sync with silent-configsite.sh
-Users who prefer to have silent rules enabled by default can edit their
-@file{config.site} file to make the variable @code{enable_silent_rules}
-default to @samp{yes}.  This should still allow disabling silent rules
-at @command{configure} time and at @command{make} time.
-
-@c FIXME: is there a need to specify this explicitly?
-For portability to different @command{make} implementations, package authors
-are advised to not set the variable @code{V} inside the @file{Makefile.am}
-file, to allow the user to override the value for subdirectories as well.
+Analogously, users who prefer to have silent rules enabled by default
+for everything on their system can edit their @file{config.site} file
+to make the variable @code{enable_silent_rules} default to @samp{yes}.
+This still allows disabling silent rules at @command{configure} time
+and at @command{make} time.
 
-To work at its best, the current implementation of this feature normally
-uses nested variable expansion @samp{$(@var{var1}$(V))}, a @file{Makefile}
+To work best, the current implementation of this feature normally uses
+nested variable expansion @samp{$(@var{var1}$(V))}, a @file{Makefile}
 feature that is not required by POSIX 2008 but is widely supported in
-practice.  On the rare @command{make} implementations that do not support
-nested variable expansion, whether rules are silent is always determined at
-configure time, and cannot be overridden at make time.  Future versions of
-POSIX are likely to require nested variable expansion, so this minor
-limitation should go away with time.
+practice.  On the rare @command{make} implementations that do not
+support nested variable expansion, whether rules are silent is always
+determined at configure time, and cannot be overridden at make time.
+Future versions of POSIX are likely to require nested variable
+expansion, so this minor limitation should go away with time.
 
 @vindex @code{AM_V_GEN}
 @vindex @code{AM_V_at}
@@ -11340,7 +11867,6 @@
 To extend the silent mode to your own rules, you have a few choices:
 
 @itemize @bullet
-
 @item
 You can use the predefined variable @code{AM_V_GEN} as a prefix to
 commands that should output a status line in silent mode, and
@@ -11352,36 +11878,81 @@
 You can silence a recipe unconditionally with @code{@@}, and then use
 the predefined variable @code{AM_V_P} to know whether make is being run
 in silent or verbose mode; adjust the verbose information your recipe
-displays accordingly:
+displays accordingly. For example:
 
-@example
+@c smallexample because text is too wide for normal example.
+@smallexample
 generate-headers:
-        @set -e; \
-        ... commands defining a shell variable '$headers' ...; \
+        @@set -e; \
+        ... commands defining shell variable '$headers' ...; \
         if $(AM_V_P); then set -x; else echo " GEN   headers"; fi; \
         rm -f $$headers && generate-header --flags $$headers
-@end example
+@end smallexample
+
+@code{AM_V_P} is (must be) always set to a simple command, not needing
+shell quoting, typically either @code{:} or @code{true} or
+@code{false}.
 
 @item
 You can add your own variables, so strings of your own choice are shown.
 The following snippet shows how you would define your own equivalent of
-@code{AM_V_GEN}:
+@code{AM_V_GEN}, say a string @samp{PKG-GEN}:
 
-@example
+@c smallexample because regular example would look weird
+@c next to the smallexample above.
+@smallexample
 pkg_verbose = $(pkg_verbose_@@AM_V@@)
 pkg_verbose_ = $(pkg_verbose_@@AM_DEFAULT_V@@)
 pkg_verbose_0 = @@echo PKG-GEN $@@;
 
 foo: foo.in
         $(pkg_verbose)cp $(srcdir)/foo.in $@@
-@end example
+@end smallexample
 
 @end itemize
 
-As a final note, observe that, even when silent rules are enabled,
-the @option{--no-print-directory} option is still required with GNU
-@command{make} if the ``@i{Entering/Leaving directory ...}'' messages
-are to be disabled.
+Even when silent rules are enabled, the @option{--no-print-directory}
+option is still required with GNU @command{make} if the
+``@i{Entering/Leaving directory @dots{}}'' messages are to be elided.
+
+@node Unsilencing Automake
+@section Unsilencing Automake
+
+@cindex unsilencing Automake
+@cindex verbose output from Automake
+
+With the @code{AM_SILENT_RULES} macro described in the previous
+section, Automake does a good job reducing @command{make} output to a
+bare minimum.  Sometimes you want to see more than that, especially
+when debugging.  Let's summarize ways to get more information out of
+Automake packages:
+
+@itemize
+@item
+Running @code{make V=1} will produce generally verbose output.
+
+@item
+Adding @code{AM_V_GEN= AM_V_at=} will unsilence more rules. Thus, in all:
+@code{make V=1 AM_V_GEN= AM_V_at=}.
+
+@c VERBOSE=1 is (highly) relevant to the Automake test suite,
+@c but not in general, so shouldn't be mentioned here. See automake/HACKING.
+@c item
+@c Adding @code{VERBOSE=1} can unsilence yet more. Thus, in all:
+@c ode{make V=1 AM_V_GEN= AM_V_at= VERBOSE=1}.
+
+@item
+Even this will not unsilence everything. To see the real truth of what
+gets executed, resort to GNU Make's debugging feature: @code{make
+--debug=p ... @var{otherargs} ...}.  This reports every command being
+run, ignoring the @code{@@} prefix on rules (which is what silences
+them).  In the case of Automake, these commands are generally complex
+shell constructs, and you'll want to track down the source files in
+Automake to actually understand them; but at least you'll have the
+text to search for.  You may wish to include other debugging options.
+@xref{Options Summary,,,make, The GNU Make Manual}.
+
+@end itemize
 
 @node Not Enough
 @chapter When Automake Isn't Enough
@@ -11680,7 +12251,7 @@
 subproject, but they are required for the whole package to work.  It's
 OK to have a rule that does nothing, so if you are integrating a
 third-party project with no documentation or tag support, you could
-simply augment its @file{Makefile} as follows:
+augment its @file{Makefile} as follows:
 
 @vindex EMPTY_AUTOMAKE_TARGETS
 @cindex Automake targets, no-op
@@ -11711,7 +12282,7 @@
 and @samp{@@top_builddir@@} are defined by @file{configure} when it
 processes a @file{Makefile} (@pxref{Preset Output Variables, , Preset
 Output Variables, autoconf, The Autoconf Manual}); they are not
-computed by the Makefile like the aforementioned @samp{$(distdir)} and
+computed by the @file{Makefile} like the aforementioned @samp{$(distdir)} and
 @samp{$(top_distdir)} variables.
 
 It is sometimes inconvenient to modify a third-party @file{Makefile}
@@ -11776,28 +12347,27 @@
 
 Pushing this idea to the extreme, it is also possible to ignore the
 subproject build system and build everything from this proxy
-@file{Makefile.am}.  This might sound very sensible if you need VPATH
+@file{Makefile.am}.  This might well be sensible if you need VPATH
 builds but the subproject does not support them.
 
 @node Distributing
 @chapter Distributing @file{Makefile.in}s
 
 Automake places no restrictions on the distribution of the resulting
-@file{Makefile.in}s.  We still encourage software authors to
-distribute their work under terms like those of the GPL, but doing so
-is not required to use Automake.
+@file{Makefile.in}s.  We encourage software authors to distribute
+their work under terms like those of the GPL, but doing so is not
+required to use Automake.
 
 Some of the files that can be automatically installed via the
 @option{--add-missing} switch do fall under the GPL@.  However, these also
 have a special exception allowing you to distribute them with your
 package, regardless of the licensing you choose.
 
-
 @node API Versioning
 @chapter Automake API Versioning
 
 New Automake releases usually include bug fixes and new features.
-Unfortunately they may also introduce new bugs and incompatibilities.
+Unfortunately they may also introduce new bugs and incompatibility.
 This makes four reasons why a package may require a particular Automake
 version.
 
@@ -11913,7 +12483,7 @@
 
 Before upgrading to a new major release, it is a good idea to read the
 file @file{NEWS}.  This file lists all changes between releases: new
-features, obsolete constructs, known incompatibilities, and
+features, obsolete constructs, known incompatibility, and
 workarounds.
 
 @node FAQ
@@ -11923,11 +12493,10 @@
 lists.
 
 @menu
-* CVS::                         CVS and generated files
+* Version Control::             Version control and generated files
 * maintainer-mode::             missing and AM_MAINTAINER_MODE
 * Wildcards::                   Why doesn't Automake support wildcards?
 * Limitations on File Names::   Limitations on source and installed file names
-* Errors with distclean::       Files left in build directory after distclean
 * Flag Variables Ordering::     CFLAGS vs.@: AM_CFLAGS vs.@: mumble_CFLAGS
 * Renamed Objects::             Why are object files sometimes renamed?
 * Per-Object Flags::            How to simulate per-object flags?
@@ -11937,9 +12506,10 @@
 * Reporting Bugs::              Feedback on bugs and feature requests
 @end menu
 
-@node CVS
-@section CVS and generated files
+@node Version Control
+@section Version control and generated files
 
+@anchor{CVS}@c old name of node, keep for compatibility
 @subheading Background: distributed generated Files
 @cindex generated files, distributed
 @cindex rebuild rules
@@ -11951,52 +12521,47 @@
 rebuild them.  Other generated files like Lex scanners, Yacc parsers,
 or Info documentation are usually distributed on similar grounds.
 
-Automake output generates rules in @file{Makefile}s to rebuild these files.
-For instance, @command{make} will run @command{autoconf} to rebuild
-@file{configure} whenever @file{configure.ac} is changed.  This makes
-development safer by ensuring a @file{configure} is never out-of-date
-with respect to @file{configure.ac}.
+Automake output generates rules in @file{Makefile}s to rebuild these
+files.  For instance, @command{make} will run @command{autoconf} to
+rebuild @file{configure} whenever @file{configure.ac} is changed.
+This makes development safer by ensuring a @file{configure} is never
+out-of-date with respect to @file{configure.ac}.
 
 As generated files shipped in packages are up-to-date, and because
-@command{tar} preserves times-tamps, these rebuild rules are not
+@command{tar} preserves timestamps, these rebuild rules are not
 triggered when a user unpacks and builds a package.
 
-@subheading Background: CVS and Timestamps
-@cindex timestamps and CVS
-@cindex CVS and timestamps
-
-Unless you use CVS keywords (in which case files must be updated at
-commit time), CVS preserves timestamp during @samp{cvs commit} and
-@samp{cvs import -d} operations.
-
-When you check out a file using @samp{cvs checkout} its timestamp is
-set to that of the revision that is being checked out.
-
-However, during @command{cvs update}, files will have the date of the
-update, not the original timestamp of this revision.  This is meant to
-make sure that @command{make} notices that sources files have been updated.
+@subheading Background: Version Control and Timestamps
+@cindex timestamps and version control
+@cindex version control and timestamps
+
+Typically when you update files with version control commands, working
+files will have the timestamp of your update, not the original
+timestamp of the commit.  This is meant to make sure that
+@command{make} notices that source files have been updated.
 
 This timestamp shift is troublesome when both sources and generated
-files are kept under CVS@.  Because CVS processes files in lexical
-order, @file{configure.ac} will appear newer than @file{configure}
-after a @command{cvs update} that updates both files, even if
-@file{configure} was newer than @file{configure.ac} when it was
-checked in.  Calling @command{make} will then trigger a spurious rebuild
-of @file{configure}.
-
-@subheading Living with CVS in Autoconfiscated Projects
-@cindex CVS and generated files
-@cindex generated files and CVS
-
-There are basically two clans amongst maintainers: those who keep all
-distributed files under CVS, including generated files, and those who
-keep generated files @emph{out} of CVS.
+files are kept under version control.  Because version control
+commands often process files in lexical order, @file{configure.ac}
+will appear newer than @file{configure} after a version control
+command that updates both files, even if @file{configure} was newer
+than @file{configure.ac} when it was committed.  Calling
+@command{make} will then trigger a spurious rebuild of
+@file{configure}.
+
+@subheading Living with Version Control in Autoconfiscated Projects
+@cindex version control and generated files
+@cindex generated files and version control
+
+There are basically two clans among maintainers: those who keep all
+distributed files under version control, including generated files, and
+those who keep generated files @emph{out} of version control.
 
-@subsubheading All Files in CVS
+@subsubheading All Files under Version Control
 
 @itemize @bullet
 @item
-The CVS repository contains all distributed files so you know exactly
+The repository contains all distributed files so you know exactly
 what is distributed, and you can check out any prior version entirely.
 
 @item
@@ -12009,8 +12574,7 @@
 works just like a released tarball.
 
 @item
-If users use @command{cvs update} to update their copy, instead of
-@command{cvs checkout} to fetch a fresh one, timestamps will be
+If users use version control to update their copy, timestamps will likely be
 inaccurate.  Some rebuild rules will be triggered and attempt to
 run developer tools such as @command{autoconf} or @command{automake}.
 
@@ -12021,58 +12585,54 @@
 ``command not found'' error, or (worse) some obscure message from some
 older version of the required tool they happen to have installed.
 
-Maintainers interested in keeping their package buildable from a CVS
+Maintainers interested in keeping their package buildable from a
 checkout even for those users that lack maintainer-specific tools might
 want to provide a helper script (or to enhance their existing bootstrap
-script) to fix the timestamps after a
-@command{cvs update} or a @command{git checkout}, to prevent spurious
+script) to fix the timestamps after a checkout, to prevent spurious
 rebuilds.  In case of a project committing the Autotools-generated
 files, as well as the generated @file{.info} files, such a script might
 look something like this:
 
 @smallexample
 #!/bin/sh
-# fix-timestamp.sh: prevents useless rebuilds after "cvs update"
+# fix-timestamp.sh: Prevent useless rebuilds after "git pull".
 sleep 1
 # aclocal-generated aclocal.m4 depends on locally-installed
-# '.m4' macro files, as well as on 'configure.ac'
+# '.m4' macro files, as well as on 'configure.ac'.
 touch aclocal.m4
 sleep 1
-# autoconf-generated configure depends on aclocal.m4 and on
-# configure.ac
-touch configure
-# so does autoheader-generated config.h.in
-touch config.h.in
-# and all the automake-generated Makefile.in files
-touch `find . -name Makefile.in -print`
-# finally, the makeinfo-generated '.info' files depend on the
-# corresponding '.texi' files
-touch doc/*.info
+# autoconf-generated 'configure' and autoheader-generated
+# config.h.in both depend on aclocal.m4 and on configure.ac.
+touch configure config.h.in
+# Automake-generated Makefile.in files depend on Makefile.am,
+# and makeinfo-generated '.info' files depend on the
+# corresponding '.texi' files.
+touch $(git ls-files '*/Makefile.in' '*.info')
 @end smallexample
 
 @item
 In distributed development, developers are likely to have different
 versions of the maintainer tools installed.  In this case rebuilds
-triggered by timestamp lossage will lead to spurious changes
-to generated files.  There are several solutions to this:
+triggered by clock skew can lead to spurious changes to generated
+files.  There are several solutions to this:
 
 @itemize
 @item
 All developers should use the same versions, so that the rebuilt files
-are identical to files in CVS@.  (This starts to be difficult when each
-project you work on uses different versions.)
+are identical to files in the repository.  (This becomes difficult
+when different projects on which you are working use different versions.)
 @item
 Or people use a script to fix the timestamp after a checkout (the GCC
 folks have such a script).
 @item
-Or @file{configure.ac} uses @code{AM_MAINTAINER_MODE}, which will
-disable all of these rebuild rules by default.  This is further discussed
-in @ref{maintainer-mode}.
+Or @file{configure.ac} uses @code{AM_MAINTAINER_MODE}, which disables
+all of these rebuild rules by default.  This is further discussed in
+@ref{maintainer-mode}.
 @end itemize
 
 @item
 Although we focused on spurious rebuilds, the converse can also
-happen.  CVS's timestamp handling can also let you think an
+happen.  Version control timestamp handling can also let you think an
 out-of-date file is up-to-date.
 
 For instance, suppose a developer has modified @file{Makefile.am} and
@@ -12081,30 +12641,32 @@
 (without rebuilding @file{Makefile.in} to account for the change).
 
 This last change to @file{Makefile.am} makes the copy of
-@file{Makefile.in} out-of-date.  Since CVS processes files
-alphabetically, when another developer @samp{cvs update}s his or her
-tree, @file{Makefile.in} will happen to be newer than
-@file{Makefile.am}.  This other developer will not see that
-@file{Makefile.in} is out-of-date.
+@file{Makefile.in} out-of-date.  Assuming version control processes
+files alphabetically, when another developer updates their tree,
+@file{Makefile.in} will happen to be newer than @file{Makefile.am}.
+This other developer will not see that @file{Makefile.in} is
+out-of-date.
 
 @end itemize
 
-@subsubheading Generated Files out of CVS
+@subsubheading Generated Files out of Version Control
 
-One way to get CVS and @command{make} working peacefully is to never
-store generated files in CVS, i.e., do not CVS-control files that
-are @file{Makefile} targets (also called @emph{derived} files).
+One way to get version control and @command{make} working peacefully
+is to never store generated files in version control, i.e., do not
+version-control files that are @file{Makefile} targets (also called
+@emph{derived} files).
 
 This way developers are not annoyed by changes to generated files.  It
 does not matter if they all have different versions (assuming they are
 compatible, of course).  And finally, timestamps are not lost; changes
-to sources files can't be missed as in the
+to source files can't be missed as in the
 @file{Makefile.am}/@file{Makefile.in} example discussed earlier.
 
-The drawback is that the CVS repository is not an exact copy of what
-is distributed and that users now need to install various development
-tools (maybe even specific versions) before they can build a checkout.
-But, after all, CVS's job is versioning, not distribution.
+The drawback is that the repository does not contain some files that
+are is distributed, so builders now need to install various
+development tools (maybe even specific versions) before they can build
+a checkout.  But, after all, the job of version control is versioning,
+not distribution.
 
 Allowing developers to use different versions of their tools can also
 hide bugs during distributed development.  Indeed, developers will be
@@ -12116,8 +12678,8 @@
 of this tool.
 
 @subheading Third-party Files
-@cindex CVS and third-party files
-@cindex third-party files and CVS
+@cindex version control and third-party files
+@cindex third-party files and version control
 
 Another class of files not discussed here (because they do not cause
 timestamp issues) are files that are shipped with a package, but
@@ -12125,10 +12687,11 @@
 and @command{autopoint} (from Gettext) or @command{libtoolize} (from
 Libtool), will install or update files in your package.
 
-These files, whether they are kept under CVS or not, raise similar
-concerns about version mismatch between developers' tools.  The
-Gettext manual has a section about this; see @ref{Version Control Issues,,
-Integrating with Version Control Systems, gettext, GNU gettext tools}.
+These files, whether they are kept under version control or not, raise
+similar concerns about version mismatch between developers' tools.
+The Gettext manual has a section about this; see @ref{Version Control
+Issues,, Integrating with Version Control Systems, gettext, GNU
+gettext tools}.
 
 @node maintainer-mode
 @section @command{missing} and @code{AM_MAINTAINER_MODE}
@@ -12182,7 +12745,7 @@
 to @command{configure}.
 
 People use @code{AM_MAINTAINER_MODE} either because they do not want their
-users (or themselves) annoyed by timestamp lossage (@pxref{CVS}), or
+users (or themselves) annoyed by clock skew (@pxref{Version Control}), or
 because they simply can't stand the rebuild rules and prefer running
 maintainer tools explicitly.
 
@@ -12225,13 +12788,13 @@
 There are several objections to this:
 @itemize
 @item
-When using CVS (or similar) developers need to remember they have to
-run @samp{cvs add} or @samp{cvs rm} anyway.  Updating
+When using version control, developers need to remember they have to
+add or remove files from version control anyway.  Updating
 @file{Makefile.am} accordingly quickly becomes a reflex.
 
 Conversely, if your application doesn't compile
 because you forgot to add a file in @file{Makefile.am}, it will help
-you remember to @samp{cvs add} it.
+you remember to add the file to version control.
 
 @item
 Using wildcards makes it easy to distribute files by mistake.  For
@@ -12353,157 +12916,6 @@
 Nowadays it is no longer worth worrying about the 8.3 limits of
 DOS file systems.
 
-@c FIXME This should probably be moved to the "Checking the Distribution"
-@c FIXME section...
-@node Errors with distclean
-@section Errors with distclean
-@cindex @code{distclean}, diagnostic
-@cindex @samp{make distclean}, diagnostic
-@cindex dependencies and distributed files
-@trindex distclean
-
-This is a diagnostic you might encounter while running @samp{make
-distcheck}.
-
-As explained in @ref{Checking the Distribution}, @samp{make distcheck}
-attempts to build and check your package for errors like this one.
-
-@samp{make distcheck} will perform a @code{VPATH} build of your
-package (@pxref{VPATH Builds}), and then call @samp{make distclean}.
-Files left in the build directory after @samp{make distclean} has run
-are listed after this error.
-
-This diagnostic covers two kinds of errors:
-
-@itemize @bullet
-@item
-files that are forgotten by distclean;
-@item
-distributed files that are erroneously rebuilt.
-@end itemize
-
-The former left-over files are not distributed, so the fix is to mark
-them for cleaning (@pxref{Clean}); this is obvious and doesn't deserve
-more explanation.
-
-The latter bug is not always easy to understand and fix, so let's
-proceed with an example.  Suppose our package contains a program for
-which we want to build a man page using @command{help2man}.  GNU
-@command{help2man} produces simple manual pages from the @option{--help}
-and @option{--version} output of other commands (@pxref{Top, , Overview,
-help2man, The Help2man Manual}).  Because we don't want to force our
-users to install @command{help2man}, we decide to distribute the
-generated man page using the following setup.
-
-@example
-# This Makefile.am is bogus.
-bin_PROGRAMS = foo
-foo_SOURCES = foo.c
-dist_man_MANS = foo.1
-
-foo.1: foo$(EXEEXT)
-        help2man --output=foo.1 ./foo$(EXEEXT)
-@end example
-
-This will effectively distribute the man page.  However,
-@samp{make distcheck} will fail with:
-
-@example
-ERROR: files left in build directory after distclean:
-./foo.1
-@end example
-
-Why was @file{foo.1} rebuilt?  Because although distributed,
-@file{foo.1} depends on a non-distributed built file:
-@file{foo$(EXEEXT)}.  @file{foo$(EXEEXT)} is built by the user, so it
-will always appear to be newer than the distributed @file{foo.1}.
-
-@samp{make distcheck} caught an inconsistency in our package.  Our
-intent was to distribute @file{foo.1} so users do not need to install
-@command{help2man}, however since this rule causes this file to be
-always rebuilt, users @emph{do} need @command{help2man}.  Either we
-should ensure that @file{foo.1} is not rebuilt by users, or there is
-no point in distributing @file{foo.1}.
-
-More generally, the rule is that distributed files should never depend
-on non-distributed built files.  If you distribute something
-generated, distribute its sources.
-
-One way to fix the above example, while still distributing
-@file{foo.1}, is to not depend on @file{foo$(EXEEXT)}.  For instance,
-assuming @command{foo --version} and @command{foo --help} do not
-change unless @file{foo.c} or @file{configure.ac} change, we could
-write the following @file{Makefile.am}:
-
-@example
-bin_PROGRAMS = foo
-foo_SOURCES = foo.c
-dist_man_MANS = foo.1
-
-foo.1: foo.c $(top_srcdir)/configure.ac
-        $(MAKE) $(AM_MAKEFLAGS) foo$(EXEEXT)
-        help2man --output=foo.1 ./foo$(EXEEXT)
-@end example
-
-This way, @file{foo.1} will not get rebuilt every time
-@file{foo$(EXEEXT)} changes.  The @command{make} call makes sure
-@file{foo$(EXEEXT)} is up-to-date before @command{help2man}.  Another
-way to ensure this would be to use separate directories for binaries
-and man pages, and set @code{SUBDIRS} so that binaries are built
-before man pages.
-
-We could also decide not to distribute @file{foo.1}.  In
-this case it's fine to have @file{foo.1} dependent upon
-@file{foo$(EXEEXT)}, since both will have to be rebuilt.
-However, it would be impossible to build the package in a
-cross-compilation, because building @file{foo.1} involves
-an @emph{execution} of @file{foo$(EXEEXT)}.
-
-Another context where such errors are common is when distributed files
-are built by tools that are built by the package.  The pattern is
-similar:
-
-@example
-distributed-file: built-tools distributed-sources
-        build-command
-@end example
-
-@noindent
-should be changed to
-
-@example
-distributed-file: distributed-sources
-        $(MAKE) $(AM_MAKEFLAGS) built-tools
-        build-command
-@end example
-
-@noindent
-or you could choose not to distribute @file{distributed-file}, if
-cross-compilation does not matter.
-
-The points made through these examples are worth a summary:
-
-@cartouche
-@itemize
-@item
-Distributed files should never depend upon non-distributed built
-files.
-@item
-Distributed files should be distributed with all their dependencies.
-@item
-If a file is @emph{intended} to be rebuilt by users, then there is no point
-in distributing it.
-@end itemize
-@end cartouche
-
-@vrindex distcleancheck_listfiles
-For desperate cases, it's always possible to disable this check by
-setting @code{distcleancheck_listfiles} as documented in @ref{Checking
-the Distribution}.
-Make sure you do understand the reason why @samp{make distcheck}
-complains before you do this.  @code{distcleancheck_listfiles} is a
-way to @emph{hide} errors, not to fix them.  You can always do better.
-
 @node Flag Variables Ordering
 @section Flag Variables Ordering
 @cindex Ordering flag variables
@@ -12862,6 +13274,13 @@
 tool produces multiple output files.  It is not specific to Automake
 and can be used in ordinary @file{Makefile}s.
 
+First, however: GNU @command{make} is able to express rules with
+multiple output files using pattern rules (@pxref{Pattern Examples, ,
+Pattern Rule Examples, make, The GNU Make Manual}).  We do not discuss
+pattern rules here because they are not portable, but if you're able
+to assume GNU @command{make}, they are typically more convenient than
+any of the below approaches.
+
 Suppose we have a program called @command{foo} that will read one file
 called @file{data.foo} and produce two files named @file{data.c} and
 @file{data.h}.  We want to write a @file{Makefile} rule that captures
@@ -12905,36 +13324,14 @@
 (or depends upon) a phony target.
 @end itemize
 
-A solution that works with parallel @command{make} but not with
-phony dependencies is the following:
-
-@example
-data.c data.h: data.foo
-        foo data.foo
-data.h: data.c
-@end example
-
-@noindent
-The above rules are equivalent to
-
-@example
-data.c: data.foo
-        foo data.foo
-data.h: data.foo data.c
-        foo data.foo
-@end example
+Ideally, we want a scheme that will support any number of output
+files, and that works with parallel @command{make} invocations, and
+that does nothing when @samp{make -n} is run.  It is apparently not
+possible to achieve a perfect solution.  Even an acceptable solution
+for the majority of cases gets complicated, so we will take it step by
+step.
 
-@noindent
-therefore a parallel @command{make} will have to serialize the builds
-of @file{data.c} and @file{data.h}, and will detect that the second is
-no longer needed once the first is over.
-
-Using this pattern is probably enough for most cases.  However it does
-not scale easily to more output files (in this scheme all output files
-must be totally ordered by the dependency relation), so we will
-explore a more complicated solution.
-
-Another idea is to write the following:
+One idea is to write the following:
 
 @example
 # There is still a problem with this one.
@@ -12960,6 +13357,7 @@
 missing.  Here it is:
 
 @example
+# More or less works, but not easy to generalize.
 data.c: data.foo
         foo data.foo
 data.h: data.c
@@ -12971,6 +13369,7 @@
 It is tempting to use a single test as follows:
 
 @example
+# This breaks make -n.
 data.h: data.c
 ## Recover from the removal of $@@
         @@if test -f $@@; then :; else \
@@ -13003,14 +13402,14 @@
         @@test -f $@@ || $(MAKE) $(AM_MAKEFLAGS) data.c
 @end example
 
-However there are now three minor problems in this setup.  One is related
-to the timestamp ordering of @file{data.h}, @file{data.w},
-@file{data.x}, and @file{data.c}.  Another one is a race condition
-if a parallel @command{make} attempts to run multiple instances of the
-recover block at once.  Finally, the recursive rule breaks @samp{make -n}
-when run with GNU @command{make} (as well as some other @command{make}
-implementations), as it may remove @file{data.h} even when it should not
-(@pxref{MAKE Variable, , How the @code{MAKE} Variable Works, make,
+However there are now three problems in this setup.  One is related to
+the timestamp ordering of @file{data.h}, @file{data.w}, @file{data.x},
+and @file{data.c}.  A second is a race condition if a parallel
+@command{make} attempts to run multiple instances of the recover block
+at once.  Finally, the recursive rule breaks @samp{make -n} when run
+with GNU @command{make} (as well as some other @command{make}
+implementations), as it may remove @file{data.h} even when it should
+not (@pxref{MAKE Variable, , How the @code{MAKE} Variable Works, make,
 The GNU Make Manual}).
 
 Let us deal with the first problem.  @command{foo} outputs four files,
@@ -13181,13 +13580,6 @@
         fi
 @end example
 
-For completeness it should be noted that GNU @command{make} is able to
-express rules with multiple output files using pattern rules
-(@pxref{Pattern Examples, , Pattern Rule Examples, make, The GNU Make
-Manual}).  We do not discuss pattern rules here because they are not
-portable, but they can be convenient in packages that assume GNU
-@command{make}.
-
 
 @node Hard-Coded Install Paths
 @section Installing to Hard-Coded Locations
@@ -13296,7 +13688,7 @@
 computes @samp{$(lispdir)}:
 
 @example
-$EMACS -batch -Q -eval '(while load-path
+$EMACS -batch -no-site-file -eval '(while load-path
   (princ (concat (car load-path) "\n"))
   (setq load-path (cdr load-path)))' >conftest.out
 lispdir=`sed -n
@@ -13335,8 +13727,9 @@
 @itemize
 @item
 If less verbose output has been enabled in the package with the use
-of silent rules (@pxref{Automake Silent Rules}), you can use
-@code{make V=1} to see the commands being executed.
+of silent rules (@pxref{Automake Silent Rules}), you'll probably want
+undo that and see the actual commands being run: @pxref{Unsilencing
+Automake}.
 
 @item
 @code{make -n} can help show what would be done without actually doing
@@ -13349,9 +13742,9 @@
 files.@footnote{Automake's @samp{dist} and @samp{distcheck} rules had
 a bug in this regard in that they created directories even with
 @option{-n}, but this has been fixed in Automake 1.11.}  Furthermore,
-note that GNU @command{make} will update prerequisites for the
-@file{Makefile} file itself even with @option{-n} (@pxref{Remaking
-Makefiles,,, make, The GNU Make Manual}).
+GNU @command{make} will update prerequisites for the @file{Makefile}
+file itself even with @option{-n} (@pxref{Remaking Makefiles,,, make,
+The GNU Make Manual}).
 
 @item
 @code{make SHELL="/bin/bash -vx"} can help debug complex rules.
@@ -13447,14 +13840,13 @@
 
 @printindex cp
 
-
 @bye
 
 @c  LocalWords:  texinfo setfilename settitle setchapternewpage texi direntry
 @c  LocalWords:  dircategory in's aclocal ifinfo titlepage Tromey vskip pt sp
 @c  LocalWords:  filll defcodeindex ov cv op tr syncodeindex fn cp vr ifnottex
 @c  LocalWords:  dir Automake's ac Dist Gnits gnits dfn Autoconf's pxref
-@c  LocalWords:  cindex Autoconf autoconf perl samp cvs dist trindex SUBST foo
+@c  LocalWords:  cindex Autoconf autoconf perl samp dist trindex SUBST foo
 @c  LocalWords:  xs emph FIXME ref vindex pkglibdir pkgincludedir pkgdatadir mt
 @c  LocalWords:  pkg libdir cpio bindir sbindir rmt pax sbin zar zardir acindex
 @c  LocalWords:  HTML htmldir html noinst TEXINFOS nodist nobase strudel CFLAGS
@@ -13477,7 +13869,7 @@
 @c  LocalWords:  Miller's installable includedir inc pkgdata EXEEXT libexec bsd
 @c  LocalWords:  pkglib libexecdir prog libcpio cpio's dlopen dlpreopen linux
 @c  LocalWords:  subsubsection OBJEXT esac lib LTLIBRARIES liblob LIBADD AR ar
-@c  LocalWords:  ARFLAGS cru ing maude libgettext lo LTLIBOBJS rpath SGI PRE yy
+@c  LocalWords:  ARFLAGS cr ing maude libgettext lo LTLIBOBJS rpath SGI PRE yy
 @c  LocalWords:  libmaude CCLD CXXFLAGS FFLAGS LFLAGS OBJCFLAGS RFLAGS DEFS cc
 @c  LocalWords:  OBJCXXFLAGS
 @c  LocalWords:  SHORTNAME vtable srcdir nostdinc basename yxx cxx ll lxx gdb
@@ -13488,7 +13880,7 @@
 @c  LocalWords:  yylhs yylen yydefred yydgoto yysindex yyrindex yygindex yyname
 @c  LocalWords:  yytable yycheck yyrule byacc CXXCOMPILE CXXLINK FLINK cfortran
 @c  LocalWords:  Catalogue preprocessable FLIBS libfoo baz JAVACFLAGS java exe
-@c  LocalWords:  SunOS fying basenames exeext uninstalled oldinclude kr FSF's
+@c  LocalWords:  SunOS basenames exeext uninstalled oldinclude kr FSF's
 @c  LocalWords:  pkginclude oldincludedir sysconf sharedstate localstate gcc rm
 @c  LocalWords:  sysconfdir sharedstatedir localstatedir preexist CLEANFILES gz
 @c  LocalWords:  depfile tmpdepfile depmode const interoperate
@@ -13504,7 +13896,7 @@
 @c  LocalWords:  installcheck gzipped tarZ std utils etags mkid cd
 @c  LocalWords:  ARGS taggable ETAGSFLAGS lang ctags CTAGSFLAGS GTAGS gtags idl
 @c  LocalWords:  foocc doit idlC multilibs ABIs cmindex defmac ARG enableval FC
-@c  LocalWords:  MSG xtrue DBG pathchk CYGWIN afile proglink versioned CVS's TE
+@c  LocalWords:  MSG xtrue DBG pathchk CYGWIN afile proglink versioned TE
 @c  LocalWords:  wildcards Autoconfiscated subsubheading autotools Meyering API
 @c  LocalWords:  ois's wildcard Wportability cartouche vrindex printindex Duret
 @c  LocalWords:  DSOMEFLAG DVERSION automake Lutz insertcopying versioning FAQ

_service:tar_scm:automake-1.16.5.tar.xz/doc/fdl.texi -> _service:tar_scm:automake-1.17.tar.xz/doc/fdl.texi Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/help2man -> _service:tar_scm:automake-1.17.tar.xz/doc/help2man Changed

@@ -2,7 +2,7 @@
 
 # Generate a short man page from --help and --version output.
 # Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2009,
-# 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2020, 2021 Free Software
+# 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2020, 2021, 2022 Free Software
 # Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
@@ -29,7 +29,7 @@
 use POSIX qw(strftime setlocale LC_ALL);
 
 my $this_program = 'help2man';
-my $this_version = '1.48.4';
+my $this_version = '1.49.3';
 
 sub _ { $_0 }
 sub configure_locale
@@ -54,7 +54,7 @@
 GNU %s %s
 
 Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2009,
-2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2020, 2021 Free Software
+2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2020, 2021, 2022 Free Software
 Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
@@ -178,13 +178,13 @@
 	    $key =~ s/^\s+//;
 	    $key =~ s/\s+$//;
 	    $hash = \%include;
-	    # Handle explicit <section, =section and >section
+	    # Handle explicit <section, =section and >section.
 	    if ($key =~ s/^(<>=)\s*//)
 	    {
 		if    ($1 eq '>') { $hash = \%append; }
 		elsif ($1 eq '=') { $hash = \%replace; }
 	    }
-	    # NAME/SYNOPSIS replace by default
+	    # NAME/SYNOPSIS replace by default.
 	    elsif ($key eq _('NAME') or $key eq _('SYNOPSIS'))
 	    {
 		$hash = \%replace;
@@ -220,7 +220,7 @@
 	# revision info.
 	unless ($key)
 	{
-	    # handle options
+	    # Handle options.
 	    if (/^-/)
 	    {
 		local @ARGV = shellwords $_;
@@ -265,7 +265,7 @@
 # the English version expands to the month as a word and the full year.  It
 # is used on the footer of the generated manual pages.  If in doubt, you may
 # just use %x as the value (which should be the full locale-specific date).
-my $date = enc strftime _("%B %Y"), localtime $epoch_secs;
+my $date = strftime _("%B %Y"), localtime $epoch_secs;
 my $program = program_basename $ARGV0;
 my $package = $program;
 my $version;
@@ -340,15 +340,15 @@
 # Man pages traditionally have the page title in caps.
 my $PROGRAM = uc $program;
 
-# Set default page head/footers
+# Set default page head/footers.
 $source ||= "$package $version";
 unless ($manual)
 {
     for ($section)
     {
-	if (/^(1Mm|8)/) { $manual = enc _('System Administration Utilities') }
-	elsif (/^6/)	  { $manual = enc _('Games') }
-	else		  { $manual = enc _('User Commands') }
+	if (/^(1Mm|8)/) { $manual = _('System Administration Utilities') }
+	elsif (/^6/)	  { $manual = _('Games') }
+	else		  { $manual = _('User Commands') }
     }
 }
 
@@ -534,7 +534,7 @@
     {
 	$matched .= $& if %append_match;
 	$content = ".HP\n\x84$1\n";
-	$indent = 80; # not continued
+	$indent = 80;  # not continued
     }
 
     # Indented paragraph with tag.
@@ -669,7 +669,7 @@
 }
 
 # Output header.
-print <<EOT;
+print enc <<EOT;
 .\\" DO NOT MODIFY THIS FILE!  It was generated by $this_program $this_version.
 .TH $PROGRAM "$section" "$date" "$source" "$manual"
 EOT
@@ -700,8 +700,8 @@
 	    s/\x82/\\e/g;
 	    s/\x83/\\-/g;
 
-	    # Convert some latin1 chars to troff equivalents
-	    s/\xa0/\\ /g; # non-breaking space
+	    # Convert some latin1 chars to troff equivalents.
+	    s/\xa0/\\ /g;  # non-breaking space
 
 	    print enc $_;
 	}

_service:tar_scm:automake-1.16.5.tar.xz/doc/local.mk -> _service:tar_scm:automake-1.17.tar.xz/doc/local.mk Changed

@@ -1,5 +1,5 @@
 ## -*- makefile-automake -*-
-## Copyright (C) 1995-2021 Free Software Foundation, Inc.
+## Copyright (C) 1995-2024 Free Software Foundation, Inc.
 ##
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -29,15 +29,30 @@
   %D%/automake-$(APIVERSION).1
 
 $(man1_MANS): $(top_srcdir)/configure.ac
-
 CLEANFILES += $(man1_MANS)
-# XXX: This script should be updated with 'fetch' target.
+
+# In automake, users generate man pages as part of a normal build from
+# release tarballs. This is ok because we also distribute the help2man
+# script, as given below.
+#
+# Autoconf handles this in an alternative way, of including the man
+# pages in the tarballs and thus not requiring help2man to be run by
+# users (q.v.). Neither is better or worse than the other.
+#
+# See the "Errors with distclean" node in the manual for more info.
+
+# XXX: The help2man script we include in the Automake distribution
+# should be updated with 'fetch' target, but isn't. Instead, you must
+# build help2man normally and copy it in manually. Keep the first line as:
+#   #!/usr/bin/perl -w
+# whatever it might have ended up as on your system.
 EXTRA_DIST += %D%/help2man
 
 update_mans = \
-  $(AM_V_GEN): \
-    && $(MKDIR_P) %D% \
-    && ./pre-inst-env $(PERL) $(srcdir)/%D%/help2man --output=$@
+    $(MKDIR_P) %D% \
+    && AUTOMAKE_HELP2MAN=true ./pre-inst-env \
+       $(PERL) $(srcdir)/%D%/help2man --output=$@ --info-page=automake \
+               --name="$${HELP2MAN_NAME}"
 
 %D%/aclocal.1 %D%/automake.1:
 	$(AM_V_GEN): \
@@ -46,26 +61,25 @@
 	  && echo ".so man1/$$f-$(APIVERSION).1" > $@
 
 %D%/aclocal-$(APIVERSION).1: $(aclocal_script) lib/Automake/Config.pm
-	$(update_mans) aclocal-$(APIVERSION)
+	$(AM_V_GEN):; HELP2MAN_NAME="Generate aclocal.m4 by scanning configure.ac"; export HELP2MAN_NAME; $(update_mans) $(aclocal_script)
 %D%/automake-$(APIVERSION).1: $(automake_script) lib/Automake/Config.pm
-	$(update_mans) automake-$(APIVERSION)
+	$(AM_V_GEN):; HELP2MAN_NAME="Generate Makefile.in files for configure from Makefile.am"; export HELP2MAN_NAME; $(update_mans) $(automake_script)
 
-## This target is not invoked as a dependency of anything. It exists
-## merely to make checking the links in automake.texi (that is,
+## This checklinkx target is not invoked as a dependency of anything.
+## It exists merely to make checking the links in automake.texi (that is,
 ## automake.html) more convenient. We use a slightly-enhanced version of
 ## W3C checklink to do this. We intentionally do not have automake.html
 ## as a dependency, as it seems more convenient to have its regeneration
 ## under manual control. See https://debbugs.gnu.org/10371.
 ##
 checklinkx = $(top_srcdir)/contrib/checklinkx
-# that 4-second sleep seems to be what gnu.org likes.
+# that particular sleep seems to be what gnu.org likes.
 chlx_args = -v --sleep 8 #--exclude-url-file=/tmp/xf
 # Explanation of excludes:
 # - w3.org dtds, they are fine (and slow).
 # - mailto urls, they are always forbidden.
 # - vala, redirects to a Gnome subpage and returns 403 to us.
 # - cfortran, forbidden by site's robots.txt.
-# - search.cpan.org, gets
 # - debbugs.gnu.org/automake, forbidden by robots.txt.
 # - autoconf.html, forbidden by robots.txt (since served from savannah).
 # - https://fsf.org redirects to https://www.fsf.org and nothing to do
@@ -76,7 +90,6 @@
     -X 'mailto:.*' \
     -X 'https://www\.vala-project\.org/' \
     -X 'https://www-zeus\.desy\.de/~burow/cfortran/' \
-    -X 'http://xsearch\.cpan\.org/~mschwern/Test-Simple/lib/Test/More\.pm' \
     -X 'https://debbugs\.gnu\.org/automake' \
     -X 'https://www\.gnu\.org/software/autoconf/manual/autoconf\.html' \
     -X 'https://fsf\.org/'

_service:tar_scm:automake-1.16.5.tar.xz/doc/stamp-vti -> _service:tar_scm:automake-1.17.tar.xz/doc/stamp-vti Changed

_service:tar_scm:automake-1.16.5.tar.xz/doc/version.texi -> _service:tar_scm:automake-1.17.tar.xz/doc/version.texi Changed

_service:tar_scm:automake-1.16.5.tar.xz/gen-testsuite-part -> _service:tar_scm:automake-1.17.tar.xz/gen-testsuite-part Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/ChannelDefs.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/ChannelDefs.pm Changed

@@ -1,4 +1,4 @@
-# Copyright (C) 2002-2021 Free Software Foundation, Inc.
+# Copyright (C) 2002-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -13,6 +13,11 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
+##################################################################
+# The master copy of this file is in Automake's source repository.
+# Please send updates to automake-patches@gnu.org.
+##################################################################
+
 package Automake::ChannelDefs;
 
 =head1 NAME
@@ -69,7 +74,7 @@
 =head2 CHANNELS
 
 The following channels can be used as the first argument of
-C<Automake::Channel::msg>.  For some of them we list a shorthand
+C<Automake::Channels::msg>.  For some of them we list a shorthand
 function that makes the code more readable.
 
 =over 4
@@ -197,7 +202,7 @@
 
 sub usage ()
 {
-  return "Warning categories include:
+  return "Warning categories are:
   cross                  cross compilation issues
   gnu                    GNU coding standards (default in gnu and gnits modes)
   obsolete               obsolete features or constructions (default)
@@ -207,10 +212,12 @@
   extra-portability      extra portability issues related to obscure tools
   syntax                 dubious syntactic constructs (default)
   unsupported            unsupported or incomplete features (default)
-  all                    all the warnings
-  no-CATEGORY            turn off warnings in CATEGORY
+
+-W also understands:
+  all                    turn on all the warnings
   none                   turn off all the warnings
-  error                  treat warnings as errors";
+  no-CATEGORY            turn off warnings in CATEGORY
+  error                  treat all enabled warnings as errors";
 }
 
 =item C<prog_error ($MESSAGE, %OPTIONS)>
@@ -444,8 +451,8 @@
         {
           # The character class in the second match group is ASCII \S minus
           # comma.  We are generous with this because category values may come
-          # from WARNINGS and we don't want to assume what other programs'
-          # syntaxes for warnings categories are.
+          # from WARNINGS and we don't want to assume other programs'
+          # syntax for warnings categories.
           /^(no-|)(\w\\\/\\!"#$%&'()*+-.:;<=>?@^`{|}~+)$/
             or die "Invalid warnings category: $_";
           $warnings{$2} = $1;

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Channels.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Channels.pm Changed

@@ -1,4 +1,4 @@
-# Copyright (C) 2002-2021 Free Software Foundation, Inc.
+# Copyright (C) 2002-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -13,10 +13,10 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
-###############################################################
-# The main copy of this file is in Automake's git repository. #
-# Updates should be sent to automake-patches@gnu.org.         #
-###############################################################
+##################################################################
+# The master copy of this file is in Automake's source repository.
+# Please send updates to automake-patches@gnu.org.
+##################################################################
 
 package Automake::Channels;
 
@@ -286,7 +286,7 @@
 {
   my ($ref) = @_;
   my $dup = 0;
-  foreach my $k (keys %$ref)
+  foreach my $k (keys %$ref) # sort keys not needed
     {
       $dup += $ref->{$k};
     }
@@ -328,7 +328,7 @@
   my ($hash, %options) = @_;
   local $_;
 
-  foreach (keys %options)
+  foreach (sort keys %options)
     {
       if (exists $hash->{$_})
 	{
@@ -628,7 +628,13 @@
       $location = '';
     }
 
-  confess "unknown channel $channel" unless exists $channels{$channel};
+  if (!exists $channels{$channel})
+    {
+      # This can happen as a result of e.g. m4_warn(nonsense, message)
+      # so it should not crash.
+      report_bad_channel($channel, $location);
+      $channel = 'syntax';
+    }
 
   my %opts = %{$channels{$channel}};
   _merge_options (%opts, %options);
@@ -662,6 +668,45 @@
     }
 }
 
+sub report_bad_channel ($$)
+{
+  my ($channel, $location) = @_;
+  my $message;
+  my $report_as = 'error';
+
+  # quotemeta is both too aggressive (e.g. it escapes '-') and
+  # too generous (it turns control characters into \ + themselves,
+  # not into symbolic escapes).
+  my $q_channel = $channel;
+  $q_channel =~ s/(?=\"\$\'\@\`\\)/\\/g;
+  $q_channel =~ s/(^\x20-\x7e)/sprintf('\\x%02X', ord $1)/eg;
+  $q_channel = '"' . $q_channel . '"';
+
+  if ($channel eq '' || $channel eq 'all')
+    {
+      # Prior to version 2.70, the Autoconf manual said it was valid to use
+      # "all" and the empty string as the category argument to m4_warn, so
+      # don't treat those cases as errors.
+      $report_as = 'obsolete';
+      $message = "use of $q_channel as a diagnostic category is obsolete\n";
+      $message .= "(see automake --help for a list of valid categories)";
+    }
+  elsif ($channel eq 'none'
+         || ($channel =~ /^no-/ && exists $channels{substr($channel, 3)}))
+    {
+      # Also recognize "none" and "no-category", as someone might have
+      # thought anything acceptable to -W is also acceptable to m4_warn.
+      # Note: m4_warn(error, ...) does actually issue an error.
+      $message = "-W accepts $q_channel, but it is not a diagnostic category";
+    }
+  else
+    {
+      $message = "unknown diagnostic category " . $q_channel;
+    }
+
+  msg $report_as, $location, $message;
+}
+
 
 =item C<setup_channel ($channel, %options)>
 
@@ -686,7 +731,7 @@
 sub setup_channel_type ($%)
 {
   my ($type, %opts) = @_;
-  foreach my $channel (keys %channels)
+  foreach my $channel (sort keys %channels)
     {
       setup_channel $channel, %opts
 	if $channels{$channel}{'type'} eq $type;
@@ -714,7 +759,7 @@
 sub dup_channel_setup ()
 {
   my %channels_copy;
-  foreach my $k1 (keys %channels)
+  foreach my $k1 (keys %channels) # sort keys not needed
     {
       $channels_copy{$k1} = {%{$channels{$k1}}};
     }
@@ -778,7 +823,7 @@
 sub setup_channel_queue ($$)
 {
   my ($queue, $key) = @_;
-  foreach my $channel (keys %channels)
+  foreach my $channel (sort keys %channels)
     {
       setup_channel $channel, queue => $queue, queue_key => $key
         if $channels{$channel}{'ordered'};

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Condition.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Condition.pm Changed

@@ -1,4 +1,4 @@
-# Copyright (C) 1997-2021 Free Software Foundation, Inc.
+# Copyright (C) 1997-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -273,9 +273,9 @@
 sub conds ($ )
 {
   my ($self) = @_;
-  my @conds = keys %{$self->{'hash'}};
+  my @conds = sort keys %{$self->{'hash'}};
   return ("TRUE") unless @conds;
-  return sort @conds;
+  return @conds;
 }
 
 # Undocumented, shouldn't be needed outside of this class.
@@ -306,14 +306,14 @@
 sub true ($ )
 {
   my ($self) = @_;
-  return 0 == keys %{$self->{'hash'}};
+  return 0 == keys %{$self->{'hash'}}; # sort not needed
 }
 
 =item C<$cond-E<gt>string>
 
 Build a string which denotes the condition.
 
-For instance using the C<$cond> definition from L<SYNOPSYS>,
+For instance using the C<$cond> definition from L<SYNOPSIS>,
 C<$cond-E<gt>string> will return C<"COND1_TRUE COND2_FALSE">.
 
 =cut
@@ -341,7 +341,7 @@
 
 Build a human readable string which denotes the condition.
 
-For instance using the C<$cond> definition from L<SYNOPSYS>,
+For instance using the C<$cond> definition from L<SYNOPSIS>,
 C<$cond-E<gt>string> will return C<"COND1 and !COND2">.
 
 =cut
@@ -382,7 +382,7 @@
 
 Build a C<AC_SUBST>-style string for output in F<Makefile.in>.
 
-For instance using the C<$cond> definition from L<SYNOPSYS>,
+For instance using the C<$cond> definition from L<SYNOPSIS>,
 C<$cond-E<gt>subst_string> will return C<"@COND1_TRUE@@COND2_FALSE@">.
 
 =cut
@@ -411,7 +411,7 @@
 Return 1 iff C<$cond> is true when C<$when> is true.
 Return 0 otherwise.
 
-Using the definitions from L<SYNOPSYS>, C<$cond> is true
+Using the definitions from L<SYNOPSIS>, C<$cond> is true
 when C<$both> is true, but the converse is wrong.
 
 =cut

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Config.in -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Config.in Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Configure_ac.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Configure_ac.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/DisjConditions.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/DisjConditions.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/FileUtils.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/FileUtils.pm Changed

@@ -1,4 +1,4 @@
-# Copyright (C) 2003-2021 Free Software Foundation, Inc.
+# Copyright (C) 2003-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -13,10 +13,10 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
-###############################################################
-# The main copy of this file is in Automake's git repository. #
-# Updates should be sent to automake-patches@gnu.org.         #
-###############################################################
+##################################################################
+# The master copy of this file is in Automake's source repository.
+# Please send updates to automake-patches@gnu.org.
+##################################################################
 
 package Automake::FileUtils;
 
@@ -38,21 +38,45 @@
 use strict;
 use warnings FATAL => 'all';
 
-use Exporter;
-use File::stat;
-use IO::File;
+BEGIN
+{
+  require Exporter;
+  our @ISA = qw (Exporter);
+  our @EXPORT = qw (&contents
+		    &find_file &mtime
+		    &update_file
+		    &xsystem &xsystem_hint &xqx
+		    &dir_has_case_matching_file &reset_dir_cache
+		    &set_dir_cache_file);
+}
 
+# Use sub-second resolution file timestamps if available, carry on
+# with one-second resolution timestamps if Time::HiRes is not available.
+#
+# Unfortunately, even if Time::HiRes is available, we don't get
+# timestamps to the full precision recorded by the operating system,
+# because Time::HiRes converts timestamps to floating-point, and the
+# rounding error is hundreds of nanoseconds for circa-2023 timestamps
+# in IEEE double precision.  But this is the best we can do without
+# dropping down to C.
+#
+# $subsecond_mtime is not exported, but is intended for external
+# consumption, as $Automake::FileUtils::subsecond_mtime.
+BEGIN
+{
+  our $subsecond_mtime = 0;
+  eval
+    {
+      require Time::HiRes;
+      import Time::HiRes qw(stat);
+      $subsecond_mtime = 1;
+    }
+}
+
+use IO::File;
 use Automake::Channels;
 use Automake::ChannelDefs;
 
-our @ISA = qw (Exporter);
-our @EXPORT = qw (&contents
-		  &find_file &mtime
-		  &update_file
-		  &xsystem &xsystem_hint &xqx
-		  &dir_has_case_matching_file &reset_dir_cache
-		  &set_dir_cache_file);
-
 =over 4
 
 =item C<find_file ($file_name, @include)>
@@ -115,10 +139,11 @@
   return 0
     if $file eq '-' || ! -f $file;
 
-  my $stat = stat ($file)
+  my ($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size,
+    $atime,$mtime,$ctime,$blksize,$blocks) = stat ($file)
     or fatal "cannot stat $file: $!";
 
-  return $stat->mtime;
+  return $mtime;
 }
 
 
@@ -385,3 +410,20 @@
 =cut
 
 1; # for require
+
+### Setup "GNU" style for perl-mode and cperl-mode.
+## Local Variables:
+## perl-indent-level: 2
+## perl-continued-statement-offset: 2
+## perl-continued-brace-offset: 0
+## perl-brace-offset: 0
+## perl-brace-imaginary-offset: 0
+## perl-label-offset: -2
+## cperl-indent-level: 2
+## cperl-brace-offset: 0
+## cperl-continued-brace-offset: 0
+## cperl-label-offset: -2
+## cperl-extra-newline-before-brace: t
+## cperl-merge-trailing-else: nil
+## cperl-continued-statement-offset: 2
+## End:

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/General.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/General.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Getopt.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Getopt.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Item.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Item.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/ItemDef.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/ItemDef.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Language.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Language.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Location.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Location.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Options.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Options.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Rule.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Rule.pm Changed

@@ -1,4 +1,4 @@
-# Copyright (C) 2003-2021 Free Software Foundation, Inc.
+# Copyright (C) 2003-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -430,7 +430,7 @@
   # we know how to transform $src in that "something else".
   if (exists $suffix_rules->{$dest})
     {
-      for my $dest2 (keys %{$suffix_rules->{$dest}})
+      for my $dest2 (sort keys %{$suffix_rules->{$dest}})
 	{
 	  my $dist = $suffix_rules->{$dest}{$dest2}1 + 1;
 	  # Overwrite an existing $src->$dest2 path only if
@@ -445,8 +445,8 @@
 
   # Similarly, any extension that can be derived into $src
   # can be derived into the same extensions as $src can.
-  my @dest2 = keys %{$suffix_rules->{$src}};
-  for my $src2 (keys %$suffix_rules)
+  my @dest2 = sort keys %{$suffix_rules->{$src}};
+  for my $src2 (sort keys %$suffix_rules)
     {
       if (exists $suffix_rules->{$src2}{$src})
 	{
@@ -695,6 +695,9 @@
 
   return $cond if !$message; # No ambiguity.
 
+  # Don't coalesce the several pattern rules from footer.am into a single one.
+  return $cond if $target eq "%:" && $where->get =~ /\/am\/footer\.am$/;
+
   if ($owner == RULE_USER)
     {
       # For user rules, just diagnose the ambiguity.
@@ -764,23 +767,27 @@
 
   my $tdef = _rule_defn_with_exeext_awareness ($target, $cond, $where);
 
-  # A GNU make-style pattern rule has a single "%" in the target name.
-  msg ('portability', $where,
-       "'%'-style pattern rules are a GNU make extension")
-    if $target =~ /^^%*%^%*$/;
-
-  # See whether this is a duplicated target declaration.
-  if ($tdef)
+  # The pattern rules in footer.am look like duplicates, but really aren't.
+  if ($source !~ /\/am\/footer\.am$/)
     {
-      # Diagnose invalid target redefinitions, if any.  Note that some
-      # target redefinitions are valid (e.g., for multiple-targets
-      # pattern rules).
-      _maybe_warn_about_duplicated_target ($target, $tdef, $source,
-                                           $owner, $cond, $where);
-      # Return so we don't redefine the rule in our tables, don't check
-      # for ambiguous condition, etc.  The rule will be output anyway
-      # because '&read_am_file' ignores the return code.
-      return ();
+      # A GNU make-style pattern rule has a single "%" in the target name.
+      msg ('portability', $where,
+           "'%'-style pattern rules are a GNU make extension")
+        if $target =~ /^^%*%^%*$/;
+
+      # See whether this is a duplicated target declaration.
+      if ($tdef)
+        {
+          # Diagnose invalid target redefinitions, if any.  Note that some
+          # target redefinitions are valid (e.g., for multiple-targets
+          # pattern rules).
+          _maybe_warn_about_duplicated_target ($target, $tdef, $source,
+                                               $owner, $cond, $where);
+          # Return so we don't redefine the rule in our tables, don't check
+          # for ambiguous condition, etc.  The rule will be output anyway
+          # because '&read_am_file' ignores the return code.
+          return ();
+        }
     }
 
   my $rule = _crule $target;

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/RuleDef.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/RuleDef.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/VarDef.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/VarDef.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Variable.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Variable.pm Changed

@@ -1,4 +1,4 @@
-# Copyright (C) 2003-2021 Free Software Foundation, Inc.
+# Copyright (C) 2003-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -132,7 +132,9 @@
 =cut
 
 my $_VARIABLE_CHARACTERS = '.A-Za-z0-9_@+';
-my $_VARIABLE_PATTERN = '^' . $_VARIABLE_CHARACTERS . "\$";
+my $_VARIABLE_PATTERN_EXTRA_POSIX = '*?<%DF?';
+my $_VARIABLE_PATTERN = '^(' . $_VARIABLE_CHARACTERS
+                             . '|' . $_VARIABLE_PATTERN_EXTRA_POSIX . ")\$";
 my $_VARIABLE_RECURSIVE_PATTERN =
     '^(.A-Za-z0-9_@|\$({' . $_VARIABLE_CHARACTERS . '})?)+' . "\$";
 
@@ -331,7 +333,7 @@
     {
       @vars = values %_variable_dict;
     }
-  # The behaviour of the 'sort' built-in is undefined in scalar
+  # The behavior of the 'sort' built-in is undefined in scalar
   # context, hence we need an ad-hoc handling for such context.
   return wantarray ? sort { $a->name cmp $b->name } @vars : scalar @vars;
 }
@@ -746,9 +748,14 @@
   $text =~ s/#.*$//;
 
   # Record each use of ${stuff} or $(stuff) that does not follow a $.
-  while ($text =~ /(?<!\$)\$(?:\{(^\}*)\}|$(^$*)\))/g)
+  while ($text =~ m{\$(?:\{(^\}*)\}|$(^$*)\)|(\$))}g)
     {
-      my $var = $1 || $2;
+      my $var = $1 || $2 || $3;
+      next if (! defined $var) || ($var eq '$');
+      # we check for $var being defined because NetworkManager and other
+      # packages use the strange construct $().
+      # https://lists.gnu.org/archive/html/automake/2024-06/msg00085.html
+      
       # The occurrence may look like $(string1:subst1=subst2) but
       # we want only 'string1'.
       $var =~ s/:^:=*=^=*$//;
@@ -857,6 +864,9 @@
   msg ('portability', $where, "':='-style assignments are not portable")
     if $type eq ':';
 
+  msg ('portability', $where, "escaping \\# comment markers is not portable")
+    if index ($value, '\#') != -1;
+
   check_variable_expansions ($value, $where);
 
   # If there's a comment, make sure it is \n-terminated.
@@ -1165,11 +1175,19 @@
 	  $text .= "  The usual way to define '$var' is to add "
 	    . "'$mac'\n  to '$configure_ac' and run 'aclocal' and "
 	    . "'autoconf' again.";
+	  #
 	  # aclocal will not warn about undefined macros unless it
 	  # starts with AM_.
-	  $text .= "\n  If '$mac' is in '$configure_ac', make sure\n"
+	  $text .= "\n\n  If '$mac' is in '$configure_ac', make sure\n"
 	    . "  its definition is in aclocal's search path."
 	    unless $mac =~ /^AM_/;
+	  #
+	  # More hints for the libtool case.
+	  $text .= "\n\n  If you install Automake in its own prefix,\n"
+	    . "  you'll need to arrange for the Libtool m4 files\n"
+	    . "  to be found by aclocal.  For info on this, see:\n"
+	    . "    https://gnu.org/s/automake/manual/automake.html#Libtool-library-used-but-LIBTOOL-is-undefined"
+	    if $mac eq "LT_INIT";
 	}
       elsif (exists $_ac_macro_for_var{$var})
 	{

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Version.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Version.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/Wrap.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/Wrap.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/XFile.pm -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/XFile.pm Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/Automake/local.mk -> _service:tar_scm:automake-1.17.tar.xz/lib/Automake/local.mk Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/INSTALL -> _service:tar_scm:automake-1.17.tar.xz/lib/INSTALL Changed

@@ -1,177 +1,177 @@
 Installation Instructions
 *************************
 
-   Copyright (C) 1994-1996, 1999-2002, 2004-2017, 2020-2021 Free
-Software Foundation, Inc.
-
-   Copying and distribution of this file, with or without modification,
-are permitted in any medium without royalty provided the copyright
-notice and this notice are preserved.  This file is offered as-is,
-without warranty of any kind.
-
 Basic Installation
 ==================
 
-   Briefly, the shell command './configure && make && make install'
-should configure, build, and install this package.  The following
-more-detailed instructions are generic; see the 'README' file for
-instructions specific to this package.  Some packages provide this
-'INSTALL' file but do not implement all of the features documented
-below.  The lack of an optional feature in a given package is not
-necessarily a bug.  More recommendations for GNU packages can be found
-in *note Makefile Conventions: (standards)Makefile Conventions.
-
-   The 'configure' shell script attempts to guess correct values for
+   The following shell commands:
+
+     test -f configure || ./bootstrap
+     ./configure
+     make
+     make install
+
+should configure, build, and install this package.  The first line,
+which bootstraps, is intended for developers; when building from
+distribution tarballs it does nothing and can be skipped.
+
+   The following more-detailed instructions are generic; see the
+‘README’ file for instructions specific to this package.  Some packages
+provide this ‘INSTALL’ file but do not implement all of the features
+documented below.  The lack of an optional feature in a given package is
+not necessarily a bug.  More recommendations for GNU packages can be
+found in the GNU Coding Standards.
+
+   Many packages have scripts meant for developers instead of ordinary
+builders, as they may use developer tools that are less commonly
+installed, or they may access the network, which has privacy
+implications.  If the ‘bootstrap’ shell script exists, it attempts to
+build the ‘configure’ shell script and related files, possibly using
+developer tools or the network.  Because the output of ‘bootstrap’ is
+system-independent, it is normally run by a package developer so that
+its output can be put into the distribution tarball and ordinary
+builders and users need not run ‘bootstrap’.  Some packages have
+commands like ‘./autopull.sh’ and ‘./autogen.sh’ that you can run
+instead of ‘./bootstrap’, for more fine-grained control over
+bootstrapping.
+
+   The ‘configure’ shell script attempts to guess correct values for
 various system-dependent variables used during compilation.  It uses
-those values to create a 'Makefile' in each directory of the package.
-It may also create one or more '.h' files containing system-dependent
-definitions.  Finally, it creates a shell script 'config.status' that
+those values to create a ‘Makefile’ in each directory of the package.
+It may also create one or more ‘.h’ files containing system-dependent
+definitions.  Finally, it creates a shell script ‘config.status’ that
 you can run in the future to recreate the current configuration, and a
-file 'config.log' containing compiler output (useful mainly for
-debugging 'configure').
+file ‘config.log’ containing output useful for debugging ‘configure’.
 
-   It can also use an optional file (typically called 'config.cache' and
-enabled with '--cache-file=config.cache' or simply '-C') that saves the
+   It can also use an optional file (typically called ‘config.cache’ and
+enabled with ‘--cache-file=config.cache’ or simply ‘-C’) that saves the
 results of its tests to speed up reconfiguring.  Caching is disabled by
 default to prevent problems with accidental use of stale cache files.
 
    If you need to do unusual things to compile the package, please try
-to figure out how 'configure' could check whether to do them, and mail
-diffs or instructions to the address given in the 'README' so they can
+to figure out how ‘configure’ could check whether to do them, and mail
+diffs or instructions to the address given in the ‘README’ so they can
 be considered for the next release.  If you are using the cache, and at
-some point 'config.cache' contains results you don't want to keep, you
+some point ‘config.cache’ contains results you don’t want to keep, you
 may remove or edit it.
 
-   The file 'configure.ac' (or 'configure.in') is used to create
-'configure' by a program called 'autoconf'.  You need 'configure.ac' if
-you want to change it or regenerate 'configure' using a newer version of
-'autoconf'.
+   The ‘autoconf’ program generates ‘configure’ from the file
+‘configure.ac’.  Normally you should edit ‘configure.ac’ instead of
+editing ‘configure’ directly.
 
    The simplest way to compile this package is:
 
-  1. 'cd' to the directory containing the package's source code and type
-     './configure' to configure the package for your system.
+  1. ‘cd’ to the directory containing the package’s source code.
+
+  2. If this is a developer checkout and file ‘configure’ does not yet
+     exist, type ‘./bootstrap’ to create it.  You may need special
+     developer tools and network access to bootstrap, and the network
+     access may have privacy implications.
 
-     Running 'configure' might take a while.  While running, it prints
-     some messages telling which features it is checking for.
+  3. Type ‘./configure’ to configure the package for your system.  This
+     might take a while.  While running, ‘configure’ prints messages
+     telling which features it is checking for.
 
-  2. Type 'make' to compile the package.
+  4. Type ‘make’ to compile the package.
 
-  3. Optionally, type 'make check' to run any self-tests that come with
+  5. Optionally, type ‘make check’ to run any self-tests that come with
      the package, generally using the just-built uninstalled binaries.
 
-  4. Type 'make install' to install the programs and any data files and
+  6. Type ‘make install’ to install the programs and any data files and
      documentation.  When installing into a prefix owned by root, it is
      recommended that the package be configured and built as a regular
-     user, and only the 'make install' phase executed with root
+     user, and only the ‘make install’ phase executed with root
      privileges.
 
-  5. Optionally, type 'make installcheck' to repeat any self-tests, but
+  7. Optionally, type ‘make installcheck’ to repeat any self-tests, but
      this time using the binaries in their final installed location.
      This target does not install anything.  Running this target as a
-     regular user, particularly if the prior 'make install' required
+     regular user, particularly if the prior ‘make install’ required
      root privileges, verifies that the installation completed
      correctly.
 
-  6. You can remove the program binaries and object files from the
-     source code directory by typing 'make clean'.  To also remove the
-     files that 'configure' created (so you can compile the package for
-     a different kind of computer), type 'make distclean'.  There is
-     also a 'make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
-  7. Often, you can also type 'make uninstall' to remove the installed
-     files again.  In practice, not all packages have tested that
-     uninstallation works correctly, even though it is required by the
-     GNU Coding Standards.
-
-  8. Some packages, particularly those that use Automake, provide 'make
-     distcheck', which can by used by developers to test that all other
-     targets like 'make install' and 'make uninstall' work correctly.
-     This target is generally not run by end users.
+  8. You can remove the program binaries and object files from the
+     source code directory by typing ‘make clean’.  To also remove the
+     files that ‘configure’ created (so you can compile the package for
+     a different kind of computer), type ‘make distclean’.  There is
+     also a ‘make maintainer-clean’ target, but that is intended mainly
+     for the package’s developers.  If you use it, you may have to
+     bootstrap again.
+
+  9. If the package follows the GNU Coding Standards, you can type ‘make
+     uninstall’ to remove the installed files.
 
 Compilers and Options
 =====================
 
    Some systems require unusual options for compilation or linking that
-the 'configure' script does not know about.  Run './configure --help'
+the ‘configure’ script does not know about.  Run ‘./configure --help’
 for details on some of the pertinent environment variables.
 
-   You can give 'configure' initial values for configuration parameters
+   You can give ‘configure’ initial values for configuration parameters
 by setting variables in the command line or in the environment.  Here is
 an example:
 
-     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+     ./configure CC=gcc CFLAGS=-g LIBS=-lposix
 
-   *Note Defining Variables::, for more details.
+   See “Defining Variables” for more details.
 
 Compiling For Multiple Architectures
 ====================================
 
    You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you can use GNU 'make'.  'cd' to the
-directory where you want the object files and executables to go and run
-the 'configure' script.  'configure' automatically checks for the source
-code in the directory that 'configure' is in and in '..'.  This is known
-as a "VPATH" build.
-
-   With a non-GNU 'make', it is safer to compile the package for one
-architecture at a time in the source code directory.  After you have
-installed the package for one architecture, use 'make distclean' before
-reconfiguring for another architecture.
-
-   On MacOS X 10.5 and later systems, you can create libraries and
-executables that work on multiple system types--known as "fat" or
-"universal" binaries--by specifying multiple '-arch' options to the
-compiler but only a single '-arch' option to the preprocessor.  Like
-this:
-
-     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-                 CPP="gcc -E" CXXCPP="g++ -E"
-
-   This is not guaranteed to produce working output in all cases, you
-may have to build one architecture at a time and combine the results
-using the 'lipo' tool if you have problems.
+same time, by placing the object files for each system in their own
+directory.  To do this, you can use GNU ‘make’.  ‘cd’ to the directory
+where you want the object files and executables to go and run the
+‘configure’ script.  ‘configure’ automatically checks for the source
+code in the directory that ‘configure’ is in and in ‘..’.  This is known
+as a “VPATH” build.
+
+   With a non-GNU ‘make’, it is safer to compile the package for one
+system at a time in the source code directory.  After you have installed
+the package for one system, use ‘make distclean’ before reconfiguring
+for another system.
+
+   Some platforms, notably macOS, support “fat” or “universal” binaries,
+where a single binary can execute on different architectures.  On these
+platforms you can configure and compile just once, with options specific
+to that platform.
 
 Installation Names
 ==================
 
-   By default, 'make install' installs the package's commands under
-'/usr/local/bin', include files under '/usr/local/include', etc.  You
-can specify an installation prefix other than '/usr/local' by giving
-'configure' the option '--prefix=PREFIX', where PREFIX must be an
+   By default, ‘make install’ installs the package’s commands under
+‘/usr/local/bin’, include files under ‘/usr/local/include’, etc.  You
+can specify an installation prefix other than ‘/usr/local’ by giving
+‘configure’ the option ‘--prefix=PREFIX’, where PREFIX must be an
 absolute file name.
 
    You can specify separate installation prefixes for
 architecture-specific files and architecture-independent files.  If you
-pass the option '--exec-prefix=PREFIX' to 'configure', the package uses
+pass the option ‘--exec-prefix=PREFIX’ to ‘configure’, the package uses
 PREFIX as the prefix for installing programs and libraries.
 Documentation and other data files still use the regular prefix.
 
    In addition, if you use an unusual directory layout you can give
-options like '--bindir=DIR' to specify different values for particular
-kinds of files.  Run 'configure --help' for a list of the directories
+options like ‘--bindir=DIR’ to specify different values for particular
+kinds of files.  Run ‘configure --help’ for a list of the directories
 you can set and what kinds of files go in them.  In general, the default
-for these options is expressed in terms of '${prefix}', so that
-specifying just '--prefix' will affect all of the other directory
+for these options is expressed in terms of ‘${prefix}’, so that
+specifying just ‘--prefix’ will affect all of the other directory
 specifications that were not explicitly provided.
 
    The most portable way to affect installation locations is to pass the
-correct locations to 'configure'; however, many packages provide one or
+correct locations to ‘configure’; however, many packages provide one or
 both of the following shortcuts of passing variable assignments to the
-'make install' command line to change installation locations without
+‘make install’ command line to change installation locations without
 having to reconfigure or recompile.
 
    The first method involves providing an override variable for each
-affected directory.  For example, 'make install
-prefix=/alternate/directory' will choose an alternate location for all
+affected directory.  For example, ‘make install
+prefix=/alternate/directory’ will choose an alternate location for all
 directory configuration variables that were expressed in terms of
-'${prefix}'.  Any directories that were specified during 'configure',
-but not in terms of '${prefix}', must each be overridden at install time
+‘${prefix}’.  Any directories that were specified during ‘configure’,
+but not in terms of ‘${prefix}’, must each be overridden at install time
 for the entire installation to be relocated.  The approach of makefile
 variable overrides for each directory variable is required by the GNU
 Coding Standards, and ideally causes no recompilation.  However, some
@@ -179,190 +179,187 @@
 that end up requiring recompilation when using this method, particularly
 noticeable in packages that use GNU Libtool.
 
-   The second method involves providing the 'DESTDIR' variable.  For
-example, 'make install DESTDIR=/alternate/directory' will prepend
-'/alternate/directory' before all installation names.  The approach of
-'DESTDIR' overrides is not required by the GNU Coding Standards, and
+   The second method involves providing the ‘DESTDIR’ variable.  For
+example, ‘make install DESTDIR=/alternate/directory’ will prepend
+‘/alternate/directory’ before all installation names.  The approach of
+‘DESTDIR’ overrides is not required by the GNU Coding Standards, and
 does not work on platforms that have drive letters.  On the other hand,
 it does better at avoiding recompilation issues, and works well even
-when some directory options were not specified in terms of '${prefix}'
-at 'configure' time.
+when some directory options were not specified in terms of ‘${prefix}’
+at ‘configure’ time.
 
 Optional Features
 =================
 
    If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving 'configure' the
-option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
+with an extra prefix or suffix on their names by giving ‘configure’ the
+option ‘--program-prefix=PREFIX’ or ‘--program-suffix=SUFFIX’.
 
-   Some packages pay attention to '--enable-FEATURE' options to
-'configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to '--with-PACKAGE' options, where PACKAGE
-is something like 'gnu-as' or 'x' (for the X Window System).  The
-'README' should mention any '--enable-' and '--with-' options that the
-package recognizes.
-
-   For packages that use the X Window System, 'configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the 'configure' options '--x-includes=DIR' and
-'--x-libraries=DIR' to specify their locations.
+   Some packages pay attention to ‘--enable-FEATURE’ and
+‘--disable-FEATURE’ options to ‘configure’, where FEATURE indicates an
+optional part of the package.  They may also pay attention to
+‘--with-PACKAGE’ and ‘--without-PACKAGE’ options, where PACKAGE is
+something like ‘gnu-ld’.  ‘./configure --help’ should mention the
+‘--enable-...’ and ‘--with-...’ options that the package recognizes.
 
    Some packages offer the ability to configure how verbose the
-execution of 'make' will be.  For these packages, running './configure
---enable-silent-rules' sets the default to minimal output, which can be
-overridden with 'make V=1'; while running './configure
---disable-silent-rules' sets the default to verbose, which can be
-overridden with 'make V=0'.
-
-Particular systems
-==================
-
-   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU CC
-is not installed, it is recommended to use the following options in
-order to use an ANSI C compiler:
-
-     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
-
-and if that doesn't work, install pre-built binaries of GCC for HP-UX.
-
-   HP-UX 'make' updates targets which have the same timestamps as their
-prerequisites, which makes it generally unusable when shipped generated
-files such as 'configure' are involved.  Use GNU 'make' instead.
-
-   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its '<wchar.h>' header file.  The option '-nodtk' can be used as a
-workaround.  If GNU CC is not installed, it is therefore recommended to
-try
-
-     ./configure CC="cc"
-
-and if that doesn't work, try
-
-     ./configure CC="cc -nodtk"
-
-   On Solaris, don't put '/usr/ucb' early in your 'PATH'.  This
-directory contains several dysfunctional programs; working variants of
-these programs are available in '/usr/bin'.  So, if you need '/usr/ucb'
-in your 'PATH', put it _after_ '/usr/bin'.
-
-   On Haiku, software installed for all users goes in '/boot/common',
-not '/usr/local'.  It is recommended to use the following options:
-
-     ./configure --prefix=/boot/common
-
-Specifying the System Type
-==========================
-
-   There may be some features 'configure' cannot figure out
-automatically, but needs to determine by the type of machine the package
-will run on.  Usually, assuming the package is built to be run on the
-_same_ architectures, 'configure' can figure that out, but if it prints
-a message saying it cannot guess the machine type, give it the
-'--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as 'sun4', or a canonical name which has the form:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS
-     KERNEL-OS
-
-   See the file 'config.sub' for the possible values of each field.  If
-'config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
-   If you are _building_ compiler tools for cross-compiling, you should
-use the option '--target=TYPE' to select the type of system they will
-produce code for.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with '--host=TYPE'.
+execution of ‘make’ will be.  For these packages, running ‘./configure
+--enable-silent-rules’ sets the default to minimal output, which can be
+overridden with ‘make V=1’; while running ‘./configure
+--disable-silent-rules’ sets the default to verbose, which can be
+overridden with ‘make V=0’.
+
+Specifying a System Type
+========================
+
+   By default ‘configure’ builds for the current system.  To create
+binaries that can run on a different system type, specify a
+‘--host=TYPE’ option along with compiler variables that specify how to
+generate object code for TYPE.  For example, to create binaries intended
+to run on a 64-bit ARM processor:
+
+     ./configure --host=aarch64-linux-gnu \
+        CC=aarch64-linux-gnu-gcc \
+        CXX=aarch64-linux-gnu-g++
+
+If done on a machine that can execute these binaries (e.g., via
+‘qemu-aarch64’, ‘$QEMU_LD_PREFIX’, and Linux’s ‘binfmt_misc’
+capability), the build behaves like a native build.  Otherwise it is a
+cross-build: ‘configure’ will make cross-compilation guesses instead of
+running test programs, and ‘make check’ will not work.
+
+   A system type can either be a short name like ‘mingw64’, or a
+canonical name like ‘x86_64-pc-linux-gnu’.  Canonical names have the
+form CPU-COMPANY-SYSTEM where SYSTEM is either OS or KERNEL-OS.  To
+canonicalize and validate a system type, you can run the command
+‘config.sub’, which is often squirreled away in a subdirectory like
+‘build-aux’.  For example:
+
+     $ build-aux/config.sub arm64-linux
+     aarch64-unknown-linux-gnu
+     $ build-aux/config.sub riscv-lnx
+     Invalid configuration 'riscv-lnx': OS 'lnx' not recognized
+
+You can look at the ‘config.sub’ file to see which types are recognized.
+If the file is absent, this package does not need the system type.
+
+   If ‘configure’ fails with the diagnostic “cannot guess build type”.
+‘config.sub’ did not recognize your system’s type.  In this case, first
+fetch the newest versions of these files from the GNU config package
+(https://savannah.gnu.org/projects/config).  If that fixes things,
+please report it to the maintainers of the package containing
+‘configure’.  Otherwise, you can try the configure option ‘--build=TYPE’
+where TYPE comes close to your system type; also, please report the
+problem to <config-patches@gnu.org>.
+
+   For more details about configuring system types, see the Autoconf
+documentation.
 
 Sharing Defaults
 ================
 
-   If you want to set default values for 'configure' scripts to share,
-you can create a site shell script called 'config.site' that gives
-default values for variables like 'CC', 'cache_file', and 'prefix'.
-'configure' looks for 'PREFIX/share/config.site' if it exists, then
-'PREFIX/etc/config.site' if it exists.  Or, you can set the
-'CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all 'configure' scripts look for a site script.
+   If you want to set default values for ‘configure’ scripts to share,
+you can create a site shell script called ‘config.site’ that gives
+default values for variables like ‘CC’, ‘cache_file’, and ‘prefix’.
+‘configure’ looks for ‘PREFIX/share/config.site’ if it exists, then
+‘PREFIX/etc/config.site’ if it exists.  Or, you can set the
+‘CONFIG_SITE’ environment variable to the location of the site script.
+A warning: not all ‘configure’ scripts look for a site script.
 
 Defining Variables
 ==================
 
    Variables not defined in a site shell script can be set in the
-environment passed to 'configure'.  However, some packages may run
+environment passed to ‘configure’.  However, some packages may run
 configure again during the build, and the customized values of these
 variables may be lost.  In order to avoid this problem, you should set
-them in the 'configure' command line, using 'VAR=value'.  For example:
+them in the ‘configure’ command line, using ‘VAR=value’.  For example:
 
      ./configure CC=/usr/local2/bin/gcc
 
-causes the specified 'gcc' to be used as the C compiler (unless it is
+causes the specified ‘gcc’ to be used as the C compiler (unless it is
 overridden in the site shell script).
 
-Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
+Unfortunately, this technique does not work for ‘CONFIG_SHELL’ due to an
 Autoconf limitation.  Until the limitation is lifted, you can use this
 workaround:
 
      CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
 
-'configure' Invocation
+‘configure’ Invocation
 ======================
 
-   'configure' recognizes the following options to control how it
+   ‘configure’ recognizes the following options to control how it
 operates.
 
-'--help'
-'-h'
-     Print a summary of all of the options to 'configure', and exit.
+‘--help’
+‘-h’
+     Print a summary of all of the options to ‘configure’, and exit.
 
-'--help=short'
-'--help=recursive'
-     Print a summary of the options unique to this package's
-     'configure', and exit.  The 'short' variant lists options used only
-     in the top level, while the 'recursive' variant lists options also
+‘--help=short’
+‘--help=recursive’
+     Print a summary of the options unique to this package’s
+     ‘configure’, and exit.  The ‘short’ variant lists options used only
+     in the top level, while the ‘recursive’ variant lists options also
      present in any nested packages.
 
-'--version'
-'-V'
-     Print the version of Autoconf used to generate the 'configure'
+‘--version’
+‘-V’
+     Print the version of Autoconf used to generate the ‘configure’
      script, and exit.
 
-'--cache-file=FILE'
+‘--cache-file=FILE’
      Enable the cache: use and save the results of the tests in FILE,
-     traditionally 'config.cache'.  FILE defaults to '/dev/null' to
+     traditionally ‘config.cache’.  FILE defaults to ‘/dev/null’ to
      disable caching.
 
-'--config-cache'
-'-C'
-     Alias for '--cache-file=config.cache'.
-
-'--quiet'
-'--silent'
-'-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to '/dev/null' (any error
-     messages will still be shown).
+‘--config-cache’
+‘-C’
+     Alias for ‘--cache-file=config.cache’.
 
-'--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     'configure' can determine that directory automatically.
+‘--srcdir=DIR’
+     Look for the package’s source code in directory DIR.  Usually
+     ‘configure’ can determine that directory automatically.
 
-'--prefix=DIR'
-     Use DIR as the installation prefix.  *note Installation Names:: for
+‘--prefix=DIR’
+     Use DIR as the installation prefix.  See “Installation Names” for
      more details, including other options available for fine-tuning the
      installation locations.
 
-'--no-create'
-'-n'
+‘--host=TYPE’
+     Build binaries for system TYPE.  See “Specifying a System Type”.
+
+‘--enable-FEATURE’
+‘--disable-FEATURE’
+     Enable or disable the optional FEATURE.  See “Optional Features”.
+
+‘--with-PACKAGE’
+‘--without-PACKAGE’
+     Use or omit PACKAGE when building.  See “Optional Features”.
+
+‘--quiet’
+‘--silent’
+‘-q’
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to ‘/dev/null’ (any error
+     messages will still be shown).
+
+‘--no-create’
+‘-n’
      Run the configure checks, but stop before creating any output
      files.
 
-'configure' also accepts some other, not widely useful, options.  Run
-'configure --help' for more details.
+‘configure’ also recognizes several environment variables, and accepts
+some other, less widely useful, options.  Run ‘configure --help’ for
+more details.
+
+Copyright notice
+================
+
+   Copyright © 1994–1996, 1999–2002, 2004–2017, 2020–2024 Free Software
+Foundation, Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/check.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/check.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 2001-2021 Free Software Foundation, Inc.
+## Copyright (C) 2001-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -172,6 +172,7 @@
 # Default flags passed to test drivers.
 am__common_driver_flags = \
   --color-tests "$$am__color_tests" \
+  $$am__collect_skipped_logs \
   --enable-hard-errors "$$am__enable_hard_errors" \
   --expect-failure "$$am__expect_failure"
 
@@ -197,6 +198,11 @@
 elif test -f "$$f"; then dir=;				\
 else dir="$(srcdir)/"; fi;				\
 tst=$$dir$$f; log='$@'; 				\
+if test -n '$(IGNORE_SKIPPED_LOGS)'; then		\
+  am__collect_skipped_logs='--collect-skipped-logs no';	\
+else							\
+  am__collect_skipped_logs='';				\
+fi;							\
 if test -n '$(DISABLE_HARD_ERRORS)'; then		\
   am__enable_hard_errors=no; 				\
 else							\
@@ -246,6 +252,7 @@
 ## Exists only to be overridden.  See bug#11745.
 AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
 
+## emacs-page
 $(TEST_SUITE_LOG): $(TEST_LOGS)
 	@$(am__set_TESTS_bases); \
 ## Helper shell function, tells whether a path refers to an existing,
@@ -319,9 +326,11 @@
 	else \
 	  success=false; \
 	fi; \
-## Make $br a line of exactly 76 '=' characters, that will be used to
+##
+## Make $br a line of exactly 76 '=' characters, which will be used to
 ## enclose the testsuite summary report when displayed on the console.
 	br='==================='; br=$$br$$br$$br$$br; \
+##
 ## When writing the test summary to the console, we want to color a line
 ## reporting the count of some result *only* if at least one test
 ## experienced such a result.  This function is handy in this regard.
@@ -343,6 +352,7 @@
 	    fi; \
 	    echo "$${color_start}# $$desc $$count$${color_end}"; \
 	}; \
+##
 ## A shell function that creates the testsuite summary.  We need it
 ## because we have to create *two* summaries, one for test-suite.log,
 ## and a possibly-colorized one for console output.
@@ -356,12 +366,54 @@
 	  result_count $$1 "XPASS:" $$xpass "$$red"; \
 	  result_count $$1 "ERROR:" $$error "$$mgn"; \
 	}; \
+##
+## Function to write some basic system info in the log.
+	output_system_information () \
+	{ \
+## Omit the hostname for privacy.  Always a single word.
+## Start the line with a label for clarity, and so commands like
+## grep ^Linux don't get a false hit.
+## By the way, $(AWK) should always be defined since AC_PROG_AWK is
+## required by AM_INIT_AUTOMAKE nowadays.
+          echo;                                     \
+	  { uname -a | $(AWK) '{                    \
+  printf "System information (uname -a):";          \
+  for (i = 1; i < NF; ++i)                          \
+    {                                               \
+      if (i != 2)                                   \
+        printf " %s", $$i;                          \
+    }                                               \
+  printf "\n";                                      \
+}'; } 2>&1;                                         \
+	  if test -r /etc/os-release; then          \
+	    echo "Distribution information (/etc/os-release):"; \
+	    sed 8q /etc/os-release;                 \
+	  elif test -r /etc/issue; then             \
+	    echo "Distribution information (/etc/issue):";      \
+	    cat /etc/issue;                         \
+	  fi;                                       \
+	}; \
+##
+## Function to output the "please report bugs" message.
+	please_report () \
+	{ \
+echo "Some test(s) failed.  Please report this to $(PACKAGE_BUGREPORT),";    \
+echo "together with the test-suite.log file (gzipped) and your system";      \
+echo "information.  Thanks.";                                                \
+	}; \
+##
+## emacs-page
 ## Write "global" testsuite log.
 	{								\
 	  echo "$(PACKAGE_STRING): $(subdir)/$(TEST_SUITE_LOG)" |	\
 	    $(am__rst_title);						\
 	  create_testsuite_report --no-color;				\
+	  output_system_information;                                    \
 	  echo;								\
+## What is this line for? It's a Sphinx reStructuredText directive that
+## would insert a table of contents that goes two levels deep on headings.
+## But why is it in test-suite.log? No other references to it are evident.
+## Please inform automake@gnu.org.
 	  echo ".. contents:: :depth: 2";				\
 	  echo;								\
 	  for b in $$bases; do echo $$b; done				\
@@ -384,9 +436,9 @@
 	create_testsuite_report --maybe-color;				\
 	echo "$$col$$br$$std";						\
 	if $$success; then :; else					\
-	  echo "$${col}See $(subdir)/$(TEST_SUITE_LOG)$${std}";		\
+	  echo "$${col}See $(subdir)/$(TEST_SUITE_LOG) for debugging.$${std}";\
 	  if test -n "$(PACKAGE_BUGREPORT)"; then			\
-	    echo "$${col}Please report to $(PACKAGE_BUGREPORT)$${std}";	\
+	    please_report | sed -e "s/^/$${col}/" -e s/'$$'/"$${std}"/; \
 	  fi;								\
 	  echo "$$col$$br$$std";					\
 	fi;								\
@@ -405,8 +457,8 @@
 ## ------------------------------------------ ##
 
 check-TESTS: %CHECK_DEPS%
-	@list='$(RECHECK_LOGS)';           test -z "$$list" || rm -f $$list
-	@list='$(RECHECK_LOGS:.log=.trs)'; test -z "$$list" || rm -f $$list
+	@$(am__rm_f) $(RECHECK_LOGS)
+	@$(am__rm_f) $(RECHECK_LOGS:.log=.trs)
 ## We always have to remove $(TEST_SUITE_LOG), to ensure its rule is run
 ## in any case even in lazy mode: otherwise, if no test needs rerunning,
 ## or a prior run plus reruns all happen within the same timestamp (can
@@ -414,14 +466,13 @@
 ## OTOH, this means that, in the rule for '$(TEST_SUITE_LOG)', we
 ## cannot use '$?' to compute the set of lazily rerun tests, lest
 ## we rely on .PHONY to work portably.
-	@test -z "$(TEST_SUITE_LOG)" || rm -f $(TEST_SUITE_LOG)
+	@$(am__rm_f) $(TEST_SUITE_LOG)
 	@set +e; $(am__set_TESTS_bases); \
 	log_list=`for i in $$bases; do echo $$i.log; done`; \
-	trs_list=`for i in $$bases; do echo $$i.trs; done`; \
 ## Remove newlines and normalize whitespace.  Trailing (and possibly
 ## leading) whitespace is known to cause segmentation faults on
 ## Solaris 10 XPG4 make.
-	log_list=`echo $$log_list`; trs_list=`echo $$trs_list`; \
+	log_list=`echo $$log_list`; \
 	$(MAKE) $(AM_MAKEFLAGS) $(TEST_SUITE_LOG) TEST_LOGS="$$log_list"; \
 ## Be sure to exit with the proper exit status (automake bug#9245).  See
 ## comments in the recipe of $(TEST_SUITE_LOG) above for more information.
@@ -432,7 +483,7 @@
 recheck: all %CHECK_DEPS%
 ## See comments above in the check-TESTS recipe for why remove
 ## $(TEST_SUITE_LOG) here.
-	@test -z "$(TEST_SUITE_LOG)" || rm -f $(TEST_SUITE_LOG)
+	@$(am__rm_f) $(TEST_SUITE_LOG)
 	@set +e; $(am__set_TESTS_bases); \
 ## We must only consider tests that had an unexpected outcome (FAIL
 ## or XPASS) in the earlier run.

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/check2.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/check2.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/clean-hdr.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/clean-hdr.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/clean.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/clean.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/compile.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/compile.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/configure.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/configure.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/data.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/data.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/dejagnu.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/dejagnu.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1994-2021 Free Software Foundation, Inc.
+## Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -49,33 +49,34 @@
 ## the possibility of a corrupted site.exp if make is interrupted.
 ## Jim Meyering has some useful text on this topic.
 site.exp: Makefile $(EXTRA_DEJAGNU_SITE_CONFIG)
-	@echo 'Making a new site.exp file ...'
-	@echo '## these variables are automatically generated by make ##' >site.tmp
-	@echo '# Do not edit here.  If you wish to override these values' >>site.tmp
-	@echo '# edit the last section' >>site.tmp
-	@echo 'set srcdir "$(srcdir)"' >>site.tmp
-	@echo "set objdir \"`pwd`\"" >>site.tmp
+	$(AM_V_GEN)set -e; ( \
+	echo '## these variables are automatically generated by make ##'; \
+	echo '# Do not edit here.  If you wish to override these values'; \
+	echo '# edit the last section'; \
+	echo 'set srcdir "$(srcdir)"'; \
+	echo "set objdir \"`pwd`\""; \
 ## Quote the *_alias variables because they might be empty.
-?BUILD?	@echo 'set build_alias "$(build_alias)"' >>site.tmp
-?BUILD?	@echo 'set build_triplet $(build_triplet)' >>site.tmp
-?HOST?	@echo 'set host_alias "$(host_alias)"' >>site.tmp
-?HOST?	@echo 'set host_triplet $(host_triplet)' >>site.tmp
-?TARGET?	@echo 'set target_alias "$(target_alias)"' >>site.tmp
-?TARGET?	@echo 'set target_triplet $(target_triplet)' >>site.tmp
+?BUILD?	echo 'set build_alias "$(build_alias)"'; \
+?BUILD?	echo 'set build_triplet $(build_triplet)'; \
+?HOST?	echo 'set host_alias "$(host_alias)"'; \
+?HOST?	echo 'set host_triplet $(host_triplet)'; \
+?TARGET?	echo 'set target_alias "$(target_alias)"'; \
+?TARGET?	echo 'set target_triplet $(target_triplet)'; \
 ## Allow the package author to extend site.exp.
-	@list='$(EXTRA_DEJAGNU_SITE_CONFIG)'; for f in $$list; do \
-	  echo "## Begin content included from file $$f.  Do not modify. ##" \
-	   && cat `test -f "$$f" || echo '$(srcdir)/'`$$f \
-	   && echo "## End content included from file $$f. ##" \
-	   || exit 1; \
-	 done >> site.tmp
-	@echo "## End of auto-generated content; you can edit from here. ##" >> site.tmp
-	@if test -f site.exp; then \
-	   sed -e '1,/^## End of auto-generated content.*##/d' site.exp >> site.tmp; \
-	 fi
-	@-rm -f site.bak
-	@test ! -f site.exp || mv site.exp site.bak
-	@mv site.tmp site.exp
+	list='$(EXTRA_DEJAGNU_SITE_CONFIG)'; \
+	for f in $$list; do \
+	  echo "## Begin content included from file $$f.  Do not modify. ##"; \
+	  cat `test -f "$$f" || echo '$(srcdir)/'`$$f; \
+	  echo "## End content included from file $$f. ##"; \
+	done; \
+	echo "## End of auto-generated content; you can edit from here. ##"; \
+	if test -f site.exp; then \
+	  sed -e '1,/^## End of auto-generated content.*##/d' site.exp; \
+	fi; \
+	) >site.tmp; \
+	rm -f site.bak; \
+	test ! -f site.exp || mv site.exp site.bak; \
+	mv site.tmp site.exp
 
 ## ---------- ##
 ## Cleaning.  ##

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/depend.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/depend.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/depend2.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/depend2.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/distdir.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/distdir.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 2001-2021 Free Software Foundation, Inc.
+## Copyright (C) 2001-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -23,8 +23,8 @@
 
 am__remove_distdir = \
   if test -d "$(distdir)"; then \
-    find "$(distdir)" -type d ! -perm -200 -exec chmod u+w {} ';' \
-      && rm -rf "$(distdir)" \
+    find "$(distdir)" -type d ! -perm -700 -exec chmod u+rwx {} ';' \
+      ; rm -rf "$(distdir)" \
 ## On MSYS (1.0.17) it is not possible to remove a directory that is in
 ## use; so, if the first rm fails, we sleep some seconds and retry, to
 ## give pending processes some time to exit and "release" the directory
@@ -103,7 +103,7 @@
 ##
 if %?TOPDIR_P%
 	$(am__remove_distdir)
-	test -d "$(distdir)" || mkdir "$(distdir)"
+	$(AM_V_at)$(MKDIR_P) "$(distdir)"
 endif %?TOPDIR_P%
 ##
 ##
@@ -213,7 +213,7 @@
 	  fi; \
 	done
 ##
-## Test for directory existence here because previous automake
+## Test for directory existence here because a previous automake
 ## invocation might have created some directories.  Note that we
 ## explicitly set distdir for the subdir make; that lets us mix-n-match
 ## many automake-using packages into one large package, and have "dist"
@@ -331,7 +331,7 @@
 if %?TOPDIR_P%
 
 ?GZIP?DIST_ARCHIVES += $(distdir).tar.gz
-GZIP_ENV = --best
+GZIP_ENV = -9
 .PHONY: dist-gzip
 dist-gzip: distdir
 	tardir=$(distdir) && $(am__tar) | eval GZIP= gzip $(GZIP_ENV) -c >$(distdir).tar.gz
@@ -440,7 +440,7 @@
 distcheck: dist
 	case '$(DIST_ARCHIVES)' in \
 	*.tar.gz*) \
-	  eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).tar.gz | $(am__untar) ;;\
+	  eval GZIP= gzip -dc $(distdir).tar.gz | $(am__untar) ;;\
 	*.tar.bz2*) \
 	  bzip2 -dc $(distdir).tar.bz2 | $(am__untar) ;;\
 	*.tar.lz*) \
@@ -450,7 +450,7 @@
 	*.tar.Z*) \
 	  uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
 	*.shar.gz*) \
-	  eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).shar.gz | unshar ;;\
+	  eval GZIP= gzip -dc $(distdir).shar.gz | unshar ;;\
 	*.zip*) \
 	  unzip $(distdir).zip ;;\
 	*.tar.zst*) \
@@ -568,7 +568,9 @@
 ## Define distcleancheck_listfiles and distcleancheck separately
 ## from distcheck, so that they can be overridden by the user.
 .PHONY: distcleancheck
-distcleancheck_listfiles = find . -type f -print
+distcleancheck_listfiles = \
+  find . $ -type f -a \! \
+            \( -name .nfs* -o -name .smb* -o -name .__afs* $ \) -print
 distcleancheck: distclean
 	@if test '$(srcdir)' = . ; then \
 	  echo "ERROR: distcleancheck can only run from a VPATH build" ; \

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/footer.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/footer.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/header-vars.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/header-vars.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1994-2021 Free Software Foundation, Inc.
+## Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -75,7 +75,7 @@
 ## variable $(MFLAGS) behaves much better in that regard.  So use it.
     sane_makeflags=$$MFLAGS; \
   else \
-## Non-GNU make: we must rely on $(MAKEFLAGS).  This is tricker and more
+## Non-GNU make: we must rely on $(MAKEFLAGS).  This is trickier and more
 ## brittle, but is the best we can do.
     case $$MAKEFLAGS in \
 ## If we run "make TESTS='snooze nap'", FreeBSD make will export MAKEFLAGS
@@ -140,6 +140,10 @@
 ## subdirectories, and decide whether to stop at the first error or not.
 am__make_keepgoing = (target_option=k; $(am__make_running_with_option))
 
+## Helper to handle `rm -f` failing with no arguments.
+am__rm_f = rm -f $(am__rm_f_notfound)
+am__rm_rf = rm -rf $(am__rm_f_notfound)
+
 ## Some derived variables that have been found to be useful.
 pkgdatadir = $(datadir)/@PACKAGE@
 pkgincludedir = $(includedir)/@PACKAGE@

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/header.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/header.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/inst-vars.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/inst-vars.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 2004-2021 Free Software Foundation, Inc.
+## Copyright (C) 2004-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -59,15 +59,13 @@
 ## to the directory where the files to be removed are, and to the list of
 ## such files.
 am__uninstall_files_from_dir = { \
-## Some rm implementations complain if 'rm -f' is used without arguments.
-  test -z "$$files" \
 ## At least Solaris /bin/sh still lacks 'test -e', so we use the multiple
 ## tests below instead.  We expect $dir to be either non-existent or a
 ## directory, so the failure we'll experience if it is a regular file
 ## is indeed desired and welcome (better to fail loudly thasn silently).
-    || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
-    || { echo " ( cd '$$dir' && rm -f" $$files ")"; \
-         $(am__cd) "$$dir" && rm -f $$files; }; \
+  { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
+  || { echo " ( cd '$$dir' && rm -f" $$files ")"; \
+       $(am__cd) "$$dir" && echo $$files | $(am__xargs_n) 40 $(am__rm_f); }; \
   }
 
 endif %?FIRST%

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/install.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/install.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/java.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/java.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/lang-compile.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/lang-compile.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/lex.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/lex.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/library.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/library.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/libs.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/libs.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/libtool.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/libtool.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/lisp.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/lisp.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1996-2021 Free Software Foundation, Inc.
+## Copyright (C) 1996-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -30,17 +30,18 @@
 ## The destination file is normally determined by appending "c" to the
 ## input (which would erroneously put it in $(srcdir) in VPATH builds),
 ## so we override that, too.
-	if test '$(EMACS)' != no; then \
+	$(AM_V_GEN)if test '$(EMACS)' != no; then \
 	  am__dir=. am__subdir_includes=''; \
 	  case $@ in */*) \
 	    am__dir=`echo '$@' | sed 's,/^/*$$,,'`; \
 	    am__subdir_includes="-L $$am__dir -L $(srcdir)/$$am__dir"; \
 	  esac; \
 ## Emacs byte-compilation won't create this automatically, sadly.
-	  test -d "$$am__dir" || $(MKDIR_P) "$$am__dir" || exit 1; \
-	  $(EMACS) --batch \
+	  $(MKDIR_P) "$$am__dir" || exit 1; \
+	  $(EMACS) --batch --no-site-file \
 	    $(AM_ELCFLAGS) $(ELCFLAGS) \
 	    $$am__subdir_includes -L $(builddir) -L $(srcdir) \
+	    -l bytecomp \
 	    --eval '$(am__emacs_byte_compile_setup)' \
 	    -f batch-byte-compile '$<'; \
 	else :; fi

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/local.mk -> _service:tar_scm:automake-1.17.tar.xz/lib/am/local.mk Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/ltlib.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/ltlib.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1994-2021 Free Software Foundation, Inc.
+## Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -43,7 +43,7 @@
 	test -z "$$list2" || { \
 	  echo " $(MKDIR_P) '$(DESTDIR)$(%NDIR%dir)'"; \
 	  $(MKDIR_P) "$(DESTDIR)$(%NDIR%dir)" || exit 1; \
-## Note that we explicitly set the libtool mode.  This avoids any lossage
+## Note that we explicitly set the libtool mode.  This avoids problems
 ## if the program doesn't have a name that libtool expects.
 ## Use INSTALL and not INSTALL_DATA because libtool knows the right
 ## permissions to use.
@@ -69,7 +69,7 @@
 	    test "x$$dir" = x. || { \
 	      echo " $(MKDIR_P) '$(DESTDIR)$(%NDIR%dir)/$$dir'"; \
 	      $(MKDIR_P) "$(DESTDIR)$(%NDIR%dir)/$$dir"; }; \
-## Note that we explicitly set the libtool mode.  This avoids any lossage
+## Note that we explicitly set the libtool mode.  This avoids problems
 ## if the program doesn't have a name that libtool expects.
 ## Use INSTALL and not INSTALL_DATA because libtool knows the right
 ## permissions to use.
@@ -109,7 +109,7 @@
 
 .PHONY clean-am: clean-%DIR%LTLIBRARIES
 clean-%DIR%LTLIBRARIES:
-	-test -z "$(%DIR%_LTLIBRARIES)" || rm -f $(%DIR%_LTLIBRARIES)
+	-$(am__rm_f) $(%DIR%_LTLIBRARIES)
 ## 'so_locations' files are created by some linkers (IRIX, OSF) when
 ## building a shared object.  Libtool places these files in the
 ## directory where the shared object is created.
@@ -117,7 +117,5 @@
 	locs=`for p in $$list; do echo $$p; done | \
 	      sed 's|^^/*$$|.|; s|/^/*$$||; s|$$|/so_locations|' | \
 	      sort -u`; \
-	test -z "$$locs" || { \
-	  echo rm -f $${locs}; \
-	  rm -f $${locs}; \
-	}
+	echo rm -f $${locs}; \
+	$(am__rm_f) $${locs}

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/ltlibrary.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/ltlibrary.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/mans-vars.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/mans-vars.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/mans.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/mans.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/program.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/program.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/progs.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/progs.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1994-2021 Free Software Foundation, Inc.
+## Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -64,8 +64,8 @@
 	    test -z "$$files" || { \
 ?!LIBTOOL?	      echo " $(INSTALL_PROGRAM_ENV) $(INSTALL_PROGRAM) $$files '$(DESTDIR)$(%NDIR%dir)$$dir'"; \
 ?!LIBTOOL?	      $(INSTALL_PROGRAM_ENV) $(INSTALL_PROGRAM) $$files "$(DESTDIR)$(%NDIR%dir)$$dir" || exit $$?; \
-## Note that we explicitly set the libtool mode.  This avoids any
-## lossage if the install program doesn't have a name that libtool
+## Note that we explicitly set the libtool mode.  This avoids
+## problems if the install program doesn't have a name that libtool
 ## expects.
 ?LIBTOOL?	    echo " $(INSTALL_PROGRAM_ENV) $(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=install $(INSTALL_PROGRAM) $$files '$(DESTDIR)$(%NDIR%dir)$$dir'"; \
 ?LIBTOOL?	    $(INSTALL_PROGRAM_ENV) $(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=install $(INSTALL_PROGRAM) $$files "$(DESTDIR)$(%NDIR%dir)$$dir" || exit $$?; \
@@ -95,7 +95,7 @@
 	`; \
 	test -n "$$list" || exit 0; \
 	echo " ( cd '$(DESTDIR)$(%NDIR%dir)' && rm -f" $$files ")"; \
-	cd "$(DESTDIR)$(%NDIR%dir)" && rm -f $$files
+	cd "$(DESTDIR)$(%NDIR%dir)" && $(am__rm_f) $$files
 endif %?INSTALL%
 
 
@@ -105,7 +105,7 @@
 
 .PHONY clean-am: clean-%DIR%PROGRAMS
 clean-%DIR%PROGRAMS:
-?!LIBTOOL?	-test -z "$(%DIR%_PROGRAMS)" || rm -f $(%DIR%_PROGRAMS)
+?!LIBTOOL?	-$(am__rm_f) $(%DIR%_PROGRAMS)
 ## Under Cygwin, we build 'program$(EXEEXT)'.  However, if this
 ## program uses a Libtool library, Libtool will move it in
 ## '_libs/program$(EXEEXT)' and create a 'program' wrapper (without
@@ -114,13 +114,8 @@
 ## Cleaning the '_libs/' or '.libs/' directory is done from clean-libtool.
 ## FIXME: In the future (i.e., when it works) it would be nice to delegate
 ## this task to "libtool --mode=clean".
-?LIBTOOL?	@list='$(%DIR%_PROGRAMS)'; test -n "$$list" || exit 0; \
-?LIBTOOL?	echo " rm -f" $$list; \
-?LIBTOOL?	rm -f $$list || exit $$?; \
-?LIBTOOL?	test -n "$(EXEEXT)" || exit 0; \
-?LIBTOOL?	list=`for p in $$list; do echo "$$p"; done | sed 's/$(EXEEXT)$$//'`; \
-?LIBTOOL?	echo " rm -f" $$list; \
-?LIBTOOL?	rm -f $$list
+?LIBTOOL?	$(am__rm_f) $(%DIR%_PROGRAMS)
+?LIBTOOL?	test -z "$(EXEEXT)" || $(am__rm_f) $(%DIR%_PROGRAMS:$(EXEEXT)=)
 
 
 ## ---------- ##

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/python.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/python.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1999-2021 Free Software Foundation, Inc.
+## Copyright (C) 1999-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -94,11 +94,11 @@
 ## Uninstalling.  ##
 ## -------------- ##
 
-if %?INSTALL%
-
 ?FIRST?am__pep3147_tweak = \
 ?FIRST?  sed -e 's|\.py$$||' -e 's|^/*$$|__pycache__/&.*.pyc __pycache__/&.*.pyo|'
 
+if %?INSTALL%
+
 .PHONY uninstall-am: uninstall-%DIR%PYTHON
 uninstall-%DIR%PYTHON:
 	@$(NORMAL_UNINSTALL)
@@ -117,10 +117,8 @@
 ## This is somewhat tricky, because for newer pythons we have to take PEP-3147
 ## into account.  Avoid exceeding the command-line length limit.
 	dir='$(DESTDIR)$(%NDIR%dir)'; \
-	echo "$$py_files" | $(am__pep3147_tweak) | $(am__base_list) | \
-	  while read files; do \
-	    $(am__uninstall_files_from_dir) || st=$$?; \
-	  done || exit $$?; \
+	files=`echo "$$py_files" | $(am__pep3147_tweak)`; \
+	$(am__uninstall_files_from_dir) || st=$$?; \
 	exit $$st
 endif %?INSTALL%

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/remake-hdr.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/remake-hdr.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1994-2021 Free Software Foundation, Inc.
+## Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -21,8 +21,8 @@
 
 
 %STAMP%: %CONFIG_H_DEPS% $(top_builddir)/config.status
-	@rm -f %STAMP%
-	cd $(top_builddir) && $(SHELL) ./config.status %CONFIG_H_PATH%
+	$(AM_V_at)rm -f %STAMP%
+	$(AM_V_GEN)cd $(top_builddir) && $(SHELL) ./config.status %CONFIG_H_PATH%
 
 
 ## Only the first file of AC_CONFIG_HEADERS is assumed to be generated
@@ -30,7 +30,7 @@
 if %?FIRST-HDR%
 %CONFIG_HIN%: %MAINTAINER-MODE% $(am__configure_deps) %FILES%
 ## Cater to parallel BSD make.
-	($(am__cd) $(top_srcdir) && $(AUTOHEADER))
+	$(AM_V_GEN)($(am__cd) $(top_srcdir) && $(AUTOHEADER))
 ## Whenever $(AUTOHEADER) has run, we must make sure that
 ## ./config.status will rebuild config.h.  The dependency from %STAMP%
 ## on %CONFIG_H_DEPS% (which contains config.hin) is not enough to
@@ -61,11 +61,11 @@
 ##
 ## A solution is to erase %STAMP% here so that the %STAMP% rule
 ## is always triggered after the this one.
-	rm -f %STAMP%
+	$(AM_V_at)rm -f %STAMP%
 ## Autoheader has the bad habit of not changing the timestamp if
 ## config.hin is unchanged, which breaks Make targets.  Since what
 ## must not changed gratuitously is config.h, which is already handled
 ## by config.status, there is no reason to make things complex for
 ## config.hin.
-	touch $@
+	$(AM_V_at)touch $@
 endif %?FIRST-HDR%

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/scripts.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/scripts.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/subdirs.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/subdirs.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/tags.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/tags.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/texi-vers.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/texi-vers.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/texibuild.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/texibuild.am Changed

@@ -1,5 +1,5 @@
 ## automake - create Makefile.in from Makefile.am
-## Copyright (C) 1994-2021 Free Software Foundation, Inc.
+## Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -63,7 +63,9 @@
 ?!GENERIC?%DEST_PREFIX%.dvi: %SOURCE% %DEPS% %DIRSTAMP%
 	%AM_V_TEXI2DVI%TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
 ## Must set MAKEINFO like this so that version.texi will be found even
-## if it is in srcdir (-I $(srcdir) is set in %MAKEINFOFLAGS%).
+## if it is in srcdir (-I $(srcdir) is set in %MAKEINFOFLAGS%), and in case
+## texi2dvi automatically falls back to using makeinfo for expanding (-E).
+## If texi2dvi doesn't fall back, we also pass %MAKEINFOFLAGS% directly below.
 	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) %MAKEINFOFLAGS%' \
 ## texi2dvi doesn't silence everything with -q, redirect to /dev/null instead.
 ## We still want -q (%TEXIQUIET%) because it turns on batch mode.
@@ -71,10 +73,10 @@
 ## by-products are left in there, instead of cluttering the current
 ## directory (see automake bug#11146).  Use a different build-dir for
 ## each file (and distinct from that of the corresponding PDF file) to
-## avoid hitting a Texinfop bug that could cause low-probability racy
+## avoid hitting a Texinfo bug that could cause low-probability racy
 ## failure when doing parallel builds; see:
 ## https://lists.gnu.org/archive/html/automake-patches/2012-06/msg00073.html
-	$(TEXI2DVI) %TEXIQUIET% --build-dir=$(@:.dvi=.t2d) -o $@ %TEXIDEVNULL% \
+	$(TEXI2DVI) $(AM_TEXI2FLAGS) %MAKEINFOFLAGS% %TEXIQUIET% --build-dir=$(@:.dvi=.t2d) -o $@ %TEXIDEVNULL% \
 ?GENERIC?	%SOURCE%
 ?!GENERIC?	`test -f '%SOURCE%' || echo '$(srcdir)/'`%SOURCE%
 
@@ -82,7 +84,9 @@
 ?!GENERIC?%DEST_PREFIX%.pdf: %SOURCE% %DEPS% %DIRSTAMP%
 	%AM_V_TEXI2PDF%TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
 ## Must set MAKEINFO like this so that version.texi will be found even
-## if it is in srcdir (-I $(srcdir) is set in %MAKEINFOFLAGS%).
+## if it is in srcdir (-I $(srcdir) is set in %MAKEINFOFLAGS%), and in case
+## texi2dvi automatically falls back to using makeinfo for expanding (-E).
+## If texi2dvi doesn't fall back, we also pass %MAKEINFOFLAGS% directly below.
 	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) %MAKEINFOFLAGS%' \
 ## texi2pdf doesn't silence everything with -q, redirect to /dev/null instead.
 ## We still want -q (%TEXIQUIET%) because it turns on batch mode.
@@ -90,10 +94,10 @@
 ## by-products are left in there, instead of cluttering the current
 ## directory (see automake bug#11146).  Use a different build-dir for
 ## each file (and distinct from that of the corresponding DVI file) to
-## avoid hitting a Texinfop bug that could cause low-probability racy
+## avoid hitting a Texinfo bug that could cause low-probability racy
 ## failure when doing parallel builds; see:
 ## https://lists.gnu.org/archive/html/automake-patches/2012-06/msg00073.html
-	$(TEXI2PDF) %TEXIQUIET% --build-dir=$(@:.pdf=.t2p) -o $@ %TEXIDEVNULL% \
+	$(TEXI2PDF) $(AM_TEXI2FLAGS) %MAKEINFOFLAGS% %TEXIQUIET% --build-dir=$(@:.pdf=.t2p) -o $@ %TEXIDEVNULL% \
 ?GENERIC?	%SOURCE%
 ?!GENERIC?	`test -f '%SOURCE%' || echo '$(srcdir)/'`%SOURCE%

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/texinfos.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/texinfos.am Changed

@@ -1,6 +1,6 @@
 ## automake - create Makefile.in from Makefile.am
 
-## Copyright (C) 1994-2021 Free Software Foundation, Inc.
+## Copyright (C) 1994-2024 Free Software Foundation, Inc.
 
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -386,14 +386,13 @@
 ## Use '-rf', not just '-f', because the %*CLEAN% substitutions can also
 ## contain any directory created by "makeinfo --html", as well as the
 ## '*.t2d' and '*.t2p' directories used by texi2dvi and texi2pdf.
-	-rm -rf %MOSTLYCLEAN%
+	-$(am__rm_rf) %MOSTLYCLEAN%
 
 .PHONY clean-am: clean-aminfo
 clean-aminfo:
 ## Use '-rf', not just '-f'; see comments in 'mostlyclean-aminfo'
 ## above for details.
-?TEXICLEAN?	-test -z "%TEXICLEAN%" \
-?TEXICLEAN?	|| rm -rf %TEXICLEAN%
+?TEXICLEAN?	-$(am__rm_rf) %TEXICLEAN%
 
 .PHONY maintainer-clean-am: maintainer-clean-aminfo
 maintainer-clean-aminfo:
@@ -405,7 +404,6 @@
 	done
 ## Use '-rf', not just '-f'; see comments in 'mostlyclean-aminfo'
 ## above for details.
-?MAINTCLEAN?	-test -z "%MAINTCLEAN%" \
-?MAINTCLEAN?	|| rm -rf %MAINTCLEAN%
+?MAINTCLEAN?	-$(am__rm_rf) %MAINTCLEAN%
 
 endif %?LOCAL-TEXIS%

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/vala.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/vala.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/am/yacc.am -> _service:tar_scm:automake-1.17.tar.xz/lib/am/yacc.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/ar-lib -> _service:tar_scm:automake-1.17.tar.xz/lib/ar-lib Changed

@@ -2,9 +2,9 @@
 # Wrapper for Microsoft lib.exe
 
 me=ar-lib
-scriptversion=2019-07-04.01; # UTC
+scriptversion=2024-06-19.01; # UTC
 
-# Copyright (C) 2010-2021 Free Software Foundation, Inc.
+# Copyright (C) 2010-2024 Free Software Foundation, Inc.
 # Written by Peter Rosin <peda@lysator.liu.se>.
 #
 # This program is free software; you can redistribute it and/or modify
@@ -105,11 +105,15 @@
 Usage: $me --help --version PROGRAM ACTION ARCHIVE MEMBER...
 
 Members may be specified in a file named with @FILE.
+
+Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>.
 EOF
     exit $?
     ;;
   -v | --v*)
-    echo "$me, version $scriptversion"
+    echo "$me (GNU Automake) $scriptversion"
     exit $?
     ;;
 esac
@@ -135,6 +139,10 @@
       AR="$AR $1"
       shift
       ;;
+    -nologo | -NOLOGO)
+      # We always invoke AR with -nologo, so don't need to add it again.
+      shift
+      ;;
     *)
       action=$1
       shift

_service:tar_scm:automake-1.16.5.tar.xz/lib/compile -> _service:tar_scm:automake-1.17.tar.xz/lib/compile Changed

@@ -1,9 +1,9 @@
 #! /bin/sh
 # Wrapper for compilers which do not understand '-c -o'.
 
-scriptversion=2018-03-07.03; # UTC
+scriptversion=2024-06-19.01; # UTC
 
-# Copyright (C) 1999-2021 Free Software Foundation, Inc.
+# Copyright (C) 1999-2024 Free Software Foundation, Inc.
 # Written by Tom Tromey <tromey@cygnus.com>.
 #
 # This program is free software; you can redistribute it and/or modify
@@ -143,7 +143,7 @@
 	  # configure might choose to run compile as 'compile cc -o foo foo.c'.
 	  eat=1
 	  case $2 in
-	    *.o | *.oObBjJ)
+	    *.o | *.lo | *.oObBjJ)
 	      func_file_conv "$2"
 	      set x "$@" -Fo"$file"
 	      shift
@@ -248,14 +248,17 @@
 right script to run: please start by reading the file 'INSTALL'.
 
 Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>.
 EOF
     exit $?
     ;;
   -v | --v*)
-    echo "compile $scriptversion"
+    echo "compile (GNU Automake) $scriptversion"
     exit $?
     ;;
   cl | */\\cl | cl.exe | */\\cl.exe | \
+  clang-cl | */\\clang-cl | clang-cl.exe | */\\clang-cl.exe | \
   icl | */\\icl | icl.exe | */\\icl.exe )
     func_cl_wrapper "$@"      # Doesn't return...
     ;;

_service:tar_scm:automake-1.16.5.tar.xz/lib/config.guess -> _service:tar_scm:automake-1.17.tar.xz/lib/config.guess Changed

@@ -1,14 +1,14 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
-#   Copyright 1992-2021 Free Software Foundation, Inc.
+#   Copyright 1992-2024 Free Software Foundation, Inc.
 
 # shellcheck disable=SC2006,SC2268 # see below for rationale
 
-timestamp='2021-06-03'
+timestamp='2024-01-01'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 3 of the License, or
+# the Free Software Foundation, either version 3 of the License, or
 # (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful, but
@@ -47,7 +47,7 @@
 usage="\
 Usage: $0 OPTION
 
-Output the configuration name of the system \`$me' is run on.
+Output the configuration name of the system '$me' is run on.
 
 Options:
   -h, --help         print this help, then exit
@@ -60,13 +60,13 @@
 GNU config.guess ($timestamp)
 
 Originally written by Per Bothner.
-Copyright 1992-2021 Free Software Foundation, Inc.
+Copyright 1992-2024 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
 
 help="
-Try \`$me --help' for more information."
+Try '$me --help' for more information."
 
 # Parse command line
 while test $# -gt 0 ; do
@@ -102,8 +102,8 @@
 # temporary files to be created and, as you can see below, it is a
 # headache to deal with in a portable fashion.
 
-# Historically, `CC_FOR_BUILD' used to be named `HOST_CC'. We still
-# use `HOST_CC' if defined, but it is deprecated.
+# Historically, 'CC_FOR_BUILD' used to be named 'HOST_CC'. We still
+# use 'HOST_CC' if defined, but it is deprecated.
 
 # Portable tmp directory creation inspired by the Autoconf team.
 
@@ -155,6 +155,9 @@
 
 	set_cc_for_build
 	cat <<-EOF > "$dummy.c"
+	#if defined(__ANDROID__)
+	LIBC=android
+	#else
 	#include <features.h>
 	#if defined(__UCLIBC__)
 	LIBC=uclibc
@@ -162,6 +165,8 @@
 	LIBC=dietlibc
 	#elif defined(__GLIBC__)
 	LIBC=gnu
+	#elif defined(__LLVM_LIBC__)
+	LIBC=llvm
 	#else
 	#include <stdarg.h>
 	/* First heuristic to detect musl libc.  */
@@ -169,6 +174,7 @@
 	LIBC=musl
 	#endif
 	#endif
+	#endif
 	EOF
 	cc_set_libc=`$CC_FOR_BUILD -E "$dummy.c" 2>/dev/null | grep '^LIBC' | sed 's, ,,g'`
 	eval "$cc_set_libc"
@@ -437,7 +443,7 @@
 	# This test works for both compilers.
 	if test "$CC_FOR_BUILD" != no_compiler_found; then
 	    if (echo '#ifdef __amd64'; echo IS_64BIT_ARCH; echo '#endif') | \
-		(CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) | \
+		(CCOPTS="" $CC_FOR_BUILD -m64 -E - 2>/dev/null) | \
 		grep IS_64BIT_ARCH >/dev/null
 	    then
 		SUN_ARCH=x86_64
@@ -459,7 +465,7 @@
 		UNAME_RELEASE=`uname -v`
 		;;
 	esac
-	# Japanese Language versions have a version number like `4.1.3-JL'.
+	# Japanese Language versions have a version number like '4.1.3-JL'.
 	SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/-/_/'`
 	GUESS=sparc-sun-sunos$SUN_REL
 	;;
@@ -904,7 +910,7 @@
 	fi
 	;;
     *:FreeBSD:*:*)
-	UNAME_PROCESSOR=`/usr/bin/uname -p`
+	UNAME_PROCESSOR=`uname -p`
 	case $UNAME_PROCESSOR in
 	    amd64)
 		UNAME_PROCESSOR=x86_64 ;;
@@ -929,6 +935,9 @@
     i*:PW*:*)
 	GUESS=$UNAME_MACHINE-pc-pw32
 	;;
+    *:SerenityOS:*:*)
+        GUESS=$UNAME_MACHINE-pc-serenity
+        ;;
     *:Interix*:*)
 	case $UNAME_MACHINE in
 	    x86)
@@ -963,11 +972,37 @@
 	GNU_REL=`echo "$UNAME_RELEASE" | sed -e 's/-(.*//'`
 	GUESS=$UNAME_MACHINE-unknown-$GNU_SYS$GNU_REL-$LIBC
 	;;
+    x86_64:Mmanagarm:*:*|i?86:Mmanagarm:*:*)
+	GUESS="$UNAME_MACHINE-pc-managarm-mlibc"
+	;;
+    *:Mmanagarm:*:*)
+	GUESS="$UNAME_MACHINE-unknown-managarm-mlibc"
+	;;
     *:Minix:*:*)
 	GUESS=$UNAME_MACHINE-unknown-minix
 	;;
     aarch64:Linux:*:*)
-	GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
+	set_cc_for_build
+	CPU=$UNAME_MACHINE
+	LIBCABI=$LIBC
+	if test "$CC_FOR_BUILD" != no_compiler_found; then
+	    ABI=64
+	    sed 's/^	    //' << EOF > "$dummy.c"
+	    #ifdef __ARM_EABI__
+	    #ifdef __ARM_PCS_VFP
+	    ABI=eabihf
+	    #else
+	    ABI=eabi
+	    #endif
+	    #endif
+EOF
+	    cc_set_abi=`$CC_FOR_BUILD -E "$dummy.c" 2>/dev/null | grep '^ABI' | sed 's, ,,g'`
+	    eval "$cc_set_abi"
+	    case $ABI in
+		eabi | eabihf) CPU=armv8l; LIBCABI=$LIBC$ABI ;;
+	    esac
+	fi
+	GUESS=$CPU-unknown-linux-$LIBCABI
 	;;
     aarch64_be:Linux:*:*)
 	UNAME_MACHINE=aarch64_be
@@ -1033,7 +1068,16 @@
     k1om:Linux:*:*)
 	GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
 	;;
-    loongarch32:Linux:*:* | loongarch64:Linux:*:* | loongarchx32:Linux:*:*)
+    kvx:Linux:*:*)
+	GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
+	;;
+    kvx:cos:*:*)
+	GUESS=$UNAME_MACHINE-unknown-cos
+	;;
+    kvx:mbr:*:*)
+	GUESS=$UNAME_MACHINE-unknown-mbr
+	;;
+    loongarch32:Linux:*:* | loongarch64:Linux:*:*)
 	GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
 	;;
     m32r*:Linux:*:*)
@@ -1148,16 +1192,27 @@
 	;;
     x86_64:Linux:*:*)
 	set_cc_for_build
+	CPU=$UNAME_MACHINE
 	LIBCABI=$LIBC
 	if test "$CC_FOR_BUILD" != no_compiler_found; then
-	    if (echo '#ifdef __ILP32__'; echo IS_X32; echo '#endif') | \
-		(CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) | \
-		grep IS_X32 >/dev/null
-	    then
-		LIBCABI=${LIBC}x32
-	    fi
+	    ABI=64
+	    sed 's/^	    //' << EOF > "$dummy.c"
+	    #ifdef __i386__
+	    ABI=x86
+	    #else
+	    #ifdef __ILP32__
+	    ABI=x32
+	    #endif
+	    #endif
+EOF
+	    cc_set_abi=`$CC_FOR_BUILD -E "$dummy.c" 2>/dev/null | grep '^ABI' | sed 's, ,,g'`
+	    eval "$cc_set_abi"
+	    case $ABI in
+		x86) CPU=i686 ;;
+		x32) LIBCABI=${LIBC}x32 ;;
+	    esac
 	fi
-	GUESS=$UNAME_MACHINE-pc-linux-$LIBCABI
+	GUESS=$CPU-pc-linux-$LIBCABI
 	;;
     xtensa*:Linux:*:*)
 	GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
@@ -1177,7 +1232,7 @@
 	GUESS=$UNAME_MACHINE-pc-sysv4.2uw$UNAME_VERSION
 	;;
     i*86:OS/2:*:*)
-	# If we were able to find `uname', then EMX Unix compatibility
+	# If we were able to find 'uname', then EMX Unix compatibility
 	# is probably installed.
 	GUESS=$UNAME_MACHINE-pc-os2-emx
 	;;
@@ -1318,7 +1373,7 @@
 		GUESS=ns32k-sni-sysv
 	fi
 	;;
-    PENTIUM:*:4.0*:*)	# Unisys `ClearPath HMP IX 4000' SVR4/MP effort
+    PENTIUM:*:4.0*:*)	# Unisys 'ClearPath HMP IX 4000' SVR4/MP effort
 			# says <Richard.M.Bartel@ccMail.Census.GOV>
 	GUESS=i586-unisys-sysv4
 	;;
@@ -1364,8 +1419,11 @@
     BePC:Haiku:*:*)	# Haiku running on Intel PC compatible.
 	GUESS=i586-pc-haiku
 	;;
-    x86_64:Haiku:*:*)
-	GUESS=x86_64-unknown-haiku
+    ppc:Haiku:*:*)	# Haiku running on Apple PowerPC
+	GUESS=powerpc-apple-haiku
+	;;
+    *:Haiku:*:*)	# Haiku modern gcc (not bound by BeOS compat)
+	GUESS=$UNAME_MACHINE-unknown-haiku
 	;;
     SX-4:SUPER-UX:*:*)
 	GUESS=sx4-nec-superux$UNAME_RELEASE
@@ -1522,6 +1580,9 @@
     i*86:rdos:*:*)
 	GUESS=$UNAME_MACHINE-pc-rdos
 	;;
+    i*86:Fiwix:*:*)
+	GUESS=$UNAME_MACHINE-pc-fiwix
+	;;
     *:AROS:*:*)
 	GUESS=$UNAME_MACHINE-unknown-aros
 	;;
@@ -1534,6 +1595,9 @@
     *:Unleashed:*:*)
 	GUESS=$UNAME_MACHINE-unknown-unleashed$UNAME_RELEASE
 	;;
+    *:Ironclad:*:*)
+	GUESS=$UNAME_MACHINE-unknown-ironclad
+	;;
 esac
 
 # Do we have a guess based on uname results?

_service:tar_scm:automake-1.16.5.tar.xz/lib/config.sub -> _service:tar_scm:automake-1.17.tar.xz/lib/config.sub Changed

@@ -1,14 +1,14 @@
 #! /bin/sh
 # Configuration validation subroutine script.
-#   Copyright 1992-2021 Free Software Foundation, Inc.
+#   Copyright 1992-2024 Free Software Foundation, Inc.
 
 # shellcheck disable=SC2006,SC2268 # see below for rationale
 
-timestamp='2021-08-14'
+timestamp='2024-01-01'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 3 of the License, or
+# the Free Software Foundation, either version 3 of the License, or
 # (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful, but
@@ -76,13 +76,13 @@
 version="\
 GNU config.sub ($timestamp)
 
-Copyright 1992-2021 Free Software Foundation, Inc.
+Copyright 1992-2024 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
 
 help="
-Try \`$me --help' for more information."
+Try '$me --help' for more information."
 
 # Parse command line
 while test $# -gt 0 ; do
@@ -130,7 +130,7 @@
 # Separate into logical components for further validation
 case $1 in
 	*-*-*-*-*)
-		echo Invalid configuration \`"$1"\': more than four components >&2
+		echo "Invalid configuration '$1': more than four components" >&2
 		exit 1
 		;;
 	*-*-*-*)
@@ -145,7 +145,8 @@
 			nto-qnx* | linux-* | uclinux-uclibc* \
 			| uclinux-gnu* | kfreebsd*-gnu* | knetbsd*-gnu* | netbsd*-gnu* \
 			| netbsd*-eabi* | kopensolaris*-gnu* | cloudabi*-eabi* \
-			| storm-chaos* | os2-emx* | rtmk-nova*)
+			| storm-chaos* | os2-emx* | rtmk-nova* | managarm-* \
+			| windows-* )
 				basic_machine=$field1
 				basic_os=$maybe_os
 				;;
@@ -943,7 +944,7 @@
 EOF
 		IFS=$saved_IFS
 		;;
-	# We use `pc' rather than `unknown'
+	# We use 'pc' rather than 'unknown'
 	# because (1) that's what they normally are, and
 	# (2) the word "unknown" tends to confuse beginning users.
 	i*86 | x86_64)
@@ -1020,6 +1021,11 @@
 		;;
 
 	# Here we normalize CPU types with a missing or matching vendor
+	armh-unknown | armh-alt)
+		cpu=armv7l
+		vendor=alt
+		basic_os=${basic_os:-linux-gnueabihf}
+		;;
 	dpx20-unknown | dpx20-bull)
 		cpu=rs6000
 		vendor=bull
@@ -1070,7 +1076,7 @@
 	pentium-* | p5-* | k5-* | k6-* | nexgen-* | viac3-*)
 		cpu=i586
 		;;
-	pentiumpro-* | p6-* | 6x86-* | athlon-* | athalon_*-*)
+	pentiumpro-* | p6-* | 6x86-* | athlon-* | athlon_*-*)
 		cpu=i686
 		;;
 	pentiumii-* | pentium2-* | pentiumiii-* | pentium3-*)
@@ -1121,7 +1127,7 @@
 	xscale-* | xscaleebl-*)
 		cpu=`echo "$cpu" | sed 's/^xscale/arm/'`
 		;;
-	arm64-*)
+	arm64-* | aarch64le-*)
 		cpu=aarch64
 		;;
 
@@ -1175,7 +1181,7 @@
 		case $cpu in
 			1750a | 580 \
 			| a29k \
-			| aarch64 | aarch64_be \
+			| aarch64 | aarch64_be | aarch64c | arm64ec \
 			| abacus \
 			| alpha | alphaev4-8 | alphaev56 | alphaev678 \
 			| alpha64 | alpha64ev4-8 | alpha64ev56 | alpha64ev678 \
@@ -1194,50 +1200,29 @@
 			| d10v | d30v | dlx | dsp16xx \
 			| e2k | elxsi | epiphany \
 			| f3001 | f700 | fido | fr30 | frv | ft32 | fx80 \
+			| javascript \
 			| h8300 | h8500 \
 			| hppa | hppa1.01 | hppa2.0 | hppa2.0nw | hppa64 \
 			| hexagon \
 			| i370 | i*86 | i860 | i960 | ia16 | ia64 \
 			| ip2k | iq2000 \
 			| k1om \
+			| kvx \
 			| le32 | le64 \
 			| lm32 \
-			| loongarch32 | loongarch64 | loongarchx32 \
+			| loongarch32 | loongarch64 \
 			| m32c | m32r | m32rle \
 			| m5200 | m68000 | m6800123460 | m68360 | m683?2 | m68k \
 			| m6811 | m68hc11 | m6812 | m68hc12 | m68hcs12x \
 			| m88110 | m88k | maxq | mb | mcore | mep | metag \
 			| microblaze | microblazeel \
-			| mips | mipsbe | mipseb | mipsel | mipsle \
-			| mips16 \
-			| mips64 | mips64eb | mips64el \
-			| mips64octeon | mips64octeonel \
-			| mips64orion | mips64orionel \
-			| mips64r5900 | mips64r5900el \
-			| mips64vr | mips64vrel \
-			| mips64vr4100 | mips64vr4100el \
-			| mips64vr4300 | mips64vr4300el \
-			| mips64vr5000 | mips64vr5000el \
-			| mips64vr5900 | mips64vr5900el \
-			| mipsisa32 | mipsisa32el \
-			| mipsisa32r2 | mipsisa32r2el \
-			| mipsisa32r3 | mipsisa32r3el \
-			| mipsisa32r5 | mipsisa32r5el \
-			| mipsisa32r6 | mipsisa32r6el \
-			| mipsisa64 | mipsisa64el \
-			| mipsisa64r2 | mipsisa64r2el \
-			| mipsisa64r3 | mipsisa64r3el \
-			| mipsisa64r5 | mipsisa64r5el \
-			| mipsisa64r6 | mipsisa64r6el \
-			| mipsisa64sb1 | mipsisa64sb1el \
-			| mipsisa64sr71k | mipsisa64sr71kel \
-			| mipsr5900 | mipsr5900el \
-			| mipstx39 | mipstx39el \
+			| mips* \
 			| mmix \
 			| mn10200 | mn10300 \
 			| moxie \
 			| mt \
 			| msp430 \
+			| nanomips* \
 			| nds32 | nds32le | nds32be \
 			| nfp \
 			| nios | nios2 | nios2eb | nios2el \
@@ -1269,6 +1254,7 @@
 			| ubicom32 \
 			| v70 | v850 | v850e | v850e1 | v850es | v850e2 | v850e2v3 \
 			| vax \
+			| vc4 \
 			| visium \
 			| w65 \
 			| wasm32 | wasm64 \
@@ -1280,7 +1266,7 @@
 				;;
 
 			*)
-				echo Invalid configuration \`"$1"\': machine \`"$cpu-$vendor"\' not recognized 1>&2
+				echo "Invalid configuration '$1': machine '$cpu-$vendor' not recognized" 1>&2
 				exit 1
 				;;
 		esac
@@ -1301,11 +1287,12 @@
 
 # Decode manufacturer-specific aliases for certain operating systems.
 
-if test x$basic_os != x
+if test x"$basic_os" != x
 then
 
-# First recognize some ad-hoc caes, or perhaps split kernel-os, or else just
+# First recognize some ad-hoc cases, or perhaps split kernel-os, or else just
 # set os.
+obj=
 case $basic_os in
 	gnu/linux*)
 		kernel=linux
@@ -1336,6 +1323,10 @@
 		kernel=linux
 		os=`echo "$basic_os" | sed -e 's|linux|gnu|'`
 		;;
+	managarm*)
+		kernel=managarm
+		os=`echo "$basic_os" | sed -e 's|managarm|mlibc|'`
+		;;
 	*)
 		kernel=
 		os=$basic_os
@@ -1501,10 +1492,16 @@
 			os=eabi
 			;;
 		    *)
-			os=elf
+			os=
+			obj=elf
 			;;
 		esac
 		;;
+	aout* | coff* | elf* | pe*)
+		# These are machine code file formats, not OSes
+		obj=$os
+		os=
+		;;
 	*)
 		# No normalization, but not necessarily accepted, that comes below.
 		;;
@@ -1523,12 +1520,15 @@
 # system, and we'll never get to this point.
 
 kernel=
+obj=
 case $cpu-$vendor in
 	score-*)
-		os=elf
+		os=
+		obj=elf
 		;;
 	spu-*)
-		os=elf
+		os=
+		obj=elf
 		;;
 	*-acorn)
 		os=riscix1.2
@@ -1538,28 +1538,35 @@
 		os=gnu
 		;;
 	arm*-semi)
-		os=aout
+		os=
+		obj=aout
 		;;
 	c4x-* | tic4x-*)
-		os=coff
+		os=
+		obj=coff
 		;;
 	c8051-*)
-		os=elf
+		os=
+		obj=elf
 		;;
 	clipper-intergraph)
 		os=clix
 		;;
 	hexagon-*)
-		os=elf
+		os=
+		obj=elf
 		;;
 	tic54x-*)
-		os=coff
+		os=
+		obj=coff
 		;;
 	tic55x-*)
-		os=coff
+		os=
+		obj=coff
 		;;
 	tic6x-*)
-		os=coff
+		os=
+		obj=coff
 		;;
 	# This must come before the *-dec entry.
 	pdp10-*)
@@ -1581,19 +1588,24 @@
 		os=sunos3
 		;;
 	m68*-cisco)
-		os=aout
+		os=
+		obj=aout
 		;;
 	mep-*)
-		os=elf
+		os=
+		obj=elf
 		;;
 	mips*-cisco)
-		os=elf
+		os=
+		obj=elf
 		;;
-	mips*-*)
-		os=elf
+	mips*-*|nanomips*-*)
+		os=
+		obj=elf
 		;;
 	or32-*)
-		os=coff
+		os=
+		obj=coff
 		;;
 	*-tti)	# must be before sparc entry or we get the wrong os.
 		os=sysv3
@@ -1602,7 +1614,8 @@
 		os=sunos4.1.1
 		;;
 	pru-*)
-		os=elf
+		os=
+		obj=elf
 		;;
 	*-be)
 		os=beos
@@ -1683,10 +1696,12 @@
 		os=uxpv
 		;;
 	*-rom68k)
-		os=coff
+		os=
+		obj=coff
 		;;
 	*-*bug)
-		os=coff
+		os=
+		obj=coff
 		;;
 	*-apple)
 		os=macos
@@ -1704,10 +1719,11 @@
 
 fi
 
-# Now, validate our (potentially fixed-up) OS.
+# Now, validate our (potentially fixed-up) individual pieces (OS, OBJ).
+
 case $os in
 	# Sometimes we do "kernel-libc", so those need to count as OSes.
-	musl* | newlib* | relibc* | uclibc*)
+	llvm* | musl* | newlib* | relibc* | uclibc*)
 		;;
 	# Likewise for "kernel-abi"
 	eabi* | gnueabi*)
@@ -1715,6 +1731,9 @@
 	# VxWorks passes extra cpu info in the 4th filed.
 	simlinux | simwindows | spe)
 		;;
+	# See `case $cpu-$os` validation below
+	ghcjs)
+		;;
 	# Now accept the basic system types.
 	# The portable systems comes first.
 	# Each alternative MUST end in a * to match a version number.
@@ -1723,7 +1742,7 @@
 	     | hpux* | unos* | osf* | luna* | dgux* | auroraux* | solaris* \
 	     | sym* |  plan9* | psp* | sim* | xray* | os68k* | v88r* \
 	     | hiux* | abug | nacl* | netware* | windows* \
-	     | os9* | macos* | osx* | ios* \
+	     | os9* | macos* | osx* | ios* | tvos* | watchos* \
 	     | mpw* | magic* | mmixware* | mon960* | lnews* \
 	     | amigaos* | amigados* | msdos* | newsos* | unicos* | aof* \
 	     | aos* | aros* | cloudabi* | sortix* | twizzler* \
@@ -1732,11 +1751,11 @@
 	     | mirbsd* | netbsd* | dicos* | openedition* | ose* \
 	     | bitrig* | openbsd* | secbsd* | solidbsd* | libertybsd* | os108* \
 	     | ekkobsd* | freebsd* | riscix* | lynxos* | os400* \
-	     | bosx* | nextstep* | cxux* | aout* | elf* | oabi* \
-	     | ptx* | coff* | ecoff* | winnt* | domain* | vsta* \
+	     | bosx* | nextstep* | cxux* | oabi* \
+	     | ptx* | ecoff* | winnt* | domain* | vsta* \
 	     | udi* | lites* | ieee* | go32* | aux* | hcos* \
 	     | chorusrdb* | cegcc* | glidix* | serenity* \
-	     | cygwin* | msys* | pe* | moss* | proelf* | rtems* \
+	     | cygwin* | msys* | moss* | proelf* | rtems* \
 	     | midipix* | mingw32* | mingw64* | mint* \
 	     | uxpv* | beos* | mpeix* | udk* | moxiebox* \
 	     | interix* | uwin* | mks* | rhapsody* | darwin* \
@@ -1748,49 +1767,117 @@
 	     | skyos* | haiku* | rdos* | toppers* | drops* | es* \
 	     | onefs* | tirtos* | phoenix* | fuchsia* | redox* | bme* \
 	     | midnightbsd* | amdhsa* | unleashed* | emscripten* | wasi* \
-	     | nsk* | powerunix* | genode* | zvmoe* | qnx* | emx* | zephyr*)
+	     | nsk* | powerunix* | genode* | zvmoe* | qnx* | emx* | zephyr* \
+	     | fiwix* | mlibc* | cos* | mbr* | ironclad* )
 		;;
 	# This one is extra strict with allowed versions
 	sco3.2v2 | sco3.2v4-9* | sco5v6*)
 		# Don't forget version if it is 3.2v4 or newer.
 		;;
+	# This refers to builds using the UEFI calling convention
+	# (which depends on the architecture) and PE file format.
+	# Note that this is both a different calling convention and
+	# different file format than that of GNU-EFI
+	# (x86_64-w64-mingw32).
+	uefi)
+		;;
 	none)
 		;;
+	kernel* | msvc* )
+		# Restricted further below
+		;;
+	'')
+		if test x"$obj" = x
+		then
+			echo "Invalid configuration '$1': Blank OS only allowed with explicit machine code file format" 1>&2
+		fi
+		;;
 	*)
-		echo Invalid configuration \`"$1"\': OS \`"$os"\' not recognized 1>&2
+		echo "Invalid configuration '$1': OS '$os' not recognized" 1>&2
+		exit 1
+		;;
+esac
+
+case $obj in
+	aout* | coff* | elf* | pe*)
+		;;
+	'')
+		# empty is fine
+		;;
+	*)
+		echo "Invalid configuration '$1': Machine code format '$obj' not recognized" 1>&2
+		exit 1
+		;;
+esac
+
+# Here we handle the constraint that a (synthetic) cpu and os are
+# valid only in combination with each other and nowhere else.
+case $cpu-$os in
+	# The "javascript-unknown-ghcjs" triple is used by GHC; we
+	# accept it here in order to tolerate that, but reject any
+	# variations.
+	javascript-ghcjs)
+		;;
+	javascript-* | *-ghcjs)
+		echo "Invalid configuration '$1': cpu '$cpu' is not valid with os '$os$obj'" 1>&2
 		exit 1
 		;;
 esac
 
 # As a final step for OS-related things, validate the OS-kernel combination
 # (given a valid OS), if there is a kernel.
-case $kernel-$os in
-	linux-gnu* | linux-dietlibc* | linux-android* | linux-newlib* \
-		   | linux-musl* | linux-relibc* | linux-uclibc* )
+case $kernel-$os-$obj in
+	linux-gnu*- | linux-android*- | linux-dietlibc*- | linux-llvm*- \
+		    | linux-mlibc*- | linux-musl*- | linux-newlib*- \
+		    | linux-relibc*- | linux-uclibc*- )
+		;;
+	uclinux-uclibc*- )
+		;;
+	managarm-mlibc*- | managarm-kernel*- )
 		;;
-	uclinux-uclibc* )
+	windows*-msvc*-)
 		;;
-	-dietlibc* | -newlib* | -musl* | -relibc* | -uclibc* )
+	-dietlibc*- | -llvm*- | -mlibc*- | -musl*- | -newlib*- | -relibc*- \
+		    | -uclibc*- )
 		# These are just libc implementations, not actual OSes, and thus
 		# require a kernel.
-		echo "Invalid configuration \`$1': libc \`$os' needs explicit kernel." 1>&2
+		echo "Invalid configuration '$1': libc '$os' needs explicit kernel." 1>&2
 		exit 1
 		;;
-	kfreebsd*-gnu* | kopensolaris*-gnu*)
+	-kernel*- )
+		echo "Invalid configuration '$1': '$os' needs explicit kernel." 1>&2
+		exit 1
 		;;
-	vxworks-simlinux | vxworks-simwindows | vxworks-spe)
+	*-kernel*- )
+		echo "Invalid configuration '$1': '$kernel' does not support '$os'." 1>&2
+		exit 1
 		;;
-	nto-qnx*)
+	*-msvc*- )
+		echo "Invalid configuration '$1': '$os' needs 'windows'." 1>&2
+		exit 1
 		;;
-	os2-emx)
+	kfreebsd*-gnu*- | kopensolaris*-gnu*-)
+		;;
+	vxworks-simlinux- | vxworks-simwindows- | vxworks-spe-)
+		;;
+	nto-qnx*-)
+		;;
+	os2-emx-)
 		;;
-	*-eabi* | *-gnueabi*)
+	*-eabi*- | *-gnueabi*-)
 		;;
-	-*)
+	none--*)
+		# None (no kernel, i.e. freestanding / bare metal),
+		# can be paired with an machine code file format
+		;;
+	-*-)
 		# Blank kernel with real OS is always fine.
 		;;
-	*-*)
-		echo "Invalid configuration \`$1': Kernel \`$kernel' not known to work with OS \`$os'." 1>&2
+	--*)
+		# Blank kernel and OS with real machine code file format is always fine.
+		;;
+	*-*-*)
+		echo "Invalid configuration '$1': Kernel '$kernel' not known to work with OS '$os'." 1>&2
 		exit 1
 		;;
 esac
@@ -1873,7 +1960,7 @@
 		;;
 esac
 
-echo "$cpu-$vendor-${kernel:+$kernel-}$os"
+echo "$cpu-$vendor${kernel:+-$kernel}${os:+-$os}${obj:+-$obj}"
 exit
 
 # Local variables:

_service:tar_scm:automake-1.16.5.tar.xz/lib/depcomp -> _service:tar_scm:automake-1.17.tar.xz/lib/depcomp Changed

@@ -1,9 +1,9 @@
 #! /bin/sh
 # depcomp - compile a program generating dependencies as side-effects
 
-scriptversion=2018-03-07.03; # UTC
+scriptversion=2024-06-19.01; # UTC
 
-# Copyright (C) 1999-2021 Free Software Foundation, Inc.
+# Copyright (C) 1999-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -47,11 +47,13 @@
   libtool     Whether libtool is used (yes/no).
 
 Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>.
 EOF
     exit $?
     ;;
   -v | --v*)
-    echo "depcomp $scriptversion"
+    echo "depcomp (GNU Automake) $scriptversion"
     exit $?
     ;;
 esac
@@ -113,7 +115,6 @@
 # These definitions help.
 upper=ABCDEFGHIJKLMNOPQRSTUVWXYZ
 lower=abcdefghijklmnopqrstuvwxyz
-digits=0123456789
 alpha=${upper}${lower}
 
 if test -z "$depmode" || test -z "$source" || test -z "$object"; then
@@ -128,7 +129,7 @@
 
 rm -f "$tmpdepfile"
 
-# Avoid interferences from the environment.
+# Avoid interference from the environment.
 gccflag= dashmflag=
 
 # Some modes work just like other modes, but use different flags.  We
@@ -198,8 +199,8 @@
   ;;
 
 gcc)
-## Note that this doesn't just cater to obsosete pre-3.x GCC compilers.
-## but also to in-use compilers like IMB xlc/xlC and the HP C compiler.
+## Note that this doesn't just cater to obsolete pre-3.x GCC compilers.
+## but also to in-use compilers like IBM xlc/xlC and the HP C compiler.
 ## (see the conditional assignment to $gccflag above).
 ## There are various ways to get dependency output from gcc.  Here's
 ## why we pick this rather obscure method:

_service:tar_scm:automake-1.16.5.tar.xz/lib/gendocs.sh -> _service:tar_scm:automake-1.17.tar.xz/lib/gendocs.sh Changed

@@ -2,13 +2,13 @@
 # gendocs.sh -- generate a GNU manual in many formats.  This script is
 #   mentioned in maintain.texi.  See the help message below for usage details.
 
-scriptversion=2021-07-19.18
+scriptversion=2024-07-04.03
 
-# Copyright 2003-2021 Free Software Foundation, Inc.
+# Copyright 2003-2024 Free Software Foundation, Inc.
 #
 # This program is free software: you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 3 of the License, or
+# the Free Software Foundation, either version 3 of the License, or
 # (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful,
@@ -40,22 +40,22 @@
 scripturl="https://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/gendocs.sh"
 templateurl="https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/gendocs_template"
 
-: ${SETLANG="env LANG= LC_MESSAGES= LC_ALL= LANGUAGE="}
-: ${MAKEINFO="makeinfo"}
-: ${TEXI2DVI="texi2dvi"}
-: ${DOCBOOK2HTML="docbook2html"}
-: ${DOCBOOK2PDF="docbook2pdf"}
-: ${DOCBOOK2TXT="docbook2txt"}
-: ${GENDOCS_TEMPLATE_DIR="."}
-: ${PERL='perl'}
-: ${TEXI2HTML="texi2html"}
+: "${SETLANG="env LANG= LC_TIME= LC_MESSAGES= LC_ALL= LANGUAGE="}"
+: "${MAKEINFO="makeinfo"}"
+: "${TEXI2DVI="texi2dvi"}"
+: "${DOCBOOK2HTML="docbook2html"}"
+: "${DOCBOOK2PDF="docbook2pdf"}"
+: "${DOCBOOK2TXT="docbook2txt"}"
+: "${GENDOCS_TEMPLATE_DIR="."}"
+: "${PERL="perl"}"
+: "${TEXI2HTML="texi2html"}"
 unset CDPATH
 unset use_texi2html
 
 MANUAL_TITLE=
 PACKAGE=
 EMAIL=webmasters@gnu.org  # please override with --email
-commonarg= # passed to all makeinfo/texi2html invcations.
+commonarg= # passed to all makeinfo/texi2html invocations.
 dirargs=   # passed to all tools (-I dir).
 dirs=      # -I directories.
 htmlarg="--css-ref=https://www.gnu.org/software/gnulib/manual.css -c TOP_NODE_UP_URL=/manual"
@@ -66,14 +66,14 @@
 generate_info=true
 generate_tex=true
 outdir=manual
-source_extra=
+unset source_extra
 split=node
 srcfile=
 texarg="-t @finalout"
 
 version="gendocs.sh $scriptversion
 
-Copyright 2021 Free Software Foundation, Inc.
+Copyright 2024 Free Software Foundation, Inc.
 There is NO warranty.  You may redistribute this software
 under the terms of the GNU General Public License.
 For more information about these matters, see the files named COPYING."
@@ -167,7 +167,7 @@
     --html)      shift; default_htmlarg=false; htmlarg=$1;;
     --info)      shift; infoarg=$1;;
     --no-ascii)  generate_ascii=false;;
-    --no-html)   generate_ascii=false;;
+    --no-html)   generate_html=false;;
     --no-info)   generate_info=false;;
     --no-tex)    generate_tex=false;;
     --source)    shift; source_extra=$1;;
@@ -256,8 +256,8 @@
 /<img src="(.*?)"/g && ++$need{$1};
 
 END {
-  #print "$me: @{keys %need}\n";  # for debugging, show images found.
-  FILE: for my $f (keys %need) {
+  #print "$me: @{sort keys %need}\n";  # for debugging, show images found.
+  FILE: for my $f (sort keys %need) {
     for my $d (@dirs) {
       if (-f "$d/$f") {
         use File::Basename;
@@ -304,7 +304,7 @@
 # &#xc;
 if $generate_tex; then
   cmd="$SETLANG $TEXI2DVI $dirargs $texarg \"$srcfile\""
-  printf "\nGenerating dvi... ($cmd)\n"
+  printf "\nGenerating dvi... (%s)\n" "$cmd"
   eval "$cmd"
   # compress/finish dvi:
   gzip -f -9 $PACKAGE.dvi
@@ -313,7 +313,7 @@
   ls -l "$outdir/$PACKAGE.dvi.gz"
 
   cmd="$SETLANG $TEXI2DVI --pdf $dirargs $texarg \"$srcfile\""
-  printf "\nGenerating pdf... ($cmd)\n"
+  printf "\nGenerating pdf... (%s)\n" "$cmd"
   eval "$cmd"
   pdf_size=`calcsize $PACKAGE.pdf`
   mv $PACKAGE.pdf "$outdir/"
@@ -324,7 +324,7 @@
 if $generate_ascii; then
   opt="-o $PACKAGE.txt --no-split --no-headers $commonarg"
   cmd="$SETLANG $MAKEINFO $opt \"$srcfile\""
-  printf "\nGenerating ascii... ($cmd)\n"
+  printf "\nGenerating ascii... (%s)\n" "$cmd"
   eval "$cmd"
   ascii_size=`calcsize $PACKAGE.txt`
   gzip -f -9 -c $PACKAGE.txt >"$outdir/$PACKAGE.txt.gz"
@@ -341,7 +341,7 @@
 {
   opt="--split=$1 --node-files $commonarg $htmlarg"
   cmd="$SETLANG $TEXI2HTML --output $PACKAGE.html $opt \"$srcfile\""
-  printf "\nGenerating html by $1... ($cmd)\n"
+  printf "\nGenerating html by %s... (%s)\n" "$1" "$cmd"
   eval "$cmd"
   split_html_dir=$PACKAGE.html
   (
@@ -359,7 +359,7 @@
 if test -z "$use_texi2html"; then
   opt="--no-split --html -o $PACKAGE.html $commonarg $htmlarg"
   cmd="$SETLANG $MAKEINFO $opt \"$srcfile\""
-  printf "\nGenerating monolithic html... ($cmd)\n"
+  printf "\nGenerating monolithic html... (%s)\n" "$cmd"
   rm -rf $PACKAGE.html  # in case a directory is left over
   eval "$cmd"
   html_mono_size=`calcsize $PACKAGE.html`
@@ -380,7 +380,7 @@
   #
   opt="--html -o $PACKAGE.html $split_arg $commonarg $htmlarg"
   cmd="$SETLANG $MAKEINFO $opt \"$srcfile\""
-  printf "\nGenerating html by $split... ($cmd)\n"
+  printf "\nGenerating html by %s... (%s)\n" "$split" "$cmd"
   eval "$cmd"
   split_html_dir=$PACKAGE.html
   copy_images $split_html_dir/ $split_html_dir/*.html
@@ -398,7 +398,7 @@
 else # use texi2html:
   opt="--output $PACKAGE.html $commonarg $htmlarg"
   cmd="$SETLANG $TEXI2HTML $opt \"$srcfile\""
-  printf "\nGenerating monolithic html with texi2html... ($cmd)\n"
+  printf "\nGenerating monolithic html with texi2html... (%s)\n" "$cmd"
   rm -rf $PACKAGE.html  # in case a directory is left over
   eval "$cmd"
   html_mono_size=`calcsize $PACKAGE.html`
@@ -416,11 +416,49 @@
 printf "\nMaking .tar.gz for sources...\n"
 d=`dirname $srcfile`
 (
-  cd "$d"
-  srcfiles=`ls -d *.texinfo *.texi *.txi *.eps $source_extra 2>/dev/null` || true
-  tar czfh "$abs_outdir/$PACKAGE.texi.tar.gz" $srcfiles
-  ls -l "$abs_outdir/$PACKAGE.texi.tar.gz"
-)
+  cd "$d" || exit
+
+  # Set PATS to a list of globbing patterns that expand to
+  # file names to be put into the .tar.gz for sources.
+  # Omit patterns that do not expand to file names.
+  pats=
+
+  if case `$MAKEINFO --version | sed -e 's/^^0-9*//' -e 1q` in \
+       1-6* | 7.01*) false;; \
+       *) true;; \
+     esac \
+  ; then
+
+    for pat in '*.eps'; do
+      for file in $pat; do
+        test "$file" = "$pat" && test ! -e "$file" || pats="$pats $pat"
+        break
+      done
+    done
+
+    # if $MAKEINFO is recent enough, use --trace-includes on the
+    # $srcfile to get the included files of the targeted manual only
+    base=`basename "$srcfile"`
+
+    cmd="$SETLANG $MAKEINFO $commonarg --trace-includes \"$base\""
+    eval "$cmd" \
+    | tar -czhf "$abs_outdir/$PACKAGE.texi.tar.gz" \
+        --verbatim-files-from -T- -- "$base" $pats \
+        ${source_extra+"$source_extra"} \
+    && ls -l "$abs_outdir/$PACKAGE.texi.tar.gz"
+  else
+    for pat in '*.texinfo' '*.texi' '*.txi' '*.eps'; do
+     for file in $pat; do
+       test "$file" = "$pat" && test ! -e "$file" || pats="$pats $pat"
+       break
+      done
+    done
+
+    tar -czhf "$abs_outdir/$PACKAGE.texi.tar.gz" \
+       -- $pats ${source_extra+"$source_extra"} \
+    && ls -l "$abs_outdir/$PACKAGE.texi.tar.gz"
+  fi
+) || exit
 texi_tgz_size=`calcsize "$outdir/$PACKAGE.texi.tar.gz"`
 
 # &#xc;
@@ -428,7 +466,7 @@
 if test -n "$docbook"; then
   opt="-o - --docbook $commonarg"
   cmd="$SETLANG $MAKEINFO $opt \"$srcfile\" >${srcdir}/$PACKAGE-db.xml"
-  printf "\nGenerating docbook XML... ($cmd)\n"
+  printf "\nGenerating docbook XML... (%s)\n" "$cmd"
   eval "$cmd"
   docbook_xml_size=`calcsize $PACKAGE-db.xml`
   gzip -f -9 -c $PACKAGE-db.xml >"$outdir/$PACKAGE-db.xml.gz"
@@ -438,7 +476,7 @@
   split_html_db_dir=html_node_db
   opt="$commonarg -o $split_html_db_dir"
   cmd="$DOCBOOK2HTML $opt \"${outdir}/$PACKAGE-db.xml\""
-  printf "\nGenerating docbook HTML... ($cmd)\n"
+  printf "\nGenerating docbook HTML... (%s)\n" "$cmd"
   eval "$cmd"
   (
     cd ${split_html_db_dir} || exit 1
@@ -451,26 +489,40 @@
   rmdir ${split_html_db_dir}
 
   cmd="$DOCBOOK2TXT \"${outdir}/$PACKAGE-db.xml\""
-  printf "\nGenerating docbook ASCII... ($cmd)\n"
+  printf "\nGenerating docbook ASCII... (%s)\n" "$cmd"
   eval "$cmd"
   docbook_ascii_size=`calcsize $PACKAGE-db.txt`
   mv $PACKAGE-db.txt "$outdir/"
 
   cmd="$DOCBOOK2PDF \"${outdir}/$PACKAGE-db.xml\""
-  printf "\nGenerating docbook PDF... ($cmd)\n"
+  printf "\nGenerating docbook PDF... (%s)\n" "$cmd"
   eval "$cmd"
   docbook_pdf_size=`calcsize $PACKAGE-db.pdf`
   mv $PACKAGE-db.pdf "$outdir/"
 fi
 
 # &#xc;
-printf "\nMaking index.html for $PACKAGE...\n"
+printf "\nMaking index.html for %s...\n" "$PACKAGE"
 if test -z "$use_texi2html"; then
-  CONDS="/%%IF  *HTML_SECTION%%/,/%%ENDIF  *HTML_SECTION%%/d;\
-         /%%IF  *HTML_CHAPTER%%/,/%%ENDIF  *HTML_CHAPTER%%/d"
+  if test x$split = xnode; then
+    CONDS="/%%IF  *HTML_NODE%%/d;/%%ENDIF  *HTML_NODE%%/d;\
+           /%%IF  *HTML_CHAPTER%%/,/%%ENDIF  *HTML_CHAPTER%%/d;\
+           /%%IF  *HTML_SECTION%%/,/%%ENDIF  *HTML_SECTION%%/d;"
+  elif test x$split = xchapter; then
+    CONDS="/%%IF  *HTML_CHAPTER%%/d;/%%ENDIF  *HTML_CHAPTER%%/d;\
+           /%%IF  *HTML_SECTION%%/,/%%ENDIF  *HTML_SECTION%%/d;\
+           /%%IF  *HTML_NODE%%/,/%%ENDIF  *HTML_NODE%%/d;"
+  elif test x$split = xsection; then
+    CONDS="/%%IF  *HTML_SECTION%%/d;/%%ENDIF  *HTML_SECTION%%/d;\
+           /%%IF  *HTML_CHAPTER%%/,/%%ENDIF  *HTML_CHAPTER%%/d;\
+           /%%IF  *HTML_NODE%%/,/%%ENDIF  *HTML_NODE%%/d;"
+  else
+    CONDS="/%%IF.*%%/d;/%%ENDIF.*%%/d;" # invalid split argument
+  fi
 else
-  # should take account of --split here.
-  CONDS="/%%ENDIF.*%%/d;/%%IF  *HTML_SECTION%%/d;/%%IF  *HTML_CHAPTER%%/d"
+  # for texi2html, we do not take account of --split and simply output
+  # all variants
+  CONDS="/%%IF.*%%/d;/%%ENDIF.*%%/d;"
 fi
 
 curdate=`$SETLANG date '+%B %d, %Y'`
@@ -503,7 +555,7 @@
 echo "Done, see $outdir/ subdirectory for new files."
 
 # Local variables:
-# eval: (add-hook 'before-save-hook 'time-stamp)
+# eval: (add-hook 'before-save-hook 'time-stamp nil t)
 # time-stamp-start: "scriptversion="
 # time-stamp-format: "%:y-%02m-%02d.%02H"
 # time-stamp-end: "$"

_service:tar_scm:automake-1.16.5.tar.xz/lib/gendocs_template -> _service:tar_scm:automake-1.17.tar.xz/lib/gendocs_template Changed

@@ -2,7 +2,7 @@
 
 
 
+     with the webmasters first.  -->
 </div>
 
 <div id="footer">
@@ -87,7 +89,7 @@
 to <a href="mailto:%%EMAIL%%">&lt;%%EMAIL%%&gt;</a>.</p>
 </div>
 
-<p>Copyright &copy; 2020 Free Software Foundation, Inc.</p>
+<p>Copyright &copy; 2023 Free Software Foundation, Inc.</p>
 
 <p>This page is licensed under a <a rel="license"
 href="https://creativecommons.org/licenses/by-nd/3.0/us/">Creative

_service:tar_scm:automake-1.16.5.tar.xz/lib/gitlog-to-changelog -> _service:tar_scm:automake-1.17.tar.xz/lib/gitlog-to-changelog Changed

@@ -3,7 +3,7 @@
 
 # Convert git log output to ChangeLog format.
 
-# Copyright (C) 2008-2021 Free Software Foundation, Inc.
+# Copyright (C) 2008-2024 Free Software Foundation, Inc.
 #
 # This program is free software: you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -20,7 +20,7 @@
 #
 # Written by Jim Meyering
 
-# This is a prologue that allows to run a perl script as an executable
+# This is a prologue that allows running a perl script as an executable
 # on systems that are compliant to a POSIX version before POSIX:2017.
 # On such systems, the usual invocation of an executable through execlp()
 # or execvp() fails with ENOEXEC if it is a script that does not start
@@ -35,7 +35,7 @@
 eval 'exec perl -wSx "$0" "$@"'
      if 0;
 
-my $VERSION = '2021-02-24 23:42'; # UTC
+my $VERSION = '2024-07-04 10:56'; # UTC
 # The definition above must lie within the first 8 lines in order
 # for the Emacs time-stamp write hook (at end) to update it.
 # If you change this file with Emacs, please let the write hook
@@ -97,6 +97,7 @@
    --strip-cherry-pick  remove data inserted by "git cherry-pick";
                   this includes the "cherry picked from commit ..." line,
                   and the possible final "Conflicts:" paragraph.
+   --commit-timezone  use dates respecting the timezone commits were made in.
    --help       display this help and exit
    --version    output version information and exit
 
@@ -247,6 +248,7 @@
   my $ignore_line;
   my $strip_tab = 0;
   my $strip_cherry_pick = 0;
+  my $commit_timezone = 0;
   my $srcdir;
   GetOptions
     (
@@ -262,6 +264,7 @@
      'ignore-line=s' => \$ignore_line,
      'strip-tab' => \$strip_tab,
      'strip-cherry-pick' => \$strip_cherry_pick,
+     'commit-timezone' => \$commit_timezone,
      'srcdir=s' => \$srcdir,
     ) or usage 1;
 
@@ -274,10 +277,12 @@
   # that makes a correction in the log or attribution of that commit.
   my $amend_code = defined $amend_file ? parse_amend_file $amend_file : {};
 
+  my $commit_time_format = $commit_timezone ? '%cI' : '%ct';
   my @cmd = ('git',
              git_dir_option $srcdir,
              qw(log --log-size),
-             '--pretty=format:%H:%ct  %an  <%ae>%n%n'.$format_string, @ARGV);
+             ("--pretty=format:%H:$commit_time_format"
+              . '  %an  <%ae>%n%n'.$format_string, @ARGV));
   open PIPE, '-|', @cmd
     or die ("$ME: failed to run '". quoted_cmd (@cmd) ."': $!\n"
             . "(Is your Git too old?  Version 1.5.1 or later is required.)\n");
@@ -350,17 +355,31 @@
       my $author_line = shift @line;
       defined $author_line
         or die "$ME:$.: unexpected EOF\n";
-      $author_line =~ /^(\d+)  (.*>)$/
+      $author_line =~ /^(\S+)  (.*>)$/
         or die "$ME:$.: Invalid line "
           . "(expected date/author/email):\n$author_line\n";
 
+      # Author  <email>
+      my $author = $2;
+
+      my $commit_date = $1;
+      if (! $commit_timezone)
+        {
+          # Seconds since the Epoch.
+          $commit_date = strftime "%Y-%m-%d", localtime ($commit_date);
+        }
+      else
+        {
+          # ISO 8601 date.
+          $commit_date =~ s/T.*$//;
+        }
+
       # Format 'Copyright-paperwork-exempt: Yes' as a standard ChangeLog
-      # `(tiny change)' annotation.
+      # '(tiny change)' annotation.
       my $tiny = (grep (/^(?:Copyright-paperwork-exempt|Tiny-change):\s+Yyes$/, @line)
                   ? '  (tiny change)' : '');
 
-      my $date_line = sprintf "%s  %s$tiny\n",
-        strftime ("%Y-%m-%d", localtime ($1)), $2;
+      my $date_line = "$commit_date  $author$tiny\n";
 
       my @coauthors = grep /^Co-authored-by:.*$/, @line;
       # Omit meta-data lines we've already interpreted.
@@ -495,7 +514,7 @@
 
   # Complain about any unused entry in the --amend=F specified file.
   my $fail = 0;
-  foreach my $sha (keys %$amend_code)
+  foreach my $sha (sort keys %$amend_code)
     {
       warn "$ME:$amend_file: unused entry: $sha\n";
       $fail = 1;
@@ -507,7 +526,7 @@
 # Local Variables:
 # mode: perl
 # indent-tabs-mode: nil
-# eval: (add-hook 'before-save-hook 'time-stamp)
+# eval: (add-hook 'before-save-hook 'time-stamp nil t)
 # time-stamp-line-limit: 50
 # time-stamp-start: "my $VERSION = '"
 # time-stamp-format: "%:y-%02m-%02d %02H:%02M"

_service:tar_scm:automake-1.16.5.tar.xz/lib/gnupload -> _service:tar_scm:automake-1.17.tar.xz/lib/gnupload Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/install-sh -> _service:tar_scm:automake-1.17.tar.xz/lib/install-sh Changed

@@ -1,7 +1,7 @@
 #!/bin/sh
 # install - install a program, script, or datafile
 
-scriptversion=2020-11-14.01; # UTC
+scriptversion=2024-06-19.01; # UTC
 
 # This originates from X11R5 (mit/util/scripts/install.sh), which was
 # later released in X11R6 (xc/config/util/install.sh) with the
@@ -124,9 +124,9 @@
 
 If -S is not specified, no backups are attempted.
 
-Email bug reports to bug-automake@gnu.org.
-Automake home page: https://www.gnu.org/software/automake/
-"
+Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>."
 
 while test $# -ne 0; do
   case $1 in
@@ -170,7 +170,7 @@
 
     -T) is_target_a_directory=never;;
 
-    --version) echo "$0 $scriptversion"; exit $?;;
+    --version) echo "$0 (GNU Automake) $scriptversion"; exit $?;;
 
     --) shift
         break;;
@@ -345,7 +345,7 @@
 	' 0
 
 	# Because "mkdir -p" follows existing symlinks and we likely work
-	# directly in world-writeable /tmp, make sure that the '$tmpdir'
+	# directly in world-writable /tmp, make sure that the '$tmpdir'
 	# directory is successfully created first before we actually test
 	# 'mkdir -p'.
 	if (umask $mkdir_umask &&
@@ -353,7 +353,7 @@
 	    exec $mkdirprog $mkdir_mode -p -- "$tmpdir/a/b") >/dev/null 2>&1
 	then
 	  if test -z "$dir_arg" || {
-	       # Check for POSIX incompatibilities with -m.
+	       # Check for POSIX incompatibility with -m.
 	       # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
 	       # other-writable bit of parent directory when it shouldn't.
 	       # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.

_service:tar_scm:automake-1.16.5.tar.xz/lib/local.mk -> _service:tar_scm:automake-1.17.tar.xz/lib/local.mk Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/mdate-sh -> _service:tar_scm:automake-1.17.tar.xz/lib/mdate-sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/missing -> _service:tar_scm:automake-1.17.tar.xz/lib/missing Changed

@@ -1,9 +1,11 @@
 #! /bin/sh
-# Common wrapper for a few potentially missing GNU programs.
+# Common wrapper for a few potentially missing GNU and other programs.
 
-scriptversion=2018-03-07.03; # UTC
+scriptversion=2024-06-07.14; # UTC
 
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# shellcheck disable=SC2006,SC2268 # we must support pre-POSIX shells
+
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 # Originally written by Fran,cois Pinard <pinard@iro.umontreal.ca>, 1996.
 
 # This program is free software; you can redistribute it and/or modify
@@ -54,18 +56,20 @@
   -v, --version   output version information and exit
 
 Supported PROGRAM values:
-  aclocal   autoconf  autoheader   autom4te  automake  makeinfo
-  bison     yacc      flex         lex       help2man
+aclocal autoconf autogen  autoheader autom4te automake autoreconf
+bison   flex     help2man lex        makeinfo perl     yacc
 
 Version suffixes to PROGRAM as well as the prefixes 'gnu-', 'gnu', and
 'g' are ignored when checking the name.
 
-Send bug reports to <bug-automake@gnu.org>."
+Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>."
     exit $?
     ;;
 
   -v|--v|--ve|--ver|--vers|--versi|--versio|--version)
-    echo "missing $scriptversion (GNU Automake)"
+    echo "missing (GNU Automake) $scriptversion"
     exit $?
     ;;
 
@@ -108,7 +112,7 @@
 program_details ()
 {
   case $1 in
-    aclocal|automake)
+    aclocal|automake|autoreconf)
       echo "The '$1' program is part of the GNU Automake package:"
       echo "<$gnu_software_URL/automake>"
       echo "It also requires GNU Autoconf, GNU m4 and Perl in order to run:"
@@ -123,6 +127,9 @@
       echo "<$gnu_software_URL/m4/>"
       echo "<$perl_URL>"
       ;;
+    *)
+      :
+      ;;
   esac
 }
 
@@ -137,48 +144,55 @@
   printf '%s\n' "'$1' is $msg."
 
   configure_deps="'configure.ac' or m4 files included by 'configure.ac'"
+  autoheader_deps="'acconfig.h'"
+  automake_deps="'Makefile.am'"
+  aclocal_deps="'acinclude.m4'"
   case $normalized_program in
+    aclocal*)
+      echo "You should only need it if you modified $aclocal_deps or"
+      echo "$configure_deps."
+      ;;
     autoconf*)
-      echo "You should only need it if you modified 'configure.ac',"
-      echo "or m4 files included by it."
-      program_details 'autoconf'
+      echo "You should only need it if you modified $configure_deps."
+      ;;
+    autogen*)
+      echo "You should only need it if you modified a '.def' or '.tpl' file."
+      echo "You may want to install the GNU AutoGen package:"
+      echo "<$gnu_software_URL/autogen/>"
       ;;
     autoheader*)
-      echo "You should only need it if you modified 'acconfig.h' or"
+      echo "You should only need it if you modified $autoheader_deps or"
       echo "$configure_deps."
-      program_details 'autoheader'
       ;;
     automake*)
-      echo "You should only need it if you modified 'Makefile.am' or"
-      echo "$configure_deps."
-      program_details 'automake'
-      ;;
-    aclocal*)
-      echo "You should only need it if you modified 'acinclude.m4' or"
+      echo "You should only need it if you modified $automake_deps or"
       echo "$configure_deps."
-      program_details 'aclocal'
       ;;
-   autom4te*)
+    autom4te*)
       echo "You might have modified some maintainer files that require"
       echo "the 'autom4te' program to be rebuilt."
-      program_details 'autom4te'
+      ;;
+    autoreconf*)
+      echo "You should only need it if you modified $aclocal_deps or"
+      echo "$automake_deps or $autoheader_deps or $automake_deps or"
+      echo "$configure_deps."
       ;;
     bison*|yacc*)
       echo "You should only need it if you modified a '.y' file."
       echo "You may want to install the GNU Bison package:"
       echo "<$gnu_software_URL/bison/>"
       ;;
-    lex*|flex*)
-      echo "You should only need it if you modified a '.l' file."
-      echo "You may want to install the Fast Lexical Analyzer package:"
-      echo "<$flex_URL>"
-      ;;
     help2man*)
       echo "You should only need it if you modified a dependency" \
            "of a man page."
       echo "You may want to install the GNU Help2man package:"
       echo "<$gnu_software_URL/help2man/>"
     ;;
+    lex*|flex*)
+      echo "You should only need it if you modified a '.l' file."
+      echo "You may want to install the Fast Lexical Analyzer package:"
+      echo "<$flex_URL>"
+      ;;
     makeinfo*)
       echo "You should only need it if you modified a '.texi' file, or"
       echo "any other file indirectly affecting the aspect of the manual."
@@ -189,6 +203,12 @@
       echo "want to install GNU make:"
       echo "<$gnu_software_URL/make/>"
       ;;
+    perl*)
+      echo "You should only need it to run GNU Autoconf, GNU Automake, "
+      echo "  assorted other tools, or if you modified a Perl source file."
+      echo "You may want to install the Perl 5 language interpreter:"
+      echo "<$perl_URL>"
+      ;;
     *)
       echo "You might have modified some files without having the proper"
       echo "tools for further handling them.  Check the 'README' file, it"
@@ -197,6 +217,7 @@
       echo "case some other package contains this missing '$1' program."
       ;;
   esac
+  program_details "$normalized_program"
 }
 
 give_advice "$1" | sed -e '1s/^/WARNING: /' \

_service:tar_scm:automake-1.16.5.tar.xz/lib/mkinstalldirs -> _service:tar_scm:automake-1.17.tar.xz/lib/mkinstalldirs Changed

_service:tar_scm:automake-1.16.5.tar.xz/lib/py-compile -> _service:tar_scm:automake-1.17.tar.xz/lib/py-compile Changed

@@ -1,9 +1,9 @@
 #!/bin/sh
 # py-compile - Compile a Python program
 
-scriptversion=2021-02-27.01; # UTC
+scriptversion=2024-06-19.01; # UTC
 
-# Copyright (C) 2000-2021 Free Software Foundation, Inc.
+# Copyright (C) 2000-2024 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -62,22 +62,30 @@
       ;;
     -h|--help)
       cat <<\EOF
-Usage: py-compile --help --version --basedir DIR --destdir DIR FILES..."
+Usage: py-compile options FILES...
 
 Byte compile some python scripts FILES.  Use --destdir to specify any
 leading directory path to the FILES that you don't want to include in the
 byte compiled file.  Specify --basedir for any additional path information you
 do want to be shown in the byte compiled file.
 
+Options:
+  --basedir DIR   Prefix all FILES with DIR, and include in error messages.
+  --destdir DIR   Prefix all FILES with DIR before compiling.
+  -v, --version   Display version information.
+  -h, --help      This help screen.
+
 Example:
   py-compile --destdir /tmp/pkg-root --basedir /usr/share/test test.py test2.py
 
 Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>.
 EOF
       exit $?
       ;;
     -v|--version)
-      echo "$me $scriptversion"
+      echo "$me (GNU Automake) $scriptversion"
       exit $?
       ;;
     --)
@@ -94,8 +102,7 @@
   shift
 done
 
-files=$*
-if test -z "$files"; then
+if test $# -eq 0; then
   usage_error "no files given"
 fi
 
@@ -115,68 +122,116 @@
   filetrans="filepath = os.path.normpath('$destdir' + os.sep + path)"
 fi
 
-python_major=`$PYTHON -V 2>&1 | sed -e 's/.* //;s/\..*$//;1q'`
+python_major=`$PYTHON -c 'import sys; print(sys.version_info0)'`
 if test -z "$python_major"; then
-  echo "$me: could not determine $PYTHON major version, guessing 3" >&2
-  python_major=3
+  usage_error "could not determine $PYTHON major version"
 fi
 
-# The old way to import libraries was deprecated.
-if test "$python_major" -le 2; then
-  import_lib=imp
-  import_test="hasattr(imp, 'get_tag')"
-  import_call=imp.cache_from_source
-  import_arg2=', False' # needed in one call and not the other
-else
-  import_lib=importlib
-  import_test="hasattr(sys.implementation, 'cache_tag')"
-  import_call=importlib.util.cache_from_source
-  import_arg2=
-fi
+case $python_major in
+01)
+  usage_error "python version 0.x and 1.x not supported"
+  ;;
+esac
 
-$PYTHON -c "
-import sys, os, py_compile, $import_lib
+python_minor=`$PYTHON -c 'import sys; print(sys.version_info1)'`
+
+# NB: When adding support for newer versions, prefer copying & adding new cases
+# rather than try to keep things merged with shell variables.
 
-files = '''$files'''
+# First byte compile (no optimization) all the modules.
+# This works for all currently known Python versions.
+$PYTHON -c "
+import sys, os, py_compile
+
+try:
+    import importlib
+except ImportError:
+    importlib = None
+
+# importlib.util.cache_from_source was added in 3.4
+if (
+        hasattr(importlib, 'util')
+        and hasattr(importlib.util, 'cache_from_source')
+):
+    destpath = importlib.util.cache_from_source
+else:
+    destpath = lambda filepath: filepath + 'c'
 
 sys.stdout.write('Byte-compiling python modules...\n')
-for file in files.split():
+for file in sys.argv1::
     $pathtrans
     $filetrans
-    if not os.path.exists(filepath) or not (len(filepath) >= 3
-                                            and filepath-3: == '.py'):
-	    continue
-    sys.stdout.write(file)
+    if (
+            not os.path.exists(filepath)
+            or not (len(filepath) >= 3 and filepath-3: == '.py')
+     ):
+        continue
+    sys.stdout.write(file + ' ')
     sys.stdout.flush()
-    if $import_test:
-        py_compile.compile(filepath, $import_call(filepath), path)
-    else:
-        py_compile.compile(filepath, filepath + 'c', path)
-sys.stdout.write('\n')" || exit $?
+    py_compile.compile(filepath, destpath(filepath), path)
+sys.stdout.write('\n')" "$@" || exit $?
 
-# this will fail for python < 1.5, but that doesn't matter ...
+# Then byte compile w/optimization all the modules.
 $PYTHON -O -c "
-import sys, os, py_compile, $import_lib
-
-# pypy does not use .pyo optimization
-if hasattr(sys, 'pypy_translation_info'):
+import sys, os, py_compile
+
+try:
+    import importlib
+except ImportError:
+    importlib = None
+
+# importlib.util.cache_from_source was added in 3.4
+if (
+        hasattr(importlib, 'util')
+        and hasattr(importlib.util, 'cache_from_source')
+):
+    destpath = importlib.util.cache_from_source
+else:
+    destpath = lambda filepath: filepath + 'o'
+
+# pypy2 does not use .pyo optimization
+if sys.version_info.major <= 2 and hasattr(sys, 'pypy_translation_info'):
     sys.exit(0)
 
-files = '''$files'''
 sys.stdout.write('Byte-compiling python modules (optimized versions) ...\n')
-for file in files.split():
+for file in sys.argv1::
+    $pathtrans
+    $filetrans
+    if (
+            not os.path.exists(filepath)
+            or not (len(filepath) >= 3 and filepath-3: == '.py')
+    ):
+        continue
+    sys.stdout.write(file + ' ')
+    sys.stdout.flush()
+    py_compile.compile(filepath, destpath(filepath), path)
+sys.stdout.write('\n')" "$@" 2>/dev/null || exit $?
+
+# Then byte compile w/more optimization.
+# Only do this for Python 3.5+, see https://bugs.gnu.org/38043 for background.
+case $python_major.$python_minor in
+2.*|3.0-4)
+  ;;
+*)
+  $PYTHON -OO -c "
+import sys, os, py_compile, importlib
+
+sys.stdout.write('Byte-compiling python modules (more optimized versions)'
+                 ' ...\n')
+for file in sys.argv1::
     $pathtrans
     $filetrans
-    if not os.path.exists(filepath) or not (len(filepath) >= 3
-                                            and filepath-3: == '.py'):
-	    continue
-    sys.stdout.write(file)
+    if (
+            not os.path.exists(filepath)
+            or not (len(filepath) >= 3 and filepath-3: == '.py')
+    ):
+        continue
+    sys.stdout.write(file + ' ')
     sys.stdout.flush()
-    if $import_test:
-        py_compile.compile(filepath, $import_call(filepath$import_arg2), path)
-    else:
-        py_compile.compile(filepath, filepath + 'o', path)
-sys.stdout.write('\n')" 2>/dev/null || exit $?
+    py_compile.compile(filepath, importlib.util.cache_from_source(filepath), path)
+sys.stdout.write('\n')" "$@" 2>/dev/null || exit $?
+  ;;
+esac
 
 # Local Variables:
 # mode: shell-script

_service:tar_scm:automake-1.16.5.tar.xz/lib/tap-driver.sh -> _service:tar_scm:automake-1.17.tar.xz/lib/tap-driver.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -23,7 +23,7 @@
 # bugs to <bug-automake@gnu.org> or send patches to
 # <automake-patches@gnu.org>.
 
-scriptversion=2013-12-23.17; # UTC
+scriptversion=2024-06-19.01; # UTC
 
 # Make unconditional expansion of undefined variables an error.  This
 # helps a lot in preventing typo-related bugs.
@@ -48,12 +48,16 @@
 {
   cat <<END
 Usage:
-  tap-driver.sh --test-name=NAME --log-file=PATH --trs-file=PATH
-                --expect-failure={yes|no} --color-tests={yes|no}
-                --enable-hard-errors={yes|no} --ignore-exit
-                --diagnostic-string=STRING --merge|--no-merge
+  tap-driver.sh --test-name NAME --log-file PATH --trs-file PATH
+                --expect-failure {yes|no} --color-tests {yes|no}
+                --enable-hard-errors {yes|no} --ignore-exit
+                --diagnostic-string STRING --merge|--no-merge
                 --comments|--no-comments -- TEST-COMMAND
 The '--test-name', '-log-file' and '--trs-file' options are mandatory.
+
+Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>.
 END
 }
 
@@ -71,7 +75,7 @@
 while test $# -gt 0; do
   case $1 in
   --help) print_usage; exit $?;;
-  --version) echo "$me $scriptversion"; exit $?;;
+  --version) echo "$me (GNU Automake) $scriptversion"; exit $?;;
   --test-name) test_name=$2; shift;;
   --log-file) log_file=$2; shift;;
   --trs-file) trs_file=$2; shift;;
@@ -124,7 +128,7 @@
     # problems with Korn shells.  Some Korn shells are known to propagate
     # to themselves signals that have killed a child process they were
     # waiting for; this is done at least for SIGINT (and usually only for
-    # it, in truth).  Without the `trap' below, such a behaviour could
+    # it, in truth).  Without the `trap' below, such a behavior could
     # cause a premature exit in the current subshell, e.g., in case the
     # test command it runs gets terminated by a SIGINT.  Thus, the awk
     # script we are piping into would never seen the exit status it
@@ -462,8 +466,8 @@
     # We used to report an "abnormal termination" here, but some Korn
     # shells, when a child process die due to signal number n, can leave
     # in $? an exit status of 256+n instead of the more standard 128+n.
-    # Apparently, both behaviours are allowed by POSIX (2008), so be
-    # prepared to handle them both.  See also Austing Group report ID
+    # Apparently, both behaviors are allowed by POSIX (2008), so be
+    # prepared to handle them both.  See also Austin Group report ID
     # 0000051 <http://www.austingroupbugs.net/view.php?id=51>
     exit_details = sprintf(" (terminated by signal %d?)", status - 256)
   else
@@ -578,7 +582,7 @@
     # Older versions of prove and TAP::Harness (e.g., 3.17) did not
     # recognize a "Bail out!" directive when preceded by leading
     # whitespace, but more modern versions (e.g., 3.23) do.  So we
-    # emulate the latter, "more modern" behaviour.
+    # emulate the latter, "more modern" behavior.
     else if ($0 ~ /^ \t*Bail out!/)
       {
         bailed_out = 1
@@ -592,7 +596,7 @@
           bailout_message = bailout_message " " $0
         testsuite_error(bailout_message)
       }
-    # Maybe we have too look for dianogtic comments too.
+    # Maybe we have to look for diagnostic comments too.
     else if (comments != 0)
       {
         comment = extract_tap_comment($0);

_service:tar_scm:automake-1.16.5.tar.xz/lib/test-driver -> _service:tar_scm:automake-1.17.tar.xz/lib/test-driver Changed

@@ -1,9 +1,9 @@
 #! /bin/sh
 # test-driver - basic testsuite driver script.
 
-scriptversion=2018-03-07.03; # UTC
+scriptversion=2024-06-19.01; # UTC
 
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -44,11 +44,16 @@
 Usage:
   test-driver --test-name NAME --log-file PATH --trs-file PATH
               --expect-failure {yes|no} --color-tests {yes|no}
+              --collect-skipped-logs {yes|no}
               --enable-hard-errors {yes|no} --
               TEST-SCRIPT TEST-SCRIPT-ARGUMENTS
 
 The '--test-name', '--log-file' and '--trs-file' options are mandatory.
 See the GNU Automake documentation for information.
+
+Report bugs to <bug-automake@gnu.org>.
+GNU Automake home page: <https://www.gnu.org/software/automake/>.
+General help using GNU software: <https://www.gnu.org/gethelp/>.
 END
 }
 
@@ -57,15 +62,17 @@
 trs_file=  # Where to save the metadata of the test run.
 expect_failure=no
 color_tests=no
+collect_skipped_logs=yes
 enable_hard_errors=yes
 while test $# -gt 0; do
   case $1 in
   --help) print_usage; exit $?;;
-  --version) echo "test-driver $scriptversion"; exit $?;;
+  --version) echo "test-driver (GNU Automake) $scriptversion"; exit $?;;
   --test-name) test_name=$2; shift;;
   --log-file) log_file=$2; shift;;
   --trs-file) trs_file=$2; shift;;
   --color-tests) color_tests=$2; shift;;
+  --collect-skipped-logs) collect_skipped_logs=$2; shift;;
   --expect-failure) expect_failure=$2; shift;;
   --enable-hard-errors) enable_hard_errors=$2; shift;;
   --) shift; break;;
@@ -121,7 +128,7 @@
 case $tweaked_estatus:$expect_failure in
   0:yes) col=$red res=XPASS recheck=yes gcopy=yes;;
   0:*)   col=$grn res=PASS  recheck=no  gcopy=no;;
-  77:*)  col=$blu res=SKIP  recheck=no  gcopy=yes;;
+  77:*)  col=$blu res=SKIP  recheck=no  gcopy=$collect_skipped_logs;;
   99:*)  col=$mgn res=ERROR recheck=yes gcopy=yes;;
   *:yes) col=$lgn res=XFAIL recheck=no  gcopy=yes;;
   *:*)   col=$red res=FAIL  recheck=yes gcopy=yes;;

_service:tar_scm:automake-1.16.5.tar.xz/lib/texinfo.tex -> _service:tar_scm:automake-1.17.tar.xz/lib/texinfo.tex Changed

@@ -3,9 +3,9 @@
 % Load plain if necessary, i.e., if running under initex.
 \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi
 %
-\def\texinfoversion{2021-04-25.21}
+\def\texinfoversion{2024-02-10.22}
 %
-% Copyright 1985, 1986, 1988, 1990-2021 Free Software Foundation, Inc.
+% Copyright 1985, 1986, 1988, 1990-2024 Free Software Foundation, Inc.
 %
 % This texinfo.tex file is free software: you can redistribute it and/or
 % modify it under the terms of the GNU General Public License as
@@ -58,12 +58,6 @@
 
 \message{Loading texinfo version \texinfoversion:}
 
-% If in a .fmt file, print the version number
-% and turn on active characters that we couldn't do earlier because
-% they might have appeared in the input file name.
-\everyjob{\message{Texinfo version \texinfoversion}%
-  \catcode`+=\active \catcode`\_=\active}
-
 % LaTeX's \typeout.  This ensures that the messages it is used for
 % are identical in format to the corresponding ones from latex/pdflatex.
 \def\typeout{\immediate\write17}%
@@ -241,9 +235,6 @@
 %
 \def\finalout{\overfullrule=0pt }
 
-\newdimen\outerhsize \newdimen\outervsize % set by the paper size routines
-\newdimen\topandbottommargin \topandbottommargin=.75in
-
 % Output a mark which sets \thischapter, \thissection and \thiscolor.
 % We dump everything together because we only have one kind of mark.
 % This works because we only use \botmark / \topmark, not \firstmark.
@@ -284,8 +275,7 @@
 % \topmark doesn't work for the very first chapter (after the title
 % page or the contents), so we use \firstmark there -- this gets us
 % the mark with the chapter defs, unless the user sneaks in, e.g.,
-% @setcolor (or @url, or @link, etc.) between @contents and the very
-% first @chapter.
+% @setcolor (or @url etc.) between @contents and the very first @chapter.
 \def\gettopheadingmarks{%
   \ifcase0\the\savedtopmark\fi
   \ifx\thischapter\empty \ifcase0\firstmark\fi \fi
@@ -317,16 +307,8 @@
 \newbox\footlinebox
 
 % When outputting the double column layout for indices, an output routine
-% is run several times, which hides the original value of \topmark.  This
-% can lead to a page heading being output and duplicating the chapter heading
-% of the index.  Hence, save the contents of \topmark at the beginning of
-% the output routine.  The saved contents are valid until we actually
-% \shipout a page.
-%
-% (We used to run a short output routine to actually set \topmark and
-% \firstmark to the right values, but if this was called with an empty page
-% containing whatsits for writing index entries, the whatsits would be thrown
-% away and the index auxiliary file would remain empty.)
+% is run several times, hiding the original value of \topmark.  Hence, save
+% \topmark at the beginning.
 %
 \newtoks\savedtopmark
 \newif\iftopmarksaved
@@ -351,15 +333,9 @@
   %
   \checkchapterpage
   %
-  % Retrieve the information for the headings from the marks in the page,
-  % and call Plain TeX's \makeheadline and \makefootline, which use the
-  % values in \headline and \footline.
-  %
-  % Common context changes for both heading and footing.
-  % Do this outside of the \shipout so @code etc. will be expanded in
-  % the headline as they should be, not taken literally (outputting ''code).
+  % Make the heading and footing.  \makeheadline and \makefootline
+  % use the contents of \headline and \footline.
   \def\commonheadfootline{\let\hsize=\txipagewidth \texinfochars}
-  %
   \ifodd\pageno \getoddheadingmarks \else \getevenheadingmarks \fi
   \global\setbox\headlinebox = \vbox{\commonheadfootline \makeheadline}%
   \ifodd\pageno \getoddfootingmarks \else \getevenfootingmarks \fi
@@ -450,42 +426,21 @@
 }
 
 % First remove any @comment, then any @c comment.  Pass the result on to
-% \argcheckspaces.
+% \argremovespace.
 \def\argremovecomment#1\comment#2\ArgTerm{\argremovec #1\c\ArgTerm}
-\def\argremovec#1\c#2\ArgTerm{\argcheckspaces#1\^^M\ArgTerm}
-
-% Each occurrence of `\^^M' or `<space>\^^M' is replaced by a single space.
-%
-% \argremovec might leave us with trailing space, e.g.,
+\def\argremovec#1\c#2\ArgTerm{\argremovespace#1$ $\ArgTerm}
+% \argremovec might leave us with trailing space, though; e.g.,
 %    @end itemize  @c foo
-% This space token undergoes the same procedure and is eventually removed
-% by \finishparsearg.
-%
-\def\argcheckspaces#1\^^M{\argcheckspacesX#1\^^M \^^M}
-\def\argcheckspacesX#1 \^^M{\argcheckspacesY#1\^^M}
-\def\argcheckspacesY#1\^^M#2\^^M#3\ArgTerm{%
-  \def\temp{#3}%
-  \ifx\temp\empty
-    % Do not use \next, perhaps the caller of \parsearg uses it; reuse \temp:
-    \let\temp\finishparsearg
-  \else
-    \let\temp\argcheckspaces
-  \fi
-  % Put the space token in:
-  \temp#1 #3\ArgTerm
-}
+% Note that the argument cannot contain the TeX $, as its catcode is
+% changed to \other when Texinfo source is read.
+\def\argremovespace#1 $#2\ArgTerm{\finishparsearg#1$\ArgTerm}
 
 % If a _delimited_ argument is enclosed in braces, they get stripped; so
 % to get _exactly_ the rest of the line, we had to prevent such situation.
-% We prepended an \empty token at the very beginning and we expand it now,
-% just before passing the control to \argtorun.
-% (Similarly, we have to think about #3 of \argcheckspacesY above: it is
-% either the null string, or it ends with \^^M---thus there is no danger
-% that a pair of braces would be stripped.
-%
-% But first, we have to remove the trailing space token.
-%
-\def\finishparsearg#1 \ArgTerm{\expandafter\argtorun\expandafter{#1}}
+% We prepended an \empty token at the very beginning and we expand it
+% just before passing the control to \next.
+% (But first, we have to remove the remaining $ or two.)
+\def\finishparsearg#1$#2\ArgTerm{\expandafter\argtorun\expandafter{#1}}
 
 
 % \parseargdef - define a command taking an argument on the line
@@ -547,7 +502,7 @@
 
 % ... but they get defined via ``\envdef\foo{...}'':
 \long\def\envdef#1#2{\def#1{\startenvironment#1#2}}
-\def\envparseargdef#1#2{\parseargdef#1{\startenvironment#1#2}}
+\long\def\envparseargdef#1#2{\parseargdef#1{\startenvironment#1#2}}
 
 % Check whether we're in the right environment:
 \def\checkenv#1{%
@@ -608,6 +563,9 @@
 % @/ allows a line break.
 \let\/=\allowbreak
 
+% @- allows explicit insertion of hyphenation points
+\def\-{\discretionary{\normaldash}{}{}}%
+
 % @. is an end-of-sentence period.
 \def\.{.\spacefactor=\endofsentencespacefactor\space}
 
@@ -617,21 +575,6 @@
 % @? is an end-of-sentence query.
 \def\?{?\spacefactor=\endofsentencespacefactor\space}
 
-% @frenchspacing on|off  says whether to put extra space after punctuation.
-%
-\def\onword{on}
-\def\offword{off}
-%
-\parseargdef\frenchspacing{%
-  \def\temp{#1}%
-  \ifx\temp\onword \plainfrenchspacing
-  \else\ifx\temp\offword \plainnonfrenchspacing
-  \else
-    \errhelp = \EMsimple
-    \errmessage{Unknown @frenchspacing option `\temp', must be on|off}%
-  \fi\fi
-}
-
 % @w prevents a word break.  Without the \leavevmode, @w at the
 % beginning of a paragraph, when TeX is still in vertical mode, would
 % produce a whole line of output instead of starting the paragraph.
@@ -725,32 +668,22 @@
   \dimen2 = \ht\strutbox
   \advance\dimen2 by \dp\strutbox
   \ifdim\dimen0 > \dimen2
-    %
-    % Do a \strut just to make the height of this box be normal, so the
-    % normal leading is inserted relative to the preceding line.
-    % And a page break here is fine.
-    \vtop to #1\mil{\strut\vfil}%
-    %
-    % TeX does not even consider page breaks if a penalty added to the
-    % main vertical list is 10000 or more.  But in order to see if the
-    % empty box we just added fits on the page, we must make it consider
-    % page breaks.  On the other hand, we don't want to actually break the
-    % page after the empty box.  So we use a penalty of 9999.
-    %
-    % There is an extremely small chance that TeX will actually break the
-    % page at this \penalty, if there are no other feasible breakpoints in
-    % sight.  (If the user is using lots of big @group commands, which
-    % almost-but-not-quite fill up a page, TeX will have a hard time doing
-    % good page breaking, for example.)  However, I could not construct an
-    % example where a page broke at this \penalty; if it happens in a real
-    % document, then we can reconsider our strategy.
+    % This is similar to the 'needspace' module in LaTeX.
+    % The first penalty allows a break if the end of the page is
+    % not too far away.  Following penalties and skips are discarded.
+    % Otherwise, require at least \dimen0 of vertical space.
+    %
+    % (We used to use a \vtop to reserve space, but this had spacing issues
+    % when followed by a section heading, as it was not a "discardable item".
+    % This also has the benefit of providing glue before the page break if
+    % there isn't enough space.)
+    \vskip0pt plus \dimen0
+    \penalty-100
+    \vskip0pt plus -\dimen0
+    \vskip \dimen0
     \penalty9999
-    %
-    % Back up by the size of the box, whether we did a page break or not.
-    \kern -#1\mil
-    %
-    % Do not allow a page break right after this kern.
-    \nobreak
+    \vskip -\dimen0
+    \penalty0\relax % this hides the above glue from \safewhatsit and \dobreak
   \fi
 }
 
@@ -1147,27 +1080,33 @@
 
 % Output page labels information.
 % See PDF reference v.1.7 p.594, section 8.3.1.
+% Page label ranges must be increasing.
 \ifpdf
 \def\pagelabels{%
   \def\title{0 << /P (T-) /S /D >>}%
-  \edef\roman{\the\romancount << /S /r >>}%
-  \edef\arabic{\the\arabiccount << /S /D >>}%
-  %
-  % Page label ranges must be increasing.  Remove any duplicates.
-  % (There is a slight chance of this being wrong if e.g. there is
-  % a @contents but no @titlepage, etc.)
-  %
-  \ifnum\romancount=0 \def\roman{}\fi
-  \ifnum\arabiccount=0 \def\title{}%
-  \else
-    \ifnum\romancount=\arabiccount \def\roman{}\fi
-  \fi
   %
-  \ifnum\romancount<\arabiccount
-    \pdfcatalog{/PageLabels << /Nums \title \roman \arabic  >> }\relax
-  \else
-    \pdfcatalog{/PageLabels << /Nums \title \arabic \roman  >> }\relax
-  \fi
+  % support @contents at very end of document
+  \ifnum\contentsendcount=\pagecount
+    \ifnum\arabiccount<\romancount
+      \pdfcatalog{/PageLabels << /Nums
+                  \title
+                   \the\arabiccount << /S /D >>
+                   \the\romancount << /S /r >>
+                   >> }\relax
+    \fi
+  % no contents in document
+  \else\ifnum\contentsendcount=0
+    \pdfcatalog{/PageLabels << /Nums
+                \title
+                 \the\arabiccount << /S /D >>
+                 >> }\relax
+  \else
+    \pdfcatalog{/PageLabels << /Nums
+                \title
+                 \the\romancount << /S /r >>
+                 \the\contentsendcount << /S /D >>
+                 >> }\relax
+  \fi\fi
 }
 \else
   \let\pagelabels\relax
@@ -1176,6 +1115,8 @@
 \newcount\pagecount \pagecount=0
 \newcount\romancount \romancount=0
 \newcount\arabiccount \arabiccount=0
+\newcount\contentsendcount \contentsendcount=0
+
 \ifpdf
   \let\ptxadvancepageno\advancepageno
   \def\advancepageno{%
@@ -1239,13 +1180,17 @@
   %
   % Set color, and create a mark which defines \thiscolor accordingly,
   % so that \makeheadline knows which color to restore.
+  \def\curcolor{0 0 0}%
   \def\setcolor#1{%
-    \xdef\currentcolordefs{\gdef\noexpand\thiscolor{#1}}%
-    \domark
-    \pdfsetcolor{#1}%
+    \ifx#1\curcolor\else
+      \xdef\currentcolordefs{\gdef\noexpand\thiscolor{#1}}%
+      \domark
+      \pdfsetcolor{#1}%
+      \xdef\curcolor{#1}%
+    \fi
   }
   %
-  \def\maincolor{\rgbBlack}
+  \let\maincolor\rgbBlack
   \pdfsetcolor{\maincolor}
   \edef\thiscolor{\maincolor}
   \def\currentcolordefs{}
@@ -1401,7 +1346,7 @@
   %
   % by default, use black for everything.
   \def\urlcolor{\rgbBlack}
-  \def\linkcolor{\rgbBlack}
+  \let\linkcolor\rgbBlack
   \def\endlink{\setcolor{\maincolor}\pdfendlink}
   %
   % Adding outlines to PDF; macros for calculating structure of outlines
@@ -1579,9 +1524,10 @@
     \next}
   \def\makelink{\addtokens{\toksB}%
     {\noexpand\pdflink{\the\toksC}}\toksC={}\global\countA=0}
-  \def\pdflink#1{%
+  \def\pdflink#1{\pdflinkpage{#1}{#1}}%
+  \def\pdflinkpage#1#2{%
     \startlink attr{/Border 0 0 0} goto name{\pdfmkpgn{#1}}
-    \setcolor{\linkcolor}#1\endlink}
+    \setcolor{\linkcolor}#2\endlink}
   \def\done{\edef\st{\global\noexpand\toksA={\the\toksB}}\st}
 \else
   % non-pdf mode
@@ -1828,10 +1774,11 @@
     \next}
   \def\makelink{\addtokens{\toksB}%
     {\noexpand\pdflink{\the\toksC}}\toksC={}\global\countA=0}
-  \def\pdflink#1{%
+  \def\pdflink#1{\pdflinkpage{#1}{#1}}%
+  \def\pdflinkpage#1#2{%
     \special{pdf:bann << /Border 0 0 0
       /Type /Annot /Subtype /Link /A << /S /GoTo /D (#1) >> >>}%
-    \setcolor{\linkcolor}#1\endlink}
+    \setcolor{\linkcolor}#2\endlink}
   \def\done{\edef\st{\global\noexpand\toksA={\the\toksB}}\st}
 %
   %
@@ -2176,6 +2123,11 @@
     \pdffontattr#1{/ToUnicode \the\pdflastobj\space 0 R}%
   }%
 \fi\fi
+%
+% This is what gets called when #5 of \setfont is empty.
+\let\cmap\gobble
+%
+% (end of cmaps)
 
 
 % Set the font macro #1 to the font named \fontprefix#2.
@@ -2191,11 +2143,10 @@
 \def\setfont#1#2#3#4#5{%
   \font#1=\fontprefix#2#3 scaled #4
   \csname cmap#5\endcsname#1%
+  \ifx#2\ttshape\hyphenchar#1=-1 \fi
+  \ifx#2\ttbshape\hyphenchar#1=-1 \fi
+  \ifx#2\ttslshape\hyphenchar#1=-1 \fi
 }
-% This is what gets called when #5 of \setfont is empty.
-\let\cmap\gobble
-%
-% (end of cmaps)
 
 % Use cm as the default font prefix.
 % To specify the font prefix, you must define \fontprefix
@@ -2558,7 +2509,7 @@
 \def\it{\fam=\itfam \setfontstyle{it}}
 \def\sl{\fam=\slfam \setfontstyle{sl}}
 \def\bf{\fam=\bffam \setfontstyle{bf}}\def\bfstylename{bf}
-\def\tt{\fam=\ttfam \setfontstyle{tt}}\def\ttstylename{tt}
+\def\tt{\fam=\ttfam \setfontstyle{tt}}
 
 % Texinfo sort of supports the sans serif font style, which plain TeX does not.
 % So we set up a \sf.
@@ -2586,34 +2537,30 @@
   \scriptfont\sffam=\sevensf
 }
 
-%
 
-% The font-changing commands (all called \...fonts) redefine the meanings
-% of \STYLEfont, instead of just \STYLE.  We do this because \STYLE needs
-% to also set the current \fam for math mode.  Our \STYLE (e.g., \rm)
-% commands hardwire \STYLEfont to set the current font.
-%
-% The fonts used for \ifont are for "math italics"  (\itfont is for italics
-% in regular text).  \syfont is also used in math mode only.
-%
-% Each font-changing command also sets the names \lsize (one size lower)
-% and \lllsize (three sizes lower).  These relative commands are used
-% in, e.g., the LaTeX logo and acronyms.
-%
-% This all needs generalizing, badly.
-%
+
+% \defineassignfonts{SIZE} -
+%   Define sequence \assignfontsSIZE, which switches between font sizes
+% by redefining the meanings of \STYLEfont.  (Just \STYLE additionally sets
+% the current \fam for math mode.)
+%
+\def\defineassignfonts#1{%
+  \expandafter\edef\csname assignfonts#1\endcsname{%
+    \let\noexpand\rmfont\csname #1rm\endcsname
+    \let\noexpand\itfont\csname #1it\endcsname
+    \let\noexpand\slfont\csname #1sl\endcsname
+    \let\noexpand\bffont\csname #1bf\endcsname
+    \let\noexpand\ttfont\csname #1tt\endcsname
+    \let\noexpand\smallcaps\csname #1sc\endcsname
+    \let\noexpand\sffont  \csname #1sf\endcsname
+    \let\noexpand\ifont   \csname #1i\endcsname
+    \let\noexpand\syfont  \csname #1sy\endcsname
+    \let\noexpand\ttslfont\csname #1ttsl\endcsname
+  }
+}
 
 \def\assignfonts#1{%
-  \expandafter\let\expandafter\rmfont\csname #1rm\endcsname
-  \expandafter\let\expandafter\itfont\csname #1it\endcsname
-  \expandafter\let\expandafter\slfont\csname #1sl\endcsname
-  \expandafter\let\expandafter\bffont\csname #1bf\endcsname
-  \expandafter\let\expandafter\ttfont\csname #1tt\endcsname
-  \expandafter\let\expandafter\smallcaps\csname #1sc\endcsname
-  \expandafter\let\expandafter\sffont  \csname #1sf\endcsname
-  \expandafter\let\expandafter\ifont   \csname #1i\endcsname
-  \expandafter\let\expandafter\syfont  \csname #1sy\endcsname
-  \expandafter\let\expandafter\ttslfont\csname #1ttsl\endcsname
+  \csname assignfonts#1\endcsname
 }
 
 \newif\ifrmisbold
@@ -2637,12 +2584,21 @@
    \csname\curfontstyle\endcsname
 }%
 
+% Define the font-changing commands (all called \...fonts).
+% Each font-changing command also sets the names \lsize (one size lower)
+% and \lllsize (three sizes lower).  These relative commands are used
+% in, e.g., the LaTeX logo and acronyms.
+%
+% Note: The fonts used for \ifont are for "math italics"  (\itfont is for
+% italics in regular text).  \syfont is also used in math mode only.
+%
 \def\definefontsetatsize#1#2#3#4#5{%
+  \defineassignfonts{#1}%
 \expandafter\def\csname #1fonts\endcsname{%
   \def\curfontsize{#1}%
   \def\lsize{#2}\def\lllsize{#3}%
   \csname rmisbold#5\endcsname
-  \assignfonts{#1}%
+  \csname assignfonts#1\endcsname
   \resetmathfonts
   \setleading{#4}%
 }}
@@ -2687,9 +2643,22 @@
 % Check if we are currently using a typewriter font.  Since all the
 % Computer Modern typewriter fonts have zero interword stretch (and
 % shrink), and it is reasonable to expect all typewriter fonts to have
-% this property, we can check that font parameter.
-%
-\def\ifmonospace{\ifdim\fontdimen3\font=0pt }
+% this property, we can check that font parameter. #1 is what to
+% print if we are indeed using \tt; #2 is what to print otherwise.
+\def\ifusingtt#1#2{\ifdim \fontdimen3\font=0pt #1\else #2\fi}
+
+% Same as above, but check for italic font.  Actually this also catches
+% non-italic slanted fonts since it is impossible to distinguish them from
+% italic fonts.  But since this is only used by $ and it uses \sl anyway
+% this is not a problem.
+\def\ifusingit#1#2{\ifdim \fontdimen1\font>0pt #1\else #2\fi}
+
+
+% Check if internal flag is clear, i.e. has not been @set.
+\def\ifflagclear#1#2#3{%
+  \expandafter\ifx\csname SET#1\endcsname\relax
+  #2\else#3\fi
+}
 
 {
 \catcode`\'=\active
@@ -2698,41 +2667,33 @@
 \gdef\setcodequotes{\let`\codequoteleft \let'\codequoteright}
 \gdef\setregularquotes{\let`\lq \let'\rq}
 }
+\setregularquotes
 
-% Allow an option to not use regular directed right quote/apostrophe
-% (char 0x27), but instead the undirected quote from cmtt (char 0x0d).
-% The undirected quote is ugly, so don't make it the default, but it
-% works for pasting with more pdf viewers (at least evince), the
-% lilypond developers report.  xpdf does work with the regular 0x27.
+% output for ' in @code
+% in tt font hex 0D (undirected) or 27 (curly right quote)
 %
 \def\codequoteright{%
-  \ifmonospace
-    \expandafter\ifx\csname SETtxicodequoteundirected\endcsname\relax
-      \expandafter\ifx\csname SETcodequoteundirected\endcsname\relax
-        '%
-      \else \char'15 \fi
-    \else \char'15 \fi
-   \else
-     '%
-   \fi
+  \ifusingtt
+      {\ifflagclear{txicodequoteundirected}%
+          {\ifflagclear{codequoteundirected}%
+              {'}%
+              {\char"0D }}%
+          {\char"0D }}%
+      {'}%
 }
-%
-% and a similar option for the left quote char vs. a grave accent.
-% Modern fonts display ASCII 0x60 as a grave accent, so some people like
-% the code environments to do likewise.
+
+% output for ` in @code
+% in tt font hex 12 (grave accent) or 60 (curly left quote)
+% \relax disables Spanish ligatures ?` and !` of \tt font.
 %
 \def\codequoteleft{%
-  \ifmonospace
-    \expandafter\ifx\csname SETtxicodequotebacktick\endcsname\relax
-      \expandafter\ifx\csname SETcodequotebacktick\endcsname\relax
-        % Knuth pp. 380,381,391
-        % \relax disables Spanish ligatures ?` and !` of \tt font.
-        \relax`%
-      \else \char'22 \fi
-    \else \char'22 \fi
-   \else
-     \relax`%
-   \fi
+  \ifusingtt
+      {\ifflagclear{txicodequotebacktick}%
+          {\ifflagclear{codequotebacktick}%
+              {\relax`}%
+              {\char"12 }}%
+          {\char"12 }}%
+      {\relax`}%
 }
 
 % Commands to set the quote options.
@@ -2750,7 +2711,7 @@
     \errmessage{Unknown @codequoteundirected value `\temp', must be on|off}%
   \fi\fi
 }
-%
+
 \parseargdef\codequotebacktick{%
   \def\temp{#1}%
   \ifx\temp\onword
@@ -2765,6 +2726,11 @@
   \fi\fi
 }
 
+% Turn them on by default
+\let\SETtxicodequoteundirected = t
+\let\SETtxicodequotebacktick = t
+
+
 % Knuth pp. 380,381,391, disable Spanish ligatures ?` and !` of \tt font.
 \def\noligaturesquoteleft{\relax\lq}
 
@@ -2779,15 +2745,16 @@
 \def\dosmartslant#1#2{%
   \ifusingtt
     {{\ttsl #2}\let\next=\relax}%
-    {\def\next{{#1#2}\futurelet\next\smartitaliccorrection}}%
+    {\def\next{{#1#2}\smartitaliccorrection}}%
   \next
 }
 \def\smartslanted{\dosmartslant\sl}
 \def\smartitalic{\dosmartslant\it}
 
-% Output an italic correction unless \next (presumed to be the following
-% character) is such as not to need one.
-\def\smartitaliccorrection{%
+% Output an italic correction unless the following character is such as
+% not to need one.
+\def\smartitaliccorrection{\futurelet\next\smartitaliccorrectionx}
+\def\smartitaliccorrectionx{%
   \ifx\next,%
   \else\ifx\next-%
   \else\ifx\next.%
@@ -2798,27 +2765,41 @@
   \aftersmartic
 }
 
-% Unconditional use \ttsl, and no ic.  @var is set to this for defuns.
-\def\ttslanted#1{{\ttsl #1}}
-
-% @cite is like \smartslanted except unconditionally use \sl.  We never want
-% ttsl for book titles, do we?
-\def\cite#1{{\sl #1}\futurelet\next\smartitaliccorrection}
+% @cite unconditionally uses \sl with \smartitaliccorrection.
+\def\cite#1{{\sl #1}\smartitaliccorrection}
 
+% @var unconditionally uses \sl.  This gives consistency for
+% parameter names whether they are in @def, @table @code or a
+% regular paragraph.
+%  To get ttsl font for @var when used in code context, @set txicodevaristt.
+% The \null is to reset \spacefactor.
 \def\aftersmartic{}
 \def\var#1{%
   \let\saveaftersmartic = \aftersmartic
   \def\aftersmartic{\null\let\aftersmartic=\saveaftersmartic}%
-  \smartslanted{#1}%
+  %
+  \ifflagclear{txicodevaristt}%
+    {\def\varnext{{{\sl #1}}\smartitaliccorrection}}%
+    {\def\varnext{\smartslanted{#1}}}%
+  \varnext
 }
 
+% To be removed after next release
+\def\SETtxicodevaristt{}% @set txicodevaristt
+
 \let\i=\smartitalic
 \let\slanted=\smartslanted
 \let\dfn=\smartslanted
 \let\emph=\smartitalic
 
-% Explicit font changes: @r, @sc, undocumented @ii.
-\def\r#1{{\rm #1}}              % roman font
+% @r for roman font, used for code comment
+\def\r#1{{%
+  \usenormaldash % get --, --- ligatures even if in @code
+  \defcharsdefault  % in case on def line
+  \rm #1}}
+{\catcode`-=\active \gdef\usenormaldash{\let-\normaldash}}
+
+% @sc, undocumented @ii.
 \def\sc#1{{\smallcaps#1}}       % smallcaps font
 \def\ii#1{{\it #1}}             % italic font
 
@@ -2829,12 +2810,8 @@
 % @sansserif, explicit sans.
 \def\sansserif#1{{\sf #1}}
 
-% We can't just use \exhyphenpenalty, because that only has effect at
-% the end of a paragraph.  Restore normal hyphenation at the end of the
-% group within which \nohyphenation is presumably called.
-%
-\def\nohyphenation{\hyphenchar\font = -1  \aftergroup\restorehyphenation}
-\def\restorehyphenation{\hyphenchar\font = `- }
+\newif\iffrenchspacing
+\frenchspacingfalse
 
 % Set sfcode to normal for the chars that usually have another value.
 % Can't use plain's \frenchspacing because it uses the `\x notation, and
@@ -2842,21 +2819,45 @@
 %
 \catcode`@=11
   \def\plainfrenchspacing{%
-    \sfcode`\.=\@m \sfcode`\?=\@m \sfcode`\!=\@m
-    \sfcode`\:=\@m \sfcode`\;=\@m \sfcode`\,=\@m
-    \def\endofsentencespacefactor{1000}% for @. and friends
+    \iffrenchspacing\else
+      \frenchspacingtrue
+      \sfcode`\.=\@m \sfcode`\?=\@m \sfcode`\!=\@m
+      \sfcode`\:=\@m \sfcode`\;=\@m \sfcode`\,=\@m
+      \def\endofsentencespacefactor{1000}% for @. and friends
+    \fi
   }
   \def\plainnonfrenchspacing{%
-    \sfcode`\.3000\sfcode`\?3000\sfcode`\!3000
-    \sfcode`\:2000\sfcode`\;1500\sfcode`\,1250
-    \def\endofsentencespacefactor{3000}% for @. and friends
+    \iffrenchspacing
+      \frenchspacingfalse
+       \sfcode`\.3000\sfcode`\?3000\sfcode`\!3000
+       \sfcode`\:2000\sfcode`\;1500\sfcode`\,1250
+       \def\endofsentencespacefactor{3000}% for @. and friends
+    \fi
   }
 \catcode`@=\other
 \def\endofsentencespacefactor{3000}% default
 
+% @frenchspacing on|off  says whether to put extra space after punctuation.
+%
+\def\onword{on}
+\def\offword{off}
+%
+\let\frenchspacingsetting\plainnonfrenchspacing % used in output routine
+\parseargdef\frenchspacing{%
+  \def\temp{#1}%
+  \ifx\temp\onword \let\frenchspacingsetting\plainfrenchspacing
+  \else\ifx\temp\offword \let\frenchspacingsetting\plainnonfrenchspacing
+  \else
+    \errhelp = \EMsimple
+    \errmessage{Unknown @frenchspacing option `\temp', must be on|off}%
+  \fi\fi
+  \frenchspacingsetting
+}
+
+
 % @t, explicit typewriter.
 \def\t#1{%
-  {\tt \plainfrenchspacing #1}%
+  {\tt \defcharsdefault \plainfrenchspacing #1}%
   \null
 }
 
@@ -2877,27 +2878,29 @@
     % Switch to typewriter.
     \tt
     %
-    % But `\ ' produces the large typewriter interword space.
+    % `\ ' produces the large typewriter interword space.
     \def\ {{\spaceskip = 0pt{} }}%
     %
-    % Turn off hyphenation.
-    \nohyphenation
-    %
     \plainfrenchspacing
     #1%
   }%
   \null % reset spacefactor to 1000
 }
 
-% We *must* turn on hyphenation at `-' and `_' in @code.
-% (But see \codedashfinish below.)
+% This is for LuaTeX: It is not sufficient to disable hyphenation at
+% explicit dashes by setting `\hyphenchar` to -1.
+\def\dashnobreak{%
+  \normaldash
+  \penalty 10000 }
+
+% We must turn on hyphenation at `-' and `_' in @code.
 % Otherwise, it is too hard to avoid overfull hboxes
 % in the Emacs manual, the Library manual, etc.
+% We explicitly allow hyphenation at these characters
+% using \discretionary.
 %
-% Unfortunately, TeX uses one parameter (\hyphenchar) to control
-% both hyphenation at - and hyphenation within words.
-% We must therefore turn them both off (\tclose does that)
-% and arrange explicitly to hyphenate at a dash. -- rms.
+% Hyphenation at - and hyphenation within words was turned off
+% by default for the tt fonts using the \hyphenchar parameter of TeX.
 {
   \catcode`\-=\active \catcode`\_=\active
   \catcode`\'=\active \catcode`\`=\active
@@ -2910,13 +2913,9 @@
      \let-\codedash
      \let_\codeunder
     \else
-     \let-\normaldash
+     \let-\dashnobreak
      \let_\realunder
     \fi
-    % Given -foo (with a single dash), we do not want to allow a break
-    % after the hyphen.
-    \global\let\codedashprev=\codedash
-    %
     \codex
   }
   %
@@ -2926,21 +2925,30 @@
     %
     % Now, output a discretionary to allow a line break, unless
     % (a) the next character is a -, or
-    % (b) the preceding character is a -.
+    % (b) the preceding character is a -, or
+    % (c) we are at the start of the string.
+    % In both cases (b) and (c), \codedashnobreak should be set to \codedash.
+    %
     % E.g., given --posix, we do not want to allow a break after either -.
     % Given --foo-bar, we do want to allow a break between the - and the b.
     \ifx\next\codedash \else
-      \ifx\codedashprev\codedash
+      \ifx\codedashnobreak\codedash
       \else \discretionary{}{}{}\fi
     \fi
     % we need the space after the = for the case when \next itself is a
     % space token; it would get swallowed otherwise.  As in @code{- a}.
-    \global\let\codedashprev= \next
+    \global\let\codedashnobreak= \next
   }
 }
 \def\normaldash{-}
 %
-\def\codex #1{\tclose{#1}\endgroup}
+\def\codex #1{\tclose{%
+  % Given -foo (with a single dash), we do not want to allow a break
+  % after the -.  \codedashnobreak is set to the first character in
+  % @code.
+  \futurelet\codedashnobreak\relax
+  #1%
+}\endgroup}
 
 \def\codeunder{%
   % this is all so @math{@code{var_name}+1} can work.  In math mode, _
@@ -3171,16 +3179,8 @@
 % Default is `distinct'.
 \kbdinputstyle distinct
 
-% @kbd is like @code, except that if the argument is just one @key command,
-% then @kbd has no effect.
-\def\kbd#1{{\def\look{#1}\expandafter\kbdsub\look??\par}}
-
-\def\xkey{\key}
-\def\kbdsub#1#2#3\par{%
-  \def\one{#1}\def\three{#3}\def\threex{??}%
-  \ifx\one\xkey\ifx\threex\three \key{#2}%
-  \else{\tclose{\kbdfont\setcodequotes\look}}\fi
-  \else{\tclose{\kbdfont\setcodequotes\look}}\fi
+\def\kbd#1{%
+  \tclose{\kbdfont\setcodequotes#1}%
 }
 
 % definition of @key that produces a lozenge.  Doesn't adjust to text size.
@@ -3193,14 +3193,9 @@
 %    \kern-0.4pt\hrule}%
 %  \kern-.06em\raise0.4pt\hbox{\angleright}}}}
 
-% definition of @key with no lozenge.  If the current font is already
-% monospace, don't change it; that way, we respect @kbdinputstyle.  But
-% if it isn't monospace, then use \tt.
-%
-\def\key#1{{\setregularquotes
-  \nohyphenation
-  \ifmonospace\else\tt\fi
-  #1}\null}
+% definition of @key with no lozenge.
+%
+\def\key#1{{\setregularquotes \tt #1}\null}
 
 % @clicksequence{File @click{} Open ...}
 \def\clicksequence#1{\begingroup #1\endgroup}
@@ -3403,8 +3398,8 @@
 \let\atchar=\@
 
 % @{ @} @lbracechar{} @rbracechar{} all generate brace characters.
-\def\lbracechar{{\ifmonospace\char123\else\ensuremath\lbrace\fi}}
-\def\rbracechar{{\ifmonospace\char125\else\ensuremath\rbrace\fi}}
+\def\lbracechar{{\ifusingtt{\char123}{\ensuremath\lbrace}}}
+\def\rbracechar{{\ifusingtt{\char125}{\ensuremath\rbrace}}}
 \let\{=\lbracechar
 \let\}=\rbracechar
 
@@ -3458,8 +3453,13 @@
        % Revert to plain's \scriptsize, which is 7pt.
        \count255=\the\fam $\fam\count255 \scriptstyle A$%
      \else
-       % For 11pt, we can use our lllsize.
-       \switchtolllsize A%
+       \ifx\curfontsize\smallword
+         % For footnotes and indices
+         \count255=\the\fam $\fam\count255 \scriptstyle A$%
+       \else
+         % For 11pt, we can use our lllsize.
+         \switchtolllsize A%
+       \fi
      \fi
      }%
      \vss
@@ -3467,6 +3467,7 @@
   \kern-.15em
   \TeX
 }
+\def\smallword{small}
 
 % Some math mode symbols.  Define \ensuremath to switch into math mode
 % unless we are already there.  Expansion tricks may not be needed here,
@@ -3545,7 +3546,7 @@
 
 % @pounds{} is a sterling sign, which Knuth put in the CM italic font.
 %
-\def\pounds{\ifmonospace{\ecfont\char"BF}\else{\it\$}\fi}
+\def\pounds{{\ifusingtt{\ecfont\char"BF}{\it\$}}}
 
 % @euro{} comes from a separate font, depending on the current style.
 % We use the free feym* fonts from the eurosym package by Henrik
@@ -3614,6 +3615,9 @@
 \def\quotedblbase{{\ecfont \char"12}}
 \def\quotesinglbase{{\ecfont \char"0D}}
 %
+\def\L{{\ecfont \char"8A}} % L with stroke
+\def\l{{\ecfont \char"AA}} % l with stroke
+%
 % This positioning is not perfect (see the ogonek LaTeX package), but
 % we have the precomposed glyphs for the most common cases.  We put the
 % tests to use those glyphs in the single \ogonek macro so we have fewer
@@ -3656,18 +3660,17 @@
   % hopefully nobody will notice/care.
   \edef\ecsize{\csname\curfontsize ecsize\endcsname}%
   \edef\nominalsize{\csname\curfontsize nominalsize\endcsname}%
-  \ifmonospace
-    % typewriter:
-    \font\thisecfont = #1ctt\ecsize \space at \nominalsize
-  \else
-    \ifx\curfontstyle\bfstylename
-      % bold:
-      \font\thisecfont = #1cb\ifusingit{i}{x}\ecsize \space at \nominalsize
-    \else
-      % regular:
-      \font\thisecfont = #1c\ifusingit{ti}{rm}\ecsize \space at \nominalsize
-    \fi
-  \fi
+  \ifusingtt
+      % typewriter:
+     {\font\thisecfont = #1ctt\ecsize \space at \nominalsize}%
+  % else
+     {\ifx\curfontstyle\bfstylename
+        % bold:
+        \font\thisecfont = #1cb\ifusingit{i}{x}\ecsize \space at \nominalsize
+      \else
+        % regular:
+        \font\thisecfont = #1c\ifusingit{ti}{rm}\ecsize \space at \nominalsize
+      \fi}%
   \thisecfont
 }
 
@@ -3683,7 +3686,10 @@
 
 % @textdegree - the normal degrees sign.
 %
-\def\textdegree{$^\circ$}
+\def\textdegree{%
+   \ifmmode ^\circ
+   \else {\tcfont \char 176}%
+   \fi}
 
 % Laurent Siebenmann reports \Orb undefined with:
 %  Textures 1.7.7 (preloaded format=plain 93.10.14)  (68K)  16 APR 2004 02:38
@@ -3700,11 +3706,11 @@
 % only change font for tt for correct kerning and to avoid using
 % \ecfont unless necessary.
 \def\quotedblleft{%
-  \ifmonospace{\ecfont\char"10}\else{\char"5C}\fi
+  \ifusingtt{{\ecfont\char"10}}{{\char"5C}}%
 }
 
 \def\quotedblright{%
-  \ifmonospace{\ecfont\char"11}\else{\char`\"}\fi
+  \ifusingtt{{\ecfont\char"11}}{{\char`\"}}%
 }
 
 
@@ -3729,13 +3735,14 @@
               want the contents after the title page.}}%
 
 \parseargdef\shorttitlepage{%
-  \begingroup \hbox{}\vskip 1.5in \chaprm \centerline{#1}%
-  \endgroup\page\hbox{}\page}
+  {\headingsoff \begingroup \hbox{}\vskip 1.5in \chaprm \centerline{#1}%
+  \endgroup\page\hbox{}\page}\pageone}
 
 \envdef\titlepage{%
   % Open one extra group, as we want to close it in the middle of \Etitlepage.
   \begingroup
     \parindent=0pt \textfonts
+    \headingsoff
     % Leave some space at the very top of the page.
     \vglue\titlepagetopglue
     % No rule at page bottom unless we print one at the top with @title.
@@ -3763,11 +3770,9 @@
     % If we use the new definition of \page, we always get a blank page
     % after the title page, which we certainly don't want.
     \oldpage
+    \pageone
   \endgroup
   %
-  % Need this before the \...aftertitlepage checks so that if they are
-  % in effect the toc pages will come out with page numbers.
-  \HEADINGSon
 }
 
 \def\finishtitlepage{%
@@ -3834,15 +3839,16 @@
 \newtoks\oddfootline     % footline on odd pages
 
 % Now make \makeheadline and \makefootline in Plain TeX use those variables
-\headline={{\textfonts\rm
+\headline={{\textfonts\rm\frenchspacingsetting
             \ifchapterpage
               \ifodd\pageno\the\oddchapheadline\else\the\evenchapheadline\fi
             \else
               \ifodd\pageno\the\oddheadline\else\the\evenheadline\fi
             \fi}}
 
-\footline={{\textfonts\rm \ifodd\pageno \the\oddfootline
-                            \else \the\evenfootline \fi}\HEADINGShook}
+\footline={{\textfonts\rm\frenchspacingsetting
+            \ifodd\pageno \the\oddfootline \else \the\evenfootline \fi}%
+           \HEADINGShook}
 \let\HEADINGShook=\relax
 
 % Commands to set those variables.
@@ -3935,46 +3941,37 @@
 }
 
 \def\HEADINGSoff{{\globaldefs=1 \headingsoff}} % global setting
-\HEADINGSoff  % it's the default
 
-% When we turn headings on, set the page number to 1.
+% Set the page number to 1.
 \def\pageone{
   \global\pageno=1
   \global\arabiccount = \pagecount
 }
 
+\let\contentsalignmacro = \chappager
+
+% \def\HEADINGSon{\HEADINGSdouble} % defined by \CHAPPAGon
+
 % For double-sided printing, put current file name in lower left corner,
 % chapter name on inside top of right hand pages, document
 % title on inside top of left hand pages, and page numbers on outside top
 % edge of all pages.
-\def\HEADINGSdouble{%
-\pageone
-\HEADINGSdoublex
-}
-\let\contentsalignmacro = \chappager
-
-% For single-sided printing, chapter title goes across top left of page,
-% page number on top right.
-\def\HEADINGSsingle{%
-\pageone
-\HEADINGSsinglex
-}
-\def\HEADINGSon{\HEADINGSdouble}
-
-\def\HEADINGSafter{\let\HEADINGShook=\HEADINGSdoublex}
+\def\HEADINGSafter{\let\HEADINGShook=\HEADINGSdouble}
 \let\HEADINGSdoubleafter=\HEADINGSafter
-\def\HEADINGSdoublex{%
+\def\HEADINGSdouble{%
 \global\evenfootline={\hfil}
 \global\oddfootline={\hfil}
 \global\evenheadline={\line{\folio\hfil\thistitle}}
 \global\oddheadline={\line{\thischapter\hfil\folio}}
-\global\evenchapheadline={\line{\folio\hfil}}
+\global\evenchapheadline={\line{\folio\hfil\thistitle}}
 \global\oddchapheadline={\line{\hfil\folio}}
 \global\let\contentsalignmacro = \chapoddpage
 }
 
-\def\HEADINGSsingleafter{\let\HEADINGShook=\HEADINGSsinglex}
-\def\HEADINGSsinglex{%
+% For single-sided printing, chapter title goes across top left of page,
+% page number on top right.
+\def\HEADINGSsingleafter{\let\HEADINGShook=\HEADINGSsingle}
+\def\HEADINGSsingle{%
 \global\evenfootline={\hfil}
 \global\oddfootline={\hfil}
 \global\evenheadline={\line{\thischapter\hfil\folio}}
@@ -3986,7 +3983,6 @@
 
 % for @setchapternewpage off
 \def\HEADINGSsinglechapoff{%
-\pageone
 \global\evenfootline={\hfil}
 \global\oddfootline={\hfil}
 \global\evenheadline={\line{\thischapter\hfil\folio}}
@@ -4356,8 +4352,7 @@
 % undo it ourselves.
 \def\headitemfont{\b}% for people to use in the template row; not changeable
 \def\headitem{%
-  \checkenv\multitable
-  \crcr
+  \crcr % must appear first
   \gdef\headitemcrhook{\nobreak}% attempt to avoid page break after headings
   \global\everytab={\bf}% can't use \headitemfont since the parsing differs
   \the\everytab % for the first item
@@ -4419,7 +4414,7 @@
       % Find the correct column width
       \hsize=\expandafter\csname col\the\colcount\endcsname
       %
-      \rightskip=0pt
+      \advance\rightskip by -1\rightskip % Zero leaving only any stretch
       \ifnum\colcount=1
         \advance\hsize by\leftskip % Add indent of surrounding text
       \else
@@ -4442,7 +4437,7 @@
 
 \message{conditionals,}
 
-% @iftex, @ifnotdocbook, @ifnothtml, @ifnotinfo, @ifnotplaintext,
+% @iftex, @ifnotdocbook, @ifnothtml, @ifnotinfo, @ifnotlatex, @ifnotplaintext,
 % @ifnotxml always succeed.  They currently do nothing; we don't
 % attempt to check whether the conditionals are properly nested.  But we
 % have to remember that they are conditionals, so that @end doesn't
@@ -4456,6 +4451,7 @@
 \makecond{ifnotdocbook}
 \makecond{ifnothtml}
 \makecond{ifnotinfo}
+\makecond{ifnotlatex}
 \makecond{ifnotplaintext}
 \makecond{ifnotxml}
 
@@ -4468,10 +4464,12 @@
 \def\ifdocbook{\doignore{ifdocbook}}
 \def\ifhtml{\doignore{ifhtml}}
 \def\ifinfo{\doignore{ifinfo}}
+\def\iflatex{\doignore{iflatex}}
 \def\ifnottex{\doignore{ifnottex}}
 \def\ifplaintext{\doignore{ifplaintext}}
 \def\ifxml{\doignore{ifxml}}
 \def\ignore{\doignore{ignore}}
+\def\latex{\doignore{latex}}
 \def\menu{\doignore{menu}}
 \def\xml{\doignore{xml}}
 
@@ -4710,13 +4708,11 @@
 % except not \outer, so it can be used within macros and \if's.
 \edef\newwrite{\makecsname{ptexnewwrite}}
 
-% \newindex {foo} defines an index named IX.
+% \newindex {IX} defines an index named IX.
 % It automatically defines \IXindex such that
 % \IXindex ...rest of line... puts an entry in the index IX.
 % It also defines \IXindfile to be the number of the output channel for
 % the file that accumulates this index.  The file's extension is IX.
-% The name of an index should be no more than 2 characters long
-% for the sake of vms.
 %
 \def\newindex#1{%
   \expandafter\chardef\csname#1indfile\endcsname=0
@@ -4779,21 +4775,6 @@
 \def\docodeindexxxx #1{\docind{\indexname}{#1}}
 
 
-% Used for the aux, toc and index files to prevent expansion of Texinfo
-% commands.
-%
-\def\atdummies{%
-  \definedummyletter\@%
-  \definedummyletter\ %
-  \definedummyletter\{%
-  \definedummyletter\}%
-  \definedummyletter\&%
-  %
-  % Do the redefinitions.
-  \definedummies
-  \otherbackslash
-}
-
 % \definedummyword defines \#1 as \string\#1\space, thus effectively
 % preventing its expansion.  This is used only for control words,
 % not control letters, because the \space would be incorrect for
@@ -4809,110 +4790,91 @@
 %
 \def\definedummyword  #1{\def#1{\string#1\space}}%
 \def\definedummyletter#1{\def#1{\string#1}}%
-\let\definedummyaccent\definedummyletter
 
-% Called from \atdummies to prevent the expansion of commands.
+% Used for the aux, toc and index files to prevent expansion of Texinfo
+% commands.  Most of the commands are controlled through the
+% \ifdummies conditional.
 %
-\def\definedummies{%
+\def\atdummies{%
+  \dummiestrue
   %
-  \let\commondummyword\definedummyword
-  \let\commondummyletter\definedummyletter
-  \let\commondummyaccent\definedummyaccent
-  \commondummiesnofonts
+  \definedummyletter\@%
+  \definedummyletter\ %
+  \definedummyletter\{%
+  \definedummyletter\}%
+  \definedummyletter\&%
   %
   \definedummyletter\_%
   \definedummyletter\-%
   %
-  % Non-English letters.
-  \definedummyword\AA
-  \definedummyword\AE
-  \definedummyword\DH
-  \definedummyword\L
-  \definedummyword\O
-  \definedummyword\OE
-  \definedummyword\TH
-  \definedummyword\aa
-  \definedummyword\ae
-  \definedummyword\dh
-  \definedummyword\exclamdown
-  \definedummyword\l
-  \definedummyword\o
-  \definedummyword\oe
-  \definedummyword\ordf
-  \definedummyword\ordm
-  \definedummyword\questiondown
-  \definedummyword\ss
-  \definedummyword\th
-  %
-  % Although these internal commands shouldn't show up, sometimes they do.
-  \definedummyword\bf
-  \definedummyword\gtr
-  \definedummyword\hat
-  \definedummyword\less
-  \definedummyword\sf
-  \definedummyword\sl
-  \definedummyword\tclose
-  \definedummyword\tt
-  %
-  \definedummyword\LaTeX
-  \definedummyword\TeX
-  %
-  % Assorted special characters.
-  \definedummyword\ampchar
-  \definedummyword\atchar
-  \definedummyword\arrow
-  \definedummyword\backslashchar
-  \definedummyword\bullet
-  \definedummyword\comma
-  \definedummyword\copyright
-  \definedummyword\registeredsymbol
-  \definedummyword\dots
-  \definedummyword\enddots
-  \definedummyword\entrybreak
-  \definedummyword\equiv
-  \definedummyword\error
-  \definedummyword\euro
-  \definedummyword\expansion
-  \definedummyword\geq
-  \definedummyword\guillemetleft
-  \definedummyword\guillemetright
-  \definedummyword\guilsinglleft
-  \definedummyword\guilsinglright
-  \definedummyword\lbracechar
-  \definedummyword\leq
-  \definedummyword\mathopsup
-  \definedummyword\minus
-  \definedummyword\ogonek
-  \definedummyword\pounds
-  \definedummyword\point
-  \definedummyword\print
-  \definedummyword\quotedblbase
-  \definedummyword\quotedblleft
-  \definedummyword\quotedblright
-  \definedummyword\quoteleft
-  \definedummyword\quoteright
-  \definedummyword\quotesinglbase
-  \definedummyword\rbracechar
-  \definedummyword\result
-  \definedummyword\sub
-  \definedummyword\sup
-  \definedummyword\textdegree
-  %
   \definedummyword\subentry
   %
   % We want to disable all macros so that they are not expanded by \write.
+  \let\commondummyword\definedummyword
   \macrolist
   \let\value\dummyvalue
   %
-  \normalturnoffactive
+  \turnoffactive
 }
 
-% \commondummiesnofonts: common to \definedummies and \indexnofonts.
-% Define \commondummyletter, \commondummyaccent and \commondummyword before
-% using.  Used for accents, font commands, and various control letters.
-%
-\def\commondummiesnofonts{%
-  % Control letters and accents.
+\newif\ifdummies
+\newif\ifindexnofonts
+
+\def\commondummyletter#1{%
+  \expandafter\let\csname\string#1:impl\endcsname#1%
+  \edef#1{%
+    \noexpand\ifindexnofonts
+      % empty expansion
+    \noexpand\else
+      \noexpand\ifdummies\string#1%
+      \noexpand\else
+        \noexpand\jumptwofi % dispose of the \fi
+        \expandafter\noexpand\csname\string#1:impl\endcsname
+      \noexpand\fi
+    \noexpand\fi}%
+}
+
+\def\commondummyaccent#1{%
+  \expandafter\let\csname\string#1:impl\endcsname#1%
+  \edef#1{%
+    \noexpand\ifindexnofonts
+      \noexpand\expandafter % dispose of \else ... \fi
+      \noexpand\asis
+    \noexpand\else
+      \noexpand\ifdummies\string#1%
+      \noexpand\else
+        \noexpand\jumptwofi % dispose of the \fi
+        \expandafter\noexpand\csname\string#1:impl\endcsname
+      \noexpand\fi
+    \noexpand\fi}%
+}
+
+% Like \commondummyaccent but add a \space at the end of the dummy expansion
+% #2 is the expansion used for \indexnofonts.  #2 is always followed by
+% \asis to remove a pair of following braces.
+\def\commondummyword#1#2{%
+  \expandafter\let\csname\string#1:impl\endcsname#1%
+  \expandafter\def\csname\string#1:ixnf\endcsname{#2\asis}%
+  \edef#1{%
+    \noexpand\ifindexnofonts
+      \noexpand\expandafter % dispose of \else ... \fi
+      \expandafter\noexpand\csname\string#1:ixnf\endcsname
+    \noexpand\else
+      \noexpand\ifdummies\string#1\space
+      \noexpand\else
+        \noexpand\jumptwofi % dispose of the \fi \fi
+        \expandafter\noexpand\csname\string#1:impl\endcsname
+      \noexpand\fi
+    \noexpand\fi}%
+}
+\def\jumptwofi#1\fi\fi{\fi\fi#1}
+
+% For \atdummies and \indexnofonts.  \atdummies sets
+% \dummiestrue and \indexnofonts sets \indexnofontstrue.
+\def\definedummies{
+  % @-sign is always an escape character when reading auxiliary files
+  \escapechar = `\@
+  %
   \commondummyletter\!%
   \commondummyaccent\"%
   \commondummyaccent\'%
@@ -4926,58 +4888,124 @@
   \commondummyaccent\^%
   \commondummyaccent\`%
   \commondummyaccent\~%
-  \commondummyword\u
-  \commondummyword\v
-  \commondummyword\H
-  \commondummyword\dotaccent
-  \commondummyword\ogonek
-  \commondummyword\ringaccent
-  \commondummyword\tieaccent
-  \commondummyword\ubaraccent
-  \commondummyword\udotaccent
-  \commondummyword\dotless
+  %
+  % Control letters and accents.
+  \commondummyword\u          {}%
+  \commondummyword\v          {}%
+  \commondummyword\H          {}%
+  \commondummyword\dotaccent  {}%
+  \commondummyword\ogonek     {}%
+  \commondummyword\ringaccent {}%
+  \commondummyword\tieaccent  {}%
+  \commondummyword\ubaraccent {}%
+  \commondummyword\udotaccent {}%
+  \commondummyword\dotless    {}%
   %
   % Texinfo font commands.
-  \commondummyword\b
-  \commondummyword\i
-  \commondummyword\r
-  \commondummyword\sansserif
-  \commondummyword\sc
-  \commondummyword\slanted
-  \commondummyword\t
+  \commondummyword\b          {}%
+  \commondummyword\i          {}%
+  \commondummyword\r          {}%
+  \commondummyword\sansserif  {}%
+  \commondummyword\sc         {}%
+  \commondummyword\slanted    {}%
+  \commondummyword\t          {}%
   %
   % Commands that take arguments.
-  \commondummyword\abbr
-  \commondummyword\acronym
-  \commondummyword\anchor
-  \commondummyword\cite
-  \commondummyword\code
-  \commondummyword\command
-  \commondummyword\dfn
-  \commondummyword\dmn
-  \commondummyword\email
-  \commondummyword\emph
-  \commondummyword\env
-  \commondummyword\file
-  \commondummyword\image
-  \commondummyword\indicateurl
-  \commondummyword\inforef
-  \commondummyword\kbd
-  \commondummyword\key
-  \commondummyword\math
-  \commondummyword\option
-  \commondummyword\pxref
-  \commondummyword\ref
-  \commondummyword\samp
-  \commondummyword\strong
-  \commondummyword\tie
-  \commondummyword\U
-  \commondummyword\uref
-  \commondummyword\url
-  \commondummyword\var
-  \commondummyword\verb
-  \commondummyword\w
-  \commondummyword\xref
+  \commondummyword\abbr       {}%
+  \commondummyword\acronym    {}%
+  \commondummyword\anchor     {}%
+  \commondummyword\cite       {}%
+  \commondummyword\code       {}%
+  \commondummyword\command    {}%
+  \commondummyword\dfn        {}%
+  \commondummyword\dmn        {}%
+  \commondummyword\email      {}%
+  \commondummyword\emph       {}%
+  \commondummyword\env        {}%
+  \commondummyword\file       {}%
+  \commondummyword\image      {}%
+  \commondummyword\indicateurl{}%
+  \commondummyword\inforef    {}%
+  \commondummyword\kbd        {}%
+  \commondummyword\key        {}%
+  \commondummyword\link       {}%
+  \commondummyword\math       {}%
+  \commondummyword\option     {}%
+  \commondummyword\pxref      {}%
+  \commondummyword\ref        {}%
+  \commondummyword\samp       {}%
+  \commondummyword\strong     {}%
+  \commondummyword\tie        {}%
+  \commondummyword\U          {}%
+  \commondummyword\uref       {}%
+  \commondummyword\url        {}%
+  \commondummyword\var        {}%
+  \commondummyword\verb       {}%
+  \commondummyword\w          {}%
+  \commondummyword\xref       {}%
+  %
+  \commondummyword\AA               {AA}%
+  \commondummyword\AE               {AE}%
+  \commondummyword\DH               {DZZ}%
+  \commondummyword\L                {L}%
+  \commondummyword\O                {O}%
+  \commondummyword\OE               {OE}%
+  \commondummyword\TH               {TH}%
+  \commondummyword\aa               {aa}%
+  \commondummyword\ae               {ae}%
+  \commondummyword\dh               {dzz}%
+  \commondummyword\exclamdown       {!}%
+  \commondummyword\l                {l}%
+  \commondummyword\o                {o}%
+  \commondummyword\oe               {oe}%
+  \commondummyword\ordf             {a}%
+  \commondummyword\ordm             {o}%
+  \commondummyword\questiondown     {?}%
+  \commondummyword\ss               {ss}%
+  \commondummyword\th               {th}%
+  %
+  \commondummyword\LaTeX            {LaTeX}%
+  \commondummyword\TeX              {TeX}%
+  %
+  % Assorted special characters.
+  \commondummyword\ampchar          {\normalamp}%
+  \commondummyword\atchar           {\@}%
+  \commondummyword\arrow            {->}%
+  \commondummyword\backslashchar    {\realbackslash}%
+  \commondummyword\bullet           {bullet}%
+  \commondummyword\comma            {,}%
+  \commondummyword\copyright        {copyright}%
+  \commondummyword\dots             {...}%
+  \commondummyword\enddots          {...}%
+  \commondummyword\entrybreak       {}%
+  \commondummyword\equiv            {===}%
+  \commondummyword\error            {error}%
+  \commondummyword\euro             {euro}%
+  \commondummyword\expansion        {==>}%
+  \commondummyword\geq              {>=}%
+  \commondummyword\guillemetleft    {<<}%
+  \commondummyword\guillemetright   {>>}%
+  \commondummyword\guilsinglleft    {<}%
+  \commondummyword\guilsinglright   {>}%
+  \commondummyword\lbracechar       {\{}%
+  \commondummyword\leq              {<=}%
+  \commondummyword\mathopsup        {sup}%
+  \commondummyword\minus            {-}%
+  \commondummyword\pounds           {pounds}%
+  \commondummyword\point            {.}%
+  \commondummyword\print            {-|}%
+  \commondummyword\quotedblbase     {"}%
+  \commondummyword\quotedblleft     {"}%
+  \commondummyword\quotedblright    {"}%
+  \commondummyword\quoteleft        {`}%
+  \commondummyword\quoteright       {'}%
+  \commondummyword\quotesinglbase   {,}%
+  \commondummyword\rbracechar       {\}}%
+  \commondummyword\registeredsymbol {R}%
+  \commondummyword\result           {=>}%
+  \commondummyword\sub              {}%
+  \commondummyword\sup              {}%
+  \commondummyword\textdegree       {o}%
 }
 
 \let\indexlbrace\relax
@@ -4995,25 +5023,24 @@
 \catcode`\-=13
 \catcode`\`=13
   \gdef\indexnonalnumdisappear{%
-    \expandafter\ifx\csname SETtxiindexlquoteignore\endcsname\relax\else
+    \ifflagclear{txiindexlquoteignore}{}{%
       % @set txiindexlquoteignore makes us ignore left quotes in the sort term.
       % (Introduced for FSFS 2nd ed.)
       \let`=\empty
-    \fi
+    }%
     %
-    \expandafter\ifx\csname SETtxiindexbackslashignore\endcsname\relax\else
+    \ifflagclear{txiindexbackslashignore}{}{%
       \backslashdisappear
-    \fi
-    %
-    \expandafter\ifx\csname SETtxiindexhyphenignore\endcsname\relax\else
+    }%
+    \ifflagclear{txiindexhyphenignore}{}{%
       \def-{}%
-    \fi
-    \expandafter\ifx\csname SETtxiindexlessthanignore\endcsname\relax\else
+    }%
+    \ifflagclear{txiindexlessthanignore}{}{%
       \def<{}%
-    \fi
-    \expandafter\ifx\csname SETtxiindexatsignignore\endcsname\relax\else
+    }%
+    \ifflagclear{txiindexatsignignore}{}{%
       \def\@{}%
-    \fi
+    }%
   }
 
   \gdef\indexnonalnumreappear{%
@@ -5029,18 +5056,7 @@
 % would be for a given command (usually its argument).
 %
 \def\indexnofonts{%
-  % Accent commands should become @asis.
-  \def\commondummyaccent##1{\let##1\asis}%
-  % We can just ignore other control letters.
-  \def\commondummyletter##1{\let##1\empty}%
-  % All control words become @asis by default; overrides below.
-  \let\commondummyword\commondummyaccent
-  \commondummiesnofonts
-  %
-  % Don't no-op \tt, since it isn't a user-level command
-  % and is used in the definitions of the active chars like <, >, |, etc.
-  % Likewise with the other plain tex font commands.
-  %\let\tt=\asis
+  \indexnofontstrue
   %
   \def\ { }%
   \def\@{@}%
@@ -5052,84 +5068,19 @@
   \let\lbracechar\{%
   \let\rbracechar\}%
   %
-  % Non-English letters.
-  \def\AA{AA}%
-  \def\AE{AE}%
-  \def\DH{DZZ}%
-  \def\L{L}%
-  \def\OE{OE}%
-  \def\O{O}%
-  \def\TH{TH}%
-  \def\aa{aa}%
-  \def\ae{ae}%
-  \def\dh{dzz}%
-  \def\exclamdown{!}%
-  \def\l{l}%
-  \def\oe{oe}%
-  \def\ordf{a}%
-  \def\ordm{o}%
-  \def\o{o}%
-  \def\questiondown{?}%
-  \def\ss{ss}%
-  \def\th{th}%
-  %
-  \let\do\indexnofontsdef
-  %
-  \do\LaTeX{LaTeX}%
-  \do\TeX{TeX}%
-  %
-  % Assorted special characters.
-  \do\atchar{@}%
-  \do\arrow{->}%
-  \do\bullet{bullet}%
-  \do\comma{,}%
-  \do\copyright{copyright}%
-  \do\dots{...}%
-  \do\enddots{...}%
-  \do\equiv{==}%
-  \do\error{error}%
-  \do\euro{euro}%
-  \do\expansion{==>}%
-  \do\geq{>=}%
-  \do\guillemetleft{<<}%
-  \do\guillemetright{>>}%
-  \do\guilsinglleft{<}%
-  \do\guilsinglright{>}%
-  \do\leq{<=}%
-  \do\lbracechar{\{}%
-  \do\minus{-}%
-  \do\point{.}%
-  \do\pounds{pounds}%
-  \do\print{-|}%
-  \do\quotedblbase{"}%
-  \do\quotedblleft{"}%
-  \do\quotedblright{"}%
-  \do\quoteleft{`}%
-  \do\quoteright{'}%
-  \do\quotesinglbase{,}%
-  \do\rbracechar{\}}%
-  \do\registeredsymbol{R}%
-  \do\result{=>}%
-  \do\textdegree{o}%
   %
   % We need to get rid of all macros, leaving only the arguments (if present).
   % Of course this is not nearly correct, but it is the best we can do for now.
-  % makeinfo does not expand macros in the argument to @deffn, which ends up
-  % writing an index entry, and texindex isn't prepared for an index sort entry
-  % that starts with \.
   %
   % Since macro invocations are followed by braces, we can just redefine them
   % to take a single TeX argument.  The case of a macro invocation that
   % goes to end-of-line is not handled.
   %
+  \def\commondummyword##1{\let##1\asis}%
   \macrolist
   \let\value\indexnofontsvalue
 }
 
-% Give the control sequence a definition that removes the {} that follows
-% its use, e.g. @AA{} -> AA
-\def\indexnofontsdef#1#2{\def#1##1{#2}}%
-
 
 
 
@@ -5260,7 +5211,10 @@
         \xdef\trimmed{\segment}%
         \xdef\trimmed{\expandafter\eatspaces\expandafter{\trimmed}}%
         \xdef\indexsortkey{\trimmed}%
-        \ifx\indexsortkey\empty\xdef\indexsortkey{ }\fi
+        \ifx\indexsortkey\empty
+          \message{Empty index sort key near line \the\inputlineno}%
+          \xdef\indexsortkey{ }%
+        \fi
       }\fi
       %
       % Append to \fullindexsortkey.
@@ -5284,14 +5238,14 @@
 % the current value of \escapechar.
 \def\escapeisbackslash{\escapechar=`\\}
 
-% Use \ in index files by default.  texi2dvi didn't support @ as the escape
-% character (as it checked for "\entry" in the files, and not "@entry").  When
-% the new version of texi2dvi has had a chance to become more prevalent, then
-% the escape character can change back to @ again.  This should be an easy
-% change to make now because both @ and \ are only used as escape characters in
-% index files, never standing for themselves.
+% Uncomment to use \ in index files by default.  Old texi2dvi (before 2019)
+% didn't support @ as the escape character (as it checked for "\entry" in
+% the files, and not "@entry").
+%   In the future we can remove this flag and simplify the code for
+% index files and backslashes, once the support is no longer likely to be
+% useful.
 %
-\set txiindexescapeisbackslash
+% \set txiindexescapeisbackslash
 
 % Write the entry in \indextext to the index file.
 %
@@ -5305,9 +5259,7 @@
   %
   \atdummies
   %
-  \expandafter\ifx\csname SETtxiindexescapeisbackslash\endcsname\relax\else
-    \escapeisbackslash
-  \fi
+  \ifflagclear{txiindexescapeisbackslash}{}{\escapeisbackslash}%
   %
   % For texindex which always views { and } as separators.
   \def\{{\lbracechar{}}%
@@ -5491,9 +5443,9 @@
 % old index files using \ as the escape character.  Reading this would
 % at best lead to typesetting garbage, at worst a TeX syntax error.
 \def\printindexzz#1#2\finish{%
-  \expandafter\ifx\csname SETtxiindexescapeisbackslash\endcsname\relax
+  \ifflagclear{txiindexescapeisbackslash}{%
     \uccode`\~=`\\ \uppercase{\if\noexpand~}\noexpand#1
-      \expandafter\ifx\csname SETtxiskipindexfileswithbackslash\endcsname\relax
+      \ifflagclear{txiskipindexfileswithbackslash}{%
 \errmessage{%
 ERROR: A sorted index file in an obsolete format was skipped.
 To fix this problem, please upgrade your version of 'texi2dvi'
@@ -5509,15 +5461,15 @@
 If you continue to have problems, deleting the index files and starting again
 might help (with 'rm \jobname.?? \jobname.??s')%
 }%
-      \else
+      }{%
         (Skipped sorted index file in obsolete format)
-      \fi
+      }%
     \else
       \begindoublecolumns
       \input \jobname.\indexname s
       \enddoublecolumns
     \fi
-  \else
+  }{%
     \begindoublecolumns
     \catcode`\\=0\relax
     %
@@ -5527,7 +5479,7 @@
     \catcode`\@=0\relax
     \input \jobname.\indexname s
     \enddoublecolumns
-  \fi
+  }%
 }
 
 % These macros are used by the sorted index file itself.
@@ -5602,6 +5554,16 @@
 \newdimen\entryrightmargin
 \entryrightmargin=0pt
 
+% amount to indent subsequent lines in an entry when it spans more than
+% one line.
+\newdimen\entrycontskip
+\entrycontskip=1em
+
+% for PDF output, whether to make the text of the entry a link to the page
+% number.  set for @contents and @shortcontents where there is only one
+% page number.
+\newif\iflinkentrytext
+
 % \entry typesets a paragraph consisting of the text (#1), dot leaders, and
 % then page number (#2) flushed to the right margin.  It is used for index
 % and table of contents entries.  The paragraph is indented by \leftskip.
@@ -5628,7 +5590,7 @@
 }
 \def\entrybreak{\unskip\space\ignorespaces}%
 \def\doentry{%
-    % Save the text of the entry
+    % Save the text of the entry in \boxA
     \global\setbox\boxA=\hbox\bgroup
     \bgroup % Instead of the swallowed brace.
       \noindent
@@ -5638,12 +5600,21 @@
       % with catcodes occurring.
 }
 {\catcode`\@=11
+% #1 is the page number
 \gdef\finishentry#1{%
-    \egroup % end box A
+    \egroup % end \boxA
     \dimen@ = \wd\boxA % Length of text of entry
+    % add any leaders and page number to \boxA.
     \global\setbox\boxA=\hbox\bgroup
-      \unhbox\boxA
-      % #1 is the page number.
+      \ifpdforxetex
+        \iflinkentrytext
+          \pdflinkpage{#1}{\unhbox\boxA}%
+        \else
+          \unhbox\boxA
+        \fi
+      \else
+        \unhbox\boxA
+      \fi
       %
       % Get the width of the page numbers, and only use
       % leaders if they are present.
@@ -5662,6 +5633,8 @@
         \fi
       \fi
     \egroup % end \boxA
+    %
+    % now output
     \ifdim\wd\boxB = 0pt
       \noindent\unhbox\boxA\par
       \nobreak
@@ -5679,41 +5652,17 @@
       \parfillskip=0pt plus -1fill
       %
       \advance\rightskip by \entryrightmargin
-      % Determine how far we can stretch into the margin.
-      % This allows, e.g., "Appendix H  GNU Free Documentation License" to
-      % fit on one line in @letterpaper format.
-      \ifdim\entryrightmargin>2.1em
-        \dimen@i=2.1em
-      \else
-        \dimen@i=0em
-      \fi
-      \advance \parfillskip by 0pt minus 1\dimen@i
       %
       \dimen@ii = \hsize
       \advance\dimen@ii by -1\leftskip
       \advance\dimen@ii by -1\entryrightmargin
-      \advance\dimen@ii by 1\dimen@i
       \ifdim\wd\boxA > \dimen@ii % If the entry doesn't fit in one line
       \ifdim\dimen@ > 0.8\dimen@ii   % due to long index text
-        % Try to split the text roughly evenly.  \dimen@ will be the length of
-        % the first line.
-        \dimen@ = 0.7\dimen@
-        \dimen@ii = \hsize
-        \ifnum\dimen@>\dimen@ii
-          % If the entry is too long (for example, if it needs more than
-          % two lines), use all the space in the first line.
-          \dimen@ = \dimen@ii
-        \fi
         \advance\leftskip by 0pt plus 1fill % ragged right
-        \advance \dimen@ by 1\rightskip
-        \parshape = 2 0pt \dimen@ 0em \dimen@ii
-        % Ideally we'd add a finite glue at the end of the first line only,
-        % instead of using \parshape with explicit line lengths, but TeX
-        % doesn't seem to provide a way to do such a thing.
         %
         % Indent all lines but the first one.
-        \advance\leftskip by 1em
-        \advance\parindent by -1em
+        \advance\leftskip by \entrycontskip
+        \advance\parindent by -\entrycontskip
       \fi\fi
       \indent % start paragraph
       \unhbox\boxA
@@ -5736,12 +5685,11 @@
 \newskip\thinshrinkable
 \skip\thinshrinkable=.15em minus .15em
 
-% Like plain.tex's \dotfill, except uses up at least 1 em.
+% Like plain.tex's \dotfill, except uses up at least 0.5 em.
 % The filll stretch here overpowers both the fil and fill stretch to push
 % the page number to the right.
 \def\indexdotfill{\cleaders
-  \hbox{$\mathsurround=0pt \mkern1.5mu.\mkern1.5mu$}\hskip 1em plus 1filll}
-
+  \hbox{$\mathsurround=0pt \mkern1.5mu.\mkern1.5mu$}\hskip 0.5em plus 1filll}
 
 \def\primary #1{\line{#1\hfil}}
 
@@ -5794,7 +5742,7 @@
   % below is chosen so that the gutter has the same value (well, +-<1pt)
   % as it did when we hard-coded it.
   %
-  % We put the result in a separate register, \doublecolumhsize, so we
+  % We put the result in a separate register, \doublecolumnhsize, so we
   % can restore it in \pagesofar, after \hsize itself has (potentially)
   % been clobbered.
   %
@@ -5963,7 +5911,7 @@
 % Chapters, sections, etc.
 
 % Let's start with @part.
-\outer\parseargdef\part{\partzzz{#1}}
+\parseargdef\part{\partzzz{#1}}
 \def\partzzz#1{%
   \chapoddpage
   \null
@@ -6189,8 +6137,7 @@
 % normally unnmhead0 calls unnumberedzzz:
 \outer\parseargdef\unnumbered{\unnmhead0{#1}}
 \def\unnumberedzzz#1{%
-  \global\secno=0 \global\subsecno=0 \global\subsubsecno=0
-    \global\advance\unnumberedno by 1
+  \global\advance\unnumberedno by 1
   %
   % Since an unnumbered has no number, no prefix for figures.
   \global\let\chaplevelprefix = \empty
@@ -6246,8 +6193,8 @@
 % normally calls unnumberedseczzz:
 \outer\parseargdef\unnumberedsec{\unnmhead1{#1}}
 \def\unnumberedseczzz#1{%
-  \global\subsecno=0 \global\subsubsecno=0  \global\advance\secno by 1
-  \sectionheading{#1}{sec}{Ynothing}{\the\unnumberedno.\the\secno}%
+  \global\advance\unnumberedno by 1
+  \sectionheading{#1}{sec}{Ynothing}{\the\unnumberedno}%
 }
 
 % Subsections.
@@ -6270,9 +6217,8 @@
 % normally calls unnumberedsubseczzz:
 \outer\parseargdef\unnumberedsubsec{\unnmhead2{#1}}
 \def\unnumberedsubseczzz#1{%
-  \global\subsubsecno=0  \global\advance\subsecno by 1
-  \sectionheading{#1}{subsec}{Ynothing}%
-                 {\the\unnumberedno.\the\secno.\the\subsecno}%
+  \global\advance\unnumberedno by 1
+  \sectionheading{#1}{subsec}{Ynothing}{\the\unnumberedno}%
 }
 
 % Subsubsections.
@@ -6296,9 +6242,8 @@
 % normally unnumberedsubsubseczzz:
 \outer\parseargdef\unnumberedsubsubsec{\unnmhead3{#1}}
 \def\unnumberedsubsubseczzz#1{%
-  \global\advance\subsubsecno by 1
-  \sectionheading{#1}{subsubsec}{Ynothing}%
-                 {\the\unnumberedno.\the\secno.\the\subsecno.\the\subsubsecno}%
+  \global\advance\unnumberedno by 1
+  \sectionheading{#1}{subsubsec}{Ynothing}{\the\unnumberedno}%
 }
 
 % These macros control what the section commands do, according
@@ -6361,7 +6306,7 @@
   \fi
 }
 
-\parseargdef\setchapternewpage{\csname CHAPPAG#1\endcsname}
+\parseargdef\setchapternewpage{\csname CHAPPAG#1\endcsname\HEADINGSon}
 
 \def\CHAPPAGoff{%
 \global\let\contentsalignmacro = \chappager
@@ -6378,7 +6323,7 @@
 \global\let\pchapsepmacro=\chapoddpage
 \global\def\HEADINGSon{\HEADINGSdouble}}
 
-\CHAPPAGon
+\setchapternewpage on
 
 % \chapmacro - Chapter opening.
 %
@@ -6391,6 +6336,16 @@
 \def\Yappendixkeyword{Yappendix}
 \def\Yomitfromtockeyword{Yomitfromtoc}
 %
+%
+% Definitions for @thischapter. These can be overridden in translation
+% files.
+\def\thischapterAppendix{%
+  \putwordAppendix{} \thischapternum: \thischaptername}
+
+\def\thischapterChapter{%
+  \putwordChapter{} \thischapternum: \thischaptername}
+%
+%
 \def\chapmacro#1#2#3{%
   \expandafter\ifx\thisenv\titlepage\else
     \checkenv{}% chapters, etc., should not start inside an environment.
@@ -6413,22 +6368,14 @@
     \xdef\currentchapterdefs{%
       \gdef\noexpand\thischaptername{\the\toks0}%
       \gdef\noexpand\thischapternum{\appendixletter}%
-      % \noexpand\putwordAppendix avoids expanding indigestible
-      % commands in some of the translations.
-      \gdef\noexpand\thischapter{\noexpand\putwordAppendix{}
-                                 \noexpand\thischapternum:
-                                 \noexpand\thischaptername}%
+      \let\noexpand\thischapter\noexpand\thischapterAppendix
     }%
   \else
     \toks0={#1}%
     \xdef\currentchapterdefs{%
       \gdef\noexpand\thischaptername{\the\toks0}%
       \gdef\noexpand\thischapternum{\the\chapno}%
-      % \noexpand\putwordChapter avoids expanding indigestible
-      % commands in some of the translations.
-      \gdef\noexpand\thischapter{\noexpand\putwordChapter{}
-                                 \noexpand\thischapternum:
-                                 \noexpand\thischaptername}%
+      \let\noexpand\thischapter\noexpand\thischapterChapter
     }%
   \fi\fi\fi
   %
@@ -6514,6 +6461,12 @@
 \def\subsubsecheadingskip{\subsecheadingskip}
 \def\subsubsecheadingbreak{\subsecheadingbreak}
 
+% Definition for @thissection. This can be overridden in translation
+% files.
+\def\thissectionDef{%
+  \putwordSection{} \thissectionnum: \thissectionname}
+%
+
 
 % Print any size, any type, section title.
 %
@@ -6555,11 +6508,7 @@
         \xdef\currentsectiondefs{%
           \gdef\noexpand\thissectionname{\the\toks0}%
           \gdef\noexpand\thissectionnum{#4}%
-          % \noexpand\putwordSection avoids expanding indigestible
-          % commands in some of the translations.
-          \gdef\noexpand\thissection{\noexpand\putwordSection{}
-                                     \noexpand\thissectionnum:
-                                     \noexpand\thissectionname}%
+          \let\noexpand\thissection\noexpand\thissectionDef
         }%
       \fi
     \else
@@ -6568,11 +6517,7 @@
         \xdef\currentsectiondefs{%
           \gdef\noexpand\thissectionname{\the\toks0}%
           \gdef\noexpand\thissectionnum{#4}%
-          % \noexpand\putwordSection avoids expanding indigestible
-          % commands in some of the translations.
-          \gdef\noexpand\thissection{\noexpand\putwordSection{}
-                                     \noexpand\thissectionnum:
-                                     \noexpand\thissectionname}%
+          \let\noexpand\thissection\noexpand\thissectionDef
         }%
       \fi
     \fi\fi\fi
@@ -6732,6 +6677,82 @@
   \input \tocreadfilename
 }
 
+% process toc file to find the maximum width of the section numbers for
+% each chapter
+\def\findsecnowidths{%
+  \begingroup
+  \setupdatafile
+  \activecatcodes
+  \secentryfonts
+  % Redefinitions
+  \def\numchapentry##1##2##3##4{%
+    \def\curchapname{secnowidth-##2}%
+    \curchapmax=0pt
+  }%
+  \let\appentry\numchapentry
+  %
+  \def\numsecentry##1##2##3##4{%
+    \def\cursecname{secnowidth-##2}%
+    \cursecmax=0pt
+    %
+    \setbox0=\hbox{##2}%
+    \ifdim\wd0>\curchapmax
+      \curchapmax=\wd0
+      \expandafter\xdef\csname\curchapname\endcsname{\the\wd0}%
+    \fi
+  }%
+  \let\appsecentry\numsecentry
+  %
+  \def\numsubsecentry##1##2##3##4{%
+    \def\curssecname{secnowidth-##2}%
+    \curssecmax=0pt
+    %
+    \setbox0=\hbox{##2}%
+    \ifdim\wd0>\cursecmax
+      \cursecmax=\wd0
+      \expandafter\xdef\csname\cursecname\endcsname{\the\wd0}%
+    \fi
+  }%
+  \let\appsubsecentry\numsubsecentry
+  %
+  \def\numsubsubsecentry##1##2##3##4{%
+    \setbox0=\hbox{##2}%
+    \ifdim\wd0>\curssecmax
+      \curssecmax=\wd0
+      \expandafter\xdef\csname\curssecname\endcsname{\the\wd0}%
+    \fi
+  }%
+  \let\appsubsubsecentry\numsubsubsecentry
+  %
+  % Discard any output by outputting to dummy vbox, in case the toc file
+  % contains macros that we have not redefined above.
+  \setbox\dummybox\vbox\bgroup
+    \input \tocreadfilename\relax
+  \egroup
+  \endgroup
+}
+\newdimen\curchapmax
+\newdimen\cursecmax
+\newdimen\curssecmax
+
+
+% set #1 to the maximum section width for #2
+\def\retrievesecnowidth#1#2{%
+  \expandafter\let\expandafter\savedsecnowidth \csname secnowidth-#2\endcsname
+  \ifx\savedsecnowidth\relax
+    #1=0pt
+  \else
+    #1=\savedsecnowidth
+  \fi
+}
+\newdimen\secnowidthchap
+\secnowidthchap=0pt
+\newdimen\secnowidthsec
+\secnowidthsec=0pt
+\newdimen\secnowidthssec
+\secnowidthssec=0pt
+
+
 \newskip\contentsrightmargin \contentsrightmargin=1in
 \newcount\savepageno
 \newcount\lastnegativepageno \lastnegativepageno = -1
@@ -6758,8 +6779,14 @@
     \def\thistitle{}% no title in double-sided headings
     % Record where the Roman numerals started.
     \ifnum\romancount=0 \global\romancount=\pagecount \fi
+    \linkentrytexttrue
 }
 
+% \raggedbottom in plain.tex hardcodes \topskip so override it
+\catcode`\@=11
+\def\raggedbottom{\advance\topskip by 0pt plus60pt \r@ggedbottomtrue}
+\catcode`\@=\other
+
 % redefined for the two-volume lispref.  We always output on
 % \jobname.toc even if this is redefined.
 %
@@ -6771,6 +6798,7 @@
   \startcontents{\putwordTOC}%
     \openin 1 \tocreadfilename\space
     \ifeof 1 \else
+      \findsecnowidths
       \readtocfile
     \fi
     \vfill \eject
@@ -6798,6 +6826,7 @@
     \rm
     \hyphenpenalty = 10000
     \advance\baselineskip by 1pt % Open it up a little.
+    \extrasecnoskip=0.4pt
     \def\numsecentry##1##2##3##4{}
     \let\appsecentry = \numsecentry
     \let\unnsecentry = \numsecentry
@@ -6822,12 +6851,8 @@
 % Get ready to use Arabic numerals again
 \def\contentsendroman{%
   \lastnegativepageno = \pageno
-  \global\pageno = \savepageno
-  %
-  % If \romancount > \arabiccount, the contents are at the end of the
-  % document.  Otherwise, advance where the Arabic numerals start for
-  % the page numbers.
-  \ifnum\romancount>\arabiccount\else\global\arabiccount=\pagecount\fi
+  \global\pageno=1
+  \contentsendcount = \pagecount
 }
 
 % Typeset the label for a chapter or appendix for the short contents.
@@ -6837,8 +6862,6 @@
   % This space should be enough, since a single number is .5em, and the
   % widest letter (M) is 1em, at least in the Computer Modern fonts.
   % But use \hss just in case.
-  % (This space doesn't include the extra space that gets added after
-  % the label; that gets put in by \shortchapentry above.)
   %
   % We'd like to right-justify chapter numbers, but that looks strange
   % with appendix letters.  And right-justifying numbers and
@@ -6848,10 +6871,15 @@
   \hbox to 1em{#1\hss}%
 }
 
-% These macros generate individual entries in the table of contents.
-% The first argument is the chapter or section name.
-% The last argument is the page number.
-% The arguments in between are the chapter number, section number, ...
+% These macros generate individual entries in the table of contents,
+% and are read in from the *.toc file.
+%
+% The arguments are like:
+% \def\numchapentry#1#2#3#4
+%   #1 - the chapter or section name.
+%   #2 - section number
+%   #3 - level of section (e.g "chap", "sec")
+%   #4 - page number
 
 % Parts, in the main contents.  Replace the part number, which doesn't
 % exist, with an empty box.  Let's hope all the numbers have the same width.
@@ -6864,7 +6892,7 @@
   \vskip 0pt plus 5\baselineskip
   \penalty-300
   \vskip 0pt plus -5\baselineskip
-  \dochapentry{\numeralbox\labelspace#1}{}%
+  \dochapentry{#1}{\numeralbox}{}%
 }
 %
 % Parts, in the short toc.
@@ -6875,12 +6903,14 @@
 }
 
 % Chapters, in the main contents.
-\def\numchapentry#1#2#3#4{\dochapentry{#2\labelspace#1}{#4}}
+\def\numchapentry#1#2#3#4{%
+  \retrievesecnowidth\secnowidthchap{#2}%
+  \dochapentry{#1}{#2}{#4}%
+}
 
 % Chapters, in the short toc.
-% See comments in \dochapentry re vbox and related settings.
 \def\shortchapentry#1#2#3#4{%
-  \tocentry{\shortchaplabel{#2}\labelspace #1}{\doshortpageno\bgroup#4\egroup}%
+  \tocentry{#1}{\shortchaplabel{#2}}{#4}%
 }
 
 % Appendices, in the main contents.
@@ -6891,70 +6921,111 @@
   \setbox0 = \hbox{\putwordAppendix{} M}%
   \hbox to \wd0{\putwordAppendix{} #1\hss}}
 %
-\def\appentry#1#2#3#4{\dochapentry{\appendixbox{#2}\hskip.7em#1}{#4}}
+\def\appentry#1#2#3#4{%
+  \retrievesecnowidth\secnowidthchap{#2}%
+  \dochapentry{\appendixbox{#2}\hskip.7em#1}{}{#4}%
+}
 
 % Unnumbered chapters.
-\def\unnchapentry#1#2#3#4{\dochapentry{#1}{#4}}
-\def\shortunnchapentry#1#2#3#4{\tocentry{#1}{\doshortpageno\bgroup#4\egroup}}
+\def\unnchapentry#1#2#3#4{\dochapentry{#1}{}{#4}}
+\def\shortunnchapentry#1#2#3#4{\tocentry{#1}{}{#4}}
 
 % Sections.
-\def\numsecentry#1#2#3#4{\dosecentry{#2\labelspace#1}{#4}}
+\def\numsecentry#1#2#3#4{\dosecentry{#1}{#2}{#4}}
+
+\def\numsecentry#1#2#3#4{%
+  \retrievesecnowidth\secnowidthsec{#2}%
+  \dosecentry{#1}{#2}{#4}%
+}
 \let\appsecentry=\numsecentry
-\def\unnsecentry#1#2#3#4{\dosecentry{#1}{#4}}
+\def\unnsecentry#1#2#3#4{%
+  \retrievesecnowidth\secnowidthsec{#2}%
+  \dosecentry{#1}{}{#4}%
+}
 
 % Subsections.
-\def\numsubsecentry#1#2#3#4{\dosubsecentry{#2\labelspace#1}{#4}}
+\def\numsubsecentry#1#2#3#4{%
+  \retrievesecnowidth\secnowidthssec{#2}%
+  \dosubsecentry{#1}{#2}{#4}%
+}
 \let\appsubsecentry=\numsubsecentry
-\def\unnsubsecentry#1#2#3#4{\dosubsecentry{#1}{#4}}
+\def\unnsubsecentry#1#2#3#4{%
+  \retrievesecnowidth\secnowidthssec{#2}%
+  \dosubsecentry{#1}{}{#4}%
+}
 
 % And subsubsections.
-\def\numsubsubsecentry#1#2#3#4{\dosubsubsecentry{#2\labelspace#1}{#4}}
+\def\numsubsubsecentry#1#2#3#4{\dosubsubsecentry{#1}{#2}{#4}}
 \let\appsubsubsecentry=\numsubsubsecentry
-\def\unnsubsubsecentry#1#2#3#4{\dosubsubsecentry{#1}{#4}}
+\def\unnsubsubsecentry#1#2#3#4{\dosubsubsecentry{#1}{}{#4}}
 
 % This parameter controls the indentation of the various levels.
 % Same as \defaultparindent.
 \newdimen\tocindent \tocindent = 15pt
 
-% Now for the actual typesetting. In all these, #1 is the text and #2 is the
-% page number.
+% Now for the actual typesetting. In all these, #1 is the text, #2 is
+% a section number if present, and #3 is the page number.
 %
 % If the toc has to be broken over pages, we want it to be at chapters
 % if at all possible; hence the \penalty.
-\def\dochapentry#1#2{%
+\def\dochapentry#1#2#3{%
    \penalty-300 \vskip1\baselineskip plus.33\baselineskip minus.25\baselineskip
    \begingroup
      % Move the page numbers slightly to the right
      \advance\entryrightmargin by -0.05em
      \chapentryfonts
-     \tocentry{#1}{\dopageno\bgroup#2\egroup}%
+     \extrasecnoskip=0.4em % separate chapter number more
+     \tocentry{#1}{#2}{#3}%
    \endgroup
    \nobreak\vskip .25\baselineskip plus.1\baselineskip
 }
 
-\def\dosecentry#1#2{\begingroup
+\def\dosecentry#1#2#3{\begingroup
+  \secnowidth=\secnowidthchap
   \secentryfonts \leftskip=\tocindent
-  \tocentry{#1}{\dopageno\bgroup#2\egroup}%
+  \tocentry{#1}{#2}{#3}%
 \endgroup}
 
-\def\dosubsecentry#1#2{\begingroup
+\def\dosubsecentry#1#2#3{\begingroup
+  \secnowidth=\secnowidthsec
   \subsecentryfonts \leftskip=2\tocindent
-  \tocentry{#1}{\dopageno\bgroup#2\egroup}%
+  \tocentry{#1}{#2}{#3}%
 \endgroup}
 
-\def\dosubsubsecentry#1#2{\begingroup
+\def\dosubsubsecentry#1#2#3{\begingroup
+  \secnowidth=\secnowidthssec
   \subsubsecentryfonts \leftskip=3\tocindent
-  \tocentry{#1}{\dopageno\bgroup#2\egroup}%
+  \tocentry{#1}{#2}{#3}%
 \endgroup}
 
-% We use the same \entry macro as for the index entries.
-\let\tocentry = \entry
-
-% Space between chapter (or whatever) number and the title.
-\def\labelspace{\hskip1em \relax}
-
-\def\dopageno#1{{\rm #1}}
-\def\doshortpageno#1{{\rm #1}}
+% Used for the maximum width of a section number so we can align
+% section titles.
+\newdimen\secnowidth
+\secnowidth=0pt
+\newdimen\extrasecnoskip
+\extrasecnoskip=0pt
+
+% \tocentry{TITLE}{SEC NO}{PAGE}
+%
+\def\tocentry#1#2#3{%
+  \def\secno{#2}%
+  \ifx\empty\secno
+    \entry{#1}{#3}%
+  \else
+    \ifdim 0pt=\secnowidth
+      \setbox0=\hbox{#2\hskip\labelspace\hskip\extrasecnoskip}%
+    \else
+      \advance\secnowidth by \labelspace
+      \advance\secnowidth by \extrasecnoskip
+      \setbox0=\hbox to \secnowidth{%
+        #2\hskip\labelspace\hskip\extrasecnoskip\hfill}%
+    \fi
+    \entrycontskip=\wd0
+    \entry{\box0 #1}{#3}%
+  \fi
+}
+\newdimen\labelspace
+\labelspace=0.6em
 
 \def\chapentryfonts{\secfonts \rm}
 \def\secentryfonts{\textfonts}
@@ -7100,19 +7171,25 @@
 \newdimen\cartouter\newdimen\cartinner
 \newskip\normbskip\newskip\normpskip\newskip\normlskip
 
-
-\envdef\cartouche{%
+\envparseargdef\cartouche{%
   \cartouchefontdefs
   \ifhmode\par\fi  % can't be in the midst of a paragraph.
   \startsavinginserts
   \lskip=\leftskip \rskip=\rightskip
   \leftskip=0pt\rightskip=0pt % we want these *outside*.
+  %
+  % Set paragraph width for text inside cartouche.  There are
+  % left and right margins of 3pt each plus two vrules 0.4pt each.
   \cartinner=\hsize \advance\cartinner by-\lskip
   \advance\cartinner by-\rskip
+  \advance\cartinner by -6.8pt
+  %
+  % For drawing top and bottom of cartouche.  Each corner char
+  % adds 6pt and we take off the width of a rule to line up with the
+  % right boundary perfectly.
   \cartouter=\hsize
-  \advance\cartouter by 18.4pt	% allow for 3pt kerns on either
-				% side, and for 6pt waste from
-				% each corner char, and rule thickness
+  \advance\cartouter by 11.6pt
+  %
   \normbskip=\baselineskip \normpskip=\parskip \normlskip=\lineskip
   %
   % If this cartouche directly follows a sectioning command, we need the
@@ -7120,20 +7197,23 @@
   % collide with the section heading.
   \ifnum\lastpenalty>10000 \vskip\parskip \penalty\lastpenalty \fi
   %
-  \setbox\groupbox=\vbox\bgroup
+  \setbox\groupbox=\vtop\bgroup
       \baselineskip=0pt\parskip=0pt\lineskip=0pt
       \carttop
       \hbox\bgroup
-	  \hskip\lskip
-	  \vrule\kern3pt
-	  \vbox\bgroup
-	      \kern3pt
-	      \hsize=\cartinner
-	      \baselineskip=\normbskip
-	      \lineskip=\normlskip
-	      \parskip=\normpskip
-	      \vskip -\parskip
-	      \comment % For explanation, see the end of def\group.
+          \hskip\lskip
+          \vrule\kern3pt
+          \vbox\bgroup
+              \hsize=\cartinner
+              \baselineskip=\normbskip
+              \lineskip=\normlskip
+              \parskip=\normpskip
+              \def\arg{#1}%
+              \ifx\arg\empty\else
+                \centerV{\hfil \bf #1 \hfil}%
+              \fi
+              \kern3pt
+              \vskip -\parskip
 }
 \def\Ecartouche{%
               \ifhmode\par\fi
@@ -7287,22 +7367,6 @@
 }
 \let\Eraggedright\par
 
-\envdef\raggedleft{%
-  \parindent=0pt \leftskip0pt plus2em
-  \spaceskip.3333em \xspaceskip.5em \parfillskip=0pt
-  \hbadness=10000 % Last line will usually be underfull, so turn off
-                  % badness reporting.
-}
-\let\Eraggedleft\par
-
-\envdef\raggedcenter{%
-  \parindent=0pt \rightskip0pt plus1em \leftskip0pt plus1em
-  \spaceskip.3333em \xspaceskip.5em \parfillskip=0pt
-  \hbadness=10000 % Last line will usually be underfull, so turn off
-                  % badness reporting.
-}
-\let\Eraggedcenter\par
-
 
 % @quotation does normal linebreaking (hence we can't use \nonfillstart)
 % and narrows the margins.  We keep \parskip nonzero in general, since
@@ -7400,8 +7464,9 @@
 \endgroup
 %
 \def\setupverb{%
-  \tt  % easiest (and conventionally used) font for verbatim
+  \tt
   \def\par{\leavevmode\endgraf}%
+  \parindent = 0pt
   \setcodequotes
   \tabeightspaces
   % Respect line breaks,
@@ -7525,9 +7590,11 @@
 % file; b) letting users define the frontmatter in as flexible order as
 % possible is desirable.
 %
-\def\copying{\checkenv{}\begingroup\scanargctxt\docopying}
-\def\docopying#1@end copying{\endgroup\def\copyingtext{#1}}
-%
+\def\copying{\checkenv{}\begingroup\macrobodyctxt\docopying}
+{\catcode`\ =\other
+\gdef\docopying#1@end copying{\endgroup\def\copyingtext{#1}}
+}
+
 \def\insertcopying{%
   \begingroup
     \parindent = 0pt  % paragraph indentation looks wrong on title page
@@ -7575,31 +7642,19 @@
   \exdentamount=\defbodyindent
 }
 
-\def\dodefunx#1{%
-  % First, check whether we are in the right environment:
-  \checkenv#1%
-  %
-  % As above, allow line break if we have multiple x headers in a row.
-  % It's not a great place, though.
-  \ifnum\lastpenalty=10002 \penalty3000 \else \defunpenalty=10002 \fi
-  %
-  % And now, it's time to reuse the body of the original defun:
-  \expandafter\gobbledefun#1%
-}
-\def\gobbledefun#1\startdefun{}
-
-% \printdefunline \deffnheader{text}
+% Called as \printdefunline \deffooheader{text}
 %
 \def\printdefunline#1#2{%
   \begingroup
-    % call \deffnheader:
+    \plainfrenchspacing
+    % call \deffooheader:
     #1#2 \endheader
     % common ending:
     \interlinepenalty = 10000
     \advance\rightskip by 0pt plus 1fil\relax
     \endgraf
     \nobreak\vskip -\parskip
-    \penalty\defunpenalty  % signal to \startdefun and \dodefunx
+    \penalty\defunpenalty  % signal to \startdefun and \deffoox
     % Some of the @defun-type tags do not enable magic parentheses,
     % rendering the following check redundant.  But we don't optimize.
     \checkparencounts
@@ -7608,29 +7663,55 @@
 
 \def\Edefun{\endgraf\medbreak}
 
-% \makedefun{deffn} creates \deffn, \deffnx and \Edeffn;
-% the only thing remaining is to define \deffnheader.
+% @defblock, @defline do not automatically create index entries
+\envdef\defblock{%
+  \startdefun
+}
+\let\Edefblock\Edefun
+
+\def\defline{%
+  \doingtypefnfalse
+  \parseargusing\activeparens{\printdefunline\deflineheader}%
+}
+\def\deflineheader#1 #2 #3\endheader{%
+  \printdefname{#1}{}{#2}\magicamp\defunargs{#3\unskip}%
+}
+
+\def\deftypeline{%
+  \doingtypefntrue
+  \parseargusing\activeparens{\printdefunline\deftypelineheader}%
+}
+\def\deftypelineheader#1 #2 #3 #4\endheader{%
+  \printdefname{#1}{#2}{#3}\magicamp\defunargs{#4\unskip}%
+}
+
+% \makedefun{deffoo} (\deffooheader parameters) { (\deffooheader expansion) }
 %
+% Define \deffoo, \deffoox  \Edeffoo and \deffooheader.
 \def\makedefun#1{%
   \expandafter\let\csname E#1\endcsname = \Edefun
   \edef\temp{\noexpand\domakedefun
     \makecsname{#1}\makecsname{#1x}\makecsname{#1header}}%
   \temp
 }
-
-% \domakedefun \deffn \deffnx \deffnheader { (defn. of \deffnheader) }
-%
-% Define \deffn and \deffnx, without parameters.
-% \deffnheader has to be defined explicitly.
-%
 \def\domakedefun#1#2#3{%
   \envdef#1{%
     \startdefun
     \doingtypefnfalse    % distinguish typed functions from all else
     \parseargusing\activeparens{\printdefunline#3}%
   }%
-  \def#2{\dodefunx#1}%
-  \def#3%
+  \def#2{%
+    % First, check whether we are in the right environment:
+    \checkenv#1%
+    %
+    % As in \startdefun, allow line break if we have multiple x headers
+    % in a row.  It's not a great place, though.
+    \ifnum\lastpenalty=10002 \penalty3000 \else \defunpenalty=10002 \fi
+    %
+    \doingtypefnfalse    % distinguish typed functions from all else
+    \parseargusing\activeparens{\printdefunline#3}%
+  }%
+  \def#3% definition of \deffooheader follows
 }
 
 \newif\ifdoingtypefn       % doing typed function?
@@ -7655,74 +7736,51 @@
   \fi\fi
 }
 
-% \dosubind {index}{topic}{subtopic}
-%
-% If SUBTOPIC is present, precede it with a space, and call \doind.
-% (At some time during the 20th century, this made a two-level entry in an
-% index such as the operation index.  Nobody seemed to notice the change in
-% behaviour though.)
-\def\dosubind#1#2#3{%
-  \def\thirdarg{#3}%
-  \ifx\thirdarg\empty
-    \doind{#1}{#2}%
-  \else
-    \doind{#1}{#2\space#3}%
-  \fi
-}
-
 % Untyped functions:
 
 % @deffn category name args
-\makedefun{deffn}{\deffngeneral{}}
-
-% @deffn category class name args
-\makedefun{defop}#1 {\defopon{#1\ \putwordon}}
-
-% \defopon {category on}class name args
-\def\defopon#1#2 {\deffngeneral{\putwordon\ \code{#2}}{#1\ \code{#2}} }
+\makedefun{deffn}#1 #2 #3\endheader{%
+  \doind{fn}{\code{#2}}%
+  \printdefname{#1}{}{#2}\magicamp\defunargs{#3\unskip}%
+}
 
-% \deffngeneral {subind}category name args
-%
-\def\deffngeneral#1#2 #3 #4\endheader{%
-  \dosubind{fn}{\code{#3}}{#1}%
-  \defname{#2}{}{#3}\magicamp\defunargs{#4\unskip}%
+% @defop category class name args
+\makedefun{defop}#1 {\defopheaderx{#1\ \putwordon}}
+\def\defopheaderx#1#2 #3 #4\endheader{%
+  \doind{fn}{\code{#3}\space\putwordon\ \code{#2}}%
+  \printdefname{#1\ \code{#2}}{}{#3}\magicamp\defunargs{#4\unskip}%
 }
 
 % Typed functions:
 
 % @deftypefn category type name args
-\makedefun{deftypefn}{\deftypefngeneral{}}
+\makedefun{deftypefn}#1 #2 #3 #4\endheader{%
+  \doind{fn}{\code{#3}}%
+  \doingtypefntrue
+  \printdefname{#1}{#2}{#3}\defunargs{#4\unskip}%
+}
 
 % @deftypeop category class type name args
-\makedefun{deftypeop}#1 {\deftypeopon{#1\ \putwordon}}
-
-% \deftypeopon {category on}class type name args
-\def\deftypeopon#1#2 {\deftypefngeneral{\putwordon\ \code{#2}}{#1\ \code{#2}} }
-
-% \deftypefngeneral {subind}category type name args
-%
-\def\deftypefngeneral#1#2 #3 #4 #5\endheader{%
-  \dosubind{fn}{\code{#4}}{#1}%
+\makedefun{deftypeop}#1 {\deftypeopheaderx{#1\ \putwordon}}
+\def\deftypeopheaderx#1#2 #3 #4 #5\endheader{%
+  \doind{fn}{\code{#4}\space\putwordon\ \code{#1\ \code{#2}}}%
   \doingtypefntrue
-  \defname{#2}{#3}{#4}\defunargs{#5\unskip}%
+  \printdefname{#1\ \code{#2}}{#3}{#4}\defunargs{#5\unskip}%
 }
 
 % Typed variables:
 
 % @deftypevr category type var args
-\makedefun{deftypevr}{\deftypecvgeneral{}}
+\makedefun{deftypevr}#1 #2 #3 #4\endheader{%
+  \doind{vr}{\code{#3}}%
+  \printdefname{#1}{#2}{#3}\defunargs{#4\unskip}%
+}
 
 % @deftypecv category class type var args
-\makedefun{deftypecv}#1 {\deftypecvof{#1\ \putwordof}}
-
-% \deftypecvof {category of}class type var args
-\def\deftypecvof#1#2 {\deftypecvgeneral{\putwordof\ \code{#2}}{#1\ \code{#2}} }
-
-% \deftypecvgeneral {subind}category type var args
-%
-\def\deftypecvgeneral#1#2 #3 #4 #5\endheader{%
-  \dosubind{vr}{\code{#4}}{#1}%
-  \defname{#2}{#3}{#4}\defunargs{#5\unskip}%
+\makedefun{deftypecv}#1 {\deftypecvheaderx{#1\ \putwordof}}
+\def\deftypecvheaderx#1#2 #3 #4 #5\endheader{%
+  \doind{vr}{\code{#4}\space\putwordof\ \code{#2}}%
+  \printdefname{#1\ \code{#2}}{#3}{#4}\defunargs{#5\unskip}%
 }
 
 % Untyped variables:
@@ -7731,17 +7789,15 @@
 \makedefun{defvr}#1 {\deftypevrheader{#1} {} }
 
 % @defcv category class var args
-\makedefun{defcv}#1 {\defcvof{#1\ \putwordof}}
-
-% \defcvof {category of}class var args
-\def\defcvof#1#2 {\deftypecvof{#1}#2 {} }
+\makedefun{defcv}#1 {\defcvheaderx{#1\ \putwordof}}
+\def\defcvheaderx#1#2 {\deftypecvheaderx{#1}#2 {} }
 
 % Types:
 
 % @deftp category name args
 \makedefun{deftp}#1 #2 #3\endheader{%
   \doind{tp}{\code{#2}}%
-  \defname{#1}{}{#2}\defunargs{#3\unskip}%
+  \printdefname{#1}{}{#2}\defunargs{#3\unskip}%
 }
 
 % Remaining @defun-like shortcuts:
@@ -7752,19 +7808,19 @@
 \makedefun{defvar}{\defvrheader{\putwordDefvar} }
 \makedefun{defopt}{\defvrheader{\putwordDefopt} }
 \makedefun{deftypevar}{\deftypevrheader{\putwordDefvar} }
-\makedefun{defmethod}{\defopon\putwordMethodon}
-\makedefun{deftypemethod}{\deftypeopon\putwordMethodon}
-\makedefun{defivar}{\defcvof\putwordInstanceVariableof}
-\makedefun{deftypeivar}{\deftypecvof\putwordInstanceVariableof}
+\makedefun{defmethod}{\defopheaderx\putwordMethodon}
+\makedefun{deftypemethod}{\deftypeopheaderx\putwordMethodon}
+\makedefun{defivar}{\defcvheaderx\putwordInstanceVariableof}
+\makedefun{deftypeivar}{\deftypecvheaderx\putwordInstanceVariableof}
 
-% \defname, which formats the name of the @def (not the args).
+% \printdefname, which formats the name of the @def (not the args).
 % #1 is the category, such as "Function".
 % #2 is the return type, if any.
 % #3 is the function name.
 %
 % We are followed by (but not passed) the arguments, if any.
 %
-\def\defname#1#2#3{%
+\def\printdefname#1#2#3{%
   \par
   % Get the values of \leftskip and \rightskip as they were outside the @def...
   \advance\leftskip by -\defbodyindent
@@ -7774,9 +7830,7 @@
   \rettypeownlinefalse
   \ifdoingtypefn  % doing a typed function specifically?
     % then check user option for putting return type on its own line:
-    \expandafter\ifx\csname SETtxideftypefnnl\endcsname\relax \else
-      \rettypeownlinetrue
-    \fi
+    \ifflagclear{txideftypefnnl}{}{\rettypeownlinetrue}%
   \fi
   %
   % How we'll format the category name.  Putting it in brackets helps
@@ -7820,6 +7874,8 @@
   \tolerance=10000 \hbadness=10000
   \exdentamount=\defbodyindent
   {%
+    \def\^^M{}% for line continuation
+    %
     % defun fonts. We use typewriter by default (used to be bold) because:
     % . we're printing identifiers, they should be in tt in principle.
     % . in languages with many accents, such as Czech or French, it's
@@ -7841,30 +7897,23 @@
     \fi           % no return type
     #3% output function name
   }%
-  {\rm\enskip}% hskip 0.5 em of \rmfont
+  \ifflagclear{txidefnamenospace}{%
+    {\rm\enskip}% hskip 0.5 em of \rmfont
+  }{}%
   %
   \boldbrax
   % arguments will be output next, if any.
 }
 
-% Print arguments in slanted roman (not ttsl), inconsistently with using
-% tt for the name.  This is because literal text is sometimes needed in
-% the argument list (groff manual), and ttsl and tt are not very
-% distinguishable.  Prevent hyphenation at `-' chars.
-%
+% Print arguments.  Use slanted for @def*, typewriter for @deftype*.
 \def\defunargs#1{%
-  % use sl by default (not ttsl),
-  % tt for the names.
-  \df \sl \hyphenchar\font=0
-  %
-  % On the other hand, if an argument has two dashes (for instance), we
-  % want a way to get ttsl.  We used to recommend @var for that, so
-  % leave the code in, but it's strange for @var to lead to typewriter.
-  % Nowadays we recommend @code, since the difference between a ttsl hyphen
-  % and a tt hyphen is pretty tiny.  @code also disables ?` !`.
-  \def\var##1{{\setregularquotes\ttslanted{##1}}}%
-  #1%
-  \sl\hyphenchar\font=45
+  \bgroup
+    \def\^^M{}% for line continuation
+    \df \ifdoingtypefn \tt \else \sl \fi
+    \ifflagclear{txicodevaristt}{}%
+       {\def\var##1{{\setregularquotes \ttsl ##1}}}%
+    #1%
+  \egroup
 }
 
 % We want ()& to print specially on the defun line.
@@ -7883,9 +7932,12 @@
 % so TeX would otherwise complain about undefined control sequence.
 {
   \activeparens
-  \global\let(=\lparen \global\let)=\rparen
-  \global\let=\lbrack \global\let=\rbrack
-  \global\let& = \&
+  \gdef\defcharsdefault{%
+    \let(=\lparen \let)=\rparen
+    \let=\lbrack \let=\rbrack
+    \let& = \&%
+  }
+  \globaldefs=1 \defcharsdefault
 
   \gdef\boldbrax{\let(=\opnr\let)=\clnr\let=\lbrb\let=\rbrb}
   \gdef\magicamp{\let&=\amprm}
@@ -7896,7 +7948,7 @@
 
 % If we encounter &foo, then turn on ()-hacking afterwards
 \newif\ifampseen
-\def\amprm#1 {\ampseentrue{\bf\&#1 }}
+\def\amprm#1 {\ampseentrue{\rm\&#1 }}
 
 \def\parenfont{%
   \ifampseen
@@ -8069,24 +8121,17 @@
   \catcode`\_=\other
   \catcode`\|=\other
   \catcode`\~=\other
-  \passthroughcharstrue
-}
-
-\def\scanargctxt{% used for copying and captions, not macros.
-  \scanctxt
   \catcode`\@=\other
-  \catcode`\\=\other
   \catcode`\^^M=\other
+  \catcode`\\=\active
+  \passthroughcharstrue
 }
 
-\def\macrobodyctxt{% used for @macro definitions
+\def\macrobodyctxt{% used for @macro definitions and @copying
   \scanctxt
   \catcode`\ =\other
-  \catcode`\@=\other
   \catcode`\{=\other
   \catcode`\}=\other
-  \catcode`\^^M=\other
-  \usembodybackslash
 }
 
 % Used when scanning braced macro arguments.  Note, however, that catcode
@@ -8095,14 +8140,10 @@
 \def\macroargctxt{%
   \scanctxt
   \catcode`\ =\active
-  \catcode`\@=\other
-  \catcode`\^^M=\other
-  \catcode`\\=\active
 }
 
 \def\macrolineargctxt{% used for whole-line arguments without braces
   \scanctxt
-  \catcode`\@=\other
   \catcode`\{=\other
   \catcode`\}=\other
 }
@@ -8146,7 +8187,7 @@
      \global\expandafter\let\csname ismacro.\the\macname\endcsname=1%
      \addtomacrolist{\the\macname}%
   \fi
-  \begingroup \macrobodyctxt
+  \begingroup \macrobodyctxt \usembodybackslash
   \ifrecursive \expandafter\parsermacbody
   \else \expandafter\parsemacbody
   \fi}
@@ -8161,8 +8202,6 @@
       \let\commondummyword\unmacrodo
       \xdef\macrolist{\macrolist}%
     \endgroup
-  \else
-    \errmessage{Macro #1 not defined}%
   \fi
 }
 
@@ -8229,14 +8268,14 @@
 % Read recursive and nonrecursive macro bodies. (They're different since
 % rec and nonrec macros end differently.)
 %
-% We are in \macrobodyctxt, and the \xdef causes backslashshes in the macro
+% We are in \macrobodyctxt, and the \xdef causes backslashes in the macro
 % body to be transformed.
-% Set \macrobody to the body of the macro, and call \defmacro.
+% Set \macrobody to the body of the macro, and call \macrodef.
 %
 {\catcode`\ =\other\long\gdef\parsemacbody#1@end macro{%
-\xdef\macrobody{\eatcr{#1}}\endgroup\defmacro}}%
+\xdef\macrobody{\eatcr{#1}}\endgroup\macrodef}}%
 {\catcode`\ =\other\long\gdef\parsermacbody#1@end rmacro{%
-\xdef\macrobody{\eatcr{#1}}\endgroup\defmacro}}%
+\xdef\macrobody{\eatcr{#1}}\endgroup\macrodef}}%
 
 % Make @ a letter, so that we can make private-to-Texinfo macro names.
 \edef\texiatcatcode{\the\catcode`\@}
@@ -8455,35 +8494,36 @@
 % \xdef is used so that macro definitions will survive the file
 % they're defined in: @include reads the file inside a group.
 %
-\def\defmacro{%
+\def\macrodef{%
   \let\hash=##% convert placeholders to macro parameter chars
   \ifnum\paramno=1
-    \def\xeatspaces##1{##1}%
-    % This removes the pair of braces around the argument.  We don't
-    % use \eatspaces, because this can cause ends of lines to be lost
-    % when the argument to \eatspaces is read, leading to line-based
-    % commands like "@itemize" not being read correctly.
-  \else
-    \let\xeatspaces\relax % suppress expansion
+    \long\def\xeatspaces##1{##1}%
+    % We don't use \xeatspaces for single-argument macros, because we
+    % want to keep ends of lines.  This definition removes \xeatspaces
+    % when \macrobody is expanded below.
+  \else
+    \def\xeatspaces{\string\xeatspaces}%
+    % This expands \xeatspaces as a sequence of character tokens, which
+    % stops \scantokens inserting an extra space after the control sequence.
   \fi
   \ifcase\paramno
   % 0
     \expandafter\xdef\csname\the\macname\endcsname{%
-      \bgroup
+      \begingroup
         \noexpand\spaceisspace
         \noexpand\endlineisspace
         \noexpand\expandafter % skip any whitespace after the macro name.
         \expandafter\noexpand\csname\the\macname @@@\endcsname}%
     \expandafter\xdef\csname\the\macname @@@\endcsname{%
-      \egroup
+      \endgroup
       \noexpand\scanmacro{\macrobody}}%
   \or % 1
     \expandafter\xdef\csname\the\macname\endcsname{%
-       \bgroup
+       \begingroup
        \noexpand\braceorline
        \expandafter\noexpand\csname\the\macname @@@\endcsname}%
     \expandafter\xdef\csname\the\macname @@@\endcsname##1{%
-      \egroup
+      \endgroup
       \noexpand\scanmacro{\macrobody}%
       }%
   \else % at most 9
@@ -8494,7 +8534,7 @@
       % @MACNAME@@@ removes braces surrounding the argument list.
       % @MACNAME@@@@ scans the macro body with arguments substituted.
       \expandafter\xdef\csname\the\macname\endcsname{%
-        \bgroup
+        \begingroup
         \noexpand\expandafter  % This \expandafter skip any spaces after the
         \noexpand\macroargctxt % macro before we change the catcode of space.
         \noexpand\expandafter
@@ -8508,7 +8548,7 @@
       \expandafter\xdef
       \expandafter\expandafter
         \csname\the\macname @@@@\endcsname\paramlist{%
-          \egroup\noexpand\scanmacro{\macrobody}}%
+          \endgroup\noexpand\scanmacro{\macrobody}}%
     \else % 10 or more:
       \expandafter\xdef\csname\the\macname\endcsname{%
         \noexpand\getargvals@{\the\macname}{\argl}%
@@ -8630,6 +8670,75 @@
   \fi \macnamexxx}
 
 
+% @linemacro
+
+\parseargdef\linemacro{%
+  \getargs{#1}% now \macname is the macname and \argl the arglist
+  \ifx\argl\empty
+    \paramno=0
+    \let\hash\relax
+    \def\paramlist{\hash 1\endlinemacro}%
+  \else
+    \expandafter\linegetparamlist\argl;%
+  \fi
+  \begingroup \macrobodyctxt \usembodybackslash
+  \parselinemacrobody
+}
+
+% Build up \paramlist which will be used as the parameter text for the macro.
+% At the end it will be like "#1 #2 #3\endlinemacro".
+\def\linegetparamlist#1;{%
+  \paramno=0\def\paramlist{}%
+  \let\hash\relax
+  \linegetparamlistxxx#1,;,%
+}
+\def\linegetparamlistxxx#1,{%
+  \if#1;\let\next=\linegetparamlistxxxx
+  \else \let\next=\linegetparamlistxxx
+    \advance\paramno by 1
+    \expandafter\edef\csname macarg.\eatspaces{#1}\endcsname
+        {\hash\the\paramno}%
+    \edef\paramlist{\paramlist\hash\the\paramno\space}%
+  \fi\next}
+\def\linegetparamlistxxxx{%
+  \expandafter\fixparamlist\paramlist\fixparamlist
+}
+% Replace final space token
+\def\fixparamlist#1 \fixparamlist{%
+  \def\paramlist{#1\endlinemacro}%
+}
+
+% Read the body of the macro, replacing backslash-surrounded variables
+%
+{\catcode`\ =\other\long\gdef\parselinemacrobody#1@end linemacro{%
+\xdef\macrobody{#1}%
+\endgroup
+\linemacrodef
+}}
+
+% Make the definition
+\def\linemacrodef{%
+  \let\hash=##%
+  \expandafter\xdef\csname\the\macname\endcsname{%
+    \bgroup
+    \noexpand\parsearg
+    \expandafter\noexpand\csname\the\macname @@\endcsname
+  }
+  \expandafter\xdef\csname\the\macname @@\endcsname##1{%
+    \egroup
+    \expandafter\noexpand
+    \csname\the\macname @@@\endcsname##1\noexpand\endlinemacro
+  }
+  \expandafter\expandafter
+  \expandafter\xdef
+  \expandafter\expandafter\csname\the\macname @@@\endcsname\paramlist{%
+    \newlinechar=13 % split \macrobody into lines
+    \noexpand\scantokens{\macrobody}%
+  }
+}
+
+
+
 % @alias.
 % We need some trickery to remove the optional spaces around the equal
 % sign.  Make them active and then expand them all to nothing.
@@ -8681,9 +8790,11 @@
 }
 \def\wordTop{Top}
 
-% Until the next @node or @bye command, divert output to a box that is not
-% output.
-\def\ignorenode{\setbox\dummybox\vbox\bgroup\def\node{\egroup\node}%
+% Until the next @node, @part or @bye command, divert output to a box that
+% is not output.
+\def\ignorenode{\setbox\dummybox\vbox\bgroup
+\def\part{\egroup\part}%
+\def\node{\egroup\node}%
 \ignorenodebye
 }
 
@@ -8704,6 +8815,11 @@
   \fi
 }
 
+% @nodedescription, @nodedescriptionblock - do nothing for TeX
+\parseargdef\nodedescription{}
+\def\nodedescriptionblock{\doignore{nodedescriptionblock}}
+
+
 % @anchor{NAME} -- define xref target at arbitrary point.
 %
 \newcount\savesfregister
@@ -8785,109 +8901,11 @@
 \def\xrefX#1,#2,#3,#4,#5,#6{\begingroup
   \unsepspaces
   %
-  % Get args without leading/trailing spaces.
-  \def\printedrefname{\ignorespaces #3}%
-  \setbox\printedrefnamebox = \hbox{\printedrefname\unskip}%
-  %
+  \getprintedrefname{#1}{#3}{#5}%
   \def\infofilename{\ignorespaces #4}%
   \setbox\infofilenamebox = \hbox{\infofilename\unskip}%
   %
-  \def\printedmanual{\ignorespaces #5}%
-  \setbox\printedmanualbox  = \hbox{\printedmanual\unskip}%
-  %
-  % If the printed reference name (arg #3) was not explicitly given in
-  % the @xref, figure out what we want to use.
-  \ifdim \wd\printedrefnamebox = 0pt
-    % No printed node name was explicitly given.
-    \expandafter\ifx\csname SETxref-automatic-section-title\endcsname \relax
-      % Not auto section-title: use node name inside the square brackets.
-      \def\printedrefname{\ignorespaces #1}%
-    \else
-      % Auto section-title: use chapter/section title inside
-      % the square brackets if we have it.
-      \ifdim \wd\printedmanualbox > 0pt
-        % It is in another manual, so we don't have it; use node name.
-        \def\printedrefname{\ignorespaces #1}%
-      \else
-        \ifhavexrefs
-          % We (should) know the real title if we have the xref values.
-          \def\printedrefname{\refx{#1-title}}%
-        \else
-          % Otherwise just copy the Info node name.
-          \def\printedrefname{\ignorespaces #1}%
-        \fi%
-      \fi
-    \fi
-  \fi
-  %
-  % Make link in pdf output.
-  \ifpdf
-    % For pdfTeX and LuaTeX
-    {\indexnofonts
-     \makevalueexpandable
-     \turnoffactive
-     % This expands tokens, so do it after making catcode changes, so _
-     % etc. don't get their TeX definitions.  This ignores all spaces in
-     % #4, including (wrongly) those in the middle of the filename.
-     \getfilename{#4}%
-     %
-     % This (wrongly) does not take account of leading or trailing
-     % spaces in #1, which should be ignored.
-     \setpdfdestname{#1}%
-     %
-     \ifx\pdfdestname\empty
-       \def\pdfdestname{Top}% no empty targets
-     \fi
-     %
-     \leavevmode
-     \startlink attr{/Border 0 0 0}%
-     \ifnum\filenamelength>0
-       goto file{\the\filename.pdf} name{\pdfdestname}%
-     \else
-       goto name{\pdfmkpgn{\pdfdestname}}%
-     \fi
-    }%
-    \setcolor{\linkcolor}%
-  \else
-    \ifx\XeTeXrevision\thisisundefined
-    \else
-      % For XeTeX
-      {\indexnofonts
-       \makevalueexpandable
-       \turnoffactive
-       % This expands tokens, so do it after making catcode changes, so _
-       % etc. don't get their TeX definitions.  This ignores all spaces in
-       % #4, including (wrongly) those in the middle of the filename.
-       \getfilename{#4}%
-       %
-       % This (wrongly) does not take account of leading or trailing
-       % spaces in #1, which should be ignored.
-       \setpdfdestname{#1}%
-       %
-       \ifx\pdfdestname\empty
-         \def\pdfdestname{Top}% no empty targets
-       \fi
-       %
-       \leavevmode
-       \ifnum\filenamelength>0
-         % With default settings,
-         % XeTeX (xdvipdfmx) replaces link destination names with integers.
-         % In this case, the replaced destination names of
-         % remote PDFs are no longer known.  In order to avoid a replacement,
-         % you can use xdvipdfmx's command line option `-C 0x0010'.
-         % If you use XeTeX 0.99996+ (TeX Live 2016+),
-         % this command line option is no longer necessary
-         % because we can use the `dvipdfmx:config' special.
-         \special{pdf:bann << /Border 0 0 0 /Type /Annot /Subtype /Link /A
-           << /S /GoToR /F (\the\filename.pdf) /D (\pdfdestname) >> >>}%
-       \else
-         \special{pdf:bann << /Border 0 0 0 /Type /Annot /Subtype /Link /A
-           << /S /GoTo /D (\pdfdestname) >> >>}%
-       \fi
-      }%
-      \setcolor{\linkcolor}%
-    \fi
-  \fi
+  \startxreflink{#1}{#4}%
   {%
     % Have to otherify everything special to allow the \csname to
     % include an _ in the xref name, etc.
@@ -8948,12 +8966,11 @@
       % output the `mynode' via the macro below so it can be overridden.
       \xrefprintnodename\printedrefname
       %
-      \expandafter\ifx\csname SETtxiomitxrefpg\endcsname\relax
-        % But we always want a comma and a space:
-        ,\space
-        %
+      \ifflagclear{txiomitxrefpg}{%
+        % We always want a comma
+        ,%
         % output the `page 3'.
-        \turnoffactive \putwordpage\tie\refx{#1-pg}%
+        \turnoffactive \putpageref{#1}%
         % Add a , if xref followed by a space
         \if\space\noexpand\tokenafterxref ,%
         \else\ifx\	\tokenafterxref ,% @TAB
@@ -8963,12 +8980,103 @@
                   \tokenafterxref ,%    @NL
         \else\ifx\tie\tokenafterxref ,% @tie
         \fi\fi\fi\fi\fi\fi
-      \fi
+      }{}%
     \fi\fi
   \fi
   \endlink
 \endgroup}
 
+% \getprintedrefname{NODE}{LABEL}{MANUAL}
+% - set \printedrefname and \printedmanual
+%
+\def\getprintedrefname#1#2#3{%
+  % Get args without leading/trailing spaces.
+  \def\printedrefname{\ignorespaces #2}%
+  \setbox\printedrefnamebox = \hbox{\printedrefname\unskip}%
+  %
+  \def\printedmanual{\ignorespaces #3}%
+  \setbox\printedmanualbox  = \hbox{\printedmanual\unskip}%
+  %
+  % If the printed reference name (arg #2) was not explicitly given in
+  % the @xref, figure out what we want to use.
+  \ifdim \wd\printedrefnamebox = 0pt
+    % No printed node name was explicitly given.
+    \expandafter\ifx\csname SETxref-automatic-section-title\endcsname \relax
+      % Not auto section-title: use node name inside the square brackets.
+      \def\printedrefname{\ignorespaces #1}%
+    \else
+      % Auto section-title: use chapter/section title inside
+      % the square brackets if we have it.
+      \ifdim \wd\printedmanualbox > 0pt
+        % It is in another manual, so we don't have it; use node name.
+        \def\printedrefname{\ignorespaces #1}%
+      \else
+        \ifhavexrefs
+          % We (should) know the real title if we have the xref values.
+          \def\printedrefname{\refx{#1-title}}%
+        \else
+          % Otherwise just copy the Info node name.
+          \def\printedrefname{\ignorespaces #1}%
+        \fi%
+      \fi
+    \fi
+  \fi
+}
+
+% \startxreflink{NODE}{FILE} - start link in pdf output.
+\def\startxreflink#1#2{%
+  \ifpdforxetex
+    % For pdfTeX and LuaTeX
+    {\indexnofonts
+     \makevalueexpandable
+     \turnoffactive
+     % This expands tokens, so do it after making catcode changes, so _
+     % etc. don't get their TeX definitions.  This ignores all spaces in
+     % #2, including (wrongly) those in the middle of the filename.
+     \getfilename{#2}%
+     %
+     % This (wrongly) does not take account of leading or trailing
+     % spaces in #1, which should be ignored.
+     \setpdfdestname{#1}%
+     %
+     \ifx\pdfdestname\empty
+       \def\pdfdestname{Top}% no empty targets
+     \fi
+     %
+     \leavevmode
+     \ifpdf
+       \startlink attr{/Border 0 0 0}%
+       \ifnum\filenamelength>0
+         goto file{\the\filename.pdf} name{\pdfdestname}%
+       \else
+         goto name{\pdfmkpgn{\pdfdestname}}%
+       \fi
+     \else % XeTeX
+       \ifnum\filenamelength>0
+         % With default settings,
+         % XeTeX (xdvipdfmx) replaces link destination names with integers.
+         % In this case, the replaced destination names of
+         % remote PDFs are no longer known.  In order to avoid a replacement,
+         % you can use xdvipdfmx's command line option `-C 0x0010'.
+         % If you use XeTeX 0.99996+ (TeX Live 2016+),
+         % this command line option is no longer necessary
+         % because we can use the `dvipdfmx:config' special.
+         \special{pdf:bann << /Border 0 0 0 /Type /Annot /Subtype /Link /A
+           << /S /GoToR /F (\the\filename.pdf) /D (\pdfdestname) >> >>}%
+       \else
+         \special{pdf:bann << /Border 0 0 0 /Type /Annot /Subtype /Link /A
+           << /S /GoTo /D (\pdfdestname) >> >>}%
+       \fi
+     \fi
+    }%
+    \setcolor{\linkcolor}%
+  \fi
+}
+
+% can be overridden in translation files
+\def\putpageref#1{%
+  \space\putwordpage\tie\refx{#1-pg}}
+
 % Output a cross-manual xref to #1.  Used just above (twice).
 %
 % Only include the text "Section ``foo'' in" if the foo is neither
@@ -9002,6 +9110,21 @@
 %
 \def\xrefprintnodename#1{#1}
 
+% @link{NODENAME, LABEL, MANUAL} - create a "plain" link, with no
+% page number.  Not useful if printed on paper.
+%
+\def\link#1{\linkX#1,,,}
+\def\linkX#1,#2,#3,#4{%
+  \begingroup
+  \unsepspaces
+  \getprintedrefname{#1}{#2}{#3}%
+  \startxreflink{#1}{#3}%
+  \printedrefname
+  \endlink
+  \endgroup
+}
+
+
 % Things referred to by \setref.
 %
 \def\Ynothing{}
@@ -9380,6 +9503,12 @@
     \imagexxx #1,,,,,\finish
   \fi
 }
+
+% Approximate height of a line in the standard text font.
+\newdimen\capheight
+\setbox0=\vbox{\tenrm H}
+\capheight=\ht0
+
 %
 % Arguments to @image:
 % #1 is (mandatory) image filename; we tack on .eps extension.
@@ -9392,32 +9521,30 @@
   \catcode`\^^M = 5     % in case we're inside an example
   \normalturnoffactive  % allow _ et al. in names
   \makevalueexpandable
-  % If the image is by itself, center it.
   \ifvmode
     \imagevmodetrue
-  \else \ifx\centersub\centerV
-    % for @center @image, we need a vbox so we can have our vertical space
-    \imagevmodetrue
-    \vbox\bgroup % vbox has better behavior than vtop herev
-  \fi\fi
-  %
-  \ifimagevmode
-    \nobreak\medskip
+    \medskip
     % Usually we'll have text after the image which will insert
     % \parskip glue, so insert it here too to equalize the space
     % above and below.
-    \nobreak\vskip\parskip
-    \nobreak
+    \vskip\parskip
+    %
+    % Place image in a \vtop for a top page margin that is (close to) correct,
+    % as \topskip glue is relative to the first baseline.
+    \vtop\bgroup \kern -\capheight \vskip-\parskip
   \fi
   %
-  % Leave vertical mode so that indentation from an enclosing
-  %  environment such as @quotation is respected.
-  % However, if we're at the top level, we don't want the
-  %  normal paragraph indentation.
-  % On the other hand, if we are in the case of @center @image, we don't
-  %  want to start a paragraph, which will create a hsize-width box and
-  %  eradicate the centering.
-  \ifx\centersub\centerV \else \imageindent \fi
+  \ifx\centersub\centerV
+    % For @center @image, enter vertical mode and add vertical space
+    % Enter an extra \parskip because @center doesn't add space itself.
+    \vbox\bgroup\vskip\parskip\medskip\vskip\parskip
+  \else
+    % Enter horizontal mode so that indentation from an enclosing
+    %  environment such as @quotation is respected.
+    % However, if we're at the top level, we don't want the
+    %  normal paragraph indentation.
+    \imageindent
+  \fi
   %
   % Output the image.
   \ifpdf
@@ -9439,9 +9566,13 @@
   \fi
   %
   \ifimagevmode
+    \egroup
     \medskip  % space after a standalone image
   \fi
-  \ifx\centersub\centerV \egroup \fi
+  \ifx\centersub\centerV % @center @image
+    \medskip
+    \egroup % close \vbox
+  \fi
 \endgroup}
 
 
@@ -9608,8 +9739,8 @@
 %
 \def\caption{\docaption\thiscaption}
 \def\shortcaption{\docaption\thisshortcaption}
-\def\docaption{\checkenv\float \bgroup\scanargctxt\defcaption}
-\def\defcaption#1#2{\egroup \def#1{#2}}
+\def\docaption{\checkenv\float \bgroup\scanctxt\docaptionz}
+\def\docaptionz#1#2{\egroup \def#1{#2}}
 
 % The parameter is the control sequence identifying the counter we are
 % going to use.  Create it if it doesn't exist and assign it to \floatno.
@@ -9898,12 +10029,10 @@
        % For native Unicode handling (XeTeX and LuaTeX)
        \nativeunicodechardefs
      \else
-       % For treating UTF-8 as byte sequences (TeX, eTeX and pdfTeX)
+       % For treating UTF-8 as byte sequences (TeX, eTeX and pdfTeX).
+       % Since we already invoke \utfeightchardefs at the top level,
+       % making non-ascii chars active is sufficient.
        \setnonasciicharscatcode\active
-       % since we already invoked \utfeightchardefs at the top level
-       % (below), do not re-invoke it, otherwise our check for duplicated
-       % definitions gets triggered.  Making non-ascii chars active is
-       % sufficient.
      \fi
   %
   \else
@@ -9928,7 +10057,6 @@
   \fi
 }
 
-% emacs-page
 % A message to be logged when using a character that isn't available
 % the default font encoding (OT1).
 %
@@ -9937,12 +10065,6 @@
 % Take account of \c (plain) vs. \, (Texinfo) difference.
 \def\cedilla#1{\ifx\c\ptexc\c{#1}\else\,{#1}\fi}
 
-% First, make active non-ASCII characters in order for them to be
-% correctly categorized when TeX reads the replacement text of
-% macros containing the character definitions.
-\setnonasciicharscatcode\active
-%
-
 \def\gdefchar#1#2{%
 \gdef#1{%
    \ifpassthroughchars
@@ -9952,8 +10074,14 @@
    \fi
 }}
 
+\begingroup
+
+% Make non-ASCII characters active for defining the character definition
+% macros.
+\setnonasciicharscatcode\active
+
 % Latin1 (ISO-8859-1) character definitions.
-\def\latonechardefs{%
+\gdef\latonechardefs{%
   \gdefchar^^a0{\tie}
   \gdefchar^^a1{\exclamdown}
   \gdefchar^^a2{{\tcfont \char162}} % cent
@@ -10058,7 +10186,7 @@
 }
 
 % Latin9 (ISO-8859-15) encoding character definitions.
-\def\latninechardefs{%
+\gdef\latninechardefs{%
   % Encoding is almost identical to Latin1.
   \latonechardefs
   %
@@ -10073,7 +10201,7 @@
 }
 
 % Latin2 (ISO-8859-2) character definitions.
-\def\lattwochardefs{%
+\gdef\lattwochardefs{%
   \gdefchar^^a0{\tie}
   \gdefchar^^a1{\ogonek{A}}
   \gdefchar^^a2{\u{}}
@@ -10091,7 +10219,7 @@
   \gdefchar^^ae{\v Z}
   \gdefchar^^af{\dotaccent Z}
   %
-  \gdefchar^^b0{\textdegree{}}
+  \gdefchar^^b0{\textdegree}
   \gdefchar^^b1{\ogonek{a}}
   \gdefchar^^b2{\ogonek{ }}
   \gdefchar^^b3{\l}
@@ -10177,6 +10305,8 @@
   \gdefchar^^ff{\dotaccent{}}
 }
 
+\endgroup % active chars
+
 % UTF-8 character definitions.
 %
 % This code to support UTF-8 is based on LaTeX's utf8.def, with some
@@ -10328,9 +10458,9 @@
   % Given the value in \countUTFz as a Unicode code point, set \UTFviiiTmp
   % to the corresponding UTF-8 sequence.
   \gdef\parseXMLCharref{%
-    \ifnum\countUTFz < "A0\relax
+    \ifnum\countUTFz < "20\relax
       \errhelp = \EMsimple
-      \errmessage{Cannot define Unicode char value < 00A0}%
+      \errmessage{Cannot define Unicode char value < 0020}%
     \else\ifnum\countUTFz < "800\relax
       \parseUTFviiiA,%
       \parseUTFviiiB C\UTFviiiTwoOctetsName.,%
@@ -10400,6 +10530,103 @@
 % least make most of the characters not bomb out.
 %
 \def\unicodechardefs{%
+  \DeclareUnicodeCharacter{0020}{ } % space
+  \DeclareUnicodeCharacter{0021}{\char"21 }% % space to terminate number
+  \DeclareUnicodeCharacter{0022}{\char"22 }%
+  \DeclareUnicodeCharacter{0023}{\char"23 }%
+  \DeclareUnicodeCharacter{0024}{\char"24 }%
+  \DeclareUnicodeCharacter{0025}{\char"25 }%
+  \DeclareUnicodeCharacter{0026}{\char"26 }%
+  \DeclareUnicodeCharacter{0027}{\char"27 }%
+  \DeclareUnicodeCharacter{0028}{\char"28 }%
+  \DeclareUnicodeCharacter{0029}{\char"29 }%
+  \DeclareUnicodeCharacter{002A}{\char"2A }%
+  \DeclareUnicodeCharacter{002B}{\char"2B }%
+  \DeclareUnicodeCharacter{002C}{\char"2C }%
+  \DeclareUnicodeCharacter{002D}{\char"2D }%
+  \DeclareUnicodeCharacter{002E}{\char"2E }%
+  \DeclareUnicodeCharacter{002F}{\char"2F }%
+  \DeclareUnicodeCharacter{0030}{0}%
+  \DeclareUnicodeCharacter{0031}{1}%
+  \DeclareUnicodeCharacter{0032}{2}%
+  \DeclareUnicodeCharacter{0033}{3}%
+  \DeclareUnicodeCharacter{0034}{4}%
+  \DeclareUnicodeCharacter{0035}{5}%
+  \DeclareUnicodeCharacter{0036}{6}%
+  \DeclareUnicodeCharacter{0037}{7}%
+  \DeclareUnicodeCharacter{0038}{8}%
+  \DeclareUnicodeCharacter{0039}{9}%
+  \DeclareUnicodeCharacter{003A}{\char"3A }%
+  \DeclareUnicodeCharacter{003B}{\char"3B }%
+  \DeclareUnicodeCharacter{003C}{\char"3C }%
+  \DeclareUnicodeCharacter{003D}{\char"3D }%
+  \DeclareUnicodeCharacter{003E}{\char"3E }%
+  \DeclareUnicodeCharacter{003F}{\char"3F }%
+  \DeclareUnicodeCharacter{0040}{\char"40 }%
+  \DeclareUnicodeCharacter{0041}{A}%
+  \DeclareUnicodeCharacter{0042}{B}%
+  \DeclareUnicodeCharacter{0043}{C}%
+  \DeclareUnicodeCharacter{0044}{D}%
+  \DeclareUnicodeCharacter{0045}{E}%
+  \DeclareUnicodeCharacter{0046}{F}%
+  \DeclareUnicodeCharacter{0047}{G}%
+  \DeclareUnicodeCharacter{0048}{H}%
+  \DeclareUnicodeCharacter{0049}{I}%
+  \DeclareUnicodeCharacter{004A}{J}%
+  \DeclareUnicodeCharacter{004B}{K}%
+  \DeclareUnicodeCharacter{004C}{L}%
+  \DeclareUnicodeCharacter{004D}{M}%
+  \DeclareUnicodeCharacter{004E}{N}%
+  \DeclareUnicodeCharacter{004F}{O}%
+  \DeclareUnicodeCharacter{0050}{P}%
+  \DeclareUnicodeCharacter{0051}{Q}%
+  \DeclareUnicodeCharacter{0052}{R}%
+  \DeclareUnicodeCharacter{0053}{S}%
+  \DeclareUnicodeCharacter{0054}{T}%
+  \DeclareUnicodeCharacter{0055}{U}%
+  \DeclareUnicodeCharacter{0056}{V}%
+  \DeclareUnicodeCharacter{0057}{W}%
+  \DeclareUnicodeCharacter{0058}{X}%
+  \DeclareUnicodeCharacter{0059}{Y}%
+  \DeclareUnicodeCharacter{005A}{Z}%
+  \DeclareUnicodeCharacter{005B}{\char"5B }%
+  \DeclareUnicodeCharacter{005C}{\char"5C }%
+  \DeclareUnicodeCharacter{005D}{\char"5D }%
+  \DeclareUnicodeCharacter{005E}{\char"5E }%
+  \DeclareUnicodeCharacter{005F}{\char"5F }%
+  \DeclareUnicodeCharacter{0060}{\char"60 }%
+  \DeclareUnicodeCharacter{0061}{a}%
+  \DeclareUnicodeCharacter{0062}{b}%
+  \DeclareUnicodeCharacter{0063}{c}%
+  \DeclareUnicodeCharacter{0064}{d}%
+  \DeclareUnicodeCharacter{0065}{e}%
+  \DeclareUnicodeCharacter{0066}{f}%
+  \DeclareUnicodeCharacter{0067}{g}%
+  \DeclareUnicodeCharacter{0068}{h}%
+  \DeclareUnicodeCharacter{0069}{i}%
+  \DeclareUnicodeCharacter{006A}{j}%
+  \DeclareUnicodeCharacter{006B}{k}%
+  \DeclareUnicodeCharacter{006C}{l}%
+  \DeclareUnicodeCharacter{006D}{m}%
+  \DeclareUnicodeCharacter{006E}{n}%
+  \DeclareUnicodeCharacter{006F}{o}%
+  \DeclareUnicodeCharacter{0070}{p}%
+  \DeclareUnicodeCharacter{0071}{q}%
+  \DeclareUnicodeCharacter{0072}{r}%
+  \DeclareUnicodeCharacter{0073}{s}%
+  \DeclareUnicodeCharacter{0074}{t}%
+  \DeclareUnicodeCharacter{0075}{u}%
+  \DeclareUnicodeCharacter{0076}{v}%
+  \DeclareUnicodeCharacter{0077}{w}%
+  \DeclareUnicodeCharacter{0078}{x}%
+  \DeclareUnicodeCharacter{0079}{y}%
+  \DeclareUnicodeCharacter{007A}{z}%
+  \DeclareUnicodeCharacter{007B}{\char"7B }%
+  \DeclareUnicodeCharacter{007C}{\char"7C }%
+  \DeclareUnicodeCharacter{007D}{\char"7D }%
+  \DeclareUnicodeCharacter{007E}{\char"7E }%
+  % \DeclareUnicodeCharacter{007F}{} % DEL
+  %
   \DeclareUnicodeCharacter{00A0}{\tie}%
   \DeclareUnicodeCharacter{00A1}{\exclamdown}%
   \DeclareUnicodeCharacter{00A2}{{\tcfont \char162}}% 0242=cent
@@ -10417,7 +10644,7 @@
   \DeclareUnicodeCharacter{00AE}{\registeredsymbol{}}%
   \DeclareUnicodeCharacter{00AF}{\={ }}%
   %
-  \DeclareUnicodeCharacter{00B0}{\ringaccent{ }}%
+  \DeclareUnicodeCharacter{00B0}{\textdegree}%
   \DeclareUnicodeCharacter{00B1}{\ensuremath\pm}%
   \DeclareUnicodeCharacter{00B2}{$^2$}%
   \DeclareUnicodeCharacter{00B3}{$^3$}%
@@ -10899,6 +11126,9 @@
   \DeclareUnicodeCharacter{1EF8}{\~Y}%
   \DeclareUnicodeCharacter{1EF9}{\~y}%
   %
+  % Exotic spaces
+  \DeclareUnicodeCharacter{2007}{\hphantom{0}}%
+  %
   % Punctuation
   \DeclareUnicodeCharacter{2013}{--}%
   \DeclareUnicodeCharacter{2014}{---}%
@@ -10918,7 +11148,7 @@
   %
   \DeclareUnicodeCharacter{20AC}{\euro{}}%
   %
-  \DeclareUnicodeCharacter{2192}{\expansion{}}%
+  \DeclareUnicodeCharacter{2192}{\arrow}%
   \DeclareUnicodeCharacter{21D2}{\result{}}%
   %
   % Mathematical symbols
@@ -11081,24 +11311,26 @@
 % provide a definition macro to replace/pass-through a Unicode character
 %
 \def\DeclareUnicodeCharacterNative#1#2{%
-  \catcode"#1=\active
-  \def\dodeclareunicodecharacternative##1##2##3{%
+  \ifnum"#1>"7F % only make non-ASCII chars active
+    \catcode"#1=\active
+    \def\dodeclareunicodecharacternative##1##2##3{%
+      \begingroup
+        \uccode`\~="##2\relax
+        \uppercase{\gdef~}{%
+          \ifpassthroughchars
+            ##1%
+          \else
+            ##3%
+          \fi
+        }
+      \endgroup
+    }
     \begingroup
-      \uccode`\~="##2\relax
-      \uppercase{\gdef~}{%
-        \ifpassthroughchars
-          ##1%
-        \else
-          ##3%
-        \fi
-      }
+      \uccode`\.="#1\relax
+      \uppercase{\def\UTFNativeTmp{.}}%
+      \expandafter\dodeclareunicodecharacternative\UTFNativeTmp{#1}{#2}%
     \endgroup
-  }
-  \begingroup
-    \uccode`\.="#1\relax
-    \uppercase{\def\UTFNativeTmp{.}}%
-    \expandafter\dodeclareunicodecharacternative\UTFNativeTmp{#1}{#2}%
-  \endgroup
+  \fi
 }
 
 % Native Unicode handling (XeTeX and LuaTeX) character replacing definition.
@@ -11127,14 +11359,14 @@
    \relax
 }
 
-% Define all Unicode characters we know about.  This makes UTF-8 the default
-% input encoding and allows @U to work.
+% Define all Unicode characters we know about
 \iftxinativeunicodecapable
   \nativeunicodechardefsatu
 \else
   \utfeightchardefs
 \fi
 
+
 \message{formatting,}
 
 \newdimen\defaultparindent \defaultparindent = 15pt
@@ -11181,13 +11413,9 @@
   %
   \vsize = #1\relax
   \advance\vsize by \topskip
-  \outervsize = \vsize
-  \advance\outervsize by 2\topandbottommargin
   \txipageheight = \vsize
   %
   \hsize = #2\relax
-  \outerhsize = \hsize
-  \advance\outerhsize by 0.5in
   \txipagewidth = \hsize
   %
   \normaloffset = #4\relax
@@ -11244,23 +11472,6 @@
   \defbodyindent = .5cm
 }}
 
-% Use @smallerbook to reset parameters for 6x9 trim size.
-% (Just testing, parameters still in flux.)
-\def\smallerbook{{\globaldefs = 1
-  \parskip = 1.5pt plus 1pt
-  \textleading = 12pt
-  %
-  \internalpagesizes{7.4in}{4.8in}%
-                    {-.2in}{-.4in}%
-                    {0pt}{14pt}%
-                    {9in}{6in}%
-  %
-  \lispnarrowing = 0.25in
-  \tolerance = 700
-  \contentsrightmargin = 0pt
-  \defbodyindent = .4cm
-}}
-
 % Use @afourpaper to print on European A4 paper.
 \def\afourpaper{{\globaldefs = 1
   \parskip = 3pt plus 2pt minus 1pt
@@ -11294,7 +11505,7 @@
   \textleading = 12.5pt
   %
   \internalpagesizes{160mm}{120mm}%
-                    {\voffset}{\hoffset}%
+                    {\voffset}{-11.4mm}%
                     {\bindingoffset}{8pt}%
                     {210mm}{148mm}%
   %
@@ -11373,9 +11584,138 @@
 \hfuzz = 1pt
 
 
+\message{microtype,}
+
+% protrusion, from Thanh's protcode.tex.
+\def\mtsetprotcode#1{%
+  \rpcode#1`\!=200  \rpcode#1`\,=700  \rpcode#1`\-=700  \rpcode#1`\.=700
+  \rpcode#1`\;=500  \rpcode#1`\:=500  \rpcode#1`\?=200
+  \rpcode#1`\'=700
+  \rpcode#1 34=500  % ''
+  \rpcode#1 123=300 % --
+  \rpcode#1 124=200 % ---
+  \rpcode#1`\)=50   \rpcode#1`\A=50   \rpcode#1`\F=50   \rpcode#1`\K=50
+  \rpcode#1`\L=50   \rpcode#1`\T=50   \rpcode#1`\V=50   \rpcode#1`\W=50
+  \rpcode#1`\X=50   \rpcode#1`\Y=50   \rpcode#1`\k=50   \rpcode#1`\r=50
+  \rpcode#1`\t=50   \rpcode#1`\v=50   \rpcode#1`\w=50   \rpcode#1`\x=50
+  \rpcode#1`\y=50
+  %
+  \lpcode#1`\`=700
+  \lpcode#1 92=500  % ``
+  \lpcode#1`\(=50   \lpcode#1`\A=50   \lpcode#1`\J=50   \lpcode#1`\T=50
+  \lpcode#1`\V=50   \lpcode#1`\W=50   \lpcode#1`\X=50   \lpcode#1`\Y=50
+  \lpcode#1`\v=50   \lpcode#1`\w=50   \lpcode#1`\x=50   \lpcode#1`\y=0
+  %
+  \mtadjustprotcode#1\relax
+}
+
+\newcount\countC
+\def\mtadjustprotcode#1{%
+  \countC=0
+  \loop
+    \ifcase\lpcode#1\countC\else
+      \mtadjustcp\lpcode#1\countC
+    \fi
+    \ifcase\rpcode#1\countC\else
+      \mtadjustcp\rpcode#1\countC
+    \fi
+    \advance\countC 1
+  \ifnum\countC < 256 \repeat
+}
+
+\newcount\countB
+\def\mtadjustcp#1#2#3{%
+  \setbox\boxA=\hbox{%
+    \ifx#2\font\else#2\fi
+    \char#3}%
+  \countB=\wd\boxA
+  \multiply\countB #1#2#3\relax
+  \divide\countB \fontdimen6 #2\relax
+  #1#2#3=\countB\relax
+}
+
+\ifx\XeTeXrevision\thisisundefined
+  \ifx\luatexversion\thisisundefined
+    \ifpdf % pdfTeX
+      \mtsetprotcode\textrm
+      \def\mtfontexpand#1{\pdffontexpand#1 20 20 1 autoexpand\relax}
+    \else % TeX
+      \def\mtfontexpand#1{}
+    \fi
+  \else % LuaTeX
+    \mtsetprotcode\textrm
+    \def\mtfontexpand#1{\expandglyphsinfont#1 20 20 1\relax}
+  \fi
+\else % XeTeX
+  \mtsetprotcode\textrm
+  \def\mtfontexpand#1{}
+\fi
+
+
+\newif\ifmicrotype
+
+\def\microtypeON{%
+  \microtypetrue
+  %
+  \ifx\XeTeXrevision\thisisundefined
+    \ifx\luatexversion\thisisundefined
+      \ifpdf % pdfTeX
+        \pdfadjustspacing=2
+        \pdfprotrudechars=2
+      \fi
+    \else % LuaTeX
+      \adjustspacing=2
+      \protrudechars=2
+    \fi
+  \else % XeTeX
+    \XeTeXprotrudechars=2
+  \fi
+  %
+  \mtfontexpand\textrm
+  \mtfontexpand\textsl
+  \mtfontexpand\textbf
+}
+
+\def\microtypeOFF{%
+  \microtypefalse
+  %
+  \ifx\XeTeXrevision\thisisundefined
+    \ifx\luatexversion\thisisundefined
+      \ifpdf % pdfTeX
+        \pdfadjustspacing=0
+        \pdfprotrudechars=0
+      \fi
+    \else % LuaTeX
+      \adjustspacing=0
+      \protrudechars=0
+    \fi
+  \else % XeTeX
+    \XeTeXprotrudechars=0
+  \fi
+}
+
+\microtypeOFF
+
+\parseargdef\microtype{%
+  \def\txiarg{#1}%
+  \ifx\txiarg\onword
+    \microtypeON
+  \else\ifx\txiarg\offword
+    \microtypeOFF
+  \else
+    \errhelp = \EMsimple
+    \errmessage{Unknown @microtype option `\txiarg', must be on|off}%
+  \fi\fi
+}
+
+
 \message{and turning on texinfo input format.}
 
+% Make UTF-8 the default encoding.
+\documentencodingzzz{UTF-8}
+
 \def^^L{\par} % remove \outer, so ^L can appear in an @comment
+\catcode`\^^K = 10 % treat vertical tab as whitespace
 
 % DEL is a comment character, in case @c does not suffice.
 \catcode`\^^? = 14
@@ -11391,23 +11731,6 @@
 \catcode`\|=\other \def\normalverticalbar{|}
 \catcode`\~=\other \def\normaltilde{~}
 
-% This macro is used to make a character print one way in \tt
-% (where it can probably be output as-is), and another way in other fonts,
-% where something hairier probably needs to be done.
-%
-% #1 is what to print if we are indeed using \tt; #2 is what to print
-% otherwise.  Since all the Computer Modern typewriter fonts have zero
-% interword stretch (and shrink), and it is reasonable to expect all
-% typewriter fonts to have this, we can check that font parameter.
-%
-\def\ifusingtt#1#2{\ifdim \fontdimen3\font=0pt #1\else #2\fi}
-
-% Same as above, but check for italic font.  Actually this also catches
-% non-italic slanted fonts since it is impossible to distinguish them from
-% italic fonts.  But since this is only used by $ and it uses \sl anyway
-% this is not a problem.
-\def\ifusingit#1#2{\ifdim \fontdimen1\font>0pt #1\else #2\fi}
-
 % Set catcodes for Texinfo file
 
 % Active characters for printing the wanted glyph.
@@ -11453,23 +11776,32 @@
 % Used sometimes to turn off (effectively) the active characters even after
 % parsing them.
 \def\turnoffactive{%
-  \normalturnoffactive
+  \passthroughcharstrue
+  \let-=\normaldash
+  \let"=\normaldoublequote
+  \let$=\normaldollar %$ font-lock fix
+  \let+=\normalplus
+  \let<=\normalless
+  \let>=\normalgreater
+  \let^=\normalcaret
+  \let_=\normalunderscore
+  \let|=\normalverticalbar
+  \let~=\normaltilde
   \otherbackslash
+  \setregularquotes
+  \unsepspaces
 }
 
-\catcode`\@=0
+% If a .fmt file is being used, characters that might appear in a file
+% name cannot be active until we have parsed the command line.
+% So turn them off again, and have \loadconf turn them back on.
+\catcode`+=\other \catcode`\_=\other
+
 
 % \backslashcurfont outputs one backslash character in current font,
 % as in \char`\\.
 \global\chardef\backslashcurfont=`\\
 
-% \realbackslash is an actual character `\' with catcode other.
-{\catcode`\\=\other @gdef@realbackslash{\}}
-
-% In Texinfo, backslash is an active character; it prints the backslash
-% in fixed width font.
-\catcode`\\=\active  % @ for escape char from now on.
-
 % Print a typewriter backslash.  For math mode, we can't simply use
 % \backslashcurfont: the story here is that in math mode, the \char
 % of \backslashcurfont ends up printing the roman \ from the math symbol
@@ -11479,109 +11811,125 @@
 % ignored family value; char position "5C).  We can't use " for the
 % usual hex value because it has already been made active.
 
-@def@ttbackslash{{@tt @ifmmode @mathchar29020 @else @backslashcurfont @fi}}
-@let@backslashchar = @ttbackslash % @backslashchar{} is for user documents.
-
-% \otherbackslash defines an active \ to be a literal `\' character with
-% catcode other.
-@gdef@otherbackslash{@let\=@realbackslash}
-
-% Same as @turnoffactive except outputs \ as {\tt\char`\\} instead of
-% the literal character `\'.
-%
-{@catcode`- = @active
- @gdef@normalturnoffactive{%
-   @passthroughcharstrue
-   @let-=@normaldash
-   @let"=@normaldoublequote
-   @let$=@normaldollar %$ font-lock fix
-   @let+=@normalplus
-   @let<=@normalless
-   @let>=@normalgreater
-   @let^=@normalcaret
-   @let_=@normalunderscore
-   @let|=@normalverticalbar
-   @let~=@normaltilde
-   @let\=@ttbackslash
-   @setregularquotes
-   @unsepspaces
- }
-}
-
-% If a .fmt file is being used, characters that might appear in a file
-% name cannot be active until we have parsed the command line.
-% So turn them off again, and have @fixbackslash turn them back on.
-@catcode`+=@other @catcode`@_=@other
+\def\ttbackslash{{\tt \ifmmode \mathchar29020 \else \backslashcurfont \fi}}
+\let\backslashchar = \ttbackslash % \backslashchar{} is for user documents.
 
-% \enablebackslashhack - allow file to begin `\input texinfo'
-%
-% If a .fmt file is being used, we don't want the `\input texinfo' to show up.
-% That is what \eatinput is for; after that, the `\' should revert to printing
-% a backslash.
-% If the file did not have a `\input texinfo', then it is turned off after
-% the first line; otherwise the first `\' in the file would cause an error.
-% This is used on the very last line of this file, texinfo.tex.
-% We also use @c to call @fixbackslash, in case ends of lines are hidden.
-{
-@catcode`@^=7
-@catcode`@^^M=13@gdef@enablebackslashhack{%
-  @global@let\ = @eatinput%
-  @catcode`@^^M=13%
-  @def@c{@fixbackslash@c}%
-  % Definition for the newline at the end of this file.
-  @def ^^M{@let^^M@secondlinenl}%
-  % Definition for a newline in the main Texinfo file.
-  @gdef @secondlinenl{@fixbackslash}%
-  % In case the first line has a whole-line command on it
-  @let@originalparsearg@parsearg
-  @def@parsearg{@fixbackslash@originalparsearg}
+% These are made active for url-breaking, so need
+% active definitions as the normal characters.
+\def\normaldot{.}
+\def\normalquest{?}
+\def\normalslash{/}
+
+% \newlinesloadsconf - call \loadconf as soon as possible in the
+% file, e.g. at the first newline.
+%
+{\catcode`\^=7
+\catcode`\^^M=13
+\gdef\newlineloadsconf{%
+  \catcode`\^^M=13 %
+  \newlineloadsconfzz%
+}
+\gdef\newlineloadsconfzz#1^^M{%
+  \def\c{\loadconf\c}%
+  % Definition for the first newline read in the file
+  \def ^^M{\loadconf}%
+  % In case the first line has a whole-line or environment command on it
+  \let\originalparsearg\parsearg%
+  \def\parsearg{\loadconf\originalparsearg}%
+  %
+  % \startenvironment is in the expansion of commands defined with \envdef
+  \let\originalstartenvironment\startenvironment%
+  \def\startenvironment{\loadconf\startenvironment}%
 }}
 
-{@catcode`@^=7 @catcode`@^^M=13%
-@gdef@eatinput input texinfo#1^^M{@fixbackslash}}
 
 % Emergency active definition of newline, in case an active newline token
 % appears by mistake.
-{@catcode`@^=7 @catcode13=13%
-@gdef@enableemergencynewline{%
-  @gdef^^M{%
-    @par%
-    %<warning: active newline>@par%
+{\catcode`\^=7 \catcode13=13%
+\gdef\enableemergencynewline{%
+  \gdef^^M{%
+    \par%
+    %<warning: active newline>\par%
 }}}
 
 
-@gdef@fixbackslash{%
-  @ifx\@eatinput @let\ = @ttbackslash @fi
-  @catcode13=5 % regular end of line
-  @enableemergencynewline
-  @let@c=@comment
-  @let@parsearg@originalparsearg
+% \loadconf gets called at the beginning of every Texinfo file.
+% If texinfo.cnf is present on the system, read it.  Useful for site-wide
+% @afourpaper, etc.  Not opening texinfo.cnf directly in texinfo.tex
+% makes it possible to make a format file for Texinfo.
+%
+\gdef\loadconf{%
+  \relax  % Terminate the filename if running as "tex '&texinfo' FILE.texi".
+  %
+  % Turn off the definitions that trigger \loadconf
+  \everyjobreset
+  \catcode13=5 % regular end of line
+  \enableemergencynewline
+  \let\c=\comment
+  \let\parsearg\originalparsearg
+  \let\startenvironment\originalstartenvironment
+  %
   % Also turn back on active characters that might appear in the input
   % file name, in case not using a pre-dumped format.
-  @catcode`+=@active
-  @catcode`@_=@active
+  \catcode`+=\active
+  \catcode`\_=\active
   %
-  % If texinfo.cnf is present on the system, read it.
-  % Useful for site-wide @afourpaper, etc.  This macro, @fixbackslash, gets
-  % called at the beginning of every Texinfo file.  Not opening texinfo.cnf
-  % directly in this file, texinfo.tex, makes it possible to make a format
-  % file for Texinfo.
-  %
-  @openin 1 texinfo.cnf
-  @ifeof 1 @else @input texinfo.cnf @fi
-  @closein 1
+  \openin 1 texinfo.cnf
+  \ifeof 1 \else \input texinfo.cnf \fi
+  \closein 1
 }
 
+% Redefine some control sequences to be controlled by the \ifdummies
+% and \ifindexnofonts switches.  Do this at the end so that the control
+% sequences are all defined.
+\definedummies
+
+
+
+
+\catcode`\@=0
+
+% \realbackslash is an actual character `\' with catcode other.
+{\catcode`\\=\other @gdef@realbackslash{\}}
+
+% In Texinfo, backslash is an active character; it prints the backslash
+% in fixed width font.
+\catcode`\\=\active  % @ for escape char from now on.
+
+@let\ = @ttbackslash
+
+% If in a .fmt file, print the version number.
+% \eatinput stops the `\input texinfo' from showing up.
+% After that, `\' should revert to printing a backslash.
+% Turn on active characters that we couldn't do earlier because
+% they might have appeared in the input file name.
+%
+@everyjob{@message{Texinfo version @texinfoversion}%
+  @global@let\ = @eatinput
+  @catcode`+=@active @catcode`@_=@active}
+
+{@catcode`@^=7 @catcode`@^^M=13%
+@gdef@eatinput input texinfo#1^^M{@loadconf}}
+
+@def@everyjobreset{@ifx\@eatinput @let\ = @ttbackslash @fi}
+
+% \otherbackslash defines an active \ to be a literal `\' character with
+% catcode other.
+@gdef@otherbackslash{@let\=@realbackslash}
+
+% Same as @turnoffactive except outputs \ as {\tt\char`\\} instead of
+% the literal character `\'.
+%
+{@catcode`- = @active
+ @gdef@normalturnoffactive{%
+   @turnoffactive
+   @let\=@ttbackslash
+ }
+}
 
 % Say @foo, not \foo, in error messages.
 @escapechar = `@@
 
-% These (along with & and #) are made active for url-breaking, so need
-% active definitions as the normal characters.
-@def@normaldot{.}
-@def@normalquest{?}
-@def@normalslash{/}
-
 % These look ok in all fonts, so just make them not special.
 % @hashchar{} gets its own user-level command, because of #line.
 @catcode`@& = @other @def@normalamp{&}
@@ -11596,17 +11944,11 @@
 @c Do this last of all since we use ` in the previous @catcode assignments.
 @catcode`@'=@active
 @catcode`@`=@active
-@setregularquotes
 
 @c Local variables:
-@c eval: (add-hook 'before-save-hook 'time-stamp)
-@c page-delimiter: "^\\\\message\\|emacs-page"
-@c time-stamp-start: "def\\\\texinfoversion{"
-@c time-stamp-format: "%:y-%02m-%02d.%02H"
-@c time-stamp-end: "}"
+@c eval: (add-hook 'before-save-hook 'time-stamp nil t)
+@c time-stamp-pattern: "texinfoversion{%Y-%02m-%02d.%02H}"
+@c page-delimiter: "^\\\\message"
 @c End:
 
-@c vim:sw=2:
-
-@enablebackslashhack
-
+@newlineloadsconf

_service:tar_scm:automake-1.16.5.tar.xz/lib/update-copyright -> _service:tar_scm:automake-1.17.tar.xz/lib/update-copyright Changed

@@ -3,11 +3,11 @@
 
 # Update an FSF copyright year list to include the current year.
 
-# Copyright (C) 2009-2021 Free Software Foundation, Inc.
+# Copyright (C) 2009-2024 Free Software Foundation, Inc.
 #
 # This program is free software: you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 3, or (at your option)
+# the Free Software Foundation, either version 3, or (at your option)
 # any later version.
 #
 # This program is distributed in the hope that it will be useful,
@@ -98,7 +98,8 @@
 #   6. Blank lines, even if preceded by the prefix, do not appear
 #      within the FSF copyright statement.
 #   7. Each copyright year is 2 or 4 digits, and years are separated by
-#      commas, "-", or "--".  Whitespace may appear after commas.
+#      commas, "-", "--", or "\(en" (for troff).  Whitespace may appear
+#      after commas.
 #
 # Environment variables:
 #
@@ -122,7 +123,7 @@
 #   5. Set UPDATE_COPYRIGHT_HOLDER if the copyright holder is other
 #      than "Free Software Foundation, Inc.".
 
-# This is a prologue that allows to run a perl script as an executable
+# This is a prologue that allows running a perl script as an executable
 # on systems that are compliant to a POSIX version before POSIX:2017.
 # On such systems, the usual invocation of an executable through execlp()
 # or execvp() fails with ENOEXEC if it is a script that does not start
@@ -137,7 +138,7 @@
 eval 'exec perl -wSx -0777 -pi "$0" "$@"'
      if 0;
 
-my $VERSION = '2020-04-04.15:07'; # UTC
+my $VERSION = '2024-07-04.10:56'; # UTC
 # The definition above must lie within the first 8 lines in order
 # for the Emacs time-stamp write hook (at end) to update it.
 # If you change this file with Emacs, please let the write hook
@@ -145,9 +146,11 @@
 
 use strict;
 use warnings;
+use re 'eval';
 
 my $copyright_re = 'Copyright';
 my $circle_c_re = '(?:$cC$|@copyright\{}|\\\\\(co|&copy;|©)';
+my $ndash_re = '(?:--?|\\\\\(en)';
 my $holder = $ENV{UPDATE_COPYRIGHT_HOLDER};
 $holder ||= 'Free Software Foundation, Inc.';
 my $prefix_max = 5;
@@ -167,14 +170,13 @@
 # Unless the file consistently uses "\r\n" as the EOL, use "\n" instead.
 my $eol = /(?:^|^\r)\n/ ? "\n" : "\r\n";
 
-my $leading;
-my $prefix;
-my $ws_re;
 my $stmt_re;
-while (/(^|\n)(.{0,$prefix_max})$copyright_re/g)
+my $found;
+while (/(^|\n)(.{0,$prefix_max})$copyright_re/cg)
   {
-    $leading = "$1$2";
-    $prefix = $2;
+    my $pos=pos();
+    my $leading = "$1$2";
+    my $prefix = $2;
     if ($prefix =~ /^(\s*\/)\*(\s*)$/)
       {
         $prefix =~ s,/, ,;
@@ -185,105 +187,108 @@
             $prefix = $prefix_ws;
           }
       }
-    $ws_re = ' \t\r\f'; # \s without \n
+    my $ws_re = ' \t\r\f'; # \s without \n
     $ws_re =
       "(?:$ws_re*(?:$ws_re|\\n" . quotemeta($prefix) . ")$ws_re*)";
     my $holder_re = $holder;
     $holder_re =~ s/\s/$ws_re/g;
     my $stmt_remainder_re =
       "(?:$ws_re$circle_c_re)?"
-      . "$ws_re(?:(?:\\d\\d)?\\d\\d(?:,$ws_re?|--?))*"
+      . "$ws_re(?:(?:\\d\\d)?\\d\\d(?:,$ws_re?|$ndash_re))*"
       . "((?:\\d\\d)?\\d\\d)$ws_re$holder_re";
     if (/\G$stmt_remainder_re/)
       {
+        $found = 1;
         $stmt_re =
           quotemeta($leading) . "($copyright_re$stmt_remainder_re)";
-        last;
-      }
-  }
-if (defined $stmt_re)
-  {
-    /$stmt_re/ or die; # Should never die.
-    my $stmt = $1;
-    my $final_year_orig = $2;
 
-    # Handle two-digit year numbers like "98" and "99".
-    my $final_year = $final_year_orig;
-    $final_year <= 99
-      and $final_year += 1900;
+        /$stmt_re/ or die; # Should never die.
+        my $stmt = $1;
+        my $final_year_orig = $2;
 
-    if ($final_year != $this_year)
-      {
-        # Update the year.
-        $stmt =~ s/\b$final_year_orig\b/$final_year, $this_year/;
-      }
-    if ($final_year != $this_year || $ENV{'UPDATE_COPYRIGHT_FORCE'})
-      {
-        # Normalize all whitespace including newline-prefix sequences.
-        $stmt =~ s/$ws_re/ /g;
+        # Handle two-digit year numbers like "98" and "99".
+        my $final_year = $final_year_orig;
+        $final_year <= 99
+          and $final_year += 1900;
 
-        # Put spaces after commas.
-        $stmt =~ s/, ?/, /g;
-
-        # Convert 2-digit to 4-digit years.
-        $stmt =~ s/(\b\d\d\b)/19$1/g;
-
-        # Make the use of intervals consistent.
-        if (!$ENV{UPDATE_COPYRIGHT_USE_INTERVALS})
+        if ($final_year != $this_year)
           {
-            $stmt =~ s/(\d{4})--?(\d{4})/join(', ', $1..$2)/eg;
+            # Update the year.
+            $stmt =~ s/(^|^\d)$final_year_orig\b/$1$final_year, $this_year/;
           }
-        else
+        if ($final_year != $this_year || $ENV{'UPDATE_COPYRIGHT_FORCE'})
           {
-            my $ndash = $ARGV =~ /\.tex(i(nfo)?)?$/ ? "--" : "-";
+            # Normalize all whitespace including newline-prefix sequences.
+            $stmt =~ s/$ws_re/ /g;
 
-            $stmt =~
-              s/
-                (\d{4})
-                (?:
-                  (,\ |--?)
-                  ((??{
-                    if   ($2 ne ', ') { '\d{4}'; }
-                    elsif (!$3)       { $1 + 1;  }
-                    else              { $3 + 1;  }
-                  }))
-                )+
-              /$1$ndash$3/gx;
+            # Put spaces after commas.
+            $stmt =~ s/, ?/, /g;
 
-            # When it's 2, emit a single range encompassing all year numbers.
-            $ENV{UPDATE_COPYRIGHT_USE_INTERVALS} == 2
-              and $stmt =~ s/\b(\d{4})\b.*\b(\d{4})\b/$1$ndash$2/;
-          }
+            # Convert 2-digit to 4-digit years.
+            $stmt =~ s/(\b\d\d\b)/19$1/g;
 
-        # Format within margin.
-        my $stmt_wrapped;
-        my $text_margin = $margin - length($prefix);
-        if ($prefix =~ /^(\t+)/)
-          {
-            $text_margin -= length($1) * ($tab_width - 1);
-          }
-        while (length $stmt)
-          {
-            if (($stmt =~ s/^(.{1,$text_margin})(?: |$)//)
-                || ($stmt =~ s/^(\S+)(?: |$)//))
+            # Make the use of intervals consistent.
+            if (!$ENV{UPDATE_COPYRIGHT_USE_INTERVALS})
               {
-                my $line = $1;
-                $stmt_wrapped .= $stmt_wrapped ? "$eol$prefix" : $leading;
-                $stmt_wrapped .= $line;
+                $stmt =~ s/(\d{4})$ndash_re(\d{4})/join(', ', $1..$2)/eg;
               }
             else
               {
-                # Should be unreachable, but we don't want an infinite
-                # loop if it can be reached.
-                die;
+                my $ndash = ($ARGV =~ /\.tex(i(nfo)?)?$/ ? "--"
+                             : $ARGV =~ /\.(\da-z*|man)$/ ? "\\(en"
+                             : "-");
+
+                $stmt =~
+                  s/
+                    (\d{4})
+                    (?:
+                      (,\ |$ndash_re)
+                      ((??{
+                        if   ($2 ne ', ') { '\d{4}'; }
+                        elsif (!$3)       { $1 + 1;  }
+                        else              { $3 + 1;  }
+                      }))
+                    )+
+                  /$1$ndash$3/gx;
+
+                # When it's 2, emit a single range encompassing all year numbers.
+                $ENV{UPDATE_COPYRIGHT_USE_INTERVALS} == 2
+                  and $stmt =~ s/(^|^\d)(\d{4})\b.*(?:^\d)(\d{4})\b/$1$2$ndash$3/;
               }
-          }
 
-        # Replace the old copyright statement.
-        s/$stmt_re/$stmt_wrapped/;
+            # Format within margin.
+            my $stmt_wrapped;
+            my $text_margin = $margin - length($prefix);
+            if ($prefix =~ /^(\t+)/)
+              {
+                $text_margin -= length($1) * ($tab_width - 1);
+              }
+            while (length $stmt)
+              {
+                if (($stmt =~ s/^(.{1,$text_margin})(?: |$)//)
+                    || ($stmt =~ s/^(\S+)(?: |$)//))
+                  {
+                    my $line = $1;
+                    $stmt_wrapped .= $stmt_wrapped ? "$eol$prefix" : $leading;
+                    $stmt_wrapped .= $line;
+                  }
+                else
+                  {
+                    # Should be unreachable, but we don't want an infinite
+                    # loop if it can be reached.
+                    die;
+                  }
+              }
+
+            # Replace the old copyright statement.
+            my $p = pos();
+            s/$stmt_re/$stmt_wrapped/g;
+            pos() = $p;
+          }
       }
   }
-else
+
+if (!$found)
   {
     print STDERR "$ARGV: warning: copyright statement not found\n";
   }
@@ -293,7 +298,7 @@
 # coding: utf-8
 # mode: perl
 # indent-tabs-mode: nil
-# eval: (add-hook 'before-save-hook 'time-stamp)
+# eval: (add-hook 'before-save-hook 'time-stamp nil t)
 # time-stamp-line-limit: 200
 # time-stamp-start: "my $VERSION = '"
 # time-stamp-format: "%:y-%02m-%02d.%02H:%02M"

_service:tar_scm:automake-1.16.5.tar.xz/lib/ylwrap -> _service:tar_scm:automake-1.17.tar.xz/lib/ylwrap Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/amversion.in -> _service:tar_scm:automake-1.17.tar.xz/m4/amversion.in Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/amversion.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/amversion.m4 Changed

@@ -1,6 +1,6 @@
 ##                                                          -*- Autoconf -*-
 ## Generated from amversion.in; do not edit by hand.
-# Copyright (C) 2002-2021 Free Software Foundation, Inc.
+# Copyright (C) 2002-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -12,10 +12,10 @@
 # generated from the m4 files accompanying Automake X.Y.
 # (This private macro should not be called outside this file.)
 AC_DEFUN(AM_AUTOMAKE_VERSION,
-am__api_version='1.16'
+am__api_version='1.17'
 dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to
 dnl require some minimum version.  Point them to the right macro.
-m4_if($1, 1.16.5, ,
+m4_if($1, 1.17, ,
       AC_FATAL(Do not call $0, use AM_INIT_AUTOMAKE($1).))dnl
 )
 
@@ -31,7 +31,7 @@
 # Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced.
 # This function is AC_REQUIREd by AM_INIT_AUTOMAKE.
 AC_DEFUN(AM_SET_CURRENT_AUTOMAKE_VERSION,
-AM_AUTOMAKE_VERSION(1.16.5)dnl
+AM_AUTOMAKE_VERSION(1.17)dnl
 m4_ifndef(AC_AUTOCONF_VERSION,
   m4_copy(m4_PACKAGE_VERSION, AC_AUTOCONF_VERSION))dnl
 _AM_AUTOCONF_VERSION(m4_defn(AC_AUTOCONF_VERSION)))

_service:tar_scm:automake-1.16.5.tar.xz/m4/ar-lib.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/ar-lib.m4 Changed

@@ -1,5 +1,5 @@
 ##                                                          -*- Autoconf -*-
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -13,16 +13,18 @@
 AC_DEFUN(AM_PROG_AR,
 AC_BEFORE($0, LT_INIT)dnl
 AC_BEFORE($0, AC_PROG_LIBTOOL)dnl
+AC_BEFORE($0, AC_PROG_AR)dnl
 AC_REQUIRE(AM_AUX_DIR_EXPAND)dnl
 AC_REQUIRE_AUX_FILE(ar-lib)dnl
 AC_CHECK_TOOLS(AR, ar lib "link -lib", false)
 : ${AR=ar}
+: ${ARFLAGS=cr}
 
 AC_CACHE_CHECK(the archiver ($AR) interface, am_cv_ar_interface,
   AC_LANG_PUSH(C)
    am_cv_ar_interface=ar
    AC_COMPILE_IFELSE(AC_LANG_SOURCE(int some_variable = 0;),
-     am_ar_try='$AR cru libconftest.a conftest.$ac_objext >&AS_MESSAGE_LOG_FD'
+     am_ar_try='$AR $ARFLAGS libconftest.a conftest.$ac_objext >&AS_MESSAGE_LOG_FD'
       AC_TRY_EVAL(am_ar_try)
       if test "$ac_status" -eq 0; then
         am_cv_ar_interface=ar

_service:tar_scm:automake-1.16.5.tar.xz/m4/as.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/as.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/auxdir.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/auxdir.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/cond-if.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/cond-if.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/cond.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/cond.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/depend.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/depend.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/depout.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/depout.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/dmalloc.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/dmalloc.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/extra-recurs.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/extra-recurs.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/gcj.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/gcj.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/init.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/init.m4 Changed

@@ -1,6 +1,6 @@
 # Do all the work for Automake.                             -*- Autoconf -*-
 
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -134,7 +134,7 @@
 fi
 AC_SUBST(CSCOPE)
 
-AC_REQUIRE(AM_SILENT_RULES)dnl
+AC_REQUIRE(_AM_SILENT_RULES)dnl
 dnl The testsuite driver may need to know about EXEEXT, so add the
 dnl 'am__EXEEXT' conditional if _AM_COMPILER_EXEEXT was seen.  This
 dnl macro is hooked onto _AC_COMPILER_EXEEXT early, see below.
@@ -142,47 +142,9 @@
 m4_provide_if(_AM_COMPILER_EXEEXT,
   AM_CONDITIONAL(am__EXEEXT, test -n "$EXEEXT")))dnl
 
-# POSIX will say in a future version that running "rm -f" with no argument
-# is OK; and we want to be able to make that assumption in our Makefile
-# recipes.  So use an aggressive probe to check that the usage we want is
-# actually supported "in the wild" to an acceptable degree.
-# See automake bug#10828.
-# To make any issue more visible, cause the running configure to be aborted
-# by default if the 'rm' program in use doesn't match our expectations; the
-# user can still override this though.
-if rm -f && rm -fr && rm -rf; then : OK; else
-  cat >&2 <<'END'
-Oops!
+AC_REQUIRE(_AM_PROG_RM_F)
+AC_REQUIRE(_AM_PROG_XARGS_N)
 
-Your 'rm' program seems unable to run without file operands specified
-on the command line, even when the '-f' option is present.  This is contrary
-to the behaviour of most rm programs out there, and not conforming with
-the upcoming POSIX standard: <http://austingroupbugs.net/view.php?id=542>
-
-Please tell bug-automake@gnu.org about your system, including the value
-of your $PATH and any error possibly output before this message.  This
-can help us improve future automake versions.
-
-END
-  if test x"$ACCEPT_INFERIOR_RM_PROGRAM" = x"yes"; then
-    echo 'Configuration will proceed anyway, since you have set the' >&2
-    echo 'ACCEPT_INFERIOR_RM_PROGRAM variable to "yes"' >&2
-    echo >&2
-  else
-    cat >&2 <<'END'
-Aborting the configuration process, to ensure you take notice of the issue.
-
-You can download and install GNU coreutils to get an 'rm' implementation
-that behaves properly: <https://www.gnu.org/software/coreutils/>.
-
-If you want to complete the configuration process using your problematic
-'rm' anyway, export the environment variable ACCEPT_INFERIOR_RM_PROGRAM
-to "yes", and re-run configure.
-
-END
-    AC_MSG_ERROR(Your 'rm' program is bad, sorry.)
-  fi
-fi
 dnl The trailing newline in this macro's definition is deliberate, for
 dnl backward compatibility and to allow trailing 'dnl'-style comments
 dnl after the AM_INIT_AUTOMAKE invocation. See automake bug#16841.

_service:tar_scm:automake-1.16.5.tar.xz/m4/install-sh.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/install-sh.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/internal/ac-config-macro-dirs.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/internal/ac-config-macro-dirs.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/lead-dot.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/lead-dot.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/lex.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/lex.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/lispdir.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/lispdir.m4 Changed

@@ -3,7 +3,7 @@
 ## From Ulrich Drepper
 ## Almost entirely rewritten by Alexandre Oliva
 ## ------------------------
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -34,7 +34,7 @@
   #  which is non-obvious for non-emacs users.
   # Redirecting /dev/null should help a bit; pity we can't detect "broken"
   #  emacsen earlier and avoid running this altogether.
-  AC_RUN_LOG($EMACS -batch -Q -eval '(while load-path (princ (concat (car load-path) "\n")) (setq load-path (cdr load-path)))' </dev/null >conftest.out)
+  AC_RUN_LOG($EMACS -batch -no-site-file -eval '(while load-path (princ (concat (car load-path) "\n")) (setq load-path (cdr load-path)))' </dev/null >conftest.out)
 	am_cv_lispdir=`sed -n \
        -e 's,/$,,' \
        -e '/.*\/lib\/x*emacs\/site-lisp$/{s,.*/lib/$x*emacs/site-lisp$$,${libdir}/\1,;p;q;}' \

_service:tar_scm:automake-1.16.5.tar.xz/m4/local.mk -> _service:tar_scm:automake-1.17.tar.xz/m4/local.mk Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/maintainer.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/maintainer.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/make.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/make.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/missing.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/missing.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/mkdirp.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/mkdirp.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/obsolete.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/obsolete.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/options.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/options.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/prog-cc-c-o.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/prog-cc-c-o.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/python.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/python.m4 Changed

@@ -3,7 +3,7 @@
 ## From Andrew Dalke
 ## Updated by James Henstridge and other contributors.
 ## ------------------------
-# Copyright (C) 1999-2021 Free Software Foundation, Inc.
+# Copyright (C) 1999-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -37,9 +37,12 @@
   dnl Find a Python interpreter.  Python versions prior to 2.0 are not
   dnl supported. (2.0 was released on October 16, 2000).
   m4_define_default(_AM_PYTHON_INTERPRETER_LIST,
-python python2 python3 dnl
+python python3 dnl
+ python3.20 python3.19 python3.18 python3.17 python3.16 dnl
+ python3.15 python3.14 python3.13 python3.12 python3.11 python3.10 dnl
  python3.9 python3.8 python3.7 python3.6 python3.5 python3.4 python3.3 dnl
  python3.2 python3.1 python3.0 dnl
+ python2 dnl
  python2.7 python2.6 python2.5 python2.4 python2.3 python2.2 python2.1 dnl
  python2.0)
 
@@ -234,15 +237,29 @@
     if python_implementation() == 'CPython' and sys.version:3 == '2.7':
         can_use_sysconfig = 0
 except ImportError:
-    pass"
+    pass" # end of am_python_setup_sysconfig
+
+  # More repeated code, for figuring out the installation scheme to use.
+  am_python_setup_scheme="if hasattr(sysconfig, 'get_default_scheme'):
+      scheme = sysconfig.get_default_scheme()
+    else:
+      scheme = sysconfig._get_default_scheme()
+    if scheme == 'posix_local':
+      if '$am_py_prefix' == '/usr':
+        scheme = 'deb_system' # should only happen during Debian package builds
+      else:
+        # Debian's default scheme installs to /usr/local/ but we want to
+        # follow the prefix, as we always have.
+        # See bugs#54412, #64837, et al.
+        scheme = 'posix_prefix'" # end of am_python_setup_scheme
 
   dnl emacs-page Set up 4 directories:
 
   dnl 1. pythondir: where to install python scripts.  This is the
   dnl    site-packages directory, not the python standard library
-  dnl    directory like in previous automake betas.  This behavior
+  dnl    directory as in early automake betas.  This behavior
   dnl    is more consistent with lispdir.m4 for example.
-  dnl Query distutils for this directory.
+  dnl Query sysconfig or distutils (per above) for this directory.
   dnl
   AC_CACHE_CHECK(for $am_display_PYTHON script directory (pythondir),
   am_cv_python_pythondir,
@@ -254,7 +271,11 @@
    am_cv_python_pythondir=`$PYTHON -c "
 $am_python_setup_sysconfig
 if can_use_sysconfig:
-  sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
+  try:
+    $am_python_setup_scheme
+    sitedir = sysconfig.get_path('purelib', scheme, vars={'base':'$am_py_prefix'})
+  except:
+    sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
 else:
   from distutils import sysconfig
   sitedir = sysconfig.get_python_lib(0, 0, prefix='$am_py_prefix')
@@ -284,7 +305,8 @@
 
   dnl 3. pyexecdir: directory for installing python extension modules
   dnl    (shared libraries).
-  dnl Query distutils for this directory.
+  dnl Query sysconfig or distutils for this directory.
+  dnl Much of this is the same as for prefix setup above.
   dnl
   AC_CACHE_CHECK(for $am_display_PYTHON extension module directory (pyexecdir),
   am_cv_python_pyexecdir,
@@ -296,7 +318,11 @@
    am_cv_python_pyexecdir=`$PYTHON -c "
 $am_python_setup_sysconfig
 if can_use_sysconfig:
-  sitedir = sysconfig.get_path('platlib', vars={'platbase':'$am_py_exec_prefix'})
+  try:
+    $am_python_setup_scheme
+    sitedir = sysconfig.get_path('platlib', scheme, vars={'platbase':'$am_py_exec_prefix'})
+  except:
+    sitedir = sysconfig.get_path('platlib', vars={'platbase':'$am_py_exec_prefix'})
 else:
   from distutils import sysconfig
   sitedir = sysconfig.get_python_lib(1, 0, prefix='$am_py_exec_prefix')

_service:tar_scm:automake-1.17.tar.xz/m4/rmf.m4 Added

_service:tar_scm:automake-1.16.5.tar.xz/m4/runlog.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/runlog.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/sanity.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/sanity.m4 Changed

@@ -1,15 +1,168 @@
 # Check to make sure that the build environment is sane.    -*- Autoconf -*-
 
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
 # with or without modifications, as long as this notice is preserved.
 
+# _AM_SLEEP_FRACTIONAL_SECONDS
+# ----------------------------
+AC_DEFUN(_AM_SLEEP_FRACTIONAL_SECONDS, dnl
+AC_CACHE_CHECK(whether sleep supports fractional seconds,
+               am_cv_sleep_fractional_seconds, dnl
+AS_IF(sleep 0.001 2>/dev/null, am_cv_sleep_fractional_seconds=yes,
+                                 am_cv_sleep_fractional_seconds=no)
+))
+
+# _AM_FILESYSTEM_TIMESTAMP_RESOLUTION
+# -----------------------------------
+# Determine the filesystem's resolution for file modification
+# timestamps.  The coarsest we know of is FAT, with a resolution
+# of only two seconds, even with the most recent "exFAT" extensions.
+# The finest (e.g. ext4 with large inodes, XFS, ZFS) is one
+# nanosecond, matching clock_gettime.  However, it is probably not
+# possible to delay execution of a shell script for less than one
+# millisecond, due to process creation overhead and scheduling
+# granularity, so we don't check for anything finer than that. (See below.)
+AC_DEFUN(_AM_FILESYSTEM_TIMESTAMP_RESOLUTION, dnl
+AC_REQUIRE(_AM_SLEEP_FRACTIONAL_SECONDS)
+AC_CACHE_CHECK(filesystem timestamp resolution,
+               am_cv_filesystem_timestamp_resolution, dnl
+# Default to the worst case.
+am_cv_filesystem_timestamp_resolution=2
+
+# Only try to go finer than 1 sec if sleep can do it.
+# Don't try 1 sec, because if 0.01 sec and 0.1 sec don't work,
+# - 1 sec is not much of a win compared to 2 sec, and
+# - it takes 2 seconds to perform the test whether 1 sec works.
+# 
+# Instead, just use the default 2s on platforms that have 1s resolution,
+# accept the extra 1s delay when using $sleep in the Automake tests, in
+# exchange for not incurring the 2s delay for running the test for all
+# packages.
+#
+am_try_resolutions=
+if test "$am_cv_sleep_fractional_seconds" = yes; then
+  # Even a millisecond often causes a bunch of false positives,
+  # so just try a hundredth of a second. The time saved between .001 and
+  # .01 is not terribly consequential.
+  am_try_resolutions="0.01 0.1 $am_try_resolutions"
+fi
+
+# In order to catch current-generation FAT out, we must *modify* files
+# that already exist; the *creation* timestamp is finer.  Use names
+# that make ls -t sort them differently when they have equal
+# timestamps than when they have distinct timestamps, keeping
+# in mind that ls -t prints the *newest* file first.
+rm -f conftest.ts?
+: > conftest.ts1
+: > conftest.ts2
+: > conftest.ts3
+
+# Make sure ls -t actually works.  Do 'set' in a subshell so we don't
+# clobber the current shell's arguments. (Outer-level square brackets
+# are removed by m4; they're present so that m4 does not expand
+# <dollar><star>; be careful, easy to get confused.)
+if (
+     set X `ls -t conftest.ts12` &&
+     {
+       test "$*" != "X conftest.ts1 conftest.ts2" ||
+       test "$*" != "X conftest.ts2 conftest.ts1";
+     }
+); then :; else
+  # If neither matched, then we have a broken ls.  This can happen
+  # if, for instance, CONFIG_SHELL is bash and it inherits a
+  # broken ls alias from the environment.  This has actually
+  # happened.  Such a system could not be considered "sane".
+  _AS_ECHO_UNQUOTED(
+    "Bad output from ls -t: \"`ls -t conftest.ts12`\"",
+    AS_MESSAGE_LOG_FD)
+  AC_MSG_FAILURE(ls -t produces unexpected output.
+Make sure there is not a broken ls alias in your environment.)
+fi
+
+for am_try_res in $am_try_resolutions; do
+  # Any one fine-grained sleep might happen to cross the boundary
+  # between two values of a coarser actual resolution, but if we do
+  # two fine-grained sleeps in a row, at least one of them will fall
+  # entirely within a coarse interval.
+  echo alpha > conftest.ts1
+  sleep $am_try_res
+  echo beta > conftest.ts2
+  sleep $am_try_res
+  echo gamma > conftest.ts3
+
+  # We assume that 'ls -t' will make use of high-resolution
+  # timestamps if the operating system supports them at all.
+  if (set X `ls -t conftest.ts?` &&
+      test "$2" = conftest.ts3 &&
+      test "$3" = conftest.ts2 &&
+      test "$4" = conftest.ts1); then
+    #
+    # Ok, ls -t worked. If we're at a resolution of 1 second, we're done,
+    # because we don't need to test make.
+    make_ok=true
+    if test $am_try_res != 1; then
+      # But if we've succeeded so far with a subsecond resolution, we
+      # have one more thing to check: make. It can happen that
+      # everything else supports the subsecond mtimes, but make doesn't;
+      # notably on macOS, which ships make 3.81 from 2006 (the last one
+      # released under GPLv2). https://bugs.gnu.org/68808
+      # 
+      # We test $MAKE if it is defined in the environment, else "make".
+      # It might get overridden later, but our hope is that in practice
+      # it does not matter: it is the system "make" which is (by far)
+      # the most likely to be broken, whereas if the user overrides it,
+      # probably they did so with a better, or at least not worse, make.
+      # https://lists.gnu.org/archive/html/automake/2024-06/msg00051.html
+      #
+      # Create a Makefile (real tab character here):
+      rm -f conftest.mk
+      echo 'conftest.ts1: conftest.ts2' >conftest.mk
+      echo '	touch conftest.ts2' >>conftest.mk
+      #
+      # Now, running
+      #   touch conftest.ts1; touch conftest.ts2; make
+      # should touch ts1 because ts2 is newer. This could happen by luck,
+      # but most often, it will fail if make's support is insufficient. So
+      # test for several consecutive successes.
+      #
+      # (We reuse conftest.ts12 because we still want to modify existing
+      # files, not create new ones, per above.)
+      n=0
+      make=${MAKE-make}
+      until test $n -eq 3; do
+        echo one > conftest.ts1
+        sleep $am_try_res
+        echo two > conftest.ts2 # ts2 should now be newer than ts1
+        if $make -f conftest.mk | grep 'up to date' >/dev/null; then
+          make_ok=false
+          break # out of $n loop
+        fi
+        n=`expr $n + 1`
+      done
+    fi
+    #
+    if $make_ok; then
+      # Everything we know to check worked out, so call this resolution good.
+      am_cv_filesystem_timestamp_resolution=$am_try_res
+      break # out of $am_try_res loop
+    fi
+    # Otherwise, we'll go on to check the next resolution.
+  fi
+done
+rm -f conftest.ts?
+# (end _am_filesystem_timestamp_resolution)
+))
+
 # AM_SANITY_CHECK
 # ---------------
 AC_DEFUN(AM_SANITY_CHECK,
-AC_MSG_CHECKING(whether build environment is sane)
+AC_REQUIRE(_AM_FILESYSTEM_TIMESTAMP_RESOLUTION)
+# This check should not be cached, as it may vary across builds of
+# different projects.
+AC_MSG_CHECKING(whether build environment is sane)
 # Reject unsafe characters in $srcdir or the absolute working directory
 # name.  Accept space and tab only in the latter.
 am_lf='
@@ -28,49 +181,40 @@
 # symlink; some systems play weird games with the mod time of symlinks
 # (eg FreeBSD returns the mod time of the symlink's containing
 # directory).
-if (
-   am_has_slept=no
-   for am_try in 1 2; do
-     echo "timestamp, slept: $am_has_slept" > conftest.file
-     set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null`
-     if test "$*" = "X"; then
-	# -L didn't work.
-	set X `ls -t "$srcdir/configure" conftest.file`
-     fi
-     if test "$*" != "X $srcdir/configure conftest.file" \
-	&& test "$*" != "X conftest.file $srcdir/configure"; then
+am_build_env_is_sane=no
+am_has_slept=no
+rm -f conftest.file
+for am_try in 1 2; do
+  echo "timestamp, slept: $am_has_slept" > conftest.file
+  if (
+    set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null`
+    if test "$*" = "X"; then
+      # -L didn't work.
+      set X `ls -t "$srcdir/configure" conftest.file`
+    fi
+    test "$2" = conftest.file
+  ); then
+    am_build_env_is_sane=yes
+    break
+  fi
+  # Just in case.
+  sleep "$am_cv_filesystem_timestamp_resolution"
+  am_has_slept=yes
+done
 
-	# If neither matched, then we have a broken ls.  This can happen
-	# if, for instance, CONFIG_SHELL is bash and it inherits a
-	# broken ls alias from the environment.  This has actually
-	# happened.  Such a system could not be considered "sane".
-	AC_MSG_ERROR(ls -t appears to fail.  Make sure there is not a broken
-  alias in your environment)
-     fi
-     if test "$2" = conftest.file || test $am_try -eq 2; then
-       break
-     fi
-     # Just in case.
-     sleep 1
-     am_has_slept=yes
-   done
-   test "$2" = conftest.file
-   )
-then
-   # Ok.
-   :
-else
-   AC_MSG_ERROR(newly created file is older than distributed files!
+AC_MSG_RESULT($am_build_env_is_sane)
+if test "$am_build_env_is_sane" = no; then
+  AC_MSG_ERROR(newly created file is older than distributed files!
 Check your system clock)
 fi
-AC_MSG_RESULT(yes)
+
 # If we didn't sleep, we still need to ensure time stamps of config.status and
 # generated files are strictly newer.
 am_sleep_pid=
-if grep 'slept: no' conftest.file >/dev/null 2>&1; then
-  ( sleep 1 ) &
+AS_IF(test -e conftest.file || grep 'slept: no' conftest.file >/dev/null 2>&1,, dnl
+  ( sleep "$am_cv_filesystem_timestamp_resolution" ) &
   am_sleep_pid=$!
-fi
+)
 AC_CONFIG_COMMANDS_PRE(
   AC_MSG_CHECKING(that generated files are newer than configure)
    if test -n "$am_sleep_pid"; then

_service:tar_scm:automake-1.16.5.tar.xz/m4/silent.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/silent.m4 Changed

@@ -1,16 +1,16 @@
 ##                                                          -*- Autoconf -*-
-# Copyright (C) 2009-2021 Free Software Foundation, Inc.
+# Copyright (C) 2009-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
 # with or without modifications, as long as this notice is preserved.
 
-# AM_SILENT_RULES(DEFAULT)
-# --------------------------
-# Enable less verbose build rules; with the default set to DEFAULT
-# ("yes" being less verbose, "no" or empty being verbose).
-AC_DEFUN(AM_SILENT_RULES,
-AC_ARG_ENABLE(silent-rules, dnl
+# _AM_SILENT_RULES
+# ----------------
+# Enable less verbose build rules support.
+AC_DEFUN(_AM_SILENT_RULES,
+AM_DEFAULT_VERBOSITY=1
+AC_ARG_ENABLE(silent-rules, dnl
 AS_HELP_STRING(
   --enable-silent-rules,
   less verbose build output (undo: "make V=1"))
@@ -18,11 +18,6 @@
   --disable-silent-rules,
   verbose build output (undo: "make V=0"))dnl
 )
-case $enable_silent_rules in @%:@ (((
-  yes) AM_DEFAULT_VERBOSITY=0;;
-   no) AM_DEFAULT_VERBOSITY=1;;
-    *) AM_DEFAULT_VERBOSITY=m4_if($1, yes, 0, 1);;
-esac
 dnl
 dnl A few 'make' implementations (e.g., NonStop OS and NextStep)
 dnl do not support nested variable expansions.
@@ -41,14 +36,6 @@
 else
   am_cv_make_support_nested_variables=no
 fi)
-if test $am_cv_make_support_nested_variables = yes; then
-  dnl Using '$V' instead of '$(V)' breaks IRIX make.
-  AM_V='$(V)'
-  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
-else
-  AM_V=$AM_DEFAULT_VERBOSITY
-  AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY
-fi
 AC_SUBST(AM_V)dnl
 AM_SUBST_NOTMAKE(AM_V)dnl
 AC_SUBST(AM_DEFAULT_V)dnl
@@ -57,4 +44,28 @@
 AM_BACKSLASH='\'
 AC_SUBST(AM_BACKSLASH)dnl
 _AM_SUBST_NOTMAKE(AM_BACKSLASH)dnl
+dnl Delay evaluation of AM_DEFAULT_VERBOSITY to the end to allow multiple calls
+dnl to AM_SILENT_RULES to change the default value.
+AC_CONFIG_COMMANDS_PRE(dnl
+case $enable_silent_rules in @%:@ (((
+  yes) AM_DEFAULT_VERBOSITY=0;;
+   no) AM_DEFAULT_VERBOSITY=1;;
+esac
+if test $am_cv_make_support_nested_variables = yes; then
+  dnl Using '$V' instead of '$(V)' breaks IRIX make.
+  AM_V='$(V)'
+  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
+else
+  AM_V=$AM_DEFAULT_VERBOSITY
+  AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY
+fi
+)dnl
 )
+
+# AM_SILENT_RULES(DEFAULT)
+# --------------------------
+# Set the default verbosity level to DEFAULT ("yes" being less verbose, "no" or
+# empty being verbose).
+AC_DEFUN(AM_SILENT_RULES,
+AC_REQUIRE(_AM_SILENT_RULES)
+AM_DEFAULT_VERBOSITY=m4_if($1, yes, 0, 1))

_service:tar_scm:automake-1.16.5.tar.xz/m4/strip.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/strip.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/substnot.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/substnot.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/tar.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/tar.m4 Changed

@@ -1,6 +1,6 @@
 # Check how to create a tarball.                            -*- Autoconf -*-
 
-# Copyright (C) 2004-2021 Free Software Foundation, Inc.
+# Copyright (C) 2004-2024 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -46,15 +46,19 @@
       am_uid=`id -u || echo unknown`
       am_gid=`id -g || echo unknown`
       AC_MSG_CHECKING(whether UID '$am_uid' is supported by ustar format)
-      if test $am_uid -le $am_max_uid; then
-         AC_MSG_RESULT(yes)
+      if test x$am_uid = xunknown; then
+        AC_MSG_WARN(ancient id detected; assuming current UID is ok, but dist-ustar might not work)
+      elif test $am_uid -le $am_max_uid; then
+        AC_MSG_RESULT(yes)
       else
-         AC_MSG_RESULT(no)
-         _am_tools=none
+        AC_MSG_RESULT(no)
+        _am_tools=none
       fi
       AC_MSG_CHECKING(whether GID '$am_gid' is supported by ustar format)
-      if test $am_gid -le $am_max_gid; then
-         AC_MSG_RESULT(yes)
+      if test x$gm_gid = xunknown; then
+        AC_MSG_WARN(ancient id detected; assuming current GID is ok, but dist-ustar might not work)
+      elif test $am_gid -le $am_max_gid; then
+        AC_MSG_RESULT(yes)
       else
         AC_MSG_RESULT(no)
         _am_tools=none

_service:tar_scm:automake-1.16.5.tar.xz/m4/upc.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/upc.m4 Changed

_service:tar_scm:automake-1.16.5.tar.xz/m4/vala.m4 -> _service:tar_scm:automake-1.17.tar.xz/m4/vala.m4 Changed

_service:tar_scm:automake-1.17.tar.xz/m4/xargsn.m4 Added

_service:tar_scm:automake-1.16.5.tar.xz/maintainer/am-ft -> _service:tar_scm:automake-1.17.tar.xz/maintainer/am-ft Changed

_service:tar_scm:automake-1.16.5.tar.xz/maintainer/am-xft -> _service:tar_scm:automake-1.17.tar.xz/maintainer/am-xft Changed

_service:tar_scm:automake-1.16.5.tar.xz/maintainer/maint.mk -> _service:tar_scm:automake-1.17.tar.xz/maintainer/maint.mk Changed

@@ -1,6 +1,6 @@
 # Maintainer makefile rules for Automake.
 #
-# Copyright (C) 1995-2021 Free Software Foundation, Inc.
+# Copyright (C) 1995-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -27,9 +27,11 @@
 
 gitlog_to_changelog_command = $(PERL) $(srcdir)/lib/gitlog-to-changelog
 gitlog_to_changelog_fixes = $(srcdir)/.git-log-fix
-gitlog_to_changelog_options = --amend=$(gitlog_to_changelog_fixes) \
-                              --since='2011-12-28 00:00:00' \
-                              --no-cluster --format '%s%n%n%b'
+gitlog_to_changelog_options = \
+  --srcdir=$(srcdir) \
+  --amend=$(gitlog_to_changelog_fixes) \
+  --since='2011-12-28 00:00:00' \
+  --no-cluster --format '%s%n%n%b'
 
 EXTRA_DIST += lib/gitlog-to-changelog
 EXTRA_DIST += $(gitlog_to_changelog_fixes)
@@ -109,14 +111,23 @@
 
 # First component of a version number (mandatory).
 rx-0 = ^1-90-9*
-# Later components of a version number (optional).
-rx-1 = \.0-90-9*
+#
+# Minor component of a version number (omitted only for a major
+# release): .1, .10, etc. Assume we won't go beyond .99.
+rx-1 = \.0-9{1,2}
+#
+# Micro component of a version number (optional):
+# Either a single digit 0-9, or multiple digits starting with 0-8.
+# Multiple digits starting with 9 (.90, etc.) are for test releases.
+rx-2 = \.(0-9|0-80-9+)
+#
 # Used in recipes to decide which kind of release we are.
 stable_major_version_rx = $(rx-0)\.0$$
 stable_minor_version_rx = $(rx-0)$(rx-1)$$
-stable_micro_version_rx = $(rx-0)$(rx-1)$(rx-1)$$
-beta_version_rx = $(rx-0)($(rx-1)){1,2}bdfhjlnprtvxz$$
-alpha_version_rx  = $(rx-0)($(rx-1)){1,2}acegikmoqsuwy$$
+stable_micro_version_rx = $(rx-0)$(rx-1)$(rx-2)$$
+# The 9* is for pretests beyond the first five, e.g., .990, .992, ...
+beta_version_rx = $(rx-0)$(rx-1)\.99*02468$$
+alpha_version_rx  = $(rx-0)$(rx-1)\.99*13579$$
 match_version = echo "$(VERSION)" | $(EGREP) >/dev/null
 
 # Check that we don't have uncommitted or unstaged changes.
@@ -288,6 +299,7 @@
 	  && $(determine_release_type) \
 	  && ftp_base="https://$$dest.gnu.org/gnu/$(PACKAGE)" \
 	  && X () { printf '%s\n' "$$*" >> $@-t; } \
+	  && AO () { if test "$$dest" = alpha; then X "$$*"; else :; fi; } \
 	  && X "We are pleased to announce the $(PACKAGE_NAME) $(VERSION)" \
 	       "$$announcement_type." \
 	  && X \
@@ -304,21 +316,30 @@
 	  && X "  $$ftp_base/$(PACKAGE)-$(VERSION).tar.xz" \
 	  && X \
 	  && X "Please report bugs and problems to" \
-	       "<$(PACKAGE_BUGREPORT)>," \
+	       "<$(PACKAGE_BUGREPORT)>" \
+	  && X "(instead of replying to this mail)," \
 	  && X "and send general comments and feedback to" \
-	       "<$(PACKAGE_MAILINGLIST)>." \
+	       "<$(PACKAGE_MAILINGLIST)>," \
+	  && X "and patches to" \
+	       "<automake-patches@gnu.org>." \
 	  && X \
 	  && X "Thanks to everyone who has reported problems, contributed" \
-	  && X "patches, and helped testing Automake!" \
+	  && X "patches, and helped test Automake!" \
 	  && X \
 	  && X "-*-*-*-" \
 	  && X \
+  && AO "If you install this test release in its own prefix (recommended)" \
+  && AO "and you use libtool, you'll need to arrange for the libtool m4 files"\
+  && AO "to be found by aclocal. For info on this, see:" \
+  && AO "  https://gnu.org/s/automake/manual/automake.html#Libtool-library-used-but-LIBTOOL-is-undefined" \
+  && AO \
 	  && $(AWK) '\
 	        ($$0 ~ /^New in .*:/) { wait_for_end=1; } \
 		(/^~~~/ && wait_for_end) { print; exit(0) } \
 		{ print } \
 	     ' <$(srcdir)/NEWS >> $@-t \
-	  && mv -f $@-t $@
+	  && mv -f $@-t $@ \
+	  && ls -l ./$@
 .PHONY: announcement
 CLEANFILES += announcement
 
@@ -334,7 +355,7 @@
 SV_GIT_GL = 'https://$(git-sv-host)/gitweb/?p=gnulib.git;a=blob_plain;hb=HEAD;f='
 
 # Files that we fetch and which we compare against.
-# Note that the 'lib/COPYING' file must still be synced by hand.
+# Note that the 'lib/COPYING' file and help2man must still be synced by hand.
 FETCHFILES = \
   $(SV_GIT_CF)config.guess \
   $(SV_GIT_CF)config.sub \
@@ -347,8 +368,9 @@
   $(SV_GIT_GL)doc/INSTALL
 
 # Fetch the latest versions of few scripts and files we care about.
-# A retrieval failure or a copying failure usually mean serious problems,
+# A retrieval or copying failure usually means serious problems,
 # so we'll just bail out if 'wget' or 'cp' fail.
+# Update the top-level INSTALL in sync with lib/INSTALL as a special case.
 fetch:
 	$(AM_V_at)rm -rf Fetchdir
 	$(AM_V_at)mkdir Fetchdir
@@ -362,6 +384,7 @@
 	   else \
 	     echo "$@: updating file $$file"; \
 	     cp Fetchdir/$$file $(srcdir)/lib/$$file || exit 1; \
+	     test "$$file" != INSTALL || cp Fetchdir/$$file ../$$file; \
 	   fi; \
 	done
 	$(AM_V_at)rm -rf Fetchdir
@@ -384,6 +407,11 @@
 .PHONY: web-manual web-manual-update
 web-manual web-manual-update: t = $@.dir
 
+MANUAL_VERSION_HTML = \
+	<p>See the <a href="index-full.html">full version index</a> for the manual for other releases of Automake.</p>
+MANUAL_VERSION_HTML_PARENT = \
+	<p>See the <a href="../index-full.html">full version index</a> for the manual for other releases of Automake.</p>
+
 # Build manual in several formats.  Note to the recipe:
 # 1. The symlinking of automake.texi into the temporary directory is
 #    required to pacify extra checks from gendocs.sh.
@@ -422,14 +450,20 @@
 	$(AM_V_at)mkdir $t
 	$(AM_V_at)cd $t \
 	  && $(CVS) -z3 -d :ext:$(CVS_USER)@$(WEBCVS_ROOT)/$(PACKAGE) \
-	            co $(PACKAGE)
+	            co -l $(PACKAGE)/manual \
+	  && cd $(PACKAGE)/manual \
+	  && $(CVS) up html_node
 	@# According to the rsync manpage, "a trailing slash on the
 	@# source ... avoids creating an additional directory
 	@# level at the destination".  So the trailing '/' after
 	@# '$(web_manual_dir)' below is intended.
 	$(AM_V_at)$(RSYNC) -avP $(web_manual_dir)/ $t/$(PACKAGE)/manual
+	$(AM_V_at)sed -i '/This page generated by the/i$(MANUAL_VERSION_HTML)\n' $t/$(PACKAGE)/manual/index.html
+	$(AM_V_at)$(RSYNC) -avP $(web_manual_dir)/ $t/$(PACKAGE)/manual/$(VERSION)
+	$(AM_V_at)sed -i '/This page generated by the/i$(MANUAL_VERSION_HTML_PARENT)\n' $t/$(PACKAGE)/manual/$(VERSION)/index.html
 	$(AM_V_GEN): \
 	  && cd $t/$(PACKAGE)/manual \
+	  && $(CVS) add $(VERSION) $(VERSION)/*/ \
 	  && new_files=`$(CVSU) --types='?'` \
 	  && new_files=`echo "$$new_files" | sed s/^..//` \
 	  && { test -z "$$new_files" || $(CVS) add -ko $$new_files; } \
@@ -475,7 +509,7 @@
 # This script has an MIT-style license
 files_without_copyright += lib/install-sh
 
-# The UPDATE_COPYRIGHT_YEAR environment variable is honoured by the
+# The UPDATE_COPYRIGHT_YEAR environment variable is honored by the
 # 'lib/update-copyright' script.
 .PHONY: update-copyright
 update-copyright:
@@ -602,7 +636,7 @@
 
 pkg-targets = check dist
 
-# Note: "ttp" stays for "Third Party Package".
+# Note: "ttp" stands for "Third Party Package".
 
 ttp-check ttp-check-all: do-clone = $(GIT) clone --verbose
 ttp-check: ttp-packages = $(FEW_PACKAGES)

_service:tar_scm:automake-1.16.5.tar.xz/maintainer/rename-tests -> _service:tar_scm:automake-1.17.tar.xz/maintainer/rename-tests Changed

_service:tar_scm:automake-1.16.5.tar.xz/maintainer/syntax-checks.mk -> _service:tar_scm:automake-1.17.tar.xz/maintainer/syntax-checks.mk Changed

@@ -1,6 +1,6 @@
 # Maintainer checks for Automake.  Requires GNU make.
 
-# Copyright (C) 2012-2021 Free Software Foundation, Inc.
+# Copyright (C) 2012-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -150,7 +150,7 @@
 sc_rm_minus_f:
 	@if grep -v '^#' $(ams) $(xtests) \
 	   | grep -vE '/(rm-f-probe\.sh|spy-rm\.tap|subobj-clean.*-pr10697\.sh):' \
-	   | grep -E '\<rm (^-|\-^f *\>)'; \
+	   | grep -E '\<rm (^-|-^f *\>)'; \
 	then \
 	  echo "Suspicious 'rm' invocation." 1>&2; \
 	  exit 1; \
@@ -328,6 +328,10 @@
 # Makefile.am rules, configure.ac code and helper shell script created and
 # used by out shell scripts, because Autoconf (as of version 2.69) does not
 # yet ensure that $CONFIG_SHELL will be set to a proper POSIX shell.
+# We exclude failure_footer_text_colorized in test-defs.in from the
+# check because the result differs with $(...) and I (Karl) don't know why;
+# the testsuite-summary-color.sh and tap-summary-color tests fail when
+# $(...) is used. Life is too short.
 sc_tests_command_subst:
 	@found=false; \
 	scan () { \
@@ -335,6 +339,7 @@
 	         -e '/<<.*END/,/^END/b' -e '/<<.*EOF/,/^EOF/b' \
 	         -e 's/\\`/\\{backtick}/' \
 	         -e "s/^\\'$^'*\`^'*$*'/'{quoted-text}'/g" \
+	         -e /failure_footer_text_colorized=/d \
 	         -e '/`/p' $$*; \
 	}; \
 	for file in $(xtests); do \
@@ -440,7 +445,8 @@
 # Use '$sleep' instead.  Some file systems (e.g., Windows) have only
 # a 2sec resolution.
 sc_tests_plain_sleep:
-	@if grep -E '\bsleep +12345\b' $(xtests); then \
+	@if grep -vE '^ 	*#' $(xtests) \
+	      | grep -E '\bsleep +12345\b' | grep .; then \
 	  echo 'Do not use "sleep x" in the above tests.  Use "$$sleep" instead.' 1>&2; \
 	  exit 1; \
 	fi

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog-tests -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog-tests Changed

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.00 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.00 Changed

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.01 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.01 Changed

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.02 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.02 Changed

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.03 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.03 Changed

@@ -558,7 +558,7 @@
 	* lib/Makefile.am (dist_script_DATA): Move config-ml.in ...
 	(dist_pkgvdata_DATA): ... here.
 
-	* tests/spy.test: Document overlapping ::-rules incompatibilities,
+	* tests/spy.test: Document overlapping ::-rules incompatibility,
 	and check only non-overlapping ::-rules.
 
 	* doc/automake.texi (Texinfo): Define MAKEINFO, MAKEINFOHTML,
@@ -2338,7 +2338,7 @@
 2003-04-03  Alexandre Duret-Lutz  <adl@gnu.org>
 
 	* automake.in (check_trailing_slash): New function (variation on
-	a patch by Peter Muir).  Diagnose whitespaces following trailing
+	a patch by Peter Muir).  Diagnose whitespace following trailing
 	backslash.
 	(read_am_file): Use it.
 	* tests/backsl4.test: New file.
@@ -2965,7 +2965,7 @@
 
 -----
 
-Copyright (C) 2003-2021 Free Software Foundation, Inc.
+Copyright (C) 2003-2024 Free Software Foundation, Inc.
 
 Copying and distribution of this file, with or without modification, are
 permitted provided the copyright notice and this notice are preserved.

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.04 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.04 Changed

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.09 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.09 Changed

@@ -458,7 +458,7 @@
 
 2009-09-06  Stefano Lattarini  <stefano.lattarini@gmail.com>  (tiny change)
 
-	tests/README: warn about zsh incompatibilities.
+	tests/README: warn about zsh incompatibility.
 	* tests/README (User interface, Getting details from failures):
 	Explicitly state that every test is a "shell script", not just
 	a "script", and that it's run by `/bin/sh' by default.
@@ -2085,7 +2085,7 @@
 	Fix portability issues in distcleancheck_listfiles doc example.
 	* doc/automake.texi (Dist): In the `distcleancheck_listfiles'
 	code example, add `.' path, for Solaris `find', also rewrite so
-	`{}' appears only once and as separate argument, for Posix.
+	`{}' appears only once and as separate argument, for POSIX.
 	* tests/distcleancheck.test: New test.
 	* tests/Makefile.am: Update.
 	* THANKS: Update.
@@ -4088,7 +4088,7 @@
 	* automake.in (%_macro_for_cond): New variable.
 	(cond_stack_if): Use it for better error message about
 	missing dependency tracking conditionals.
-	* tests/asm2.test: New test, modelled after asm.test.
+	* tests/asm2.test: New test, modeled after asm.test.
 	* tests/Makefile.am: Adjust.
 	Report by Ralf Corsepius.
 
@@ -4522,9 +4522,9 @@
 	Don't use 'path' to talk about file names,
 	as per GNU coding standards.  Close a race condition reported by Ralf
 	Wildenhues and Stepan Kasal.  There is still a race condition
-	on hosts that predate Posix 1003.1-1992, but we can't help this.
-	Don't mishandle weird characters like space on pre-Posix hosts.
-	Invoke mkdir at most once per dir arg on pre-Posix hosts.
+	on hosts that predate POSIX 1003.1-1992, but we can't help this.
+	Don't mishandle weird characters like space on pre-POSIX hosts.
+	Invoke mkdir at most once per dir arg on pre-POSIX hosts.
 
 2006-05-11  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
@@ -4856,7 +4856,7 @@
 2006-01-12  Paul Eggert  <eggert@cs.ucla.edu>
 
 	* lib/install-sh (dstdir): Don't use semicolons inside { } in
-	sed scripts, as Posix says it's not portable.
+	sed scripts, as POSIX says it's not portable.
 	* lib/missing (file): Likewise.
 	* lib/am/distdir.am (distcheck): Likewise.
 	* tests/comment7.test, tests/comment9.test, tests/confh.test: Likewise
@@ -5387,7 +5387,7 @@
 	* tests/pr401.test, tests/pr401b.test, tests/pr401c.test: New tests.
 	* tests/Makefile.am (TESTS): Add them.
 	* doc/automake.texi (Optional) <AC_CONFIG_LIBOBJ_DIR>: Document.
-	(LIBOBJS): Document changes in behaviour of
+	(LIBOBJS): Document changes in behavior of
 	LIBOBJS, ALLOCA, LTLIBOBJS & LTALLOCA in the presence of
 	subdir-objects and an invocation of AC_CONFIG_LIBOBJ_DIR.
 
@@ -5757,7 +5757,7 @@
 
 -----
 
-Copyright (C) 2005-2021 Free Software Foundation, Inc.
+Copyright (C) 2005-2024 Free Software Foundation, Inc.
 
 Copying and distribution of this file, with or without modification, are
 permitted provided the copyright notice and this notice are preserved.

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.11 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.11 Changed

@@ -114,14 +114,14 @@
 	was better to do so only for directories specified with a
 	relative path.
 
-	The rationale for this latter behaviour was that, before the
+	The rationale for this latter behavior 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
+	all, and start verifying the correct behavior of `-I' with a
 	new test.
 
 	* tests/aclocal-install-absdir.test: New test.
@@ -386,7 +386,7 @@
 	  $ echo status = $?
 	  status = 1
 
-	We need to work around this misbehaviour in a couple of our
+	We need to work around this misbehavior in a couple of our
 	tests (whose failures where causing cascading failures in a
 	lot of other tests).
 
@@ -543,7 +543,7 @@
 	tests was usually skipped on testsuite runs "in the wild", thus
 	needlessly reducing coverage.
 
-	Second, the older testsuite behaviour made more difficult for
+	Second, the older testsuite behavior 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
@@ -905,7 +905,7 @@
 	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).
+	be decompressed 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,
@@ -945,7 +945,7 @@
 	proceeds with the configuration process -- only for the build to
 	possibly fail later, at make time.
 
-	This behaviour is intended; the Autoconf manual reads:
+	This behavior 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,
@@ -953,7 +953,7 @@
 	   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
+	This AC_PROG_LEX behavior 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
@@ -1485,12 +1485,12 @@
 	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
+	the `${infodir}/dir' or not; instead, honor 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.
+	interference from the environment.
 	* doc/automake.texi (Texinfo): Update.
 	* NEWS: Likewise.
 	* THANKS: Likewise.
@@ -1644,7 +1644,7 @@
 	proceeds with the configuration process -- only for the build to
 	possibly fail later, at make time.
 
-	This behaviour is intended; the Autoconf manual reads:
+	This behavior 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,
@@ -1652,7 +1652,7 @@
 	   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
+	This AC_PROG_LEX behavior 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
@@ -2116,7 +2116,7 @@
 
 2011-09-28  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
-	tap/awk: account for unusual korn shell signal handling behaviour
+	tap/awk: account for unusual korn shell signal handling behavior
 	This change has been motivated by a testsuite failure on Debian
 	with the AT&T Korn Shell version 93u-1.
 	* lib/tap-driver.sh: Temporarily ignore some common signals when
@@ -2130,12 +2130,12 @@
 	tap/awk: handle exit statuses > 256 (seen on few korn shells)
 	Some Korn shells, when a child process die due to signal number
 	n, can leave in $? an exit status of 256+n instead of the more
-	standard 128+n.  Apparently, both behaviours are allowed by
+	standard 128+n.  Apparently, both behaviors are allowed by
 	POSIX, so be prepared to handle them both.
 	This change has been motivated by a testsuite failure on Debian
 	with the AT&T Korn Shell version 93u-1.
 	* lib/tap-driver.sh (get_test_exit_message): Handle the described
-	Korn Shell behaviour too.
+	Korn Shell behavior too.
 	($scriptversion): Update.
 
 2011-09-28  Stefano Lattarini  <stefano.lattarini@gmail.com>
@@ -2390,7 +2390,7 @@
 
 2011-09-13  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
-	test defs: work around weird ksh behaviour w.r.t. signal handling
+	test defs: work around weird ksh behavior w.r.t. signal handling
 	* tests/defs (is_blocked_signal): Use perl to determine whether a
 	signal is trapped, since trying to do it portably within the shell
 	means opening a nasty can of worms.
@@ -3196,7 +3196,7 @@
 	testsuite: different test scripts cannot share the same basename
 	If two test scripts have the same basename, they will end up
 	sharing the same log file, leading to all sort of undefined and
-	undesired behaviours.  Add a Makefile check verifying that this
+	undesired behaviors.  Add a Makefile check verifying that this
 	is not the case.
 	* tests/test-logs-repeated.test: New test, verifying previously
 	unspecified semantics (in the definition of $(TEST_LOGS) from
@@ -3294,7 +3294,7 @@
 	e.g. syntax or I/O errors) to the log files instead that to the
 	console.
 	* tests/tap-driver-stderr.test: New test, verifying the improved
-	driver behaviour.  Notice that this test still fails when using
+	driver behavior.  Notice that this test still fails when using
 	the perl implementation of the TAP driver.
 	* tests/Makefile.am (tap_other_tests): Update.
 
@@ -3451,7 +3451,7 @@
 	coverage: a TAP result numbered "0" is always out-of-order
 	* tests/tap-test-number-0.test: New, checks that a test result
 	numbered as 0 is to be considered out-of-order; this is
-	consistent with the behaviour of the `prove' utility.
+	consistent with the behavior of the `prove' utility.
 	* tests/Makefile.am (tap_with_common_setup_tests): Update.
 
 2011-08-20  Stefano Lattarini  <stefano.lattarini@gmail.com>
@@ -3494,7 +3494,7 @@
 	`configure.in'.
 	* tests/vpath.test: Make grepping of generated `Makefile.in'
 	slightly stricter.  Prefer trailing `:' over trailing `Exit 0'.
-	* tests/suffix6c.test: Unset OBJEXT to avoid interferences from
+	* tests/suffix6c.test: Unset OBJEXT to avoid interference from
 	the environment.
 	* tests/suffix12.test: Do not whitespace-indent `##' comments
 	when they are embedded in a makefile rule: having them indented
@@ -3727,14 +3727,14 @@
 2011-08-12  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
 	coverage: TAP diagnostics after "Bail out!" aren't reported
-	This is compatible with the behaviour of the `prove' utility.
+	This is compatible with the behavior of the `prove' utility.
 	* tests/tap-bailout-suppress-later-diagnostic.test: New test.
 	* tests/Makefile.am (tap_with_common_setup_tests): Update.
 
 2011-08-12  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
 	coverage: TAP errors after a "Bail out!" directive aren't reported
-	This is compatible with the behaviour of the `prove' utility.
+	This is compatible with the behavior of the `prove' utility.
 	* tests/tap-bailout-suppress-later-errors.test: New test.
 	* tests/tap-bailout-badexit.test: Renamed ...
 	* tests/tap-bailout-suppress-badexit.test: ... to this, for
@@ -3786,7 +3786,7 @@
 2011-08-12  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
 	tap: non-zero exit status after "Bail out!" should not be reported
-	This new behaviour is more consistent with that of the `prove'
+	This new behavior is more consistent with that of the `prove'
 	utility.  Also, experience with the use of TAP in the Automake's
 	own test suite has shown that reporting non-zero exit status from
 	a script after it has issued a "Bail out!" directive is mostly
@@ -3801,7 +3801,7 @@
 2011-08-11  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
 	tap: a "plan with SKIP" after test results is an error
-	This new behaviour is both more natural and more consistent with
+	This new behavior is both more natural and more consistent with
 	that of the `prove' utility.
 	* lib/tap-driver (handle_tap_plan): Do not stop TAP parsing when
 	a "plan with SKIP" line (e.g., "1..0 # SKIP") is encountered, and
@@ -4282,7 +4282,7 @@
 	  ok 1
 	was considered to be an error, diagnosed with a message "test
 	plan in middle of output"; as effect of the current change, such
-	input is now valid.  This is more consistent with the behaviour
+	input is now valid.  This is more consistent with the behavior
 	of the `prove' utility.
 	* lib/tap-driver ($lineno): Removed, no more needed.
 	($tap_stopped): New global variable.
@@ -4470,7 +4470,7 @@
 
 	tap: fix whitespace munging of diagnostic messages
 	* lib/tap-driver (extract_tap_comment): Pass the `g' flag to the
-	substitution operator, to strip also trailing whitespaces.  Fixes
+	substitution operator, to strip also trailing whitespace.  Fixes
 	a failure in test `tap-whitespace-normalization.test'.
 
 2011-08-06  Stefano Lattarini  <stefano.lattarini@gmail.com>
@@ -5149,7 +5149,7 @@
 	format of the `.log' files.  Note that this change makes the
 	`:end-metadata:' field obsolete.
 	* doc/automake.texi (Parallel Test Harness, Log files generation
-	and test results recording): Document the new APIs and behaviour;
+	and test results recording): Document the new APIs and behavior;
 	some related minor rewordings and fixlets.
 	* NEWS: Update.
 	* automake.in (handle_tests): When bringing in the content of
@@ -5304,7 +5304,7 @@
 	* tests/parallel-tests-fd-redirect.test: Likewise.
 	* tests/parallel-tests-am_tests_environment.test: Remove checks
 	about the use of redirections in AM_TESTS_ENVIRONMENT: they would
-	check deprecated (if not undefined) behaviour now.  Strengthen a
+	check deprecated (if not undefined) behavior now.  Strengthen a
 	couple of still valid checks, to keep the test more in sync with
 	the documentation.  Improve debugging information.
 	* tests/Makefile.am (TESTS): Update.
@@ -5569,7 +5569,7 @@
 	moved into the manual.
 	(recheck, recheck-html): Minor adjustments to better conform to the
 	documentation (this should cause no semantic changes w.r.t. the
-	former behaviour); minor improvements and extensions to existing
+	former behavior); minor improvements and extensions to existing
 	comments.
 	* tests/test-driver-create-log-dir.test: New test.
 	* tests/test-driver-strip-vpath.test: Likewise.
@@ -6119,7 +6119,7 @@
 	define (in the top-level Makefile.am) extra flags to be passed
 	to configure at "make distcheck" time; DISTCHECK_CONFIGURE_FLAGS
 	should be reserved for the user.  Add proper `@vindex' directive.
-	Document that AM_DISTCHECK_CONFIGURE_FLAGS is not honoured in a
+	Document that AM_DISTCHECK_CONFIGURE_FLAGS is not honored in a
 	subpackage Makefile.am, but the flags in it are passed down to
 	the configure script of the subpackage.
 	* lib/am/distdir.am (distcheck): Also pass the flags in
@@ -6761,13 +6761,13 @@
 
 2011-05-29  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
-	automake, aclocal: honour configure-time AUTOCONF and AUTOM4TE
+	automake, aclocal: honor configure-time AUTOCONF and AUTOM4TE
 	Currently, the Automake's own configure script allow definition
 	of AUTOCONF and AUTOM4TE, expected to point respectively to an
 	autoconf and autom4te programs.  But while these definitions are
-	honoured in the Automake's build systems and test suite, they
-	were *not* honoured in the generated `automake' and `aclocal'
-	scripts.  This behaviour, apart from being wrong in that it does
+	honored in the Automake's build systems and test suite, they
+	were *not* honored in the generated `automake' and `aclocal'
+	scripts.  This behavior, apart from being wrong in that it does
 	not allow the user enough freedom in choosing his tools, also
 	caused inconsistencies in the test suite, brining to spurious
 	failures.
@@ -6784,7 +6784,7 @@
 
 	build: the user can override AUTOM4TE, AUTORECONF and AUTOUPDATE too
 	Our build system allows the user to override AUTOCONF and AUTOHEADER
-	at configure time, and honours these overrides in our testsuite.
+	at configure time, and honors these overrides in our testsuite.
 	But it didn't do the same with AUTOM4TE, AUTORECONF and AUTOUPDATE.
 	This change fixes that inconsistency.
 	* configure.ac (am_AUTOM4TE, am_AUTOUPDATE, am_AUTORECONF): New
@@ -6956,7 +6956,7 @@
 	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 might be (partly) intended; the Autoconf manual
+	This behavior might be (partly) 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
@@ -6965,7 +6965,7 @@
 	   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
+	This AC_PROG_LEX behavior is causing some spurious failures of the
 	Automake testsuite in environments which lack a proper library
 	providing `yywrap' (this happens for example in	Linux->MinGW cross
 	compilations).  But at this point is clear that a proper workaround
@@ -7208,7 +7208,7 @@
 	is passed to the exit trap.  Indeed, this happens in practice, as
 	an autoconf-generated configure script can exit with status `77'
 	if it fails to find, e.g., a required compiler.
-	While this behaviour is quite useful for avoiding spurious test
+	While this behavior is quite useful for avoiding spurious test
 	failures in the wild, it can also sometimes prevent the Automake
 	developers to easily see and declare the requirements of their
 	tests.
@@ -7342,7 +7342,7 @@
 	* tests/gen-parallel-tests: Do not generate "siblings" for tests
 	that explicitly define the `parallel_tests', whether to "yes" or
 	to any other value.  Extend heading comments to give a rationale
-	for this behaviour.
+	for this behavior.
 	* tests/README: Update.
 
 2011-05-20  Stefano Lattarini  <stefano.lattarini@gmail.com>
@@ -7484,7 +7484,7 @@
 
 	depmod tests: fix bug in depmodes list extraction
 	* tests/depmod-tests.sh (get_depmodes): Use `echo $all_depmodes'
-	instead of `... | tr "$nl" "$sp"' to strip extra whitespaces and
+	instead of `... | tr "$nl" "$sp"' to strip extra whitespace and
 	newlines from `$all_depmodes'.  The latter idiom with `tr' is
 	wrong since it gets run before `./defs' is sourced, and thus `$nl'
 	and `$sp' are undefined.
@@ -8116,7 +8116,7 @@
 	testsuite: more environment sanitization
 	* tests/defs.in: Sanity check: abort if any of `parallel_tests'
 	or `required' is in the environment.
-	($sed_unindent_prog): Initialize to empty, to avoid interferences
+	($sed_unindent_prog): Initialize to empty, to avoid interference
 	from the environment.
 	* tests/self-check-me-in-env.test: Renamed to ...
 	* tests/self-check-env-sanitize.test: ... this, and extended.
@@ -8411,13 +8411,13 @@
 
 	yacc: update NEWS and docs about yacc-generated headers extensions
 	* doc/automake.texi (Yacc and Lex): Document explicitly that
-	extensions of yacc-generated headers are modelled after the
+	extensions of yacc-generated headers are modeled after the
 	extension of the corresponding sources.
 	* NEWS: Update.
 
 2011-01-28   Stefano Lattarini  <stefano.lattarini@gmail.com>
 
-	yacc: extension of headers modelled after extension of sources
+	yacc: extension of headers modeled after extension of sources
 	With this change, if '-d' is in *YFLAGS, a yacc input file named
 	foo.y++ will cause a foo.h++ header to be generated, instead of a
 	foo.h header.  Similarly for foo.ypp, foo.yxx and foo.yy.
@@ -8428,7 +8428,7 @@
 	* lib/am/yacc.am (am__yacc_c2h): New internal variable.
 	(?GENERIC?%EXT%%DERIVED-EXT%, ?!GENERIC?%OBJ%): Get the name of
 	the header dynamically at make runtime, so that its extension is
-	modelled after the extension of the source.
+	modeled after the extension of the source.
 	* automake.in (lang_yacc_target_hook): Adjust the calculation of
 	`$header' accordingly.
 	* tests/yacc-cxx.test: New test.
@@ -9701,7 +9701,7 @@
 	* tests/txinfo4.test: Escape literal dots in grep regexps.  Add
 	trailing `:' command.
 	* tests/txinfo29.test: Likewise.  Relax grepping of generated
-	Makefile.in w.r.t. whitespaces.  Prefer `cat' over `echo' to
+	Makefile.in w.r.t. whitespace.  Prefer `cat' over `echo' to
 	append to configure.in.
 	* tests/txinfo3.test: Likewise.
 	* tests/vtexi.test: Improve grepping of Makefile.in (sometimes
@@ -9832,8 +9832,8 @@
 
 2011-01-09  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
-	cosmetics: remove trailing whitespaces
-	* doc/automake.texi: Remove trailing whitespaces.
+	cosmetics: remove trailing whitespace
+	* doc/automake.texi: Remove trailing whitespace.
 	* tests/cond13.test: Likewise.
 	* tests/cond14.test: Likewise.
 	* tests/fort4.test: Likewise.
@@ -10538,7 +10538,7 @@
 	* tests/specflg3.test: Enable `errexit' shell flag, with related
 	changes.  Avoid unportable use of `-e' option of fgrep.  Prefer
 	trailing `:' over trailing `Exit 0'.  Remove extra empty lines,
-	and cosmetic changes to whitespaces.
+	and cosmetic changes to whitespace.
 	* tests/obsolete.test: Enable `errexit' shell flag, with related
 	changes.  Improve verbosity.  Other miscellaneous changes.
 
@@ -11112,7 +11112,7 @@
 	Improve tests `help*.test' (also fixes maintcheck failures).
 	* tests/help.test: To run automake, use `$AUTOMAKE' with all `-W'
 	flags stripped away rather than hard-coded `automake-$APIVERSION',
-	to better honour user-overrides.  Similarly for aclocal.
+	to better honor user-overrides.  Similarly for aclocal.
 	* tests/help2.test: Likewise.
 	* tests/help3.test: Likewise.
 	* tests/help4.test: Likewise.
@@ -11410,7 +11410,7 @@
 	* NEWS: Update.
 	Report by Bob Friesenhahn.
 
-	Posix 2008 requires make to set errexit.
+	POSIX 2008 requires make to set errexit.
 	* lib/am/check.am: Update comment.
 
 2010-09-06  Stefano Lattarini  <stefano.lattarini@gmail.com>
@@ -12136,7 +12136,7 @@
 	* tests/obsolete.test: Add a comment explaining why we need
 	an indirection in adding $AUTOUPDATE to $required.
 
-	Normalize whitespaces in 'tests/Makefile.am'.
+	Normalize whitespace in 'tests/Makefile.am'.
 	* tests/Makefile.am (TESTS): Use only spaces, not tabs, in the
 	definition of this variable.
 
@@ -12935,7 +12935,7 @@
 	* tests/parallel-tests10.test: Likewise.
 	* tests/README (Section "Writing Test Cases" subsection "Do"):
 	Adjusted the parts referring to tests checking `parallel-tests'
-	behaviour.  Some other minor related improvements.
+	behavior.  Some other minor related improvements.
 	* tests/.gitignore (defs-p): Removed.
 
 2010-03-04  Stefano Lattarini  <stefano.lattarini@gmail.com>
@@ -13097,7 +13097,7 @@
 
 -----
 
-Copyright (C) 2010-2021 Free Software Foundation, Inc.
+Copyright (C) 2010-2024 Free Software Foundation, Inc.
 
 Copying and distribution of this file, with or without modification, are
 permitted provided the copyright notice and this notice are preserved.

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.96 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.96 Changed

_service:tar_scm:automake-1.16.5.tar.xz/old/ChangeLog.98 -> _service:tar_scm:automake-1.17.tar.xz/old/ChangeLog.98 Changed

_service:tar_scm:automake-1.16.5.tar.xz/old/TODO -> _service:tar_scm:automake-1.17.tar.xz/old/TODO Changed

@@ -217,7 +217,7 @@
 Jim's idea: should look for @setfilename and warn if filenames too long
 * guess split size
 
-from joerg-martin schwarz:
+from Joerg-Martin Schwarz:
  -- If Makefile.am contains $(CC), $(COMPILE), $(YLWRAP), ....
     in an explicitly written rule,  you should emit the corresponding
     Makefile variables automatically.
@@ -254,7 +254,7 @@
 install.  In BSD environment, use:
 	LINKS = from1 to1 from2 to2 ...
 
-Need way to say there are no suffixes in a Makefile (Franc,ois'
+Need way to say there are no suffixes in a Makefile (François'
 "override" idea suffices here)
 
 Check to make sure various scripts are executable (IE when looking for
@@ -363,9 +363,6 @@
 
 Make a definition of the term "source"
 
-document how to use Automake with CVS.  Idea from Mark Galassi.  Also
-include Greg Woods' more sophisticated "cvs-dist" target.
-
 -- must document all variables that are supposed
    to be public knowledge
 
@@ -483,7 +480,7 @@
 
 * copyright notice
 
-Copyright 1994-2021 Free Software Foundation, Inc.
+Copyright 1994-2024 Free Software Foundation, Inc.
 
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by

_service:tar_scm:automake-1.16.5.tar.xz/pre-inst-env.in -> _service:tar_scm:automake-1.17.tar.xz/pre-inst-env.in Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/CheckListOfTests.am -> _service:tar_scm:automake-1.17.tar.xz/t/CheckListOfTests.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/README -> _service:tar_scm:automake-1.17.tar.xz/t/README Changed

@@ -1,10 +1,8 @@
 			    The Automake test suite
 
-
 User interface
 ==============
 
-
 Running the tests
 -----------------
 
@@ -99,7 +97,7 @@
 
   The test scripts are written with portability in mind, and should run
   with any decent POSIX shell.  However, it is worth nothing that older
-  versions of Zsh (pre-4.3) exhibited several bugs and incompatibilities
+  versions of Zsh (pre-4.3) exhibited several bugs and compatibility issues
   with our uses, and are thus not supported for running Automake's test
   scripts.
 
@@ -117,10 +115,18 @@
 Writing test cases
 ==================
 
+* See also summary information in the top-level HACKING file.
+
 * If you plan to fix a bug, write the test case first.  This way you'll
   make sure the test catches the bug, and that it succeeds once you have
   fixed the bug.
 
+* Sometimes it is better to add to an existing test than to write a new one.
+  In any case, it is good to look for existing tests checking for
+  something related, and use one or more them as a starting point.
+  The posixtarget test is a nearly-minimal test if you end up starting
+  from scratch.
+
 * Add a copyright/license paragraph.
 
 * Explain what the test does, i.e., which features it checks, which
@@ -142,8 +148,7 @@
   tools which can be taken for granted because they're listed in the
   GNU Coding Standards (for example, 'gzip').
 
-* Include 'test-init.sh' in every test script (see existing tests for
-  examples of how to do this).
+* Include 'test-init.sh' in every test script.
 
 * Use the 'skip_' function to skip tests, with a meaningful message if
   possible.  Where convenient, use the 'warn_' function to print generic
@@ -222,8 +227,8 @@
   than another.
 
 * Use cat or grep or similar commands to display (part of) files that
-  may be interesting for debugging, so that when a user send a verbose
-  output we don't have to ask him for more details.  Display stderr
+  may be interesting for debugging, so that when users send verbose
+  output we don't have to ask them for more details.  Display stderr
   output on the stderr file descriptor.  If some redirected command is
   likely to fail, display its output even in the failure case, before
   exiting.

_service:tar_scm:automake-1.16.5.tar.xz/t/ac-output-old.tap -> _service:tar_scm:automake-1.17.tar.xz/t/ac-output-old.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-I-and-install.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-I-and-install.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-I-order-1.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-I-order-1.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-I-order-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-I-order-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-I-order-3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-I-order-3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-acdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-acdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-amflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-amflags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-autoconf-version-check.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-autoconf-version-check.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-comments-respected.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-comments-respected.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-deleted-header-aclocal-amflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-deleted-header-aclocal-amflags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-deleted-header.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-deleted-header.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-deps-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-deps-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-deps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-deps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-dirlist-abspath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-dirlist-abspath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-dirlist-globbing.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-dirlist-globbing.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-dirlist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-dirlist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-install-absdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-install-absdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-install-fail.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-install-fail.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-install-mkdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-install-mkdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-m4-include-are-scanned-aclocal-amflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-m4-include-are-scanned-aclocal-amflags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-m4-include-are-scanned.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-m4-include-are-scanned.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-m4-sinclude.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-m4-sinclude.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-macrodir.tap -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-macrodir.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-macrodirs.tap -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-macrodirs.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-missing-macros.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-missing-macros.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-no-extra-scan.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-no-extra-scan.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-no-force.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-no-force.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-no-install-no-mkdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-no-install-no-mkdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-no-symlinked-overwrite.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-no-symlinked-overwrite.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-no-unused-required.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-no-unused-required.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-path-install-serial.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-path-install-serial.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-path-install.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-path-install.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-path-nonexistent.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-path-nonexistent.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-path-precedence.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-path-precedence.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -26,6 +26,7 @@
 BAR_MACRO
 AC_PROG_LIBTOOL
 AM_GNU_GETTEXT
+AC_OUTPUT
 END
 
 mkdir mdir1 mdir2 mdir3 sysdir extradir
@@ -88,4 +89,32 @@
 # A final sanity check.
 $FGREP '::fail' configure && exit 1
 
+# Same checks, but now with the command line option.
+ACLOCAL_PATH=mdir2:mdir1 $ACLOCAL -I mdir3 --system-acdir sysdir --aclocal-path "mdir1:mdir2"
+$ACLOCAL -I mdir3 --system-acdir sysdir --aclocal-path "mdir1:mdir2"
+$AUTOCONF
+
+$FGREP '::' configure # For debugging.
+
+# Directories coming first in ACLOCAL_PATH should take precedence
+# over those coming later.
+$FGREP '::pass-foo::' configure
+
+# Directories from '-I' options should take precedence over directories
+# in ACLOCAL_PATH.
+$FGREP '::pass-bar::' configure
+
+# Directories in ACLOCAL_PATH should take precedence over system acdir
+# (typically '${prefix}/share/aclocal'), and any directory added through
+# the 'dirlist' special file.
+$FGREP '::pass-gettext::' configure
+$FGREP '::pass-libtool::' configure
+
+# Directories in ACLOCAL_PATH shouldn't take precedence over the internal
+# automake acdir (typically '${prefix}/share/aclocal-${APIVERSION}').
+$FGREP 'am__api_version' configure
+
+# A final sanity check.
+$FGREP '::fail' configure && exit 1
+
 :

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-path.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-path.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-pr450.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-pr450.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-print-acdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-print-acdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-remake-misc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-remake-misc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-req.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-req.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-scan-configure-ac-pr319.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-scan-configure-ac-pr319.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-serial.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-serial.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-underquoted-defun.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-underquoted-defun.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal-verbose-install.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal-verbose-install.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aclocal.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aclocal.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/acsilent.sh -> _service:tar_scm:automake-1.17.tar.xz/t/acsilent.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/acsubst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/acsubst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/acsubst2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/acsubst2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/add-missing-install-sh.sh -> _service:tar_scm:automake-1.17.tar.xz/t/add-missing-install-sh.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/add-missing-multiple.sh -> _service:tar_scm:automake-1.17.tar.xz/t/add-missing-multiple.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/add-missing.tap -> _service:tar_scm:automake-1.17.tar.xz/t/add-missing.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/all.sh -> _service:tar_scm:automake-1.17.tar.xz/t/all.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/all2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/all2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/alloca.sh -> _service:tar_scm:automake-1.17.tar.xz/t/alloca.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/alloca2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/alloca2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/alpha.sh -> _service:tar_scm:automake-1.17.tar.xz/t/alpha.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/alpha2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/alpha2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-config-header.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-config-header.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-default-source-ext.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-default-source-ext.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-include-only-one-generated-fragment.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-include-only-one-generated-fragment.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-macro-not-found.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-macro-not-found.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-missing-prog.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-missing-prog.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-prog-cc-c-o.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-prog-cc-c-o.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-prog-cc-stdc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-prog-cc-stdc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/am-tests-environment.sh -> _service:tar_scm:automake-1.17.tar.xz/t/am-tests-environment.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amassign.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amassign.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amhello-binpkg.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amhello-binpkg.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amhello-cflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amhello-cflags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amhello-cross-compile.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amhello-cross-compile.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aminit-moreargs-deprecation.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aminit-moreargs-deprecation.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/aminit-trailing-dnl-comment-pr16841.sh -> _service:tar_scm:automake-1.17.tar.xz/t/aminit-trailing-dnl-comment-pr16841.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amopt.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amopt.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amopts-location.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amopts-location.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amopts-variable-expansion.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amopts-variable-expansion.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/amsubst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/amsubst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ansi2knr-no-more.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ansi2knr-no-more.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib5a.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib5a.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib5b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib5b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib6a.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib6a.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib6b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib6b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar-lib7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar-lib7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ar5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ar5.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/ar_override.sh Added

@@ -0,0 +1,50 @@
+#! /bin/sh
+# Copyright (C) 2009-2024 Free Software Foundation, Inc.
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Test to make sure _AR variables are detected and used as documented.
+
+. test-init.sh
+
+cat >> configure.ac << 'END'
+AC_PROG_CC
+AM_PROG_AR
+AC_PROG_RANLIB
+AC_OUTPUT
+END
+
+cat > Makefile.am << 'END'
+EXTRA_LIBRARIES = libfoo.a libbar.a
+libfoo_a_SOURCES = foo.c
+libfoo_a_AR = $(AR)
+libbar_a_SOURCES = bar.c
+END
+
+$ACLOCAL
+$AUTOMAKE -a
+
+# We should use libfoo_a_AR not AR ARFLAGS.
+grep '.\$(libfoo_a_AR) *libfoo.a' Makefile.in
+grep '.\$(AR).*libfoo.a' Makefile.in && exit 1
+grep '.\$(ARFLAGS).*libfoo.a' Makefile.in && exit 1
+grep '^ *libfoo_a_AR *=.*\$(ARFLAGS)' Makefile.in && exit 1
+
+# We should use default AR ARFLAGS.
+grep '^ *libbar_a_AR *=.*\$(ARFLAGS)' Makefile.in
+
+# Silent make rules should use AM_V_AR.
+grep '.\$(AM_V_AR)\$(libbar_a_AR)' Makefile.in
+
+exit 0

_service:tar_scm:automake-1.16.5.tar.xz/t/asm.sh -> _service:tar_scm:automake-1.17.tar.xz/t/asm.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/asm2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/asm2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/asm3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/asm3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-acconfig-no-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-acconfig-no-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-acconfig.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-acconfig.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-aclocal-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-aclocal-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-config-headers.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-config-headers.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-configure-no-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-configure-no-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-no-duplicate.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-no-duplicate.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-stamp-vti.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-stamp-vti.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autodist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autodist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autohdr-subdir-pr12495.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autohdr-subdir-pr12495.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autohdr.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autohdr.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autohdr3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autohdr3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autohdr4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autohdr4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/autohdrdry.sh -> _service:tar_scm:automake-1.17.tar.xz/t/autohdrdry.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/automake-cmdline.tap -> _service:tar_scm:automake-1.17.tar.xz/t/automake-cmdline.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-autodetect.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-autodetect.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-cc-pr15981.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-cc-pr15981.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-computed.tap -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-computed.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-misplaced.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-misplaced.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-nonexistent.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-nonexistent.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-pr15981.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-pr15981.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-pr19311.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-pr19311.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/auxdir-subsubdir.sh Added

@@ -0,0 +1,40 @@
+#! /bin/sh
+# Copyright (C) 2022-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Make sure auxdir with subdir aux files works.
+# https://bugs.gnu.org/20300
+
+. test-init.sh
+
+cat > configure.ac <<END
+AC_INIT($me, 1.0)
+AC_CONFIG_AUX_DIR(build-aux)
+AC_REQUIRE_AUX_FILE(top-file)
+AC_REQUIRE_AUX_FILE(subdir/file)
+AM_INIT_AUTOMAKE
+AC_CONFIG_FILES(Makefile)
+END
+
+touch Makefile.am
+
+mkdir -p build-aux/subdir
+: >build-aux/top-file
+: >build-aux/subdir/file
+
+$ACLOCAL
+$AUTOMAKE --add-missing
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir-unportable.tap -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir-unportable.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/auxdir8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/auxdir8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/am-test-lib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/am-test-lib.sh Changed

@@ -1,6 +1,6 @@
 # -*- shell-script -*-
 #
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -103,13 +103,14 @@
   # Use perl, since trying to do this portably in the shell can be
   # very tricky, if not downright impossible.  For reference, see:
   # <https://lists.gnu.org/archive/html/bug-autoconf/2011-09/msg00004.html>
-  if $PERL -w -e '
-    use strict;
-    use warnings FATAL => "all";
-    use POSIX;
-    my %oldsigaction = ();
-    sigaction('"$1"', 0, \%oldsigaction);
-    exit ($oldsigaction{"HANDLER"} eq "IGNORE" ? 0 : 77);
+  if $PERL -Mstrict -Mwarnings=FATAL,all -MPOSIX -Mconstant=SN,"$1" -e '
+    my $new = POSIX::SigAction->new(sub {});
+    my $old = POSIX::SigAction->new();
+    { no warnings quninitialized; sigaction(SN, $new, $old) }
+    my $oldhandler;
+    if ($old->can(qhandler)) { $oldhandler = $old->handler }
+    else { $oldhandler = $old->{HANDLER} }
+    exit ($oldhandler eq "IGNORE" ? 0 : 77);
   '; then
     return 0
   elif test $? -eq 77; then
@@ -187,7 +188,7 @@
   am__make_redirect_stdall=no
   am__make_flags=
   am__make_rc_exp=0
-  # Follow-up code might want to analyse this, so mark is as
+  # Follow-up code might want to analyze this, so mark it as
   # publicly accessible (no double undesrscore).
   am_make_rc=0
   # Parse options for this function.
@@ -424,7 +425,7 @@
       fatal_ "invalid value for \$am__using_gmake: '$am__using_gmake'";;
   esac
 }
-am__using_gmake="" # Avoid interferences from the environment.
+am__using_gmake="" # Avoid interference from the environment.
 
 # make_can_chain_suffix_rules
 # ---------------------------
@@ -460,7 +461,7 @@
       *) fatal_ "make_can_chain_suffix_rules: internal error";;
   esac
 }
-am__can_chain_suffix_rules="" # Avoid interferences from the environment.
+am__can_chain_suffix_rules="" # Avoid interference from the environment.
 
 # useless_vpath_rebuild
 # ---------------------
@@ -634,6 +635,10 @@
     am_pep3147_tag=$($PYTHON -c 'import imp; print(imp.get_tag())') \
       || am_pep3147_tag=none
   fi
+  if test "$am_pep3147_tag" = "none"; then
+    am_pep3147_tag=$($PYTHON -c 'import sys; print(sys.implementation.cache_tag)') \
+      || am_pep3147_tag=none
+  fi
   test $am_pep3147_tag != none
 }
 am_pep3147_tag=
@@ -1057,7 +1062,7 @@
 
 am_extra_info ()
 {
-  echo "Running from installcheck: $am_running_installcheck"
-  echo "Test Protocol: $am_test_protocol"
-  echo "PATH = $PATH"
+  echo "am-test-lib.sh: Running from installcheck: $am_running_installcheck"
+  echo "am-test-lib.sh: Test Protocol: $am_test_protocol"
+  echo "am-test-lib.sh: PATH = $PATH"
 }

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/cc-no-c-o.in -> _service:tar_scm:automake-1.17.tar.xz/t/ax/cc-no-c-o.in Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/deltree.pl -> _service:tar_scm:automake-1.17.tar.xz/t/ax/deltree.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/depcomp.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/depcomp.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2012-2021 Free Software Foundation, Inc.
+# Copyright (C) 2012-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -14,7 +14,7 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
-# Check dependency tracking in various flavours.
+# Check dependency tracking in various flavors.
 # Contains both libtool and non-libtool case.
 # Sourced by the various (autogenerated) 'depcomp*.tap' tests.
 # Examples of reported failures that motivated those test are
@@ -160,7 +160,7 @@
     echo lib_LTLIBRARIES = libfoo.la >> Makefile.am
     make_ok ()
     {
-      run_make -M -- ${1+"$@"}
+      run_make -M -- ${1+"$@"} || return 1
       $FGREP 'unknown directive' output && return 1
       rm -f output
       # Checks for stray files possibly left around by less common
@@ -243,6 +243,8 @@
 #include <stdio.h>
 extern int subfoo (void);
 END
+# Save subfoo.h so we can restore it below; see #60962.
+cp sub/subfoo.h sub/subfoo.save
 
 cat > src/baz.c <<'END'
 #include "baz.h"
@@ -399,8 +401,7 @@
       && rewrite "$srcdir"/sub/subfoo.h echo 'choke me' \
       && not $MAKE \
       && delete "$srcdir"/sub/subfoo.h \
-      && edit "$srcdir"/sub/subfoo.c -e 1d \
-      && edit "$srcdir"/foo.h -e 2d \
+      && cp "$srcdir"/sub/subfoo.save "$srcdir"/sub/subfoo.h \
       && make_ok \
       || r='not ok'
     result_ "$r" "$pfx dependency tracking works"

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/distcheck-hook-m4.am -> _service:tar_scm:automake-1.17.tar.xz/t/ax/distcheck-hook-m4.am Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/extract-testsuite-summary.pl -> _service:tar_scm:automake-1.17.tar.xz/t/ax/extract-testsuite-summary.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/is -> _service:tar_scm:automake-1.17.tar.xz/t/ax/is Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/is_newest -> _service:tar_scm:automake-1.17.tar.xz/t/ax/is_newest Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/runtest.in -> _service:tar_scm:automake-1.17.tar.xz/t/ax/runtest.in Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/shell-no-trail-bslash.in -> _service:tar_scm:automake-1.17.tar.xz/t/ax/shell-no-trail-bslash.in Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/tap-functions.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/tap-functions.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/tap-setup.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/tap-setup.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/tap-summary-aux.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/tap-summary-aux.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/test-defs.in -> _service:tar_scm:automake-1.17.tar.xz/t/ax/test-defs.in Changed

@@ -1,7 +1,7 @@
 # -*- shell-script -*-
 # @configure_input@
 #
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -23,8 +23,7 @@
 #   - This code has to be 'set -e' clean.
 
 # See whether the current test script is expected to use TAP or not.
-# Use a sensible default, while allowing the scripts to override this
-# check.
+# Use a sensible default, while allowing the scripts to override this check.
 if test -z "$am_test_protocol"; then
   case $argv0 in
     *.tap) am_test_protocol=tap;;
@@ -64,7 +63,7 @@
     am_system_acdir=""
     ;;
   *)
-    echo "$me: variable 'am_running_installcheck' has invalid"
+    echo "$me: variable 'am_running_installcheck' has invalid" \
          "value '$am_running_installcheck'" >&2
     exit 99
     ;;
@@ -172,17 +171,82 @@
 GNU_GCJ=${AM_TESTSUITE_GNU_GCJ-${GNU_GCJ-'@GNU_GCJ@'}}
 GNU_GCJFLAGS=${AM_TESTSUITE_GNU_GCJFLAGS-${GNU_GCJFLAGS-'@GNU_GCJFLAGS@'}}
 
-# No all versions of Tex support '--version', so we use a configure
+# Not all versions of Tex support '--version', so we use a configure
 # check to decide if tex is available.  This decision is embodied in
 # this variable.
 TEX=${AM_TESTSUITE_TEX-'@TEX@'}
 
-# The amount we should wait after modifying files depends on the platform.
-# For instance, Windows '95, '98 and ME have 2-second granularity
-# and can be up to 3 seconds in the future w.r.t. the system clock.
-# The creative quoting is to avoid spuriously triggering a failure in
-# the maintainer checks,
-sleep='sleep ''@MODIFICATION_DELAY@'
+# The time we should wait after modifying files depends on the platform, and
+# also the capabilities of the 'automake' and 'autom4te' programs, which in
+# turn depend on the capabilities of the Perl interpreter.  configure has
+# detected the platform's resolution for file modification times; we still
+# need to check automake and autom4te.
+MTIME_RESOLUTION='@MTIME_RESOLUTION@'
+case $MTIME_RESOLUTION in
+  1 | 2) ;; # Can assume these values are usable as is.
+  *)
+    if $AUTOMAKE --version 2>&1 |
+         grep 'Features:.*subsecond-mtime' > /dev/null 2>&1 &&
+       $AUTOM4TE --version 2>&1 |
+         grep 'Features:.*subsecond-mtime' > /dev/null 2>&1; then
+      # subsecond-mtime should be supported; use the timestamp
+      # resolution that we determined.
+      if test -n "$am_cv_filesystem_timestamp_resolution"; then
+        #echo "$BASH_SOURCE: amftr=$am_cv_filesystem_timestamp_resolution" >&2
+        MTIME_RESOLUTION=$am_cv_filesystem_timestamp_resolution
+        
+      elif test -n "$MTIME_RESOLUTION"; then
+        #echo "$BASH_SOURCE: M_R=$MTIME_RESOLUTION" >&2
+        # This is normal when running tests: the cache variable is
+        # not set, but MTIME_RESOLUTION is, because config.status is sourced.
+        # Its value should be usable, but because this was discovered
+        # just before the 1.17 release, for safety, let's set it to 1,
+        # and try it after the release.
+        MTIME_RESOLUTION=1
+
+      # If MTIME_RESOLUTION is empty too, that's weird.
+      else
+        # This message ends up in test-suite.log.
+        echo "$me: subsecond-mtime supported per automake and auto4mte" \
+             "--version, but neither am_cv_filesystem_timestamp_resolution;" \
+             "nor MTIME_RESOLUTION are set; that's an error somewhere." \
+             "Proceeding with value 1." >&2
+        MTIME_RESOLUTION=1
+      fi
+    else
+      #echo "$BASH_SOURCE: some --version doesn't support subsecond-mtime" >&2
+      #$AUTOMAKE --version >&2
+      #$AUTOM4TE --version >&2
+      #
+      MTIME_RESOLUTION=1
+      #
+      # we must not sleep for fractional seconds when autom4te does not
+      # support subsecond-mtimes, even when sleep supports it. See bug#67670.
+      am_cv_sleep_fractional_seconds=no
+      export am_cv_sleep_fractional_seconds
+    fi
+  ;;
+esac
+
+# This sleep variable is used explicitly in tests when AC_OUTPUT is not
+# used, hence config.status is not created, hence AC_CONFIG_COMMANDS_*
+# is not evaluated. Originally set up here:
+#   https://lists.gnu.org/archive/html/bug-automake/2010-10/msg00000.html
+# Discovered again in this review of the "sleep" history:
+#   https://lists.gnu.org/archive/html/automake/2024-06/msg00054.html
+# It seems a better fix would be to have Automake (in sanity.m4) figure
+# out the need for sleep even when AC_OUTPUT is not used.
+# 
+# In general, the problem is when the mtime resolution is 1 second (or
+# more) and the configure file is created less than 1 second ago, which
+# happens routinely in the tests, and for many fast-enough configure
+# scripts in other packages, too.
+# 
+# At any rate, with this set to "sleep 1", there were still random
+# parallelization failures; setting am_cv_sleep_fractional_seconds=no
+# as above was still needed.
+#
+sleep="sleep $MTIME_RESOLUTION"
 
 # An old timestamp that can be given to a file, in "touch -t" format.
 # The time stamp should be portable to all file systems of interest.
@@ -190,9 +254,23 @@
 # in UTC; see <https://www.gnu.org/gnu/initial-announcement.html>.
 old_timestamp=198309271735.59
 
+# We need this in multiple tests and the wording is subject to change.
+# Don't include the ${br} lines since br is not defined at this point.
+#
+failure_footer_text="\
+See ./test-suite.log for debugging.
+Some test(s) failed.  Please report this to bug-automake@gnu.org,
+together with the test-suite.log file (gzipped) and your system
+information.  Thanks."
+#
+# And with color.
+red='&#x1b;0;31m'
+std='&#x1b;m';
+failure_footer_text_colorized="`echo \"$failure_footer_text\" | sed -e "s/^/${red}/" -e s/'$'/"${std}"/`"
+
 # Make our wrapper script (or installed scripts, if running under
-# "installcheck") accessible by default.  And avoid to uselessly
-# extend $PATH multiple times if this file is sourced multiple times.
+# "installcheck") accessible by default.  And avoid uselessly
+# extending $PATH multiple times if this file is sourced multiple times.
 case $PATH in
   $am_bindir$PATH_SEPARATOR*) ;;
   *) PATH=$am_bindir$PATH_SEPARATOR$PATH;;

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/test-init.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/test-init.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/test-lib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/test-lib.sh Changed

@@ -1,6 +1,6 @@
 # -*- shell-script -*-
 #
-# Copyright (C) 1996-2021 Free Software Foundation, Inc.
+# Copyright (C) 1996-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -35,7 +35,7 @@
   NULLCMD=:
   setopt NO_GLOB_SUBST
   # If Zsh is not started directly in POSIX-compatibility mode, it has some
-  # incompatibilities in the handling of $0 that conflict with our usage;
+  # incompatibility in the handling of $0 that conflict with our usage;
   # i.e., $0 inside a file sourced with the '.' builtin is temporarily set
   # to the name of the sourced file.  Work around that.
   # Note that a bug in some versions of Zsh prevents us from resetting $0
@@ -95,7 +95,7 @@
   # Extra escaping to ensure we do not call our 'exit' alias.
   (\exit $1); \exit $1
 }
-# Avoid interferences from the environment
+# Avoid interference from the environment
 am__test_skipped=no
 # This alias must actually be placed before any use if 'exit' -- even
 # just inside a function definition.  Weird, but real.
@@ -249,7 +249,7 @@
   fi
   sed "$sed_unindent_prog" ${1+"$@"}
 }
-sed_unindent_prog="" # Avoid interferences from the environment.
+sed_unindent_prog="" # Avoid interference from the environment.
 
 ## ---------------------------------------------------------------- ##
 ##  Create and set up of the temporary directory used by the test.  ##
@@ -271,7 +271,7 @@
   else
     # This is to ensure that a test script does give a SKIP outcome just
     # because a command in it happens to exit with status 77.  This
-    # behaviour, while from time to time useful to developers, is not
+    # behavior, while from time to time useful to developers, is not
     # meant to be enabled by default, as it could cause spurious failures
     # in the wild.  Thus it will be enabled only when the variable
     # 'am_explicit_skips' is set to a "true" value.
@@ -305,7 +305,7 @@
   #  - /bin/ksh and /usr/xpg4/bin/sh on Solaris 10
   #  - Bash 3.2.51 on Solaris 10 and bash 4.1.5 on Debian GNU/Linux
   #  - AT&T ksh on Debian Gnu/Linux (deb package ksh, version 93u-1)
-  # OTOH, at least these shells that do *not* exhibit that behaviour:
+  # OTOH, at least these shells that do *not* exhibit that behavior:
   #  - modern version of the Almquist Shell (at least 0.5.5.1), on
   #    both Solaris and GNU/Linux
   #  - public domain Korn Shell, version 5.2.14, on Debian GNU/Linux

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/testsuite-summary-checks.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ax/testsuite-summary-checks.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ax/trivial-test-driver -> _service:tar_scm:automake-1.17.tar.xz/t/ax/trivial-test-driver Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/backcompat-acout.sh -> _service:tar_scm:automake-1.17.tar.xz/t/backcompat-acout.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/backcompat.sh -> _service:tar_scm:automake-1.17.tar.xz/t/backcompat.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/backcompat2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/backcompat2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/backcompat3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/backcompat3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/backcompat6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/backcompat6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/backslash-before-trailing-whitespace.sh -> _service:tar_scm:automake-1.17.tar.xz/t/backslash-before-trailing-whitespace.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/backslash-issues.sh -> _service:tar_scm:automake-1.17.tar.xz/t/backslash-issues.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/badline.sh -> _service:tar_scm:automake-1.17.tar.xz/t/badline.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/badopt.sh -> _service:tar_scm:automake-1.17.tar.xz/t/badopt.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/badprog.sh -> _service:tar_scm:automake-1.17.tar.xz/t/badprog.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/built-sources-check.sh -> _service:tar_scm:automake-1.17.tar.xz/t/built-sources-check.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/built-sources-cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/built-sources-cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/built-sources-fork-bomb.sh -> _service:tar_scm:automake-1.17.tar.xz/t/built-sources-fork-bomb.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/built-sources-install-exec.sh -> _service:tar_scm:automake-1.17.tar.xz/t/built-sources-install-exec.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/built-sources-install.sh -> _service:tar_scm:automake-1.17.tar.xz/t/built-sources-install.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/built-sources-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/built-sources-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/built-sources.sh -> _service:tar_scm:automake-1.17.tar.xz/t/built-sources.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/c-demo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/c-demo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/candist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/candist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon-name.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon-name.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/canon8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/canon8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ccnoco-deps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ccnoco-deps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ccnoco-lib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ccnoco-lib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ccnoco-lt.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ccnoco-lt.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ccnoco.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ccnoco.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ccnoco3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ccnoco3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ccnoco4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ccnoco4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check-concurrency-bug9245.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check-concurrency-bug9245.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check-exported-srcdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check-exported-srcdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check-fd-redirect.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check-fd-redirect.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check-no-test-driver.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check-no-test-driver.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check-subst-prog.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check-subst-prog.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check-subst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check-subst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check-tests-in-builddir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check-tests-in-builddir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check11.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check11.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check12.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check12.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/check8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/check8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/checkall.sh -> _service:tar_scm:automake-1.17.tar.xz/t/checkall.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/clean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/clean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colneq.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colneq.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colneq2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colneq2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colneq3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colneq3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colon.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colon.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colon2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colon2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colon3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colon3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colon4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colon4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colon5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colon5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colon6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colon6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/colon7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/colon7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/color-tests-opt.sh -> _service:tar_scm:automake-1.17.tar.xz/t/color-tests-opt.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/color-tests.sh -> _service:tar_scm:automake-1.17.tar.xz/t/color-tests.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/color-tests2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/color-tests2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/commen10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/commen10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/commen11.sh -> _service:tar_scm:automake-1.17.tar.xz/t/commen11.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment-block.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment-block.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/comment12.sh Added

@@ -0,0 +1,44 @@
+#! /bin/sh
+# Copyright (C) 2022-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Make sure that earlier comments are consumed when appending to it.
+
+. test-init.sh
+
+cat > Makefile.am << 'END'
+VAR1=# eat this comment
+VAR2 =# eat this comment
+VAR3 = # eat this comment
+VAR4 =	# eat this comment
+VAR5 = val# eat this comment
+VAR6 = val # eat this comment
+
+VAR1 += val
+VAR2 += val
+VAR3 += val
+VAR4 += val
+VAR5 +=
+VAR6 +=
+END
+
+$ACLOCAL
+$AUTOMAKE
+
+# For debugging.
+grep '^VAR' Makefile.in
+
+count=$(grep '^VAR. = val$' Makefile.in | wc -l)
+ $count -eq 6

_service:tar_scm:automake-1.16.5.tar.xz/t/comment2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/comment9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comment9.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/comments-escaped-in-var.sh Added

@@ -0,0 +1,50 @@
+#! /bin/sh
+# Copyright (C) 2022-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Make sure Automake preserves escaped comments in the output.
+
+. test-init.sh
+
+cat >> configure.ac <<'END'
+AC_OUTPUT
+END
+
+cat > Makefile.am << 'END'
+# This value should be preserved.
+var = -DVAL='"\#xxx\#"'   # this should be stripped
+var += -DX=1  # this should be kept
+END
+
+$ACLOCAL
+
+# This should fail due to -Werror, as in:
+#   automake-1.16: warnings are treated as errors
+#   Makefile.am:2: warning: escaping \# comment markers is not portable
+AUTOMAKE_fails
+grep 'escaping.*comment markers.*portable' stderr
+
+# This should pass though.
+$AUTOMAKE -Wno-portability
+
+# For debugging.
+grep ^var Makefile.in
+
+# The full flag should be retained.
+grep '^var.*\\#xxx\\#.*DX=1' Makefile.in
+
+# Only the 2nd comment should be retained.
+grep '^var.*stripped' Makefile.in && exit 1 || :
+grep '^var.*should be kept' Makefile.in

_service:tar_scm:automake-1.16.5.tar.xz/t/comments-in-var-def.sh -> _service:tar_scm:automake-1.17.tar.xz/t/comments-in-var-def.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile_f90_c_cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile_f90_c_cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/compile_f_c_cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/compile_f_c_cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond11.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond11.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond13.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond13.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond14.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond14.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond15.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond15.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond16.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond16.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond17.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond17.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond18.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond18.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond19.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond19.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond20.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond20.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond21.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond21.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond22.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond22.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond23.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond23.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond24.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond24.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond25.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond25.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond26.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond26.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond27.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond27.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond28.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond28.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond30.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond30.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond31.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond31.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond32.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond32.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond33.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond33.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond34.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond34.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond35.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond35.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond36.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond36.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond37.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond37.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond38.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond38.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond39.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond39.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond40.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond40.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond41.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond41.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond42.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond42.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond43.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond43.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond44.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond44.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond45.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond45.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond46.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond46.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cond9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cond9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condd.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condd.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condhook.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condhook.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condhook2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condhook2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condinc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condinc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condinc2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condinc2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condlib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condlib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condman2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condman2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/condman3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/condman3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confdeps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confdeps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/conff.sh -> _service:tar_scm:automake-1.17.tar.xz/t/conff.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/conff2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/conff2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/conffile-leading-dot.sh -> _service:tar_scm:automake-1.17.tar.xz/t/conffile-leading-dot.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confh-subdir-clean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confh-subdir-clean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confh.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confh.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confh4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confh4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confh5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confh5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confh6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confh6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confh7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confh7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confh8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confh8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/configure.sh -> _service:tar_scm:automake-1.17.tar.xz/t/configure.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confincl.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confincl.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/conflnk.sh -> _service:tar_scm:automake-1.17.tar.xz/t/conflnk.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/conflnk2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/conflnk2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/conflnk3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/conflnk3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/conflnk4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/conflnk4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confsub.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confsub.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confvar.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confvar.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/confvar2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/confvar2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/copy.sh -> _service:tar_scm:automake-1.17.tar.xz/t/copy.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cscope.tap -> _service:tar_scm:automake-1.17.tar.xz/t/cscope.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cscope2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cscope2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cscope3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cscope3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxx-demo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxx-demo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxx-lt-demo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxx-lt-demo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxx2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxx2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxxcpp.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxxcpp.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxxlibobj.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxxlibobj.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxxlink.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxxlink.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cxxnoc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cxxnoc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cygnus-no-more.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cygnus-no-more.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/cygwin32.sh -> _service:tar_scm:automake-1.17.tar.xz/t/cygwin32.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dash.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dash.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/defun.sh -> _service:tar_scm:automake-1.17.tar.xz/t/defun.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/defun2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/defun2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu-absolute-builddir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu-absolute-builddir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu-relative-srcdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu-relative-srcdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu-siteexp-append.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu-siteexp-append.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu-siteexp-extend.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu-siteexp-extend.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu-siteexp-useredit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu-siteexp-useredit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dejagnu7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dejagnu7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/deleted-am.sh -> _service:tar_scm:automake-1.17.tar.xz/t/deleted-am.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/deleted-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/deleted-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depacl2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depacl2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depcomp-implicit-auxdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depcomp-implicit-auxdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depcomp.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depcomp.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depcomp2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depcomp2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depcomp8a.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depcomp8a.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depcomp8b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depcomp8b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depdist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depdist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depend-postproc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depend-postproc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depend.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depend.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depend3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depend3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depend4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depend4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depend5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depend5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/depend6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/depend6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/deprecated-acinit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/deprecated-acinit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/destdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/destdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dir-named-obj-is-bad.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dir-named-obj-is-bad.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/discover.sh -> _service:tar_scm:automake-1.17.tar.xz/t/discover.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-auxdir-many-subdirs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-auxdir-many-subdirs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-auxfile-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-auxfile-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-auxfile.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-auxfile.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-formats.tap -> _service:tar_scm:automake-1.17.tar.xz/t/dist-formats.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-included-parent-dir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-included-parent-dir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-install-sh.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-install-sh.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-lzma.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-lzma.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-missing-am.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-missing-am.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-missing-included-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-missing-included-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-missing-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-missing-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-no-built-sources.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-no-built-sources.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2021 Free Software Foundation, Inc.
+# Copyright (C) 2021-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -58,8 +58,9 @@
   # In any case, the tarball should contain y.c, but not x.c.
   # The tarball is always named based on $0, regardless of our options.
   pkg_ver=$me-1.0
-  ! tar tf "${pkg_ver}".tar.gz "${pkg_ver}"/x.c
-  tar tf "${pkg_ver}".tar.gz "${pkg_ver}"/y.c
+  gzip -d "${pkg_ver}".tar.gz
+  ! tar tf "${pkg_ver}".tar "${pkg_ver}"/x.c
+  tar tf "${pkg_ver}".tar "${pkg_ver}"/y.c
 
   # And x.c should have been built only for the built-sources version.
   if test "$testopt" = no-built-sources; then
@@ -69,4 +70,8 @@
     # built-sources build should have it
     test -e x.c
   fi
+
+  # If the test runs fast enough, the make dist second time through
+  # won't do anything since the tarball will be considered up to date.
+  rm -f "${pkg_ver}".tar.gz "${pkg_ver}".tar
 done

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-pr109765.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-pr109765.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-readonly.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-readonly.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-repeated.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-repeated.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-shar.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-shar.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-tarZ.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-tarZ.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-vs-built-sources.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-vs-built-sources.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dist-with-unreadable-makefile-fails.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dist-with-unreadable-makefile-fails.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-configure-flags-am.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-configure-flags-am.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-configure-flags-subpkg.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-configure-flags-subpkg.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-configure-flags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-configure-flags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-hook.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-hook.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-hook2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-hook2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-missing-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-missing-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-no-prefix-or-srcdir-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-no-prefix-or-srcdir-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-outdated-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-outdated-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-override-dvi.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-override-dvi.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-override-infodir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-override-infodir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-pr10470.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-pr10470.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-pr18286.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-pr18286.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-pr9579.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-pr9579.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcheck-writable-srcdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcheck-writable-srcdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcleancheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcleancheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcom-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcom-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcom2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcom2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcom3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcom3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcom4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcom4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distcom5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distcom5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/disthook.sh -> _service:tar_scm:automake-1.17.tar.xz/t/disthook.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distlinks.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distlinks.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distlinksbrk.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distlinksbrk.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/distname.sh -> _service:tar_scm:automake-1.17.tar.xz/t/distname.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dmalloc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dmalloc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/doc-parsing-buglets-colneq-subst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/doc-parsing-buglets-colneq-subst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/doc-parsing-buglets-tabs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/doc-parsing-buglets-tabs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dollar.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dollar.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dollarvar.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dollarvar.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dollarvar2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dollarvar2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/double.sh -> _service:tar_scm:automake-1.17.tar.xz/t/double.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/dup2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/dup2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/else.sh -> _service:tar_scm:automake-1.17.tar.xz/t/else.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/empty-data-primary.sh -> _service:tar_scm:automake-1.17.tar.xz/t/empty-data-primary.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/empty-sources-primary.tap -> _service:tar_scm:automake-1.17.tar.xz/t/empty-sources-primary.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/exdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/exdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/exdir2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/exdir2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/exdir3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/exdir3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/exeext.sh -> _service:tar_scm:automake-1.17.tar.xz/t/exeext.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/exeext2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/exeext2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/exeext3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/exeext3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/exeext4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/exeext4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ext.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ext.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ext2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ext2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ext3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ext3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-data.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-data.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-deps-lt.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-deps-lt.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-deps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-deps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-dist-dirs-and-subdirs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-dist-dirs-and-subdirs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-dist-vpath-dir-merge.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-dist-vpath-dir-merge.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-dist-vpath-dir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-dist-vpath-dir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-dist-wildcards-gnu.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-dist-wildcards-gnu.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-dist-wildcards-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-dist-wildcards-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-dist-wildcards.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-dist-wildcards.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-portability.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-portability.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-portability2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-portability2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-portability3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-portability3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-programs-and-libs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-programs-and-libs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-programs-empty.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-programs-empty.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-programs-misc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-programs-misc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-sources-no-spurious.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-sources-no-spurious.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra-sources.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra-sources.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/extra.sh -> _service:tar_scm:automake-1.17.tar.xz/t/extra.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/f90only.sh -> _service:tar_scm:automake-1.17.tar.xz/t/f90only.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/flavor.sh -> _service:tar_scm:automake-1.17.tar.xz/t/flavor.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/flibs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/flibs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fn99.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fn99.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fn99subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fn99subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fnoc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fnoc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fonly.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fonly.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/forcemiss.sh -> _service:tar_scm:automake-1.17.tar.xz/t/forcemiss.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/forcemiss2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/forcemiss2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fort1.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fort1.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fort2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fort2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fort4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fort4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fort5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fort5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/fortdep.sh -> _service:tar_scm:automake-1.17.tar.xz/t/fortdep.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gcj.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gcj.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gcj2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gcj2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gcj3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gcj3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gcj4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gcj4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gcj5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gcj5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gcj6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gcj6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/get-sysconf.sh -> _service:tar_scm:automake-1.17.tar.xz/t/get-sysconf.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -25,7 +25,7 @@
 st=0
 if test -d "$am_top_srcdir"/.git; then
   # We are running from a git checkout.
-  (cd "$am_top_srcdir" && git log -1) || st=1
+  (cd "$am_top_srcdir" && git --no-pager log -1) || st=1
 elif test -f "$am_top_srcdir"/ChangeLog; then
   # We are probably running from a distribution tarball.
   awk '
@@ -46,13 +46,20 @@
 # happen with older perl installation, or on MinGW/MSYS.
 $PERL -e 'use TAP::Parser; print $TAP::Parser::VERSION, "\n"' || :
 
+$AUTOCONF --version
+$AUTOCONF --help
+
+# It's OK if libtool is missing, as the relevant tests skip.
+libtoolize --version || :
+libtoolize --help || :
+
 # It's OK if the selected Lex and Yacc programs don't know how to print
 # the version number or the help screen; those are usually available only
 # for Flex and Bison.
-$LEX --version || :
-$LEX --help || :
-$YACC --version || :
-$YACC --help || :
+$LEX --version </dev/null || :
+$LEX --help </dev/null || :
+$YACC --version </dev/null || :
+$YACC --help </dev/null || :
 
 cat "$am_top_builddir/config.log" || st=1
 cat "$am_top_builddir/bin/aclocal-$APIVERSION" || st=1

_service:tar_scm:automake-1.16.5.tar.xz/t/gettext-basics.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gettext-basics.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2002-2021 Free Software Foundation, Inc.
+# Copyright (C) 2002-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -20,7 +20,7 @@
 . test-init.sh
 
 cat >> configure.ac << 'END'
-AM_GNU_GETTEXT
+AM_GNU_GETTEXT(external)
 AC_OUTPUT
 END
 
@@ -31,28 +31,23 @@
 $ACLOCAL
 $AUTOCONF
 
-# po/ and intl/ are required.
+# po/ is required.  intl/ may not be used with external gettext.
+# Internal (bundled) was deprecated upstream in gettext 0.18 (2010)
+# and made fatal in gettext 0.20 (2019).
 
 AUTOMAKE_fails --add-missing
 grep 'AM_GNU_GETTEXT.*SUBDIRS' stderr
 
 echo 'SUBDIRS = po' >Makefile.am
-AUTOMAKE_fails --add-missing
-grep 'AM_GNU_GETTEXT.*intl' stderr
+# Should not fail.
+$AUTOMAKE --add-missing
 
 echo 'SUBDIRS = intl' >Makefile.am
 AUTOMAKE_fails --add-missing
 grep 'AM_GNU_GETTEXT.*po' stderr
 
-# Ok.
-
 echo 'SUBDIRS = po intl' >Makefile.am
-$AUTOMAKE --add-missing
-
-# Make sure distcheck runs './configure --with-included-gettext'.
-./configure
-echo distdir: > po/Makefile
-echo distdir: > intl/Makefile
-$MAKE -n distcheck | grep '.*--with-included-gettext'
+AUTOMAKE_fails --add-missing
+grep 'intl.*SUBDIRS.*AM_GNU_GETTEXT' stderr
 
 :

_service:tar_scm:automake-1.16.5.tar.xz/t/gettext-config-rpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gettext-config-rpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gettext-external-pr338.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gettext-external-pr338.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gettext-intl-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gettext-intl-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gettext-macros.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gettext-macros.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gettext-pr381.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gettext-pr381.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gnits.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gnits.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gnits2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gnits2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gnits3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gnits3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gnumake.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gnumake.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gnuwarn.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gnuwarn.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/gnuwarn2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/gnuwarn2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/hdr-vars-defined-once.sh -> _service:tar_scm:automake-1.17.tar.xz/t/hdr-vars-defined-once.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/header.sh -> _service:tar_scm:automake-1.17.tar.xz/t/header.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-depend.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-depend.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-depend2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-depend2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-dmalloc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-dmalloc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-init.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-init.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-lispdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-lispdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-python.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-python.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-silent.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-silent.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help-upc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help-upc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/help4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/help4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/hfs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/hfs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/implicit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/implicit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/init.sh -> _service:tar_scm:automake-1.17.tar.xz/t/init.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/init2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/init2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/install-info-dir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/install-info-dir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/install-sh-option-C.sh -> _service:tar_scm:automake-1.17.tar.xz/t/install-sh-option-C.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/install-sh-option-S.sh -> _service:tar_scm:automake-1.17.tar.xz/t/install-sh-option-S.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/install-sh-unittests.sh -> _service:tar_scm:automake-1.17.tar.xz/t/install-sh-unittests.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/installdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/installdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdat.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdat.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdat2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdat2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-cond2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-cond2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-java.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-java.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-lisp.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-lisp.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-ltlib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-ltlib.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2009-2021 Free Software Foundation, Inc.
+# Copyright (C) 2009-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -15,12 +15,20 @@
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 # If $(libdir) or $(pyexecdir) is the empty string, then nothing should
-# be installed there.
-# This test exercises the libtool code paths.
+# be installed there, and in fact libtool will refuse to link due to the
+# missing argument for -rpath:
+#   /bin/sh ./libtool ... -rpath  libfoo.lo  
+#   libtool:   error: only absolute run-paths are allowed
+# (Hopefully the error message will be improved.)
+# Thus this test is expected to fail.
+# 
+# This test exercises some of the libtool code paths.
 
 required='cc libtoolize'
 . test-init.sh
 
+# Although LT_INIT is preferred nowadays, keep using AC_PROG_LIBTOOL
+# to help make sure it's still supported.
 cat >>configure.ac <<'END'
 AC_PROG_CC
 AM_PROG_AR
@@ -35,9 +43,9 @@
 AUTOMAKE_OPTIONS = subdir-objects
 bin_PROGRAMS = p
 nobase_bin_PROGRAMS = np sub/np
-lib_LTIBRARIES = libfoo.la
+lib_LTLIBRARIES = libfoo.la
 nobase_lib_LTLIBRARIES = libnfoo.la sub/libnfoo.la
-pyexec_LTIBRARIES = libpy.la
+pyexec_LTLIBRARIES = libpy.la
 nobase_pyexec_LTLIBRARIES = libnpy.la sub/libnpy.la
 END

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-no-empty.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-no-empty.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-prog.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-prog.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-python.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-python.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir-texi.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir-texi.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instdir2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instdir2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instexec.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instexec.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instfail-info.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instfail-info.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instfail-java.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instfail-java.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instfail-libtool.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instfail-libtool.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instfail.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instfail.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/insthook.sh -> _service:tar_scm:automake-1.17.tar.xz/t/insthook.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instman.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instman.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instman2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instman2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instmany-mans.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instmany-mans.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instmany-python.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instmany-python.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instmany.sh -> _service:tar_scm:automake-1.17.tar.xz/t/instmany.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/instspc.tap -> _service:tar_scm:automake-1.17.tar.xz/t/instspc.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/interp.sh -> _service:tar_scm:automake-1.17.tar.xz/t/interp.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/interp2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/interp2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-check.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-check.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-clean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-clean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-compile-install.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-compile-install.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-compile-run-flat.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-compile-run-flat.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-compile-run-nested.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-compile-run-nested.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-empty-classpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-empty-classpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-extra.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-extra.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-mix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-mix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-no-duplicate.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-no-duplicate.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-nobase.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-nobase.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-noinst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-noinst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-rebuild.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-rebuild.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-sources.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-sources.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java-uninstall.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java-uninstall.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/java3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/java3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/javadir-undefined.sh -> _service:tar_scm:automake-1.17.tar.xz/t/javadir-undefined.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/javaflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/javaflags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/javaprim.sh -> _service:tar_scm:automake-1.17.tar.xz/t/javaprim.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/javasubst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/javasubst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ldadd.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ldadd.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ldflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ldflags.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/lex-args.sh Added

@@ -0,0 +1,90 @@
+#! /bin/sh
+# Copyright (C) 2023-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Autoconf 2.70 requires AC_PROG_LEX to be called with either 'yywrap'
+# or 'noyywrap' as the parameter (previously, the macro had no parameters).
+# After updating AM_PROG_LEX, check that either the required parameter values
+# are passed down to AC_PROG_LEX, the defaults are used, or a warning is
+# issued (and the default is used).
+# (parts copied from t/lex-clean.sh)
+
+required='cc lex'
+. test-init.sh
+
+expected_errmsg='AC_PROG_LEX without either yywrap or noyywrap'
+
+cp configure.ac configure.bak
+
+cat > Makefile.am << 'END'
+bin_PROGRAMS = foo
+foo_SOURCES = main.c lexer.l
+LDADD = $(LEXLIB)
+END
+
+cat > lexer.l << 'END'
+%{
+#define YY_NO_UNISTD_H 1
+%}
+%%
+"GOOD"   return EOF;
+.
+END
+
+cat > main.c << 'END'
+int main (void) { return yylex (); }
+int yywrap (void) { return 1; }
+END
+
+for failing in '' '()' '()';
+do
+	echo "============== Testing AM_PROG_LEX with >$failing<"
+
+	cat configure.bak - > configure.ac <<END
+AC_PROG_CC
+AM_PROG_LEX$failing
+AC_OUTPUT
+END
+	# debug:
+	#cat configure.ac
+
+	# aclocal seems required every time (at least, if 'make' would be run)
+	$ACLOCAL
+	# we expect the message, so missing is an error:
+	($AUTOCONF 2>&1 | grep "$expected_errmsg") \
+		|| (cat configure.ac && exit 1)
+	rm -rf autom4te*.cache
+done;
+
+for working in '(noyywrap)' '(yywrap)';
+do
+	echo "============== Testing AM_PROG_LEX with >$working<"
+
+	cat configure.bak - > configure.ac <<END
+AC_PROG_CC
+AM_PROG_LEX$working
+AC_OUTPUT
+END
+	# debug:
+	#cat configure.ac
+
+	$ACLOCAL
+	# we don't expect the message, so it is an error if found:
+	($AUTOCONF 2>&1 | grep "$expected_errmsg") \
+		&& cat configure.ac && exit 2
+	rm -rf autom4te*.cache
+done;
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-clean-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-clean-cxx.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -29,6 +29,8 @@
 END
 
 cat > Makefile.am << 'END'
+AM_LFLAGS = --never-interactive
+
 bin_PROGRAMS = foo bar baz qux
 
 foo_SOURCES = mainfoo.cc parsefoo.lxx
@@ -51,12 +53,15 @@
 LDADD = $(LEXLIB)
 END
 
+# For the explanation of the conditionals on using extern "C",
+# see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45205#13.
 cat > parsefoo.lxx << 'END'
 %{
 #define YY_DECL int yylex (void)
-extern "C" YY_DECL;
-#define YY_NO_UNISTD_H 1
-int isatty (int fd) { return 0; }
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+extern "C"
+#endif
+YY_DECL;
 %}
 %%
 "GOOD"   return EOF;
@@ -71,7 +76,10 @@
 
 cat > mainfoo.cc << 'END'
 // This file should contain valid C++ but invalid C.
-extern "C" int yylex (void);
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+extern "C"
+#endif
+int yylex (void);
 using namespace std;
 int main (int argc, char **argv)
 {

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-clean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-clean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-depend-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-depend-cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-depend-grep.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-depend-grep.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-depend.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-depend.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-header.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-header.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-lib-external.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-lib-external.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-lib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-lib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-libobj.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-libobj.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-line.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-line.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-multiple.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-multiple.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-nodist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-nodist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-noyywrap.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-noyywrap.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-pr204.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-pr204.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex-subobj-nodep.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex-subobj-nodep.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lex5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lex5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lexcpp.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lexcpp.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lexvpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lexvpath.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2010-2021 Free Software Foundation, Inc.
+# Copyright (C) 2010-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -20,7 +20,7 @@
 # 'make' and 'make distdir' and check whether the version of 'lexer.c'
 # to be distributed is up to date.
 
-# Please keep this in sync with sister test 'yaccvapth.sh'.
+# Please keep this in sync with sister test 'yaccvpath.sh'.
 
 required='cc lex'
 . test-init.sh
@@ -37,6 +37,8 @@
 END
 
 cat > Makefile.am << 'END'
+AM_LFLAGS = --never-interactive
+
 bin_PROGRAMS = foo
 foo_SOURCES = lexer.l foo.c
 LDADD = $(LEXLIB)
@@ -44,9 +46,6 @@
 
 # Original lexer, with a "foobar" comment
 cat > lexer.l << 'END'
-%{
-#define YY_NO_UNISTD_H 1
-%}
 %%
 "END" return EOF;
 .
@@ -89,9 +88,6 @@
 
 # New lexer, with 'fubar' comment.
 cat > ../lexer.l << 'END'
-%{
-#define YY_NO_UNISTD_H 1
-%}
 %%
 "END" return EOF;
 .
@@ -112,9 +108,6 @@
 
 # New lexer, with 'maude' comment.
 cat > ../lexer.l << 'END'
-%{
-#define YY_NO_UNISTD_H 1
-%}
 %%
 "END" return EOF;
 .

_service:tar_scm:automake-1.16.5.tar.xz/t/lflags-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lflags-cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lflags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libexec.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libexec.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj-no-dependency-tracking.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj-no-dependency-tracking.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj12.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj12.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj13.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj13.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj14.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj14.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj15a.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj15a.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj15b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj15b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj15c.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj15c.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj16a.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj16a.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj16b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj16b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj17.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj17.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj18.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj18.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj19.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj19.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj20a.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj20a.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj20b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj20b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj20c.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj20c.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libobj7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libobj7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/library.sh -> _service:tar_scm:automake-1.17.tar.xz/t/library.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/library2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/library2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/library3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/library3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtoo10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtoo10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtoo11.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtoo11.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool-macros.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool-macros.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/libtool9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/libtool9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/license.sh -> _service:tar_scm:automake-1.17.tar.xz/t/license.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/license2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/license2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_c_cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_c_cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_dist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_dist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_f90_only.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_f90_only.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_f_only.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_f_only.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_fc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_fc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_fccxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_fccxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_fcxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_fcxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/link_override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/link_override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp-flags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp-flags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp-loadpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp-loadpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp-pr11806.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp-pr11806.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp-readonly-srcdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp-readonly-srcdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp-subdir-mix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp-subdir-mix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp-subdir2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp-subdir2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lisp8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lisp8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/lispdry.sh -> _service:tar_scm:automake-1.17.tar.xz/t/lispdry.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/list-of-tests.mk -> _service:tar_scm:automake-1.17.tar.xz/t/list-of-tests.mk Changed

@@ -2,7 +2,7 @@
 ## testsuite.  This fragment is meant to be included by the Makefile.am,
 ## but also to be executed directly by make when bootstrapping automake.
 
-## Copyright (C) 2011-2021 Free Software Foundation, Inc.
+## Copyright (C) 2011-2024 Free Software Foundation, Inc.
 ##
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -17,7 +17,7 @@
 ## You should have received a copy of the GNU General Public License
 ## along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
-# FIXME: this "expected failures" are in truth an hack used to
+# FIXME: These "expected failures" are a kludge used to
 # FIXME: to verify that some incorrect usages of our perl libraries
 # FIXME: raise an error.  We should find a cleaner way to check that.
 perl_fake_XFAIL_TESTS = \
@@ -28,6 +28,9 @@
 t/pm/Version2.pl \
 t/pm/Version3.pl
 
+# These must be separately/redundantly included in handwritten_TESTS
+# below.  Despite the redundancy, it seems cleaner to keep
+# handwritten_TESTS as a list of all such .sh tests.
 XFAIL_TESTS = \
 t/all.sh \
 t/cond17.sh \
@@ -36,6 +39,7 @@
 t/override-conditional-pr13940.sh \
 t/dist-pr109765.sh \
 t/instdir-cond2.sh \
+t/instdir-ltlib.sh \
 t/java-nobase.sh \
 t/objext-pr10128.sh \
 t/remake-timing-bug-pr8365.sh \
@@ -160,6 +164,7 @@
 t/ar3.sh \
 t/ar4.sh \
 t/ar5.sh \
+t/ar_override.sh \
 t/asm.sh \
 t/asm2.sh \
 t/asm3.sh \
@@ -187,6 +192,7 @@
 t/auxdir-misplaced.sh \
 t/auxdir-nonexistent.sh \
 t/auxdir-pr19311.sh \
+t/auxdir-subsubdir.sh \
 t/auxdir-unportable.tap \
 t/backcompat.sh \
 t/backcompat2.sh \
@@ -264,7 +270,9 @@
 t/comment9.sh \
 t/commen10.sh \
 t/commen11.sh \
+t/comment12.sh \
 t/comment-block.sh \
+t/comments-escaped-in-var.sh \
 t/comments-in-var-def.sh \
 t/compile.sh \
 t/compile2.sh \
@@ -588,6 +596,7 @@
 t/lex5.sh \
 t/lexcpp.sh \
 t/lexvpath.sh \
+t/lex-args.sh \
 t/lex-subobj-nodep.sh \
 t/lex-header.sh \
 t/lex-lib.sh \
@@ -723,6 +732,7 @@
 t/no-extra-makefile-code.sh \
 t/no-spurious-install-recursive.sh \
 t/nobase.sh \
+t/nobase-dist.sh \
 t/nobase-libtool.sh \
 t/nobase-python.sh \
 t/nobase-nodist.sh \
@@ -809,6 +819,7 @@
 t/parallel-tests-empty-testlogs.sh \
 t/parallel-tests-driver-install.sh \
 t/parallel-tests-no-color-in-log.sh \
+t/parallel-tests-without-skipped-logs.sh \
 t/parallel-tests-no-spurious-summary.sh \
 t/parallel-tests-exit-statuses.sh \
 t/parallel-tests-console-output.sh \
@@ -867,6 +878,7 @@
 t/pluseq9.sh \
 t/pluseq10.sh \
 t/pluseq11.sh \
+t/posixtarget.sh \
 t/posixsubst-data.sh \
 t/posixsubst-extradist.sh \
 t/posixsubst-ldadd.sh \
@@ -916,6 +928,7 @@
 t/py-compile-basedir.sh \
 t/py-compile-destdir.sh \
 t/py-compile-env.sh \
+t/py-compile-files.sh \
 t/py-compile-option-terminate.sh \
 t/py-compile-usage.sh \
 t/python.sh \
@@ -932,6 +945,7 @@
 t/python-vars.sh \
 t/python-virtualenv.sh \
 t/python-pr10995.sh \
+t/ranlib_override.sh \
 t/recurs-user.sh \
 t/recurs-user2.sh \
 t/recurs-user-deeply-nested.sh \
@@ -1009,6 +1023,7 @@
 t/seenc.sh \
 t/silent-c.sh \
 t/silent-cxx.sh \
+t/silent-defaults.sh \
 t/silent-lt.sh \
 t/silent-f77.sh \
 t/silent-f90.sh \
@@ -1223,6 +1238,8 @@
 t/txinfo-no-installinfo.sh \
 t/txinfo-no-repeated-targets.sh \
 t/txinfo-no-setfilename.sh \
+t/txinfo-no-setfilename-no-inputs.sh \
+t/txinfo-no-texi-but-texi-in.sh \
 t/txinfo-other-suffixes.sh \
 t/txinfo-override-infodeps.sh \
 t/txinfo-override-texinfo-tex.sh \
@@ -1265,6 +1282,7 @@
 t/vala-recursive-setup.sh \
 t/vala-vapi.sh \
 t/vala-vpath.sh \
+t/varempty.sh \
 t/vars.sh \
 t/vars3.sh \
 t/var-recurs.sh \

_service:tar_scm:automake-1.16.5.tar.xz/t/listval.sh -> _service:tar_scm:automake-1.17.tar.xz/t/listval.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/local.mk -> _service:tar_scm:automake-1.17.tar.xz/t/local.mk Changed

@@ -1,5 +1,5 @@
 ## -*- makefile-automake -*-
-## Copyright (C) 1995-2021 Free Software Foundation, Inc.
+## Copyright (C) 1995-2024 Free Software Foundation, Inc.
 ##
 ## This program is free software; you can redistribute it and/or modify
 ## it under the terms of the GNU General Public License as published by
@@ -42,6 +42,11 @@
 # Keep this in sync with the similar list in ax/runtest.in.
 AM_TESTS_ENVIRONMENT = \
   for v in \
+    ACLOCAL \
+    AUTOCONF \
+    AUTOHEADER \
+    AUTOMAKE \
+    AUTOUPDATE \
     required \
     am_test_protocol \
     am_serial_tests \
@@ -51,7 +56,7 @@
     am_test_lib_sourced \
     test_lib_sourced \
   ; do \
-    eval test x"\$${$$v}" = x || unset $$v; \
+    eval test x\"\$${$$v}\" = x || unset $$v; \
   done;
 # We want warning messages and explanations for skipped tests to go to
 # the console if possible, so set up 'stderr_fileno_' properly.
@@ -166,7 +171,7 @@
 
 # If two test scripts have the same basename, they will end up sharing
 # the same log file, leading to all sort of undefined and undesired
-# behaviours.
+# behaviors.
 check-no-repeated-test-name:
 	@LC_ALL=C; export LC_ALL; \
 	 lst='$(TEST_LOGS)'; for log in $$lst; do echo $$log; done \
@@ -273,6 +278,7 @@
 clean-local: clean-local-check
 .PHONY: clean-local-check
 clean-local-check:
+	find . -type d ! -perm -700 -exec chmod u+rwx {} ';'
 	$(AM_V_GEN)$(PERL) $(srcdir)/t/ax/deltree.pl t/*.dir t/*/*.dir */t/*.dir
 
 # vim: ft=automake noet

_service:tar_scm:automake-1.16.5.tar.xz/t/location.sh -> _service:tar_scm:automake-1.17.tar.xz/t/location.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/longlin2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/longlin2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/longline.sh -> _service:tar_scm:automake-1.17.tar.xz/t/longline.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltcond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltcond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltcond2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltcond2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltconv.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltconv.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltdeps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltdeps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltinit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltinit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltinstloc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltinstloc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltlibobjs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltlibobjs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltlibsrc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltlibsrc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/ltorder.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ltorder.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/m4-inclusion.sh -> _service:tar_scm:automake-1.17.tar.xz/t/m4-inclusion.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/maintclean-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/maintclean-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/maintclean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/maintclean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/maintmode-configure-msg.sh -> _service:tar_scm:automake-1.17.tar.xz/t/maintmode-configure-msg.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/make-dryrun.tap -> _service:tar_scm:automake-1.17.tar.xz/t/make-dryrun.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/make-is-gnu.sh -> _service:tar_scm:automake-1.17.tar.xz/t/make-is-gnu.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/make-keepgoing.tap -> _service:tar_scm:automake-1.17.tar.xz/t/make-keepgoing.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/make.sh -> _service:tar_scm:automake-1.17.tar.xz/t/make.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/makefile-deps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/makefile-deps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/makej.sh -> _service:tar_scm:automake-1.17.tar.xz/t/makej.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/makej2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/makej2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/maken.sh -> _service:tar_scm:automake-1.17.tar.xz/t/maken.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/maken3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/maken3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/makevars.sh -> _service:tar_scm:automake-1.17.tar.xz/t/makevars.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/man.sh -> _service:tar_scm:automake-1.17.tar.xz/t/man.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/man2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/man2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/man3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/man3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/man5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/man5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/man6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/man6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/man7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/man7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/man8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/man8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mdate.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mdate.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mdate2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mdate2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mdate3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mdate3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mdate4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mdate4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mdate5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mdate5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mdate6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mdate6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/missing-auxfile-stops-makefiles-creation.sh -> _service:tar_scm:automake-1.17.tar.xz/t/missing-auxfile-stops-makefiles-creation.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/missing-version-mismatch.sh -> _service:tar_scm:automake-1.17.tar.xz/t/missing-version-mismatch.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/missing3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/missing3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mkdir_p.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mkdir_p.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mkdirp-deprecation.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mkdirp-deprecation.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mkinst2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mkinst2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mkinst3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mkinst3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mkinstall.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mkinstall.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mmode.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mmode.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/mmodely.sh -> _service:tar_scm:automake-1.17.tar.xz/t/mmodely.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/no-extra-c-stuff.sh -> _service:tar_scm:automake-1.17.tar.xz/t/no-extra-c-stuff.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/no-extra-makefile-code.sh -> _service:tar_scm:automake-1.17.tar.xz/t/no-extra-makefile-code.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/no-spurious-install-recursive.sh -> _service:tar_scm:automake-1.17.tar.xz/t/no-spurious-install-recursive.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/nobase-dist.sh Added

@@ -0,0 +1,67 @@
+#! /bin/sh
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+# Interaction of 'nobase_' and 'dist_' prefixes.
+
+. test-init.sh
+
+cat >> configure.ac <<'EOF'
+AC_OUTPUT
+EOF
+
+cat > Makefile.am <<'EOF'
+foodir = $(prefix)/foo
+
+bardir = $(prefix)/bar
+
+sub/nodist.dat:
+	$(MKDIR_P) sub
+	: > $@
+
+nobase_foo_DATA = sub/nodist.dat
+nobase_dist_foo_DATA = sub/dist.dat
+
+dist_bar_DATA = sub/base.dat
+nobase_dist_bar_DATA = sub/nobase.dat
+
+CLEANFILES = sub/nodist.dat
+EOF
+
+mkdir sub
+
+: > sub/dist.dat
+: > sub/nobase.dat
+: > sub/base.dat
+
+rm -f install-sh
+
+$ACLOCAL
+$AUTOCONF
+$AUTOMAKE -a
+./configure --prefix "$(pwd)/inst"
+
+$MAKE
+$MAKE install
+
+test -f inst/foo/sub/nodist.dat
+test -f inst/foo/sub/dist.dat
+
+test -f inst/bar/sub/nobase.dat
+test -f inst/bar/base.dat
+
+$MAKE distcheck
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/nobase-libtool.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nobase-libtool.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nobase-nodist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nobase-nodist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nobase-python.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nobase-python.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nobase.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nobase.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodef.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodef.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodef2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodef2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodep.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodep.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodep2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodep2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodepcomp.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodepcomp.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodist2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodist2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nodist3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nodist3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/noinst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/noinst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/noinstdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/noinstdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nolink.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nolink.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/nostdinc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/nostdinc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/notrans.sh -> _service:tar_scm:automake-1.17.tar.xz/t/notrans.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/number.sh -> _service:tar_scm:automake-1.17.tar.xz/t/number.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objc-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objc-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objc-deps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objc-deps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objc-flags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objc-flags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objc-megademo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objc-megademo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objc-minidemo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objc-minidemo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objcxx-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objcxx-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objcxx-deps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objcxx-deps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objcxx-flags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objcxx-flags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objcxx-minidemo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objcxx-minidemo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/objext-pr10128.sh -> _service:tar_scm:automake-1.17.tar.xz/t/objext-pr10128.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/oldvars.sh -> _service:tar_scm:automake-1.17.tar.xz/t/oldvars.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/order.sh -> _service:tar_scm:automake-1.17.tar.xz/t/order.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output-order.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output-order.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output11.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output11.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output12.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output12.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output13.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output13.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/output9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/output9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/override-conditional-1.sh -> _service:tar_scm:automake-1.17.tar.xz/t/override-conditional-1.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/override-conditional-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/override-conditional-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/override-conditional-pr13940.sh -> _service:tar_scm:automake-1.17.tar.xz/t/override-conditional-pr13940.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/override-html.sh -> _service:tar_scm:automake-1.17.tar.xz/t/override-html.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/override-suggest-local.sh -> _service:tar_scm:automake-1.17.tar.xz/t/override-suggest-local.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-am.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-am.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-am2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-am2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-am3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-am3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-basics.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-basics.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-cmdline-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-cmdline-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-concurrency-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-concurrency-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-concurrency.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-concurrency.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-console-output.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-console-output.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-driver-install.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-driver-install.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-dry-run-1.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-dry-run-1.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-dry-run-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-dry-run-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-empty-testlogs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-empty-testlogs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-empty.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-empty.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-exeext.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-exeext.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-exit-status-reported.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-exit-status-reported.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-exit-statuses.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-exit-statuses.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-extra-programs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-extra-programs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-fd-redirect-exeext.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-fd-redirect-exeext.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-fd-redirect.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-fd-redirect.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-fork-bomb.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-fork-bomb.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -39,7 +39,7 @@
 
  is_too_deep := $(shell test $(MAKELEVEL) -lt 10 && echo no)
 
-## Indenteation here required to avoid confusing Automake.
+## Indentation here required to avoid confusing Automake.
  ifeq ($(is_too_deep),no)
  else
  $(error $(errmsg), $(MAKELEVEL) levels)
@@ -48,9 +48,9 @@
 else !IS_GNU_MAKE
 
 # We use mkdir to detect the level of recursion, since it is easy
-# to use and assured to be portably atomical.  Also use an higher
+# to use and assured to be portably atomic.  Also use a higher
 # number than with GNU make above, since the level used here can
-# be incremented by tow or more per recursion.
+# be incremented by two or more per recursion.
 recursion-not-too-deep:
 	@ok=no; \
 	for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 \

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-generated-and-distributed.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-generated-and-distributed.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-harderror.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-harderror.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-interrupt.tap -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-interrupt.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-log-compiler-1.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-log-compiler-1.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-log-compiler-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-log-compiler-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-log-compiler-example.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-log-compiler-example.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-log-override-1.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-log-override-1.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-log-override-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-log-override-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-log-override-recheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-log-override-recheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-no-color-in-log.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-no-color-in-log.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-no-spurious-summary.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-no-spurious-summary.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-once.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-once.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-recheck-depends-on-all.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-recheck-depends-on-all.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-recheck-pr11791.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-recheck-pr11791.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-recheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-recheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-reset-term.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-reset-term.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-suffix-prog.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-suffix-prog.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-suffix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-suffix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-trailing-whitespace.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-trailing-whitespace.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/parallel-tests-unreadable.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-unreadable.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/parallel-tests-without-skipped-logs.sh Added

@@ -0,0 +1,62 @@
+#! /bin/sh
+# Copyright (C) 2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# If IGNORE_SKIPPED_LOGS is set, skipped tests should not be in test-suite.log.
+
+. test-init.sh
+
+cat >>configure.ac <<END
+AC_OUTPUT
+END
+
+cat >Makefile.am <<'END'
+LOG_COMPILER = $(SHELL)
+TESTS = pass fail skiptest xpass xfail error
+XFAIL_TESTS = xpass xfail
+END
+
+echo 'exit 0' > pass
+echo 'exit 0' > xpass
+echo 'exit 1' > fail
+echo 'exit 1' > xfail
+echo 'exit 77' > skiptest # unique name for grep
+echo 'exit 99' > error
+
+$ACLOCAL
+$AUTOCONF
+$AUTOMAKE --add-missing
+
+# Check that IGNORE_SKIPPED_LOGS works when given on the command line.
+
+./configure
+run_make -e FAIL check IGNORE_SKIPPED_LOGS=true
+grep skiptest test-suite.log && exit 1
+
+rm -f test-suite.log
+
+# Check that IGNORE_SKIPPED_LOGS works when given in the Makefile.
+
+cat >>Makefile.am <<'END'
+IGNORE_SKIPPED_LOGS = true
+END
+
+$AUTOMAKE --add-missing
+
+./configure
+run_make -e FAIL check
+grep skiptest test-suite.log && exit 1
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/parse.sh -> _service:tar_scm:automake-1.17.tar.xz/t/parse.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/per-target-flags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/per-target-flags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/percent.sh -> _service:tar_scm:automake-1.17.tar.xz/t/percent.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/percent2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/percent2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/perf/cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/perf/cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/perf/testsuite-recheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/perf/testsuite-recheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/perf/testsuite-summary.sh -> _service:tar_scm:automake-1.17.tar.xz/t/perf/testsuite-summary.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/phony.sh -> _service:tar_scm:automake-1.17.tar.xz/t/phony.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pkg-config-macros.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pkg-config-macros.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq11.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq11.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pluseq9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pluseq9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Cond2.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Cond2.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Cond3.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Cond3.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Condition-t.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Condition-t.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Condition.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Condition.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/DisjCon2.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/DisjCon2.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/DisjCon3.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/DisjCon3.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/DisjConditions-t.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/DisjConditions-t.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/DisjConditions.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/DisjConditions.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/General.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/General.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Version.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Version.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Version2.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Version2.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Version3.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Version3.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pm/Wrap.pl -> _service:tar_scm:automake-1.17.tar.xz/t/pm/Wrap.pl Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-data.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-data.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-extradist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-extradist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-ldadd.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-ldadd.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-libraries.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-libraries.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-ltlibraries.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-ltlibraries.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-programs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-programs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-scripts.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-scripts.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-sources.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-sources.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/posixsubst-tests.sh -> _service:tar_scm:automake-1.17.tar.xz/t/posixsubst-tests.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/posixtarget.sh Added

@@ -0,0 +1,43 @@
+#! /bin/sh
+# Copyright (C) 2023-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Check that the posix option is supported. See https://bugs.gnu.org/55025.
+
+. test-init.sh
+
+cat > configure.ac << 'END'
+AC_INIT(posixtest, 0.0)
+AM_INIT_AUTOMAKE(posix foreign)
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+END
+
+cat > Makefile.am << 'END'
+# Some comment.
+random-target:
+END
+
+$ACLOCAL
+$AUTOCONF
+$AUTOMAKE
+
+# .POSIX should be the first non-blank non-comment line.
+sed -e '/^$/d' -e '/^ *#/d' -e 1q Makefile.in | grep '^\.POSIX:'
+
+./configure
+# Although we aren't responsible for what autoconf does, check that the
+# result is as expected, since we're here.
+sed -e '/^$/d' -e '/^ *#/d' -e 1q Makefile | grep '^\.POSIX:'

_service:tar_scm:automake-1.16.5.tar.xz/t/ppf77.sh -> _service:tar_scm:automake-1.17.tar.xz/t/ppf77.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr211.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr211.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr220.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr220.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr224.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr224.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr229.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr229.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr243.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr243.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr266.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr266.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr279-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr279-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr279.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr279.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr287.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr287.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr300-lib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr300-lib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr300-ltlib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr300-ltlib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr300-prog.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr300-prog.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr307.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr307.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr401.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr401.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr401b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr401b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr401c.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr401c.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr72.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr72.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr87.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr87.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/pr9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/pr9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/precious.sh -> _service:tar_scm:automake-1.17.tar.xz/t/precious.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/prefix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/prefix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/preproc-basics.sh -> _service:tar_scm:automake-1.17.tar.xz/t/preproc-basics.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/preproc-c-compile.sh -> _service:tar_scm:automake-1.17.tar.xz/t/preproc-c-compile.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/preproc-demo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/preproc-demo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/preproc-errmsg.sh -> _service:tar_scm:automake-1.17.tar.xz/t/preproc-errmsg.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/primary-prefix-couples-documented-valid.sh -> _service:tar_scm:automake-1.17.tar.xz/t/primary-prefix-couples-documented-valid.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/primary-prefix-couples-force-valid.sh -> _service:tar_scm:automake-1.17.tar.xz/t/primary-prefix-couples-force-valid.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/primary-prefix-invalid-couples.tap -> _service:tar_scm:automake-1.17.tar.xz/t/primary-prefix-invalid-couples.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/primary-prefix-valid-couples.sh -> _service:tar_scm:automake-1.17.tar.xz/t/primary-prefix-valid-couples.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/primary.sh -> _service:tar_scm:automake-1.17.tar.xz/t/primary.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/primary2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/primary2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/primary3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/primary3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/print-libdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/print-libdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/proginst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/proginst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/programs-primary-rewritten.sh -> _service:tar_scm:automake-1.17.tar.xz/t/programs-primary-rewritten.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/py-compile-basedir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/py-compile-basedir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/py-compile-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/py-compile-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/py-compile-destdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/py-compile-destdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/py-compile-env.sh -> _service:tar_scm:automake-1.17.tar.xz/t/py-compile-env.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/py-compile-files.sh Added

@@ -0,0 +1,36 @@
+#! /bin/sh
+# Copyright (C) 2022-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Verify 'py-compile' script can handle inputs with spaces, etc...
+
+required=python
+. test-init.sh
+
+cp "$am_scriptdir/py-compile" . \
+  || fatal_ "failed to fetch auxiliary script py-compile"
+
+# Create files that require proper quoting.
+mkdir "dir with spaces"
+touch "nospace.py" "has space.py" "*.py" "dir with spaces/|.py"
+
+./py-compile "nospace.py" "has space.py" "*.py" "dir with spaces/|.py"
+
+py_installed "nospace.pyc"
+py_installed "has space.pyc"
+py_installed "*.pyc"
+py_installed "dir with spaces/|.pyc"
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/py-compile-option-terminate.sh -> _service:tar_scm:automake-1.17.tar.xz/t/py-compile-option-terminate.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/py-compile-usage.sh -> _service:tar_scm:automake-1.17.tar.xz/t/py-compile-usage.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -29,8 +29,8 @@
 cat stdout
 test -s stderr && { cat stderr >&2; exit 1; }
 grep '^Usage: py-compile .' stdout
-$FGREP ' --basedir DIR' stdout
-$FGREP ' --destdir DIR' stdout
+$FGREP ' --basedir DIR ' stdout
+$FGREP ' --destdir DIR ' stdout
 
 # --version
 
@@ -38,11 +38,11 @@
   || { cat stdout; cat stderr >&2; exit 1; }
 cat stdout
 test -s stderr && { cat stderr >&2; exit 1; }
-year='200-90-9' # Hopefully automake will be obsolete in 80 years ;-)
+year='20-90-90-9'
 month='(00-9|1012)'
 day='(0120-9|301)'
 hour='(010-9|20123)'
-LC_ALL=C $EGREP "^py-compile $year-$month-$day\.$hour" stdout
+LC_ALL=C $EGREP "^py-compile .* $year-$month-$day\.$hour" stdout
 test $(wc -l <stdout) -eq 1
 
 # Unknown option.

_service:tar_scm:automake-1.16.5.tar.xz/t/python-am-path-iftrue.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-am-path-iftrue.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python-dist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-dist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python-missing.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-missing.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python-pr10995.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-pr10995.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python-prefix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-prefix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python-too-old.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-too-old.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python-vars.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-vars.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python-virtualenv.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python-virtualenv.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -100,6 +100,8 @@
 	python -c 'from am_foo import foo_func; assert (foo_func () == 12345)'
 	python -c 'from am_virtenv import old_am; assert (old_am () == "AutoMake")'
 all-local: debug
+get-pyexecdir:
+	@echo $(pyexecdir)
 END
 
 cat > am_foo.py << 'END'
@@ -127,8 +129,8 @@
   py_installed "$py_site"/am_foo.pyc
   py_installed "$py_site"/am_virtenv/__init__.py
   py_installed "$py_site"/am_virtenv/__init__.pyc
-  test -f      "$py_site"/libquux.a
-  test -f      "$py_site"/am_virtenv/libzardoz.a
+  test -f      "$($MAKE get-pyexecdir ${1+"$@"})"/libquux.a
+  test -f      "$($MAKE get-pyexecdir ${1+"$@"})"/am_virtenv/libzardoz.a
 }
 
 check_uninstall ()
@@ -139,8 +141,8 @@
   py_installed --not "$py_site"/am_foo.pyc
   test ! -e          "$py_site"/am_virtenv/__init__.py
   py_installed --not "$py_site"/am_virtenv/__init__.pyc
-  test ! -e          "$py_site"/libquux.a
-  test ! -e          "$py_site"/am_virtenv/libzardoz.a
+  test ! -e          "$($MAKE get-pyexecdir ${1+"$@"})"/libquux.a
+  test ! -e          "$($MAKE get-pyexecdir ${1+"$@"})"/am_virtenv/libzardoz.a
 }
 
 $ACLOCAL

_service:tar_scm:automake-1.16.5.tar.xz/t/python.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python11.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python11.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python12.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python12.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/python3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/python3.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/ranlib_override.sh Added

@@ -0,0 +1,49 @@
+#! /bin/sh
+# Copyright (C) 2009-2024 Free Software Foundation, Inc.
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Test to make sure _RANLIB variables are detected and used as documented.
+
+. test-init.sh
+
+cat >> configure.ac << 'END'
+AC_PROG_CC
+AM_PROG_AR
+AC_PROG_RANLIB
+AC_OUTPUT
+END
+
+cat > Makefile.am << 'END'
+EXTRA_LIBRARIES = libfoo.a libbar.a
+libfoo_a_SOURCES = foo.c
+libfoo_a_RANLIB = $(RANLIB)
+libbar_a_SOURCES = bar.c
+END
+
+$ACLOCAL
+$AUTOMAKE -a
+
+# We should use libfoo_a_RANLIB not RANLIB.
+grep '.\$(libfoo_a_RANLIB) *libfoo.a' Makefile.in
+grep '.\$(RANLIB).*libfoo.a' Makefile.in && exit 1
+
+# We should use default RANLIB.
+grep '^ *libbar_a_RANLIB *=.*\$(RANLIB)' Makefile.in
+
+# Silent make rules should use AM_V_at as they're silenced.
+grep '.\$(AM_V_at)\$(libfoo_a_RANLIB)' Makefile.in
+grep '.\$(AM_V_at)\$(libbar_a_RANLIB)' Makefile.in
+
+exit 0

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-deeply-nested.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-deeply-nested.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-indir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-indir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-keep-going.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-keep-going.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-many.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-many.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-no-subdirs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-no-subdirs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-no-top-level.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-no-top-level.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-phony.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-phony.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user-wrap.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user-wrap.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/recurs-user2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/recurs-user2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/relativize.tap -> _service:tar_scm:automake-1.17.tar.xz/t/relativize.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-aclocal-version-mismatch.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-aclocal-version-mismatch.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-after-acinclude-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-after-acinclude-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-after-aclocal-m4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-after-aclocal-m4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-after-configure-ac.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-after-configure-ac.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-after-makefile-am.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-after-makefile-am.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-all-1.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-all-1.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-all-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-all-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-am-pr10111.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-am-pr10111.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-config-status-dependencies.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-config-status-dependencies.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-configure-dependencies.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-configure-dependencies.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-deeply-nested.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-deeply-nested.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-deleted-am-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-deleted-am-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-deleted-am-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-deleted-am-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-deleted-am.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-deleted-am.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-deleted-m4-file.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-deleted-m4-file.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-fail.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-fail.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-gnulib-add-acsubst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-gnulib-add-acsubst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-gnulib-add-header.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-gnulib-add-header.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-gnulib-remove-header.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-gnulib-remove-header.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-include-aclocal.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-include-aclocal.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-include-configure.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-include-configure.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-include-makefile.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-include-makefile.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-m4-pr10111.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-m4-pr10111.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-macrodir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-macrodir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-maintainer-mode.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-maintainer-mode.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-makefile-intree.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-makefile-intree.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-makefile-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-makefile-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-mild-stress.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-mild-stress.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-moved-m4-file.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-moved-m4-file.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-not-after-make-dist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-not-after-make-dist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-recurs-user.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-recurs-user.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-renamed-am.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-renamed-am.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-renamed-m4-file.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-renamed-m4-file.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-renamed-m4-macro-and-file.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-renamed-m4-macro-and-file.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-renamed-m4-macro.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-renamed-m4-macro.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir-from-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir-from-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir-gnu.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir-gnu.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir-grepping.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir-grepping.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir-long-time.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir-long-time.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir-no-makefile.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir-no-makefile.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir-only.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir-only.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-subdir3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-subdir3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/remake-timing-bug-pr8365.sh -> _service:tar_scm:automake-1.17.tar.xz/t/remake-timing-bug-pr8365.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/repeated-options.sh -> _service:tar_scm:automake-1.17.tar.xz/t/repeated-options.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/reqd2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/reqd2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/rm-f-probe.sh -> _service:tar_scm:automake-1.17.tar.xz/t/rm-f-probe.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2013-2021 Free Software Foundation, Inc.
+# Copyright (C) 2013-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -14,8 +14,8 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
-# Verify our probe that checks that "rm -f" doesn't complain if called
-# without file operands works as expected.  See automake bug#10828.
+# Verify our probe that checks that "rm -f" behavior works.
+# https://bugs.gnu.org/10828
 
 . test-init.sh
 
@@ -40,8 +40,8 @@
   shift
 done
 if test $# -eq 0; then
-  echo "Oops, fake rm called without arguments" >&2
-  exit 1
+  echo "Oops, fake rm called without arguments" >&2 #DELETE
+  exit 1 #CHANGE
 else
   exec rm $rm_opts "$@"
 fi
@@ -54,19 +54,17 @@
 
 rm -f && exit 99 # Sanity check.
 
-./configure 2>stderr && { cat stderr >&2; exit 1; }
-cat stderr >&2
-
-grep "'rm' program.* unable to run without file operands" stderr
-$FGREP "tell bug-automake@gnu.org about your system" stderr
-$FGREP "install GNU coreutils" stderr
-$EGREP "(^| |')ACCEPT_INFERIOR_RM_PROGRAM($| |')" stderr
+# Check that `rm -f` is detected as broken.
+./configure
+grep '^am__rm_f_notfound = ""$' Makefile
 
-ACCEPT_INFERIOR_RM_PROGRAM=yes; export ACCEPT_INFERIOR_RM_PROGRAM
+# Change the `rm -f` behavior to work.
+sed -e '/#DELETE/d' -e '/#CHANGE/s:1:0:' bin/rm > bin/rm.tmp
+cat bin/rm.tmp > bin/rm
 
+# Check that `rm -f` is detected as working.
 ./configure
-$MAKE
-$MAKE distcheck
+grep '^am__rm_f_notfound = *$' Makefile
 
 # For the sake of our exit trap.
 PATH=$original_PATH; export PATH

_service:tar_scm:automake-1.16.5.tar.xz/t/rulepat.sh -> _service:tar_scm:automake-1.17.tar.xz/t/rulepat.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/sanity.sh -> _service:tar_scm:automake-1.17.tar.xz/t/sanity.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/seenc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/seenc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-cc-no-c-o.sh -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-cc-no-c-o.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-configure-help.sh -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-configure-help.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-dir.tap -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-dir.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-exit.tap -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-exit.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-explicit-skips.sh -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-explicit-skips.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-is-blocked-signal.tap -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-is-blocked-signal.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-is_newest.tap -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-is_newest.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-me.tap -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-me.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-report.sh -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-report.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-seq.tap -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-seq.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-shell-no-trail-bslash.sh -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-shell-no-trail-bslash.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/self-check-unindent.tap -> _service:tar_scm:automake-1.17.tar.xz/t/self-check-unindent.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/serial-tests.sh -> _service:tar_scm:automake-1.17.tar.xz/t/serial-tests.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-c.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-c.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-configsite.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-configsite.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-custom.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-custom.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-cxx.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/silent-defaults.sh Added

@@ -0,0 +1,185 @@
+#!/bin/sh
+# Copyright (C) 2022-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Check verbose mode defaults and behavior. See bug#32868.
+# Because we have to rerun the autotools for every configuration,
+# this test can take 30 seconds or so to run.
+
+. test-init.sh
+
+: > Makefile.am
+
+# &#xc;
+echo "Default behavior is currently verbose."
+cat <<EOF >configure.ac
+AC_INIT(silent-defaults-default-verbose, 1.0)
+AM_INIT_AUTOMAKE
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+EOF
+
+$ACLOCAL
+$AUTOMAKE
+$AUTOCONF
+
+./configure
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+./configure -C --enable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --disable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+# &#xc;
+echo "User doesn't pick a silent mode default before AM_INIT_AUTOMAKE."
+cat <<EOF >configure.ac
+AC_INIT(silent-defaults-use-am_silent_rules, 1.0)
+AM_SILENT_RULES
+AM_INIT_AUTOMAKE
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+EOF
+
+$ACLOCAL
+$AUTOMAKE
+$AUTOCONF
+
+./configure
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+./configure -C --enable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --disable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+# &#xc;
+echo "User disables silent mode default before AM_INIT_AUTOMAKE."
+cat <<EOF >configure.ac
+AC_INIT(silent-defaults-user-disable-before-am_init, 1.0)
+AM_SILENT_RULES(no)
+AM_INIT_AUTOMAKE
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+EOF
+
+$ACLOCAL
+$AUTOMAKE
+$AUTOCONF
+
+./configure
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+./configure -C --enable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --disable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+# &#xc;
+echo "User enables silent mode default before AM_INIT_AUTOMAKE."
+cat <<EOF >configure.ac
+AC_INIT(silent-defaults-user-enable-before-am_init, 1.0)
+AM_SILENT_RULES(yes)
+AM_INIT_AUTOMAKE
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+EOF
+
+$ACLOCAL
+$AUTOMAKE
+$AUTOCONF
+
+./configure
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --enable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --disable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+# &#xc;
+echo "User doesn't pick a silent mode default after AM_INIT_AUTOMAKE."
+cat <<EOF >configure.ac
+AC_INIT(silent-defaults-user-no-default-after-am_init, 1.0)
+AM_INIT_AUTOMAKE
+AM_SILENT_RULES
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+EOF
+
+$ACLOCAL
+$AUTOMAKE
+$AUTOCONF
+
+./configure
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+./configure -C --enable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --disable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+# &#xc;
+echo "User disables silent mode default after AM_INIT_AUTOMAKE."
+cat <<EOF >configure.ac
+AC_INIT(silent-defaults-user-disable-after-am_init, 1.0)
+AM_INIT_AUTOMAKE
+AM_SILENT_RULES(no)
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+EOF
+
+$ACLOCAL
+$AUTOMAKE
+$AUTOCONF
+
+./configure
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+./configure -C --enable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --disable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+# &#xc;
+echo "User enables silent mode default after AM_INIT_AUTOMAKE."
+cat <<EOF >configure.ac
+AC_INIT(silent-defaults-user-enable-after-am_init, 1.0)
+AM_INIT_AUTOMAKE
+AM_SILENT_RULES(yes)
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
+EOF
+
+$ACLOCAL
+$AUTOMAKE
+$AUTOCONF
+
+./configure
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --enable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 0' Makefile
+
+./configure -C --disable-silent-rules
+grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-f77.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-f77.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-f90.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-f90.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-gen.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-gen.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-lex.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-lex.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-lt.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-lt.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-many-languages.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-many-languages.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-nested-vars.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-nested-vars.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-texi.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-texi.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-yacc-headers.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-yacc-headers.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/silent-yacc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/silent-yacc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/sourcefile-in-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/sourcefile-in-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/space.sh -> _service:tar_scm:automake-1.17.tar.xz/t/space.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/specflg-dummy.sh -> _service:tar_scm:automake-1.17.tar.xz/t/specflg-dummy.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/specflg6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/specflg6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/specflg7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/specflg7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/specflg8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/specflg8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/specflg9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/specflg9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/spell.sh -> _service:tar_scm:automake-1.17.tar.xz/t/spell.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/spell2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/spell2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/spell3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/spell3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/spelling.sh -> _service:tar_scm:automake-1.17.tar.xz/t/spelling.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/spy-double-colon.sh -> _service:tar_scm:automake-1.17.tar.xz/t/spy-double-colon.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/spy-rm.tap -> _service:tar_scm:automake-1.17.tar.xz/t/spy-rm.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/src-acsubst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/src-acsubst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/stamph2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/stamph2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/stdinc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/stdinc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/stdlib.sh -> _service:tar_scm:automake-1.17.tar.xz/t/stdlib.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/stdlib2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/stdlib2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/strictness-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/strictness-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/strictness-precedence.sh -> _service:tar_scm:automake-1.17.tar.xz/t/strictness-precedence.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/strip.sh -> _service:tar_scm:automake-1.17.tar.xz/t/strip.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/strip2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/strip2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/strip3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/strip3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-ac-subst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-ac-subst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-add-pr46.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-add-pr46.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-add2-pr46.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-add2-pr46.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2003-2021 Free Software Foundation, Inc.
+# Copyright (C) 2003-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -32,11 +32,15 @@
 
 cat > Makefile.am << 'END'
 SUBDIRS = sub
+
+# The test can fail under a parallel make, so disable.
+# No evident way to debug or reliably reproduce.
+.NOTPARALLEL:
 END
 
 mkdir sub
 
-: > sub/Makefile.am
+echo .NOTPARALLEL: >sub/Makefile.am
 
 mkdir m4
 echo 'AC_DEFUN(MORE_DEFS, )' > m4/moredefs.m4
@@ -53,7 +57,7 @@
 # configure.ac.  That is already tested by 'subdir-add-pr46.sh' though,
 # so here we try to just edit a file that is included by configure.ac,
 # without touching configure.ac itself.
-
+$sleep
 mkdir sub/maude
 cat > sub/maude/Makefile.am << 'END'
 include_HEADERS = foo.h
@@ -76,6 +80,7 @@
 # We want a simple rebuild from sub/ to create sub/maude/Makefile
 # and maude/Makefile automatically.
 cd sub
+$sleep
 $MAKE
 cd ..
 grep '^SUBDIRS = *maude *$' sub/Makefile.in
@@ -85,6 +90,7 @@
 
 # Make sure the dependencies of aclocal.m4 or honored at least from
 # the top-level directory.
+$sleep
 echo 'AC_DEFUN(MORE_DEFS, AC_SUBST(GREPME))' > m4/moredefs.m4
 $MAKE

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-am-cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-am-cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-cond-err.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-cond-err.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-cond-gettext.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-cond-gettext.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-distclean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-distclean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-env-interference.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-env-interference.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-keep-going-pr12554.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-keep-going-pr12554.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-order.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-order.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-subsub.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-subsub.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir-with-slash.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir-with-slash.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj-clean-lt-pr10697.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj-clean-lt-pr10697.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj-clean-pr10697.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj-clean-pr10697.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj-indir-pr13928.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj-indir-pr13928.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj-objname-clash.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj-objname-clash.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj-pr13928-more-langs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj-pr13928-more-langs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj-vpath-pr13928.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj-vpath-pr13928.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj10.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj10.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj11a.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj11a.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj11b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj11b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj11c.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj11c.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobj9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobj9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subobjname.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subobjname.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subpkg-macrodir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subpkg-macrodir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subpkg-yacc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subpkg-yacc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subpkg.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subpkg.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subpkg2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subpkg2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subpkg3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subpkg3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subpkg4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subpkg4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subst-no-trailing-empty-line.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subst-no-trailing-empty-line.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subst3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subst3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subst4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subst4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/subst5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/subst5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/substre2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/substre2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/substref.sh -> _service:tar_scm:automake-1.17.tar.xz/t/substref.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/substtarg.sh -> _service:tar_scm:automake-1.17.tar.xz/t/substtarg.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix-chain.tap -> _service:tar_scm:automake-1.17.tar.xz/t/suffix-chain.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix-custom-pr14441.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix-custom-pr14441.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix-custom-subobj-and-specflg.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix-custom-subobj-and-specflg.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix-custom-subobj.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix-custom-subobj.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix-extra-c-stuff-pr14560.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix-extra-c-stuff-pr14560.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix10.tap -> _service:tar_scm:automake-1.17.tar.xz/t/suffix10.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix11.tap -> _service:tar_scm:automake-1.17.tar.xz/t/suffix11.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix3.tap -> _service:tar_scm:automake-1.17.tar.xz/t/suffix3.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix5.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix5.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix6b.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix6b.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix6c.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix6c.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix8.tap -> _service:tar_scm:automake-1.17.tar.xz/t/suffix8.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/suffix9.sh -> _service:tar_scm:automake-1.17.tar.xz/t/suffix9.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/symlink.sh -> _service:tar_scm:automake-1.17.tar.xz/t/symlink.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/symlink2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/symlink2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/syntax.sh -> _service:tar_scm:automake-1.17.tar.xz/t/syntax.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tags-lisp-space.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tags-lisp-space.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tags-pr12372.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tags-pr12372.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tags2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tags2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tagsub.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tagsub.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-ambiguous-directive.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-ambiguous-directive.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-autonumber.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-autonumber.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-bad-prog.tap -> _service:tar_scm:automake-1.17.tar.xz/t/tap-bad-prog.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-bailout-and-logging.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-bailout-and-logging.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-bailout-leading-space.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-bailout-leading-space.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-bailout-suppress-badexit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-bailout-suppress-badexit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-bailout-suppress-later-diagnostic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-bailout-suppress-later-diagnostic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-bailout-suppress-later-errors.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-bailout-suppress-later-errors.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-bailout.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-bailout.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-color.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-color.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-common-setup.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-common-setup.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-deps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-deps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-diagnostic-custom.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-diagnostic-custom.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-diagnostic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-diagnostic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-doc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-doc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-doc2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-doc2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-driver-stderr.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-driver-stderr.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-empty-diagnostic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-empty-diagnostic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-empty.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-empty.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-escape-directive-2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-escape-directive-2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-escape-directive.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-escape-directive.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-exit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-exit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-fancy.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-fancy.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-fancy2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-fancy2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-global-log.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-global-log.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-global-result.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-global-result.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-log.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-log.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-merge-stdout-stderr.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-merge-stdout-stderr.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-missing-plan-and-bad-exit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-missing-plan-and-bad-exit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-more.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-more.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-more2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-more2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-msg0-bailout.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-msg0-bailout.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-msg0-directive.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-msg0-directive.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-msg0-misc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-msg0-misc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-msg0-planskip.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-msg0-planskip.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-msg0-result.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-msg0-result.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-negative-numbers.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-negative-numbers.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-no-disable-hard-error.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-no-disable-hard-error.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-no-merge-stdout-stderr.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-no-merge-stdout-stderr.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-no-spurious-numbers.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-no-spurious-numbers.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-no-spurious-summary.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-no-spurious-summary.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-no-spurious.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-no-spurious.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-not-ok-skip.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-not-ok-skip.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-number-wordboundary.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-number-wordboundary.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-numbers-leading-zero.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-numbers-leading-zero.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-numeric-description.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-numeric-description.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-out-of-order.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-out-of-order.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-passthrough-exit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-passthrough-exit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-passthrough.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-passthrough.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-plan-corner.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-plan-corner.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-plan-errors.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-plan-errors.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-plan-leading-zero.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-plan-leading-zero.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-plan-malformed.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-plan-malformed.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-plan-middle.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-plan-middle.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-plan-whitespace.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-plan-whitespace.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-plan.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-plan.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-and-logging.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-and-logging.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-badexit.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-badexit.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-bailout.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-bailout.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-case-insensitive.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-case-insensitive.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-late.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-late.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-later-errors.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-later-errors.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-unplanned-corner.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-unplanned-corner.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-unplanned.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-unplanned.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip-whitespace.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip-whitespace.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-planskip.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-planskip.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-recheck-logs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-recheck-logs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-recheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-recheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-result-comment.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-result-comment.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-signal.tap -> _service:tar_scm:automake-1.17.tar.xz/t/tap-signal.tap Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-summary-color.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-summary-color.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-summary.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-summary.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-test-number-0.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-test-number-0.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-todo-skip-together.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-todo-skip-together.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-todo-skip-whitespace.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-todo-skip-whitespace.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-todo-skip.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-todo-skip.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-unplanned.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-unplanned.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-whitespace-normalization.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-whitespace-normalization.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-with-and-without-number.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-with-and-without-number.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tap-xfail-tests.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tap-xfail-tests.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tar-opts-errors.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tar-opts-errors.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tar-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tar-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tar-pax.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tar-pax.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tar-ustar-id-too-high.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tar-ustar-id-too-high.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tar-ustar.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tar-ustar.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/target-cflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/target-cflags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/targetclash.sh -> _service:tar_scm:automake-1.17.tar.xz/t/targetclash.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-acsubst.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-acsubst.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-create-log-dir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-create-log-dir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-custom-multitest-recheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-custom-multitest-recheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-custom-multitest-recheck2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-custom-multitest-recheck2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-custom-multitest.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-custom-multitest.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -62,8 +62,8 @@
 cat > pass-fail.t << 'END'
 echo %% pass-fail %%
 echo 'FAIL: this fails :-('
-echo 'some randome message'
-echo 'some randome warning' >&2
+echo 'some random message'
+echo 'some random warning' >&2
 echo 'PASS: this passes :-)'
 echo 'INFO: blah'
 echo 'WARNING: blah blah' >&2
@@ -148,7 +148,7 @@
   # Check that the content of, and only of, the test logs with at least
   # one failing test case has been copied into 'test-suite.log'.  Note
   # that test logs containing skipped or xfailed test cases are *not*
-  # copied into 'test-suite.log' -- a behaviour that deliberately differs
+  # copied into 'test-suite.log' -- a behavior that deliberately differs
   # from the one of the built-in Automake test drivers.
   grep '%%' test-suite.log # For debugging.
   grep '%% fail %%' test-suite.log

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-custom-no-extra-driver.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-custom-no-extra-driver.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-custom-xfail-tests.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-custom-xfail-tests.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-custom.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-custom.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-fail.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-fail.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-is-distributed.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-is-distributed.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-strip-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-strip-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-driver-trs-suffix-registered.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-driver-trs-suffix-registered.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-extensions-cond.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-extensions-cond.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-extensions-empty.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-extensions-empty.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-extensions.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-extensions.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-harness-vpath-rewrite.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-harness-vpath-rewrite.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-log.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-log.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-logs-repeated.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-logs-repeated.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-metadata-global-log.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-metadata-global-log.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-metadata-global-result.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-metadata-global-result.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-metadata-recheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-metadata-recheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-metadata-results.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-metadata-results.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-missing.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-missing.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-missing2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-missing2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-trs-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-trs-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-trs-recover.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-trs-recover.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/test-trs-recover2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/test-trs-recover2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tests-environment-and-log-compiler.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tests-environment-and-log-compiler.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tests-environment-backcompat.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tests-environment-backcompat.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/tests-environment-fd-redirect.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tests-environment-fd-redirect.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -14,14 +14,14 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
-# Test for a behaviour of 'TESTS_ENVIRONMENT' and 'AM_TESTS_ENVIRONMENT'
+# Test for a behavior of 'TESTS_ENVIRONMENT' and 'AM_TESTS_ENVIRONMENT'
 # w.r.t. file descriptor redirections which, although undocumented,
 # is nonetheless required by Gnulib's 'tests/init.sh' and by coreutils'
 # testsuite.
-# The checked behaviour is that we can portably do file descriptor
+# The checked behavior is that we can portably do file descriptor
 # redirections by placing them at the end of a {AM_,}TESTS_ENVIRONMENT
 # definition without a following semicolon.  The need to support this
-# is detailedly motivated by coreutils bug#8846:
+# is motivated in detail by coreutils bug#8846:
 #   <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=8846>
 # and the following CC:ed thread on bug-autoconf list:
 #   <https://lists.gnu.org/archive/html/bug-autoconf/2011-06/msg00002.html>

_service:tar_scm:automake-1.16.5.tar.xz/t/tests-environment.sh -> _service:tar_scm:automake-1.17.tar.xz/t/tests-environment.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/testsuite-summary-color.sh -> _service:tar_scm:automake-1.17.tar.xz/t/testsuite-summary-color.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/testsuite-summary-count-many.sh -> _service:tar_scm:automake-1.17.tar.xz/t/testsuite-summary-count-many.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/testsuite-summary-count.sh -> _service:tar_scm:automake-1.17.tar.xz/t/testsuite-summary-count.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/testsuite-summary-header.sh -> _service:tar_scm:automake-1.17.tar.xz/t/testsuite-summary-header.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/testsuite-summary-reference-log.sh -> _service:tar_scm:automake-1.17.tar.xz/t/testsuite-summary-reference-log.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -46,11 +46,11 @@
 ../configure
 
 run_make -O -e FAIL check
-grep '^See \./my_test_suite\.log$' stdout
+grep '^See \./my_test_suite\.log for debugging\.$' stdout
 
 mkdir bar
 run_make -O -e FAIL TEST_SUITE_LOG=bar/bar.log check
-grep '^See \./bar/bar\.log$' stdout
+grep '^See \./bar/bar\.log for debugging\.$' stdout
 
 cd ..
 
@@ -70,13 +70,13 @@
 
 ./configure
 run_make -O -e FAIL check
-grep '^See sub/test-suite\.log$' stdout
+grep '^See sub/test-suite\.log for debugging\.$' stdout
 cd sub
 run_make -O -e FAIL check
-grep '^See sub/test-suite\.log$' stdout
+grep '^See sub/test-suite\.log for debugging\.$' stdout
 cd ..
 
 run_make -O -e FAIL TEST_SUITE_LOG=foo.log check
-grep '^See sub/foo\.log$' stdout
+grep '^See sub/foo\.log for debugging\.$' stdout
 
 :

_service:tar_scm:automake-1.16.5.tar.xz/t/toplevelmd.sh -> _service:tar_scm:automake-1.17.tar.xz/t/toplevelmd.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/transform.sh -> _service:tar_scm:automake-1.17.tar.xz/t/transform.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/transform2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/transform2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/transform3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/transform3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-absolute-srcdir-pr408.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-absolute-srcdir-pr408.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-add-missing-and-dist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-add-missing-and-dist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-bsd-make-recurs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-bsd-make-recurs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-builddir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-builddir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-clean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-clean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-dvi-recurs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-dvi-recurs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-include.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-include.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2012-2021 Free Software Foundation, Inc.
+# Copyright (C) 2012-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -28,6 +28,9 @@
 sub_more_TEXINFOS = sub/desc.texi sub/hist.texi
 END
 
+# We avoid apostrophes in the test document since Texinfo
+# turns them into UTF-8, which is not easy to grep.
+#
 cat > main.texi << 'END'
 \input texinfo
 @setfilename main.info
@@ -61,8 +64,8 @@
 
 cat > three.texi << 'END'
 @node three
-@chapter Chapter two
-GNU's Not Unix.
+@chapter Chapter three
+Quux quux quux.
 END
 
 mkdir sub
@@ -106,7 +109,7 @@
   srcdir=${1-.}
   $FGREP "Foo bar, baz."                        $srcdir/main.info
   $FGREP "Blah Blah Blah."                      $srcdir/main.info
-  $FGREP "GNU's Not Unix."                      $srcdir/main.info
+  $FGREP "Quux quux quux."                      $srcdir/main.info
   $FGREP 'It does something, really.'           $srcdir/sub/more.info
   $FGREP 'It was written somehow.'              $srcdir/sub/more.info
 }

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-info-in-srcdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-info-in-srcdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-makeinfo-error-no-clobber.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-makeinfo-error-no-clobber.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-many-output-formats-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-many-output-formats-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-many-output-formats.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-many-output-formats.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2003-2021 Free Software Foundation, Inc.
+# Copyright (C) 2003-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -86,6 +86,10 @@
 $AUTOMAKE --add-missing
 $AUTOCONF
 
+# Make sure AM_TEXI2FLAGS is passed down.
+grep '\$(TEXI2DVI).*\$(AM_TEXI2FLAGS)' Makefile.in
+grep '\$(TEXI2PDF).*\$(AM_TEXI2FLAGS)' Makefile.in
+
 # To simplify syncing with sister test 'txinfo-many-output-formats.sh'
 srcdir=.
 
@@ -156,6 +160,13 @@
 test ! -e share/$me/html/main2.html
 test ! -e share/$me/html/main3.html
 
+# Restore the makefile without a broken AM_MAKEINFOFLAGS definition.
+# This must happen before processing any non-html targets.  See
+# https://bugs.gnu.org/30172
+cp -f $srcdir/Makefile.sav $srcdir/Makefile.am
+(cd $srcdir && $AUTOMAKE)
+./config.status Makefile
+
 $MAKE dvi
 test -f main.dvi
 test -f sub/main2.dvi
@@ -199,8 +210,6 @@
 test ! -e share/$me/pdf/main3.pdf
 test ! -e share/$me/pdf/hello
 
-# Restore the makefile without a broken AM_MAKEINFOFLAGS definition.
-cp -f $srcdir/Makefile.sav $srcdir/Makefile.am
 using_gmake || $MAKE Makefile
 $MAKE distcheck

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-no-clutter.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-no-clutter.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-no-extra-dist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-no-extra-dist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-no-installinfo.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-no-installinfo.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-no-repeated-targets.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-no-repeated-targets.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/txinfo-no-setfilename-no-inputs.sh Added

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-no-setfilename.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-no-setfilename.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/txinfo-no-texi-but-texi-in.sh Added

@@ -0,0 +1,63 @@
+#! /bin/sh
+# Copyright (C) 2023-2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# Check if Automake doesn't exit with an error for Texinfo output files
+# without a direct input file, but with a matching input file processed
+# by 'configure' (file.texi.in).
+# https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54063#41
+#
+# This also tests an @setfilename that is different from the file name,
+# and the lack of any @setfilename, in the case of using .texi.in.
+# (See scan_texinfo_file in automake.)
+
+. test-init.sh
+
+echo AC_OUTPUT >> configure.ac
+
+cat > Makefile.am << 'END'
+info_TEXINFOS = main.texi
+END
+
+cat > main.texi.in << 'END'
+\input texinfo
+@setfilename main.info
+@settitle main
+@node Top
+Hello world.
+@bye
+END
+
+$ACLOCAL
+$AUTOMAKE --add-missing
+
+grep '/main.info:' Makefile.in
+
+# Recreate the test document without @setfilename.
+cat > main.texi.in << 'END'
+\input texinfo
+@settitle main
+@node Top
+Hello world.
+@bye
+END
+
+$ACLOCAL
+$AUTOMAKE
+
+# The result should use main.info (from the .texi file name).
+grep '/main.info:' Makefile.in
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-nodist-info.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-nodist-info.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-other-suffixes.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-other-suffixes.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-override-infodeps.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-override-infodeps.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-override-texinfo-tex.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-override-texinfo-tex.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-setfilename-repeated.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-setfilename-repeated.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-setfilename-suffix-strip.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-setfilename-suffix-strip.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-subdir-pr343.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-subdir-pr343.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-tex-dist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-tex-dist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-unrecognized-extension.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-unrecognized-extension.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-unrecognized-info-suffix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-unrecognized-info-suffix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-vtexi.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-vtexi.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-vtexi2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-vtexi2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-vtexi3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-vtexi3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-vtexi4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-vtexi4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo-without-info-suffix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo-without-info-suffix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo19.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo19.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo23.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo23.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo24.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo24.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo25.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo25.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/txinfo28.sh -> _service:tar_scm:automake-1.17.tar.xz/t/txinfo28.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/uninstall-fail.sh -> _service:tar_scm:automake-1.17.tar.xz/t/uninstall-fail.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/uninstall-pr9578.sh -> _service:tar_scm:automake-1.17.tar.xz/t/uninstall-pr9578.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/unused.sh -> _service:tar_scm:automake-1.17.tar.xz/t/unused.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/upc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/upc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/upc2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/upc2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/upc3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/upc3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-configure.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-configure.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-grepping.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-grepping.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-headers.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-headers.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-libs-distcheck.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-libs-distcheck.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-libs-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-libs-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-libs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-libs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-mix.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-mix.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-mix2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-mix2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-non-recursive-setup.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-non-recursive-setup.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-parallel.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-parallel.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-per-target-flags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-per-target-flags.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-recursive-setup.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-recursive-setup.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-vapi.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-vapi.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2012-2021 Free Software Foundation, Inc.
+# Copyright (C) 2012-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -14,7 +14,7 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
-# Test and that vapi files are correctly handled by Vala support.
+# Test that vapi files are correctly handled by Vala support.
 
 required='pkg-config valac cc GNUmake'
 . test-init.sh
@@ -42,7 +42,7 @@
 }
 END
 
-# Use printf, not echo, to avoid '\n' being considered and escape
+# Use printf, not echo, to avoid '\n' being considered an escape
 # sequence and printed as a newline in 'foo.h'.
 printf '%s\n' '#define BARBAR "Zardoz!\n"' > foo.h
 
@@ -78,7 +78,7 @@
 
 # Simple check on remake rules.
 $sleep
-# Use printf, not echo, to avoid '\n' being considered and escape
+# Use printf, not echo, to avoid '\n' being considered an escape
 # sequence and printed as a newline in 'foo.h'.
 printf '%s\n' '#define BAZBAZ "Quux!\n"' > foo.h
 sed 's/BARBAR/BAZBAZ/' zardoz.vala > t && mv -f t zardoz.vala || exit 99

_service:tar_scm:automake-1.16.5.tar.xz/t/vala-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vala-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/var-recurs.sh -> _service:tar_scm:automake-1.17.tar.xz/t/var-recurs.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/var-recurs2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/var-recurs2.sh Changed

_service:tar_scm:automake-1.17.tar.xz/t/varempty.sh Added

@@ -0,0 +1,36 @@
+#! /bin/sh
+# Copyright (C) 2024 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+# An empty variable name $() should not cause a Perl warning, namely:
+#   Use of uninitialized value $var in string eq at
+#   .../lib/Automake/Variable.pm line 754, <GEN2> line 3.
+# (in scan_variable_expansions)
+# 
+# This showed up with the NetworkManager and other packages in Fedora:
+# https://lists.gnu.org/archive/html/automake/2024-06/msg00085.html
+# (The actual purpose of the "$()" is unclear.)
+
+. test-init.sh
+
+cat > Makefile.am << 'END'
+x:
+	$()
+END
+
+$ACLOCAL
+$AUTOMAKE
+
+:

_service:tar_scm:automake-1.16.5.tar.xz/t/vars.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vars.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vars3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vars3.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2002-2021 Free Software Foundation, Inc.
+# Copyright (C) 2002-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -15,7 +15,8 @@
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 # Check that Automake warns about variables containing spaces
-# and other non-POSIX characters.
+# and other non-POSIX characters, but not about real POSIX
+# variables (see bug#9587).
 
 . test-init.sh
 
@@ -32,6 +33,10 @@
 	echo $${ok-this is}
 L11: $(thisis) $(ok)
 	${here}
+just_a_test:
+	echo "$(@F) $(%F) $(?F) $(<F) $(*F) $(@D) $(%D) $(?D) $(<D) $(*D)" > $@
+	echo "$(%) $(?) $(<) $(*)" > $@
+	echo "$% $? $< $*" > $@
 EOF
 
 $ACLOCAL
@@ -59,6 +64,20 @@
 grep ':9:.*another Error' stderr
 
 $EGREP 'ok|thisis|here' stderr && exit 1
+grep '@F' stderr && exit 1
+grep '%F' stderr && exit 1
+grep '?F' stderr && exit 1
+grep '<F' stderr && exit 1
+grep '*F' stderr && exit 1
+grep '@D' stderr && exit 1
+grep '%D' stderr && exit 1
+grep '?D' stderr && exit 1
+grep '<D' stderr && exit 1
+grep '*D' stderr && exit 1
+grep ': %: ' stderr && exit 1
+grep ': ?: ' stderr && exit 1
+grep ': <: ' stderr && exit 1
+grep ': *: ' stderr && exit 1
 
 # None of these errors be diagnosed with '-Wno-portability'.
 $AUTOMAKE -Wno-portability

_service:tar_scm:automake-1.16.5.tar.xz/t/vartar.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vartar.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vartypo2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vartypo2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vartypos.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vartypos.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/version3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/version3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/version4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/version4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/version6.sh -> _service:tar_scm:automake-1.17.tar.xz/t/version6.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/version7.sh -> _service:tar_scm:automake-1.17.tar.xz/t/version7.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/version8.sh -> _service:tar_scm:automake-1.17.tar.xz/t/version8.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warning-groups-win-over-strictness.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warning-groups-win-over-strictness.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warnings-obsolete-default.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warnings-obsolete-default.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warnings-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warnings-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warnings-precedence.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warnings-precedence.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warnings-strictness-interactions.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warnings-strictness-interactions.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warnings-unknown.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warnings-unknown.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warnings-win-over-strictness.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warnings-win-over-strictness.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/warnopts.sh -> _service:tar_scm:automake-1.17.tar.xz/t/warnopts.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/werror.sh -> _service:tar_scm:automake-1.17.tar.xz/t/werror.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/werror2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/werror2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/werror3.sh -> _service:tar_scm:automake-1.17.tar.xz/t/werror3.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/werror4.sh -> _service:tar_scm:automake-1.17.tar.xz/t/werror4.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/whoami.sh -> _service:tar_scm:automake-1.17.tar.xz/t/whoami.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/xsource.sh -> _service:tar_scm:automake-1.17.tar.xz/t/xsource.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-auxdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-auxdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-bison-skeleton-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-bison-skeleton-cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-bison-skeleton.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-bison-skeleton.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-clean-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-clean-cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-clean.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-clean.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-cxx-grepping.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-cxx-grepping.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-cxx.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -28,6 +28,8 @@
 END
 
 cat > Makefile.am << 'END'
+AM_LFLAGS = --never-interactive
+
 bin_PROGRAMS = foo1 foo2 foo3 foo4
 foo1_SOURCES = parse1.yy  foo.cc
 foo2_SOURCES = parse2.y++ bar.c++
@@ -43,12 +45,25 @@
 
 cat > parse1.yy << 'END'
 %{
+// Include C header to provide global symbols that flex assumes.
+// https://bugs.gnu.org/20031
+#include <stdlib.h>
 // Valid C++, but deliberately invalid C.
 #include <cstdio>
 #include <cstdlib>
+using std::exit;
+using std::free;
+using std::malloc;
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+extern "C" {
+#endif
 // "std::" qualification required by Sun C++ 5.9.
 int yylex (void) { return std::getchar (); }
 void yyerror (const char *s) {}
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+}
+#endif
+
 %}
 %%
 a : 'a' { exit(0); };

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-d-basic.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-d-basic.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-d-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-d-cxx.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -26,11 +26,23 @@
   header=$1
   unindent <<END
     %{
+    // Include C header to provide global symbols that flex assumes.
+    // https://bugs.gnu.org/20031
+    #include <stdlib.h>
     // Valid C++, but deliberately invalid C.
     #include <cstdlib>
+    using std::exit;
+    using std::free;
+    using std::malloc;
     #include "$header"
+    #if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+    extern "C" {
+    #endif
     int yylex (void) { return 0; }
     void yyerror (const char *s) {}
+    #if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+    }
+    #endif
     %}
     %%
     x : 'x' {};
@@ -64,6 +76,8 @@
 
 # These makefiles will be extended later.
 cat > Makefile.am <<'END'
+AM_LFLAGS = --never-interactive
+
 .PHONY: echo-distcom
 echo-distcom:
 	@echo ' ' $(DIST_COMMON) ' '

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-d-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-d-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-deleted-headers.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-deleted-headers.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-depend.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-depend.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-depend2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-depend2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-dist-nobuild-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-dist-nobuild-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-dist-nobuild.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-dist-nobuild.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-dry.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-dry.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-grepping.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-grepping.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-grepping2.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-grepping2.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-headers-and-dist-pr47.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-headers-and-dist-pr47.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-line.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-line.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-misc.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-misc.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-mix-c-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-mix-c-cxx.sh Changed

@@ -1,5 +1,5 @@
 #! /bin/sh
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2024 Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -28,6 +28,8 @@
 END
 
 cat > Makefile.am << 'END'
+AM_LFLAGS = --never-interactive
+
 bin_PROGRAMS = c1 c2 cxx1 cxx2 cxx3
 AM_YFLAGS = -d
 
@@ -52,8 +54,14 @@
 
 cat > p.y <<'END'
 %{
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+extern "C" {
+#endif
 int yylex (void) { int new = 0; return new; }
 void yyerror (const char *s) {}
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+}
+#endif
 %}
 %token ZARDOZ
 %%
@@ -63,6 +71,7 @@
 
 cat > 1.c <<'END'
 #include "p.h"
+extern int yyparse (void);
 int main ()
 {
     int new = ZARDOZ;
@@ -72,6 +81,7 @@
 END
 
 cat > 2.c <<'END'
+extern int yyparse (void);
 int main ()
 {
     int yyparse ();
@@ -82,10 +92,23 @@
 
 cat > parse.yy <<'END'
 %{
+// Include C header to provide global symbols that flex assumes.
+// https://bugs.gnu.org/20031
+#include <stdlib.h>
+// Valid C++, but deliberately invalid C.
 #include <cstdlib>
+using std::exit;
+using std::free;
+using std::malloc;
 #include "parse.hh"
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+extern "C" {
+#endif
 int yylex (void) { return 0; }
 void yyerror (const char *s) {}
+#if (defined __cplusplus) && ((!defined __sun) || (defined __EXTERN_C__))
+}
+#endif
 %}
 %token FOOBAR
 %%

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-nodist.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-nodist.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-pr204.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-pr204.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-subdir.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-subdir.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-vpath.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-vpath.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yacc-weirdnames.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yacc-weirdnames.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags-cmdline-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags-cmdline-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags-conditional.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags-conditional.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags-cxx.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags-cxx.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags-d-false-positives.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags-d-false-positives.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags-force-conditional.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags-force-conditional.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags-force-override.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags-force-override.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags-var-expand.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags-var-expand.sh Changed

_service:tar_scm:automake-1.16.5.tar.xz/t/yflags.sh -> _service:tar_scm:automake-1.17.tar.xz/t/yflags.sh Changed

Changes of Revision 2