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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
111 - The user is no longer allowed to override the --srcdir nor the --prefix
112 configure options used by "make distcheck" (bug#14991).
114 - Fixed a gross inefficiency in the recipes for installing byte-compiled
115 python files, that was causing an O(N^2) performance on the number N of
116 files, instead of the expected O(N) performance. Note that this bug
117 was only relevant when the number of python files was high (which is
118 unusual in practice).
120 - Automake try to offer a more reproducible output for warning messages,
121 in the face of the newly-introduced randomization for hash keys order
124 - The 'test-driver' script now actually error out with a clear error
125 message on the most common invalid usages.
127 - Several spurious failures/hangs in the testsuite (bugs #14706, #14707,
128 #14760, #14911, #15181, #15237).
130 * Documentation fixes:
132 - Fixed typos in the 'fix-timestamp.sh' example script that made it
135 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
139 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
141 - The 'compile' script is now unconditionally required for all packages
142 that perform C compilation (if you are using the '--add-missing'
143 option, automake will fetch that script for you, so you shouldn't
144 need any explicit adjustment). This new behaviour is needed to avoid
145 obscure errors when the 'subdir-objects' option is used, and the
146 compiler is an inferior one that doesn't grasp the combined use of
147 both the "-c -o" options; see discussion about automake bug#13378 for
149 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
150 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
152 - The next major Automake version (2.0) will unconditionally activate
153 the 'subdir-objects' option. In order to smooth out the transition,
154 we now give a warning (in the category 'unsupported') whenever a
155 source file is present in a subdirectory but the 'subdir-object' is
156 not enabled. For example, the following usage will trigger such a
159 bin_PROGRAMS = sub/foo
160 sub_foo_SOURCES = sub/main.c sub/bar.c
162 - Automake will automatically enhance the autoconf-provided macro
163 AC_PROG_CC to force it to check, at configure time, that the
164 C compiler supports the combined use of both the '-c' and '-o'
165 options. The result of this check is saved in the cache variable
166 'am_cv_prog_cc_c_o', and said result can be overridden by
167 pre-defining that variable.
169 - The AM_PROG_CC_C_O macro can still be called, albeit that should no
170 longer be necessary. This macro is now just a thin wrapper around the
171 Automake-enhanced AC_PROG_CC. This means, among the other things,
172 that its behaviour is changed in three ways:
174 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
175 macro behind the scenes.
177 2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
178 and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
179 dynamically computed only at configure runtime (really!) from
180 the content of the '$CC' variable.
182 3. It no longer automatically AC_DEFINE the C preprocessor
183 symbol 'NO_MINUS_C_MINUS_O'.
187 - Automake can now be instructed to place '.info' files generated from
188 Texinfo input in the builddir rather than in the srcdir; this is done
189 specifying the new automake option 'info-in-builddir'. This feature
190 was requested by the developers of GCC, GDB, GNU binutils and the GNU
191 bfd library. See the extensive discussion about automake bug#11034
194 - For quite a long time, Automake has been implementing an undocumented
195 hack which ensured that '.info' files which appeared to be cleaned
196 (by being listed in the CLEANFILES or DISTCLEANFILES variables) were
197 built in the builddir rather than in the srcdir; this hack was
198 introduced to ensure better backward-compatibility with package
199 such as Texinfo, which do things like:
201 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
202 DISTCLEANFILES = texinfo texinfo-* info*.info*
203 # Do not create info files for distribution.
207 in order not to distribute generated '.info' files.
209 Now that we have the 'info-in-builddir' option that explicitly causes
210 generated '.info' files to be placed in the builddir, this hack should
211 be longer necessary, so we deprecate it with runtime warnings. It will
212 likely be removed altogether in Automake 2.0.
214 * Relative directory in Makefile fragments:
216 - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
217 (and their short versions, '%D%' and '%C%' respectively) can now be used
218 in an included Makefile fragment. The former is substituted with the
219 relative directory of the included fragment (compared to the top-level
220 including Makefile), and the latter with the canonicalized version of
221 the same relative directory.
224 bin_PROGRAMS = # will be updated by included Makefile fragments
225 include src/Makefile.inc
227 # in 'src/Makefile.inc':
228 bin_PROGRAMS += %reldir%/foo
229 %canon_reldir%_foo_SOURCES = %reldir%/bar.c
231 This should be especially useful for packages using a non-recursive
234 * Deprecated distribution formats:
236 - The 'shar' and 'compress' distribution formats are deprecated, and
237 scheduled for removal in Automake 2.0. Accordingly, the use of the
238 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
239 (in the 'obsolete' category), and the recipes of the Automake-generated
240 targets 'dist-shar' and 'dist-tarZ' will unconditionally display
241 (non-fatal) warnings at make runtime.
243 * New configure runtime warnings about "rm -f" support:
245 - To simplify transition to Automake 2.0, the shell code expanded by
246 AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
247 'rm' program in PATH doesn't complain when called without any
248 non-option argument if the '-f' option is given (so that commands like
249 "rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
250 If this is not the case, the configure script is aborted, to call the
251 attention of the user on the issue, and invite him to fix his PATH.
252 The checked 'rm' behavior is very widespread in the wild, and will be
253 required by future POSIX versions:
255 <http://austingroupbugs.net/view.php?id=542>
257 The user can still force the configure process to complete even in the
258 presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
259 environment variable to "yes". And the generated Makefiles should
260 still work correctly even when such broken 'rm' is used. But note
261 that this will no longer be the case with Automake 2.0 though, so, if
262 you encounter the warning, please report it to us ASAP (and try to fix
263 your environment as well).
265 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
271 - Fix a minor regression introduced in Automake 1.13.3: when two or more
272 user-defined suffix rules were present in a single Makefile.am,
273 automake would needlessly include definition of some make variables
274 related to C compilation in the generated Makefile.in (bug#14560).
276 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
280 * Documentation fixes:
282 - The documentation no longer mistakenly reports that the obsolete
283 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
284 to be removed in Automake 2.0.
288 - Byte-compilation of Emacs lisp files could fail spuriously on
289 Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
291 - If the same user-defined suffixes were transformed into different
292 Automake-known suffixes in different Makefile.am files in the same
293 project, automake could get confused and generate inconsistent
294 Makefiles (automake bug#14441).
295 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
296 and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
297 would have mistakenly placed into 'Makefile.in' rules to compile
298 "*.c" files into object files, and into 'sub/Makefile.in' rules to
299 compile "*.cc" files into object files --- rather than the other
300 way around. This is now fixed.
304 - The test cases no longer have the executable bit set. This should
305 make it clear that they are not meant to be run directly; as
306 explained in t/README, they can only be run through the custom
307 'runtest' script, or by a "make check" invocation.
309 - The testsuite has seen the introduction of a new helper function
310 'run_make', and several related changes. These serve a two-fold
313 1. Remove brittleness due to the use of "make -e" in test cases.
315 2. Seamlessly allow the use of parallel make ("make -j...") in the
316 test cases, even where redirection of make output is involved
317 (see automake bug#11413 for a description of the subtle issues
320 - Several spurious failures have been fixed (they hit especially
321 MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
322 #14498, #14499, #14500, #14501, #14517 and #14528.
324 - Some other minor miscellaneous changes and fixlets.
326 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
330 * Documentation fixes:
332 - The long-deprecated but still supported two-arguments invocation form
333 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
334 thing to do, given that support for such usage might need to remain
335 in place for an unspecified amount of time in order to cater to people
336 who want to define the version number for their package dynamically at
337 configure runtime (unfortunately, Autoconf does not yet support this
338 scenario, so we cannot delegate the work to it).
340 - The serial testsuite harness is no longer reported as "deprecated",
341 but as "discouraged". We have no plan to remove it, nor to make its
342 use cause runtime warnings.
344 - The parallel testsuite is no longer reported as "experimental"; it
345 is well tested, and should be stable now.
347 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
348 'dist-tarZ' options are obsolescent, and their use is deprecated
349 in the documentation.
351 - Other minor miscellaneous fixes and improvements; in particular,
352 some improvements in cross-references.
354 * Obsolescent features:
356 - Use of suffix-less info files (that can be specified through the
357 '@setfilename' macro in Texinfo input files) is discouraged, and
358 its use will raise warnings in the 'obsolete' category. Simply
359 use the '.info' extension for all your info files, transforming
362 @setfilename myprogram
366 @setfilename myprogram.info
368 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
369 is discouraged, and its use will raise warnings in the 'obsolete'
370 category. You are advised to simply use the '.texi' extension
375 - When the 'ustar' option is used, the generated configure script no
376 longer risks hanging during the tests for the availability of the
377 'pax' utility, even if the user running configure has a UID or GID
378 that requires more than 21 bits to be represented.
379 See automake bug#8343 and bug#13588.
381 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
382 again, as they did in Automake 1.12.x (albeit printing runtime
383 warnings in the 'obsolete' category). Removing them has turned
384 out to be a very bad idea, because it complicated distro packing
385 enormously. Making them issue fatal warnings, as we did in
386 Automake 1.13, has turned out to be a similarly very bad idea,
387 for exactly the same reason.
389 - aclocal will no longer error out if the first local m4 directory
390 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
391 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
392 a warning in the 'unsupported' category. This is done to support
393 some pre-existing real-world usages. See automake bug#13514.
395 - aclocal will no longer consider directories for extra m4 files more
396 than once, even if they are specified multiple times. This ensures
397 packages that specify both
399 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
400 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
402 will work correctly, even when the 'm4' directory contains no
403 package-specific files, but is used only to install third-party
404 m4 files (as can happen with e.g., "libtoolize --install").
405 See automake bug#13514.
407 - Analysis of make flags in Automake-generated rules has been made more
408 robust, and more future-proof. For example, in presence of make that
409 (like '-I') take an argument, the characters in said argument will no
410 longer be spuriously considered as a set of additional make options.
411 In particular, automake-generated rules will no longer spuriously
412 believe to be running in dry mode ("make -n") if run with an invocation
413 like "make -I noob"; nor will they believe to be running in keep-going
414 mode ("make -k") if run with an invocation like "make -I kool"
415 (automake bug#12554).
417 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
423 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
424 causes a clear and helpful error message, instead of obscure ones
425 (issue introduced in Automake 1.13).
427 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
433 - ylwrap renames properly header guards in generated header files
434 (*.h), instead of leaving Y_TAB_H.
436 - ylwrap now also converts header guards in implementation files
437 (*.c). Because ylwrap failed to rename properly #include in the
438 implementation files, current versions of Bison (e.g., 2.7)
439 duplicate the generated header file in the implementation file.
440 The header guard then protects the implementation file from
441 duplicate definitions from the header file.
443 * Version requirements:
445 - Autoconf 2.65 or greater is now required.
447 - The rules to build PDF and DVI output from Texinfo input now
448 require Texinfo 4.9 or later.
452 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
453 option) has been removed. See discussion about automake bug#11034
454 for more background: <http://debbugs.gnu.org/11034>.
456 - The deprecated aclocal option '--acdir' has been removed. You
457 should use the options '--automake-acdir' and '--system-acdir'
458 instead (which have been introduced in Automake 1.11.2).
460 - The following long-obsolete m4 macros have been removed:
462 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
463 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
464 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
465 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
466 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
467 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
468 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
469 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
470 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
471 of the now-removed automatic de-ANSI-fication
474 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
476 - Use of the long-deprecated two- and three-arguments invocation forms
477 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
478 though (albeit with a warning in the 'obsolete' category), to cater
479 for people who want to define the version number for their package
480 dynamically (e.g., from the current VCS revision). We'll have to
481 continue this support until Autoconf itself is fixed to allow better
482 support for such dynamic version numbers.
484 * Elisp byte-compilation:
486 - The byte compilation of '.el' files into '.elc' files is now done
487 with a suffix rule. This has simplified the compilation process, and
488 more importantly made it less brittle. The downside is that emacs is
489 now invoked once for each '.el' files, which cause some noticeable
490 slowdowns. These should however be mitigated on multicore machines
491 (which are becoming the norm today) if concurrent make ("make -j")
494 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
495 files in the same subdirectory; for example, byte-compiling of file
496 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
497 'foo.elc'. This behaviour is backward-incompatible with older
498 Automake versions, but it is more natural and more sane. See also
501 - The Emacs invocation performing byte-compilation of '.el' files honors
502 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
503 one is developer-reserved and the latter one user-reserved.
505 - The 'elisp-comp' script, once provided by Automake, has been rendered
506 obsoleted by the just-described changes, and thus removed.
508 * Changes to Automake-generated testsuite harnesses:
510 - The parallel testsuite harness (previously only enabled by the
511 'parallel-tests' option) is the default one; the older serial
512 testsuite harness will still be available through the use of the
513 'serial-tests' option (introduced in Automake 1.12).
515 - The 'color-tests' option is now unconditionally activated by default.
516 In particular, this means that testsuite output is now colorized by
517 default if the attached terminal seems to support ANSI escapes, and
518 that the user can force output colorization by setting the variable
519 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
520 for backward-compatibility, although it's a handled as a no-op now.
522 * Silent rules support:
524 - Support for silent rules is now always active in Automake-generated
525 Makefiles. So, although the verbose output is still the default,
526 the user can now always use "./configure --enable-silent-rules" or
527 "make V=0" to enable quieter output in the package he's building.
529 - The 'silent-rules' option has now become a no-op, preserved for
530 backward-compatibility only. In particular, its use no longer
531 disables the warnings in the 'portability-recursive' category.
535 - The rules to build PDF and DVI files from Texinfo input now require
536 Texinfo 4.9 or later.
538 - The rules to build PDF and DVI files from Texinfo input now use the
539 '--build-dir' option, to keep the auxiliary files used by texi2dvi
540 and texi2pdf around without cluttering the build directory, and to
541 make it possible to run the "dvi" and "pdf" recipes in parallel.
543 * Automatic remake rules and 'missing' script:
545 - The 'missing' script no longer tries to update the timestamp of
546 out-of-date files that require a maintainer-specific tool to be
547 remade, in case the user lacks such a tool (or has a too-old version
548 of it). It just gives a useful warning, and in some cases also a
549 tip about how to obtain such a tool.
551 - The missing script has thus become useless as a (poor) way to work
552 around the sketched-timestamps issues that can happen for projects
553 that keep generated files committed in their VCS repository. Such
554 projects are now encouraged to write a custom "fix-timestamps.sh"
555 script to avoid such issues; a simple example is provided in the
556 "CVS and generated files" chapter of the automake manual.
560 - The user can now define his own recursive targets that recurse
561 in the directories specified in $(SUBDIRS). This can be done by
562 specifying the name of such targets in invocations of the new
563 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
567 - Any failure in the recipe of the "tags", "ctags", "cscope" or
568 "cscopelist" targets in a subdirectory is now propagated to the
569 top-level make invocation.
571 - Tags are correctly computed also for files in _SOURCES variables that
572 only list files with non-standard suffixes (see automake bug#12372).
574 * Improvements to aclocal and related rebuilds rules:
576 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
577 are now traced by aclocal, and can be used to declare the local m4
578 include directories. Formerly, one had to specify it with an explicit
579 '-I' option to the 'aclocal' invocation.
581 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
582 Automake versions will warn about its use, and later version will
583 remove support for it altogether.
585 * The depcomp script:
587 - Dropped support for libtool 1.4.
589 - Various internal refactorings. They should cause no visible change,
590 but the chance for regression is there anyway, so please report any
591 unexpected or suspicious behaviour.
593 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
594 This should cause no problem, since icc 8.0 has been released in
595 December 2003 -- almost nine years ago.
597 - Support for tcc (the Tiny C Compiler) has been improved, and is now
598 handled through a dedicated 'tcc' mode.
602 - ylwrap generates header guards with a single '_' for series of non
603 alphabetic characters, instead of several. This is what Bison >=
606 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
608 Bugs fixed in 1.12.6:
610 * Python-related bugs:
612 - The default installation location for python modules has been improved
613 for Python 3 on Debian and Ubuntu systems, changing from:
615 ${prefix}/lib/python3/dist-packages
619 ${prefix}/lib/python3.x/site-packages
621 This change should ensure modules installed using the default ${prefix}
622 "/usr/local" are found by default by system python 3.x installations.
623 See automake bug#10227.
625 - Python byte-compilation supports the new layout mandated by PEP-3147,
626 with its __pycache__ directory (automake bug#8847).
628 * Build system issues:
630 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
631 Automake's own build system works correctly again (bug introduced
636 - The Vala-related tests has been changed to adjust to the removal of
637 the 'posix' profile in the valac compiler. See automake bug#12934
640 - Some spurious testsuite failures related to older tools and systems
643 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
649 - The AM_PROG_VALAC macro has been enhanced to takes two further
650 optional arguments; it's signature now being
652 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
653 [ACTION-IF-NOT-FOUND])
655 - By default, AM_PROG_VALAC no longer aborts the configure invocation
656 if the Vala compiler found is too old, but simply prints a warning
657 messages (as it did when the Vala compiler was not found). This
658 should avoid unnecessary difficulties for end users that just want
659 to compile the unmodified, distributed Vala-generated C sources,
660 but happens to have an old Vala compiler in their PATH. This fixes
663 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
664 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
665 This is a better default, because with it a triggered makefile rule
666 invoking a Vala compilation will clearly fail with an informative error
667 message like "valac: command not found", rather than silently, with
668 the error possibly going unnoticed or triggering harder-to-diagnose
669 fallout failures in later steps.
671 * Miscellaneous changes:
673 - automake and aclocal no longer honours the 'perllibdir' environment
674 variable. That had always been intended only as an hack required in
675 the testsuite, not meant for any use beyond that.
677 Bugs fixed in 1.12.5:
679 * Long-standing bugs:
681 - Automake no longer generates spurious remake rules invoking autoheader
682 to regenerate the template corresponding to header files specified after
683 the first one in AC_CONFIG_HEADERS (automake bug#12495).
685 - When wrapping Microsoft tools, the 'compile' script falls back to
686 finding classic 'libname.a' style libraries when 'name.lib' and
687 'name.dll.lib' aren't available.
689 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
693 * Warnings and deprecations:
695 - Warnings in the 'obsolete' category are enabled by default both in
696 automake and aclocal.
698 * Miscellaneous changes:
700 - Some testsuite weaknesses and spurious failures have been fixed.
702 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
706 * Miscellaneous changes:
708 - The '.m4' files provided by Automake no longer define serial numbers.
709 This should cause no difference in the behaviour of aclocal though.
711 - Some testsuite weaknesses and spurious failures have been fixed.
713 - There is initial support for automatic dependency tracking with the
714 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
716 Bugs fixed in 1.12.3:
718 * Long-standing bugs:
720 - Instead of renaming only self-references of files (typically for
721 #lines), ylwrap now also renames references to the other generated
722 files. This fixes support for GLR and C++ parsers from Bison (PR
723 automake/491 and automake bug#7648): 'parser.c' now properly
724 #includes 'parser.h' instead of 'y.tab.h'.
726 - Generated files unknown to ylwrap are now preserved. This fixes
727 C++ support for Bison (automake bug#7648): location.hh and the
728 like are no longer discarded.
730 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
734 * Warnings and deprecations:
736 - Automake now issues a warning (in the 'portability' category) if
737 'configure.in' is used instead of 'configure.ac' as the Autoconf
738 input file. Such a warning will also be present in the next
739 Autoconf version (2.70).
743 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
744 order (as done by the other recursive rules), rather than in the
745 inverse order. They used to do that in order to work a round a
746 limitation in an older implementation of the automatic dependency
747 tracking support, but that limitation had been lifted years ago
748 already, when the automatic dependency tracking based on side-effects
749 of compilation had been introduced.
751 - Cleaning rules for compiled objects (both "plain" and libtool) work
752 better when subdir objects are involved, not triggering a distinct
753 'rm' invocation for each such object. They do so by removing *any*
754 compiled object file that is in the same directory of a subdir
755 object. See automake bug#10697.
757 * Silent rules support:
759 - A new predefined $(AM_V_P) make variable is provided; it expands
760 to a shell conditional that can be used in recipes to know whether
761 make is being run in silent or verbose mode.
763 Bugs fixed in 1.12.2:
765 * SECURITY VULNERABILITIES!
767 - The 'distcheck' recipe no longer grants temporary world-write
768 permissions on the extracted distdir. Even if such rights were
769 only granted for a vanishingly small time window, the implied
770 race condition proved to be enough to allow a local attacker
771 to run arbitrary code with the privileges of the user running
772 "make distcheck". This is CVE-2012-3386.
774 * Long-standing bugs:
776 - The "recheck" targets behaves better in the face of build failures
777 related to previously failed tests. For example, if a test is a
778 compiled program that must be rerun by "make recheck", and its
779 compilation fails, it will still be rerun by further "make recheck"
780 invocations. See automake bug#11791.
782 * Bugs introduced by 1.12.1:
784 - Automake provides once again the '$(mkdir_p)' make variable and the
785 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
786 for better backward-compatibility.
788 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
792 * New supported languages:
794 - Support for Objective C++ has been added; it should work similarly to
795 the support for Objective C.
797 * Deprecated obsolescent features:
799 - Use of the long-deprecated two- and three-arguments invocation forms
800 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
801 category. Starting from some future major Automake release (likely
802 post-1.13), such usages will no longer be allowed.
804 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
805 now deprecated (its use triggers a warning in the 'obsolete' category).
806 It will be removed in the next major Automake release (1.13).
808 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
809 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
810 m4 macro are deprecated, eliciting a warning in the 'obsolete'
813 * Miscellaneous changes:
815 - The Automake test cases now require a proper POSIX-conforming shell.
816 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
817 be accepted. In most cases, the user shouldn't have to specify such
818 POSIX shell explicitly, since it will be looked up at configure time.
819 Still, when this lookup fails, or when the user wants to override its
820 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
821 to the shell that will be used to run the Automake test cases).
823 Bugs fixed in 1.12.1:
825 * Bugs introduced by 1.12:
827 - Several weaknesses in Automake's own build system and test suite
830 * Bugs introduced by 1.11.3:
832 - When given non-option arguments, aclocal rejects them, instead of
833 silently ignoring them.
835 * Long-standing bugs:
837 - When the 'color-tests' option is in use, forcing of colored testsuite
838 output through "AM_COLOR_TESTS=always" works even if the terminal is
839 a non-ANSI one, i.e., if the TERM environment variable has a value of
842 - Several inefficiencies and poor performances in the implementation
843 of the parallel-tests 'check' and 'recheck' targets have been fixed.
845 - The post-processing of output "#line" directives done the ylwrap
846 script is more faithful w.r.t. files in a subdirectory; for example,
847 if the processed file is "src/grammar.y", ylwrap will correctly
848 produce directives like:
849 #line 7 "src/grammar.y"
854 * Bugs with new Perl versions:
856 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
858 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
862 * Obsolete features removed:
864 - The never documented nor truly used script 'acinstall' has been
867 - Support for automatic de-ANSI-fication has been removed.
869 - The support for the "obscure" multilib feature has been removed
870 from Automake core (but remains available in the 'contrib/'
871 directory of the Automake distribution).
873 - Support for ".log -> .html" conversion and the check-html and
874 recheck-html targets has been removed from Automake core (but
875 remains available in the 'contrib/' directory of the Automake
878 - The deprecated 'lzma' compression format for distribution archives
879 has been removed, in favor of 'xz' and 'lzip'.
881 - The obsolete AM_WITH_REGEX macro has been removed.
883 - The long-deprecated options '--output-dir', '--Werror' and
884 '--Wno-error' have been removed.
886 - The chapter on the history of Automake has been moved out of the
887 reference manual, into a new dedicated Texinfo file.
891 - New 'cscope' target to build a cscope database for the source tree.
893 * Changes to Automake-generated testsuite harnesses:
895 - The new automake option 'serial-tests' has been introduced. It can
896 be used to explicitly instruct automake to use the older serial
897 testsuite harness. This is still the default at the moment, but it
898 might change in future versions.
900 - The 'recheck' target (provided by the parallel testsuite harness) now
901 depends on the 'all' target. This allows for a better user-experience
902 in test-driven development. See automake bug#11252.
904 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
905 and unexpected or internal error, or a failure to set up the test case
906 scenario) have their outcome reported as an 'ERROR' now. Previous
907 versions of automake reported such an outcome as a 'FAIL' (the only
908 difference with normal failures being that hard errors were counted
909 as failures even when the test originating them was listed in
912 - The testsuite summary displayed by the parallel-test harness has a
913 completely new format, that always list the numbers of passed, failed,
914 xfailed, xpassed, skipped and errored tests, even when these numbers
915 are zero (but using smart coloring when the color-tests option is in
918 - The default testsuite driver offered by the 'parallel-tests' option is
919 now implemented (partly at least) with the help of automake-provided
920 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
921 on code in the generated Makefile.in.
922 This has two noteworthy implications. The first one is that projects
923 using the 'parallel-tests' option should now either run automake with
924 the '--add-missing' option, or manually copy the 'test-driver' script
925 into their tree. The second, and more important, implication is that
926 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
927 no longer be used to define a test runner, and the command specified
928 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
929 program or script. For example, this is still a valid usage (albeit
932 TESTS_ENVIRONMENT = \
933 if test -n '$(STRICT_TESTS)'; then \
934 maybe_errexit='-e'; \
938 LOG_COMPILER = $(SHELL) $$maybe_errexit
940 OTOH, this is no longer a valid usage:
942 TESTS_ENVIRONMENT = \
943 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
947 TESTS_ENVIRONMENT = \
948 run_with_perl_or_shell () \
950 if grep -q '^#!.*perl' $$1; then
956 LOG_COMPILER = run_with_perl_or_shell
958 - The package authors can now use customary testsuite drivers within
959 the framework provided by the 'parallel-tests' testsuite harness.
960 Consistently with the existing syntax, this can be done by defining
961 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
963 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
964 to redirect/define file descriptors used by the test scripts.
966 - The parallel-tests harness generates now, in addition the '.log' files
967 holding the output produced by the test scripts, a new set of '.trs'
968 files, holding "metadata" derived by the execution of the test scripts;
969 among such metadata are the outcomes of the test cases run by a script.
971 - Initial and still experimental support for the TAP test protocol is
974 * Changes to Yacc and Lex support:
976 - C source and header files derived from non-distributed Yacc and/or
977 Lex sources are now removed by a simple "make clean" (while they were
978 previously removed only by "make maintainer-clean").
980 - Slightly backward-incompatible change, relevant only for use of Yacc
981 with C++: the extensions of the header files produced by the Yacc
982 rules are now modelled after the extension of the corresponding
983 sources. For example, yacc files named "foo.y++" and "bar.yy" will
984 produce header files named "foo.h++" and "bar.hh" respectively, where
985 they would have previously produced header files named simply "foo.h"
986 and "bar.h". This change offers better compatibility with 'bison -o'.
988 * Miscellaneous changes:
990 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
991 rather than 1, if the vala compiler found is too old.
993 - The build system of Automake itself now avoids the use of make
994 recursion as much as possible.
996 - Automake now prefers to quote 'like this' or "like this", rather
997 than `like this', in diagnostic message and generated Makefiles,
998 to accommodate the new GNU Coding Standards recommendations.
1000 - Automake has a new option '--print-libdir' that prints the path of the
1001 directory containing the Automake-provided scripts and data files.
1003 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
1005 - The rules to create pdf, dvi and ps output from Texinfo files now
1006 works better with modern 'texi2dvi' script, by explicitly passing
1007 it the '--clean' option to ensure stray auxiliary files are not
1008 left to clutter the build directory.
1010 - Automake can now generate silenced rules for texinfo outputs.
1012 - Some auxiliary files that are automatically distributed by Automake
1013 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
1014 C sources) might now be listed in the DIST_COMMON variable in many
1015 Makefile.in files, rather than in the top-level one.
1017 - Messages of types warning or error from 'automake' and 'aclocal'
1018 are now prefixed with the respective type, and presence of -Werror
1021 - Automake's early configure-time sanity check now tries to avoid
1022 sleeping for a second, which slowed down cached configure runs
1023 noticeably. In that case, it will check back at the end of the
1024 configure script to ensure that at least one second has passed, to
1025 avoid time stamp issues with makefile rules rerunning autotools
1028 - The warnings in the category 'extra-portability' are now enabled by
1029 '-Wall'. In previous versions, one has to use '-Wextra-portability'
1034 - Various minor bugfixes for recent or long-standing bugs.
1036 * Bugs introduced by 1.11:
1038 - The AM_COND_IF macro also works if the shell expression for the
1039 conditional is no longer valid for the condition.
1041 - The automake-provided parallel testsuite harness no longer fails
1042 with BSD make used in parallel mode when there are test scripts in
1043 a subdirectory, like in:
1045 TESTS = sub/foo.test sub/bar.test
1047 * Long-standing bugs:
1049 - Automake's own build system finally have a real "installcheck" target.
1051 - Vala-related cleanup rules are now more complete, and work better in
1054 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
1055 now automatically distributed also if the directory of the auxiliary
1056 files coincides with the top-level directory.
1058 - Automake now detects the presence of the '-d' flag in the various
1059 '*YFLAGS' variables even when their definitions involve indirections
1060 through other variables, such as in:
1062 AM_YFLAGS = $(foo_opts)
1064 - Automake now complains if a '*YFLAGS' variable has any conditional
1065 content, not only a conditional definition.
1067 - Explicit enabling and/or disabling of Automake warning categories
1068 through the '-W...' options now always takes precedence over the
1069 implicit warning level implied by Automake strictness (foreign, gnu
1070 or gnits), regardless of the order in which such strictness and
1071 warning flags appear. For example, a setting like:
1072 AUTOMAKE_OPTIONS = -Wall --foreign
1073 will cause the warnings in category 'portability' to be enabled, even
1074 if those warnings are by default disabled in 'foreign' strictness.
1076 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1078 Bugs fixed in 1.11.5:
1080 * Bugs introduced by 1.11.3:
1082 - Vala files with '.vapi' extension are now recognized and handled
1083 correctly again. See automake bug#11222.
1085 - Vala support work again for projects that contain some program
1086 built from '.vala' (and possibly '.c') sources and some other
1087 program built from '.c' sources *only*. See automake bug#11229.
1089 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1093 * Miscellaneous changes:
1095 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
1096 symbol index) modifiers as well as the "s" action, as the symbol index
1097 is created unconditionally by Microsoft lib. Also, the "q" (quick)
1098 action is now a synonym for "r" (replace). Also, the script has been
1099 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
1101 - When the 'compile' script is used to wrap MSVC, it now accepts an
1102 optional space between the -I, -L and -l options and their respective
1103 arguments, for better POSIX compliance.
1105 - There is an initial, experimental support for automatic dependency
1106 tracking with tcc (the Tiny C Compiler). Its associated depmode is
1107 currently recognized as "icc" (but this and other details are likely
1108 to change in future versions).
1110 - Automatic dependency tracking now works also with the IBM XL C/C++
1111 compilers, thanks to the new new depmode 'xlc'.
1113 Bugs fixed in 1.11.4:
1115 * Bugs introduced by 1.11.2:
1117 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
1118 no longer cause spurious failures upon "make install".
1120 - The user can now instruct the 'uninstall-info' rule not to update
1121 the '${infodir}/dir' file by exporting the environment variable
1122 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
1123 with how the 'install-info' rule operates since automake 1.11.2.
1125 * Long-standing bugs:
1127 - It is now possible for a foo_SOURCES variable to hold Vala sources
1128 together with C header files, as well as with sources and headers for
1129 other supported languages (e.g., C++). Previously, only mixing C and
1130 Vala sources was supported.
1132 - If "aclocal --install" is used, and the first directory specified with
1133 '-I' is non-existent, aclocal will now create it before trying to copy
1136 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
1137 install rules to create an empty $(foodir) directory; for example, if
1138 Makefile.am contains something like:
1140 pkglibexec_SCRIPTS =
1142 pkglibexec_SCRIPTS += bar.sh
1145 the $(pkglibexec) directory will not be created upon "make install".
1147 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1151 * Miscellaneous changes:
1153 - Automake's own build system is more silent by default, making use of
1154 the 'silent-rules' option.
1156 - The master copy of the 'gnupload' script is now maintained in gnulib,
1159 - The 'missing' script no longer tries to wrap calls to 'tar'.
1161 - "make dist" no longer wraps 'tar' invocations with the 'missing'
1162 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
1163 shouldn't be using BTW ;-) no longer invokes the 'missing' script
1164 to wrap tar, but simply invokes the 'tar' program itself.
1166 - "make dist" can now create lzip-compressed tarballs.
1168 - In the Automake info documentation, the Top node and the nodes about
1169 the invocation of the automake and aclocal programs have been renamed;
1170 now, calling "info automake" will open the Top node, while calling
1171 "info automake-invocation" and "info aclocal-invocation" will access
1172 the nodes about the invocation of respectively automake and aclocal.
1174 - Automake is now distributed as a gzip-compressed and an xz-compressed
1175 tarball. Previously, bzip2 was used instead of xz.
1177 - The last relics of Python 1.5 support have been removed from the
1178 AM_PATH_PYTHON macro.
1180 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
1181 and adds them to the normal list of dependencies, but without
1182 overwriting the foo_DEPENDENCIES variable, which is normally computed
1185 Bugs fixed in 1.11.3:
1187 * Bugs introduced by 1.11.2:
1189 - Automake now correctly recognizes the prefix/primary combination
1190 'pkglibexec_SCRIPTS' as valid.
1192 - The parallel-tests harness no longer trips on sed implementations
1193 with stricter limits on the length of input lines (problem seen at
1194 least on Solaris 8).
1196 * Long-standing bugs:
1198 - The "deleted header file problem" for *.am files is avoided by stub
1199 rules. This allows 'make' to trigger a rerun of 'automake' also if
1200 some previously needed '.am' file has been removed.
1202 - The 'silent-rules' option now generates working makefiles even
1203 for the uncommon 'make' implementations that do not support the
1204 nested-variables extension to POSIX 2008. For such 'make'
1205 implementations, whether a build is silent is determined at
1206 configure time, and cannot be overridden at make time with
1207 "make V=0" or "make V=1".
1209 - Vala support now works better in VPATH setups.
1211 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1215 * Changes to aclocal:
1217 - The `--acdir' option is deprecated. Now you should use the new options
1218 `--automake-acdir' and `--system-acdir' instead.
1220 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1221 colon-separated list of additional directories to search after the
1222 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1223 and before the system acdir (by default ${prefix}/share/aclocal).
1225 * Miscellaneous changes:
1227 - The Automake support for automatic de-ANSI-fication has been
1228 deprecated. It will probably be removed in the next major Automake
1231 - The `lzma' compression scheme and associated automake option `dist-lzma'
1232 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1234 - You may adjust the compression options used in dist-xz and dist-bzip2.
1235 The default is now merely -e for xz, but still -9 for bzip; you may
1236 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1237 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1239 - The `compile' script now converts some options for MSVC for a better
1240 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1242 - The py-compile script now accepts empty arguments passed to the options
1243 `--destdir' and `--basedir', and complains about unrecognized options.
1244 Moreover, a non-option argument or a special `--' argument terminates
1245 the list of options.
1247 - A developer that needs to pass specific flags to configure at "make
1248 distcheck" time can now, and indeed is advised to, do so by defining
1249 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1250 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1251 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1252 user; still, the old Makefile.am files that used to define it will
1253 still continue to work as before.
1255 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1256 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1257 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1258 is run with -Wextra-portability and -Werror.
1260 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1261 file generated by automake-provided rules by defining the special make
1262 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1264 - The `install-info' rule can now be instructed not to create/update
1265 the `${infodir}/dir' file, by exporting the new environment variable
1266 `AM_UPDATE_INFO_DIR' to the value "no".
1268 Bugs fixed in 1.11.2:
1270 * Bugs introduced by 1.11:
1272 - The parallel-tests driver no longer produces erroneous results with
1273 Tru64/OSF 5.1 sh upon unreadable log files.
1275 - The `parallel-tests' test driver does not report spurious successes
1276 when used with concurrent FreeBSD make (e.g., "make check -j3").
1278 - When the parallel-tests driver is in use, automake now explicitly
1279 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1280 instead of issuing confusing and apparently unrelated error messages
1281 (e.g., "non-POSIX variable name", "bad characters in variable name",
1282 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1283 silently producing broken `Makefile.in' files.
1285 - The `silent-rules' option now truly silences all compile rules, even
1286 when dependency tracking is disabled. Also, when `silent-rules' is
1287 not used, `make' output no longer contains spurious backslash-only
1288 lines, thus once again matching what Automake did before 1.11.
1290 - The AM_COND_IF macro also works if the shell expression for the
1291 conditional is no longer valid for the condition.
1293 * Long-standing bugs:
1295 - The order of Yacc and Lex flags is fixed to be consistent with other
1296 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1297 $(LFLAGS), so that the user variables override the developer variables.
1299 - "make distcheck" now correctly complains also when "make uninstall"
1300 leaves one and only one file installed in $(prefix).
1302 - A "make uninstall" issued before a "make install", or after a mere
1303 "make install-data" or a mere "make install-exec" does not spuriously
1306 - Automake now warns about more primary/directory invalid combinations,
1307 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1309 - Rules generated by Automake now try harder to not change any files when
1310 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1311 Yacc source files and the rule to update config.h.
1313 - Several scripts and the parallel-tests testsuite driver now exit with
1314 the right exit status upon receiving a signal.
1316 - A per-Makefile.am setting of -Werror does not erroneously carry over
1317 to the handling of other Makefile.am files.
1319 - The code for automatic dependency tracking works around a Solaris
1320 make bug triggered by sources containing repeated slashes when the
1321 `subdir-objects' option was used.
1323 - The makedepend and hp depmodes now work better with VPATH builds.
1325 - Java sources specified with check_JAVA are no longer compiled for
1326 "make all", but only for "make check".
1328 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1329 and error out if `javadir' is undefined, instead of silently producing
1330 a broken Makefile.in.
1332 - aclocal and automake now honour the configure-time definitions of
1333 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1335 - The `install-info' recipe no longer tries to guess whether the
1336 `install-info' program is from Debian or from GNU, and adaptively
1337 change its behaviour; this has proven to be frail and easy to
1340 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1342 Bugs fixed in 1.11.1:
1344 - Lots of minor bugfixes.
1346 * Bugs introduced by 1.11:
1348 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1349 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1351 * Long standing bugs:
1353 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1354 even if the `--prefix' argument pointed outside of a system directory.
1355 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1356 `get_python_lib' function if it points outside the configured prefix,
1357 unless the `--prefix' argument was either `/usr' or below `/System'.
1359 - The testsuite does not try to change the mode of `ltmain.sh' files from
1360 a Libtool installation (symlinked to test directories) any more.
1362 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1363 tools are preferred in a cross-compile setup.
1365 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1366 This fixes a race condition where untrusted users could modify files
1367 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1368 build directory was world-searchable. This is CVE-2009-4029.
1370 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1374 * Version requirements:
1376 - Autoconf 2.62 or greater is required.
1378 * Changes to aclocal:
1380 - The autoconf version check implemented by aclocal in aclocal.m4
1381 (and new in Automake 1.10) is degraded to a warning. This helps
1382 in the common case where the Autoconf versions used are compatible.
1384 * Changes to automake:
1386 - The automake program can run multiple threads for creating most
1387 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1388 with interpreter-based threads enabled. Set the environment variable
1389 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1390 enable this experimental feature.
1392 * Changes to Libtool support:
1394 - Libtool generic flags are now passed to the install and uninstall
1397 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1398 config.lt is removed correctly now.
1400 * Languages changes:
1402 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1403 Fortran, and Ratfor).
1405 - For files with extension .f90, .f95, .f03, or .f08, the flag
1406 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1408 - Files with extension .sx are also treated as preprocessed assembler.
1410 - The default source file extension (.c) can be overridden with
1411 AM_DEFAULT_SOURCE_EXT now.
1413 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1416 - AM_PATH_PYTHON honors python's idea about the site directory.
1418 - There is initial support for the Vala programming language, when using
1419 Vala 0.7.0 or later.
1421 * Miscellaneous changes:
1423 - Automake development is done in a git repository on Savannah now, see
1425 http://git.sv.gnu.org/gitweb/?p=automake.git
1427 A read-only CVS mirror is provided at
1429 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1430 checkout -d automake HEAD
1432 - "make dist" can now create xz-compressed tarballs,
1433 as well as (deprecated?) lzma-compressed tarballs.
1435 - `automake --add-missing' will by default install the GPLv3 file as
1436 COPYING if it is missing. It will also warn that the license file
1437 should be added to source control. Note that Automake will never
1438 overwrite an existing COPYING file, even when the `--force-missing'
1441 - The manual is now distributed under the terms of the GNU FDL 1.3.
1443 - Automake ships and installs man pages for automake and aclocal now.
1445 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1447 - install-sh supports -C, which does not update the installed file
1448 (and its time stamps) if the contents did not change.
1450 - The `gnupload' script has been revamped.
1452 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1454 - The targets `install' and `uninstall' are more efficient now, in that
1455 for example multiple files from one Automake variable such as
1456 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1457 invocation if they do not have to be renamed.
1459 Both install and uninstall may sometimes enter (`cd' into) the target
1460 installation directory now, when no build-local scripts are used.
1462 Both install and uninstall do not fail anymore but do nothing if an
1463 installation directory variable like `bindir' is set to the empty string.
1465 For built-in rules, `make install' now fails reliably if installation
1466 of a file failed. Conversely, `make uninstall' even succeeds when
1467 issued multiple times.
1469 These changes may need some adjustments from users: For example,
1470 some `install' programs refuse to install multiple copies of the
1471 same file in one invocation, so you may need to remove duplicate
1472 entries from file lists.
1474 Also, within one set of files, say, nobase_data_DATA, the order of
1475 installation may be changed, or even unstable among different hosts,
1476 due to the use of associative arrays in awk. The increased use of
1477 awk matches a similar move in Autoconf to provide for better scaling.
1479 Further, most undocumented per-rule install command variables such as
1480 binSCRIPT_INSTALL have been removed because they are not needed any
1481 more. Packages which use them should be using the appropriate one of
1482 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1483 counterpart, depending on the type of files and the need for automatic
1484 target directory creation.
1486 - The "deleted header file problem" for *.m4 files is avoided by
1487 stub rules. This allows `make' to trigger a rerun of `aclocal'
1488 also if some previously needed macro file has been removed.
1490 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1491 an otherwise up to date tree.
1493 - The `color-tests' option causes colored test result output on terminals.
1495 - The `parallel-tests' option enables a new test driver that allows for
1496 parallel test execution, inter-test dependencies, lazy test execution
1497 for unit-testing, re-testing only failed tests, and formatted result output
1498 as RST (reStructuredText) and HTML. Enabling this option may require some
1499 changes to your test suite setup; see the manual for details.
1501 - The `silent-rules' option enables Linux kernel-style silent build output.
1502 This option requires the widely supported but non-POSIX `make' feature
1503 of recursive variable expansion, so do not use it if your package needs
1504 to build with `make' implementations that do not support it.
1506 To enable less verbose build output, the developer has to use the Automake
1507 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1508 macro. The user may then set the default verbosity by passing the
1509 `--enable-silent-rules' option to `configure'. At `make' run time, this
1510 default may be overridden using `make V=0' for less verbose, and `make V=1'
1511 for backward-compatible verbose output.
1513 - New prefix `notrans_' for manpages which should not be transformed
1514 by --program-transform.
1516 - New macro AM_COND_IF for conditional evaluation and conditional
1519 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1520 remove the file in a non-VPATH build. Such setups work with Autoconf
1523 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1524 the default setting.
1526 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1527 useful especially for multi-line values.
1529 - Automake's early configure-time sanity check now diagnoses an
1530 unsafe absolute source directory name and makes configure fail.
1532 - The Automake macros and rules cope better with whitespace in the
1533 current directory name, as long as the relative path to `configure'
1534 does not contain whitespace. To this end, the values of `$(MISSING)'
1535 and `$(install_sh)' may contain suitable quoting, and their expansion
1536 might need `eval'uation if used outside of a makefile. These
1537 undocumented variables may be used in several documented macros such
1538 as $(AUTOCONF) or $(MAKEINFO).
1542 * Long-standing bugs:
1544 - Fix aix dependency tracking for libtool objects.
1546 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1547 unnecessary use of the `compile' script.
1549 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1550 correct `-rpath' argument is used now.
1552 - `config.status --file=Makefile depfiles' now also works with the
1553 extra quoting used internally by Autoconf 2.62 and newer
1554 (it used to work only without the `--file=' bit).
1556 - The `missing' script works better with versioned tool names.
1558 - Semantics for `missing help2man' have been revamped:
1560 Previously, if `help2man' was not present, `missing help2man' would have
1561 the following semantics: if some man page was out of date but present, then
1562 a warning would be printed, but the exit status was 0. If the man page was
1563 not present at all, then `missing' would create a replacement man page
1564 containing an error message, and exit with a status of 2. This does not play
1565 well with `make': the next run will see this particular man page as being up
1566 to date, and will only error out on the next generated man page, if any;
1567 repeat until all pages are done. This was not desirable.
1569 These are the new semantics: if some man page is not present, and help2man
1570 is not either, then `missing' will warn and generate the replacement page
1571 containing the error message, but exit successfully. However, `make dist'
1572 will ensure that no such bogus man pages are packaged into a tarball.
1574 - Targets provided by automake behave better with `make -n', in that they
1575 take care not to create files.
1577 - `config.status Makefile... depfiles' works fine again in the presence of
1578 disabled dependency tracking.
1580 - The default no-op recursive rules for these targets also work with BSD make
1581 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1583 - `make distcheck' works also when both a directory and some file below it
1584 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1586 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1587 `make mostlyclean' any more; only the LaTeX by-products are.
1589 - Renamed objects also work with the `subdir-objects' option and
1590 source file languages which Automake does not know itself.
1592 - `automake' now correctly complains about variable assignments which are
1593 preceded by a comment, extend over multiple lines with backslash-escaped
1594 newlines, and end in a comment sign. Previous versions would silently
1595 and wrongly ignore such assignments completely.
1597 * Bugs introduced by 1.10:
1599 - Fix output of dummy dependency files in presence of post-processed
1600 Makefile.in's again, but also cope with long lines.
1602 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1603 that have been declared as programs in the same Makefile.
1604 This is for consistency with the analogous change to TESTS in 1.10.
1606 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1607 followed by directories containing config headers.
1609 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1613 * Version requirements:
1615 - Autoconf 2.60 or greater is required.
1617 - Perl 5.6 or greater is required.
1619 * Changes to aclocal:
1621 - aclocal now also supports -Wmumble and -Wno-mumble options.
1623 - `dirlist' entries (for the aclocal search path) may use shell
1624 wildcards such as `*', `?', or `[...]'.
1626 - aclocal supports an --install option that will cause system-wide
1627 third-party macros to be installed in the local directory
1628 specified with the first -I flag. This option also uses #serial
1629 lines in M4 files to upgrade local macros.
1631 The new aclocal options --dry-run and --diff help to review changes
1632 before they are installed.
1634 - aclocal now outputs an autoconf version check in aclocal.m4 in
1635 projects using automake.
1637 For a few years, automake and aclocal have been calling autoconf
1638 (or its underlying engine autom4te) to accurately retrieve the
1639 data they need from configure.ac and its siblings. Doing so can
1640 only work if all autotools use the same version of autoconf. For
1641 instance a Makefile.in generated by automake for one version of
1642 autoconf may stop working if configure is regenerated with another
1643 version of autoconf, and vice versa.
1645 This new version check ensures that the whole build system has
1646 been generated using the same autoconf version.
1648 * Support for new Autoconf macros:
1650 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1652 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1653 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1654 in different directories. However, only one instance of such a
1655 library objects directory is supported.
1657 * Change to Libtool support:
1659 - Libtool generic flags (those that go before the --mode=MODE option)
1660 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1662 * Yacc and Lex changes:
1664 - The rebuild rules for distributed Yacc and Lex output will avoid
1665 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1668 - ylwrap is now always used for lex and yacc source files,
1669 regardless of whether there is more than one source per directory.
1671 * Languages changes:
1673 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1674 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1675 tracking, unlike non-preprocessed assembler (*.s).
1677 - subdir-object mode works now with Assembler. Automake assumes
1678 that the compiler understands `-c -o'.
1680 - Preprocessed assembler (*.S) compilation now also honors
1681 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1683 - Improved support for Objective C:
1684 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1685 - A new section of the manual documents the support.
1687 - New support for Unified Parallel C:
1688 - AM_PROG_UPC looks for a UPC compiler.
1689 - A new section of the manual documents the support.
1691 - Per-target flags are now correctly handled in link rules.
1693 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1694 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1695 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1696 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1698 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1699 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1700 is expected to work (and actually works during compilation).
1702 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1703 "in addition to" breaks backward compatibility with older versions.
1704 If your package used both variables, as in
1706 AM_LDFLAGS = common flags
1707 bin_PROGRAMS = a b c
1708 a_LDFLAGS = more flags
1711 and assumed *_LDFLAGS would sum up, you should rewrite it as
1713 AM_LDFLAGS = common flags
1714 bin_PROGRAMS = a b c
1715 a_LDFLAGS = $(AM_LDFLAGS) more flags
1718 This new behavior of *_LDFLAGS is more coherent with other
1719 per-target variables, and the way *_LDFLAGS variables were
1720 considered internally.
1722 * New installation targets:
1724 - New targets mandated by GNU Coding Standards:
1729 By default they will only install Texinfo manuals.
1730 You can customize them with *-local variants:
1736 - The undocumented recursive target `uninstall-info' no longer exists.
1737 (`uninstall' is in charge of removing all possible documentation
1738 flavors, including optional formats such as dvi, ps, or info even
1739 when `no-installinfo' is used.)
1741 * Miscellaneous changes:
1743 - Automake no longer complains if input files for AC_CONFIG_FILES
1744 are specified using shell variables.
1746 - clean, distribution, or rebuild rules are normally disabled for
1747 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1748 AC_CONFIG_LINK specified using shell variables. However, if these
1749 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1750 be able to output rules anyway.
1751 (See the Automake documentation for AC_CONFIG_FILES.)
1753 - $(EXEEXT) is automatically appended to filenames of TESTS
1754 that have been declared as programs in the same Makefile.
1755 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1757 - `-Wportability' has finally been turned on by default for `gnu' and
1758 `gnits' strictness. This means, automake will complain about %-rules
1759 or $(GNU Make functions) unless you switch to `foreign' strictness or
1760 use `-Wno-portability'.
1762 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1763 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1764 $(mkdir_p) variable is still defined (to the same value as
1765 $(MKDIR_P)) but should be considered obsolete. If you are using
1766 $(mkdir_p) in some of your rules, please plan to update them to
1767 $(MKDIR_P) at some point.
1769 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1770 They still work in this release, but may be withdrawn in a future one.
1772 - Inline compilation rules for gcc3-style dependency tracking are
1775 - Automake installs a "Hello World!" example package in $(docdir).
1776 This example is used throughout the new "Autotools Introduction"
1777 chapter of the manual.
1779 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1783 * Makefile.in bloat reduction:
1785 - Inference rules are used to compile sources in subdirectories when
1786 the `subdir-objects' option is used and no per-target flags are
1787 used. This should reduce the size of some projects a lot, because
1788 Automake used to output an explicit rule for each such object in
1791 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1792 object that must be built with explicit rules. It just outputs
1793 the rules required to build the kind of object considered: either
1794 the two .o and .obj rules for usual objects, or the .lo rule for
1797 * Change to Libtool support:
1799 - Libtool tags are used with libtool versions that support them.
1800 (I.e., with Libtool 1.5 or greater.)
1802 - Automake is now able to handle setups where a libtool library is
1803 conditionally installed in different directories, as in
1806 lib_LTLIBRARIES = liba.la
1808 pkglib_LTLIBRARIES = liba.la
1810 liba_la_SOURCES = ...
1812 * Changes to aclocal:
1814 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1815 really evaluated, before it decides to include them in aclocal.m4.
1816 This solves nasty problems with conditional redefinitions of
1817 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1818 *.m4 files to be included in any project using these macros.
1819 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1820 most famous instance of this bug.)
1822 - Do not complain about missing conditionally AC_REQUIREd macros
1823 that are not actually used. In 1.8.x aclocal would correctly
1824 determine which of these macros were really needed (and include
1825 only these in the package); unfortunately it would also require
1826 all of them to be present in order to run. This created
1827 situations were aclocal would not work on a tarball distributing
1828 all the macros it uses. For instance running aclocal on a project
1829 containing only the subset of the Gettext macros in use by the
1830 project did not work, because gettext conditionally requires other
1833 * Portability improvements:
1835 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1836 tar-pax. The new option filename-length-max=99 helps diagnosing
1837 filenames that are too long for tar-v7. (PR/414)
1839 - Variables augmented with `+=' are now automatically flattened (i.e.,
1840 trailing backslashes removed) and then wrapped around 80 columns
1841 (adding trailing backslashes). In previous versions, a long series
1847 would result in a single-line definition of VAR that could possibly
1848 exceed the maximum line length of some make implementations.
1850 Non-augmented variables are still output as they are defined in
1855 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1856 Works the same as the old Fortran 77 implementation; just replace
1857 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1858 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1860 - Support for conditional _LISP.
1862 - Support for conditional -hook and -local rules (PR/428).
1864 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1866 - Automake will not write any Makefile.ins after the first error it
1867 encounters. The previous Makefile.ins (if any) will be left in
1868 place. (Warnings will not prevent output, but remember they can
1869 be turned into errors with -Werror.)
1871 - The restriction that SUBDIRS must contain direct children is gone.
1874 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1875 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1877 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1879 Bugs fixed in 1.8.5:
1881 * Long-standing bugs:
1883 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1884 so that `make distclean' and `make maintainer-clean' can work.
1886 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1888 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1890 - Polish diagnostic when no input file is found.
1892 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1894 Bugs fixed in 1.8.4:
1896 * Long-standing bugs:
1898 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1899 overridden by the user.
1901 - Honor PATH_SEPARATOR in various places of the Automake package, for
1904 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1907 - Fix install-sh so it can install the `mv' binary... using `mv'.
1909 - Fix tru64 dependency tracking for libtool objects.
1911 - Work around Exuberant Ctags when creating a TAGS files in a directory
1912 without files to scan but with subdirectories to include.
1914 * Bugs introduced by 1.8:
1916 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1917 not defined in the same conditions as the _LDADD that uses it.
1919 - Do not warn when JAVAROOT is overridden, this is legitimate.
1921 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1923 Bugs fixed in 1.8.3:
1925 * Long-standing bugs:
1927 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1928 or any of the other *dir variables contain a space.
1930 Please note that Automake does not and cannot support spaces in
1931 filenames that are involved during the build. This change affects
1932 only installation paths, so that `make install' does not bomb out
1933 in packages configured with
1934 ./configure --prefix '/c/Program Files'
1936 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1937 POSIXLY_CORRECT is set.
1939 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1940 since Autoconf 2.54, which defines LIBOBJS itself.
1942 - Fix a potential (but unlikely) race condition in parallel elisp
1943 builds. (Introduced in 1.7.3.)
1945 - Do not assume that users override _DEPENDENCIES in all conditions
1946 where Automake will try to define them.
1948 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1949 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1952 This fix also affects the $(mkdir_p) variable defined since
1953 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1954 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1956 - Secure temporary directory creation in `make distcheck'. (PR/413)
1958 - Do not generate two build rules for `parser.h' when the
1959 parser appears in two different conditionals.
1961 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1962 checking. Usually ./configure will not pick this shell; so this
1963 fix only helps cases where the shell is forced to /bin/sh.
1965 * Bugs introduced by 1.8:
1967 - In some situations (hand-written `m4_include's), aclocal would
1968 call the `File::Spec->rel2abs' method, which was only introduced
1969 in Perl 5.6. This new version reestablish support Perl 5.005.
1971 It is likely that the next major Automake releases will require at
1972 least Perl 5.6. Consider upgrading your development environment
1973 if you are still using the five-year-old Perl 5.005.
1975 - Automake would sometimes fail to define rules for targets listed
1976 in variables defined in multiple conditions. For instance on
1982 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1983 `b.$(OBJEXT): b.c' rule.
1985 * New sections in manual:
1987 - Third-Party Makefiles: how to interface third party Makefiles.
1988 - Upgrading: upgrading packages to newer Automake versions.
1989 - Multiple Outputs: handling tools that produce many outputs.
1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1995 * A (well known) portability bug slipped in the changes made to
1996 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1997 install anything on Tru64.
1999 * Fix install rules for conditionally built python files. (This never
2002 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2006 * Bugs introduced by 1.8:
2008 - Fix Config.pm import error with old Perl versions (at least
2009 5.005_03). One symptom is that aclocal could not find its macro
2012 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
2013 created by `make install' are always world readable, even if the
2014 installer happens to have an overly restrictive umask (e.g. 077).
2015 This was a mistake and has been reverted. There are at least two
2016 reasons why we must not use `-m 0755':
2017 - it causes special bits like SGID to be ignored,
2018 - it may be too restrictive (some setups expect 775 directories).
2020 - Fix aclocal to honor definitions located in files which have been
2021 m4_included manually. aclocal 1.8 had been updated to check
2022 m4_included files for new requirements, but forgot that these
2023 m4_included files can also provide new definitions.
2025 Note that if you have such a setup, we recommend you get rid of
2026 it. In the past, there was a reason to m4_include files manually:
2027 aclocal used to duplicate entire M4 files into aclocal.m4, even
2028 files that were distributed. Some packages were therefore
2029 m4_including the distributed file directly, and playing some
2030 tricks to ensure aclocal would not copy that file to aclocal.m4,
2031 in order to limit the amount of duplication. Since aclocal 1.8.x
2032 will precisely output m4_includes for local M4 files, we recommend
2033 that you clean up your setup, removing all manual m4_includes and
2034 letting aclocal output them.
2036 - Output detailed menus in the Info version if the Automake manual,
2037 so that Emacs can locate the indexes.
2039 - configure.ac and configure were listed twice in DIST_COMMON (an
2040 internal variable where Automake lists configury files to
2041 distribute). This was harmless, but unaesthetic.
2043 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
2044 This was an issue only in the Automake package itself, not in
2047 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
2048 DEST:SRC. This was wrong, as some packages do
2049 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
2052 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
2053 argument. This caused two kinds of failures:
2054 - Rules installing data in a conditionally defined directory
2055 failed when that directory was undefined. In this case no
2056 argument was supplied.
2057 - `make installdirs' failed, because several directories were
2058 passed to $(mkdir_p). This was an issue only on platform
2059 were $(mkdir_p) is implemented with `install-sh -d'.
2060 $(mkdir_p) as been changed to accept 0 or more arguments, as
2063 * Long-standing bugs:
2065 - Fix an unexpected diagnostic occurring when users attempt
2066 to override some internal variables that Automake appends to.
2068 - aclocal now scans configure.ac for macro definitions (PR/319).
2070 - Fix a portability issue with OSF1/Tru64 Make. If a directory
2071 distributes files which are outside itself (this usually occurs
2072 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
2073 from a parent package), then `make distcheck' fails due to an
2074 optimization performed by OSF1/Tru64 Make in its VPATH handling.
2075 (tests/subpkg2.test failure)
2077 - Fix another portability issue with Sun and OSF1/Tru64 Make.
2078 In a VPATH-build configuration, `make install' would install
2079 nobase_ files to wrong locations.
2081 - Fix a Perl `uninitialized value' diagnostic occurring when
2082 automake complains that a Texinfo file does not have a
2083 @setfilename statement.
2085 - Erase config.status.lineno during `make distclean'. This file
2086 can be created by config.status. Automake already knew about
2087 configure.lineno, but forgot config.status.lineno.
2089 - Distribute all files, even those which are built and installed
2090 conditionally. This change affects files listed in conditionally
2091 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
2092 as well as those listed in conditionally defined dist_*_DATA,
2093 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
2095 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
2096 doesn't conform to POSIX.
2098 - Normalize help strings for configure variables and options added
2103 - Check for python2.4 in AM_PATH_PYTHON.
2105 * Spurious failures in test suite:
2107 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
2108 tests/ltconv.test: fix failures with CVS Libtool.
2109 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
2110 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
2111 fix failures with old Texinfo versions.
2113 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2119 - The NEWS file is more verbose.
2123 - Autoconf 2.58 or greater is required.
2127 - Default source file names in the absence of a _SOURCES declaration
2128 are made by removing any target extension before appending `.c', so
2129 to make the libtool module `foo.la' from `foo.c', you only need to
2132 lib_LTLIBRARIES = foo.la
2133 foo_la_LDFLAGS = -module
2135 For backward compatibility, foo_la.c will be used instead of
2136 foo.c if this file exists or is the explicit target of a rule.
2137 However -Wobsolete will warn about this deprecated naming.
2139 - AR's `cru' flags are now set in a global ARFLAGS variable instead
2140 of being hard-coded in each $(AR) invocation, so they can be
2141 substituted from configure.ac. This has been requested by people
2142 dealing with non-POSIX ar implementations.
2144 - New warning option: -Woverride. This will warn about any user
2145 target or variable definitions which override Automake
2148 - Texinfo rules back up and restore info files when makeinfo fails.
2150 - Texinfo rules now support the `html' target.
2151 Running this requires Texinfo 4.0 or greater.
2153 `html' is a new recursive target, so if your package mixes
2154 hand-crafted `Makefile.in's with Automake-generated
2155 `Makefile.in's, you should adjust the former to support (or
2156 ignore) this target so that `make html' recurses successfully. If
2157 you had a custom `html' rule in your `Makefile.am', it's better to
2158 rename it as `html-local', otherwise your rule will override
2159 Automake's new rule (you can check that by running `automake
2160 -Woverride') and that will stop the recursion to subdirectories.
2162 Last but not least, this `html' rule is declared PHONY, even when
2163 overridden. Fortunately, it appears that few packages use a
2164 non-PHONY `html' rule.
2166 - Any file which is m4_included from configure.ac will appear as a
2167 configure and Makefile.in dependency, and will be automatically
2170 - The rules for rebuilding Makefiles and Makefile.ins will now
2171 rebuild all Makefiles and all Makefile.ins at once when one of
2172 configure's dependencies has changed. This is considerably faster
2173 than previous implementations, where config.status and automake
2174 were run separately in each directory (this still happens when you
2175 change a Makefile.am locally, without touching configure.ac or
2176 friends). Doing this also solves a longstanding issue: these
2177 rebuild rules failed to work when adding new directories to the
2178 tree, forcing you to run automake manually.
2180 - For similar reasons, the rules to rebuild configure,
2181 config.status, and aclocal.m4 are now defined in all directories.
2182 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
2183 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
2184 should better define them in all directories. This is easily done
2185 using an AC_SUBST (make sure you prefix these dependencies with
2186 $(top_srcdir) since this variable will appear at different
2187 levels of the build tree).
2189 - aclocal will now use `m4_include' instead of copying local m4
2190 files into aclocal.m4. (Local m4 files are those you ship with
2191 your project, other files will be copied as usual.)
2193 Because m4_included files are automatically distributed, it means
2194 for most projects there is no point in EXTRA_DISTing the list of
2195 m4 files which are used. (You can probably get rid of
2196 m4/Makefile.am if you had one.)
2198 - aclocal will avoid touching aclocal.m4 when possible, so that
2199 Autom4te's cache isn't needlessly invalidated. This behavior can
2200 be switched off with the new `--force' option.
2202 - aclocal now uses Autoconf's --trace to detect macros which are
2203 actually used and will no longer include unused macros simply
2204 because they where mentioned. This was often the case for macros
2205 called conditionally.
2207 - New options no-dist and no-dist-gzip.
2209 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2210 py-compile, and ylwrap, now all understand --version and --help.
2212 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2213 links as part of the distclean target and including source files in
2216 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2217 argument. The latter can be used to override the default behavior
2218 (which is to abort).
2220 - Automake will exit with $? = 63 on version mismatch. (So does
2221 Autoconf 2.58) missing knows this, and in this case it will
2222 emulate the tools as if they were absent. Because older versions
2223 of Automake and Autoconf did not use this exit code, this change
2224 will only be useful in projects generated with future versions of
2227 - When using AC_CONFIG_FILES with multiple input files, Automake
2228 generates the first ".in" input file for which a ".am" exists.
2229 (Former versions would try to use only the first input file.)
2231 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2232 idiom to disable byte-compilation of lisp_LISP files, it is
2233 recommended that you switch to using lisp_DATA. Note that
2234 this is not strictly equivalent: lisp_DATA will install elisp
2235 files even if emacs is not installed, while *_LISP do not
2236 install anything unless emacs is found.
2238 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2239 available. This selection is achieved through the Makefile
2240 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2241 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2242 `$(install_sh) -m 0755 -d'.
2246 - Because `mkdir -p' is available on most platforms, and we can use
2247 `install-sh -d' when it is not, the use of the mkinstalldirs
2248 script is being phased out. `automake --add-missing' no longer
2249 installs it, and if you remove mkinstalldirs from your package,
2250 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2252 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2253 gettextize and autopoint will install it when needed. Automake
2254 will continue to define the $(mkinstalldirs) and to distribute
2255 mkinstalldirs when this script is in the source tree.
2257 - AM_PROG_CC_STDC is now empty. The content of this macro was
2258 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2259 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2260 renaming should be safe, even if you have to support several,
2261 versions of Automake, because AC_PROG_CC defines this variable
2262 since Autoconf 2.54.)
2264 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2265 variable to override the aclocal.m4 dependencies computed
2266 (inaccurately) by older versions of Automake. Because Automake
2267 now tracks configure's m4 dependencies accurately (see m4_include
2268 above), the use of ACLOCAL_M4_SOURCES should be considered
2269 obsolete and will be flagged as such when running `automake
2274 - Defining programs conditionally using Automake conditionals no
2275 longer leads to a combinatorial explosion. The following
2276 construct used to be troublesome when used with dozens of
2291 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2293 - Due to implementation constraints, previous versions of Automake
2294 proscribed multiple conditional definitions of some variables
2304 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2305 This restriction has been lifted, and these variables now
2306 support multiple conditional definitions as do other variables.
2308 - Cleanup the definitions of $(distdir) and $(top_distdir).
2309 $(top_distdir) now points to the root of the distribution
2310 directory created during `make dist', as it did in Automake 1.4,
2311 not to the root of the build tree as it did in intervening
2312 versions. Furthermore these two variables are now only defined in
2313 the top level Makefile, and passed to sub-directories when running
2316 - The --no-force option now correctly checks the Makefile.in's
2317 dependencies before deciding not to update it.
2319 - Do not assume that make files are called Makefile in cleaning rules.
2321 - Update .info files in the source tree, not in the build tree. This
2322 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2323 used to update these files in the build tree (previous versions did
2324 it in the source tree too), and it caused several problems, varying
2325 from mere annoyance to portability issues.
2327 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2328 when --add-missing and --force-missing are used. For backward
2329 compatibility --add-missing will continue to install COPYING (in
2330 `gnu' strictness) when none of these three files exist, but this
2331 use is deprecated: you should better choose a license yourself and
2332 install it once for all in your source tree (and in your code
2335 - Fix ylwrap so that it does not overwrite header files that haven't
2336 changed, as the inline rule already does.
2338 - User-defined rules override automake-defined rules for the same
2339 targets, even when rules do not have commands. This is not new
2340 (and was documented), however some of the automake-generated
2341 rules have escaped this principle in former Automake versions.
2342 Rules for the following targets are affected by this fix:
2344 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2345 info, info-am, install-data-am, install-exec-am, install-info,
2346 install-info-am, install-man, installcheck-am, maintainer-clean,
2347 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2348 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2350 Practically it means that an attempt to supplement the dependencies
2351 of some target, as in
2353 clean: my-clean-rule
2355 will now *silently override* the automake definition of the
2356 rule for this target. Running `automake -Woverride' will diagnose
2357 all such overriding definitions.
2359 It should be noted that almost all of these targets support a *-local
2360 variant that is meant to supplement the automake-defined rule
2361 (See node `Extending' in the manual). The above rule should
2364 clean-local: my-clean-rule
2366 These *-local targets have been documented since at least
2367 Automake 1.2, so you should not fear the change if you have
2368 to support multiple automake versions.
2372 - The Automake manual is now distributed under the terms of the GNU FDL.
2374 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2376 - core dumps are no longer removed by the cleaning rules. There are
2377 at least three reasons for this:
2378 1. These files should not be created by any build step,
2379 so their removal do not fit any of the cleaning rules.
2380 Actually, they may be precious to the developer.
2381 2. If such file is created during a build, then it's clearly a
2382 bug Automake should not hide. Not removing the file will
2383 cause `make distcheck' to complain about its presence.
2384 3. Operating systems have different naming conventions for
2385 core dump files. A core file on one system might be a
2386 completely legitimate data file on another system.
2388 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2389 defined by Automake. This means that any definition in the
2390 environment will be used, unless overridden in the Makefile.am or
2391 on the command line. The old behavior, where these variables were
2392 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2393 AC_ARG_VARing each variable from configure.ac.
2395 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2396 documented. (The is not a new feature, these variables have
2397 been there since at least Automake 1.4.)
2399 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2401 Bugs fixed in 1.7.9:
2402 * Fix install-strip to work with nobase_ binaries.
2403 * Fix renaming of #line directives in ylwrap.
2404 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2406 Bugs fixed in 1.7.8:
2407 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2408 * Fix detection of Debian's install-info, broken since version 1.5.
2409 (Debian bug #213524).
2410 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2411 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2413 Bugs fixed in 1.7.7:
2414 * The implementation of automake's --no-force option is unreliable,
2415 so this option is ignored in this version. A real fix will appear in
2416 Automake 1.8. (Debian Bug #206299)
2417 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2418 argument is given. (PR/399)
2419 * Do not warn about leading `_' in variable names, even with -Wportability.
2420 * Support user redefinitions of TEXINFO_TEX.
2421 * depcomp: support AIX Compiler version 6.
2422 * Fix missing rebuilds during `make dist' with BSD make.
2423 (Could produce tarballs containing out-of-date files.)
2424 * Resurrect multilib support.
2425 * Noteworthy manual updates:
2426 - Extending aclocal: how to write m4 macros that won't trigger warnings
2428 - A Shared Library: Rewrite and split into subsections.
2430 Bugs fixed in 1.7.6:
2431 * Fix depcomp's icc mode for ICC 7.1.
2432 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2433 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2434 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2435 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2436 * Remove Latin-1 characters from elisp-comp.
2437 * Update the manual's @dircategory to match the Free Software Directory.
2439 Bugs fixed in 1.7.5:
2440 * Update install-sh's license to remove an advertising clause.
2441 (Debian bug #191717)
2442 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2443 that caused invalid Makefile.ins to be generated.
2444 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2445 * New FAQ entry: renamed objects.
2447 Bugs fixed in 1.7.4:
2448 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2449 the Emacs implementation)
2450 * Fix output of aclocal.m4 dependencies in subdirectories.
2451 * Use `mv -f' instead of `mv' in fastdep rules.
2452 * Upgrade mdate-sh to work on OS/2.
2453 * Don't byte-compile elisp files when ELCFILES is set empty.
2454 (this documented feature was broken by 1.7.3)
2455 * Diagnose trailing backslashes on last line of Makefile.am.
2456 * Diagnose whitespace following trailing backslashes.
2457 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2458 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2460 * `make install' will build `BUILT_SOURCES' first.
2461 * Minor documentation fixes.
2463 Bugs fixed in 1.7.3:
2464 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2465 * Query distutils for `pythondir' and `pythonexecdir', instead of
2466 using an hardcoded path. This should allow builds on 64-bit
2467 distributions that usually use lib64/ instead of lib/.
2468 * AM_PATH_PYTHON will also search for python2.3.
2469 * elisp files are now built all at once instead of one by one. Besides
2470 incurring a speed-up, this is required to support interdependent elisp files.
2471 * Support for DJGPP:
2472 - `make distcheck' will now work in `_inst/' and `_build' instead
2473 of `=inst/' and `=build/'
2474 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2475 - install/uninstall `*.i[0-9][0-9]'-style info files
2476 - more changes that affect only the Automake package (not its output)
2477 * Fix some incompatibilities with upcoming perl-5.10.
2478 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2479 PACKAGE and VERSION.
2481 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2482 is troublesome with gcc and Solaris compilers. (PR/385)
2483 - makedepend mode: work with Libtool. (PR/385 too)
2485 * better support for unusual gettext setups, such as multiple po/ directories
2487 - Flag missing po/ and intl/ directories as warnings, not errors.
2488 - Disable these warnings if po/ does not exist.
2489 * Noteworthy manual updates:
2491 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2493 - Document `AM_YFLAGS = -d'. (PR/382)
2495 Bugs fixed in 1.7.2:
2496 * Fix installation and uninstallation of Info files built in subdirectories.
2497 * Do not run `./configure --with-included-gettext' during `make distcheck'
2498 if AM_GNU_GETTEXT([external]) is used.
2499 * Correctly uninstall renamed man pages.
2500 * Do not strip escaped newline in variables defined in one condition
2501 and augmented in another condition.
2502 * Fix ansi2knr rules for LIBOBJS sources.
2503 * Clean all known Texinfo index files, not only those which appear to
2504 be used, because we cannot know which indexes are used in included files.
2505 (PR/375, Debian Bug #168671)
2506 * Honor only the first @setfilename seen in a Texinfo file.
2507 * Treat "required file X not found" diagnostics as errors (exit status 1).
2508 * Don't complain that a required file is not found when it is a Makefile
2510 * Don't use single suffix inference rules when building `.info'-less
2511 Info files, for the sake of Solaris make.
2512 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2513 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2514 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2515 * Fix building of deansified files from subdirectories. (PR/370)
2516 * Add missing `fi' in the .c->.obj rules.
2517 * Improve install-sh to work even when names contain spaces or certain
2518 (but not all) shell metachars.
2519 * Fix the following spurious failures in the test suite:
2520 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2521 * Noteworthy manual updates:
2522 - Augment the section about BUILT_SOURCES.
2523 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2525 Bugs fixed in 1.7.1:
2526 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2528 * Aclocal should now recognize macro names containing parentheses, e.g.
2529 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2530 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2532 * Install Python files even if they were built. (PR/369)
2533 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2534 version might not be defined in the latter. (PR/358)
2535 * Reorder arguments passed to a couple of commands, so things works
2536 when POSIXLY_CORRECT=1.
2537 * Fix a regex that can cause Perl to segfault on large input.
2539 * Fix distribution of packages that have some sources defined conditionally,
2540 as in the `Conditional compilation using Automake conditionals' example
2542 * Fix spurious test suite failures on IRIX.
2543 * Don't report a required variable as undefined if it has been
2544 defined conditionally for the "right" conditions.
2545 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2546 `make distcheck' fails.
2547 * Fix distribution of included Makefile fragment, so we don't create
2548 spurious directories in the distribution. (PR/366)
2549 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2552 * Autoconf 2.54 is required.
2553 * `aclocal' and `automake' will no longer warn about obsolete
2554 configure macros. This is done by `autoconf -Wobsolete'.
2555 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2556 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2557 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2558 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2559 `configure.ac' for you.
2560 * Support for per-program and per-library `_CPPFLAGS'.
2561 * New `ctags' target (builds CTAGS files).
2562 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2563 (see `automake --help' or the manual for a list of them).
2564 * Honor the WARNINGS environment variable.
2565 * Omit the call to depcomp when using gcc3: call the compiler directly.
2566 * A new option, std-options, tests that programs support --help and --version
2567 when `make installcheck' is run. This is enabled by --gnits.
2568 * Texinfo rules now support the `ps' and `pdf' targets.
2569 * Info files are now created in the build directory, not the source directory.
2570 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2572 * `make distcheck' will enforce DESTDIR support by attempting
2574 * `+=' can be used in conditionals, even if the augmented variable
2575 was defined for another condition.
2576 * Makefile fragments (inserted with `include') are always distributed.
2577 * Use Autoconf's --trace interface to inspect configure.ac and get
2578 a more accurate view of it.
2579 * Add support for extending aclocal's default macro search path
2580 using a `dirlist' file within the aclocal directory.
2581 * automake --output-dir is deprecated.
2582 * The part of the distcheck target that checks whether uninstall actually
2583 removes all installed files has been moved in a separate target,
2584 distuninstallcheck, so it can be overridden easily.
2588 * Support for AM_INIT_GETTEXT([external])
2589 * Bug fixes, including:
2590 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2591 - nobase_ programs and scripts honor --program-transform correctly.
2592 - Erase configure.lineno during `make distclean'.
2593 - Erase YACC and LEX outputs during `make maintainer-clean'.
2596 * Many bug fixes, including:
2597 - Requiring the current version works.
2598 - Fix "$@" portability issues (for Zsh).
2599 - Fix output of dummy dependency files in presence of post-processed
2601 - Don't compute dependencies in background to avoid races with libtool.
2602 - Fix handling of _OBJECTS variables for targets sharing source variables.
2603 - Check dependency mode for Java when AM_PROG_GCJ is used.
2606 * automake --output-dir is deprecated
2607 * Many bug fixes, including:
2608 - Don't choke on AM_LDFLAGS definitions.
2609 - Clean libtool objects from subdirectories.
2610 - Allow configure variables with reserved suffix and unknown prefix
2611 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2612 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2615 * Autoconf 2.52 is required.
2616 * automake no longer run libtoolize.
2617 This is the job of autoreconf (from GNU Autoconf).
2618 * `dist' generates all the archive flavors, as did `dist-all'.
2619 * `dist-gzip' generates the Gzip tar file only.
2620 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2621 explosion. Makefile.in's keep a reasonable size.
2622 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2623 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2625 * `#line' of Lex and Yacc files are properly set.
2626 * EXTRA_DIST can contain generated directories.
2627 * Support for dot-less extensions in suffix rules.
2628 * The part of the distcheck target that checks whether distclean actually
2629 cleans all built files has been moved in a separate target, distcleancheck,
2630 so it can be overridden easily.
2631 * `make distcheck' will pass additional options defined in
2632 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2633 * Fixed CDPATH portability problems, in particular for MacOS X.
2634 * Fixed handling of nobase_ targets.
2635 * Fixed support of implicit rules leading to .lo objects.
2636 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2637 * Added uninstall-hook target
2638 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2639 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2640 (Note that "pkgname" is not "tarname", see the manual for details.)
2641 It is also possible to pass a list of global Automake options as
2642 first argument to this new form of AM_INIT_AUTOMAKE.
2643 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2644 to be a real assembler.
2645 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2646 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2647 * aclocal and automake are also installed with the version number
2648 appended, and some of the install directory names have changed.
2649 This lets you have multiple versions installed simultaneously.
2650 * Support for parsers and lexers in subdirectories.
2653 * Support for `configure.ac'.
2654 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2655 * `make dist-all' is much faster.
2656 * Allows '@' AC_SUBSTs in macro names.
2657 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2658 * User-side dependency tracking. Developers no longer need GNU make
2660 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2661 * Most files are correctly handled if they appear in subdirs
2662 For instance, a _DATA file can appear in a subdir
2663 * GNU tar is no longer required for `make dist'
2664 * Added support for `dist_' and `nodist_' prefixes
2665 * Added support for `nobase_' prefix
2666 * Compiled Java support
2667 * Support for per-executable and per-library compilation flags
2671 * Added support for the Fortran 77 programming language.
2672 * Re-indexed the Automake Texinfo manual.
2673 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2674 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2675 * Support for latest autoconf, including support for objext
2676 * Can now put `.' in SUBDIRS to control build order
2677 * `include' command and `+=' support for macro assignment
2678 * Dependency tracking no long susceptible to deleted header file problem
2679 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2684 * Better Cygwin32 support
2685 * Support for suffix rules with _SOURCES variables
2686 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2687 * @LEXLIB@ no longer required when lex source seen
2688 Lex support in `missing', and new lex macro. Update your missing script.
2689 * Built-in support for assembly
2690 * aclocal gives error if `AM_' macro not found
2691 * Passed YFLAGS, not YACCFLAGS, to yacc
2692 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2693 * Dependencies computed as a side effect of compilation
2694 * Preliminary support for Java
2695 * DESTDIR support at "make install" time
2696 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2700 * Better DejaGnu support
2701 * Added no-installinfo option
2702 * Added Emacs Lisp support
2703 * Added --no-force option
2704 * Included `aclocal' program
2705 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2706 * Now uses `AM_' macro names everywhere
2707 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2708 ansi2knr now works correctly on K&R sources
2709 * Better C++, yacc, lex support
2710 * Will compute _DEPENDENCIES variables automatically if not supplied
2711 * Will interpolate $(...) and ${...} when examining contents of a variable
2712 * .deps files now in build directory, not source directory; dependency
2713 handling generally rewritten
2714 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2715 * can now put config.h into a subdir
2716 * Added dist-all target
2717 * Support for install-info program (see texinfo 3.9)
2718 * Support for "yacc -d"
2719 * configure substitutions are automatically discovered and included
2720 in generated Makefile.in
2721 * Special --cygnus mode
2722 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2723 when making distribution. Some dependencies are auto-ignored.
2724 * Changed how libraries are specified in _LIBRARIES variable
2725 * Full libtool support, from Gord Matzigkeit
2726 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2727 AM_CONFIG_HEADER handles it automatically
2728 * Texinfo output files no longer need .info extension
2729 * Added `missing' support
2731 * Conditionals in Makefile.am, from Ian Taylor
2735 * distcheck target runs install and installcheck targets
2736 * Added preliminary support for DejaGnu.
2741 * More libtool fixes from Gord Matzigkeit; libtool support is still
2743 * Added support for jm_MAINTAINER_MODE
2745 * New "distcheck" target
2749 * mkinstalldirs and mdate-sh now appear in directory specified by
2751 * Removed DIST_SUBDIRS, DIST_OTHER
2752 * AC_ARG_PROGRAM only required when an actual program exists
2753 * dist-hook target now run before distribution packaged up; idea from
2754 Dieter Baron. Other hooks exist, too.
2755 * Preliminary (unfinished) support for libtool
2756 * Added short option names.
2757 * Better "dist" support when gluing together multiple packages
2761 * Documentation updates (many from François Pinard)
2762 * strictness `normal' now renamed to `foreign'
2763 * Renamed --install-missing to --add-missing
2764 * Now handles AC_CONFIG_AUX_DIR
2765 * Now handles TESTS macro
2766 * DIST_OTHER renamed to EXTRA_DIST
2767 * DIST_SUBDIRS is deprecated
2768 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2769 * Better error messages in many cases
2770 * Program names are canonicalized
2771 * Added "check" prefix; from Gord Matzigkeit
2775 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2776 * Beginnings of a test suite
2777 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2778 * Doesn't print anything when running
2779 * Beginnings of MAINT_CHARSET support
2780 * Can specify version in AUTOMAKE_OPTIONS
2781 * Most errors recognizable by Emacs' M-x next-error
2782 * Added --verbose option
2783 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2784 configure-generated names
2785 * Required macros now distributed in aclocal.m4
2787 * --strictness=gnu is default
2791 * More sophisticated configure.in scanning; now understands ALLOCA and
2792 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2793 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2794 * CONFIG_HEADER variable now obsolete
2795 * Can handle multiple Texinfo sources
2796 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2797 * HEADERS variable no longer needed; now can put .h files directly into
2798 foo_SOURCES variable.
2799 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2800 corresponding ".in" files are included in the distribution.
2803 * Added --gnu and --gnits options
2804 * More standards checking
2806 * Cleaned up 'dist' targets
2807 * Added AUTOMAKE_OPTIONS variable and several options
2808 * Now scans configure.in to get some information (preliminary)
2811 * Works with Perl 4 again
2814 * Added --install-missing option.
2815 * Pretty-prints generated macros and rules
2816 * Comments in Makefile.am are placed more intelligently in Makefile.in
2817 * Generates .PHONY target
2818 * Rule or macro in Makefile.am now overrides contents of Automake file
2819 * Substantial cleanups from François Pinard
2823 * Works with Perl 4 again.
2826 * New uniform naming scheme.
2827 * --strictness option
2829 * '.c' files corresponding to '.y' or '.l' files are automatically
2831 * Many bug fixes and cleanups
2834 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2837 * Bug fixes in 'clean' code.
2838 * Now generates 'installdirs' target.
2839 * man page installation reworked.
2840 * 'make dist' no longer re-creates all Makefile.in's.
2843 * Reimplemented in Perl
2844 * Added --amdir option (for debugging)
2845 * Texinfo support cleaned up.
2846 * Automatic de-ANSI-fication cleaned up.
2847 * Cleaned up 'clean' targets.
2850 * Automatic dependency tracking
2851 * More documentation
2852 * New variables DATA and PACKAGEDATA
2853 * SCRIPTS installed using $(INSTALL_SCRIPT)
2854 * No longer uses double-colon rules
2856 * Changes in advance of internationalization
2860 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2862 This program is free software; you can redistribute it and/or modify
2863 it under the terms of the GNU General Public License as published by
2864 the Free Software Foundation; either version 2, or (at your option)
2867 This program is distributed in the hope that it will be useful,
2868 but WITHOUT ANY WARRANTY; without even the implied warranty of
2869 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2870 GNU General Public License for more details.
2872 You should have received a copy of the GNU General Public License
2873 along with this program. If not, see <http://www.gnu.org/licenses/>.