1 * WARNING: New versioning scheme for Automake.
3 - Beginning with the release 1.13.2, Automake has started to use a
4 more rational versioning scheme, that should allow users to know
5 which kind of changes can be expected from a new version, based
8 + Micro releases (e.g., 1.13.3, 2.0.1, 3.2.8) introduce only bug
9 and regression fixes and documentation updates; they should not
10 introduce new features, nor any backward-incompatibility (any
11 such incompatibility would be considered a bug, to be fixed with
12 a further micro release).
14 + Minor releases (e.g., 1.14, 2.1) can introduce new backward
15 compatible features; the only backward-incompatibilities allowed
16 in such a release are new *non-fatal* deprecations and warnings,
17 and possibly fixes for old or non-trivial bugs (or even inefficient
18 behaviours) that could unfortunately have been seen and used by
19 some as "corner case features". Possible disruptions caused by
20 this kind of fixes should hopefully be quite rare, and their
21 effects limited in scope.
23 + Major versions (now expected to be released every 18 or 24 months,
24 and not more often) can introduce new big features (possibly with
25 rough edges and not-fully-stabilized APIs), removal of deprecated
26 features, backward-incompatible changes of behaviour, and possibly
27 major refactorings (that, while ideally transparent to the user,
28 could introduce new bugs). Incompatibilities should however not
29 be introduced gratuitously and abruptly; a proper deprecation path
30 should be duly implemented in the preceding minor releases.
32 - According to this new scheme, the next major version of Automake
33 (the one that had previously been labelled as "1.14") will actually
34 become "Automake 2.0". Automake 1.14 has already been released as
35 the last minor release, and the present one is a bug-fixing release
36 following up on that one.
38 - See discussion about automake bug#13578 for more details and
39 background: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578>
41 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
43 * WARNING: Future backward-incompatibilities!
45 - Makefile recipes generated by Automake 2.0 will expect to use an
46 'rm' program that doesn't complain when called without any non-option
47 argument if the '-f' option is given (so that commands like "rm -f"
48 and "rm -rf" will act as a no-op, instead of raising usage errors).
49 This behavior of 'rm' is very widespread in the wild, and it will be
50 required in the next POSIX version:
52 <http://austingroupbugs.net/view.php?id=542>
54 Accordingly, AM_INIT_AUTOMAKE now expands some shell code that checks
55 that the default 'rm' program in PATH satisfies this requirement,
56 aborting the configure process if this is not the case. For the
57 moment, it's still possible to force the configuration process to
58 succeed even with a broken 'rm', that that will no longer be the case
61 - Automake 2.0 will require Autoconf 2.70 or later (which is still
62 unreleased at the moment of writing, but is planned to be released
63 before Automake 2.0 is).
65 - Automake 2.0 will drop support for the long-deprecated 'configure.in'
66 name for the Autoconf input file. You are advised to start using the
67 recommended name 'configure.ac' instead, ASAP.
69 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated in
70 Automake 2.0: it will raise warnings in the "obsolete" category (but
71 still no hard error of course, for compatibilities with the many, many
72 packages that still relies on that variable). You are advised to
73 start relying on the new Automake support for AC_CONFIG_MACRO_DIRS
74 instead (which was introduced in Automake 1.13).
76 - Automake 2.0 will remove support for automatic dependency tracking
77 with the SGI C/C++ compilers on IRIX. The SGI depmode has been
78 reported broken "in the wild" already, and we don't think investing
79 time in debugging and fixing is worthwhile, especially considering
80 that SGI has last updated those compilers in 2006, and is expected
81 to retire support for them in December 2013:
82 <http://www.sgi.com/services/support/irix_mips_support.html>
84 - Automake 2.0 will remove support for MS-DOS and Windows 95/98/ME
85 (support for them was offered by relying on the DJGPP project).
86 Note however that both Cygwin and MSYS/MinGW on modern Windows
87 versions will continue to be fully supported.
89 - Automake-provided scripts and makefile recipes might (finally!)
90 start assuming a POSIX shell in Automake 2.0. There still is no
91 certainty about this though: we'd first like to wait and see
92 whether future Autoconf versions will be enhanced to guarantee
93 that such a shell is always found and provided by the checks in
96 - Starting from Automake 2.0, third-party m4 files located in the
97 system-wide aclocal directory, as well as in any directory listed
98 in the ACLOCAL_PATH environment variable, will take precedence
99 over "built-in" Automake macros. For example (assuming Automake
100 is installed in the /usr/local hierarchy), a definition of the
101 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
102 should take precedence over the same-named automake-provided macro
103 (defined in '/usr/local/share/aclocal-2.0/vala.m4').
105 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
109 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
111 - The 'compile' script is now unconditionally required for all packages
112 that perform C compilation (if you are using the '--add-missing'
113 option, automake will fetch that script for you, so you shouldn't
114 need any explicit adjustment). This new behaviour is needed to avoid
115 obscure errors when the 'subdir-objects' option is used, and the
116 compiler is an inferior one that doesn't grasp the combined use of
117 both the "-c -o" options; see discussion about automake bug#13378 for
119 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
120 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
122 - The next major Automake version (2.0) will unconditionally activate
123 the 'subdir-objects' option. In order to smooth out the transition,
124 we now give a warning (in the category 'unsupported') whenever a
125 source file is present in a subdirectory but the 'subdir-object' is
126 not enabled. For example, the following usage will trigger such a
129 bin_PROGRAMS = sub/foo
130 sub_foo_SOURCES = sub/main.c sub/bar.c
132 - Automake will automatically enhance the autoconf-provided macro
133 AC_PROG_CC to force it to check, at configure time, that the
134 C compiler supports the combined use of both the '-c' and '-o'
135 options. The result of this check is saved in the cache variable
136 'am_cv_prog_cc_c_o', and said result can be overridden by
137 pre-defining that variable.
139 - The AM_PROG_CC_C_O macro can still be called, albeit that should no
140 longer be necessary. This macro is now just a thin wrapper around the
141 Automake-enhanced AC_PROG_CC. This means, among the other things,
142 that its behaviour is changed in three ways:
144 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
145 macro behind the scenes.
147 2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
148 and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
149 dynamically computed only at configure runtime (really!) from
150 the content of the '$CC' variable.
152 3. It no longer automatically AC_DEFINE the C preprocessor
153 symbol 'NO_MINUS_C_MINUS_O'.
157 - Automake can now be instructed to place '.info' files generated from
158 Texinfo input in the builddir rather than in the srcdir; this is done
159 specifying the new automake option 'info-in-builddir'. This feature
160 was requested by the developers of GCC, GDB, GNU binutils and the GNU
161 bfd library. See the extensive discussion about automake bug#11034
164 - For quite a long time, Automake has been implementing an undocumented
165 hack which ensured that '.info' files which appeared to be cleaned
166 (by being listed in the CLEANFILES or DISTCLEANFILES variables) were
167 built in the builddir rather than in the srcdir; this hack was
168 introduced to ensure better backward-compatibility with package
169 such as Texinfo, which do things like:
171 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
172 DISTCLEANFILES = texinfo texinfo-* info*.info*
173 # Do not create info files for distribution.
177 in order not to distribute generated '.info' files.
179 Now that we have the 'info-in-builddir' option that explicitly causes
180 generated '.info' files to be placed in the builddir, this hack should
181 be longer necessary, so we deprecate it with runtime warnings. It will
182 likely be removed altogether in Automake 2.0.
184 * Relative directory in Makefile fragments:
186 - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
187 (and their short versions, '%D%' and '%C%' respectively) can now be used
188 in an included Makefile fragment. The former is substituted with the
189 relative directory of the included fragment (compared to the top-level
190 including Makefile), and the latter with the canonicalized version of
191 the same relative directory.
194 bin_PROGRAMS = # will be updated by included Makefile fragments
195 include src/Makefile.inc
197 # in 'src/Makefile.inc':
198 bin_PROGRAMS += %reldir%/foo
199 %canon_reldir%_foo_SOURCES = %reldir%/bar.c
201 This should be especially useful for packages using a non-recursive
204 * Deprecated distribution formats:
206 - The 'shar' and 'compress' distribution formats are deprecated, and
207 scheduled for removal in Automake 2.0. Accordingly, the use of the
208 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
209 (in the 'obsolete' category), and the recipes of the Automake-generated
210 targets 'dist-shar' and 'dist-tarZ' will unconditionally display
211 (non-fatal) warnings at make runtime.
213 * New configure runtime warnings about "rm -f" support:
215 - To simplify transition to Automake 2.0, the shell code expanded by
216 AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
217 'rm' program in PATH doesn't complain when called without any
218 non-option argument if the '-f' option is given (so that commands like
219 "rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
220 If this is not the case, the configure script is aborted, to call the
221 attention of the user on the issue, and invite him to fix his PATH.
222 The checked 'rm' behavior is very widespread in the wild, and will be
223 required by future POSIX versions:
225 <http://austingroupbugs.net/view.php?id=542>
227 The user can still force the configure process to complete even in the
228 presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
229 environment variable to "yes". And the generated Makefiles should
230 still work correctly even when such broken 'rm' is used. But note
231 that this will no longer be the case with Automake 2.0 though, so, if
232 you encounter the warning, please report it to us ASAP (and try to fix
233 your environment as well).
235 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
241 - Fix a minor regression introduced in Automake 1.13.3: when two or more
242 user-defined suffix rules were present in a single Makefile.am,
243 automake would needlessly include definition of some make variables
244 related to C compilation in the generated Makefile.in (bug#14560).
246 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
250 * Documentation fixes:
252 - The documentation no longer mistakenly reports that the obsolete
253 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
254 to be removed in Automake 2.0.
258 - Byte-compilation of Emacs lisp files could fail spuriously on
259 Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
261 - If the same user-defined suffixes were transformed into different
262 Automake-known suffixes in different Makefile.am files in the same
263 project, automake could get confused and generate inconsistent
264 Makefiles (automake bug#14441).
265 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
266 and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
267 would have mistakenly placed into 'Makefile.in' rules to compile
268 "*.c" files into object files, and into 'sub/Makefile.in' rules to
269 compile "*.cc" files into object files --- rather than the other
270 way around. This is now fixed.
274 - The test cases no longer have the executable bit set. This should
275 make it clear that they are not meant to be run directly; as
276 explained in t/README, they can only be run through the custom
277 'runtest' script, or by a "make check" invocation.
279 - The testsuite has seen the introduction of a new helper function
280 'run_make', and several related changes. These serve a two-fold
283 1. Remove brittleness due to the use of "make -e" in test cases.
285 2. Seamlessly allow the use of parallel make ("make -j...") in the
286 test cases, even where redirection of make output is involved
287 (see automake bug#11413 for a description of the subtle issues
290 - Several spurious failures have been fixed (they hit especially
291 MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
292 #14498, #14499, #14500, #14501, #14517 and #14528.
294 - Some other minor miscellaneous changes and fixlets.
296 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
300 * Documentation fixes:
302 - The long-deprecated but still supported two-arguments invocation form
303 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
304 thing to do, given that support for such usage might need to remain
305 in place for an unspecified amount of time in order to cater to people
306 who want to define the version number for their package dynamically at
307 configure runtime (unfortunately, Autoconf does not yet support this
308 scenario, so we cannot delegate the work to it).
310 - The serial testsuite harness is no longer reported as "deprecated",
311 but as "discouraged". We have no plan to remove it, nor to make its
312 use cause runtime warnings.
314 - The parallel testsuite is no longer reported as "experimental"; it
315 is well tested, and should be stable now.
317 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
318 'dist-tarZ' options are obsolescent, and their use is deprecated
319 in the documentation.
321 - Other minor miscellaneous fixes and improvements; in particular,
322 some improvements in cross-references.
324 * Obsolescent features:
326 - Use of suffix-less info files (that can be specified through the
327 '@setfilename' macro in Texinfo input files) is discouraged, and
328 its use will raise warnings in the 'obsolete' category. Simply
329 use the '.info' extension for all your info files, transforming
332 @setfilename myprogram
336 @setfilename myprogram.info
338 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
339 is discouraged, and its use will raise warnings in the 'obsolete'
340 category. You are advised to simply use the '.texi' extension
345 - When the 'ustar' option is used, the generated configure script no
346 longer risks hanging during the tests for the availability of the
347 'pax' utility, even if the user running configure has a UID or GID
348 that requires more than 21 bits to be represented.
349 See automake bug#8343 and bug#13588.
351 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
352 again, as they did in Automake 1.12.x (albeit printing runtime
353 warnings in the 'obsolete' category). Removing them has turned
354 out to be a very bad idea, because it complicated distro packing
355 enormously. Making them issue fatal warnings, as we did in
356 Automake 1.13, has turned out to be a similarly very bad idea,
357 for exactly the same reason.
359 - aclocal will no longer error out if the first local m4 directory
360 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
361 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
362 a warning in the 'unsupported' category. This is done to support
363 some pre-existing real-world usages. See automake bug#13514.
365 - aclocal will no longer consider directories for extra m4 files more
366 than once, even if they are specified multiple times. This ensures
367 packages that specify both
369 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
370 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
372 will work correctly, even when the 'm4' directory contains no
373 package-specific files, but is used only to install third-party
374 m4 files (as can happen with e.g., "libtoolize --install").
375 See automake bug#13514.
377 - Analysis of make flags in Automake-generated rules has been made more
378 robust, and more future-proof. For example, in presence of make that
379 (like '-I') take an argument, the characters in said argument will no
380 longer be spuriously considered as a set of additional make options.
381 In particular, automake-generated rules will no longer spuriously
382 believe to be running in dry mode ("make -n") if run with an invocation
383 like "make -I noob"; nor will they believe to be running in keep-going
384 mode ("make -k") if run with an invocation like "make -I kool"
385 (automake bug#12554).
387 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
393 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
394 causes a clear and helpful error message, instead of obscure ones
395 (issue introduced in Automake 1.13).
397 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
403 - ylwrap renames properly header guards in generated header files
404 (*.h), instead of leaving Y_TAB_H.
406 - ylwrap now also converts header guards in implementation files
407 (*.c). Because ylwrap failed to rename properly #include in the
408 implementation files, current versions of Bison (e.g., 2.7)
409 duplicate the generated header file in the implementation file.
410 The header guard then protects the implementation file from
411 duplicate definitions from the header file.
413 * Version requirements:
415 - Autoconf 2.65 or greater is now required.
417 - The rules to build PDF and DVI output from Texinfo input now
418 require Texinfo 4.9 or later.
422 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
423 option) has been removed. See discussion about automake bug#11034
424 for more background: <http://debbugs.gnu.org/11034>.
426 - The deprecated aclocal option '--acdir' has been removed. You
427 should use the options '--automake-acdir' and '--system-acdir'
428 instead (which have been introduced in Automake 1.11.2).
430 - The following long-obsolete m4 macros have been removed:
432 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
433 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
434 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
435 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
436 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
437 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
438 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
439 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
440 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
441 of the now-removed automatic de-ANSI-fication
444 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
446 - Use of the long-deprecated two- and three-arguments invocation forms
447 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
448 though (albeit with a warning in the 'obsolete' category), to cater
449 for people who want to define the version number for their package
450 dynamically (e.g., from the current VCS revision). We'll have to
451 continue this support until Autoconf itself is fixed to allow better
452 support for such dynamic version numbers.
454 * Elisp byte-compilation:
456 - The byte compilation of '.el' files into '.elc' files is now done
457 with a suffix rule. This has simplified the compilation process, and
458 more importantly made it less brittle. The downside is that emacs is
459 now invoked once for each '.el' files, which cause some noticeable
460 slowdowns. These should however be mitigated on multicore machines
461 (which are becoming the norm today) if concurrent make ("make -j")
464 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
465 files in the same subdirectory; for example, byte-compiling of file
466 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
467 'foo.elc'. This behaviour is backward-incompatible with older
468 Automake versions, but it is more natural and more sane. See also
471 - The Emacs invocation performing byte-compilation of '.el' files honors
472 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
473 one is developer-reserved and the latter one user-reserved.
475 - The 'elisp-comp' script, once provided by Automake, has been rendered
476 obsoleted by the just-described changes, and thus removed.
478 * Changes to Automake-generated testsuite harnesses:
480 - The parallel testsuite harness (previously only enabled by the
481 'parallel-tests' option) is the default one; the older serial
482 testsuite harness will still be available through the use of the
483 'serial-tests' option (introduced in Automake 1.12).
485 - The 'color-tests' option is now unconditionally activated by default.
486 In particular, this means that testsuite output is now colorized by
487 default if the attached terminal seems to support ANSI escapes, and
488 that the user can force output colorization by setting the variable
489 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
490 for backward-compatibility, although it's a handled as a no-op now.
492 * Silent rules support:
494 - Support for silent rules is now always active in Automake-generated
495 Makefiles. So, although the verbose output is still the default,
496 the user can now always use "./configure --enable-silent-rules" or
497 "make V=0" to enable quieter output in the package he's building.
499 - The 'silent-rules' option has now become a no-op, preserved for
500 backward-compatibility only. In particular, its use no longer
501 disables the warnings in the 'portability-recursive' category.
505 - The rules to build PDF and DVI files from Texinfo input now require
506 Texinfo 4.9 or later.
508 - The rules to build PDF and DVI files from Texinfo input now use the
509 '--build-dir' option, to keep the auxiliary files used by texi2dvi
510 and texi2pdf around without cluttering the build directory, and to
511 make it possible to run the "dvi" and "pdf" recipes in parallel.
513 * Automatic remake rules and 'missing' script:
515 - The 'missing' script no longer tries to update the timestamp of
516 out-of-date files that require a maintainer-specific tool to be
517 remade, in case the user lacks such a tool (or has a too-old version
518 of it). It just gives a useful warning, and in some cases also a
519 tip about how to obtain such a tool.
521 - The missing script has thus become useless as a (poor) way to work
522 around the sketched-timestamps issues that can happen for projects
523 that keep generated files committed in their VCS repository. Such
524 projects are now encouraged to write a custom "fix-timestamps.sh"
525 script to avoid such issues; a simple example is provided in the
526 "CVS and generated files" chapter of the automake manual.
530 - The user can now define his own recursive targets that recurse
531 in the directories specified in $(SUBDIRS). This can be done by
532 specifying the name of such targets in invocations of the new
533 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
537 - Any failure in the recipe of the "tags", "ctags", "cscope" or
538 "cscopelist" targets in a subdirectory is now propagated to the
539 top-level make invocation.
541 - Tags are correctly computed also for files in _SOURCES variables that
542 only list files with non-standard suffixes (see automake bug#12372).
544 * Improvements to aclocal and related rebuilds rules:
546 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
547 are now traced by aclocal, and can be used to declare the local m4
548 include directories. Formerly, one had to specify it with an explicit
549 '-I' option to the 'aclocal' invocation.
551 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
552 Automake versions will warn about its use, and later version will
553 remove support for it altogether.
555 * The depcomp script:
557 - Dropped support for libtool 1.4.
559 - Various internal refactorings. They should cause no visible change,
560 but the chance for regression is there anyway, so please report any
561 unexpected or suspicious behaviour.
563 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
564 This should cause no problem, since icc 8.0 has been released in
565 December 2003 -- almost nine years ago.
567 - Support for tcc (the Tiny C Compiler) has been improved, and is now
568 handled through a dedicated 'tcc' mode.
572 - ylwrap generates header guards with a single '_' for series of non
573 alphabetic characters, instead of several. This is what Bison >=
576 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
578 Bugs fixed in 1.12.6:
580 * Python-related bugs:
582 - The default installation location for python modules has been improved
583 for Python 3 on Debian and Ubuntu systems, changing from:
585 ${prefix}/lib/python3/dist-packages
589 ${prefix}/lib/python3.x/site-packages
591 This change should ensure modules installed using the default ${prefix}
592 "/usr/local" are found by default by system python 3.x installations.
593 See automake bug#10227.
595 - Python byte-compilation supports the new layout mandated by PEP-3147,
596 with its __pycache__ directory (automake bug#8847).
598 * Build system issues:
600 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
601 Automake's own build system works correctly again (bug introduced
606 - The Vala-related tests has been changed to adjust to the removal of
607 the 'posix' profile in the valac compiler. See automake bug#12934
610 - Some spurious testsuite failures related to older tools and systems
613 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
619 - The AM_PROG_VALAC macro has been enhanced to takes two further
620 optional arguments; it's signature now being
622 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
623 [ACTION-IF-NOT-FOUND])
625 - By default, AM_PROG_VALAC no longer aborts the configure invocation
626 if the Vala compiler found is too old, but simply prints a warning
627 messages (as it did when the Vala compiler was not found). This
628 should avoid unnecessary difficulties for end users that just want
629 to compile the unmodified, distributed Vala-generated C sources,
630 but happens to have an old Vala compiler in their PATH. This fixes
633 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
634 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
635 This is a better default, because with it a triggered makefile rule
636 invoking a Vala compilation will clearly fail with an informative error
637 message like "valac: command not found", rather than silently, with
638 the error possibly going unnoticed or triggering harder-to-diagnose
639 fallout failures in later steps.
641 * Miscellaneous changes:
643 - automake and aclocal no longer honours the 'perllibdir' environment
644 variable. That had always been intended only as an hack required in
645 the testsuite, not meant for any use beyond that.
647 Bugs fixed in 1.12.5:
649 * Long-standing bugs:
651 - Automake no longer generates spurious remake rules invoking autoheader
652 to regenerate the template corresponding to header files specified after
653 the first one in AC_CONFIG_HEADERS (automake bug#12495).
655 - When wrapping Microsoft tools, the 'compile' script falls back to
656 finding classic 'libname.a' style libraries when 'name.lib' and
657 'name.dll.lib' aren't available.
659 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
663 * Warnings and deprecations:
665 - Warnings in the 'obsolete' category are enabled by default both in
666 automake and aclocal.
668 * Miscellaneous changes:
670 - Some testsuite weaknesses and spurious failures have been fixed.
672 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
676 * Miscellaneous changes:
678 - The '.m4' files provided by Automake no longer define serial numbers.
679 This should cause no difference in the behaviour of aclocal though.
681 - Some testsuite weaknesses and spurious failures have been fixed.
683 - There is initial support for automatic dependency tracking with the
684 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
686 Bugs fixed in 1.12.3:
688 * Long-standing bugs:
690 - Instead of renaming only self-references of files (typically for
691 #lines), ylwrap now also renames references to the other generated
692 files. This fixes support for GLR and C++ parsers from Bison (PR
693 automake/491 and automake bug#7648): 'parser.c' now properly
694 #includes 'parser.h' instead of 'y.tab.h'.
696 - Generated files unknown to ylwrap are now preserved. This fixes
697 C++ support for Bison (automake bug#7648): location.hh and the
698 like are no longer discarded.
700 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
704 * Warnings and deprecations:
706 - Automake now issues a warning (in the 'portability' category) if
707 'configure.in' is used instead of 'configure.ac' as the Autoconf
708 input file. Such a warning will also be present in the next
709 Autoconf version (2.70).
713 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
714 order (as done by the other recursive rules), rather than in the
715 inverse order. They used to do that in order to work a round a
716 limitation in an older implementation of the automatic dependency
717 tracking support, but that limitation had been lifted years ago
718 already, when the automatic dependency tracking based on side-effects
719 of compilation had been introduced.
721 - Cleaning rules for compiled objects (both "plain" and libtool) work
722 better when subdir objects are involved, not triggering a distinct
723 'rm' invocation for each such object. They do so by removing *any*
724 compiled object file that is in the same directory of a subdir
725 object. See automake bug#10697.
727 * Silent rules support:
729 - A new predefined $(AM_V_P) make variable is provided; it expands
730 to a shell conditional that can be used in recipes to know whether
731 make is being run in silent or verbose mode.
733 Bugs fixed in 1.12.2:
735 * SECURITY VULNERABILITIES!
737 - The 'distcheck' recipe no longer grants temporary world-write
738 permissions on the extracted distdir. Even if such rights were
739 only granted for a vanishingly small time window, the implied
740 race condition proved to be enough to allow a local attacker
741 to run arbitrary code with the privileges of the user running
742 "make distcheck". This is CVE-2012-3386.
744 * Long-standing bugs:
746 - The "recheck" targets behaves better in the face of build failures
747 related to previously failed tests. For example, if a test is a
748 compiled program that must be rerun by "make recheck", and its
749 compilation fails, it will still be rerun by further "make recheck"
750 invocations. See automake bug#11791.
752 * Bugs introduced by 1.12.1:
754 - Automake provides once again the '$(mkdir_p)' make variable and the
755 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
756 for better backward-compatibility.
758 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
762 * New supported languages:
764 - Support for Objective C++ has been added; it should work similarly to
765 the support for Objective C.
767 * Deprecated obsolescent features:
769 - Use of the long-deprecated two- and three-arguments invocation forms
770 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
771 category. Starting from some future major Automake release (likely
772 post-1.13), such usages will no longer be allowed.
774 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
775 now deprecated (its use triggers a warning in the 'obsolete' category).
776 It will be removed in the next major Automake release (1.13).
778 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
779 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
780 m4 macro are deprecated, eliciting a warning in the 'obsolete'
783 * Miscellaneous changes:
785 - The Automake test cases now require a proper POSIX-conforming shell.
786 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
787 be accepted. In most cases, the user shouldn't have to specify such
788 POSIX shell explicitly, since it will be looked up at configure time.
789 Still, when this lookup fails, or when the user wants to override its
790 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
791 to the shell that will be used to run the Automake test cases).
793 Bugs fixed in 1.12.1:
795 * Bugs introduced by 1.12:
797 - Several weaknesses in Automake's own build system and test suite
800 * Bugs introduced by 1.11.3:
802 - When given non-option arguments, aclocal rejects them, instead of
803 silently ignoring them.
805 * Long-standing bugs:
807 - When the 'color-tests' option is in use, forcing of colored testsuite
808 output through "AM_COLOR_TESTS=always" works even if the terminal is
809 a non-ANSI one, i.e., if the TERM environment variable has a value of
812 - Several inefficiencies and poor performances in the implementation
813 of the parallel-tests 'check' and 'recheck' targets have been fixed.
815 - The post-processing of output "#line" directives done the ylwrap
816 script is more faithful w.r.t. files in a subdirectory; for example,
817 if the processed file is "src/grammar.y", ylwrap will correctly
818 produce directives like:
819 #line 7 "src/grammar.y"
824 * Bugs with new Perl versions:
826 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
828 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
832 * Obsolete features removed:
834 - The never documented nor truly used script 'acinstall' has been
837 - Support for automatic de-ANSI-fication has been removed.
839 - The support for the "obscure" multilib feature has been removed
840 from Automake core (but remains available in the 'contrib/'
841 directory of the Automake distribution).
843 - Support for ".log -> .html" conversion and the check-html and
844 recheck-html targets has been removed from Automake core (but
845 remains available in the 'contrib/' directory of the Automake
848 - The deprecated 'lzma' compression format for distribution archives
849 has been removed, in favor of 'xz' and 'lzip'.
851 - The obsolete AM_WITH_REGEX macro has been removed.
853 - The long-deprecated options '--output-dir', '--Werror' and
854 '--Wno-error' have been removed.
856 - The chapter on the history of Automake has been moved out of the
857 reference manual, into a new dedicated Texinfo file.
861 - New 'cscope' target to build a cscope database for the source tree.
863 * Changes to Automake-generated testsuite harnesses:
865 - The new automake option 'serial-tests' has been introduced. It can
866 be used to explicitly instruct automake to use the older serial
867 testsuite harness. This is still the default at the moment, but it
868 might change in future versions.
870 - The 'recheck' target (provided by the parallel testsuite harness) now
871 depends on the 'all' target. This allows for a better user-experience
872 in test-driven development. See automake bug#11252.
874 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
875 and unexpected or internal error, or a failure to set up the test case
876 scenario) have their outcome reported as an 'ERROR' now. Previous
877 versions of automake reported such an outcome as a 'FAIL' (the only
878 difference with normal failures being that hard errors were counted
879 as failures even when the test originating them was listed in
882 - The testsuite summary displayed by the parallel-test harness has a
883 completely new format, that always list the numbers of passed, failed,
884 xfailed, xpassed, skipped and errored tests, even when these numbers
885 are zero (but using smart coloring when the color-tests option is in
888 - The default testsuite driver offered by the 'parallel-tests' option is
889 now implemented (partly at least) with the help of automake-provided
890 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
891 on code in the generated Makefile.in.
892 This has two noteworthy implications. The first one is that projects
893 using the 'parallel-tests' option should now either run automake with
894 the '--add-missing' option, or manually copy the 'test-driver' script
895 into their tree. The second, and more important, implication is that
896 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
897 no longer be used to define a test runner, and the command specified
898 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
899 program or script. For example, this is still a valid usage (albeit
902 TESTS_ENVIRONMENT = \
903 if test -n '$(STRICT_TESTS)'; then \
904 maybe_errexit='-e'; \
908 LOG_COMPILER = $(SHELL) $$maybe_errexit
910 OTOH, this is no longer a valid usage:
912 TESTS_ENVIRONMENT = \
913 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
917 TESTS_ENVIRONMENT = \
918 run_with_perl_or_shell () \
920 if grep -q '^#!.*perl' $$1; then
926 LOG_COMPILER = run_with_perl_or_shell
928 - The package authors can now use customary testsuite drivers within
929 the framework provided by the 'parallel-tests' testsuite harness.
930 Consistently with the existing syntax, this can be done by defining
931 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
933 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
934 to redirect/define file descriptors used by the test scripts.
936 - The parallel-tests harness generates now, in addition the '.log' files
937 holding the output produced by the test scripts, a new set of '.trs'
938 files, holding "metadata" derived by the execution of the test scripts;
939 among such metadata are the outcomes of the test cases run by a script.
941 - Initial and still experimental support for the TAP test protocol is
944 * Changes to Yacc and Lex support:
946 - C source and header files derived from non-distributed Yacc and/or
947 Lex sources are now removed by a simple "make clean" (while they were
948 previously removed only by "make maintainer-clean").
950 - Slightly backward-incompatible change, relevant only for use of Yacc
951 with C++: the extensions of the header files produced by the Yacc
952 rules are now modelled after the extension of the corresponding
953 sources. For example, yacc files named "foo.y++" and "bar.yy" will
954 produce header files named "foo.h++" and "bar.hh" respectively, where
955 they would have previously produced header files named simply "foo.h"
956 and "bar.h". This change offers better compatibility with 'bison -o'.
958 * Miscellaneous changes:
960 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
961 rather than 1, if the vala compiler found is too old.
963 - The build system of Automake itself now avoids the use of make
964 recursion as much as possible.
966 - Automake now prefers to quote 'like this' or "like this", rather
967 than `like this', in diagnostic message and generated Makefiles,
968 to accommodate the new GNU Coding Standards recommendations.
970 - Automake has a new option '--print-libdir' that prints the path of the
971 directory containing the Automake-provided scripts and data files.
973 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
975 - The rules to create pdf, dvi and ps output from Texinfo files now
976 works better with modern 'texi2dvi' script, by explicitly passing
977 it the '--clean' option to ensure stray auxiliary files are not
978 left to clutter the build directory.
980 - Automake can now generate silenced rules for texinfo outputs.
982 - Some auxiliary files that are automatically distributed by Automake
983 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
984 C sources) might now be listed in the DIST_COMMON variable in many
985 Makefile.in files, rather than in the top-level one.
987 - Messages of types warning or error from 'automake' and 'aclocal'
988 are now prefixed with the respective type, and presence of -Werror
991 - Automake's early configure-time sanity check now tries to avoid
992 sleeping for a second, which slowed down cached configure runs
993 noticeably. In that case, it will check back at the end of the
994 configure script to ensure that at least one second has passed, to
995 avoid time stamp issues with makefile rules rerunning autotools
998 - The warnings in the category 'extra-portability' are now enabled by
999 '-Wall'. In previous versions, one has to use '-Wextra-portability'
1004 - Various minor bugfixes for recent or long-standing bugs.
1006 * Bugs introduced by 1.11:
1008 - The AM_COND_IF macro also works if the shell expression for the
1009 conditional is no longer valid for the condition.
1011 - The automake-provided parallel testsuite harness no longer fails
1012 with BSD make used in parallel mode when there are test scripts in
1013 a subdirectory, like in:
1015 TESTS = sub/foo.test sub/bar.test
1017 * Long-standing bugs:
1019 - Automake's own build system finally have a real "installcheck" target.
1021 - Vala-related cleanup rules are now more complete, and work better in
1024 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
1025 now automatically distributed also if the directory of the auxiliary
1026 files coincides with the top-level directory.
1028 - Automake now detects the presence of the '-d' flag in the various
1029 '*YFLAGS' variables even when their definitions involve indirections
1030 through other variables, such as in:
1032 AM_YFLAGS = $(foo_opts)
1034 - Automake now complains if a '*YFLAGS' variable has any conditional
1035 content, not only a conditional definition.
1037 - Explicit enabling and/or disabling of Automake warning categories
1038 through the '-W...' options now always takes precedence over the
1039 implicit warning level implied by Automake strictness (foreign, gnu
1040 or gnits), regardless of the order in which such strictness and
1041 warning flags appear. For example, a setting like:
1042 AUTOMAKE_OPTIONS = -Wall --foreign
1043 will cause the warnings in category 'portability' to be enabled, even
1044 if those warnings are by default disabled in 'foreign' strictness.
1046 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1048 Bugs fixed in 1.11.5:
1050 * Bugs introduced by 1.11.3:
1052 - Vala files with '.vapi' extension are now recognized and handled
1053 correctly again. See automake bug#11222.
1055 - Vala support work again for projects that contain some program
1056 built from '.vala' (and possibly '.c') sources and some other
1057 program built from '.c' sources *only*. See automake bug#11229.
1059 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1063 * Miscellaneous changes:
1065 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
1066 symbol index) modifiers as well as the "s" action, as the symbol index
1067 is created unconditionally by Microsoft lib. Also, the "q" (quick)
1068 action is now a synonym for "r" (replace). Also, the script has been
1069 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
1071 - When the 'compile' script is used to wrap MSVC, it now accepts an
1072 optional space between the -I, -L and -l options and their respective
1073 arguments, for better POSIX compliance.
1075 - There is an initial, experimental support for automatic dependency
1076 tracking with tcc (the Tiny C Compiler). Its associated depmode is
1077 currently recognized as "icc" (but this and other details are likely
1078 to change in future versions).
1080 - Automatic dependency tracking now works also with the IBM XL C/C++
1081 compilers, thanks to the new new depmode 'xlc'.
1083 Bugs fixed in 1.11.4:
1085 * Bugs introduced by 1.11.2:
1087 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
1088 no longer cause spurious failures upon "make install".
1090 - The user can now instruct the 'uninstall-info' rule not to update
1091 the '${infodir}/dir' file by exporting the environment variable
1092 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
1093 with how the 'install-info' rule operates since automake 1.11.2.
1095 * Long-standing bugs:
1097 - It is now possible for a foo_SOURCES variable to hold Vala sources
1098 together with C header files, as well as with sources and headers for
1099 other supported languages (e.g., C++). Previously, only mixing C and
1100 Vala sources was supported.
1102 - If "aclocal --install" is used, and the first directory specified with
1103 '-I' is non-existent, aclocal will now create it before trying to copy
1106 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
1107 install rules to create an empty $(foodir) directory; for example, if
1108 Makefile.am contains something like:
1110 pkglibexec_SCRIPTS =
1112 pkglibexec_SCRIPTS += bar.sh
1115 the $(pkglibexec) directory will not be created upon "make install".
1117 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1121 * Miscellaneous changes:
1123 - Automake's own build system is more silent by default, making use of
1124 the 'silent-rules' option.
1126 - The master copy of the 'gnupload' script is now maintained in gnulib,
1129 - The 'missing' script no longer tries to wrap calls to 'tar'.
1131 - "make dist" no longer wraps 'tar' invocations with the 'missing'
1132 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
1133 shouldn't be using BTW ;-) no longer invokes the 'missing' script
1134 to wrap tar, but simply invokes the 'tar' program itself.
1136 - "make dist" can now create lzip-compressed tarballs.
1138 - In the Automake info documentation, the Top node and the nodes about
1139 the invocation of the automake and aclocal programs have been renamed;
1140 now, calling "info automake" will open the Top node, while calling
1141 "info automake-invocation" and "info aclocal-invocation" will access
1142 the nodes about the invocation of respectively automake and aclocal.
1144 - Automake is now distributed as a gzip-compressed and an xz-compressed
1145 tarball. Previously, bzip2 was used instead of xz.
1147 - The last relics of Python 1.5 support have been removed from the
1148 AM_PATH_PYTHON macro.
1150 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
1151 and adds them to the normal list of dependencies, but without
1152 overwriting the foo_DEPENDENCIES variable, which is normally computed
1155 Bugs fixed in 1.11.3:
1157 * Bugs introduced by 1.11.2:
1159 - Automake now correctly recognizes the prefix/primary combination
1160 'pkglibexec_SCRIPTS' as valid.
1162 - The parallel-tests harness no longer trips on sed implementations
1163 with stricter limits on the length of input lines (problem seen at
1164 least on Solaris 8).
1166 * Long-standing bugs:
1168 - The "deleted header file problem" for *.am files is avoided by stub
1169 rules. This allows 'make' to trigger a rerun of 'automake' also if
1170 some previously needed '.am' file has been removed.
1172 - The 'silent-rules' option now generates working makefiles even
1173 for the uncommon 'make' implementations that do not support the
1174 nested-variables extension to POSIX 2008. For such 'make'
1175 implementations, whether a build is silent is determined at
1176 configure time, and cannot be overridden at make time with
1177 "make V=0" or "make V=1".
1179 - Vala support now works better in VPATH setups.
1181 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1185 * Changes to aclocal:
1187 - The `--acdir' option is deprecated. Now you should use the new options
1188 `--automake-acdir' and `--system-acdir' instead.
1190 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1191 colon-separated list of additional directories to search after the
1192 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1193 and before the system acdir (by default ${prefix}/share/aclocal).
1195 * Miscellaneous changes:
1197 - The Automake support for automatic de-ANSI-fication has been
1198 deprecated. It will probably be removed in the next major Automake
1201 - The `lzma' compression scheme and associated automake option `dist-lzma'
1202 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1204 - You may adjust the compression options used in dist-xz and dist-bzip2.
1205 The default is now merely -e for xz, but still -9 for bzip; you may
1206 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1207 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1209 - The `compile' script now converts some options for MSVC for a better
1210 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1212 - The py-compile script now accepts empty arguments passed to the options
1213 `--destdir' and `--basedir', and complains about unrecognized options.
1214 Moreover, a non-option argument or a special `--' argument terminates
1215 the list of options.
1217 - A developer that needs to pass specific flags to configure at "make
1218 distcheck" time can now, and indeed is advised to, do so by defining
1219 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1220 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1221 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1222 user; still, the old Makefile.am files that used to define it will
1223 still continue to work as before.
1225 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1226 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1227 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1228 is run with -Wextra-portability and -Werror.
1230 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1231 file generated by automake-provided rules by defining the special make
1232 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1234 - The `install-info' rule can now be instructed not to create/update
1235 the `${infodir}/dir' file, by exporting the new environment variable
1236 `AM_UPDATE_INFO_DIR' to the value "no".
1238 Bugs fixed in 1.11.2:
1240 * Bugs introduced by 1.11:
1242 - The parallel-tests driver no longer produces erroneous results with
1243 Tru64/OSF 5.1 sh upon unreadable log files.
1245 - The `parallel-tests' test driver does not report spurious successes
1246 when used with concurrent FreeBSD make (e.g., "make check -j3").
1248 - When the parallel-tests driver is in use, automake now explicitly
1249 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1250 instead of issuing confusing and apparently unrelated error messages
1251 (e.g., "non-POSIX variable name", "bad characters in variable name",
1252 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1253 silently producing broken `Makefile.in' files.
1255 - The `silent-rules' option now truly silences all compile rules, even
1256 when dependency tracking is disabled. Also, when `silent-rules' is
1257 not used, `make' output no longer contains spurious backslash-only
1258 lines, thus once again matching what Automake did before 1.11.
1260 - The AM_COND_IF macro also works if the shell expression for the
1261 conditional is no longer valid for the condition.
1263 * Long-standing bugs:
1265 - The order of Yacc and Lex flags is fixed to be consistent with other
1266 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1267 $(LFLAGS), so that the user variables override the developer variables.
1269 - "make distcheck" now correctly complains also when "make uninstall"
1270 leaves one and only one file installed in $(prefix).
1272 - A "make uninstall" issued before a "make install", or after a mere
1273 "make install-data" or a mere "make install-exec" does not spuriously
1276 - Automake now warns about more primary/directory invalid combinations,
1277 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1279 - Rules generated by Automake now try harder to not change any files when
1280 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1281 Yacc source files and the rule to update config.h.
1283 - Several scripts and the parallel-tests testsuite driver now exit with
1284 the right exit status upon receiving a signal.
1286 - A per-Makefile.am setting of -Werror does not erroneously carry over
1287 to the handling of other Makefile.am files.
1289 - The code for automatic dependency tracking works around a Solaris
1290 make bug triggered by sources containing repeated slashes when the
1291 `subdir-objects' option was used.
1293 - The makedepend and hp depmodes now work better with VPATH builds.
1295 - Java sources specified with check_JAVA are no longer compiled for
1296 "make all", but only for "make check".
1298 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1299 and error out if `javadir' is undefined, instead of silently producing
1300 a broken Makefile.in.
1302 - aclocal and automake now honour the configure-time definitions of
1303 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1305 - The `install-info' recipe no longer tries to guess whether the
1306 `install-info' program is from Debian or from GNU, and adaptively
1307 change its behaviour; this has proven to be frail and easy to
1310 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1312 Bugs fixed in 1.11.1:
1314 - Lots of minor bugfixes.
1316 * Bugs introduced by 1.11:
1318 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1319 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1321 * Long standing bugs:
1323 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1324 even if the `--prefix' argument pointed outside of a system directory.
1325 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1326 `get_python_lib' function if it points outside the configured prefix,
1327 unless the `--prefix' argument was either `/usr' or below `/System'.
1329 - The testsuite does not try to change the mode of `ltmain.sh' files from
1330 a Libtool installation (symlinked to test directories) any more.
1332 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1333 tools are preferred in a cross-compile setup.
1335 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1336 This fixes a race condition where untrusted users could modify files
1337 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1338 build directory was world-searchable. This is CVE-2009-4029.
1340 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1344 * Version requirements:
1346 - Autoconf 2.62 or greater is required.
1348 * Changes to aclocal:
1350 - The autoconf version check implemented by aclocal in aclocal.m4
1351 (and new in Automake 1.10) is degraded to a warning. This helps
1352 in the common case where the Autoconf versions used are compatible.
1354 * Changes to automake:
1356 - The automake program can run multiple threads for creating most
1357 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1358 with interpreter-based threads enabled. Set the environment variable
1359 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1360 enable this experimental feature.
1362 * Changes to Libtool support:
1364 - Libtool generic flags are now passed to the install and uninstall
1367 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1368 config.lt is removed correctly now.
1370 * Languages changes:
1372 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1373 Fortran, and Ratfor).
1375 - For files with extension .f90, .f95, .f03, or .f08, the flag
1376 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1378 - Files with extension .sx are also treated as preprocessed assembler.
1380 - The default source file extension (.c) can be overridden with
1381 AM_DEFAULT_SOURCE_EXT now.
1383 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1386 - AM_PATH_PYTHON honors python's idea about the site directory.
1388 - There is initial support for the Vala programming language, when using
1389 Vala 0.7.0 or later.
1391 * Miscellaneous changes:
1393 - Automake development is done in a git repository on Savannah now, see
1395 http://git.sv.gnu.org/gitweb/?p=automake.git
1397 A read-only CVS mirror is provided at
1399 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1400 checkout -d automake HEAD
1402 - "make dist" can now create xz-compressed tarballs,
1403 as well as (deprecated?) lzma-compressed tarballs.
1405 - `automake --add-missing' will by default install the GPLv3 file as
1406 COPYING if it is missing. It will also warn that the license file
1407 should be added to source control. Note that Automake will never
1408 overwrite an existing COPYING file, even when the `--force-missing'
1411 - The manual is now distributed under the terms of the GNU FDL 1.3.
1413 - Automake ships and installs man pages for automake and aclocal now.
1415 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1417 - install-sh supports -C, which does not update the installed file
1418 (and its time stamps) if the contents did not change.
1420 - The `gnupload' script has been revamped.
1422 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1424 - The targets `install' and `uninstall' are more efficient now, in that
1425 for example multiple files from one Automake variable such as
1426 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1427 invocation if they do not have to be renamed.
1429 Both install and uninstall may sometimes enter (`cd' into) the target
1430 installation directory now, when no build-local scripts are used.
1432 Both install and uninstall do not fail anymore but do nothing if an
1433 installation directory variable like `bindir' is set to the empty string.
1435 For built-in rules, `make install' now fails reliably if installation
1436 of a file failed. Conversely, `make uninstall' even succeeds when
1437 issued multiple times.
1439 These changes may need some adjustments from users: For example,
1440 some `install' programs refuse to install multiple copies of the
1441 same file in one invocation, so you may need to remove duplicate
1442 entries from file lists.
1444 Also, within one set of files, say, nobase_data_DATA, the order of
1445 installation may be changed, or even unstable among different hosts,
1446 due to the use of associative arrays in awk. The increased use of
1447 awk matches a similar move in Autoconf to provide for better scaling.
1449 Further, most undocumented per-rule install command variables such as
1450 binSCRIPT_INSTALL have been removed because they are not needed any
1451 more. Packages which use them should be using the appropriate one of
1452 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1453 counterpart, depending on the type of files and the need for automatic
1454 target directory creation.
1456 - The "deleted header file problem" for *.m4 files is avoided by
1457 stub rules. This allows `make' to trigger a rerun of `aclocal'
1458 also if some previously needed macro file has been removed.
1460 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1461 an otherwise up to date tree.
1463 - The `color-tests' option causes colored test result output on terminals.
1465 - The `parallel-tests' option enables a new test driver that allows for
1466 parallel test execution, inter-test dependencies, lazy test execution
1467 for unit-testing, re-testing only failed tests, and formatted result output
1468 as RST (reStructuredText) and HTML. Enabling this option may require some
1469 changes to your test suite setup; see the manual for details.
1471 - The `silent-rules' option enables Linux kernel-style silent build output.
1472 This option requires the widely supported but non-POSIX `make' feature
1473 of recursive variable expansion, so do not use it if your package needs
1474 to build with `make' implementations that do not support it.
1476 To enable less verbose build output, the developer has to use the Automake
1477 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1478 macro. The user may then set the default verbosity by passing the
1479 `--enable-silent-rules' option to `configure'. At `make' run time, this
1480 default may be overridden using `make V=0' for less verbose, and `make V=1'
1481 for backward-compatible verbose output.
1483 - New prefix `notrans_' for manpages which should not be transformed
1484 by --program-transform.
1486 - New macro AM_COND_IF for conditional evaluation and conditional
1489 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1490 remove the file in a non-VPATH build. Such setups work with Autoconf
1493 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1494 the default setting.
1496 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1497 useful especially for multi-line values.
1499 - Automake's early configure-time sanity check now diagnoses an
1500 unsafe absolute source directory name and makes configure fail.
1502 - The Automake macros and rules cope better with whitespace in the
1503 current directory name, as long as the relative path to `configure'
1504 does not contain whitespace. To this end, the values of `$(MISSING)'
1505 and `$(install_sh)' may contain suitable quoting, and their expansion
1506 might need `eval'uation if used outside of a makefile. These
1507 undocumented variables may be used in several documented macros such
1508 as $(AUTOCONF) or $(MAKEINFO).
1512 * Long-standing bugs:
1514 - Fix aix dependency tracking for libtool objects.
1516 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1517 unnecessary use of the `compile' script.
1519 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1520 correct `-rpath' argument is used now.
1522 - `config.status --file=Makefile depfiles' now also works with the
1523 extra quoting used internally by Autoconf 2.62 and newer
1524 (it used to work only without the `--file=' bit).
1526 - The `missing' script works better with versioned tool names.
1528 - Semantics for `missing help2man' have been revamped:
1530 Previously, if `help2man' was not present, `missing help2man' would have
1531 the following semantics: if some man page was out of date but present, then
1532 a warning would be printed, but the exit status was 0. If the man page was
1533 not present at all, then `missing' would create a replacement man page
1534 containing an error message, and exit with a status of 2. This does not play
1535 well with `make': the next run will see this particular man page as being up
1536 to date, and will only error out on the next generated man page, if any;
1537 repeat until all pages are done. This was not desirable.
1539 These are the new semantics: if some man page is not present, and help2man
1540 is not either, then `missing' will warn and generate the replacement page
1541 containing the error message, but exit successfully. However, `make dist'
1542 will ensure that no such bogus man pages are packaged into a tarball.
1544 - Targets provided by automake behave better with `make -n', in that they
1545 take care not to create files.
1547 - `config.status Makefile... depfiles' works fine again in the presence of
1548 disabled dependency tracking.
1550 - The default no-op recursive rules for these targets also work with BSD make
1551 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1553 - `make distcheck' works also when both a directory and some file below it
1554 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1556 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1557 `make mostlyclean' any more; only the LaTeX by-products are.
1559 - Renamed objects also work with the `subdir-objects' option and
1560 source file languages which Automake does not know itself.
1562 - `automake' now correctly complains about variable assignments which are
1563 preceded by a comment, extend over multiple lines with backslash-escaped
1564 newlines, and end in a comment sign. Previous versions would silently
1565 and wrongly ignore such assignments completely.
1567 * Bugs introduced by 1.10:
1569 - Fix output of dummy dependency files in presence of post-processed
1570 Makefile.in's again, but also cope with long lines.
1572 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1573 that have been declared as programs in the same Makefile.
1574 This is for consistency with the analogous change to TESTS in 1.10.
1576 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1577 followed by directories containing config headers.
1579 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1583 * Version requirements:
1585 - Autoconf 2.60 or greater is required.
1587 - Perl 5.6 or greater is required.
1589 * Changes to aclocal:
1591 - aclocal now also supports -Wmumble and -Wno-mumble options.
1593 - `dirlist' entries (for the aclocal search path) may use shell
1594 wildcards such as `*', `?', or `[...]'.
1596 - aclocal supports an --install option that will cause system-wide
1597 third-party macros to be installed in the local directory
1598 specified with the first -I flag. This option also uses #serial
1599 lines in M4 files to upgrade local macros.
1601 The new aclocal options --dry-run and --diff help to review changes
1602 before they are installed.
1604 - aclocal now outputs an autoconf version check in aclocal.m4 in
1605 projects using automake.
1607 For a few years, automake and aclocal have been calling autoconf
1608 (or its underlying engine autom4te) to accurately retrieve the
1609 data they need from configure.ac and its siblings. Doing so can
1610 only work if all autotools use the same version of autoconf. For
1611 instance a Makefile.in generated by automake for one version of
1612 autoconf may stop working if configure is regenerated with another
1613 version of autoconf, and vice versa.
1615 This new version check ensures that the whole build system has
1616 been generated using the same autoconf version.
1618 * Support for new Autoconf macros:
1620 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1622 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1623 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1624 in different directories. However, only one instance of such a
1625 library objects directory is supported.
1627 * Change to Libtool support:
1629 - Libtool generic flags (those that go before the --mode=MODE option)
1630 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1632 * Yacc and Lex changes:
1634 - The rebuild rules for distributed Yacc and Lex output will avoid
1635 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1638 - ylwrap is now always used for lex and yacc source files,
1639 regardless of whether there is more than one source per directory.
1641 * Languages changes:
1643 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1644 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1645 tracking, unlike non-preprocessed assembler (*.s).
1647 - subdir-object mode works now with Assembler. Automake assumes
1648 that the compiler understands `-c -o'.
1650 - Preprocessed assembler (*.S) compilation now also honors
1651 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1653 - Improved support for Objective C:
1654 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1655 - A new section of the manual documents the support.
1657 - New support for Unified Parallel C:
1658 - AM_PROG_UPC looks for a UPC compiler.
1659 - A new section of the manual documents the support.
1661 - Per-target flags are now correctly handled in link rules.
1663 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1664 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1665 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1666 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1668 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1669 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1670 is expected to work (and actually works during compilation).
1672 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1673 "in addition to" breaks backward compatibility with older versions.
1674 If your package used both variables, as in
1676 AM_LDFLAGS = common flags
1677 bin_PROGRAMS = a b c
1678 a_LDFLAGS = more flags
1681 and assumed *_LDFLAGS would sum up, you should rewrite it as
1683 AM_LDFLAGS = common flags
1684 bin_PROGRAMS = a b c
1685 a_LDFLAGS = $(AM_LDFLAGS) more flags
1688 This new behavior of *_LDFLAGS is more coherent with other
1689 per-target variables, and the way *_LDFLAGS variables were
1690 considered internally.
1692 * New installation targets:
1694 - New targets mandated by GNU Coding Standards:
1699 By default they will only install Texinfo manuals.
1700 You can customize them with *-local variants:
1706 - The undocumented recursive target `uninstall-info' no longer exists.
1707 (`uninstall' is in charge of removing all possible documentation
1708 flavors, including optional formats such as dvi, ps, or info even
1709 when `no-installinfo' is used.)
1711 * Miscellaneous changes:
1713 - Automake no longer complains if input files for AC_CONFIG_FILES
1714 are specified using shell variables.
1716 - clean, distribution, or rebuild rules are normally disabled for
1717 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1718 AC_CONFIG_LINK specified using shell variables. However, if these
1719 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1720 be able to output rules anyway.
1721 (See the Automake documentation for AC_CONFIG_FILES.)
1723 - $(EXEEXT) is automatically appended to filenames of TESTS
1724 that have been declared as programs in the same Makefile.
1725 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1727 - `-Wportability' has finally been turned on by default for `gnu' and
1728 `gnits' strictness. This means, automake will complain about %-rules
1729 or $(GNU Make functions) unless you switch to `foreign' strictness or
1730 use `-Wno-portability'.
1732 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1733 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1734 $(mkdir_p) variable is still defined (to the same value as
1735 $(MKDIR_P)) but should be considered obsolete. If you are using
1736 $(mkdir_p) in some of your rules, please plan to update them to
1737 $(MKDIR_P) at some point.
1739 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1740 They still work in this release, but may be withdrawn in a future one.
1742 - Inline compilation rules for gcc3-style dependency tracking are
1745 - Automake installs a "Hello World!" example package in $(docdir).
1746 This example is used throughout the new "Autotools Introduction"
1747 chapter of the manual.
1749 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1753 * Makefile.in bloat reduction:
1755 - Inference rules are used to compile sources in subdirectories when
1756 the `subdir-objects' option is used and no per-target flags are
1757 used. This should reduce the size of some projects a lot, because
1758 Automake used to output an explicit rule for each such object in
1761 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1762 object that must be built with explicit rules. It just outputs
1763 the rules required to build the kind of object considered: either
1764 the two .o and .obj rules for usual objects, or the .lo rule for
1767 * Change to Libtool support:
1769 - Libtool tags are used with libtool versions that support them.
1770 (I.e., with Libtool 1.5 or greater.)
1772 - Automake is now able to handle setups where a libtool library is
1773 conditionally installed in different directories, as in
1776 lib_LTLIBRARIES = liba.la
1778 pkglib_LTLIBRARIES = liba.la
1780 liba_la_SOURCES = ...
1782 * Changes to aclocal:
1784 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1785 really evaluated, before it decides to include them in aclocal.m4.
1786 This solves nasty problems with conditional redefinitions of
1787 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1788 *.m4 files to be included in any project using these macros.
1789 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1790 most famous instance of this bug.)
1792 - Do not complain about missing conditionally AC_REQUIREd macros
1793 that are not actually used. In 1.8.x aclocal would correctly
1794 determine which of these macros were really needed (and include
1795 only these in the package); unfortunately it would also require
1796 all of them to be present in order to run. This created
1797 situations were aclocal would not work on a tarball distributing
1798 all the macros it uses. For instance running aclocal on a project
1799 containing only the subset of the Gettext macros in use by the
1800 project did not work, because gettext conditionally requires other
1803 * Portability improvements:
1805 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1806 tar-pax. The new option filename-length-max=99 helps diagnosing
1807 filenames that are too long for tar-v7. (PR/414)
1809 - Variables augmented with `+=' are now automatically flattened (i.e.,
1810 trailing backslashes removed) and then wrapped around 80 columns
1811 (adding trailing backslashes). In previous versions, a long series
1817 would result in a single-line definition of VAR that could possibly
1818 exceed the maximum line length of some make implementations.
1820 Non-augmented variables are still output as they are defined in
1825 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1826 Works the same as the old Fortran 77 implementation; just replace
1827 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1828 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1830 - Support for conditional _LISP.
1832 - Support for conditional -hook and -local rules (PR/428).
1834 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1836 - Automake will not write any Makefile.ins after the first error it
1837 encounters. The previous Makefile.ins (if any) will be left in
1838 place. (Warnings will not prevent output, but remember they can
1839 be turned into errors with -Werror.)
1841 - The restriction that SUBDIRS must contain direct children is gone.
1844 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1845 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1847 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1849 Bugs fixed in 1.8.5:
1851 * Long-standing bugs:
1853 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1854 so that `make distclean' and `make maintainer-clean' can work.
1856 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1858 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1860 - Polish diagnostic when no input file is found.
1862 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1864 Bugs fixed in 1.8.4:
1866 * Long-standing bugs:
1868 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1869 overridden by the user.
1871 - Honor PATH_SEPARATOR in various places of the Automake package, for
1874 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1877 - Fix install-sh so it can install the `mv' binary... using `mv'.
1879 - Fix tru64 dependency tracking for libtool objects.
1881 - Work around Exuberant Ctags when creating a TAGS files in a directory
1882 without files to scan but with subdirectories to include.
1884 * Bugs introduced by 1.8:
1886 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1887 not defined in the same conditions as the _LDADD that uses it.
1889 - Do not warn when JAVAROOT is overridden, this is legitimate.
1891 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1893 Bugs fixed in 1.8.3:
1895 * Long-standing bugs:
1897 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1898 or any of the other *dir variables contain a space.
1900 Please note that Automake does not and cannot support spaces in
1901 filenames that are involved during the build. This change affects
1902 only installation paths, so that `make install' does not bomb out
1903 in packages configured with
1904 ./configure --prefix '/c/Program Files'
1906 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1907 POSIXLY_CORRECT is set.
1909 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1910 since Autoconf 2.54, which defines LIBOBJS itself.
1912 - Fix a potential (but unlikely) race condition in parallel elisp
1913 builds. (Introduced in 1.7.3.)
1915 - Do not assume that users override _DEPENDENCIES in all conditions
1916 where Automake will try to define them.
1918 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1919 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1922 This fix also affects the $(mkdir_p) variable defined since
1923 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1924 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1926 - Secure temporary directory creation in `make distcheck'. (PR/413)
1928 - Do not generate two build rules for `parser.h' when the
1929 parser appears in two different conditionals.
1931 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1932 checking. Usually ./configure will not pick this shell; so this
1933 fix only helps cases where the shell is forced to /bin/sh.
1935 * Bugs introduced by 1.8:
1937 - In some situations (hand-written `m4_include's), aclocal would
1938 call the `File::Spec->rel2abs' method, which was only introduced
1939 in Perl 5.6. This new version reestablish support Perl 5.005.
1941 It is likely that the next major Automake releases will require at
1942 least Perl 5.6. Consider upgrading your development environment
1943 if you are still using the five-year-old Perl 5.005.
1945 - Automake would sometimes fail to define rules for targets listed
1946 in variables defined in multiple conditions. For instance on
1952 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1953 `b.$(OBJEXT): b.c' rule.
1955 * New sections in manual:
1957 - Third-Party Makefiles: how to interface third party Makefiles.
1958 - Upgrading: upgrading packages to newer Automake versions.
1959 - Multiple Outputs: handling tools that produce many outputs.
1961 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1965 * A (well known) portability bug slipped in the changes made to
1966 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1967 install anything on Tru64.
1969 * Fix install rules for conditionally built python files. (This never
1972 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1976 * Bugs introduced by 1.8:
1978 - Fix Config.pm import error with old Perl versions (at least
1979 5.005_03). One symptom is that aclocal could not find its macro
1982 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1983 created by `make install' are always world readable, even if the
1984 installer happens to have an overly restrictive umask (e.g. 077).
1985 This was a mistake and has been reverted. There are at least two
1986 reasons why we must not use `-m 0755':
1987 - it causes special bits like SGID to be ignored,
1988 - it may be too restrictive (some setups expect 775 directories).
1990 - Fix aclocal to honor definitions located in files which have been
1991 m4_included manually. aclocal 1.8 had been updated to check
1992 m4_included files for new requirements, but forgot that these
1993 m4_included files can also provide new definitions.
1995 Note that if you have such a setup, we recommend you get rid of
1996 it. In the past, there was a reason to m4_include files manually:
1997 aclocal used to duplicate entire M4 files into aclocal.m4, even
1998 files that were distributed. Some packages were therefore
1999 m4_including the distributed file directly, and playing some
2000 tricks to ensure aclocal would not copy that file to aclocal.m4,
2001 in order to limit the amount of duplication. Since aclocal 1.8.x
2002 will precisely output m4_includes for local M4 files, we recommend
2003 that you clean up your setup, removing all manual m4_includes and
2004 letting aclocal output them.
2006 - Output detailed menus in the Info version if the Automake manual,
2007 so that Emacs can locate the indexes.
2009 - configure.ac and configure were listed twice in DIST_COMMON (an
2010 internal variable where Automake lists configury files to
2011 distribute). This was harmless, but unaesthetic.
2013 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
2014 This was an issue only in the Automake package itself, not in
2017 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
2018 DEST:SRC. This was wrong, as some packages do
2019 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
2022 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
2023 argument. This caused two kinds of failures:
2024 - Rules installing data in a conditionally defined directory
2025 failed when that directory was undefined. In this case no
2026 argument was supplied.
2027 - `make installdirs' failed, because several directories were
2028 passed to $(mkdir_p). This was an issue only on platform
2029 were $(mkdir_p) is implemented with `install-sh -d'.
2030 $(mkdir_p) as been changed to accept 0 or more arguments, as
2033 * Long-standing bugs:
2035 - Fix an unexpected diagnostic occurring when users attempt
2036 to override some internal variables that Automake appends to.
2038 - aclocal now scans configure.ac for macro definitions (PR/319).
2040 - Fix a portability issue with OSF1/Tru64 Make. If a directory
2041 distributes files which are outside itself (this usually occurs
2042 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
2043 from a parent package), then `make distcheck' fails due to an
2044 optimization performed by OSF1/Tru64 Make in its VPATH handling.
2045 (tests/subpkg2.test failure)
2047 - Fix another portability issue with Sun and OSF1/Tru64 Make.
2048 In a VPATH-build configuration, `make install' would install
2049 nobase_ files to wrong locations.
2051 - Fix a Perl `uninitialized value' diagnostic occurring when
2052 automake complains that a Texinfo file does not have a
2053 @setfilename statement.
2055 - Erase config.status.lineno during `make distclean'. This file
2056 can be created by config.status. Automake already knew about
2057 configure.lineno, but forgot config.status.lineno.
2059 - Distribute all files, even those which are built and installed
2060 conditionally. This change affects files listed in conditionally
2061 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
2062 as well as those listed in conditionally defined dist_*_DATA,
2063 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
2065 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
2066 doesn't conform to POSIX.
2068 - Normalize help strings for configure variables and options added
2073 - Check for python2.4 in AM_PATH_PYTHON.
2075 * Spurious failures in test suite:
2077 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
2078 tests/ltconv.test: fix failures with CVS Libtool.
2079 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
2080 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
2081 fix failures with old Texinfo versions.
2083 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2089 - The NEWS file is more verbose.
2093 - Autoconf 2.58 or greater is required.
2097 - Default source file names in the absence of a _SOURCES declaration
2098 are made by removing any target extension before appending `.c', so
2099 to make the libtool module `foo.la' from `foo.c', you only need to
2102 lib_LTLIBRARIES = foo.la
2103 foo_la_LDFLAGS = -module
2105 For backward compatibility, foo_la.c will be used instead of
2106 foo.c if this file exists or is the explicit target of a rule.
2107 However -Wobsolete will warn about this deprecated naming.
2109 - AR's `cru' flags are now set in a global ARFLAGS variable instead
2110 of being hard-coded in each $(AR) invocation, so they can be
2111 substituted from configure.ac. This has been requested by people
2112 dealing with non-POSIX ar implementations.
2114 - New warning option: -Woverride. This will warn about any user
2115 target or variable definitions which override Automake
2118 - Texinfo rules back up and restore info files when makeinfo fails.
2120 - Texinfo rules now support the `html' target.
2121 Running this requires Texinfo 4.0 or greater.
2123 `html' is a new recursive target, so if your package mixes
2124 hand-crafted `Makefile.in's with Automake-generated
2125 `Makefile.in's, you should adjust the former to support (or
2126 ignore) this target so that `make html' recurses successfully. If
2127 you had a custom `html' rule in your `Makefile.am', it's better to
2128 rename it as `html-local', otherwise your rule will override
2129 Automake's new rule (you can check that by running `automake
2130 -Woverride') and that will stop the recursion to subdirectories.
2132 Last but not least, this `html' rule is declared PHONY, even when
2133 overridden. Fortunately, it appears that few packages use a
2134 non-PHONY `html' rule.
2136 - Any file which is m4_included from configure.ac will appear as a
2137 configure and Makefile.in dependency, and will be automatically
2140 - The rules for rebuilding Makefiles and Makefile.ins will now
2141 rebuild all Makefiles and all Makefile.ins at once when one of
2142 configure's dependencies has changed. This is considerably faster
2143 than previous implementations, where config.status and automake
2144 were run separately in each directory (this still happens when you
2145 change a Makefile.am locally, without touching configure.ac or
2146 friends). Doing this also solves a longstanding issue: these
2147 rebuild rules failed to work when adding new directories to the
2148 tree, forcing you to run automake manually.
2150 - For similar reasons, the rules to rebuild configure,
2151 config.status, and aclocal.m4 are now defined in all directories.
2152 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
2153 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
2154 should better define them in all directories. This is easily done
2155 using an AC_SUBST (make sure you prefix these dependencies with
2156 $(top_srcdir) since this variable will appear at different
2157 levels of the build tree).
2159 - aclocal will now use `m4_include' instead of copying local m4
2160 files into aclocal.m4. (Local m4 files are those you ship with
2161 your project, other files will be copied as usual.)
2163 Because m4_included files are automatically distributed, it means
2164 for most projects there is no point in EXTRA_DISTing the list of
2165 m4 files which are used. (You can probably get rid of
2166 m4/Makefile.am if you had one.)
2168 - aclocal will avoid touching aclocal.m4 when possible, so that
2169 Autom4te's cache isn't needlessly invalidated. This behavior can
2170 be switched off with the new `--force' option.
2172 - aclocal now uses Autoconf's --trace to detect macros which are
2173 actually used and will no longer include unused macros simply
2174 because they where mentioned. This was often the case for macros
2175 called conditionally.
2177 - New options no-dist and no-dist-gzip.
2179 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2180 py-compile, and ylwrap, now all understand --version and --help.
2182 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2183 links as part of the distclean target and including source files in
2186 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2187 argument. The latter can be used to override the default behavior
2188 (which is to abort).
2190 - Automake will exit with $? = 63 on version mismatch. (So does
2191 Autoconf 2.58) missing knows this, and in this case it will
2192 emulate the tools as if they were absent. Because older versions
2193 of Automake and Autoconf did not use this exit code, this change
2194 will only be useful in projects generated with future versions of
2197 - When using AC_CONFIG_FILES with multiple input files, Automake
2198 generates the first ".in" input file for which a ".am" exists.
2199 (Former versions would try to use only the first input file.)
2201 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2202 idiom to disable byte-compilation of lisp_LISP files, it is
2203 recommended that you switch to using lisp_DATA. Note that
2204 this is not strictly equivalent: lisp_DATA will install elisp
2205 files even if emacs is not installed, while *_LISP do not
2206 install anything unless emacs is found.
2208 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2209 available. This selection is achieved through the Makefile
2210 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2211 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2212 `$(install_sh) -m 0755 -d'.
2216 - Because `mkdir -p' is available on most platforms, and we can use
2217 `install-sh -d' when it is not, the use of the mkinstalldirs
2218 script is being phased out. `automake --add-missing' no longer
2219 installs it, and if you remove mkinstalldirs from your package,
2220 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2222 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2223 gettextize and autopoint will install it when needed. Automake
2224 will continue to define the $(mkinstalldirs) and to distribute
2225 mkinstalldirs when this script is in the source tree.
2227 - AM_PROG_CC_STDC is now empty. The content of this macro was
2228 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2229 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2230 renaming should be safe, even if you have to support several,
2231 versions of Automake, because AC_PROG_CC defines this variable
2232 since Autoconf 2.54.)
2234 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2235 variable to override the aclocal.m4 dependencies computed
2236 (inaccurately) by older versions of Automake. Because Automake
2237 now tracks configure's m4 dependencies accurately (see m4_include
2238 above), the use of ACLOCAL_M4_SOURCES should be considered
2239 obsolete and will be flagged as such when running `automake
2244 - Defining programs conditionally using Automake conditionals no
2245 longer leads to a combinatorial explosion. The following
2246 construct used to be troublesome when used with dozens of
2261 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2263 - Due to implementation constraints, previous versions of Automake
2264 proscribed multiple conditional definitions of some variables
2274 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2275 This restriction has been lifted, and these variables now
2276 support multiple conditional definitions as do other variables.
2278 - Cleanup the definitions of $(distdir) and $(top_distdir).
2279 $(top_distdir) now points to the root of the distribution
2280 directory created during `make dist', as it did in Automake 1.4,
2281 not to the root of the build tree as it did in intervening
2282 versions. Furthermore these two variables are now only defined in
2283 the top level Makefile, and passed to sub-directories when running
2286 - The --no-force option now correctly checks the Makefile.in's
2287 dependencies before deciding not to update it.
2289 - Do not assume that make files are called Makefile in cleaning rules.
2291 - Update .info files in the source tree, not in the build tree. This
2292 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2293 used to update these files in the build tree (previous versions did
2294 it in the source tree too), and it caused several problems, varying
2295 from mere annoyance to portability issues.
2297 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2298 when --add-missing and --force-missing are used. For backward
2299 compatibility --add-missing will continue to install COPYING (in
2300 `gnu' strictness) when none of these three files exist, but this
2301 use is deprecated: you should better choose a license yourself and
2302 install it once for all in your source tree (and in your code
2305 - Fix ylwrap so that it does not overwrite header files that haven't
2306 changed, as the inline rule already does.
2308 - User-defined rules override automake-defined rules for the same
2309 targets, even when rules do not have commands. This is not new
2310 (and was documented), however some of the automake-generated
2311 rules have escaped this principle in former Automake versions.
2312 Rules for the following targets are affected by this fix:
2314 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2315 info, info-am, install-data-am, install-exec-am, install-info,
2316 install-info-am, install-man, installcheck-am, maintainer-clean,
2317 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2318 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2320 Practically it means that an attempt to supplement the dependencies
2321 of some target, as in
2323 clean: my-clean-rule
2325 will now *silently override* the automake definition of the
2326 rule for this target. Running `automake -Woverride' will diagnose
2327 all such overriding definitions.
2329 It should be noted that almost all of these targets support a *-local
2330 variant that is meant to supplement the automake-defined rule
2331 (See node `Extending' in the manual). The above rule should
2334 clean-local: my-clean-rule
2336 These *-local targets have been documented since at least
2337 Automake 1.2, so you should not fear the change if you have
2338 to support multiple automake versions.
2342 - The Automake manual is now distributed under the terms of the GNU FDL.
2344 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2346 - core dumps are no longer removed by the cleaning rules. There are
2347 at least three reasons for this:
2348 1. These files should not be created by any build step,
2349 so their removal do not fit any of the cleaning rules.
2350 Actually, they may be precious to the developer.
2351 2. If such file is created during a build, then it's clearly a
2352 bug Automake should not hide. Not removing the file will
2353 cause `make distcheck' to complain about its presence.
2354 3. Operating systems have different naming conventions for
2355 core dump files. A core file on one system might be a
2356 completely legitimate data file on another system.
2358 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2359 defined by Automake. This means that any definition in the
2360 environment will be used, unless overridden in the Makefile.am or
2361 on the command line. The old behavior, where these variables were
2362 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2363 AC_ARG_VARing each variable from configure.ac.
2365 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2366 documented. (The is not a new feature, these variables have
2367 been there since at least Automake 1.4.)
2369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2371 Bugs fixed in 1.7.9:
2372 * Fix install-strip to work with nobase_ binaries.
2373 * Fix renaming of #line directives in ylwrap.
2374 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2376 Bugs fixed in 1.7.8:
2377 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2378 * Fix detection of Debian's install-info, broken since version 1.5.
2379 (Debian bug #213524).
2380 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2381 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2383 Bugs fixed in 1.7.7:
2384 * The implementation of automake's --no-force option is unreliable,
2385 so this option is ignored in this version. A real fix will appear in
2386 Automake 1.8. (Debian Bug #206299)
2387 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2388 argument is given. (PR/399)
2389 * Do not warn about leading `_' in variable names, even with -Wportability.
2390 * Support user redefinitions of TEXINFO_TEX.
2391 * depcomp: support AIX Compiler version 6.
2392 * Fix missing rebuilds during `make dist' with BSD make.
2393 (Could produce tarballs containing out-of-date files.)
2394 * Resurrect multilib support.
2395 * Noteworthy manual updates:
2396 - Extending aclocal: how to write m4 macros that won't trigger warnings
2398 - A Shared Library: Rewrite and split into subsections.
2400 Bugs fixed in 1.7.6:
2401 * Fix depcomp's icc mode for ICC 7.1.
2402 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2403 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2404 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2405 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2406 * Remove Latin-1 characters from elisp-comp.
2407 * Update the manual's @dircategory to match the Free Software Directory.
2409 Bugs fixed in 1.7.5:
2410 * Update install-sh's license to remove an advertising clause.
2411 (Debian bug #191717)
2412 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2413 that caused invalid Makefile.ins to be generated.
2414 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2415 * New FAQ entry: renamed objects.
2417 Bugs fixed in 1.7.4:
2418 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2419 the Emacs implementation)
2420 * Fix output of aclocal.m4 dependencies in subdirectories.
2421 * Use `mv -f' instead of `mv' in fastdep rules.
2422 * Upgrade mdate-sh to work on OS/2.
2423 * Don't byte-compile elisp files when ELCFILES is set empty.
2424 (this documented feature was broken by 1.7.3)
2425 * Diagnose trailing backslashes on last line of Makefile.am.
2426 * Diagnose whitespace following trailing backslashes.
2427 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2428 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2430 * `make install' will build `BUILT_SOURCES' first.
2431 * Minor documentation fixes.
2433 Bugs fixed in 1.7.3:
2434 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2435 * Query distutils for `pythondir' and `pythonexecdir', instead of
2436 using an hardcoded path. This should allow builds on 64-bit
2437 distributions that usually use lib64/ instead of lib/.
2438 * AM_PATH_PYTHON will also search for python2.3.
2439 * elisp files are now built all at once instead of one by one. Besides
2440 incurring a speed-up, this is required to support interdependent elisp files.
2441 * Support for DJGPP:
2442 - `make distcheck' will now work in `_inst/' and `_build' instead
2443 of `=inst/' and `=build/'
2444 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2445 - install/uninstall `*.i[0-9][0-9]'-style info files
2446 - more changes that affect only the Automake package (not its output)
2447 * Fix some incompatibilities with upcoming perl-5.10.
2448 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2449 PACKAGE and VERSION.
2451 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2452 is troublesome with gcc and Solaris compilers. (PR/385)
2453 - makedepend mode: work with Libtool. (PR/385 too)
2455 * better support for unusual gettext setups, such as multiple po/ directories
2457 - Flag missing po/ and intl/ directories as warnings, not errors.
2458 - Disable these warnings if po/ does not exist.
2459 * Noteworthy manual updates:
2461 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2463 - Document `AM_YFLAGS = -d'. (PR/382)
2465 Bugs fixed in 1.7.2:
2466 * Fix installation and uninstallation of Info files built in subdirectories.
2467 * Do not run `./configure --with-included-gettext' during `make distcheck'
2468 if AM_GNU_GETTEXT([external]) is used.
2469 * Correctly uninstall renamed man pages.
2470 * Do not strip escaped newline in variables defined in one condition
2471 and augmented in another condition.
2472 * Fix ansi2knr rules for LIBOBJS sources.
2473 * Clean all known Texinfo index files, not only those which appear to
2474 be used, because we cannot know which indexes are used in included files.
2475 (PR/375, Debian Bug #168671)
2476 * Honor only the first @setfilename seen in a Texinfo file.
2477 * Treat "required file X not found" diagnostics as errors (exit status 1).
2478 * Don't complain that a required file is not found when it is a Makefile
2480 * Don't use single suffix inference rules when building `.info'-less
2481 Info files, for the sake of Solaris make.
2482 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2483 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2484 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2485 * Fix building of deansified files from subdirectories. (PR/370)
2486 * Add missing `fi' in the .c->.obj rules.
2487 * Improve install-sh to work even when names contain spaces or certain
2488 (but not all) shell metachars.
2489 * Fix the following spurious failures in the test suite:
2490 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2491 * Noteworthy manual updates:
2492 - Augment the section about BUILT_SOURCES.
2493 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2495 Bugs fixed in 1.7.1:
2496 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2498 * Aclocal should now recognize macro names containing parentheses, e.g.
2499 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2500 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2502 * Install Python files even if they were built. (PR/369)
2503 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2504 version might not be defined in the latter. (PR/358)
2505 * Reorder arguments passed to a couple of commands, so things works
2506 when POSIXLY_CORRECT=1.
2507 * Fix a regex that can cause Perl to segfault on large input.
2509 * Fix distribution of packages that have some sources defined conditionally,
2510 as in the `Conditional compilation using Automake conditionals' example
2512 * Fix spurious test suite failures on IRIX.
2513 * Don't report a required variable as undefined if it has been
2514 defined conditionally for the "right" conditions.
2515 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2516 `make distcheck' fails.
2517 * Fix distribution of included Makefile fragment, so we don't create
2518 spurious directories in the distribution. (PR/366)
2519 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2522 * Autoconf 2.54 is required.
2523 * `aclocal' and `automake' will no longer warn about obsolete
2524 configure macros. This is done by `autoconf -Wobsolete'.
2525 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2526 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2527 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2528 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2529 `configure.ac' for you.
2530 * Support for per-program and per-library `_CPPFLAGS'.
2531 * New `ctags' target (builds CTAGS files).
2532 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2533 (see `automake --help' or the manual for a list of them).
2534 * Honor the WARNINGS environment variable.
2535 * Omit the call to depcomp when using gcc3: call the compiler directly.
2536 * A new option, std-options, tests that programs support --help and --version
2537 when `make installcheck' is run. This is enabled by --gnits.
2538 * Texinfo rules now support the `ps' and `pdf' targets.
2539 * Info files are now created in the build directory, not the source directory.
2540 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2542 * `make distcheck' will enforce DESTDIR support by attempting
2544 * `+=' can be used in conditionals, even if the augmented variable
2545 was defined for another condition.
2546 * Makefile fragments (inserted with `include') are always distributed.
2547 * Use Autoconf's --trace interface to inspect configure.ac and get
2548 a more accurate view of it.
2549 * Add support for extending aclocal's default macro search path
2550 using a `dirlist' file within the aclocal directory.
2551 * automake --output-dir is deprecated.
2552 * The part of the distcheck target that checks whether uninstall actually
2553 removes all installed files has been moved in a separate target,
2554 distuninstallcheck, so it can be overridden easily.
2558 * Support for AM_INIT_GETTEXT([external])
2559 * Bug fixes, including:
2560 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2561 - nobase_ programs and scripts honor --program-transform correctly.
2562 - Erase configure.lineno during `make distclean'.
2563 - Erase YACC and LEX outputs during `make maintainer-clean'.
2566 * Many bug fixes, including:
2567 - Requiring the current version works.
2568 - Fix "$@" portability issues (for Zsh).
2569 - Fix output of dummy dependency files in presence of post-processed
2571 - Don't compute dependencies in background to avoid races with libtool.
2572 - Fix handling of _OBJECTS variables for targets sharing source variables.
2573 - Check dependency mode for Java when AM_PROG_GCJ is used.
2576 * automake --output-dir is deprecated
2577 * Many bug fixes, including:
2578 - Don't choke on AM_LDFLAGS definitions.
2579 - Clean libtool objects from subdirectories.
2580 - Allow configure variables with reserved suffix and unknown prefix
2581 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2582 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2585 * Autoconf 2.52 is required.
2586 * automake no longer run libtoolize.
2587 This is the job of autoreconf (from GNU Autoconf).
2588 * `dist' generates all the archive flavors, as did `dist-all'.
2589 * `dist-gzip' generates the Gzip tar file only.
2590 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2591 explosion. Makefile.in's keep a reasonable size.
2592 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2593 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2595 * `#line' of Lex and Yacc files are properly set.
2596 * EXTRA_DIST can contain generated directories.
2597 * Support for dot-less extensions in suffix rules.
2598 * The part of the distcheck target that checks whether distclean actually
2599 cleans all built files has been moved in a separate target, distcleancheck,
2600 so it can be overridden easily.
2601 * `make distcheck' will pass additional options defined in
2602 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2603 * Fixed CDPATH portability problems, in particular for MacOS X.
2604 * Fixed handling of nobase_ targets.
2605 * Fixed support of implicit rules leading to .lo objects.
2606 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2607 * Added uninstall-hook target
2608 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2609 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2610 (Note that "pkgname" is not "tarname", see the manual for details.)
2611 It is also possible to pass a list of global Automake options as
2612 first argument to this new form of AM_INIT_AUTOMAKE.
2613 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2614 to be a real assembler.
2615 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2616 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2617 * aclocal and automake are also installed with the version number
2618 appended, and some of the install directory names have changed.
2619 This lets you have multiple versions installed simultaneously.
2620 * Support for parsers and lexers in subdirectories.
2623 * Support for `configure.ac'.
2624 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2625 * `make dist-all' is much faster.
2626 * Allows '@' AC_SUBSTs in macro names.
2627 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2628 * User-side dependency tracking. Developers no longer need GNU make
2630 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2631 * Most files are correctly handled if they appear in subdirs
2632 For instance, a _DATA file can appear in a subdir
2633 * GNU tar is no longer required for `make dist'
2634 * Added support for `dist_' and `nodist_' prefixes
2635 * Added support for `nobase_' prefix
2636 * Compiled Java support
2637 * Support for per-executable and per-library compilation flags
2641 * Added support for the Fortran 77 programming language.
2642 * Re-indexed the Automake Texinfo manual.
2643 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2644 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2645 * Support for latest autoconf, including support for objext
2646 * Can now put `.' in SUBDIRS to control build order
2647 * `include' command and `+=' support for macro assignment
2648 * Dependency tracking no long susceptible to deleted header file problem
2649 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2654 * Better Cygwin32 support
2655 * Support for suffix rules with _SOURCES variables
2656 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2657 * @LEXLIB@ no longer required when lex source seen
2658 Lex support in `missing', and new lex macro. Update your missing script.
2659 * Built-in support for assembly
2660 * aclocal gives error if `AM_' macro not found
2661 * Passed YFLAGS, not YACCFLAGS, to yacc
2662 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2663 * Dependencies computed as a side effect of compilation
2664 * Preliminary support for Java
2665 * DESTDIR support at "make install" time
2666 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2670 * Better DejaGnu support
2671 * Added no-installinfo option
2672 * Added Emacs Lisp support
2673 * Added --no-force option
2674 * Included `aclocal' program
2675 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2676 * Now uses `AM_' macro names everywhere
2677 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2678 ansi2knr now works correctly on K&R sources
2679 * Better C++, yacc, lex support
2680 * Will compute _DEPENDENCIES variables automatically if not supplied
2681 * Will interpolate $(...) and ${...} when examining contents of a variable
2682 * .deps files now in build directory, not source directory; dependency
2683 handling generally rewritten
2684 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2685 * can now put config.h into a subdir
2686 * Added dist-all target
2687 * Support for install-info program (see texinfo 3.9)
2688 * Support for "yacc -d"
2689 * configure substitutions are automatically discovered and included
2690 in generated Makefile.in
2691 * Special --cygnus mode
2692 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2693 when making distribution. Some dependencies are auto-ignored.
2694 * Changed how libraries are specified in _LIBRARIES variable
2695 * Full libtool support, from Gord Matzigkeit
2696 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2697 AM_CONFIG_HEADER handles it automatically
2698 * Texinfo output files no longer need .info extension
2699 * Added `missing' support
2701 * Conditionals in Makefile.am, from Ian Taylor
2705 * distcheck target runs install and installcheck targets
2706 * Added preliminary support for DejaGnu.
2711 * More libtool fixes from Gord Matzigkeit; libtool support is still
2713 * Added support for jm_MAINTAINER_MODE
2715 * New "distcheck" target
2719 * mkinstalldirs and mdate-sh now appear in directory specified by
2721 * Removed DIST_SUBDIRS, DIST_OTHER
2722 * AC_ARG_PROGRAM only required when an actual program exists
2723 * dist-hook target now run before distribution packaged up; idea from
2724 Dieter Baron. Other hooks exist, too.
2725 * Preliminary (unfinished) support for libtool
2726 * Added short option names.
2727 * Better "dist" support when gluing together multiple packages
2731 * Documentation updates (many from François Pinard)
2732 * strictness `normal' now renamed to `foreign'
2733 * Renamed --install-missing to --add-missing
2734 * Now handles AC_CONFIG_AUX_DIR
2735 * Now handles TESTS macro
2736 * DIST_OTHER renamed to EXTRA_DIST
2737 * DIST_SUBDIRS is deprecated
2738 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2739 * Better error messages in many cases
2740 * Program names are canonicalized
2741 * Added "check" prefix; from Gord Matzigkeit
2745 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2746 * Beginnings of a test suite
2747 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2748 * Doesn't print anything when running
2749 * Beginnings of MAINT_CHARSET support
2750 * Can specify version in AUTOMAKE_OPTIONS
2751 * Most errors recognizable by Emacs' M-x next-error
2752 * Added --verbose option
2753 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2754 configure-generated names
2755 * Required macros now distributed in aclocal.m4
2757 * --strictness=gnu is default
2761 * More sophisticated configure.in scanning; now understands ALLOCA and
2762 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2763 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2764 * CONFIG_HEADER variable now obsolete
2765 * Can handle multiple Texinfo sources
2766 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2767 * HEADERS variable no longer needed; now can put .h files directly into
2768 foo_SOURCES variable.
2769 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2770 corresponding ".in" files are included in the distribution.
2773 * Added --gnu and --gnits options
2774 * More standards checking
2776 * Cleaned up 'dist' targets
2777 * Added AUTOMAKE_OPTIONS variable and several options
2778 * Now scans configure.in to get some information (preliminary)
2781 * Works with Perl 4 again
2784 * Added --install-missing option.
2785 * Pretty-prints generated macros and rules
2786 * Comments in Makefile.am are placed more intelligently in Makefile.in
2787 * Generates .PHONY target
2788 * Rule or macro in Makefile.am now overrides contents of Automake file
2789 * Substantial cleanups from François Pinard
2793 * Works with Perl 4 again.
2796 * New uniform naming scheme.
2797 * --strictness option
2799 * '.c' files corresponding to '.y' or '.l' files are automatically
2801 * Many bug fixes and cleanups
2804 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2807 * Bug fixes in 'clean' code.
2808 * Now generates 'installdirs' target.
2809 * man page installation reworked.
2810 * 'make dist' no longer re-creates all Makefile.in's.
2813 * Reimplemented in Perl
2814 * Added --amdir option (for debugging)
2815 * Texinfo support cleaned up.
2816 * Automatic de-ANSI-fication cleaned up.
2817 * Cleaned up 'clean' targets.
2820 * Automatic dependency tracking
2821 * More documentation
2822 * New variables DATA and PACKAGEDATA
2823 * SCRIPTS installed using $(INSTALL_SCRIPT)
2824 * No longer uses double-colon rules
2826 * Changes in advance of internationalization
2830 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2832 This program is free software; you can redistribute it and/or modify
2833 it under the terms of the GNU General Public License as published by
2834 the Free Software Foundation; either version 2, or (at your option)
2837 This program is distributed in the hope that it will be useful,
2838 but WITHOUT ANY WARRANTY; without even the implied warranty of
2839 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2840 GNU General Public License for more details.
2842 You should have received a copy of the GNU General Public License
2843 along with this program. If not, see <http://www.gnu.org/licenses/>.