1 * WARNING: New versioning scheme for Automake.
3 - Starting with this version onward, Automake will use an update and
4 more rational versioning scheme, one that will allow users to know
5 which kind of changes can be expected from a new version, based on
8 + Micro versions (e.g., 1.13.3, 2.0.1, 3.2.8) will introduce only
9 documentation updates and bug and regression fixes; they will
10 not 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 versions (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 developers as "corner case features". Possible disruptions
20 caused by this kind of fixes should hopefully be quite rare.
22 + Major versions (now expected to be released every 18 or 24 months,
23 and not more often) can introduce new big features (possibly with
24 rough edges and not-fully-stabilized APIs), removal of deprecated
25 features, backward-incompatible changes of behaviour, and possibly
26 major refactorings (that, while ideally transparent to the user,
27 could introduce new bugs). Incompatibilities should however not
28 be introduced gratuitously and abruptly; a proper deprecation path
29 should be duly implemented in the preceding minor releases.
31 - According to this new scheme, the next major version of Automake
32 (the one that has until now been labelled as '1.14') will actually
33 become "Automake 2.0". Automake 1.14 will be the next minor version,
34 which will introduce new features, deprecations and bug fixes, but
35 no serious backward incompatibility.
37 - See discussion about automake bug#13578 for more details and
38 background: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578>
40 * WARNING: Future backward-incompatibilities!
42 - Makefile recipes generated by Automake 2.0 will expect to use an
43 'rm' program that doesn't complain when called without any non-option
44 argument if the '-f' option is given (so that commands like "rm -f"
45 and "rm -rf" will act as a no-op, instead of raising usage errors).
46 Accordingly, AM_INIT_AUTOMAKE will expand new shell code checking
47 that the default 'rm' program in PATH satisfies this requirement, and
48 aborting the configure process if this is not the case. This behavior
49 of 'rm' is very widespread in the wild, and it will be required in the
51 <http://austingroupbugs.net/view.php?id=542>
53 - Automake 2.0 will require Autoconf 2.70 or later (which is still
54 unreleased at the moment of writing, but is planned to be released
55 before Automake 2.0 is).
57 - Automake 2.0 will drop support for the long-deprecated 'configure.in'
58 name for the Autoconf input file. You are advised to start using the
59 recommended name 'configure.ac' instead, ASAP.
61 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated
62 in Automake 2.0 (where it will raise warnings in the "obsolete"
63 category). You are advised to start relying on the new Automake
64 support for AC_CONFIG_MACRO_DIRS instead (which was introduced in
67 - Automake 2.0 will remove support for automatic dependency tracking
68 with the SGI C/C++ compilers on IRIX. The SGI depmode has been
69 reported broken "in the wild" already, and we don't think investing
70 time in debugging and fixing is worthwhile, especially considering
71 that SGI has last updated those compilers in 2006, and is expected
72 to retire support for them in December 2013:
73 <http://www.sgi.com/services/support/irix_mips_support.html>
75 - Automake 2.0 will remove support for MS-DOS and Windows 95/98/ME
76 (support for them was offered by relying on the DJGPP project).
77 Note however that both Cygwin and MSYS/MinGW on modern Windows
78 versions will continue to be fully supported.
80 - Automake-provided scripts and makefile recipes might (finally!)
81 start assuming a POSIX shell in Automake 2.0.
83 - Starting from Automake 2.0, third-party m4 files located in the
84 system-wide aclocal directory, as well as in any directory listed
85 in the ACLOCAL_PATH environment variable, will take precedence
86 over "built-in" Automake macros. For example (assuming Automake
87 is installed in the /usr/local hierarchy), a definition of the
88 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
89 should take precedence over the same-named automake-provided macro
90 (defined in '/usr/local/share/aclocal-2.0/vala.m4').
92 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
96 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
98 - The 'compile' script is now unconditionally required for all
99 packages that perform C compilation (note that if you are using
100 the '--add-missing' option, automake will fetch that script for
101 you, so you shouldn't need any explicit adjustment).
102 This new behaviour is needed to avoid obscure errors when the
103 'subdir-objects' option is used, and the compiler is an inferior
104 one that doesn't grasp the combined use of both the "-c -o"
105 options; see discussion about automake bug#13378 for more details:
106 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
107 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
109 - The next major Automake version (2.0) will unconditionally turn on
110 the 'subdir-objects' option. In order to smooth out the transition,
111 we now give a warning (in the category 'unsupported') whenever a
112 source file is present in a subdirectory but the 'subdir-object' is
113 not enabled. For example, the following usage will trigger such a
114 warning (of course, assuming the 'subdir-objects' option is off):
116 bin_PROGRAMS = sub/foo
117 sub_foo_SOURCES = sub/main.c sub/bar.c
119 - Automake will automatically enhance the AC_PROG_CC autoconf macro
120 to make it check, at configure time, that the C compiler supports
121 the combined use of both the "-c -o" options. The result of this
122 check is saved in the cache variable 'am_cv_prog_cc_c_o', and said
123 result can be overridden by pre-defining that variable.
125 - The AM_PROG_CC_C_O can still be called, but that should no longer
126 be necessary. This macro is now just a thin wrapper around the
127 Automake-enhanced AC_PROG_CC. This means, among the other things,
128 that its behaviour is changed in three ways:
130 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
131 macros behind the scenes.
133 2. It caches the check result in the 'am_cv_prog_cc_c_o'variable,
134 and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name
135 in only dynamically computed at configure runtime (sic!) from
136 the content of the '$CC' variable.
138 3. It no longer automatically AC_DEFINE the C preprocessor
139 symbol 'NO_MINUS_C_MINUS_O'.
143 - Automake can now be instructed to place '.info' files generated from
144 Texinfo input in the builddir rather than in the srcdir; this is done
145 specifying the new automake option 'info-in-builddir'. This feature
146 was requested by the developers of GCC, GDB, GNU binutils and the GNU
147 bfd library. See the extensive discussion about automake bug#11034
150 - For quite a long time, Automake has been implementing an undocumented
151 hack which ensured that '.info' files which appeared to be cleaned
152 (by e.g. being listed in the CLEANFILES or DISTCLEANFILES variables)
153 were built in the builddir rather than in the srcdir; this hack was
154 introduced to ensure better backward-compatibility with packages such
155 as Texinfo, which did things like:
157 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
158 DISTCLEANFILES = texinfo texinfo-* info*.info*
159 # Do not create info files for distribution.
163 in order not to distribute generated '.info' files.
165 Now that we have the 'info-in-builddir' option that explicitly causes
166 generated '.info' files to be placed in the builddir, this hack should
167 be longer necessary, so we deprecate it with runtime warnings. It will
168 likely be removed altogether in Automake 2.0.
170 * Relative directory in Makefile fragments:
172 - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
173 (and their short versions, '%D%' and '%C%' respectively) can now be used
174 in an included Makefile fragment. The former is substituted with the
175 relative directory of the included fragment (compared to the top level
176 including Makefile), and the latter with the canonicalized version of
177 the same relative directory:
179 bin_PROGRAMS += %reldir%/foo
180 %canon_reldir%_foo_SOURCES = %reldir%/bar.c
182 * Deprecated distribution formats:
184 - The 'shar' and 'compress' distribution formats are deprecated, and
185 scheduled for removal in Automake 2.0. Accordingly, the use of the
186 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
187 (in the 'obsolete' category), and the recipes for the Automake-generated
188 targets 'dist-shar' and 'dist-tarZ' will unconditionally display
189 (non-fatal) warnings at make runtime.
191 * New configure runtime warnings about "rm -f" support:
193 - To simplify transition to Automake 2.0, the shell code expanded by
194 AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
195 'rm' program in PATH doesn't complain when called without any
196 non-option argument if the '-f' option is given (so that commands
197 like "rm -f" and "rm -rf" act as a no-op, instead of raising usage
198 error). If this is not the case,
199 the configure script is aborted, to call the attention of the user
200 on the issue, and invite him to fix his PATH. The checked 'rm'
201 behavior is very widespread in the wild, and will be required by
202 future POSIX version:
204 <http://austingroupbugs.net/view.php?id=542>
206 The user can still force the configure process to complete even in the
207 presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
208 environment variable to "yes". And the generated Makefiles should
209 still work correctly even when such broken 'rm' is used. But note
210 that this will no longer be the case with Automake 2.0 though, so, if
211 you encounter the warning, please report it to us ASAP (and try to fix
212 your environment as well).
214 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
218 * Documentation fixes:
220 - The documentation no longer mistakenly reports that the obsolete
221 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
222 to be removed in Automake 2.0.
226 - Byte-compilation of Emacs lisp files could fail spuriously on
227 Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
229 - If the same user-defined suffixes were transformed into different
230 Automake-known suffixes in different Makefile.am files in the same
231 project, automake could get confused and generate inconsistent
232 Makefiles (automake bug#14441).
233 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
234 and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
235 would have mistakenly placed into 'Makefile.in' rules to compile
236 "*.c" files into object files, and into 'sub/Makefile.in' rules to
237 compile "*.cc" files into object files --- rather than the other
238 way around. This is now fixed.
242 - The test cases no longer have the executable bit set. This should
243 make it clear that they are not meant to be run directly; as
244 explained in t/README, they can only be run through the custom
245 'runtest' script, or by a "make check" invocation.
247 - The testsuite has seen the introduction of a new helper function
248 'run_make', and several related changes. These serve a two-fold
251 1. Remove brittleness due to the use of "make -e" in test cases.
253 2. Seamlessly allow the use of parallel make ("make -j...") in the
254 test cases, even where redirection of make output is involved
255 (see automake bug#11413 for a description of the subtle issues
258 - Several spurious failures have been fixed (they hit especially
259 MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
260 #14498, #14499, #14500, #14501, #14517 and #14528.
262 - Some other minor miscellaneous changes and fixlets.
264 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
268 * Documentation fixes:
270 - The long-deprecated but still supported two-arguments invocation form
271 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
272 thing to do, given that support for such usage might need to remain
273 in place for an unspecified amount of time in order to cater to people
274 who want to define the version number for their package dynamically at
275 configure runtime (unfortunately, Autoconf does not yet support this
276 scenario, so we cannot delegate the work to it).
278 - The serial testsuite harness is no longer reported as "deprecated",
279 but as "discouraged". We have no plan to remove it, nor to make its
280 use cause runtime warnings.
282 - The parallel testsuite is no longer reported as "experimental"; it
283 is well tested, and should be stable now.
285 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
286 'dist-tarZ' options are obsolescent, and their use is deprecated
287 in the documentation.
289 - Other minor miscellaneous fixes and improvements; in particular,
290 some improvements in cross-references.
292 * Obsolescent features:
294 - Use of suffix-less info files (that can be specified through the
295 '@setfilename' macro in Texinfo input files) is discouraged, and
296 its use will raise warnings in the 'obsolete' category. Simply
297 use the '.info' extension for all your info files, transforming
300 @setfilename myprogram
304 @setfilename myprogram.info
306 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
307 is discouraged, and its use will raise warnings in the 'obsolete'
308 category. You are advised to simply use the '.texi' extension
313 - When the 'ustar' option is used, the generated configure script no
314 longer risks hanging during the tests for the availability of the
315 'pax' utility, even if the user running configure has a UID or GID
316 that requires more than 21 bits to be represented.
317 See automake bug#8343 and bug#13588.
319 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
320 again, as they did in Automake 1.12.x (albeit printing runtime
321 warnings in the 'obsolete' category). Removing them has turned
322 out to be a very bad idea, because it complicated distro packing
323 enormously. Making them issue fatal warnings, as we did in
324 Automake 1.13, has turned out to be a similarly very bad idea,
325 for exactly the same reason.
327 - aclocal will no longer error out if the first local m4 directory
328 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
329 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
330 a warning in the 'unsupported' category. This is done to support
331 some pre-existing real-world usages. See automake bug#13514.
333 - aclocal will no longer consider directories for extra m4 files more
334 than once, even if they are specified multiple times. This ensures
335 packages that specify both
337 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
338 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
340 will work correctly, even when the 'm4' directory contains no
341 package-specific files, but is used only to install third-party
342 m4 files (as can happen with e.g., "libtoolize --install").
343 See automake bug#13514.
345 - Analysis of make flags in Automake-generated rules has been made more
346 robust, and more future-proof. For example, in presence of make that
347 (like '-I') take an argument, the characters in said argument will no
348 longer be spuriously considered as a set of additional make options.
349 In particular, automake-generated rules will no longer spuriously
350 believe to be running in dry mode ("make -n") if run with an invocation
351 like "make -I noob"; nor will they believe to be running in keep-going
352 mode ("make -k") if run with an invocation like "make -I kool"
353 (automake bug#12554).
355 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
361 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
362 causes a clear and helpful error message, instead of obscure ones
363 (issue introduced in Automake 1.13).
365 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
371 - ylwrap renames properly header guards in generated header files
372 (*.h), instead of leaving Y_TAB_H.
374 - ylwrap now also converts header guards in implementation files
375 (*.c). Because ylwrap failed to rename properly #include in the
376 implementation files, current versions of Bison (e.g., 2.7)
377 duplicate the generated header file in the implementation file.
378 The header guard then protects the implementation file from
379 duplicate definitions from the header file.
381 * Version requirements:
383 - Autoconf 2.65 or greater is now required.
385 - The rules to build PDF and DVI output from Texinfo input now
386 require Texinfo 4.9 or later.
390 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
391 option) has been removed. See discussion about automake bug#11034
392 for more background: <http://debbugs.gnu.org/11034>.
394 - The deprecated aclocal option '--acdir' has been removed. You
395 should use the options '--automake-acdir' and '--system-acdir'
396 instead (which have been introduced in Automake 1.11.2).
398 - The following long-obsolete m4 macros have been removed:
400 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
401 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
402 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
403 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
404 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
405 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
406 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
407 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
408 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
409 of the now-removed automatic de-ANSI-fication
412 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
414 - Use of the long-deprecated two- and three-arguments invocation forms
415 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
416 though (albeit with a warning in the 'obsolete' category), to cater
417 for people who want to define the version number for their package
418 dynamically (e.g., from the current VCS revision). We'll have to
419 continue this support until Autoconf itself is fixed to allow better
420 support for such dynamic version numbers.
422 * Elisp byte-compilation:
424 - The byte compilation of '.el' files into '.elc' files is now done
425 with a suffix rule. This has simplified the compilation process, and
426 more importantly made it less brittle. The downside is that emacs is
427 now invoked once for each '.el' files, which cause some noticeable
428 slowdowns. These should however be mitigated on multicore machines
429 (which are becoming the norm today) if concurrent make ("make -j")
432 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
433 files in the same subdirectory; for example, byte-compiling of file
434 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
435 'foo.elc'. This behaviour is backward-incompatible with older
436 Automake versions, but it is more natural and more sane. See also
439 - The Emacs invocation performing byte-compilation of '.el' files honors
440 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
441 one is developer-reserved and the latter one user-reserved.
443 - The 'elisp-comp' script, once provided by Automake, has been rendered
444 obsoleted by the just-described changes, and thus removed.
446 * Changes to Automake-generated testsuite harnesses:
448 - The parallel testsuite harness (previously only enabled by the
449 'parallel-tests' option) is the default one; the older serial
450 testsuite harness will still be available through the use of the
451 'serial-tests' option (introduced in Automake 1.12).
453 - The 'color-tests' option is now unconditionally activated by default.
454 In particular, this means that testsuite output is now colorized by
455 default if the attached terminal seems to support ANSI escapes, and
456 that the user can force output colorization by setting the variable
457 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
458 for backward-compatibility, although it's a handled as a no-op now.
460 * Silent rules support:
462 - Support for silent rules is now always active in Automake-generated
463 Makefiles. So, although the verbose output is still the default,
464 the user can now always use "./configure --enable-silent-rules" or
465 "make V=0" to enable quieter output in the package he's building.
467 - The 'silent-rules' option has now become a no-op, preserved for
468 backward-compatibility only. In particular, its use no longer
469 disables the warnings in the 'portability-recursive' category.
473 - The rules to build PDF and DVI files from Texinfo input now require
474 Texinfo 4.9 or later.
476 - The rules to build PDF and DVI files from Texinfo input now use the
477 '--build-dir' option, to keep the auxiliary files used by texi2dvi
478 and texi2pdf around without cluttering the build directory, and to
479 make it possible to run the "dvi" and "pdf" recipes in parallel.
481 * Automatic remake rules and 'missing' script:
483 - The 'missing' script no longer tries to update the timestamp of
484 out-of-date files that require a maintainer-specific tool to be
485 remade, in case the user lacks such a tool (or has a too-old version
486 of it). It just gives a useful warning, and in some cases also a
487 tip about how to obtain such a tool.
489 - The missing script has thus become useless as a (poor) way to work
490 around the sketched-timestamps issues that can happen for projects
491 that keep generated files committed in their VCS repository. Such
492 projects are now encouraged to write a custom "fix-timestamps.sh"
493 script to avoid such issues; a simple example is provided in the
494 "CVS and generated files" chapter of the automake manual.
498 - The user can now define his own recursive targets that recurse
499 in the directories specified in $(SUBDIRS). This can be done by
500 specifying the name of such targets in invocations of the new
501 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
505 - Any failure in the recipe of the "tags", "ctags", "cscope" or
506 "cscopelist" targets in a subdirectory is now propagated to the
507 top-level make invocation.
509 - Tags are correctly computed also for files in _SOURCES variables that
510 only list files with non-standard suffixes (see automake bug#12372).
512 * Improvements to aclocal and related rebuilds rules:
514 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
515 are now traced by aclocal, and can be used to declare the local m4
516 include directories. Formerly, one had to specify it with an explicit
517 '-I' option to the 'aclocal' invocation.
519 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
520 Automake versions will warn about its use, and later version will
521 remove support for it altogether.
523 * The depcomp script:
525 - Dropped support for libtool 1.4.
527 - Various internal refactorings. They should cause no visible change,
528 but the chance for regression is there anyway, so please report any
529 unexpected or suspicious behaviour.
531 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
532 This should cause no problem, since icc 8.0 has been released in
533 December 2003 -- almost nine years ago.
535 - Support for tcc (the Tiny C Compiler) has been improved, and is now
536 handled through a dedicated 'tcc' mode.
540 - ylwrap generates header guards with a single '_' for series of non
541 alphabetic characters, instead of several. This is what Bison >=
544 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
546 Bugs fixed in 1.12.6:
548 * Python-related bugs:
550 - The default installation location for python modules has been improved
551 for Python 3 on Debian and Ubuntu systems, changing from:
553 ${prefix}/lib/python3/dist-packages
557 ${prefix}/lib/python3.x/site-packages
559 This change should ensure modules installed using the default ${prefix}
560 "/usr/local" are found by default by system python 3.x installations.
561 See automake bug#10227.
563 - Python byte-compilation supports the new layout mandated by PEP-3147,
564 with its __pycache__ directory (automake bug#8847).
566 * Build system issues:
568 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
569 Automake's own build system works correctly again (bug introduced
574 - The Vala-related tests has been changed to adjust to the removal of
575 the 'posix' profile in the valac compiler. See automake bug#12934
578 - Some spurious testsuite failures related to older tools and systems
581 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
587 - The AM_PROG_VALAC macro has been enhanced to takes two further
588 optional arguments; it's signature now being
590 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
591 [ACTION-IF-NOT-FOUND])
593 - By default, AM_PROG_VALAC no longer aborts the configure invocation
594 if the Vala compiler found is too old, but simply prints a warning
595 messages (as it did when the Vala compiler was not found). This
596 should avoid unnecessary difficulties for end users that just want
597 to compile the unmodified, distributed Vala-generated C sources,
598 but happens to have an old Vala compiler in their PATH. This fixes
601 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
602 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
603 This is a better default, because with it a triggered makefile rule
604 invoking a Vala compilation will clearly fail with an informative error
605 message like "valac: command not found", rather than silently, with
606 the error possibly going unnoticed or triggering harder-to-diagnose
607 fallout failures in later steps.
609 * Miscellaneous changes:
611 - automake and aclocal no longer honours the 'perllibdir' environment
612 variable. That had always been intended only as an hack required in
613 the testsuite, not meant for any use beyond that.
615 Bugs fixed in 1.12.5:
617 * Long-standing bugs:
619 - Automake no longer generates spurious remake rules invoking autoheader
620 to regenerate the template corresponding to header files specified after
621 the first one in AC_CONFIG_HEADERS (automake bug#12495).
623 - When wrapping Microsoft tools, the 'compile' script falls back to
624 finding classic 'libname.a' style libraries when 'name.lib' and
625 'name.dll.lib' aren't available.
627 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
631 * Warnings and deprecations:
633 - Warnings in the 'obsolete' category are enabled by default both in
634 automake and aclocal.
636 * Miscellaneous changes:
638 - Some testsuite weaknesses and spurious failures have been fixed.
640 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
644 * Miscellaneous changes:
646 - The '.m4' files provided by Automake no longer define serial numbers.
647 This should cause no difference in the behaviour of aclocal though.
649 - Some testsuite weaknesses and spurious failures have been fixed.
651 - There is initial support for automatic dependency tracking with the
652 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
654 Bugs fixed in 1.12.3:
656 * Long-standing bugs:
658 - Instead of renaming only self-references of files (typically for
659 #lines), ylwrap now also renames references to the other generated
660 files. This fixes support for GLR and C++ parsers from Bison (PR
661 automake/491 and automake bug#7648): 'parser.c' now properly
662 #includes 'parser.h' instead of 'y.tab.h'.
664 - Generated files unknown to ylwrap are now preserved. This fixes
665 C++ support for Bison (automake bug#7648): location.hh and the
666 like are no longer discarded.
668 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
672 * Warnings and deprecations:
674 - Automake now issues a warning (in the 'portability' category) if
675 'configure.in' is used instead of 'configure.ac' as the Autoconf
676 input file. Such a warning will also be present in the next
677 Autoconf version (2.70).
681 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
682 order (as done by the other recursive rules), rather than in the
683 inverse order. They used to do that in order to work a round a
684 limitation in an older implementation of the automatic dependency
685 tracking support, but that limitation had been lifted years ago
686 already, when the automatic dependency tracking based on side-effects
687 of compilation had been introduced.
689 - Cleaning rules for compiled objects (both "plain" and libtool) work
690 better when subdir objects are involved, not triggering a distinct
691 'rm' invocation for each such object. They do so by removing *any*
692 compiled object file that is in the same directory of a subdir
693 object. See automake bug#10697.
695 * Silent rules support:
697 - A new predefined $(AM_V_P) make variable is provided; it expands
698 to a shell conditional that can be used in recipes to know whether
699 make is being run in silent or verbose mode.
701 Bugs fixed in 1.12.2:
703 * SECURITY VULNERABILITIES!
705 - The 'distcheck' recipe no longer grants temporary world-write
706 permissions on the extracted distdir. Even if such rights were
707 only granted for a vanishingly small time window, the implied
708 race condition proved to be enough to allow a local attacker
709 to run arbitrary code with the privileges of the user running
710 "make distcheck". This is CVE-2012-3386.
712 * Long-standing bugs:
714 - The "recheck" targets behaves better in the face of build failures
715 related to previously failed tests. For example, if a test is a
716 compiled program that must be rerun by "make recheck", and its
717 compilation fails, it will still be rerun by further "make recheck"
718 invocations. See automake bug#11791.
720 * Bugs introduced by 1.12.1:
722 - Automake provides once again the '$(mkdir_p)' make variable and the
723 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
724 for better backward-compatibility.
726 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
730 * New supported languages:
732 - Support for Objective C++ has been added; it should work similarly to
733 the support for Objective C.
735 * Deprecated obsolescent features:
737 - Use of the long-deprecated two- and three-arguments invocation forms
738 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
739 category. Starting from some future major Automake release (likely
740 post-1.13), such usages will no longer be allowed.
742 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
743 now deprecated (its use triggers a warning in the 'obsolete' category).
744 It will be removed in the next major Automake release (1.13).
746 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
747 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
748 m4 macro are deprecated, eliciting a warning in the 'obsolete'
751 * Miscellaneous changes:
753 - The Automake test cases now require a proper POSIX-conforming shell.
754 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
755 be accepted. In most cases, the user shouldn't have to specify such
756 POSIX shell explicitly, since it will be looked up at configure time.
757 Still, when this lookup fails, or when the user wants to override its
758 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
759 to the shell that will be used to run the Automake test cases).
761 Bugs fixed in 1.12.1:
763 * Bugs introduced by 1.12:
765 - Several weaknesses in Automake's own build system and test suite
768 * Bugs introduced by 1.11.3:
770 - When given non-option arguments, aclocal rejects them, instead of
771 silently ignoring them.
773 * Long-standing bugs:
775 - When the 'color-tests' option is in use, forcing of colored testsuite
776 output through "AM_COLOR_TESTS=always" works even if the terminal is
777 a non-ANSI one, i.e., if the TERM environment variable has a value of
780 - Several inefficiencies and poor performances in the implementation
781 of the parallel-tests 'check' and 'recheck' targets have been fixed.
783 - The post-processing of output "#line" directives done the ylwrap
784 script is more faithful w.r.t. files in a subdirectory; for example,
785 if the processed file is "src/grammar.y", ylwrap will correctly
786 produce directives like:
787 #line 7 "src/grammar.y"
792 * Bugs with new Perl versions:
794 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
796 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
800 * Obsolete features removed:
802 - The never documented nor truly used script 'acinstall' has been
805 - Support for automatic de-ANSI-fication has been removed.
807 - The support for the "obscure" multilib feature has been removed
808 from Automake core (but remains available in the 'contrib/'
809 directory of the Automake distribution).
811 - Support for ".log -> .html" conversion and the check-html and
812 recheck-html targets has been removed from Automake core (but
813 remains available in the 'contrib/' directory of the Automake
816 - The deprecated 'lzma' compression format for distribution archives
817 has been removed, in favor of 'xz' and 'lzip'.
819 - The obsolete AM_WITH_REGEX macro has been removed.
821 - The long-deprecated options '--output-dir', '--Werror' and
822 '--Wno-error' have been removed.
824 - The chapter on the history of Automake has been moved out of the
825 reference manual, into a new dedicated Texinfo file.
829 - New 'cscope' target to build a cscope database for the source tree.
831 * Changes to Automake-generated testsuite harnesses:
833 - The new automake option 'serial-tests' has been introduced. It can
834 be used to explicitly instruct automake to use the older serial
835 testsuite harness. This is still the default at the moment, but it
836 might change in future versions.
838 - The 'recheck' target (provided by the parallel testsuite harness) now
839 depends on the 'all' target. This allows for a better user-experience
840 in test-driven development. See automake bug#11252.
842 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
843 and unexpected or internal error, or a failure to set up the test case
844 scenario) have their outcome reported as an 'ERROR' now. Previous
845 versions of automake reported such an outcome as a 'FAIL' (the only
846 difference with normal failures being that hard errors were counted
847 as failures even when the test originating them was listed in
850 - The testsuite summary displayed by the parallel-test harness has a
851 completely new format, that always list the numbers of passed, failed,
852 xfailed, xpassed, skipped and errored tests, even when these numbers
853 are zero (but using smart coloring when the color-tests option is in
856 - The default testsuite driver offered by the 'parallel-tests' option is
857 now implemented (partly at least) with the help of automake-provided
858 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
859 on code in the generated Makefile.in.
860 This has two noteworthy implications. The first one is that projects
861 using the 'parallel-tests' option should now either run automake with
862 the '--add-missing' option, or manually copy the 'test-driver' script
863 into their tree. The second, and more important, implication is that
864 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
865 no longer be used to define a test runner, and the command specified
866 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
867 program or script. For example, this is still a valid usage (albeit
870 TESTS_ENVIRONMENT = \
871 if test -n '$(STRICT_TESTS)'; then \
872 maybe_errexit='-e'; \
876 LOG_COMPILER = $(SHELL) $$maybe_errexit
878 OTOH, this is no longer a valid usage:
880 TESTS_ENVIRONMENT = \
881 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
885 TESTS_ENVIRONMENT = \
886 run_with_perl_or_shell () \
888 if grep -q '^#!.*perl' $$1; then
894 LOG_COMPILER = run_with_perl_or_shell
896 - The package authors can now use customary testsuite drivers within
897 the framework provided by the 'parallel-tests' testsuite harness.
898 Consistently with the existing syntax, this can be done by defining
899 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
901 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
902 to redirect/define file descriptors used by the test scripts.
904 - The parallel-tests harness generates now, in addition the '.log' files
905 holding the output produced by the test scripts, a new set of '.trs'
906 files, holding "metadata" derived by the execution of the test scripts;
907 among such metadata are the outcomes of the test cases run by a script.
909 - Initial and still experimental support for the TAP test protocol is
912 * Changes to Yacc and Lex support:
914 - C source and header files derived from non-distributed Yacc and/or
915 Lex sources are now removed by a simple "make clean" (while they were
916 previously removed only by "make maintainer-clean").
918 - Slightly backward-incompatible change, relevant only for use of Yacc
919 with C++: the extensions of the header files produced by the Yacc
920 rules are now modelled after the extension of the corresponding
921 sources. For example, yacc files named "foo.y++" and "bar.yy" will
922 produce header files named "foo.h++" and "bar.hh" respectively, where
923 they would have previously produced header files named simply "foo.h"
924 and "bar.h". This change offers better compatibility with 'bison -o'.
926 * Miscellaneous changes:
928 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
929 rather than 1, if the vala compiler found is too old.
931 - The build system of Automake itself now avoids the use of make
932 recursion as much as possible.
934 - Automake now prefers to quote 'like this' or "like this", rather
935 than `like this', in diagnostic message and generated Makefiles,
936 to accommodate the new GNU Coding Standards recommendations.
938 - Automake has a new option '--print-libdir' that prints the path of the
939 directory containing the Automake-provided scripts and data files.
941 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
943 - The rules to create pdf, dvi and ps output from Texinfo files now
944 works better with modern 'texi2dvi' script, by explicitly passing
945 it the '--clean' option to ensure stray auxiliary files are not
946 left to clutter the build directory.
948 - Automake can now generate silenced rules for texinfo outputs.
950 - Some auxiliary files that are automatically distributed by Automake
951 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
952 C sources) might now be listed in the DIST_COMMON variable in many
953 Makefile.in files, rather than in the top-level one.
955 - Messages of types warning or error from 'automake' and 'aclocal'
956 are now prefixed with the respective type, and presence of -Werror
959 - Automake's early configure-time sanity check now tries to avoid
960 sleeping for a second, which slowed down cached configure runs
961 noticeably. In that case, it will check back at the end of the
962 configure script to ensure that at least one second has passed, to
963 avoid time stamp issues with makefile rules rerunning autotools
966 - The warnings in the category 'extra-portability' are now enabled by
967 '-Wall'. In previous versions, one has to use '-Wextra-portability'
972 - Various minor bugfixes for recent or long-standing bugs.
974 * Bugs introduced by 1.11:
976 - The AM_COND_IF macro also works if the shell expression for the
977 conditional is no longer valid for the condition.
979 - The automake-provided parallel testsuite harness no longer fails
980 with BSD make used in parallel mode when there are test scripts in
981 a subdirectory, like in:
983 TESTS = sub/foo.test sub/bar.test
985 * Long-standing bugs:
987 - Automake's own build system finally have a real "installcheck" target.
989 - Vala-related cleanup rules are now more complete, and work better in
992 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
993 now automatically distributed also if the directory of the auxiliary
994 files coincides with the top-level directory.
996 - Automake now detects the presence of the '-d' flag in the various
997 '*YFLAGS' variables even when their definitions involve indirections
998 through other variables, such as in:
1000 AM_YFLAGS = $(foo_opts)
1002 - Automake now complains if a '*YFLAGS' variable has any conditional
1003 content, not only a conditional definition.
1005 - Explicit enabling and/or disabling of Automake warning categories
1006 through the '-W...' options now always takes precedence over the
1007 implicit warning level implied by Automake strictness (foreign, gnu
1008 or gnits), regardless of the order in which such strictness and
1009 warning flags appear. For example, a setting like:
1010 AUTOMAKE_OPTIONS = -Wall --foreign
1011 will cause the warnings in category 'portability' to be enabled, even
1012 if those warnings are by default disabled in 'foreign' strictness.
1014 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1016 Bugs fixed in 1.11.5:
1018 * Bugs introduced by 1.11.3:
1020 - Vala files with '.vapi' extension are now recognized and handled
1021 correctly again. See automake bug#11222.
1023 - Vala support work again for projects that contain some program
1024 built from '.vala' (and possibly '.c') sources and some other
1025 program built from '.c' sources *only*. See automake bug#11229.
1027 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1031 * Miscellaneous changes:
1033 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
1034 symbol index) modifiers as well as the "s" action, as the symbol index
1035 is created unconditionally by Microsoft lib. Also, the "q" (quick)
1036 action is now a synonym for "r" (replace). Also, the script has been
1037 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
1039 - When the 'compile' script is used to wrap MSVC, it now accepts an
1040 optional space between the -I, -L and -l options and their respective
1041 arguments, for better POSIX compliance.
1043 - There is an initial, experimental support for automatic dependency
1044 tracking with tcc (the Tiny C Compiler). Its associated depmode is
1045 currently recognized as "icc" (but this and other details are likely
1046 to change in future versions).
1048 - Automatic dependency tracking now works also with the IBM XL C/C++
1049 compilers, thanks to the new new depmode 'xlc'.
1051 Bugs fixed in 1.11.4:
1053 * Bugs introduced by 1.11.2:
1055 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
1056 no longer cause spurious failures upon "make install".
1058 - The user can now instruct the 'uninstall-info' rule not to update
1059 the '${infodir}/dir' file by exporting the environment variable
1060 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
1061 with how the 'install-info' rule operates since automake 1.11.2.
1063 * Long-standing bugs:
1065 - It is now possible for a foo_SOURCES variable to hold Vala sources
1066 together with C header files, as well as with sources and headers for
1067 other supported languages (e.g., C++). Previously, only mixing C and
1068 Vala sources was supported.
1070 - If "aclocal --install" is used, and the first directory specified with
1071 '-I' is non-existent, aclocal will now create it before trying to copy
1074 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
1075 install rules to create an empty $(foodir) directory; for example, if
1076 Makefile.am contains something like:
1078 pkglibexec_SCRIPTS =
1080 pkglibexec_SCRIPTS += bar.sh
1083 the $(pkglibexec) directory will not be created upon "make install".
1085 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1089 * Miscellaneous changes:
1091 - Automake's own build system is more silent by default, making use of
1092 the 'silent-rules' option.
1094 - The master copy of the 'gnupload' script is now maintained in gnulib,
1097 - The 'missing' script no longer tries to wrap calls to 'tar'.
1099 - "make dist" no longer wraps 'tar' invocations with the 'missing'
1100 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
1101 shouldn't be using BTW ;-) no longer invokes the 'missing' script
1102 to wrap tar, but simply invokes the 'tar' program itself.
1104 - "make dist" can now create lzip-compressed tarballs.
1106 - In the Automake info documentation, the Top node and the nodes about
1107 the invocation of the automake and aclocal programs have been renamed;
1108 now, calling "info automake" will open the Top node, while calling
1109 "info automake-invocation" and "info aclocal-invocation" will access
1110 the nodes about the invocation of respectively automake and aclocal.
1112 - Automake is now distributed as a gzip-compressed and an xz-compressed
1113 tarball. Previously, bzip2 was used instead of xz.
1115 - The last relics of Python 1.5 support have been removed from the
1116 AM_PATH_PYTHON macro.
1118 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
1119 and adds them to the normal list of dependencies, but without
1120 overwriting the foo_DEPENDENCIES variable, which is normally computed
1123 Bugs fixed in 1.11.3:
1125 * Bugs introduced by 1.11.2:
1127 - Automake now correctly recognizes the prefix/primary combination
1128 'pkglibexec_SCRIPTS' as valid.
1130 - The parallel-tests harness no longer trips on sed implementations
1131 with stricter limits on the length of input lines (problem seen at
1132 least on Solaris 8).
1134 * Long-standing bugs:
1136 - The "deleted header file problem" for *.am files is avoided by stub
1137 rules. This allows 'make' to trigger a rerun of 'automake' also if
1138 some previously needed '.am' file has been removed.
1140 - The 'silent-rules' option now generates working makefiles even
1141 for the uncommon 'make' implementations that do not support the
1142 nested-variables extension to POSIX 2008. For such 'make'
1143 implementations, whether a build is silent is determined at
1144 configure time, and cannot be overridden at make time with
1145 "make V=0" or "make V=1".
1147 - Vala support now works better in VPATH setups.
1149 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1153 * Changes to aclocal:
1155 - The `--acdir' option is deprecated. Now you should use the new options
1156 `--automake-acdir' and `--system-acdir' instead.
1158 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1159 colon-separated list of additional directories to search after the
1160 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1161 and before the system acdir (by default ${prefix}/share/aclocal).
1163 * Miscellaneous changes:
1165 - The Automake support for automatic de-ANSI-fication has been
1166 deprecated. It will probably be removed in the next major Automake
1169 - The `lzma' compression scheme and associated automake option `dist-lzma'
1170 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1172 - You may adjust the compression options used in dist-xz and dist-bzip2.
1173 The default is now merely -e for xz, but still -9 for bzip; you may
1174 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1175 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1177 - The `compile' script now converts some options for MSVC for a better
1178 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1180 - The py-compile script now accepts empty arguments passed to the options
1181 `--destdir' and `--basedir', and complains about unrecognized options.
1182 Moreover, a non-option argument or a special `--' argument terminates
1183 the list of options.
1185 - A developer that needs to pass specific flags to configure at "make
1186 distcheck" time can now, and indeed is advised to, do so by defining
1187 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1188 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1189 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1190 user; still, the old Makefile.am files that used to define it will
1191 still continue to work as before.
1193 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1194 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1195 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1196 is run with -Wextra-portability and -Werror.
1198 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1199 file generated by automake-provided rules by defining the special make
1200 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1202 - The `install-info' rule can now be instructed not to create/update
1203 the `${infodir}/dir' file, by exporting the new environment variable
1204 `AM_UPDATE_INFO_DIR' to the value "no".
1206 Bugs fixed in 1.11.2:
1208 * Bugs introduced by 1.11:
1210 - The parallel-tests driver no longer produces erroneous results with
1211 Tru64/OSF 5.1 sh upon unreadable log files.
1213 - The `parallel-tests' test driver does not report spurious successes
1214 when used with concurrent FreeBSD make (e.g., "make check -j3").
1216 - When the parallel-tests driver is in use, automake now explicitly
1217 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1218 instead of issuing confusing and apparently unrelated error messages
1219 (e.g., "non-POSIX variable name", "bad characters in variable name",
1220 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1221 silently producing broken `Makefile.in' files.
1223 - The `silent-rules' option now truly silences all compile rules, even
1224 when dependency tracking is disabled. Also, when `silent-rules' is
1225 not used, `make' output no longer contains spurious backslash-only
1226 lines, thus once again matching what Automake did before 1.11.
1228 - The AM_COND_IF macro also works if the shell expression for the
1229 conditional is no longer valid for the condition.
1231 * Long-standing bugs:
1233 - The order of Yacc and Lex flags is fixed to be consistent with other
1234 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1235 $(LFLAGS), so that the user variables override the developer variables.
1237 - "make distcheck" now correctly complains also when "make uninstall"
1238 leaves one and only one file installed in $(prefix).
1240 - A "make uninstall" issued before a "make install", or after a mere
1241 "make install-data" or a mere "make install-exec" does not spuriously
1244 - Automake now warns about more primary/directory invalid combinations,
1245 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1247 - Rules generated by Automake now try harder to not change any files when
1248 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1249 Yacc source files and the rule to update config.h.
1251 - Several scripts and the parallel-tests testsuite driver now exit with
1252 the right exit status upon receiving a signal.
1254 - A per-Makefile.am setting of -Werror does not erroneously carry over
1255 to the handling of other Makefile.am files.
1257 - The code for automatic dependency tracking works around a Solaris
1258 make bug triggered by sources containing repeated slashes when the
1259 `subdir-objects' option was used.
1261 - The makedepend and hp depmodes now work better with VPATH builds.
1263 - Java sources specified with check_JAVA are no longer compiled for
1264 "make all", but only for "make check".
1266 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1267 and error out if `javadir' is undefined, instead of silently producing
1268 a broken Makefile.in.
1270 - aclocal and automake now honour the configure-time definitions of
1271 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1273 - The `install-info' recipe no longer tries to guess whether the
1274 `install-info' program is from Debian or from GNU, and adaptively
1275 change its behaviour; this has proven to be frail and easy to
1278 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1280 Bugs fixed in 1.11.1:
1282 - Lots of minor bugfixes.
1284 * Bugs introduced by 1.11:
1286 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1287 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1289 * Long standing bugs:
1291 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1292 even if the `--prefix' argument pointed outside of a system directory.
1293 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1294 `get_python_lib' function if it points outside the configured prefix,
1295 unless the `--prefix' argument was either `/usr' or below `/System'.
1297 - The testsuite does not try to change the mode of `ltmain.sh' files from
1298 a Libtool installation (symlinked to test directories) any more.
1300 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1301 tools are preferred in a cross-compile setup.
1303 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1304 This fixes a race condition where untrusted users could modify files
1305 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1306 build directory was world-searchable. This is CVE-2009-4029.
1308 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1312 * Version requirements:
1314 - Autoconf 2.62 or greater is required.
1316 * Changes to aclocal:
1318 - The autoconf version check implemented by aclocal in aclocal.m4
1319 (and new in Automake 1.10) is degraded to a warning. This helps
1320 in the common case where the Autoconf versions used are compatible.
1322 * Changes to automake:
1324 - The automake program can run multiple threads for creating most
1325 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1326 with interpreter-based threads enabled. Set the environment variable
1327 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1328 enable this experimental feature.
1330 * Changes to Libtool support:
1332 - Libtool generic flags are now passed to the install and uninstall
1335 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1336 config.lt is removed correctly now.
1338 * Languages changes:
1340 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1341 Fortran, and Ratfor).
1343 - For files with extension .f90, .f95, .f03, or .f08, the flag
1344 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1346 - Files with extension .sx are also treated as preprocessed assembler.
1348 - The default source file extension (.c) can be overridden with
1349 AM_DEFAULT_SOURCE_EXT now.
1351 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1354 - AM_PATH_PYTHON honors python's idea about the site directory.
1356 - There is initial support for the Vala programming language, when using
1357 Vala 0.7.0 or later.
1359 * Miscellaneous changes:
1361 - Automake development is done in a git repository on Savannah now, see
1363 http://git.sv.gnu.org/gitweb/?p=automake.git
1365 A read-only CVS mirror is provided at
1367 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1368 checkout -d automake HEAD
1370 - "make dist" can now create xz-compressed tarballs,
1371 as well as (deprecated?) lzma-compressed tarballs.
1373 - `automake --add-missing' will by default install the GPLv3 file as
1374 COPYING if it is missing. It will also warn that the license file
1375 should be added to source control. Note that Automake will never
1376 overwrite an existing COPYING file, even when the `--force-missing'
1379 - The manual is now distributed under the terms of the GNU FDL 1.3.
1381 - Automake ships and installs man pages for automake and aclocal now.
1383 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1385 - install-sh supports -C, which does not update the installed file
1386 (and its time stamps) if the contents did not change.
1388 - The `gnupload' script has been revamped.
1390 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1392 - The targets `install' and `uninstall' are more efficient now, in that
1393 for example multiple files from one Automake variable such as
1394 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1395 invocation if they do not have to be renamed.
1397 Both install and uninstall may sometimes enter (`cd' into) the target
1398 installation directory now, when no build-local scripts are used.
1400 Both install and uninstall do not fail anymore but do nothing if an
1401 installation directory variable like `bindir' is set to the empty string.
1403 For built-in rules, `make install' now fails reliably if installation
1404 of a file failed. Conversely, `make uninstall' even succeeds when
1405 issued multiple times.
1407 These changes may need some adjustments from users: For example,
1408 some `install' programs refuse to install multiple copies of the
1409 same file in one invocation, so you may need to remove duplicate
1410 entries from file lists.
1412 Also, within one set of files, say, nobase_data_DATA, the order of
1413 installation may be changed, or even unstable among different hosts,
1414 due to the use of associative arrays in awk. The increased use of
1415 awk matches a similar move in Autoconf to provide for better scaling.
1417 Further, most undocumented per-rule install command variables such as
1418 binSCRIPT_INSTALL have been removed because they are not needed any
1419 more. Packages which use them should be using the appropriate one of
1420 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1421 counterpart, depending on the type of files and the need for automatic
1422 target directory creation.
1424 - The "deleted header file problem" for *.m4 files is avoided by
1425 stub rules. This allows `make' to trigger a rerun of `aclocal'
1426 also if some previously needed macro file has been removed.
1428 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1429 an otherwise up to date tree.
1431 - The `color-tests' option causes colored test result output on terminals.
1433 - The `parallel-tests' option enables a new test driver that allows for
1434 parallel test execution, inter-test dependencies, lazy test execution
1435 for unit-testing, re-testing only failed tests, and formatted result output
1436 as RST (reStructuredText) and HTML. Enabling this option may require some
1437 changes to your test suite setup; see the manual for details.
1439 - The `silent-rules' option enables Linux kernel-style silent build output.
1440 This option requires the widely supported but non-POSIX `make' feature
1441 of recursive variable expansion, so do not use it if your package needs
1442 to build with `make' implementations that do not support it.
1444 To enable less verbose build output, the developer has to use the Automake
1445 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1446 macro. The user may then set the default verbosity by passing the
1447 `--enable-silent-rules' option to `configure'. At `make' run time, this
1448 default may be overridden using `make V=0' for less verbose, and `make V=1'
1449 for backward-compatible verbose output.
1451 - New prefix `notrans_' for manpages which should not be transformed
1452 by --program-transform.
1454 - New macro AM_COND_IF for conditional evaluation and conditional
1457 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1458 remove the file in a non-VPATH build. Such setups work with Autoconf
1461 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1462 the default setting.
1464 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1465 useful especially for multi-line values.
1467 - Automake's early configure-time sanity check now diagnoses an
1468 unsafe absolute source directory name and makes configure fail.
1470 - The Automake macros and rules cope better with whitespace in the
1471 current directory name, as long as the relative path to `configure'
1472 does not contain whitespace. To this end, the values of `$(MISSING)'
1473 and `$(install_sh)' may contain suitable quoting, and their expansion
1474 might need `eval'uation if used outside of a makefile. These
1475 undocumented variables may be used in several documented macros such
1476 as $(AUTOCONF) or $(MAKEINFO).
1480 * Long-standing bugs:
1482 - Fix aix dependency tracking for libtool objects.
1484 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1485 unnecessary use of the `compile' script.
1487 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1488 correct `-rpath' argument is used now.
1490 - `config.status --file=Makefile depfiles' now also works with the
1491 extra quoting used internally by Autoconf 2.62 and newer
1492 (it used to work only without the `--file=' bit).
1494 - The `missing' script works better with versioned tool names.
1496 - Semantics for `missing help2man' have been revamped:
1498 Previously, if `help2man' was not present, `missing help2man' would have
1499 the following semantics: if some man page was out of date but present, then
1500 a warning would be printed, but the exit status was 0. If the man page was
1501 not present at all, then `missing' would create a replacement man page
1502 containing an error message, and exit with a status of 2. This does not play
1503 well with `make': the next run will see this particular man page as being up
1504 to date, and will only error out on the next generated man page, if any;
1505 repeat until all pages are done. This was not desirable.
1507 These are the new semantics: if some man page is not present, and help2man
1508 is not either, then `missing' will warn and generate the replacement page
1509 containing the error message, but exit successfully. However, `make dist'
1510 will ensure that no such bogus man pages are packaged into a tarball.
1512 - Targets provided by automake behave better with `make -n', in that they
1513 take care not to create files.
1515 - `config.status Makefile... depfiles' works fine again in the presence of
1516 disabled dependency tracking.
1518 - The default no-op recursive rules for these targets also work with BSD make
1519 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1521 - `make distcheck' works also when both a directory and some file below it
1522 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1524 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1525 `make mostlyclean' any more; only the LaTeX by-products are.
1527 - Renamed objects also work with the `subdir-objects' option and
1528 source file languages which Automake does not know itself.
1530 - `automake' now correctly complains about variable assignments which are
1531 preceded by a comment, extend over multiple lines with backslash-escaped
1532 newlines, and end in a comment sign. Previous versions would silently
1533 and wrongly ignore such assignments completely.
1535 * Bugs introduced by 1.10:
1537 - Fix output of dummy dependency files in presence of post-processed
1538 Makefile.in's again, but also cope with long lines.
1540 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1541 that have been declared as programs in the same Makefile.
1542 This is for consistency with the analogous change to TESTS in 1.10.
1544 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1545 followed by directories containing config headers.
1547 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1551 * Version requirements:
1553 - Autoconf 2.60 or greater is required.
1555 - Perl 5.6 or greater is required.
1557 * Changes to aclocal:
1559 - aclocal now also supports -Wmumble and -Wno-mumble options.
1561 - `dirlist' entries (for the aclocal search path) may use shell
1562 wildcards such as `*', `?', or `[...]'.
1564 - aclocal supports an --install option that will cause system-wide
1565 third-party macros to be installed in the local directory
1566 specified with the first -I flag. This option also uses #serial
1567 lines in M4 files to upgrade local macros.
1569 The new aclocal options --dry-run and --diff help to review changes
1570 before they are installed.
1572 - aclocal now outputs an autoconf version check in aclocal.m4 in
1573 projects using automake.
1575 For a few years, automake and aclocal have been calling autoconf
1576 (or its underlying engine autom4te) to accurately retrieve the
1577 data they need from configure.ac and its siblings. Doing so can
1578 only work if all autotools use the same version of autoconf. For
1579 instance a Makefile.in generated by automake for one version of
1580 autoconf may stop working if configure is regenerated with another
1581 version of autoconf, and vice versa.
1583 This new version check ensures that the whole build system has
1584 been generated using the same autoconf version.
1586 * Support for new Autoconf macros:
1588 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1590 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1591 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1592 in different directories. However, only one instance of such a
1593 library objects directory is supported.
1595 * Change to Libtool support:
1597 - Libtool generic flags (those that go before the --mode=MODE option)
1598 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1600 * Yacc and Lex changes:
1602 - The rebuild rules for distributed Yacc and Lex output will avoid
1603 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1606 - ylwrap is now always used for lex and yacc source files,
1607 regardless of whether there is more than one source per directory.
1609 * Languages changes:
1611 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1612 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1613 tracking, unlike non-preprocessed assembler (*.s).
1615 - subdir-object mode works now with Assembler. Automake assumes
1616 that the compiler understands `-c -o'.
1618 - Preprocessed assembler (*.S) compilation now also honors
1619 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1621 - Improved support for Objective C:
1622 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1623 - A new section of the manual documents the support.
1625 - New support for Unified Parallel C:
1626 - AM_PROG_UPC looks for a UPC compiler.
1627 - A new section of the manual documents the support.
1629 - Per-target flags are now correctly handled in link rules.
1631 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1632 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1633 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1634 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1636 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1637 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1638 is expected to work (and actually works during compilation).
1640 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1641 "in addition to" breaks backward compatibility with older versions.
1642 If your package used both variables, as in
1644 AM_LDFLAGS = common flags
1645 bin_PROGRAMS = a b c
1646 a_LDFLAGS = more flags
1649 and assumed *_LDFLAGS would sum up, you should rewrite it as
1651 AM_LDFLAGS = common flags
1652 bin_PROGRAMS = a b c
1653 a_LDFLAGS = $(AM_LDFLAGS) more flags
1656 This new behavior of *_LDFLAGS is more coherent with other
1657 per-target variables, and the way *_LDFLAGS variables were
1658 considered internally.
1660 * New installation targets:
1662 - New targets mandated by GNU Coding Standards:
1667 By default they will only install Texinfo manuals.
1668 You can customize them with *-local variants:
1674 - The undocumented recursive target `uninstall-info' no longer exists.
1675 (`uninstall' is in charge of removing all possible documentation
1676 flavors, including optional formats such as dvi, ps, or info even
1677 when `no-installinfo' is used.)
1679 * Miscellaneous changes:
1681 - Automake no longer complains if input files for AC_CONFIG_FILES
1682 are specified using shell variables.
1684 - clean, distribution, or rebuild rules are normally disabled for
1685 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1686 AC_CONFIG_LINK specified using shell variables. However, if these
1687 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1688 be able to output rules anyway.
1689 (See the Automake documentation for AC_CONFIG_FILES.)
1691 - $(EXEEXT) is automatically appended to filenames of TESTS
1692 that have been declared as programs in the same Makefile.
1693 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1695 - `-Wportability' has finally been turned on by default for `gnu' and
1696 `gnits' strictness. This means, automake will complain about %-rules
1697 or $(GNU Make functions) unless you switch to `foreign' strictness or
1698 use `-Wno-portability'.
1700 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1701 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1702 $(mkdir_p) variable is still defined (to the same value as
1703 $(MKDIR_P)) but should be considered obsolete. If you are using
1704 $(mkdir_p) in some of your rules, please plan to update them to
1705 $(MKDIR_P) at some point.
1707 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1708 They still work in this release, but may be withdrawn in a future one.
1710 - Inline compilation rules for gcc3-style dependency tracking are
1713 - Automake installs a "Hello World!" example package in $(docdir).
1714 This example is used throughout the new "Autotools Introduction"
1715 chapter of the manual.
1717 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1721 * Makefile.in bloat reduction:
1723 - Inference rules are used to compile sources in subdirectories when
1724 the `subdir-objects' option is used and no per-target flags are
1725 used. This should reduce the size of some projects a lot, because
1726 Automake used to output an explicit rule for each such object in
1729 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1730 object that must be built with explicit rules. It just outputs
1731 the rules required to build the kind of object considered: either
1732 the two .o and .obj rules for usual objects, or the .lo rule for
1735 * Change to Libtool support:
1737 - Libtool tags are used with libtool versions that support them.
1738 (I.e., with Libtool 1.5 or greater.)
1740 - Automake is now able to handle setups where a libtool library is
1741 conditionally installed in different directories, as in
1744 lib_LTLIBRARIES = liba.la
1746 pkglib_LTLIBRARIES = liba.la
1748 liba_la_SOURCES = ...
1750 * Changes to aclocal:
1752 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1753 really evaluated, before it decides to include them in aclocal.m4.
1754 This solves nasty problems with conditional redefinitions of
1755 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1756 *.m4 files to be included in any project using these macros.
1757 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1758 most famous instance of this bug.)
1760 - Do not complain about missing conditionally AC_REQUIREd macros
1761 that are not actually used. In 1.8.x aclocal would correctly
1762 determine which of these macros were really needed (and include
1763 only these in the package); unfortunately it would also require
1764 all of them to be present in order to run. This created
1765 situations were aclocal would not work on a tarball distributing
1766 all the macros it uses. For instance running aclocal on a project
1767 containing only the subset of the Gettext macros in use by the
1768 project did not work, because gettext conditionally requires other
1771 * Portability improvements:
1773 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1774 tar-pax. The new option filename-length-max=99 helps diagnosing
1775 filenames that are too long for tar-v7. (PR/414)
1777 - Variables augmented with `+=' are now automatically flattened (i.e.,
1778 trailing backslashes removed) and then wrapped around 80 columns
1779 (adding trailing backslashes). In previous versions, a long series
1785 would result in a single-line definition of VAR that could possibly
1786 exceed the maximum line length of some make implementations.
1788 Non-augmented variables are still output as they are defined in
1793 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1794 Works the same as the old Fortran 77 implementation; just replace
1795 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1796 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1798 - Support for conditional _LISP.
1800 - Support for conditional -hook and -local rules (PR/428).
1802 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1804 - Automake will not write any Makefile.ins after the first error it
1805 encounters. The previous Makefile.ins (if any) will be left in
1806 place. (Warnings will not prevent output, but remember they can
1807 be turned into errors with -Werror.)
1809 - The restriction that SUBDIRS must contain direct children is gone.
1812 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1813 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1815 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1817 Bugs fixed in 1.8.5:
1819 * Long-standing bugs:
1821 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1822 so that `make distclean' and `make maintainer-clean' can work.
1824 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1826 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1828 - Polish diagnostic when no input file is found.
1830 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1832 Bugs fixed in 1.8.4:
1834 * Long-standing bugs:
1836 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1837 overridden by the user.
1839 - Honor PATH_SEPARATOR in various places of the Automake package, for
1842 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1845 - Fix install-sh so it can install the `mv' binary... using `mv'.
1847 - Fix tru64 dependency tracking for libtool objects.
1849 - Work around Exuberant Ctags when creating a TAGS files in a directory
1850 without files to scan but with subdirectories to include.
1852 * Bugs introduced by 1.8:
1854 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1855 not defined in the same conditions as the _LDADD that uses it.
1857 - Do not warn when JAVAROOT is overridden, this is legitimate.
1859 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1861 Bugs fixed in 1.8.3:
1863 * Long-standing bugs:
1865 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1866 or any of the other *dir variables contain a space.
1868 Please note that Automake does not and cannot support spaces in
1869 filenames that are involved during the build. This change affects
1870 only installation paths, so that `make install' does not bomb out
1871 in packages configured with
1872 ./configure --prefix '/c/Program Files'
1874 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1875 POSIXLY_CORRECT is set.
1877 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1878 since Autoconf 2.54, which defines LIBOBJS itself.
1880 - Fix a potential (but unlikely) race condition in parallel elisp
1881 builds. (Introduced in 1.7.3.)
1883 - Do not assume that users override _DEPENDENCIES in all conditions
1884 where Automake will try to define them.
1886 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1887 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1890 This fix also affects the $(mkdir_p) variable defined since
1891 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1892 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1894 - Secure temporary directory creation in `make distcheck'. (PR/413)
1896 - Do not generate two build rules for `parser.h' when the
1897 parser appears in two different conditionals.
1899 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1900 checking. Usually ./configure will not pick this shell; so this
1901 fix only helps cases where the shell is forced to /bin/sh.
1903 * Bugs introduced by 1.8:
1905 - In some situations (hand-written `m4_include's), aclocal would
1906 call the `File::Spec->rel2abs' method, which was only introduced
1907 in Perl 5.6. This new version reestablish support Perl 5.005.
1909 It is likely that the next major Automake releases will require at
1910 least Perl 5.6. Consider upgrading your development environment
1911 if you are still using the five-year-old Perl 5.005.
1913 - Automake would sometimes fail to define rules for targets listed
1914 in variables defined in multiple conditions. For instance on
1920 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1921 `b.$(OBJEXT): b.c' rule.
1923 * New sections in manual:
1925 - Third-Party Makefiles: how to interface third party Makefiles.
1926 - Upgrading: upgrading packages to newer Automake versions.
1927 - Multiple Outputs: handling tools that produce many outputs.
1929 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1933 * A (well known) portability bug slipped in the changes made to
1934 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1935 install anything on Tru64.
1937 * Fix install rules for conditionally built python files. (This never
1940 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1944 * Bugs introduced by 1.8:
1946 - Fix Config.pm import error with old Perl versions (at least
1947 5.005_03). One symptom is that aclocal could not find its macro
1950 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1951 created by `make install' are always world readable, even if the
1952 installer happens to have an overly restrictive umask (e.g. 077).
1953 This was a mistake and has been reverted. There are at least two
1954 reasons why we must not use `-m 0755':
1955 - it causes special bits like SGID to be ignored,
1956 - it may be too restrictive (some setups expect 775 directories).
1958 - Fix aclocal to honor definitions located in files which have been
1959 m4_included manually. aclocal 1.8 had been updated to check
1960 m4_included files for new requirements, but forgot that these
1961 m4_included files can also provide new definitions.
1963 Note that if you have such a setup, we recommend you get rid of
1964 it. In the past, there was a reason to m4_include files manually:
1965 aclocal used to duplicate entire M4 files into aclocal.m4, even
1966 files that were distributed. Some packages were therefore
1967 m4_including the distributed file directly, and playing some
1968 tricks to ensure aclocal would not copy that file to aclocal.m4,
1969 in order to limit the amount of duplication. Since aclocal 1.8.x
1970 will precisely output m4_includes for local M4 files, we recommend
1971 that you clean up your setup, removing all manual m4_includes and
1972 letting aclocal output them.
1974 - Output detailed menus in the Info version if the Automake manual,
1975 so that Emacs can locate the indexes.
1977 - configure.ac and configure were listed twice in DIST_COMMON (an
1978 internal variable where Automake lists configury files to
1979 distribute). This was harmless, but unaesthetic.
1981 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1982 This was an issue only in the Automake package itself, not in
1985 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1986 DEST:SRC. This was wrong, as some packages do
1987 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1990 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1991 argument. This caused two kinds of failures:
1992 - Rules installing data in a conditionally defined directory
1993 failed when that directory was undefined. In this case no
1994 argument was supplied.
1995 - `make installdirs' failed, because several directories were
1996 passed to $(mkdir_p). This was an issue only on platform
1997 were $(mkdir_p) is implemented with `install-sh -d'.
1998 $(mkdir_p) as been changed to accept 0 or more arguments, as
2001 * Long-standing bugs:
2003 - Fix an unexpected diagnostic occurring when users attempt
2004 to override some internal variables that Automake appends to.
2006 - aclocal now scans configure.ac for macro definitions (PR/319).
2008 - Fix a portability issue with OSF1/Tru64 Make. If a directory
2009 distributes files which are outside itself (this usually occurs
2010 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
2011 from a parent package), then `make distcheck' fails due to an
2012 optimization performed by OSF1/Tru64 Make in its VPATH handling.
2013 (tests/subpkg2.test failure)
2015 - Fix another portability issue with Sun and OSF1/Tru64 Make.
2016 In a VPATH-build configuration, `make install' would install
2017 nobase_ files to wrong locations.
2019 - Fix a Perl `uninitialized value' diagnostic occurring when
2020 automake complains that a Texinfo file does not have a
2021 @setfilename statement.
2023 - Erase config.status.lineno during `make distclean'. This file
2024 can be created by config.status. Automake already knew about
2025 configure.lineno, but forgot config.status.lineno.
2027 - Distribute all files, even those which are built and installed
2028 conditionally. This change affects files listed in conditionally
2029 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
2030 as well as those listed in conditionally defined dist_*_DATA,
2031 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
2033 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
2034 doesn't conform to POSIX.
2036 - Normalize help strings for configure variables and options added
2041 - Check for python2.4 in AM_PATH_PYTHON.
2043 * Spurious failures in test suite:
2045 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
2046 tests/ltconv.test: fix failures with CVS Libtool.
2047 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
2048 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
2049 fix failures with old Texinfo versions.
2051 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2057 - The NEWS file is more verbose.
2061 - Autoconf 2.58 or greater is required.
2065 - Default source file names in the absence of a _SOURCES declaration
2066 are made by removing any target extension before appending `.c', so
2067 to make the libtool module `foo.la' from `foo.c', you only need to
2070 lib_LTLIBRARIES = foo.la
2071 foo_la_LDFLAGS = -module
2073 For backward compatibility, foo_la.c will be used instead of
2074 foo.c if this file exists or is the explicit target of a rule.
2075 However -Wobsolete will warn about this deprecated naming.
2077 - AR's `cru' flags are now set in a global ARFLAGS variable instead
2078 of being hard-coded in each $(AR) invocation, so they can be
2079 substituted from configure.ac. This has been requested by people
2080 dealing with non-POSIX ar implementations.
2082 - New warning option: -Woverride. This will warn about any user
2083 target or variable definitions which override Automake
2086 - Texinfo rules back up and restore info files when makeinfo fails.
2088 - Texinfo rules now support the `html' target.
2089 Running this requires Texinfo 4.0 or greater.
2091 `html' is a new recursive target, so if your package mixes
2092 hand-crafted `Makefile.in's with Automake-generated
2093 `Makefile.in's, you should adjust the former to support (or
2094 ignore) this target so that `make html' recurses successfully. If
2095 you had a custom `html' rule in your `Makefile.am', it's better to
2096 rename it as `html-local', otherwise your rule will override
2097 Automake's new rule (you can check that by running `automake
2098 -Woverride') and that will stop the recursion to subdirectories.
2100 Last but not least, this `html' rule is declared PHONY, even when
2101 overridden. Fortunately, it appears that few packages use a
2102 non-PHONY `html' rule.
2104 - Any file which is m4_included from configure.ac will appear as a
2105 configure and Makefile.in dependency, and will be automatically
2108 - The rules for rebuilding Makefiles and Makefile.ins will now
2109 rebuild all Makefiles and all Makefile.ins at once when one of
2110 configure's dependencies has changed. This is considerably faster
2111 than previous implementations, where config.status and automake
2112 were run separately in each directory (this still happens when you
2113 change a Makefile.am locally, without touching configure.ac or
2114 friends). Doing this also solves a longstanding issue: these
2115 rebuild rules failed to work when adding new directories to the
2116 tree, forcing you to run automake manually.
2118 - For similar reasons, the rules to rebuild configure,
2119 config.status, and aclocal.m4 are now defined in all directories.
2120 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
2121 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
2122 should better define them in all directories. This is easily done
2123 using an AC_SUBST (make sure you prefix these dependencies with
2124 $(top_srcdir) since this variable will appear at different
2125 levels of the build tree).
2127 - aclocal will now use `m4_include' instead of copying local m4
2128 files into aclocal.m4. (Local m4 files are those you ship with
2129 your project, other files will be copied as usual.)
2131 Because m4_included files are automatically distributed, it means
2132 for most projects there is no point in EXTRA_DISTing the list of
2133 m4 files which are used. (You can probably get rid of
2134 m4/Makefile.am if you had one.)
2136 - aclocal will avoid touching aclocal.m4 when possible, so that
2137 Autom4te's cache isn't needlessly invalidated. This behavior can
2138 be switched off with the new `--force' option.
2140 - aclocal now uses Autoconf's --trace to detect macros which are
2141 actually used and will no longer include unused macros simply
2142 because they where mentioned. This was often the case for macros
2143 called conditionally.
2145 - New options no-dist and no-dist-gzip.
2147 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2148 py-compile, and ylwrap, now all understand --version and --help.
2150 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2151 links as part of the distclean target and including source files in
2154 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2155 argument. The latter can be used to override the default behavior
2156 (which is to abort).
2158 - Automake will exit with $? = 63 on version mismatch. (So does
2159 Autoconf 2.58) missing knows this, and in this case it will
2160 emulate the tools as if they were absent. Because older versions
2161 of Automake and Autoconf did not use this exit code, this change
2162 will only be useful in projects generated with future versions of
2165 - When using AC_CONFIG_FILES with multiple input files, Automake
2166 generates the first ".in" input file for which a ".am" exists.
2167 (Former versions would try to use only the first input file.)
2169 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2170 idiom to disable byte-compilation of lisp_LISP files, it is
2171 recommended that you switch to using lisp_DATA. Note that
2172 this is not strictly equivalent: lisp_DATA will install elisp
2173 files even if emacs is not installed, while *_LISP do not
2174 install anything unless emacs is found.
2176 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2177 available. This selection is achieved through the Makefile
2178 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2179 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2180 `$(install_sh) -m 0755 -d'.
2184 - Because `mkdir -p' is available on most platforms, and we can use
2185 `install-sh -d' when it is not, the use of the mkinstalldirs
2186 script is being phased out. `automake --add-missing' no longer
2187 installs it, and if you remove mkinstalldirs from your package,
2188 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2190 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2191 gettextize and autopoint will install it when needed. Automake
2192 will continue to define the $(mkinstalldirs) and to distribute
2193 mkinstalldirs when this script is in the source tree.
2195 - AM_PROG_CC_STDC is now empty. The content of this macro was
2196 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2197 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2198 renaming should be safe, even if you have to support several,
2199 versions of Automake, because AC_PROG_CC defines this variable
2200 since Autoconf 2.54.)
2202 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2203 variable to override the aclocal.m4 dependencies computed
2204 (inaccurately) by older versions of Automake. Because Automake
2205 now tracks configure's m4 dependencies accurately (see m4_include
2206 above), the use of ACLOCAL_M4_SOURCES should be considered
2207 obsolete and will be flagged as such when running `automake
2212 - Defining programs conditionally using Automake conditionals no
2213 longer leads to a combinatorial explosion. The following
2214 construct used to be troublesome when used with dozens of
2229 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2231 - Due to implementation constraints, previous versions of Automake
2232 proscribed multiple conditional definitions of some variables
2242 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2243 This restriction has been lifted, and these variables now
2244 support multiple conditional definitions as do other variables.
2246 - Cleanup the definitions of $(distdir) and $(top_distdir).
2247 $(top_distdir) now points to the root of the distribution
2248 directory created during `make dist', as it did in Automake 1.4,
2249 not to the root of the build tree as it did in intervening
2250 versions. Furthermore these two variables are now only defined in
2251 the top level Makefile, and passed to sub-directories when running
2254 - The --no-force option now correctly checks the Makefile.in's
2255 dependencies before deciding not to update it.
2257 - Do not assume that make files are called Makefile in cleaning rules.
2259 - Update .info files in the source tree, not in the build tree. This
2260 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2261 used to update these files in the build tree (previous versions did
2262 it in the source tree too), and it caused several problems, varying
2263 from mere annoyance to portability issues.
2265 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2266 when --add-missing and --force-missing are used. For backward
2267 compatibility --add-missing will continue to install COPYING (in
2268 `gnu' strictness) when none of these three files exist, but this
2269 use is deprecated: you should better choose a license yourself and
2270 install it once for all in your source tree (and in your code
2273 - Fix ylwrap so that it does not overwrite header files that haven't
2274 changed, as the inline rule already does.
2276 - User-defined rules override automake-defined rules for the same
2277 targets, even when rules do not have commands. This is not new
2278 (and was documented), however some of the automake-generated
2279 rules have escaped this principle in former Automake versions.
2280 Rules for the following targets are affected by this fix:
2282 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2283 info, info-am, install-data-am, install-exec-am, install-info,
2284 install-info-am, install-man, installcheck-am, maintainer-clean,
2285 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2286 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2288 Practically it means that an attempt to supplement the dependencies
2289 of some target, as in
2291 clean: my-clean-rule
2293 will now *silently override* the automake definition of the
2294 rule for this target. Running `automake -Woverride' will diagnose
2295 all such overriding definitions.
2297 It should be noted that almost all of these targets support a *-local
2298 variant that is meant to supplement the automake-defined rule
2299 (See node `Extending' in the manual). The above rule should
2302 clean-local: my-clean-rule
2304 These *-local targets have been documented since at least
2305 Automake 1.2, so you should not fear the change if you have
2306 to support multiple automake versions.
2310 - The Automake manual is now distributed under the terms of the GNU FDL.
2312 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2314 - core dumps are no longer removed by the cleaning rules. There are
2315 at least three reasons for this:
2316 1. These files should not be created by any build step,
2317 so their removal do not fit any of the cleaning rules.
2318 Actually, they may be precious to the developer.
2319 2. If such file is created during a build, then it's clearly a
2320 bug Automake should not hide. Not removing the file will
2321 cause `make distcheck' to complain about its presence.
2322 3. Operating systems have different naming conventions for
2323 core dump files. A core file on one system might be a
2324 completely legitimate data file on another system.
2326 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2327 defined by Automake. This means that any definition in the
2328 environment will be used, unless overridden in the Makefile.am or
2329 on the command line. The old behavior, where these variables were
2330 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2331 AC_ARG_VARing each variable from configure.ac.
2333 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2334 documented. (The is not a new feature, these variables have
2335 been there since at least Automake 1.4.)
2337 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2339 Bugs fixed in 1.7.9:
2340 * Fix install-strip to work with nobase_ binaries.
2341 * Fix renaming of #line directives in ylwrap.
2342 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2344 Bugs fixed in 1.7.8:
2345 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2346 * Fix detection of Debian's install-info, broken since version 1.5.
2347 (Debian bug #213524).
2348 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2349 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2351 Bugs fixed in 1.7.7:
2352 * The implementation of automake's --no-force option is unreliable,
2353 so this option is ignored in this version. A real fix will appear in
2354 Automake 1.8. (Debian Bug #206299)
2355 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2356 argument is given. (PR/399)
2357 * Do not warn about leading `_' in variable names, even with -Wportability.
2358 * Support user redefinitions of TEXINFO_TEX.
2359 * depcomp: support AIX Compiler version 6.
2360 * Fix missing rebuilds during `make dist' with BSD make.
2361 (Could produce tarballs containing out-of-date files.)
2362 * Resurrect multilib support.
2363 * Noteworthy manual updates:
2364 - Extending aclocal: how to write m4 macros that won't trigger warnings
2366 - A Shared Library: Rewrite and split into subsections.
2368 Bugs fixed in 1.7.6:
2369 * Fix depcomp's icc mode for ICC 7.1.
2370 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2371 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2372 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2373 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2374 * Remove Latin-1 characters from elisp-comp.
2375 * Update the manual's @dircategory to match the Free Software Directory.
2377 Bugs fixed in 1.7.5:
2378 * Update install-sh's license to remove an advertising clause.
2379 (Debian bug #191717)
2380 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2381 that caused invalid Makefile.ins to be generated.
2382 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2383 * New FAQ entry: renamed objects.
2385 Bugs fixed in 1.7.4:
2386 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2387 the Emacs implementation)
2388 * Fix output of aclocal.m4 dependencies in subdirectories.
2389 * Use `mv -f' instead of `mv' in fastdep rules.
2390 * Upgrade mdate-sh to work on OS/2.
2391 * Don't byte-compile elisp files when ELCFILES is set empty.
2392 (this documented feature was broken by 1.7.3)
2393 * Diagnose trailing backslashes on last line of Makefile.am.
2394 * Diagnose whitespace following trailing backslashes.
2395 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2396 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2398 * `make install' will build `BUILT_SOURCES' first.
2399 * Minor documentation fixes.
2401 Bugs fixed in 1.7.3:
2402 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2403 * Query distutils for `pythondir' and `pythonexecdir', instead of
2404 using an hardcoded path. This should allow builds on 64-bit
2405 distributions that usually use lib64/ instead of lib/.
2406 * AM_PATH_PYTHON will also search for python2.3.
2407 * elisp files are now built all at once instead of one by one. Besides
2408 incurring a speed-up, this is required to support interdependent elisp files.
2409 * Support for DJGPP:
2410 - `make distcheck' will now work in `_inst/' and `_build' instead
2411 of `=inst/' and `=build/'
2412 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2413 - install/uninstall `*.i[0-9][0-9]'-style info files
2414 - more changes that affect only the Automake package (not its output)
2415 * Fix some incompatibilities with upcoming perl-5.10.
2416 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2417 PACKAGE and VERSION.
2419 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2420 is troublesome with gcc and Solaris compilers. (PR/385)
2421 - makedepend mode: work with Libtool. (PR/385 too)
2423 * better support for unusual gettext setups, such as multiple po/ directories
2425 - Flag missing po/ and intl/ directories as warnings, not errors.
2426 - Disable these warnings if po/ does not exist.
2427 * Noteworthy manual updates:
2429 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2431 - Document `AM_YFLAGS = -d'. (PR/382)
2433 Bugs fixed in 1.7.2:
2434 * Fix installation and uninstallation of Info files built in subdirectories.
2435 * Do not run `./configure --with-included-gettext' during `make distcheck'
2436 if AM_GNU_GETTEXT([external]) is used.
2437 * Correctly uninstall renamed man pages.
2438 * Do not strip escaped newline in variables defined in one condition
2439 and augmented in another condition.
2440 * Fix ansi2knr rules for LIBOBJS sources.
2441 * Clean all known Texinfo index files, not only those which appear to
2442 be used, because we cannot know which indexes are used in included files.
2443 (PR/375, Debian Bug #168671)
2444 * Honor only the first @setfilename seen in a Texinfo file.
2445 * Treat "required file X not found" diagnostics as errors (exit status 1).
2446 * Don't complain that a required file is not found when it is a Makefile
2448 * Don't use single suffix inference rules when building `.info'-less
2449 Info files, for the sake of Solaris make.
2450 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2451 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2452 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2453 * Fix building of deansified files from subdirectories. (PR/370)
2454 * Add missing `fi' in the .c->.obj rules.
2455 * Improve install-sh to work even when names contain spaces or certain
2456 (but not all) shell metachars.
2457 * Fix the following spurious failures in the test suite:
2458 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2459 * Noteworthy manual updates:
2460 - Augment the section about BUILT_SOURCES.
2461 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2463 Bugs fixed in 1.7.1:
2464 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2466 * Aclocal should now recognize macro names containing parentheses, e.g.
2467 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2468 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2470 * Install Python files even if they were built. (PR/369)
2471 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2472 version might not be defined in the latter. (PR/358)
2473 * Reorder arguments passed to a couple of commands, so things works
2474 when POSIXLY_CORRECT=1.
2475 * Fix a regex that can cause Perl to segfault on large input.
2477 * Fix distribution of packages that have some sources defined conditionally,
2478 as in the `Conditional compilation using Automake conditionals' example
2480 * Fix spurious test suite failures on IRIX.
2481 * Don't report a required variable as undefined if it has been
2482 defined conditionally for the "right" conditions.
2483 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2484 `make distcheck' fails.
2485 * Fix distribution of included Makefile fragment, so we don't create
2486 spurious directories in the distribution. (PR/366)
2487 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2490 * Autoconf 2.54 is required.
2491 * `aclocal' and `automake' will no longer warn about obsolete
2492 configure macros. This is done by `autoconf -Wobsolete'.
2493 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2494 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2495 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2496 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2497 `configure.ac' for you.
2498 * Support for per-program and per-library `_CPPFLAGS'.
2499 * New `ctags' target (builds CTAGS files).
2500 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2501 (see `automake --help' or the manual for a list of them).
2502 * Honor the WARNINGS environment variable.
2503 * Omit the call to depcomp when using gcc3: call the compiler directly.
2504 * A new option, std-options, tests that programs support --help and --version
2505 when `make installcheck' is run. This is enabled by --gnits.
2506 * Texinfo rules now support the `ps' and `pdf' targets.
2507 * Info files are now created in the build directory, not the source directory.
2508 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2510 * `make distcheck' will enforce DESTDIR support by attempting
2512 * `+=' can be used in conditionals, even if the augmented variable
2513 was defined for another condition.
2514 * Makefile fragments (inserted with `include') are always distributed.
2515 * Use Autoconf's --trace interface to inspect configure.ac and get
2516 a more accurate view of it.
2517 * Add support for extending aclocal's default macro search path
2518 using a `dirlist' file within the aclocal directory.
2519 * automake --output-dir is deprecated.
2520 * The part of the distcheck target that checks whether uninstall actually
2521 removes all installed files has been moved in a separate target,
2522 distuninstallcheck, so it can be overridden easily.
2526 * Support for AM_INIT_GETTEXT([external])
2527 * Bug fixes, including:
2528 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2529 - nobase_ programs and scripts honor --program-transform correctly.
2530 - Erase configure.lineno during `make distclean'.
2531 - Erase YACC and LEX outputs during `make maintainer-clean'.
2534 * Many bug fixes, including:
2535 - Requiring the current version works.
2536 - Fix "$@" portability issues (for Zsh).
2537 - Fix output of dummy dependency files in presence of post-processed
2539 - Don't compute dependencies in background to avoid races with libtool.
2540 - Fix handling of _OBJECTS variables for targets sharing source variables.
2541 - Check dependency mode for Java when AM_PROG_GCJ is used.
2544 * automake --output-dir is deprecated
2545 * Many bug fixes, including:
2546 - Don't choke on AM_LDFLAGS definitions.
2547 - Clean libtool objects from subdirectories.
2548 - Allow configure variables with reserved suffix and unknown prefix
2549 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2550 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2553 * Autoconf 2.52 is required.
2554 * automake no longer run libtoolize.
2555 This is the job of autoreconf (from GNU Autoconf).
2556 * `dist' generates all the archive flavors, as did `dist-all'.
2557 * `dist-gzip' generates the Gzip tar file only.
2558 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2559 explosion. Makefile.in's keep a reasonable size.
2560 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2561 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2563 * `#line' of Lex and Yacc files are properly set.
2564 * EXTRA_DIST can contain generated directories.
2565 * Support for dot-less extensions in suffix rules.
2566 * The part of the distcheck target that checks whether distclean actually
2567 cleans all built files has been moved in a separate target, distcleancheck,
2568 so it can be overridden easily.
2569 * `make distcheck' will pass additional options defined in
2570 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2571 * Fixed CDPATH portability problems, in particular for MacOS X.
2572 * Fixed handling of nobase_ targets.
2573 * Fixed support of implicit rules leading to .lo objects.
2574 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2575 * Added uninstall-hook target
2576 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2577 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2578 (Note that "pkgname" is not "tarname", see the manual for details.)
2579 It is also possible to pass a list of global Automake options as
2580 first argument to this new form of AM_INIT_AUTOMAKE.
2581 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2582 to be a real assembler.
2583 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2584 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2585 * aclocal and automake are also installed with the version number
2586 appended, and some of the install directory names have changed.
2587 This lets you have multiple versions installed simultaneously.
2588 * Support for parsers and lexers in subdirectories.
2591 * Support for `configure.ac'.
2592 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2593 * `make dist-all' is much faster.
2594 * Allows '@' AC_SUBSTs in macro names.
2595 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2596 * User-side dependency tracking. Developers no longer need GNU make
2598 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2599 * Most files are correctly handled if they appear in subdirs
2600 For instance, a _DATA file can appear in a subdir
2601 * GNU tar is no longer required for `make dist'
2602 * Added support for `dist_' and `nodist_' prefixes
2603 * Added support for `nobase_' prefix
2604 * Compiled Java support
2605 * Support for per-executable and per-library compilation flags
2609 * Added support for the Fortran 77 programming language.
2610 * Re-indexed the Automake Texinfo manual.
2611 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2612 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2613 * Support for latest autoconf, including support for objext
2614 * Can now put `.' in SUBDIRS to control build order
2615 * `include' command and `+=' support for macro assignment
2616 * Dependency tracking no long susceptible to deleted header file problem
2617 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2622 * Better Cygwin32 support
2623 * Support for suffix rules with _SOURCES variables
2624 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2625 * @LEXLIB@ no longer required when lex source seen
2626 Lex support in `missing', and new lex macro. Update your missing script.
2627 * Built-in support for assembly
2628 * aclocal gives error if `AM_' macro not found
2629 * Passed YFLAGS, not YACCFLAGS, to yacc
2630 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2631 * Dependencies computed as a side effect of compilation
2632 * Preliminary support for Java
2633 * DESTDIR support at "make install" time
2634 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2638 * Better DejaGnu support
2639 * Added no-installinfo option
2640 * Added Emacs Lisp support
2641 * Added --no-force option
2642 * Included `aclocal' program
2643 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2644 * Now uses `AM_' macro names everywhere
2645 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2646 ansi2knr now works correctly on K&R sources
2647 * Better C++, yacc, lex support
2648 * Will compute _DEPENDENCIES variables automatically if not supplied
2649 * Will interpolate $(...) and ${...} when examining contents of a variable
2650 * .deps files now in build directory, not source directory; dependency
2651 handling generally rewritten
2652 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2653 * can now put config.h into a subdir
2654 * Added dist-all target
2655 * Support for install-info program (see texinfo 3.9)
2656 * Support for "yacc -d"
2657 * configure substitutions are automatically discovered and included
2658 in generated Makefile.in
2659 * Special --cygnus mode
2660 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2661 when making distribution. Some dependencies are auto-ignored.
2662 * Changed how libraries are specified in _LIBRARIES variable
2663 * Full libtool support, from Gord Matzigkeit
2664 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2665 AM_CONFIG_HEADER handles it automatically
2666 * Texinfo output files no longer need .info extension
2667 * Added `missing' support
2669 * Conditionals in Makefile.am, from Ian Taylor
2673 * distcheck target runs install and installcheck targets
2674 * Added preliminary support for DejaGnu.
2679 * More libtool fixes from Gord Matzigkeit; libtool support is still
2681 * Added support for jm_MAINTAINER_MODE
2683 * New "distcheck" target
2687 * mkinstalldirs and mdate-sh now appear in directory specified by
2689 * Removed DIST_SUBDIRS, DIST_OTHER
2690 * AC_ARG_PROGRAM only required when an actual program exists
2691 * dist-hook target now run before distribution packaged up; idea from
2692 Dieter Baron. Other hooks exist, too.
2693 * Preliminary (unfinished) support for libtool
2694 * Added short option names.
2695 * Better "dist" support when gluing together multiple packages
2699 * Documentation updates (many from François Pinard)
2700 * strictness `normal' now renamed to `foreign'
2701 * Renamed --install-missing to --add-missing
2702 * Now handles AC_CONFIG_AUX_DIR
2703 * Now handles TESTS macro
2704 * DIST_OTHER renamed to EXTRA_DIST
2705 * DIST_SUBDIRS is deprecated
2706 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2707 * Better error messages in many cases
2708 * Program names are canonicalized
2709 * Added "check" prefix; from Gord Matzigkeit
2713 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2714 * Beginnings of a test suite
2715 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2716 * Doesn't print anything when running
2717 * Beginnings of MAINT_CHARSET support
2718 * Can specify version in AUTOMAKE_OPTIONS
2719 * Most errors recognizable by Emacs' M-x next-error
2720 * Added --verbose option
2721 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2722 configure-generated names
2723 * Required macros now distributed in aclocal.m4
2725 * --strictness=gnu is default
2729 * More sophisticated configure.in scanning; now understands ALLOCA and
2730 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2731 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2732 * CONFIG_HEADER variable now obsolete
2733 * Can handle multiple Texinfo sources
2734 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2735 * HEADERS variable no longer needed; now can put .h files directly into
2736 foo_SOURCES variable.
2737 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2738 corresponding ".in" files are included in the distribution.
2741 * Added --gnu and --gnits options
2742 * More standards checking
2744 * Cleaned up 'dist' targets
2745 * Added AUTOMAKE_OPTIONS variable and several options
2746 * Now scans configure.in to get some information (preliminary)
2749 * Works with Perl 4 again
2752 * Added --install-missing option.
2753 * Pretty-prints generated macros and rules
2754 * Comments in Makefile.am are placed more intelligently in Makefile.in
2755 * Generates .PHONY target
2756 * Rule or macro in Makefile.am now overrides contents of Automake file
2757 * Substantial cleanups from François Pinard
2761 * Works with Perl 4 again.
2764 * New uniform naming scheme.
2765 * --strictness option
2767 * '.c' files corresponding to '.y' or '.l' files are automatically
2769 * Many bug fixes and cleanups
2772 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2775 * Bug fixes in 'clean' code.
2776 * Now generates 'installdirs' target.
2777 * man page installation reworked.
2778 * 'make dist' no longer re-creates all Makefile.in's.
2781 * Reimplemented in Perl
2782 * Added --amdir option (for debugging)
2783 * Texinfo support cleaned up.
2784 * Automatic de-ANSI-fication cleaned up.
2785 * Cleaned up 'clean' targets.
2788 * Automatic dependency tracking
2789 * More documentation
2790 * New variables DATA and PACKAGEDATA
2791 * SCRIPTS installed using $(INSTALL_SCRIPT)
2792 * No longer uses double-colon rules
2794 * Changes in advance of internationalization
2798 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2800 This program is free software; you can redistribute it and/or modify
2801 it under the terms of the GNU General Public License as published by
2802 the Free Software Foundation; either version 2, or (at your option)
2805 This program is distributed in the hope that it will be useful,
2806 but WITHOUT ANY WARRANTY; without even the implied warranty of
2807 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2808 GNU General Public License for more details.
2810 You should have received a copy of the GNU General Public License
2811 along with this program. If not, see <http://www.gnu.org/licenses/>.