~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-New in 1.12.3:
+New in 1.12.4:
* WARNING: Future backward-incompatibilities!
long-deprecated 'configure.in' name for the Autoconf input file.
You are advised to use the recommended name 'configure.ac' instead.
- - Starting from the next major Automake version (1.13), the rules to
- build pdf, ps and dvi output from Texinfo input will use the '--tidy'
- option by default. Since such an option was introduced in Texinfo
- 4.9, this means that Makefiles generated by future Automake versions
- will require at least that version of Texinfo.
+ - Support for the "Cygnus-style" trees (as enabled by the 'cygnus'
+ option) will be removed in the next major Automake release (1.13).
+
+ - The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will
+ be removed in Automake 1.13. The $(mkdir_p) make variable and the
+ @mkdir_p@ substitution will still remain available (as aliases of
+ $(MKDIR_P)) for the moment, for better backward compatibility.
+
+ - Autoconf 2.65 or later will be required by the next major Automake
+ version (1.13). Until now, Automake has required Autoconf version
+ 2.62 or later.
+
+ - Starting from the next major Automake version (1.13), the rules
+ to build pdf, ps and dvi output from Texinfo input will use the
+ '--build-dir' option by default. Since such an option was only
+ introduced in Texinfo 4.9, this means that Makefiles generated by
+ future Automake versions will require at least that version of
+ Texinfo.
- Starting from the next major Automake version (1.13), the parallel
testsuite harness (previously only enabled by the 'parallel-tests'
harness will still be available through the use of the 'serial-tests'
option.
- - Support for the two- and three-arguments invocation forms of the
- AM_INIT_AUTOMAKE macro is deprecated, and will be removed in the
- next major Automake version (1.13).
+ - The following long-obsolete m4 macros will be removed in the
+ next major Automake version (1.13):
+
+ AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
+ fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
+ fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
+ AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
+ ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
+ jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
+ ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
+ gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
+ fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
+ of the now-removed automatic de-ANSI-fication
+ support of Automake)
+
+ - All the "old alias" macros in 'm4/obsolete.m4' will be removed in
+ the next major Automake version (1.13).
- - The exact order in which the directories in the aclocal macro
- search path are looked up is probably going to be changed in the
- next Automake release (1.13).
+ - The '--acdir' option of aclocal is deprecated, and will probably
+ be removed in the next major Automake release (1.13). You should
+ use the options '--automake-acdir' and '--system-acdir' instead
+ (which have been introduced in Automake 1.11.2).
- The 'missing' script will not try anymore to update the timestamp
of out-of-date files that require a maintainer-specific tool to be
giving more useful warnings than a bare "command not found" from a
make recipe would.
+* Warnings and deprecations:
+
+ - Warnings in the 'obsolete' category are enabled by default both in
+ automake and aclocal.
+
+* Miscellaneous changes:
+
+ - Some testsuite weaknesses and spurious failures have been fixed.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.12.3:
+
* Miscellaneous changes:
- The '.m4' files provided by Automake does not define serial numbers
- Use of the long-deprecated two- and three-arguments invocation forms
of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
- category. Starting from the next major Automake release (1.13), such
- usages won't be allowed anymore.
+ category. Starting from some future major Automake release (likely
+ post-1.13), such usages won't be allowed anymore.
- Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
now deprecated (its use triggers a warning in the 'obsolete' category).