3 * Compilation and object files:
5 - If a source file is placed in a subdirectory, the corresponding compiled
6 object will *always* be put into the subdirectory named after the source
7 file, rather than in the current directory. For instance, 'src/file.c'
8 and 'src/file.f90' will be compiled to 'src/file.o', and 'sub/dir/mu.cc'
9 will be compiled to 'sub/dir/mu.o'. Put in another way, Automake 2.0
10 and later will *unconditionally* behave as older Automake versions did
11 when the 'subdir-objects' option was given.
15 - Automake used to implement an undocumented hack causing '.info' files
16 that appeared to be cleaned (by e.g. being listed in the CLEANFILES
17 variable) to also be built in the builddir rather than in the srcdir;
18 this was for backward compatibility with packages such as Texinfo,
19 which did things like:
21 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
22 DISTCLEANFILES = texinfo texinfo-* info*.info*
23 # Do not create info files for distribution.
27 in order not to distribute .info files.
29 Now that we have the 'info-in-builddir' option that explicitly causes
30 generated '.info' files to be placed in the builddir, this hack is no
31 longer necessary. We have thus removed\ it.
33 * Aclocal search path:
35 - Third-party m4 files located in the system-wide aclocal directory,
36 as well as in any directory listed in the ACLOCAL_PATH environment
37 variable, now take precedence over "built-in" Automake macros.
38 For example, assuming Automake is installed in the '/usr/local'
39 hierarchy, a definition of the AM_PROG_VALAC macro found in file
40 (say) '/usr/local/share/aclocal/my-vala.m4' should take precedence
41 over the same-named automake-provided macro, as defined in file
42 '/usr/local/share/aclocal-2.0/vala.m4'.
44 * Obsolescent features flagged:
46 - Use of the special makefile variable 'ACLOCAL_AMFLAGS' is deprecated.
47 To specify locations of extra m4 files, the 'AC_CONFIG_MACRO_DIR' or
48 'AC_CONFIG_MACRO_DIRS' (the latter introduced with autoconf 2.70)
49 should be used instead. And use of the '--install' aclocal option in
50 'ACLOCAL_AMFLAGS' has proved to be a bad idea anyway -- see automake
53 * Obsolete features removed:
55 - Support for the long-deprecated name 'configure.in' for the Autoconf
56 input file has been removed altogether. Just use the modern name
57 'configure.ac' instead.
59 - Support for the long-obsolete variable $(ACLOCAL_M4_SOURCES) has
60 been removed. It should be safe to simply remove any definition
61 of it you have in your Makefiles.
63 * Removed support for obsolete platforms:
65 - Support for automatic dependency tracking with the SGI C/C++ compilers
66 on IRIX has been removed. The SGI depmode had been reported broken
67 "in the wild" already, and we don't think investing time in debugging
68 and fixing it would have been worthwhile, especially considering that
69 SGI has last updated those compilers in 2006, and is expected to retire
70 support for them in December 2013:
71 <http://www.sgi.com/services/support/irix_mips_support.html>
73 - Support for DJGPP on MS-DOS and/or Windows 95/98/ME has been removed.
74 Note that both Cygwin and MSYS/MinGW on modern Windows versions will
75 continue to be fully supported.
77 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
79 * WARNING: Future backward-incompatibilities!
81 - Makefile recipes generated by Automake 2.0 will expect to use an
82 'rm' program that doesn't complain when called without any non-option
83 argument if the '-f' option is given (so that commands like "rm -f"
84 and "rm -rf" will act as a no-op, instead of raising usage errors).
85 This behavior of 'rm' is very widespread in the wild, and it will be
86 required in the next POSIX version:
88 <http://austingroupbugs.net/view.php?id=542>
90 Accordingly, AM_INIT_AUTOMAKE now expands some shell code that checks
91 that the default 'rm' program in PATH satisfies this requirement,
92 aborting the configure process if this is not the case. For the
93 moment, it's still possible to force the configuration process to
94 succeed even with a broken 'rm', that that will no longer be the case
97 - Automake 2.0 will require Autoconf 2.70 or later (which is still
98 unreleased at the moment of writing, but is planned to be released
99 before Automake 2.0 is).
101 - Automake 2.0 will drop support for the long-deprecated 'configure.in'
102 name for the Autoconf input file. You are advised to start using the
103 recommended name 'configure.ac' instead, ASAP.
105 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated in
106 Automake 2.0: it will raise warnings in the "obsolete" category (but
107 still no hard error of course, for compatibilities with the many, many
108 packages that still relies on that variable). You are advised to
109 start relying on the new Automake support for AC_CONFIG_MACRO_DIRS
110 instead (which was introduced in Automake 1.13).
112 - Automake 2.0 will remove support for automatic dependency tracking
113 with the SGI C/C++ compilers on IRIX. The SGI depmode has been
114 reported broken "in the wild" already, and we don't think investing
115 time in debugging and fixing is worthwhile, especially considering
116 that SGI has last updated those compilers in 2006, and retired
117 support for them in December 2013:
118 <http://www.sgi.com/services/support/irix_mips_support.html>
120 - Automake 2.0 will remove support for MS-DOS and Windows 95/98/ME
121 (support for them was offered by relying on the DJGPP project).
122 Note however that both Cygwin and MSYS/MinGW on modern Windows
123 versions will continue to be fully supported.
125 - Automake-provided scripts and makefile recipes might (finally!)
126 start assuming a POSIX shell in Automake 2.0. There still is no
127 certainty about this though: we'd first like to wait and see
128 whether future Autoconf versions will be enhanced to guarantee
129 that such a shell is always found and provided by the checks in
132 - Starting from Automake 2.0, third-party m4 files located in the
133 system-wide aclocal directory, as well as in any directory listed
134 in the ACLOCAL_PATH environment variable, will take precedence
135 over "built-in" Automake macros. For example (assuming Automake
136 is installed in the /usr/local hierarchy), a definition of the
137 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
138 should take precedence over the same-named automake-provided macro
139 (defined in '/usr/local/share/aclocal-2.0/vala.m4').
141 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
145 * Miscellaneous changes
147 - When subdir-objects is in effect, Automake will now construct
148 shorter object file names when no programs and libraries name
149 clashes are encountered. This should make the discouraged use of
150 'foo_SHORTNAME' unnecessary in many cases.
154 - Automatic dependency tracking has been fixed to work also when the
155 'subdir-object' option is used and some 'foo_SOURCES' definition
156 contains unexpanded references to make variables, as in, e.g.:
158 a_src = sources/libs/aaa
160 foo_SOURCES = $(a_src)/bar.c $(b_src)/baz.c
162 With such a setup, the created makefile fragment containing dependency
163 tracking information will be correctly placed under the directories
164 named 'sources/libs/aaa/.deps' and 'sources/bbb/.deps', rather than
165 mistakenly under directories named (literally!) '$(src_a)/.deps' and
166 '$(src_b)/.deps' (this was the first part of automake bug#13928).
168 Notice that in order to fix this bug we had to slightly change the
169 semantics of how config.status bootstraps the makefile fragments
170 required for the dependency tracking to work: rather than attempting
171 to parse the Makefiles via grep and sed trickeries only, we actually
172 invoke 'make' on a slightly preprocessed version of those Makefiles,
173 using a private target that is only meant to bootstrap the required
176 - The 'subdir-object' option no longer causes object files corresponding
177 to source files specified with an explicit '$(srcdir)' component to be
178 placed in the source tree rather than in the build tree.
180 For example, if Makefile.am contains:
182 AUTOMAKE_OPTIONS = subdir-objects
183 foo_SOURCES = $(srcdir)/foo.c $(srcdir)/s/bar.c $(top_srcdir)/baz.c
185 then "make all" will create 'foo.o' and 's/bar.o' in $(builddir) rather
186 than in $(srcdir), and will create 'baz.o' in $(top_builddir) rather
187 than in $(top_srcdir).
189 This was the second part of automake bug#13928.
191 - Installed 'aclocal' m4 macros can now accept installation directories
192 containing '@' characters (automake bug#20903)
194 - When combining AC_LIBOBJ or AC_FUNC_ALLOCA with the
195 "--disable-dependency-tracking" configure option in an out of source
196 build, the build sub-directory defined by AC_CONFIG_LIBOBJ_DIR is now
197 properly created. (automake bug#27781)
199 - The time printed by 'mdate-sh' is now using the UTC time zone to support
200 the reproducible build effort. (automake bug#20314)
202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
208 - The code has been adapted to remove a warning present since Perl
209 5.22 stating that "Unescaped left brace in regex is deprecated".
210 This warning has become an hard error in Perl 5.26 (bug#22372).
212 - The generated Makefiles do not rely on the obsolescent GZIP
213 environment variable which was used for passing arguments to
214 'gzip'. Compatibility with old versions has been
215 preserved. (bug#20132)
217 * Miscellaneous changes:
219 - Support the Windows version of the Intel C Compiler (icl) in the
220 'compile' script in the same way the (compatible) Microsoft C
221 Compiler is supported.
223 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
227 * Improvements and refactorings in the install-sh script:
229 - It has been modernized, and now makes the following assumptions
231 (1) a working 'dirname' program is available;
232 (2) the ${var:-value} shell parameters substitution works;
233 (3) the "set -f" and "set +f" shell commands work, and, respectively,
234 disable and enable shell globbing.
236 - The script implements stricter error checking, and now it complains
237 and bails out if any of the following expectations is not met:
238 (1) the options -d and -t are never used together;
239 (2) the argument passed to option -t is a directory;
240 (3) if there are two or more SOURCEFILE arguments, the
241 DESTINATION argument must be a directory.
243 * Automake-generated testsuites:
245 - The default test-driver used by the Automake-generated testsuites
246 now appends the result and exit status of each "plain" test to the
247 associated log file (automake bug#11814).
249 - The perl implementation of the TAP testsuite driver is no longer
250 installed in the Automake's scripts directory, and is instead just
251 distributed as a "contrib" addition. There should be no reason to
252 use this implementation anyway in real packages, since the awk+shell
253 implementation of the TAP driver (which is documented in the manual)
254 is more portable and has feature parity with the perl implementation.
256 - The rule generating 'test-suite.log' no longer risk incurring in an
257 extra useless "make all" recursive invocation in some corner cases
258 (automake bug#16302).
262 - Automake bug#18286: "make distcheck" could sometimes fail to detect
263 files missing from the distribution tarball, especially in those cases
264 where both the generated files and their dependencies are explicitly
265 in $(srcdir). An important example of this are *generated* makefile
266 fragments included at Automake time in Makefile.am; e.g.:
269 $(srcdir)/fragment.am: $(srcdir)/data.txt $(srcdir)/preproc.sh
270 cd $(srcdir) && $(SHELL) preproc.sh <data.txt >fragment.am
271 include $(srcdir)/fragment.am
274 If the use forgot to add data.txt and/or preproc.sh in the distribution
275 tarball, "make distcheck" would have erroneously succeeded! This issue
278 - As a consequence of the previous change, "make distcheck" will run
279 using '$(distdir)/_build/sub' as the build directory, rather than
280 simply '$(distdir)/_build' (as it was the case for Automake 1.14 and
281 earlier). Consequently, the './configure' and 'make' invocations
282 issued by the distcheck recipe now have $(srcdir) equal to '../..',
283 rather than to just '..'. Dependent and similar variables (e.g.,
284 '$(top_srcdir)') are also changed accordingly.
286 Thus, Makefiles that made assumptions about the exact values of the
287 build and source directories used by "make distcheck" will have to
288 be adjusted. Notice that making such assumptions was a bad and
289 unsupported practice anyway, since the exact locations of those
290 directories should be considered implementation details, and we
291 reserve the right to change them at any time.
293 * Miscellaneous bugs fixed:
295 - The expansion of AM_INIT_AUTOMAKE ends once again with a trailing
296 newline (bug#16841). Regression introduced in Automake 1.14.
298 - We no longer risk to use '$ac_aux_dir' before it's defined (see
299 automake bug#15981). Bug introduced in Automake 1.14.
301 - The code used to detect whether the currently used make is GNU make
302 or not (relying on the private macro 'am__is_gnu_make') no longer
303 risks causing "Arg list too long" for projects using automatic
304 dependency tracking and having a ton of source files (bug#18744).
306 - Automake tries to offer a more deterministic output for generated
307 Makefiles, in the face of the newly-introduced randomization for
308 hash keys order in Perl 5.18.
310 - In older Automake versions, if a user defined one single Makefile
311 fragment (say 'foo.am') to be included via Automake includes in
312 his main Makefile.am, and defined a custom make rule to generate that
313 file from other data, Automake used to spuriously complain with some
314 message like "... overrides Automake target '$(srcdir)/foo.am".
315 This bug is now fixed.
317 - The user can now extend the special .PRECIOUS target, the same way
318 he could already do with the .MAKE .and .PHONY targets.
320 - Some confusing typos have been fixed in the manual and in few warning
321 messages (automake bug#16827 and bug#16997).
323 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
329 - The user is no longer allowed to override the --srcdir nor the --prefix
330 configure options used by "make distcheck" (bug#14991).
332 - Fixed a gross inefficiency in the recipes for installing byte-compiled
333 python files, that was causing an O(N^2) performance on the number N of
334 files, instead of the expected O(N) performance. Note that this bug
335 was only relevant when the number of python files was high (which is
336 unusual in practice).
338 - Automake try to offer a more deterministic output for warning messages,
339 in the face of the newly-introduced randomization for hash keys order
342 - The 'test-driver' script now actually error out with a clear error
343 message on the most common invalid usages.
345 - Several spurious failures/hangs in the testsuite (bugs #14706, #14707,
346 #14760, #14911, #15181, #15237).
348 * Documentation fixes:
350 - Fixed typos in the 'fix-timestamp.sh' example script that made it
353 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
357 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
359 - The 'compile' script is now unconditionally required for all packages
360 that perform C compilation (if you are using the '--add-missing'
361 option, automake will fetch that script for you, so you shouldn't
362 need any explicit adjustment). This new behaviour is needed to avoid
363 obscure errors when the 'subdir-objects' option is used, and the
364 compiler is an inferior one that doesn't grasp the combined use of
365 both the "-c -o" options; see discussion about automake bug#13378 for
367 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
368 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
370 - The next major Automake version (2.0) will unconditionally activate
371 the 'subdir-objects' option. In order to smooth out the transition,
372 we now give a warning (in the category 'unsupported') whenever a
373 source file is present in a subdirectory but the 'subdir-object' is
374 not enabled. For example, the following usage will trigger such a
377 bin_PROGRAMS = sub/foo
378 sub_foo_SOURCES = sub/main.c sub/bar.c
380 - Automake will automatically enhance the autoconf-provided macro
381 AC_PROG_CC to force it to check, at configure time, that the
382 C compiler supports the combined use of both the '-c' and '-o'
383 options. The result of this check is saved in the cache variable
384 'am_cv_prog_cc_c_o', and said result can be overridden by
385 pre-defining that variable.
387 - The AM_PROG_CC_C_O macro can still be called, albeit that should no
388 longer be necessary. This macro is now just a thin wrapper around the
389 Automake-enhanced AC_PROG_CC. This means, among the other things,
390 that its behaviour is changed in three ways:
392 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
393 macro behind the scenes.
395 2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
396 and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
397 dynamically computed only at configure runtime (really!) from
398 the content of the '$CC' variable.
400 3. It no longer automatically AC_DEFINE the C preprocessor
401 symbol 'NO_MINUS_C_MINUS_O'.
405 - Automake can now be instructed to place '.info' files generated from
406 Texinfo input in the builddir rather than in the srcdir; this is done
407 specifying the new automake option 'info-in-builddir'. This feature
408 was requested by the developers of GCC, GDB, GNU binutils and the GNU
409 bfd library. See the extensive discussion about automake bug#11034
412 - For quite a long time, Automake has been implementing an undocumented
413 hack which ensured that '.info' files which appeared to be cleaned
414 (by being listed in the CLEANFILES or DISTCLEANFILES variables) were
415 built in the builddir rather than in the srcdir; this hack was
416 introduced to ensure better backward-compatibility with package
417 such as Texinfo, which do things like:
419 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
420 DISTCLEANFILES = texinfo texinfo-* info*.info*
421 # Do not create info files for distribution.
425 in order not to distribute generated '.info' files.
427 Now that we have the 'info-in-builddir' option that explicitly causes
428 generated '.info' files to be placed in the builddir, this hack should
429 be longer necessary, so we deprecate it with runtime warnings.
430 It will be removed altogether in Automake 2.0.
432 * Relative directory in Makefile fragments:
434 - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
435 (and their short versions, '%D%' and '%C%' respectively) can now be used
436 in an included Makefile fragment. The former is substituted with the
437 relative directory of the included fragment (compared to the top-level
438 including Makefile), and the latter with the canonicalized version of
439 the same relative directory.
442 bin_PROGRAMS = # will be updated by included Makefile fragments
443 include src/Makefile.inc
445 # in 'src/Makefile.inc':
446 bin_PROGRAMS += %reldir%/foo
447 %canon_reldir%_foo_SOURCES = %reldir%/bar.c
449 This should be especially useful for packages using a non-recursive
452 * Deprecated distribution formats:
454 - The 'shar' and 'compress' distribution formats are deprecated, and
455 scheduled for removal in Automake 2.0. Accordingly, the use of the
456 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
457 (in the 'obsolete' category), and the recipes of the Automake-generated
458 targets 'dist-shar' and 'dist-tarZ' will unconditionally display
459 (non-fatal) warnings at make runtime.
461 * New configure runtime warnings about "rm -f" support:
463 - To simplify transition to Automake 2.0, the shell code expanded by
464 AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
465 'rm' program in PATH doesn't complain when called without any
466 non-option argument if the '-f' option is given (so that commands like
467 "rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
468 If this is not the case, the configure script is aborted, to call the
469 attention of the user on the issue, and invite him to fix his PATH.
470 The checked 'rm' behavior is very widespread in the wild, and will be
471 required by future POSIX versions:
473 <http://austingroupbugs.net/view.php?id=542>
475 The user can still force the configure process to complete even in the
476 presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
477 environment variable to "yes". And the generated Makefiles should
478 still work correctly even when such broken 'rm' is used. But note
479 that this will no longer be the case with Automake 2.0 though, so, if
480 you encounter the warning, please report it to us ASAP (and try to fix
481 your environment as well).
483 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
489 - Fix a minor regression introduced in Automake 1.13.3: when two or more
490 user-defined suffix rules were present in a single Makefile.am,
491 automake would needlessly include definition of some make variables
492 related to C compilation in the generated Makefile.in (bug#14560).
494 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
498 * Documentation fixes:
500 - The documentation no longer mistakenly reports that the obsolete
501 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
502 to be removed in Automake 2.0.
506 - Byte-compilation of Emacs lisp files could fail spuriously on
507 Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
509 - If the same user-defined suffixes were transformed into different
510 Automake-known suffixes in different Makefile.am files in the same
511 project, automake could get confused and generate inconsistent
512 Makefiles (automake bug#14441).
513 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
514 and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
515 would have mistakenly placed into 'Makefile.in' rules to compile
516 "*.c" files into object files, and into 'sub/Makefile.in' rules to
517 compile "*.cc" files into object files --- rather than the other
518 way around. This is now fixed.
522 - The test cases no longer have the executable bit set. This should
523 make it clear that they are not meant to be run directly; as
524 explained in t/README, they can only be run through the custom
525 'runtest' script, or by a "make check" invocation.
527 - The testsuite has seen the introduction of a new helper function
528 'run_make', and several related changes. These serve a two-fold
531 1. Remove brittleness due to the use of "make -e" in test cases.
533 2. Seamlessly allow the use of parallel make ("make -j...") in the
534 test cases, even where redirection of make output is involved
535 (see automake bug#11413 for a description of the subtle issues
538 - Several spurious failures have been fixed (they hit especially
539 MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
540 #14498, #14499, #14500, #14501, #14517 and #14528.
542 - Some other minor miscellaneous changes and fixlets.
544 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
548 * Documentation fixes:
550 - The long-deprecated but still supported two-arguments invocation form
551 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
552 thing to do, given that support for such usage might need to remain
553 in place for an unspecified amount of time in order to cater to people
554 who want to define the version number for their package dynamically at
555 configure runtime (unfortunately, Autoconf does not yet support this
556 scenario, so we cannot delegate the work to it).
558 - The serial testsuite harness is no longer reported as "deprecated",
559 but as "discouraged". We have no plan to remove it, nor to make its
560 use cause runtime warnings.
562 - The parallel testsuite is no longer reported as "experimental"; it
563 is well tested, and should be stable now.
565 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
566 'dist-tarZ' options are obsolescent, and their use is deprecated
567 in the documentation.
569 - Other minor miscellaneous fixes and improvements; in particular,
570 some improvements in cross-references.
572 * Obsolescent features:
574 - Use of suffix-less info files (that can be specified through the
575 '@setfilename' macro in Texinfo input files) is discouraged, and
576 its use will raise warnings in the 'obsolete' category. Simply
577 use the '.info' extension for all your info files, transforming
580 @setfilename myprogram
584 @setfilename myprogram.info
586 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
587 is discouraged, and its use will raise warnings in the 'obsolete'
588 category. You are advised to simply use the '.texi' extension
593 - When the 'ustar' option is used, the generated configure script no
594 longer risks hanging during the tests for the availability of the
595 'pax' utility, even if the user running configure has a UID or GID
596 that requires more than 21 bits to be represented.
597 See automake bug#8343 and bug#13588.
599 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
600 again, as they did in Automake 1.12.x (albeit printing runtime
601 warnings in the 'obsolete' category). Removing them has turned
602 out to be a very bad idea, because it complicated distro packing
603 enormously. Making them issue fatal warnings, as we did in
604 Automake 1.13, has turned out to be a similarly very bad idea,
605 for exactly the same reason.
607 - aclocal will no longer error out if the first local m4 directory
608 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
609 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
610 a warning in the 'unsupported' category. This is done to support
611 some pre-existing real-world usages. See automake bug#13514.
613 - aclocal will no longer consider directories for extra m4 files more
614 than once, even if they are specified multiple times. This ensures
615 packages that specify both
617 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
618 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
620 will work correctly, even when the 'm4' directory contains no
621 package-specific files, but is used only to install third-party
622 m4 files (as can happen with e.g., "libtoolize --install").
623 See automake bug#13514.
625 - Analysis of make flags in Automake-generated rules has been made more
626 robust, and more future-proof. For example, in presence of make that
627 (like '-I') take an argument, the characters in said argument will no
628 longer be spuriously considered as a set of additional make options.
629 In particular, automake-generated rules will no longer spuriously
630 believe to be running in dry mode ("make -n") if run with an invocation
631 like "make -I noob"; nor will they believe to be running in keep-going
632 mode ("make -k") if run with an invocation like "make -I kool"
633 (automake bug#12554).
635 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
641 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
642 causes a clear and helpful error message, instead of obscure ones
643 (issue introduced in Automake 1.13).
645 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
651 - ylwrap renames properly header guards in generated header files
652 (*.h), instead of leaving Y_TAB_H.
654 - ylwrap now also converts header guards in implementation files
655 (*.c). Because ylwrap failed to rename properly #include in the
656 implementation files, current versions of Bison (e.g., 2.7)
657 duplicate the generated header file in the implementation file.
658 The header guard then protects the implementation file from
659 duplicate definitions from the header file.
661 * Version requirements:
663 - Autoconf 2.65 or greater is now required.
665 - The rules to build PDF and DVI output from Texinfo input now
666 require Texinfo 4.9 or later.
670 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
671 option) has been removed. See discussion about automake bug#11034
672 for more background: <https://debbugs.gnu.org/11034>.
674 - The deprecated aclocal option '--acdir' has been removed. You
675 should use the options '--automake-acdir' and '--system-acdir'
676 instead (which have been introduced in Automake 1.11.2).
678 - The following long-obsolete m4 macros have been removed:
680 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
681 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
682 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
683 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
684 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
685 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
686 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
687 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
688 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
689 of the now-removed automatic de-ANSI-fication
692 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
694 - Use of the long-deprecated two- and three-arguments invocation forms
695 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
696 though (albeit with a warning in the 'obsolete' category), to cater
697 for people who want to define the version number for their package
698 dynamically (e.g., from the current VCS revision). We'll have to
699 continue this support until Autoconf itself is fixed to allow better
700 support for such dynamic version numbers.
702 * Elisp byte-compilation:
704 - The byte compilation of '.el' files into '.elc' files is now done
705 with a suffix rule. This has simplified the compilation process, and
706 more importantly made it less brittle. The downside is that emacs is
707 now invoked once for each '.el' files, which cause some noticeable
708 slowdowns. These should however be mitigated on multicore machines
709 (which are becoming the norm today) if concurrent make ("make -j")
712 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
713 files in the same subdirectory; for example, byte-compiling of file
714 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
715 'foo.elc'. This behaviour is backward-incompatible with older
716 Automake versions, but it is more natural and more sane. See also
719 - The Emacs invocation performing byte-compilation of '.el' files honors
720 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
721 one is developer-reserved and the latter one user-reserved.
723 - The 'elisp-comp' script, once provided by Automake, has been rendered
724 obsoleted by the just-described changes, and thus removed.
726 * Changes to Automake-generated testsuite harnesses:
728 - The parallel testsuite harness (previously only enabled by the
729 'parallel-tests' option) is the default one; the older serial
730 testsuite harness will still be available through the use of the
731 'serial-tests' option (introduced in Automake 1.12).
733 - The 'color-tests' option is now unconditionally activated by default.
734 In particular, this means that testsuite output is now colorized by
735 default if the attached terminal seems to support ANSI escapes, and
736 that the user can force output colorization by setting the variable
737 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
738 for backward-compatibility, although it's a handled as a no-op now.
740 * Silent rules support:
742 - Support for silent rules is now always active in Automake-generated
743 Makefiles. So, although the verbose output is still the default,
744 the user can now always use "./configure --enable-silent-rules" or
745 "make V=0" to enable quieter output in the package he's building.
747 - The 'silent-rules' option has now become a no-op, preserved for
748 backward-compatibility only. In particular, its use no longer
749 disables the warnings in the 'portability-recursive' category.
753 - The rules to build PDF and DVI files from Texinfo input now require
754 Texinfo 4.9 or later.
756 - The rules to build PDF and DVI files from Texinfo input now use the
757 '--build-dir' option, to keep the auxiliary files used by texi2dvi
758 and texi2pdf around without cluttering the build directory, and to
759 make it possible to run the "dvi" and "pdf" recipes in parallel.
761 * Automatic remake rules and 'missing' script:
763 - The 'missing' script no longer tries to update the timestamp of
764 out-of-date files that require a maintainer-specific tool to be
765 remade, in case the user lacks such a tool (or has a too-old version
766 of it). It just gives a useful warning, and in some cases also a
767 tip about how to obtain such a tool.
769 - The missing script has thus become useless as a (poor) way to work
770 around the sketched-timestamps issues that can happen for projects
771 that keep generated files committed in their VCS repository. Such
772 projects are now encouraged to write a custom "fix-timestamps.sh"
773 script to avoid such issues; a simple example is provided in the
774 "CVS and generated files" chapter of the automake manual.
778 - The user can now define his own recursive targets that recurse
779 in the directories specified in $(SUBDIRS). This can be done by
780 specifying the name of such targets in invocations of the new
781 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
785 - Any failure in the recipe of the "tags", "ctags", "cscope" or
786 "cscopelist" targets in a subdirectory is now propagated to the
787 top-level make invocation.
789 - Tags are correctly computed also for files in _SOURCES variables that
790 only list files with non-standard suffixes (see automake bug#12372).
792 * Improvements to aclocal and related rebuilds rules:
794 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
795 are now traced by aclocal, and can be used to declare the local m4
796 include directories. Formerly, one had to specify it with an explicit
797 '-I' option to the 'aclocal' invocation.
799 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
800 Automake versions will warn about its use, and later version will
801 remove support for it altogether.
803 * The depcomp script:
805 - Dropped support for libtool 1.4.
807 - Various internal refactorings. They should cause no visible change,
808 but the chance for regression is there anyway, so please report any
809 unexpected or suspicious behaviour.
811 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
812 This should cause no problem, since icc 8.0 has been released in
813 December 2003 -- almost nine years ago.
815 - Support for tcc (the Tiny C Compiler) has been improved, and is now
816 handled through a dedicated 'tcc' mode.
820 - ylwrap generates header guards with a single '_' for series of non
821 alphabetic characters, instead of several. This is what Bison >=
824 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
826 Bugs fixed in 1.12.6:
828 * Python-related bugs:
830 - The default installation location for python modules has been improved
831 for Python 3 on Debian and Ubuntu systems, changing from:
833 ${prefix}/lib/python3/dist-packages
837 ${prefix}/lib/python3.x/site-packages
839 This change should ensure modules installed using the default ${prefix}
840 "/usr/local" are found by default by system python 3.x installations.
841 See automake bug#10227.
843 - Python byte-compilation supports the new layout mandated by PEP-3147,
844 with its __pycache__ directory (automake bug#8847).
846 * Build system issues:
848 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
849 Automake's own build system works correctly again (bug introduced
854 - The Vala-related tests has been changed to adjust to the removal of
855 the 'posix' profile in the valac compiler. See automake bug#12934
858 - Some spurious testsuite failures related to older tools and systems
861 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
867 - The AM_PROG_VALAC macro has been enhanced to takes two further
868 optional arguments; it's signature now being
870 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
871 [ACTION-IF-NOT-FOUND])
873 - By default, AM_PROG_VALAC no longer aborts the configure invocation
874 if the Vala compiler found is too old, but simply prints a warning
875 messages (as it did when the Vala compiler was not found). This
876 should avoid unnecessary difficulties for end users that just want
877 to compile the unmodified, distributed Vala-generated C sources,
878 but happens to have an old Vala compiler in their PATH. This fixes
881 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
882 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
883 This is a better default, because with it a triggered makefile rule
884 invoking a Vala compilation will clearly fail with an informative error
885 message like "valac: command not found", rather than silently, with
886 the error possibly going unnoticed or triggering harder-to-diagnose
887 fallout failures in later steps.
889 * Miscellaneous changes:
891 - automake and aclocal no longer honours the 'perllibdir' environment
892 variable. That had always been intended only as an hack required in
893 the testsuite, not meant for any use beyond that.
895 Bugs fixed in 1.12.5:
897 * Long-standing bugs:
899 - Automake no longer generates spurious remake rules invoking autoheader
900 to regenerate the template corresponding to header files specified after
901 the first one in AC_CONFIG_HEADERS (automake bug#12495).
903 - When wrapping Microsoft tools, the 'compile' script falls back to
904 finding classic 'libname.a' style libraries when 'name.lib' and
905 'name.dll.lib' aren't available.
907 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
911 * Warnings and deprecations:
913 - Warnings in the 'obsolete' category are enabled by default both in
914 automake and aclocal.
916 * Miscellaneous changes:
918 - Some testsuite weaknesses and spurious failures have been fixed.
920 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
924 * Miscellaneous changes:
926 - The '.m4' files provided by Automake no longer define serial numbers.
927 This should cause no difference in the behaviour of aclocal though.
929 - Some testsuite weaknesses and spurious failures have been fixed.
931 - There is initial support for automatic dependency tracking with the
932 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
934 Bugs fixed in 1.12.3:
936 * Long-standing bugs:
938 - Instead of renaming only self-references of files (typically for
939 #lines), ylwrap now also renames references to the other generated
940 files. This fixes support for GLR and C++ parsers from Bison (PR
941 automake/491 and automake bug#7648): 'parser.c' now properly
942 #includes 'parser.h' instead of 'y.tab.h'.
944 - Generated files unknown to ylwrap are now preserved. This fixes
945 C++ support for Bison (automake bug#7648): location.hh and the
946 like are no longer discarded.
948 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
952 * Warnings and deprecations:
954 - Automake now issues a warning (in the 'portability' category) if
955 'configure.in' is used instead of 'configure.ac' as the Autoconf
956 input file. Such a warning will also be present in the next
957 Autoconf version (2.70).
961 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
962 order (as done by the other recursive rules), rather than in the
963 inverse order. They used to do that in order to work a round a
964 limitation in an older implementation of the automatic dependency
965 tracking support, but that limitation had been lifted years ago
966 already, when the automatic dependency tracking based on side-effects
967 of compilation had been introduced.
969 - Cleaning rules for compiled objects (both "plain" and libtool) work
970 better when subdir objects are involved, not triggering a distinct
971 'rm' invocation for each such object. They do so by removing *any*
972 compiled object file that is in the same directory of a subdir
973 object. See automake bug#10697.
975 * Silent rules support:
977 - A new predefined $(AM_V_P) make variable is provided; it expands
978 to a shell conditional that can be used in recipes to know whether
979 make is being run in silent or verbose mode.
981 Bugs fixed in 1.12.2:
983 * SECURITY VULNERABILITIES!
985 - The 'distcheck' recipe no longer grants temporary world-write
986 permissions on the extracted distdir. Even if such rights were
987 only granted for a vanishingly small time window, the implied
988 race condition proved to be enough to allow a local attacker
989 to run arbitrary code with the privileges of the user running
990 "make distcheck". This is CVE-2012-3386.
992 * Long-standing bugs:
994 - The "recheck" targets behaves better in the face of build failures
995 related to previously failed tests. For example, if a test is a
996 compiled program that must be rerun by "make recheck", and its
997 compilation fails, it will still be rerun by further "make recheck"
998 invocations. See automake bug#11791.
1000 * Bugs introduced by 1.12.1:
1002 - Automake provides once again the '$(mkdir_p)' make variable and the
1003 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
1004 for better backward-compatibility.
1006 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1010 * New supported languages:
1012 - Support for Objective C++ has been added; it should work similarly to
1013 the support for Objective C.
1015 * Deprecated obsolescent features:
1017 - Use of the long-deprecated two- and three-arguments invocation forms
1018 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
1019 category. Starting from some future major Automake release (likely
1020 post-1.13), such usages will no longer be allowed.
1022 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
1023 now deprecated (its use triggers a warning in the 'obsolete' category).
1024 It will be removed in the next major Automake release (1.13).
1026 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
1027 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
1028 m4 macro are deprecated, eliciting a warning in the 'obsolete'
1031 * Miscellaneous changes:
1033 - The Automake test cases now require a proper POSIX-conforming shell.
1034 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
1035 be accepted. In most cases, the user shouldn't have to specify such
1036 POSIX shell explicitly, since it will be looked up at configure time.
1037 Still, when this lookup fails, or when the user wants to override its
1038 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
1039 to the shell that will be used to run the Automake test cases).
1041 Bugs fixed in 1.12.1:
1043 * Bugs introduced by 1.12:
1045 - Several weaknesses in Automake's own build system and test suite
1048 * Bugs introduced by 1.11.3:
1050 - When given non-option arguments, aclocal rejects them, instead of
1051 silently ignoring them.
1053 * Long-standing bugs:
1055 - When the 'color-tests' option is in use, forcing of colored testsuite
1056 output through "AM_COLOR_TESTS=always" works even if the terminal is
1057 a non-ANSI one, i.e., if the TERM environment variable has a value of
1060 - Several inefficiencies and poor performances in the implementation
1061 of the parallel-tests 'check' and 'recheck' targets have been fixed.
1063 - The post-processing of output "#line" directives done the ylwrap
1064 script is more faithful w.r.t. files in a subdirectory; for example,
1065 if the processed file is "src/grammar.y", ylwrap will correctly
1066 produce directives like:
1067 #line 7 "src/grammar.y"
1072 * Bugs with new Perl versions:
1074 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
1076 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1080 * Obsolete features removed:
1082 - The never documented nor truly used script 'acinstall' has been
1085 - Support for automatic de-ANSI-fication has been removed.
1087 - The support for the "obscure" multilib feature has been removed
1088 from Automake core (but remains available in the 'contrib/'
1089 directory of the Automake distribution).
1091 - Support for ".log -> .html" conversion and the check-html and
1092 recheck-html targets has been removed from Automake core (but
1093 remains available in the 'contrib/' directory of the Automake
1096 - The deprecated 'lzma' compression format for distribution archives
1097 has been removed, in favor of 'xz' and 'lzip'.
1099 - The obsolete AM_WITH_REGEX macro has been removed.
1101 - The long-deprecated options '--output-dir', '--Werror' and
1102 '--Wno-error' have been removed.
1104 - The chapter on the history of Automake has been moved out of the
1105 reference manual, into a new dedicated Texinfo file.
1109 - New 'cscope' target to build a cscope database for the source tree.
1111 * Changes to Automake-generated testsuite harnesses:
1113 - The new automake option 'serial-tests' has been introduced. It can
1114 be used to explicitly instruct automake to use the older serial
1115 testsuite harness. This is still the default at the moment, but it
1116 might change in future versions.
1118 - The 'recheck' target (provided by the parallel testsuite harness) now
1119 depends on the 'all' target. This allows for a better user-experience
1120 in test-driven development. See automake bug#11252.
1122 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
1123 and unexpected or internal error, or a failure to set up the test case
1124 scenario) have their outcome reported as an 'ERROR' now. Previous
1125 versions of automake reported such an outcome as a 'FAIL' (the only
1126 difference with normal failures being that hard errors were counted
1127 as failures even when the test originating them was listed in
1130 - The testsuite summary displayed by the parallel-test harness has a
1131 completely new format, that always list the numbers of passed, failed,
1132 xfailed, xpassed, skipped and errored tests, even when these numbers
1133 are zero (but using smart coloring when the color-tests option is in
1136 - The default testsuite driver offered by the 'parallel-tests' option is
1137 now implemented (partly at least) with the help of automake-provided
1138 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
1139 on code in the generated Makefile.in.
1140 This has two noteworthy implications. The first one is that projects
1141 using the 'parallel-tests' option should now either run automake with
1142 the '--add-missing' option, or manually copy the 'test-driver' script
1143 into their tree. The second, and more important, implication is that
1144 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
1145 no longer be used to define a test runner, and the command specified
1146 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
1147 program or script. For example, this is still a valid usage (albeit
1148 a little contorted):
1150 TESTS_ENVIRONMENT = \
1151 if test -n '$(STRICT_TESTS)'; then \
1152 maybe_errexit='-e'; \
1156 LOG_COMPILER = $(SHELL) $$maybe_errexit
1158 OTOH, this is no longer a valid usage:
1160 TESTS_ENVIRONMENT = \
1161 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
1165 TESTS_ENVIRONMENT = \
1166 run_with_perl_or_shell () \
1168 if grep -q '^#!.*perl' $$1; then
1174 LOG_COMPILER = run_with_perl_or_shell
1176 - The package authors can now use customary testsuite drivers within
1177 the framework provided by the 'parallel-tests' testsuite harness.
1178 Consistently with the existing syntax, this can be done by defining
1179 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
1181 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
1182 to redirect/define file descriptors used by the test scripts.
1184 - The parallel-tests harness generates now, in addition the '.log' files
1185 holding the output produced by the test scripts, a new set of '.trs'
1186 files, holding "metadata" derived by the execution of the test scripts;
1187 among such metadata are the outcomes of the test cases run by a script.
1189 - Initial and still experimental support for the TAP test protocol is
1192 * Changes to Yacc and Lex support:
1194 - C source and header files derived from non-distributed Yacc and/or
1195 Lex sources are now removed by a simple "make clean" (while they were
1196 previously removed only by "make maintainer-clean").
1198 - Slightly backward-incompatible change, relevant only for use of Yacc
1199 with C++: the extensions of the header files produced by the Yacc
1200 rules are now modelled after the extension of the corresponding
1201 sources. For example, yacc files named "foo.y++" and "bar.yy" will
1202 produce header files named "foo.h++" and "bar.hh" respectively, where
1203 they would have previously produced header files named simply "foo.h"
1204 and "bar.h". This change offers better compatibility with 'bison -o'.
1206 * Miscellaneous changes:
1208 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
1209 rather than 1, if the vala compiler found is too old.
1211 - The build system of Automake itself now avoids the use of make
1212 recursion as much as possible.
1214 - Automake now prefers to quote 'like this' or "like this", rather
1215 than `like this', in diagnostic message and generated Makefiles,
1216 to accommodate the new GNU Coding Standards recommendations.
1218 - Automake has a new option '--print-libdir' that prints the path of the
1219 directory containing the Automake-provided scripts and data files.
1221 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
1223 - The rules to create pdf, dvi and ps output from Texinfo files now
1224 works better with modern 'texi2dvi' script, by explicitly passing
1225 it the '--clean' option to ensure stray auxiliary files are not
1226 left to clutter the build directory.
1228 - Automake can now generate silenced rules for texinfo outputs.
1230 - Some auxiliary files that are automatically distributed by Automake
1231 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
1232 C sources) might now be listed in the DIST_COMMON variable in many
1233 Makefile.in files, rather than in the top-level one.
1235 - Messages of types warning or error from 'automake' and 'aclocal'
1236 are now prefixed with the respective type, and presence of -Werror
1239 - Automake's early configure-time sanity check now tries to avoid
1240 sleeping for a second, which slowed down cached configure runs
1241 noticeably. In that case, it will check back at the end of the
1242 configure script to ensure that at least one second has passed, to
1243 avoid time stamp issues with makefile rules rerunning autotools
1246 - The warnings in the category 'extra-portability' are now enabled by
1247 '-Wall'. In previous versions, one has to use '-Wextra-portability'
1252 - Various minor bugfixes for recent or long-standing bugs.
1254 * Bugs introduced by 1.11:
1256 - The AM_COND_IF macro also works if the shell expression for the
1257 conditional is no longer valid for the condition.
1259 - The automake-provided parallel testsuite harness no longer fails
1260 with BSD make used in parallel mode when there are test scripts in
1261 a subdirectory, like in:
1263 TESTS = sub/foo.test sub/bar.test
1265 * Long-standing bugs:
1267 - Automake's own build system finally have a real "installcheck" target.
1269 - Vala-related cleanup rules are now more complete, and work better in
1272 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
1273 now automatically distributed also if the directory of the auxiliary
1274 files coincides with the top-level directory.
1276 - Automake now detects the presence of the '-d' flag in the various
1277 '*YFLAGS' variables even when their definitions involve indirections
1278 through other variables, such as in:
1280 AM_YFLAGS = $(foo_opts)
1282 - Automake now complains if a '*YFLAGS' variable has any conditional
1283 content, not only a conditional definition.
1285 - Explicit enabling and/or disabling of Automake warning categories
1286 through the '-W...' options now always takes precedence over the
1287 implicit warning level implied by Automake strictness (foreign, gnu
1288 or gnits), regardless of the order in which such strictness and
1289 warning flags appear. For example, a setting like:
1290 AUTOMAKE_OPTIONS = -Wall --foreign
1291 will cause the warnings in category 'portability' to be enabled, even
1292 if those warnings are by default disabled in 'foreign' strictness.
1294 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1296 Bugs fixed in 1.11.5:
1298 * Bugs introduced by 1.11.3:
1300 - Vala files with '.vapi' extension are now recognized and handled
1301 correctly again. See automake bug#11222.
1303 - Vala support work again for projects that contain some program
1304 built from '.vala' (and possibly '.c') sources and some other
1305 program built from '.c' sources *only*. See automake bug#11229.
1307 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1311 * Miscellaneous changes:
1313 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
1314 symbol index) modifiers as well as the "s" action, as the symbol index
1315 is created unconditionally by Microsoft lib. Also, the "q" (quick)
1316 action is now a synonym for "r" (replace). Also, the script has been
1317 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
1319 - When the 'compile' script is used to wrap MSVC, it now accepts an
1320 optional space between the -I, -L and -l options and their respective
1321 arguments, for better POSIX compliance.
1323 - There is an initial, experimental support for automatic dependency
1324 tracking with tcc (the Tiny C Compiler). Its associated depmode is
1325 currently recognized as "icc" (but this and other details are likely
1326 to change in future versions).
1328 - Automatic dependency tracking now works also with the IBM XL C/C++
1329 compilers, thanks to the new new depmode 'xlc'.
1331 Bugs fixed in 1.11.4:
1333 * Bugs introduced by 1.11.2:
1335 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
1336 no longer cause spurious failures upon "make install".
1338 - The user can now instruct the 'uninstall-info' rule not to update
1339 the '${infodir}/dir' file by exporting the environment variable
1340 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
1341 with how the 'install-info' rule operates since automake 1.11.2.
1343 * Long-standing bugs:
1345 - It is now possible for a foo_SOURCES variable to hold Vala sources
1346 together with C header files, as well as with sources and headers for
1347 other supported languages (e.g., C++). Previously, only mixing C and
1348 Vala sources was supported.
1350 - If "aclocal --install" is used, and the first directory specified with
1351 '-I' is non-existent, aclocal will now create it before trying to copy
1354 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
1355 install rules to create an empty $(foodir) directory; for example, if
1356 Makefile.am contains something like:
1358 pkglibexec_SCRIPTS =
1360 pkglibexec_SCRIPTS += bar.sh
1363 the $(pkglibexec) directory will not be created upon "make install".
1365 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1369 * Miscellaneous changes:
1371 - Automake's own build system is more silent by default, making use of
1372 the 'silent-rules' option.
1374 - The master copy of the 'gnupload' script is now maintained in gnulib,
1377 - The 'missing' script no longer tries to wrap calls to 'tar'.
1379 - "make dist" no longer wraps 'tar' invocations with the 'missing'
1380 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
1381 shouldn't be using BTW ;-) no longer invokes the 'missing' script
1382 to wrap tar, but simply invokes the 'tar' program itself.
1384 - "make dist" can now create lzip-compressed tarballs.
1386 - In the Automake info documentation, the Top node and the nodes about
1387 the invocation of the automake and aclocal programs have been renamed;
1388 now, calling "info automake" will open the Top node, while calling
1389 "info automake-invocation" and "info aclocal-invocation" will access
1390 the nodes about the invocation of respectively automake and aclocal.
1392 - Automake is now distributed as a gzip-compressed and an xz-compressed
1393 tarball. Previously, bzip2 was used instead of xz.
1395 - The last relics of Python 1.5 support have been removed from the
1396 AM_PATH_PYTHON macro.
1398 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
1399 and adds them to the normal list of dependencies, but without
1400 overwriting the foo_DEPENDENCIES variable, which is normally computed
1403 Bugs fixed in 1.11.3:
1405 * Bugs introduced by 1.11.2:
1407 - Automake now correctly recognizes the prefix/primary combination
1408 'pkglibexec_SCRIPTS' as valid.
1410 - The parallel-tests harness no longer trips on sed implementations
1411 with stricter limits on the length of input lines (problem seen at
1412 least on Solaris 8).
1414 * Long-standing bugs:
1416 - The "deleted header file problem" for *.am files is avoided by stub
1417 rules. This allows 'make' to trigger a rerun of 'automake' also if
1418 some previously needed '.am' file has been removed.
1420 - The 'silent-rules' option now generates working makefiles even
1421 for the uncommon 'make' implementations that do not support the
1422 nested-variables extension to POSIX 2008. For such 'make'
1423 implementations, whether a build is silent is determined at
1424 configure time, and cannot be overridden at make time with
1425 "make V=0" or "make V=1".
1427 - Vala support now works better in VPATH setups.
1429 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1433 * Changes to aclocal:
1435 - The `--acdir' option is deprecated. Now you should use the new options
1436 `--automake-acdir' and `--system-acdir' instead.
1438 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1439 colon-separated list of additional directories to search after the
1440 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1441 and before the system acdir (by default ${prefix}/share/aclocal).
1443 * Miscellaneous changes:
1445 - The Automake support for automatic de-ANSI-fication has been
1446 deprecated. It will probably be removed in the next major Automake
1449 - The `lzma' compression scheme and associated automake option `dist-lzma'
1450 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1452 - You may adjust the compression options used in dist-xz and dist-bzip2.
1453 The default is now merely -e for xz, but still -9 for bzip; you may
1454 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1455 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1457 - The `compile' script now converts some options for MSVC for a better
1458 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1460 - The py-compile script now accepts empty arguments passed to the options
1461 `--destdir' and `--basedir', and complains about unrecognized options.
1462 Moreover, a non-option argument or a special `--' argument terminates
1463 the list of options.
1465 - A developer that needs to pass specific flags to configure at "make
1466 distcheck" time can now, and indeed is advised to, do so by defining
1467 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1468 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1469 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1470 user; still, the old Makefile.am files that used to define it will
1471 still continue to work as before.
1473 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1474 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1475 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1476 is run with -Wextra-portability and -Werror.
1478 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1479 file generated by automake-provided rules by defining the special make
1480 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1482 - The `install-info' rule can now be instructed not to create/update
1483 the `${infodir}/dir' file, by exporting the new environment variable
1484 `AM_UPDATE_INFO_DIR' to the value "no".
1486 Bugs fixed in 1.11.2:
1488 * Bugs introduced by 1.11:
1490 - The parallel-tests driver no longer produces erroneous results with
1491 Tru64/OSF 5.1 sh upon unreadable log files.
1493 - The `parallel-tests' test driver does not report spurious successes
1494 when used with concurrent FreeBSD make (e.g., "make check -j3").
1496 - When the parallel-tests driver is in use, automake now explicitly
1497 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1498 instead of issuing confusing and apparently unrelated error messages
1499 (e.g., "non-POSIX variable name", "bad characters in variable name",
1500 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1501 silently producing broken `Makefile.in' files.
1503 - The `silent-rules' option now truly silences all compile rules, even
1504 when dependency tracking is disabled. Also, when `silent-rules' is
1505 not used, `make' output no longer contains spurious backslash-only
1506 lines, thus once again matching what Automake did before 1.11.
1508 - The AM_COND_IF macro also works if the shell expression for the
1509 conditional is no longer valid for the condition.
1511 * Long-standing bugs:
1513 - The order of Yacc and Lex flags is fixed to be consistent with other
1514 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1515 $(LFLAGS), so that the user variables override the developer variables.
1517 - "make distcheck" now correctly complains also when "make uninstall"
1518 leaves one and only one file installed in $(prefix).
1520 - A "make uninstall" issued before a "make install", or after a mere
1521 "make install-data" or a mere "make install-exec" does not spuriously
1524 - Automake now warns about more primary/directory invalid combinations,
1525 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1527 - Rules generated by Automake now try harder to not change any files when
1528 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1529 Yacc source files and the rule to update config.h.
1531 - Several scripts and the parallel-tests testsuite driver now exit with
1532 the right exit status upon receiving a signal.
1534 - A per-Makefile.am setting of -Werror does not erroneously carry over
1535 to the handling of other Makefile.am files.
1537 - The code for automatic dependency tracking works around a Solaris
1538 make bug triggered by sources containing repeated slashes when the
1539 `subdir-objects' option was used.
1541 - The makedepend and hp depmodes now work better with VPATH builds.
1543 - Java sources specified with check_JAVA are no longer compiled for
1544 "make all", but only for "make check".
1546 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1547 and error out if `javadir' is undefined, instead of silently producing
1548 a broken Makefile.in.
1550 - aclocal and automake now honour the configure-time definitions of
1551 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1553 - The `install-info' recipe no longer tries to guess whether the
1554 `install-info' program is from Debian or from GNU, and adaptively
1555 change its behaviour; this has proven to be frail and easy to
1558 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1560 Bugs fixed in 1.11.1:
1562 - Lots of minor bugfixes.
1564 * Bugs introduced by 1.11:
1566 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1567 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1569 * Long standing bugs:
1571 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1572 even if the `--prefix' argument pointed outside of a system directory.
1573 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1574 `get_python_lib' function if it points outside the configured prefix,
1575 unless the `--prefix' argument was either `/usr' or below `/System'.
1577 - The testsuite does not try to change the mode of `ltmain.sh' files from
1578 a Libtool installation (symlinked to test directories) any more.
1580 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1581 tools are preferred in a cross-compile setup.
1583 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1584 This fixes a race condition where untrusted users could modify files
1585 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1586 build directory was world-searchable. This is CVE-2009-4029.
1588 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1592 * Version requirements:
1594 - Autoconf 2.62 or greater is required.
1596 * Changes to aclocal:
1598 - The autoconf version check implemented by aclocal in aclocal.m4
1599 (and new in Automake 1.10) is degraded to a warning. This helps
1600 in the common case where the Autoconf versions used are compatible.
1602 * Changes to automake:
1604 - The automake program can run multiple threads for creating most
1605 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1606 with interpreter-based threads enabled. Set the environment variable
1607 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1608 enable this experimental feature.
1610 * Changes to Libtool support:
1612 - Libtool generic flags are now passed to the install and uninstall
1615 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1616 config.lt is removed correctly now.
1618 * Languages changes:
1620 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1621 Fortran, and Ratfor).
1623 - For files with extension .f90, .f95, .f03, or .f08, the flag
1624 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1626 - Files with extension .sx are also treated as preprocessed assembler.
1628 - The default source file extension (.c) can be overridden with
1629 AM_DEFAULT_SOURCE_EXT now.
1631 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1634 - AM_PATH_PYTHON honors python's idea about the site directory.
1636 - There is initial support for the Vala programming language, when using
1637 Vala 0.7.0 or later.
1639 * Miscellaneous changes:
1641 - Automake development is done in a git repository on Savannah now, see
1643 https://git.sv.gnu.org/gitweb/?p=automake.git
1645 A read-only CVS mirror is provided at
1647 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1648 checkout -d automake HEAD
1650 - "make dist" can now create xz-compressed tarballs,
1651 as well as (deprecated?) lzma-compressed tarballs.
1653 - `automake --add-missing' will by default install the GPLv3 file as
1654 COPYING if it is missing. It will also warn that the license file
1655 should be added to source control. Note that Automake will never
1656 overwrite an existing COPYING file, even when the `--force-missing'
1659 - The manual is now distributed under the terms of the GNU FDL 1.3.
1661 - Automake ships and installs man pages for automake and aclocal now.
1663 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1665 - install-sh supports -C, which does not update the installed file
1666 (and its time stamps) if the contents did not change.
1668 - The `gnupload' script has been revamped.
1670 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1672 - The targets `install' and `uninstall' are more efficient now, in that
1673 for example multiple files from one Automake variable such as
1674 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1675 invocation if they do not have to be renamed.
1677 Both install and uninstall may sometimes enter (`cd' into) the target
1678 installation directory now, when no build-local scripts are used.
1680 Both install and uninstall do not fail anymore but do nothing if an
1681 installation directory variable like `bindir' is set to the empty string.
1683 For built-in rules, `make install' now fails reliably if installation
1684 of a file failed. Conversely, `make uninstall' even succeeds when
1685 issued multiple times.
1687 These changes may need some adjustments from users: For example,
1688 some `install' programs refuse to install multiple copies of the
1689 same file in one invocation, so you may need to remove duplicate
1690 entries from file lists.
1692 Also, within one set of files, say, nobase_data_DATA, the order of
1693 installation may be changed, or even unstable among different hosts,
1694 due to the use of associative arrays in awk. The increased use of
1695 awk matches a similar move in Autoconf to provide for better scaling.
1697 Further, most undocumented per-rule install command variables such as
1698 binSCRIPT_INSTALL have been removed because they are not needed any
1699 more. Packages which use them should be using the appropriate one of
1700 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1701 counterpart, depending on the type of files and the need for automatic
1702 target directory creation.
1704 - The "deleted header file problem" for *.m4 files is avoided by
1705 stub rules. This allows `make' to trigger a rerun of `aclocal'
1706 also if some previously needed macro file has been removed.
1708 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1709 an otherwise up to date tree.
1711 - The `color-tests' option causes colored test result output on terminals.
1713 - The `parallel-tests' option enables a new test driver that allows for
1714 parallel test execution, inter-test dependencies, lazy test execution
1715 for unit-testing, re-testing only failed tests, and formatted result output
1716 as RST (reStructuredText) and HTML. Enabling this option may require some
1717 changes to your test suite setup; see the manual for details.
1719 - The `silent-rules' option enables Linux kernel-style silent build output.
1720 This option requires the widely supported but non-POSIX `make' feature
1721 of recursive variable expansion, so do not use it if your package needs
1722 to build with `make' implementations that do not support it.
1724 To enable less verbose build output, the developer has to use the Automake
1725 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1726 macro. The user may then set the default verbosity by passing the
1727 `--enable-silent-rules' option to `configure'. At `make' run time, this
1728 default may be overridden using `make V=0' for less verbose, and `make V=1'
1729 for backward-compatible verbose output.
1731 - New prefix `notrans_' for manpages which should not be transformed
1732 by --program-transform.
1734 - New macro AM_COND_IF for conditional evaluation and conditional
1737 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1738 remove the file in a non-VPATH build. Such setups work with Autoconf
1741 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1742 the default setting.
1744 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1745 useful especially for multi-line values.
1747 - Automake's early configure-time sanity check now diagnoses an
1748 unsafe absolute source directory name and makes configure fail.
1750 - The Automake macros and rules cope better with whitespace in the
1751 current directory name, as long as the relative path to `configure'
1752 does not contain whitespace. To this end, the values of `$(MISSING)'
1753 and `$(install_sh)' may contain suitable quoting, and their expansion
1754 might need `eval'uation if used outside of a makefile. These
1755 undocumented variables may be used in several documented macros such
1756 as $(AUTOCONF) or $(MAKEINFO).
1760 * Long-standing bugs:
1762 - Fix aix dependency tracking for libtool objects.
1764 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1765 unnecessary use of the `compile' script.
1767 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1768 correct `-rpath' argument is used now.
1770 - `config.status --file=Makefile depfiles' now also works with the
1771 extra quoting used internally by Autoconf 2.62 and newer
1772 (it used to work only without the `--file=' bit).
1774 - The `missing' script works better with versioned tool names.
1776 - Semantics for `missing help2man' have been revamped:
1778 Previously, if `help2man' was not present, `missing help2man' would have
1779 the following semantics: if some man page was out of date but present, then
1780 a warning would be printed, but the exit status was 0. If the man page was
1781 not present at all, then `missing' would create a replacement man page
1782 containing an error message, and exit with a status of 2. This does not play
1783 well with `make': the next run will see this particular man page as being up
1784 to date, and will only error out on the next generated man page, if any;
1785 repeat until all pages are done. This was not desirable.
1787 These are the new semantics: if some man page is not present, and help2man
1788 is not either, then `missing' will warn and generate the replacement page
1789 containing the error message, but exit successfully. However, `make dist'
1790 will ensure that no such bogus man pages are packaged into a tarball.
1792 - Targets provided by automake behave better with `make -n', in that they
1793 take care not to create files.
1795 - `config.status Makefile... depfiles' works fine again in the presence of
1796 disabled dependency tracking.
1798 - The default no-op recursive rules for these targets also work with BSD make
1799 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1801 - `make distcheck' works also when both a directory and some file below it
1802 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1804 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1805 `make mostlyclean' any more; only the LaTeX by-products are.
1807 - Renamed objects also work with the `subdir-objects' option and
1808 source file languages which Automake does not know itself.
1810 - `automake' now correctly complains about variable assignments which are
1811 preceded by a comment, extend over multiple lines with backslash-escaped
1812 newlines, and end in a comment sign. Previous versions would silently
1813 and wrongly ignore such assignments completely.
1815 * Bugs introduced by 1.10:
1817 - Fix output of dummy dependency files in presence of post-processed
1818 Makefile.in's again, but also cope with long lines.
1820 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1821 that have been declared as programs in the same Makefile.
1822 This is for consistency with the analogous change to TESTS in 1.10.
1824 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1825 followed by directories containing config headers.
1827 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1831 * Version requirements:
1833 - Autoconf 2.60 or greater is required.
1835 - Perl 5.6 or greater is required.
1837 * Changes to aclocal:
1839 - aclocal now also supports -Wmumble and -Wno-mumble options.
1841 - `dirlist' entries (for the aclocal search path) may use shell
1842 wildcards such as `*', `?', or `[...]'.
1844 - aclocal supports an --install option that will cause system-wide
1845 third-party macros to be installed in the local directory
1846 specified with the first -I flag. This option also uses #serial
1847 lines in M4 files to upgrade local macros.
1849 The new aclocal options --dry-run and --diff help to review changes
1850 before they are installed.
1852 - aclocal now outputs an autoconf version check in aclocal.m4 in
1853 projects using automake.
1855 For a few years, automake and aclocal have been calling autoconf
1856 (or its underlying engine autom4te) to accurately retrieve the
1857 data they need from configure.ac and its siblings. Doing so can
1858 only work if all autotools use the same version of autoconf. For
1859 instance a Makefile.in generated by automake for one version of
1860 autoconf may stop working if configure is regenerated with another
1861 version of autoconf, and vice versa.
1863 This new version check ensures that the whole build system has
1864 been generated using the same autoconf version.
1866 * Support for new Autoconf macros:
1868 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1870 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1871 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1872 in different directories. However, only one instance of such a
1873 library objects directory is supported.
1875 * Change to Libtool support:
1877 - Libtool generic flags (those that go before the --mode=MODE option)
1878 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1880 * Yacc and Lex changes:
1882 - The rebuild rules for distributed Yacc and Lex output will avoid
1883 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1886 - ylwrap is now always used for lex and yacc source files,
1887 regardless of whether there is more than one source per directory.
1889 * Languages changes:
1891 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1892 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1893 tracking, unlike non-preprocessed assembler (*.s).
1895 - subdir-object mode works now with Assembler. Automake assumes
1896 that the compiler understands `-c -o'.
1898 - Preprocessed assembler (*.S) compilation now also honors
1899 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1901 - Improved support for Objective C:
1902 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1903 - A new section of the manual documents the support.
1905 - New support for Unified Parallel C:
1906 - AM_PROG_UPC looks for a UPC compiler.
1907 - A new section of the manual documents the support.
1909 - Per-target flags are now correctly handled in link rules.
1911 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1912 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1913 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1914 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1916 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1917 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1918 is expected to work (and actually works during compilation).
1920 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1921 "in addition to" breaks backward compatibility with older versions.
1922 If your package used both variables, as in
1924 AM_LDFLAGS = common flags
1925 bin_PROGRAMS = a b c
1926 a_LDFLAGS = more flags
1929 and assumed *_LDFLAGS would sum up, you should rewrite it as
1931 AM_LDFLAGS = common flags
1932 bin_PROGRAMS = a b c
1933 a_LDFLAGS = $(AM_LDFLAGS) more flags
1936 This new behavior of *_LDFLAGS is more coherent with other
1937 per-target variables, and the way *_LDFLAGS variables were
1938 considered internally.
1940 * New installation targets:
1942 - New targets mandated by GNU Coding Standards:
1947 By default they will only install Texinfo manuals.
1948 You can customize them with *-local variants:
1954 - The undocumented recursive target `uninstall-info' no longer exists.
1955 (`uninstall' is in charge of removing all possible documentation
1956 flavors, including optional formats such as dvi, ps, or info even
1957 when `no-installinfo' is used.)
1959 * Miscellaneous changes:
1961 - Automake no longer complains if input files for AC_CONFIG_FILES
1962 are specified using shell variables.
1964 - clean, distribution, or rebuild rules are normally disabled for
1965 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1966 AC_CONFIG_LINK specified using shell variables. However, if these
1967 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1968 be able to output rules anyway.
1969 (See the Automake documentation for AC_CONFIG_FILES.)
1971 - $(EXEEXT) is automatically appended to filenames of TESTS
1972 that have been declared as programs in the same Makefile.
1973 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1975 - `-Wportability' has finally been turned on by default for `gnu' and
1976 `gnits' strictness. This means, automake will complain about %-rules
1977 or $(GNU Make functions) unless you switch to `foreign' strictness or
1978 use `-Wno-portability'.
1980 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1981 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1982 $(mkdir_p) variable is still defined (to the same value as
1983 $(MKDIR_P)) but should be considered obsolete. If you are using
1984 $(mkdir_p) in some of your rules, please plan to update them to
1985 $(MKDIR_P) at some point.
1987 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1988 They still work in this release, but may be withdrawn in a future one.
1990 - Inline compilation rules for gcc3-style dependency tracking are
1993 - Automake installs a "Hello World!" example package in $(docdir).
1994 This example is used throughout the new "Autotools Introduction"
1995 chapter of the manual.
1997 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2001 * Makefile.in bloat reduction:
2003 - Inference rules are used to compile sources in subdirectories when
2004 the `subdir-objects' option is used and no per-target flags are
2005 used. This should reduce the size of some projects a lot, because
2006 Automake used to output an explicit rule for each such object in
2009 - Automake no longer outputs three rules (.o, .obj, .lo) for each
2010 object that must be built with explicit rules. It just outputs
2011 the rules required to build the kind of object considered: either
2012 the two .o and .obj rules for usual objects, or the .lo rule for
2015 * Change to Libtool support:
2017 - Libtool tags are used with libtool versions that support them.
2018 (I.e., with Libtool 1.5 or greater.)
2020 - Automake is now able to handle setups where a libtool library is
2021 conditionally installed in different directories, as in
2024 lib_LTLIBRARIES = liba.la
2026 pkglib_LTLIBRARIES = liba.la
2028 liba_la_SOURCES = ...
2030 * Changes to aclocal:
2032 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
2033 really evaluated, before it decides to include them in aclocal.m4.
2034 This solves nasty problems with conditional redefinitions of
2035 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
2036 *.m4 files to be included in any project using these macros.
2037 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
2038 most famous instance of this bug.)
2040 - Do not complain about missing conditionally AC_REQUIREd macros
2041 that are not actually used. In 1.8.x aclocal would correctly
2042 determine which of these macros were really needed (and include
2043 only these in the package); unfortunately it would also require
2044 all of them to be present in order to run. This created
2045 situations were aclocal would not work on a tarball distributing
2046 all the macros it uses. For instance running aclocal on a project
2047 containing only the subset of the Gettext macros in use by the
2048 project did not work, because gettext conditionally requires other
2051 * Portability improvements:
2053 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
2054 tar-pax. The new option filename-length-max=99 helps diagnosing
2055 filenames that are too long for tar-v7. (PR/414)
2057 - Variables augmented with `+=' are now automatically flattened (i.e.,
2058 trailing backslashes removed) and then wrapped around 80 columns
2059 (adding trailing backslashes). In previous versions, a long series
2065 would result in a single-line definition of VAR that could possibly
2066 exceed the maximum line length of some make implementations.
2068 Non-augmented variables are still output as they are defined in
2073 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
2074 Works the same as the old Fortran 77 implementation; just replace
2075 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
2076 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
2078 - Support for conditional _LISP.
2080 - Support for conditional -hook and -local rules (PR/428).
2082 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
2084 - Automake will not write any Makefile.ins after the first error it
2085 encounters. The previous Makefile.ins (if any) will be left in
2086 place. (Warnings will not prevent output, but remember they can
2087 be turned into errors with -Werror.)
2089 - The restriction that SUBDIRS must contain direct children is gone.
2092 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
2093 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
2095 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2097 Bugs fixed in 1.8.5:
2099 * Long-standing bugs:
2101 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
2102 so that `make distclean' and `make maintainer-clean' can work.
2104 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
2106 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
2108 - Polish diagnostic when no input file is found.
2110 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2112 Bugs fixed in 1.8.4:
2114 * Long-standing bugs:
2116 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
2117 overridden by the user.
2119 - Honor PATH_SEPARATOR in various places of the Automake package, for
2122 - Adjust dependency tracking mode detection to ICC 8.0's new output.
2125 - Fix install-sh so it can install the `mv' binary... using `mv'.
2127 - Fix tru64 dependency tracking for libtool objects.
2129 - Work around Exuberant Ctags when creating a TAGS files in a directory
2130 without files to scan but with subdirectories to include.
2132 * Bugs introduced by 1.8:
2134 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
2135 not defined in the same conditions as the _LDADD that uses it.
2137 - Do not warn when JAVAROOT is overridden, this is legitimate.
2139 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2141 Bugs fixed in 1.8.3:
2143 * Long-standing bugs:
2145 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
2146 or any of the other *dir variables contain a space.
2148 Please note that Automake does not and cannot support spaces in
2149 filenames that are involved during the build. This change affects
2150 only installation paths, so that `make install' does not bomb out
2151 in packages configured with
2152 ./configure --prefix '/c/Program Files'
2154 - Fix the depfiles output so it works with GNU sed (<4.1) even when
2155 POSIXLY_CORRECT is set.
2157 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
2158 since Autoconf 2.54, which defines LIBOBJS itself.
2160 - Fix a potential (but unlikely) race condition in parallel elisp
2161 builds. (Introduced in 1.7.3.)
2163 - Do not assume that users override _DEPENDENCIES in all conditions
2164 where Automake will try to define them.
2166 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
2167 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
2170 This fix also affects the $(mkdir_p) variable defined since
2171 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
2172 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
2174 - Secure temporary directory creation in `make distcheck'. (PR/413)
2176 - Do not generate two build rules for `parser.h' when the
2177 parser appears in two different conditionals.
2179 - Work around a Solaris 8 /bin/sh bug in the test for dependency
2180 checking. Usually ./configure will not pick this shell; so this
2181 fix only helps cases where the shell is forced to /bin/sh.
2183 * Bugs introduced by 1.8:
2185 - In some situations (hand-written `m4_include's), aclocal would
2186 call the `File::Spec->rel2abs' method, which was only introduced
2187 in Perl 5.6. This new version reestablish support Perl 5.005.
2189 It is likely that the next major Automake releases will require at
2190 least Perl 5.6. Consider upgrading your development environment
2191 if you are still using the five-year-old Perl 5.005.
2193 - Automake would sometimes fail to define rules for targets listed
2194 in variables defined in multiple conditions. For instance on
2200 it would define only the `a.$(OBJEXT): a.c' rule and omit the
2201 `b.$(OBJEXT): b.c' rule.
2203 * New sections in manual:
2205 - Third-Party Makefiles: how to interface third party Makefiles.
2206 - Upgrading: upgrading packages to newer Automake versions.
2207 - Multiple Outputs: handling tools that produce many outputs.
2209 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2213 * A (well known) portability bug slipped in the changes made to
2214 install-sh in Automake 1.8.1. The broken install-sh would refuse to
2215 install anything on Tru64.
2217 * Fix install rules for conditionally built python files. (This never
2220 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2224 * Bugs introduced by 1.8:
2226 - Fix Config.pm import error with old Perl versions (at least
2227 5.005_03). One symptom is that aclocal could not find its macro
2230 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
2231 created by `make install' are always world readable, even if the
2232 installer happens to have an overly restrictive umask (e.g. 077).
2233 This was a mistake and has been reverted. There are at least two
2234 reasons why we must not use `-m 0755':
2235 - it causes special bits like SGID to be ignored,
2236 - it may be too restrictive (some setups expect 775 directories).
2238 - Fix aclocal to honor definitions located in files which have been
2239 m4_included manually. aclocal 1.8 had been updated to check
2240 m4_included files for new requirements, but forgot that these
2241 m4_included files can also provide new definitions.
2243 Note that if you have such a setup, we recommend you get rid of
2244 it. In the past, there was a reason to m4_include files manually:
2245 aclocal used to duplicate entire M4 files into aclocal.m4, even
2246 files that were distributed. Some packages were therefore
2247 m4_including the distributed file directly, and playing some
2248 tricks to ensure aclocal would not copy that file to aclocal.m4,
2249 in order to limit the amount of duplication. Since aclocal 1.8.x
2250 will precisely output m4_includes for local M4 files, we recommend
2251 that you clean up your setup, removing all manual m4_includes and
2252 letting aclocal output them.
2254 - Output detailed menus in the Info version if the Automake manual,
2255 so that Emacs can locate the indexes.
2257 - configure.ac and configure were listed twice in DIST_COMMON (an
2258 internal variable where Automake lists configury files to
2259 distribute). This was harmless, but unaesthetic.
2261 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
2262 This was an issue only in the Automake package itself, not in
2265 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
2266 DEST:SRC. This was wrong, as some packages do
2267 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
2270 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
2271 argument. This caused two kinds of failures:
2272 - Rules installing data in a conditionally defined directory
2273 failed when that directory was undefined. In this case no
2274 argument was supplied.
2275 - `make installdirs' failed, because several directories were
2276 passed to $(mkdir_p). This was an issue only on platform
2277 were $(mkdir_p) is implemented with `install-sh -d'.
2278 $(mkdir_p) as been changed to accept 0 or more arguments, as
2281 * Long-standing bugs:
2283 - Fix an unexpected diagnostic occurring when users attempt
2284 to override some internal variables that Automake appends to.
2286 - aclocal now scans configure.ac for macro definitions (PR/319).
2288 - Fix a portability issue with OSF1/Tru64 Make. If a directory
2289 distributes files which are outside itself (this usually occurs
2290 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
2291 from a parent package), then `make distcheck' fails due to an
2292 optimization performed by OSF1/Tru64 Make in its VPATH handling.
2293 (tests/subpkg2.test failure)
2295 - Fix another portability issue with Sun and OSF1/Tru64 Make.
2296 In a VPATH-build configuration, `make install' would install
2297 nobase_ files to wrong locations.
2299 - Fix a Perl `uninitialized value' diagnostic occurring when
2300 automake complains that a Texinfo file does not have a
2301 @setfilename statement.
2303 - Erase config.status.lineno during `make distclean'. This file
2304 can be created by config.status. Automake already knew about
2305 configure.lineno, but forgot config.status.lineno.
2307 - Distribute all files, even those which are built and installed
2308 conditionally. This change affects files listed in conditionally
2309 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
2310 as well as those listed in conditionally defined dist_*_DATA,
2311 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
2313 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
2314 doesn't conform to POSIX.
2316 - Normalize help strings for configure variables and options added
2321 - Check for python2.4 in AM_PATH_PYTHON.
2323 * Spurious failures in test suite:
2325 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
2326 tests/ltconv.test: fix failures with CVS Libtool.
2327 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
2328 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
2329 fix failures with old Texinfo versions.
2331 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2337 - The NEWS file is more verbose.
2341 - Autoconf 2.58 or greater is required.
2345 - Default source file names in the absence of a _SOURCES declaration
2346 are made by removing any target extension before appending `.c', so
2347 to make the libtool module `foo.la' from `foo.c', you only need to
2350 lib_LTLIBRARIES = foo.la
2351 foo_la_LDFLAGS = -module
2353 For backward compatibility, foo_la.c will be used instead of
2354 foo.c if this file exists or is the explicit target of a rule.
2355 However -Wobsolete will warn about this deprecated naming.
2357 - AR's `cru' flags are now set in a global ARFLAGS variable instead
2358 of being hard-coded in each $(AR) invocation, so they can be
2359 substituted from configure.ac. This has been requested by people
2360 dealing with non-POSIX ar implementations.
2362 - New warning option: -Woverride. This will warn about any user
2363 target or variable definitions which override Automake
2366 - Texinfo rules back up and restore info files when makeinfo fails.
2368 - Texinfo rules now support the `html' target.
2369 Running this requires Texinfo 4.0 or greater.
2371 `html' is a new recursive target, so if your package mixes
2372 hand-crafted `Makefile.in's with Automake-generated
2373 `Makefile.in's, you should adjust the former to support (or
2374 ignore) this target so that `make html' recurses successfully. If
2375 you had a custom `html' rule in your `Makefile.am', it's better to
2376 rename it as `html-local', otherwise your rule will override
2377 Automake's new rule (you can check that by running `automake
2378 -Woverride') and that will stop the recursion to subdirectories.
2380 Last but not least, this `html' rule is declared PHONY, even when
2381 overridden. Fortunately, it appears that few packages use a
2382 non-PHONY `html' rule.
2384 - Any file which is m4_included from configure.ac will appear as a
2385 configure and Makefile.in dependency, and will be automatically
2388 - The rules for rebuilding Makefiles and Makefile.ins will now
2389 rebuild all Makefiles and all Makefile.ins at once when one of
2390 configure's dependencies has changed. This is considerably faster
2391 than previous implementations, where config.status and automake
2392 were run separately in each directory (this still happens when you
2393 change a Makefile.am locally, without touching configure.ac or
2394 friends). Doing this also solves a longstanding issue: these
2395 rebuild rules failed to work when adding new directories to the
2396 tree, forcing you to run automake manually.
2398 - For similar reasons, the rules to rebuild configure,
2399 config.status, and aclocal.m4 are now defined in all directories.
2400 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
2401 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
2402 should better define them in all directories. This is easily done
2403 using an AC_SUBST (make sure you prefix these dependencies with
2404 $(top_srcdir) since this variable will appear at different
2405 levels of the build tree).
2407 - aclocal will now use `m4_include' instead of copying local m4
2408 files into aclocal.m4. (Local m4 files are those you ship with
2409 your project, other files will be copied as usual.)
2411 Because m4_included files are automatically distributed, it means
2412 for most projects there is no point in EXTRA_DISTing the list of
2413 m4 files which are used. (You can probably get rid of
2414 m4/Makefile.am if you had one.)
2416 - aclocal will avoid touching aclocal.m4 when possible, so that
2417 Autom4te's cache isn't needlessly invalidated. This behavior can
2418 be switched off with the new `--force' option.
2420 - aclocal now uses Autoconf's --trace to detect macros which are
2421 actually used and will no longer include unused macros simply
2422 because they where mentioned. This was often the case for macros
2423 called conditionally.
2425 - New options no-dist and no-dist-gzip.
2427 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2428 py-compile, and ylwrap, now all understand --version and --help.
2430 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2431 links as part of the distclean target and including source files in
2434 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2435 argument. The latter can be used to override the default behavior
2436 (which is to abort).
2438 - Automake will exit with $? = 63 on version mismatch. (So does
2439 Autoconf 2.58) missing knows this, and in this case it will
2440 emulate the tools as if they were absent. Because older versions
2441 of Automake and Autoconf did not use this exit code, this change
2442 will only be useful in projects generated with future versions of
2445 - When using AC_CONFIG_FILES with multiple input files, Automake
2446 generates the first ".in" input file for which a ".am" exists.
2447 (Former versions would try to use only the first input file.)
2449 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2450 idiom to disable byte-compilation of lisp_LISP files, it is
2451 recommended that you switch to using lisp_DATA. Note that
2452 this is not strictly equivalent: lisp_DATA will install elisp
2453 files even if emacs is not installed, while *_LISP do not
2454 install anything unless emacs is found.
2456 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2457 available. This selection is achieved through the Makefile
2458 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2459 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2460 `$(install_sh) -m 0755 -d'.
2464 - Because `mkdir -p' is available on most platforms, and we can use
2465 `install-sh -d' when it is not, the use of the mkinstalldirs
2466 script is being phased out. `automake --add-missing' no longer
2467 installs it, and if you remove mkinstalldirs from your package,
2468 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2470 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2471 gettextize and autopoint will install it when needed. Automake
2472 will continue to define the $(mkinstalldirs) and to distribute
2473 mkinstalldirs when this script is in the source tree.
2475 - AM_PROG_CC_STDC is now empty. The content of this macro was
2476 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2477 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2478 renaming should be safe, even if you have to support several,
2479 versions of Automake, because AC_PROG_CC defines this variable
2480 since Autoconf 2.54.)
2482 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2483 variable to override the aclocal.m4 dependencies computed
2484 (inaccurately) by older versions of Automake. Because Automake
2485 now tracks configure's m4 dependencies accurately (see m4_include
2486 above), the use of ACLOCAL_M4_SOURCES should be considered
2487 obsolete and will be flagged as such when running `automake
2492 - Defining programs conditionally using Automake conditionals no
2493 longer leads to a combinatorial explosion. The following
2494 construct used to be troublesome when used with dozens of
2509 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2511 - Due to implementation constraints, previous versions of Automake
2512 proscribed multiple conditional definitions of some variables
2522 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2523 This restriction has been lifted, and these variables now
2524 support multiple conditional definitions as do other variables.
2526 - Cleanup the definitions of $(distdir) and $(top_distdir).
2527 $(top_distdir) now points to the root of the distribution
2528 directory created during `make dist', as it did in Automake 1.4,
2529 not to the root of the build tree as it did in intervening
2530 versions. Furthermore these two variables are now only defined in
2531 the top level Makefile, and passed to sub-directories when running
2534 - The --no-force option now correctly checks the Makefile.in's
2535 dependencies before deciding not to update it.
2537 - Do not assume that make files are called Makefile in cleaning rules.
2539 - Update .info files in the source tree, not in the build tree. This
2540 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2541 used to update these files in the build tree (previous versions did
2542 it in the source tree too), and it caused several problems, varying
2543 from mere annoyance to portability issues.
2545 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2546 when --add-missing and --force-missing are used. For backward
2547 compatibility --add-missing will continue to install COPYING (in
2548 `gnu' strictness) when none of these three files exist, but this
2549 use is deprecated: you should better choose a license yourself and
2550 install it once for all in your source tree (and in your code
2553 - Fix ylwrap so that it does not overwrite header files that haven't
2554 changed, as the inline rule already does.
2556 - User-defined rules override automake-defined rules for the same
2557 targets, even when rules do not have commands. This is not new
2558 (and was documented), however some of the automake-generated
2559 rules have escaped this principle in former Automake versions.
2560 Rules for the following targets are affected by this fix:
2562 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2563 info, info-am, install-data-am, install-exec-am, install-info,
2564 install-info-am, install-man, installcheck-am, maintainer-clean,
2565 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2566 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2568 Practically it means that an attempt to supplement the dependencies
2569 of some target, as in
2571 clean: my-clean-rule
2573 will now *silently override* the automake definition of the
2574 rule for this target. Running `automake -Woverride' will diagnose
2575 all such overriding definitions.
2577 It should be noted that almost all of these targets support a *-local
2578 variant that is meant to supplement the automake-defined rule
2579 (See node `Extending' in the manual). The above rule should
2582 clean-local: my-clean-rule
2584 These *-local targets have been documented since at least
2585 Automake 1.2, so you should not fear the change if you have
2586 to support multiple automake versions.
2590 - The Automake manual is now distributed under the terms of the GNU FDL.
2592 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2594 - core dumps are no longer removed by the cleaning rules. There are
2595 at least three reasons for this:
2596 1. These files should not be created by any build step,
2597 so their removal do not fit any of the cleaning rules.
2598 Actually, they may be precious to the developer.
2599 2. If such file is created during a build, then it's clearly a
2600 bug Automake should not hide. Not removing the file will
2601 cause `make distcheck' to complain about its presence.
2602 3. Operating systems have different naming conventions for
2603 core dump files. A core file on one system might be a
2604 completely legitimate data file on another system.
2606 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2607 defined by Automake. This means that any definition in the
2608 environment will be used, unless overridden in the Makefile.am or
2609 on the command line. The old behavior, where these variables were
2610 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2611 AC_ARG_VARing each variable from configure.ac.
2613 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2614 documented. (The is not a new feature, these variables have
2615 been there since at least Automake 1.4.)
2617 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2619 Bugs fixed in 1.7.9:
2620 * Fix install-strip to work with nobase_ binaries.
2621 * Fix renaming of #line directives in ylwrap.
2622 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2624 Bugs fixed in 1.7.8:
2625 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2626 * Fix detection of Debian's install-info, broken since version 1.5.
2627 (Debian bug #213524).
2628 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2629 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2631 Bugs fixed in 1.7.7:
2632 * The implementation of automake's --no-force option is unreliable,
2633 so this option is ignored in this version. A real fix will appear in
2634 Automake 1.8. (Debian Bug #206299)
2635 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2636 argument is given. (PR/399)
2637 * Do not warn about leading `_' in variable names, even with -Wportability.
2638 * Support user redefinitions of TEXINFO_TEX.
2639 * depcomp: support AIX Compiler version 6.
2640 * Fix missing rebuilds during `make dist' with BSD make.
2641 (Could produce tarballs containing out-of-date files.)
2642 * Resurrect multilib support.
2643 * Noteworthy manual updates:
2644 - Extending aclocal: how to write m4 macros that won't trigger warnings
2646 - A Shared Library: Rewrite and split into subsections.
2648 Bugs fixed in 1.7.6:
2649 * Fix depcomp's icc mode for ICC 7.1.
2650 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2651 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2652 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2653 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2654 * Remove Latin-1 characters from elisp-comp.
2655 * Update the manual's @dircategory to match the Free Software Directory.
2657 Bugs fixed in 1.7.5:
2658 * Update install-sh's license to remove an advertising clause.
2659 (Debian bug #191717)
2660 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2661 that caused invalid Makefile.ins to be generated.
2662 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2663 * New FAQ entry: renamed objects.
2665 Bugs fixed in 1.7.4:
2666 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2667 the Emacs implementation)
2668 * Fix output of aclocal.m4 dependencies in subdirectories.
2669 * Use `mv -f' instead of `mv' in fastdep rules.
2670 * Upgrade mdate-sh to work on OS/2.
2671 * Don't byte-compile elisp files when ELCFILES is set empty.
2672 (this documented feature was broken by 1.7.3)
2673 * Diagnose trailing backslashes on last line of Makefile.am.
2674 * Diagnose whitespace following trailing backslashes.
2675 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2676 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2678 * `make install' will build `BUILT_SOURCES' first.
2679 * Minor documentation fixes.
2681 Bugs fixed in 1.7.3:
2682 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2683 * Query distutils for `pythondir' and `pythonexecdir', instead of
2684 using an hardcoded path. This should allow builds on 64-bit
2685 distributions that usually use lib64/ instead of lib/.
2686 * AM_PATH_PYTHON will also search for python2.3.
2687 * elisp files are now built all at once instead of one by one. Besides
2688 incurring a speed-up, this is required to support interdependent elisp files.
2689 * Support for DJGPP:
2690 - `make distcheck' will now work in `_inst/' and `_build' instead
2691 of `=inst/' and `=build/'
2692 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2693 - install/uninstall `*.i[0-9][0-9]'-style info files
2694 - more changes that affect only the Automake package (not its output)
2695 * Fix some incompatibilities with upcoming perl-5.10.
2696 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2697 PACKAGE and VERSION.
2699 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2700 is troublesome with gcc and Solaris compilers. (PR/385)
2701 - makedepend mode: work with Libtool. (PR/385 too)
2703 * better support for unusual gettext setups, such as multiple po/ directories
2705 - Flag missing po/ and intl/ directories as warnings, not errors.
2706 - Disable these warnings if po/ does not exist.
2707 * Noteworthy manual updates:
2709 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2711 - Document `AM_YFLAGS = -d'. (PR/382)
2713 Bugs fixed in 1.7.2:
2714 * Fix installation and uninstallation of Info files built in subdirectories.
2715 * Do not run `./configure --with-included-gettext' during `make distcheck'
2716 if AM_GNU_GETTEXT([external]) is used.
2717 * Correctly uninstall renamed man pages.
2718 * Do not strip escaped newline in variables defined in one condition
2719 and augmented in another condition.
2720 * Fix ansi2knr rules for LIBOBJS sources.
2721 * Clean all known Texinfo index files, not only those which appear to
2722 be used, because we cannot know which indexes are used in included files.
2723 (PR/375, Debian Bug #168671)
2724 * Honor only the first @setfilename seen in a Texinfo file.
2725 * Treat "required file X not found" diagnostics as errors (exit status 1).
2726 * Don't complain that a required file is not found when it is a Makefile
2728 * Don't use single suffix inference rules when building `.info'-less
2729 Info files, for the sake of Solaris make.
2730 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2731 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2732 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2733 * Fix building of deansified files from subdirectories. (PR/370)
2734 * Add missing `fi' in the .c->.obj rules.
2735 * Improve install-sh to work even when names contain spaces or certain
2736 (but not all) shell metachars.
2737 * Fix the following spurious failures in the test suite:
2738 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2739 * Noteworthy manual updates:
2740 - Augment the section about BUILT_SOURCES.
2741 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2743 Bugs fixed in 1.7.1:
2744 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2746 * Aclocal should now recognize macro names containing parentheses, e.g.
2747 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2748 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2750 * Install Python files even if they were built. (PR/369)
2751 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2752 version might not be defined in the latter. (PR/358)
2753 * Reorder arguments passed to a couple of commands, so things works
2754 when POSIXLY_CORRECT=1.
2755 * Fix a regex that can cause Perl to segfault on large input.
2757 * Fix distribution of packages that have some sources defined conditionally,
2758 as in the `Conditional compilation using Automake conditionals' example
2760 * Fix spurious test suite failures on IRIX.
2761 * Don't report a required variable as undefined if it has been
2762 defined conditionally for the "right" conditions.
2763 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2764 `make distcheck' fails.
2765 * Fix distribution of included Makefile fragment, so we don't create
2766 spurious directories in the distribution. (PR/366)
2767 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2770 * Autoconf 2.54 is required.
2771 * `aclocal' and `automake' will no longer warn about obsolete
2772 configure macros. This is done by `autoconf -Wobsolete'.
2773 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2774 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2775 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2776 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2777 `configure.ac' for you.
2778 * Support for per-program and per-library `_CPPFLAGS'.
2779 * New `ctags' target (builds CTAGS files).
2780 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2781 (see `automake --help' or the manual for a list of them).
2782 * Honor the WARNINGS environment variable.
2783 * Omit the call to depcomp when using gcc3: call the compiler directly.
2784 * A new option, std-options, tests that programs support --help and --version
2785 when `make installcheck' is run. This is enabled by --gnits.
2786 * Texinfo rules now support the `ps' and `pdf' targets.
2787 * Info files are now created in the build directory, not the source directory.
2788 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2790 * `make distcheck' will enforce DESTDIR support by attempting
2792 * `+=' can be used in conditionals, even if the augmented variable
2793 was defined for another condition.
2794 * Makefile fragments (inserted with `include') are always distributed.
2795 * Use Autoconf's --trace interface to inspect configure.ac and get
2796 a more accurate view of it.
2797 * Add support for extending aclocal's default macro search path
2798 using a `dirlist' file within the aclocal directory.
2799 * automake --output-dir is deprecated.
2800 * The part of the distcheck target that checks whether uninstall actually
2801 removes all installed files has been moved in a separate target,
2802 distuninstallcheck, so it can be overridden easily.
2806 * Support for AM_INIT_GETTEXT([external])
2807 * Bug fixes, including:
2808 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2809 - nobase_ programs and scripts honor --program-transform correctly.
2810 - Erase configure.lineno during `make distclean'.
2811 - Erase YACC and LEX outputs during `make maintainer-clean'.
2814 * Many bug fixes, including:
2815 - Requiring the current version works.
2816 - Fix "$@" portability issues (for Zsh).
2817 - Fix output of dummy dependency files in presence of post-processed
2819 - Don't compute dependencies in background to avoid races with libtool.
2820 - Fix handling of _OBJECTS variables for targets sharing source variables.
2821 - Check dependency mode for Java when AM_PROG_GCJ is used.
2824 * automake --output-dir is deprecated
2825 * Many bug fixes, including:
2826 - Don't choke on AM_LDFLAGS definitions.
2827 - Clean libtool objects from subdirectories.
2828 - Allow configure variables with reserved suffix and unknown prefix
2829 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2830 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2833 * Autoconf 2.52 is required.
2834 * automake no longer run libtoolize.
2835 This is the job of autoreconf (from GNU Autoconf).
2836 * `dist' generates all the archive flavors, as did `dist-all'.
2837 * `dist-gzip' generates the Gzip tar file only.
2838 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2839 explosion. Makefile.in's keep a reasonable size.
2840 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2841 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2843 * `#line' of Lex and Yacc files are properly set.
2844 * EXTRA_DIST can contain generated directories.
2845 * Support for dot-less extensions in suffix rules.
2846 * The part of the distcheck target that checks whether distclean actually
2847 cleans all built files has been moved in a separate target, distcleancheck,
2848 so it can be overridden easily.
2849 * `make distcheck' will pass additional options defined in
2850 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2851 * Fixed CDPATH portability problems, in particular for MacOS X.
2852 * Fixed handling of nobase_ targets.
2853 * Fixed support of implicit rules leading to .lo objects.
2854 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2855 * Added uninstall-hook target
2856 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2857 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2858 (Note that "pkgname" is not "tarname", see the manual for details.)
2859 It is also possible to pass a list of global Automake options as
2860 first argument to this new form of AM_INIT_AUTOMAKE.
2861 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2862 to be a real assembler.
2863 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2864 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2865 * aclocal and automake are also installed with the version number
2866 appended, and some of the install directory names have changed.
2867 This lets you have multiple versions installed simultaneously.
2868 * Support for parsers and lexers in subdirectories.
2871 * Support for `configure.ac'.
2872 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2873 * `make dist-all' is much faster.
2874 * Allows '@' AC_SUBSTs in macro names.
2875 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2876 * User-side dependency tracking. Developers no longer need GNU make
2878 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2879 * Most files are correctly handled if they appear in subdirs
2880 For instance, a _DATA file can appear in a subdir
2881 * GNU tar is no longer required for `make dist'
2882 * Added support for `dist_' and `nodist_' prefixes
2883 * Added support for `nobase_' prefix
2884 * Compiled Java support
2885 * Support for per-executable and per-library compilation flags
2889 * Added support for the Fortran 77 programming language.
2890 * Re-indexed the Automake Texinfo manual.
2891 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2892 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2893 * Support for latest autoconf, including support for objext
2894 * Can now put `.' in SUBDIRS to control build order
2895 * `include' command and `+=' support for macro assignment
2896 * Dependency tracking no long susceptible to deleted header file problem
2897 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2902 * Better Cygwin32 support
2903 * Support for suffix rules with _SOURCES variables
2904 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2905 * @LEXLIB@ no longer required when lex source seen
2906 Lex support in `missing', and new lex macro. Update your missing script.
2907 * Built-in support for assembly
2908 * aclocal gives error if `AM_' macro not found
2909 * Passed YFLAGS, not YACCFLAGS, to yacc
2910 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2911 * Dependencies computed as a side effect of compilation
2912 * Preliminary support for Java
2913 * DESTDIR support at "make install" time
2914 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2918 * Better DejaGnu support
2919 * Added no-installinfo option
2920 * Added Emacs Lisp support
2921 * Added --no-force option
2922 * Included `aclocal' program
2923 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2924 * Now uses `AM_' macro names everywhere
2925 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2926 ansi2knr now works correctly on K&R sources
2927 * Better C++, yacc, lex support
2928 * Will compute _DEPENDENCIES variables automatically if not supplied
2929 * Will interpolate $(...) and ${...} when examining contents of a variable
2930 * .deps files now in build directory, not source directory; dependency
2931 handling generally rewritten
2932 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2933 * can now put config.h into a subdir
2934 * Added dist-all target
2935 * Support for install-info program (see texinfo 3.9)
2936 * Support for "yacc -d"
2937 * configure substitutions are automatically discovered and included
2938 in generated Makefile.in
2939 * Special --cygnus mode
2940 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2941 when making distribution. Some dependencies are auto-ignored.
2942 * Changed how libraries are specified in _LIBRARIES variable
2943 * Full libtool support, from Gord Matzigkeit
2944 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2945 AM_CONFIG_HEADER handles it automatically
2946 * Texinfo output files no longer need .info extension
2947 * Added `missing' support
2949 * Conditionals in Makefile.am, from Ian Taylor
2953 * distcheck target runs install and installcheck targets
2954 * Added preliminary support for DejaGnu.
2959 * More libtool fixes from Gord Matzigkeit; libtool support is still
2961 * Added support for jm_MAINTAINER_MODE
2963 * New "distcheck" target
2967 * mkinstalldirs and mdate-sh now appear in directory specified by
2969 * Removed DIST_SUBDIRS, DIST_OTHER
2970 * AC_ARG_PROGRAM only required when an actual program exists
2971 * dist-hook target now run before distribution packaged up; idea from
2972 Dieter Baron. Other hooks exist, too.
2973 * Preliminary (unfinished) support for libtool
2974 * Added short option names.
2975 * Better "dist" support when gluing together multiple packages
2979 * Documentation updates (many from François Pinard)
2980 * strictness `normal' now renamed to `foreign'
2981 * Renamed --install-missing to --add-missing
2982 * Now handles AC_CONFIG_AUX_DIR
2983 * Now handles TESTS macro
2984 * DIST_OTHER renamed to EXTRA_DIST
2985 * DIST_SUBDIRS is deprecated
2986 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2987 * Better error messages in many cases
2988 * Program names are canonicalized
2989 * Added "check" prefix; from Gord Matzigkeit
2993 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2994 * Beginnings of a test suite
2995 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2996 * Doesn't print anything when running
2997 * Beginnings of MAINT_CHARSET support
2998 * Can specify version in AUTOMAKE_OPTIONS
2999 * Most errors recognizable by Emacs' M-x next-error
3000 * Added --verbose option
3001 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
3002 configure-generated names
3003 * Required macros now distributed in aclocal.m4
3005 * --strictness=gnu is default
3009 * More sophisticated configure.in scanning; now understands ALLOCA and
3010 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
3011 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
3012 * CONFIG_HEADER variable now obsolete
3013 * Can handle multiple Texinfo sources
3014 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
3015 * HEADERS variable no longer needed; now can put .h files directly into
3016 foo_SOURCES variable.
3017 * Automake automatically rebuilds files listed in AC_OUTPUT. The
3018 corresponding ".in" files are included in the distribution.
3021 * Added --gnu and --gnits options
3022 * More standards checking
3024 * Cleaned up 'dist' targets
3025 * Added AUTOMAKE_OPTIONS variable and several options
3026 * Now scans configure.in to get some information (preliminary)
3029 * Works with Perl 4 again
3032 * Added --install-missing option.
3033 * Pretty-prints generated macros and rules
3034 * Comments in Makefile.am are placed more intelligently in Makefile.in
3035 * Generates .PHONY target
3036 * Rule or macro in Makefile.am now overrides contents of Automake file
3037 * Substantial cleanups from François Pinard
3041 * Works with Perl 4 again.
3044 * New uniform naming scheme.
3045 * --strictness option
3047 * '.c' files corresponding to '.y' or '.l' files are automatically
3049 * Many bug fixes and cleanups
3052 * Allow objects to be conditionally included in libraries via lib_LIBADD.
3055 * Bug fixes in 'clean' code.
3056 * Now generates 'installdirs' target.
3057 * man page installation reworked.
3058 * 'make dist' no longer re-creates all Makefile.in's.
3061 * Reimplemented in Perl
3062 * Added --amdir option (for debugging)
3063 * Texinfo support cleaned up.
3064 * Automatic de-ANSI-fication cleaned up.
3065 * Cleaned up 'clean' targets.
3068 * Automatic dependency tracking
3069 * More documentation
3070 * New variables DATA and PACKAGEDATA
3071 * SCRIPTS installed using $(INSTALL_SCRIPT)
3072 * No longer uses double-colon rules
3074 * Changes in advance of internationalization
3078 Copyright (C) 1995-2017 Free Software Foundation, Inc.
3080 This program is free software; you can redistribute it and/or modify
3081 it under the terms of the GNU General Public License as published by
3082 the Free Software Foundation; either version 2, or (at your option)
3085 This program is distributed in the hope that it will be useful,
3086 but WITHOUT ANY WARRANTY; without even the implied warranty of
3087 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
3088 GNU General Public License for more details.
3090 You should have received a copy of the GNU General Public License
3091 along with this program. If not, see <https://www.gnu.org/licenses/>.