1 * WARNING: New versioning scheme for Automake.
3 - Starting with this version onward, Automake will use an update and
4 more rational versioning scheme, one that will allow users to know
5 which kind of changes can be expected from a new version, based on
8 + Micro versions (e.g., 1.13.3, 2.0.1, 3.2.8) will introduce only
9 documentation updates and bug and regression fixes; they will
10 not introduce new features, nor any backward-incompatibility (any
11 such incompatibility would be considered a bug, to be fixed with
12 a further micro release).
14 + Minor versions (e.g., 1.14, 2.1) can introduce new backward
15 compatible features; the only backward-incompatibilities allowed
16 in such a release are new *non-fatal* deprecations and warnings,
17 and possibly fixes for old or non-trivial bugs (or even inefficient
18 behaviours) that could unfortunately have been seen, and used, by
19 some developers as "corner case features". Possible disruptions
20 caused by this kind of fixes should hopefully be quite rare.
22 + Major versions (now expected to be released every 18 or 24 months,
23 and not more often) can introduce new big features (possibly with
24 rough edges and not-fully-stabilized APIs), removal of deprecated
25 features, backward-incompatible changes of behaviour, and possibly
26 major refactorings (that, while ideally transparent to the user,
27 could introduce new bugs). Incompatibilities should however not
28 be introduced gratuitously and abruptly; a proper deprecation path
29 should be duly implemented in the preceding minor releases.
31 - According to this new scheme, the next major version of Automake
32 (the one that has until now been labelled as '1.14') will actually
33 become "Automake 2.0". Automake 1.14 will be the next minor version,
34 which will introduce new features, deprecations and bug fixes, but
35 no serious backward incompatibility.
37 - See discussion about automake bug#13578 for more details and
38 background: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578>
40 * WARNING: Future backward-incompatibilities!
42 - Makefile recipes generated by Automake 2.0 will expect to use an
43 'rm' program that doesn't complain when called without any non-option
44 argument if the '-f' option is given (so that commands like "rm -f"
45 and "rm -rf" will act as a no-op, instead of raising usage errors).
46 Accordingly, AM_INIT_AUTOMAKE will expand new shell code checking
47 that the default 'rm' program in PATH satisfies this requirement, and
48 aborting the configure process if this is not the case. This behavior
49 of 'rm' is very widespread in the wild, and it will be required in the
51 <http://austingroupbugs.net/view.php?id=542>
53 - Automake 2.0 will require Autoconf 2.70 or later (which is still
54 unreleased at the moment of writing, but is planned to be released
55 before Automake 2.0 is).
57 - Automake 2.0 will drop support for the long-deprecated 'configure.in'
58 name for the Autoconf input file. You are advised to start using the
59 recommended name 'configure.ac' instead, ASAP.
61 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated
62 in Automake 2.0 (where it will raise warnings in the "obsolete"
63 category). You are advised to start relying on the new Automake
64 support for AC_CONFIG_MACRO_DIRS instead (which was introduced in
67 - Automake 2.0 will remove support for automatic dependency tracking
68 with the SGI C/C++ compilers on IRIX. The SGI depmode has been
69 reported broken "in the wild" already, and we don't think investing
70 time in debugging and fixing is worthwhile, especially considering
71 that SGI has last updated those compilers in 2006, and is expected
72 to retire support for them in December 2013:
73 <http://www.sgi.com/services/support/irix_mips_support.html>
75 - Automake 2.0 will remove support for MS-DOS and Windows 95/98/ME
76 (support for them was offered by relying on the DJGPP project).
77 Note however that both Cygwin and MSYS/MinGW on modern Windows
78 versions will continue to be fully supported.
80 - Automake-provided scripts and makefile recipes might (finally!)
81 start assuming a POSIX shell in Automake 2.0.
83 - Starting from Automake 2.0, third-party m4 files located in the
84 system-wide aclocal directory, as well as in any directory listed
85 in the ACLOCAL_PATH environment variable, will take precedence
86 over "built-in" Automake macros. For example (assuming Automake
87 is installed in the /usr/local hierarchy), a definition of the
88 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
89 should take precedence over the same-named automake-provided macro
90 (defined in '/usr/local/share/aclocal-2.0/vala.m4').
92 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
96 * Documentation fixes:
98 - The documentation no longer mistakenly reports that the obsolete
99 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
100 to be removed in Automake 2.0.
104 - Byte-compilation of Emacs lisp files could fail spuriously on
105 Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
107 - If the same user-defined suffixes were transformed into different
108 Automake-known suffixes in different Makefile.am files in the same
109 project, automake could get confused and generate inconsistent
110 Makefiles (automake bug#14441).
111 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
112 and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
113 would have mistakenly placed into 'Makefile.in' rules to compile
114 "*.c" files into object files, and into 'sub/Makefile.in' rules to
115 compile "*.cc" files into object files --- rather than the other
116 way around. This is now fixed.
120 - The test cases no longer have the executable bit set. This should
121 make it clear that they are not meant to be run directly; as
122 explained in t/README, they can only be run through the custom
123 'runtest' script, or by a "make check" invocation.
125 - The testsuite has seen the introduction of a new helper function
126 'run_make', and several related changes. These serve a two-fold
129 1. Remove brittleness due to the use of "make -e" in test cases.
131 2. Seamlessly allow the use of parallel make ("make -j...") in the
132 test cases, even where redirection of make output is involved
133 (see automake bug#11413 for a description of the subtle issues
136 - Several spurious failures have been fixed (they hit especially
137 MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
138 #14498, #14499, #14500, #14501, #14517 and #14528.
140 - Some other minor miscellaneous changes and fixlets.
142 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
146 * Obsolescent features:
148 - Use of suffix-less info files (that can be specified through the
149 '@setfilename' macro in Texinfo input files) is discouraged, and
150 its use will raise warnings in the 'obsolete' category.
152 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
153 is discouraged, and its use will raise warnings in the 'obsolete'
154 category. You are advised to simply use the '.texi' extension
157 * Documentation fixes:
159 - The long-deprecated but still supported two-arguments invocation form
160 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
161 thing to do, given that support for such usage might need to remain
162 in place for an unspecified amount of time in order to cater to people
163 who want to define the version number for their package dynamically at
164 configure runtime (unfortunately, Autoconf does not yet support this
165 scenario, so we cannot delegate the work to it).
167 - The serial testsuite harness is no longer reported as "deprecated",
168 but as "discouraged". We have no plan to remove it, nor to make its
169 use cause runtime warnings.
171 - The parallel testsuite is no longer reported as "experimental"; it
172 is well tested, and should be stable now.
174 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
175 'dist-tarZ' options are obsolescent, and their use is deprecated
176 in the documentation.
178 - Other minor miscellaneous fixes and improvements; in particular,
179 some improvements in cross-references.
183 - When the 'ustar' option is used, the generated configure script no
184 longer risks hanging during the tests for the availability of the
185 'pax' utility, even if the user running configure has a UID or GID
186 that requires more than 21 bits to be represented.
187 See automake bug#8343 and bug#13588.
189 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
190 again, as they did in Automake 1.12.x (albeit printing runtime
191 warnings in the 'obsolete' category). Removing them has turned
192 out to be a very bad idea, because it complicated distro packing
193 enormously. Making them issue fatal warnings, as we did in
194 Automake 1.13, has turned out to be a similarly very bad idea,
195 for exactly the same reason.
197 - aclocal will no longer error out if the first local m4 directory
198 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
199 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
200 a warning in the 'unsupported' category. This is done to support
201 some pre-existing real-world usages. See automake bug#13514.
203 - aclocal will no longer consider directories for extra m4 files more
204 than once, even if they are specified multiple times. This ensures
205 packages that specify both
207 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
208 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
210 will work correctly, even when the 'm4' directory contains no
211 package-specific files, but is used only to install third-party
212 m4 files (as can happen with e.g., "libtoolize --install").
213 See automake bug#13514.
215 - Analysis of make flags in Automake-generated rules has been made more
216 robust, and more future-proof. For example, in presence of make that
217 (like '-I') take an argument, the characters in said argument will no
218 longer be spuriously considered as a set of additional make options.
219 In particular, automake-generated rules will no longer spuriously
220 believe to be running in dry mode ("make -n") if run with an invocation
221 like "make -I noob"; nor will they believe to be running in keep-going
222 mode ("make -k") if run with an invocation like "make -I kool"
223 (automake bug#12554).
225 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
231 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
232 causes a clear and helpful error message, instead of obscure ones
233 (issue introduced in Automake 1.13).
235 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
241 - ylwrap renames properly header guards in generated header files
242 (*.h), instead of leaving Y_TAB_H.
244 - ylwrap now also converts header guards in implementation files
245 (*.c). Because ylwrap failed to rename properly #include in the
246 implementation files, current versions of Bison (e.g., 2.7)
247 duplicate the generated header file in the implementation file.
248 The header guard then protects the implementation file from
249 duplicate definitions from the header file.
251 * Version requirements:
253 - Autoconf 2.65 or greater is now required.
255 - The rules to build PDF and DVI output from Texinfo input now
256 require Texinfo 4.9 or later.
260 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
261 option) has been removed. See discussion about automake bug#11034
262 for more background: <http://debbugs.gnu.org/11034>.
264 - The deprecated aclocal option '--acdir' has been removed. You
265 should use the options '--automake-acdir' and '--system-acdir'
266 instead (which have been introduced in Automake 1.11.2).
268 - The following long-obsolete m4 macros have been removed:
270 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
271 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
272 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
273 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
274 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
275 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
276 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
277 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
278 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
279 of the now-removed automatic de-ANSI-fication
282 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
284 - Use of the long-deprecated two- and three-arguments invocation forms
285 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
286 though (albeit with a warning in the 'obsolete' category), to cater
287 for people who want to define the version number for their package
288 dynamically (e.g., from the current VCS revision). We'll have to
289 continue this support until Autoconf itself is fixed to allow better
290 support for such dynamic version numbers.
292 * Elisp byte-compilation:
294 - The byte compilation of '.el' files into '.elc' files is now done
295 with a suffix rule. This has simplified the compilation process, and
296 more importantly made it less brittle. The downside is that emacs is
297 now invoked once for each '.el' files, which cause some noticeable
298 slowdowns. These should however be mitigated on multicore machines
299 (which are becoming the norm today) if concurrent make ("make -j")
302 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
303 files in the same subdirectory; for example, byte-compiling of file
304 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
305 'foo.elc'. This behaviour is backward-incompatible with older
306 Automake versions, but it is more natural and more sane. See also
309 - The Emacs invocation performing byte-compilation of '.el' files honors
310 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
311 one is developer-reserved and the latter one user-reserved.
313 - The 'elisp-comp' script, once provided by Automake, has been rendered
314 obsoleted by the just-described changes, and thus removed.
316 * Changes to Automake-generated testsuite harnesses:
318 - The parallel testsuite harness (previously only enabled by the
319 'parallel-tests' option) is the default one; the older serial
320 testsuite harness will still be available through the use of the
321 'serial-tests' option (introduced in Automake 1.12).
323 - The 'color-tests' option is now unconditionally activated by default.
324 In particular, this means that testsuite output is now colorized by
325 default if the attached terminal seems to support ANSI escapes, and
326 that the user can force output colorization by setting the variable
327 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
328 for backward-compatibility, although it's a handled as a no-op now.
330 * Silent rules support:
332 - Support for silent rules is now always active in Automake-generated
333 Makefiles. So, although the verbose output is still the default,
334 the user can now always use "./configure --enable-silent-rules" or
335 "make V=0" to enable quieter output in the package he's building.
337 - The 'silent-rules' option has now become a no-op, preserved for
338 backward-compatibility only. In particular, its use no longer
339 disables the warnings in the 'portability-recursive' category.
343 - The rules to build PDF and DVI files from Texinfo input now require
344 Texinfo 4.9 or later.
346 - The rules to build PDF and DVI files from Texinfo input now use the
347 '--build-dir' option, to keep the auxiliary files used by texi2dvi
348 and texi2pdf around without cluttering the build directory, and to
349 make it possible to run the "dvi" and "pdf" recipes in parallel.
351 * Automatic remake rules and 'missing' script:
353 - The 'missing' script no longer tries to update the timestamp of
354 out-of-date files that require a maintainer-specific tool to be
355 remade, in case the user lacks such a tool (or has a too-old version
356 of it). It just gives a useful warning, and in some cases also a
357 tip about how to obtain such a tool.
359 - The missing script has thus become useless as a (poor) way to work
360 around the sketched-timestamps issues that can happen for projects
361 that keep generated files committed in their VCS repository. Such
362 projects are now encouraged to write a custom "fix-timestamps.sh"
363 script to avoid such issues; a simple example is provided in the
364 "CVS and generated files" chapter of the automake manual.
368 - The user can now define his own recursive targets that recurse
369 in the directories specified in $(SUBDIRS). This can be done by
370 specifying the name of such targets in invocations of the new
371 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
375 - Any failure in the recipe of the "tags", "ctags", "cscope" or
376 "cscopelist" targets in a subdirectory is now propagated to the
377 top-level make invocation.
379 - Tags are correctly computed also for files in _SOURCES variables that
380 only list files with non-standard suffixes (see automake bug#12372).
382 * Improvements to aclocal and related rebuilds rules:
384 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
385 are now traced by aclocal, and can be used to declare the local m4
386 include directories. Formerly, one had to specify it with an explicit
387 '-I' option to the 'aclocal' invocation.
389 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
390 Automake versions will warn about its use, and later version will
391 remove support for it altogether.
393 * The depcomp script:
395 - Dropped support for libtool 1.4.
397 - Various internal refactorings. They should cause no visible change,
398 but the chance for regression is there anyway, so please report any
399 unexpected or suspicious behaviour.
401 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
402 This should cause no problem, since icc 8.0 has been released in
403 December 2003 -- almost nine years ago.
405 - Support for tcc (the Tiny C Compiler) has been improved, and is now
406 handled through a dedicated 'tcc' mode.
410 - ylwrap generates header guards with a single '_' for series of non
411 alphabetic characters, instead of several. This is what Bison >=
414 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
416 Bugs fixed in 1.12.6:
418 * Python-related bugs:
420 - The default installation location for python modules has been improved
421 for Python 3 on Debian and Ubuntu systems, changing from:
423 ${prefix}/lib/python3/dist-packages
427 ${prefix}/lib/python3.x/site-packages
429 This change should ensure modules installed using the default ${prefix}
430 "/usr/local" are found by default by system python 3.x installations.
431 See automake bug#10227.
433 - Python byte-compilation supports the new layout mandated by PEP-3147,
434 with its __pycache__ directory (automake bug#8847).
436 * Build system issues:
438 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
439 Automake's own build system works correctly again (bug introduced
444 - The Vala-related tests has been changed to adjust to the removal of
445 the 'posix' profile in the valac compiler. See automake bug#12934
448 - Some spurious testsuite failures related to older tools and systems
451 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
457 - The AM_PROG_VALAC macro has been enhanced to takes two further
458 optional arguments; it's signature now being
460 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
461 [ACTION-IF-NOT-FOUND])
463 - By default, AM_PROG_VALAC no longer aborts the configure invocation
464 if the Vala compiler found is too old, but simply prints a warning
465 messages (as it did when the Vala compiler was not found). This
466 should avoid unnecessary difficulties for end users that just want
467 to compile the unmodified, distributed Vala-generated C sources,
468 but happens to have an old Vala compiler in their PATH. This fixes
471 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
472 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
473 This is a better default, because with it a triggered makefile rule
474 invoking a Vala compilation will clearly fail with an informative error
475 message like "valac: command not found", rather than silently, with
476 the error possibly going unnoticed or triggering harder-to-diagnose
477 fallout failures in later steps.
479 * Miscellaneous changes:
481 - automake and aclocal no longer honours the 'perllibdir' environment
482 variable. That had always been intended only as an hack required in
483 the testsuite, not meant for any use beyond that.
485 Bugs fixed in 1.12.5:
487 * Long-standing bugs:
489 - Automake no longer generates spurious remake rules invoking autoheader
490 to regenerate the template corresponding to header files specified after
491 the first one in AC_CONFIG_HEADERS (automake bug#12495).
493 - When wrapping Microsoft tools, the 'compile' script falls back to
494 finding classic 'libname.a' style libraries when 'name.lib' and
495 'name.dll.lib' aren't available.
497 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
501 * Warnings and deprecations:
503 - Warnings in the 'obsolete' category are enabled by default both in
504 automake and aclocal.
506 * Miscellaneous changes:
508 - Some testsuite weaknesses and spurious failures have been fixed.
510 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
514 * Miscellaneous changes:
516 - The '.m4' files provided by Automake no longer define serial numbers.
517 This should cause no difference in the behaviour of aclocal though.
519 - Some testsuite weaknesses and spurious failures have been fixed.
521 - There is initial support for automatic dependency tracking with the
522 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
524 Bugs fixed in 1.12.3:
526 * Long-standing bugs:
528 - Instead of renaming only self-references of files (typically for
529 #lines), ylwrap now also renames references to the other generated
530 files. This fixes support for GLR and C++ parsers from Bison (PR
531 automake/491 and automake bug#7648): 'parser.c' now properly
532 #includes 'parser.h' instead of 'y.tab.h'.
534 - Generated files unknown to ylwrap are now preserved. This fixes
535 C++ support for Bison (automake bug#7648): location.hh and the
536 like are no longer discarded.
538 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
542 * Warnings and deprecations:
544 - Automake now issues a warning (in the 'portability' category) if
545 'configure.in' is used instead of 'configure.ac' as the Autoconf
546 input file. Such a warning will also be present in the next
547 Autoconf version (2.70).
551 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
552 order (as done by the other recursive rules), rather than in the
553 inverse order. They used to do that in order to work a round a
554 limitation in an older implementation of the automatic dependency
555 tracking support, but that limitation had been lifted years ago
556 already, when the automatic dependency tracking based on side-effects
557 of compilation had been introduced.
559 - Cleaning rules for compiled objects (both "plain" and libtool) work
560 better when subdir objects are involved, not triggering a distinct
561 'rm' invocation for each such object. They do so by removing *any*
562 compiled object file that is in the same directory of a subdir
563 object. See automake bug#10697.
565 * Silent rules support:
567 - A new predefined $(AM_V_P) make variable is provided; it expands
568 to a shell conditional that can be used in recipes to know whether
569 make is being run in silent or verbose mode.
571 Bugs fixed in 1.12.2:
573 * SECURITY VULNERABILITIES!
575 - The 'distcheck' recipe no longer grants temporary world-write
576 permissions on the extracted distdir. Even if such rights were
577 only granted for a vanishingly small time window, the implied
578 race condition proved to be enough to allow a local attacker
579 to run arbitrary code with the privileges of the user running
580 "make distcheck". This is CVE-2012-3386.
582 * Long-standing bugs:
584 - The "recheck" targets behaves better in the face of build failures
585 related to previously failed tests. For example, if a test is a
586 compiled program that must be rerun by "make recheck", and its
587 compilation fails, it will still be rerun by further "make recheck"
588 invocations. See automake bug#11791.
590 * Bugs introduced by 1.12.1:
592 - Automake provides once again the '$(mkdir_p)' make variable and the
593 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
594 for better backward-compatibility.
596 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
600 * New supported languages:
602 - Support for Objective C++ has been added; it should work similarly to
603 the support for Objective C.
605 * Deprecated obsolescent features:
607 - Use of the long-deprecated two- and three-arguments invocation forms
608 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
609 category. Starting from some future major Automake release (likely
610 post-1.13), such usages will no longer be allowed.
612 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
613 now deprecated (its use triggers a warning in the 'obsolete' category).
614 It will be removed in the next major Automake release (1.13).
616 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
617 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
618 m4 macro are deprecated, eliciting a warning in the 'obsolete'
621 * Miscellaneous changes:
623 - The Automake test cases now require a proper POSIX-conforming shell.
624 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
625 be accepted. In most cases, the user shouldn't have to specify such
626 POSIX shell explicitly, since it will be looked up at configure time.
627 Still, when this lookup fails, or when the user wants to override its
628 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
629 to the shell that will be used to run the Automake test cases).
631 Bugs fixed in 1.12.1:
633 * Bugs introduced by 1.12:
635 - Several weaknesses in Automake's own build system and test suite
638 * Bugs introduced by 1.11.3:
640 - When given non-option arguments, aclocal rejects them, instead of
641 silently ignoring them.
643 * Long-standing bugs:
645 - When the 'color-tests' option is in use, forcing of colored testsuite
646 output through "AM_COLOR_TESTS=always" works even if the terminal is
647 a non-ANSI one, i.e., if the TERM environment variable has a value of
650 - Several inefficiencies and poor performances in the implementation
651 of the parallel-tests 'check' and 'recheck' targets have been fixed.
653 - The post-processing of output "#line" directives done the ylwrap
654 script is more faithful w.r.t. files in a subdirectory; for example,
655 if the processed file is "src/grammar.y", ylwrap will correctly
656 produce directives like:
657 #line 7 "src/grammar.y"
662 * Bugs with new Perl versions:
664 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
666 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
670 * Obsolete features removed:
672 - The never documented nor truly used script 'acinstall' has been
675 - Support for automatic de-ANSI-fication has been removed.
677 - The support for the "obscure" multilib feature has been removed
678 from Automake core (but remains available in the 'contrib/'
679 directory of the Automake distribution).
681 - Support for ".log -> .html" conversion and the check-html and
682 recheck-html targets has been removed from Automake core (but
683 remains available in the 'contrib/' directory of the Automake
686 - The deprecated 'lzma' compression format for distribution archives
687 has been removed, in favor of 'xz' and 'lzip'.
689 - The obsolete AM_WITH_REGEX macro has been removed.
691 - The long-deprecated options '--output-dir', '--Werror' and
692 '--Wno-error' have been removed.
694 - The chapter on the history of Automake has been moved out of the
695 reference manual, into a new dedicated Texinfo file.
699 - New 'cscope' target to build a cscope database for the source tree.
701 * Changes to Automake-generated testsuite harnesses:
703 - The new automake option 'serial-tests' has been introduced. It can
704 be used to explicitly instruct automake to use the older serial
705 testsuite harness. This is still the default at the moment, but it
706 might change in future versions.
708 - The 'recheck' target (provided by the parallel testsuite harness) now
709 depends on the 'all' target. This allows for a better user-experience
710 in test-driven development. See automake bug#11252.
712 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
713 and unexpected or internal error, or a failure to set up the test case
714 scenario) have their outcome reported as an 'ERROR' now. Previous
715 versions of automake reported such an outcome as a 'FAIL' (the only
716 difference with normal failures being that hard errors were counted
717 as failures even when the test originating them was listed in
720 - The testsuite summary displayed by the parallel-test harness has a
721 completely new format, that always list the numbers of passed, failed,
722 xfailed, xpassed, skipped and errored tests, even when these numbers
723 are zero (but using smart coloring when the color-tests option is in
726 - The default testsuite driver offered by the 'parallel-tests' option is
727 now implemented (partly at least) with the help of automake-provided
728 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
729 on code in the generated Makefile.in.
730 This has two noteworthy implications. The first one is that projects
731 using the 'parallel-tests' option should now either run automake with
732 the '--add-missing' option, or manually copy the 'test-driver' script
733 into their tree. The second, and more important, implication is that
734 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
735 no longer be used to define a test runner, and the command specified
736 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
737 program or script. For example, this is still a valid usage (albeit
740 TESTS_ENVIRONMENT = \
741 if test -n '$(STRICT_TESTS)'; then \
742 maybe_errexit='-e'; \
746 LOG_COMPILER = $(SHELL) $$maybe_errexit
748 OTOH, this is no longer a valid usage:
750 TESTS_ENVIRONMENT = \
751 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
755 TESTS_ENVIRONMENT = \
756 run_with_perl_or_shell () \
758 if grep -q '^#!.*perl' $$1; then
764 LOG_COMPILER = run_with_perl_or_shell
766 - The package authors can now use customary testsuite drivers within
767 the framework provided by the 'parallel-tests' testsuite harness.
768 Consistently with the existing syntax, this can be done by defining
769 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
771 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
772 to redirect/define file descriptors used by the test scripts.
774 - The parallel-tests harness generates now, in addition the '.log' files
775 holding the output produced by the test scripts, a new set of '.trs'
776 files, holding "metadata" derived by the execution of the test scripts;
777 among such metadata are the outcomes of the test cases run by a script.
779 - Initial and still experimental support for the TAP test protocol is
782 * Changes to Yacc and Lex support:
784 - C source and header files derived from non-distributed Yacc and/or
785 Lex sources are now removed by a simple "make clean" (while they were
786 previously removed only by "make maintainer-clean").
788 - Slightly backward-incompatible change, relevant only for use of Yacc
789 with C++: the extensions of the header files produced by the Yacc
790 rules are now modelled after the extension of the corresponding
791 sources. For example, yacc files named "foo.y++" and "bar.yy" will
792 produce header files named "foo.h++" and "bar.hh" respectively, where
793 they would have previously produced header files named simply "foo.h"
794 and "bar.h". This change offers better compatibility with 'bison -o'.
796 * Miscellaneous changes:
798 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
799 rather than 1, if the vala compiler found is too old.
801 - The build system of Automake itself now avoids the use of make
802 recursion as much as possible.
804 - Automake now prefers to quote 'like this' or "like this", rather
805 than `like this', in diagnostic message and generated Makefiles,
806 to accommodate the new GNU Coding Standards recommendations.
808 - Automake has a new option '--print-libdir' that prints the path of the
809 directory containing the Automake-provided scripts and data files.
811 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
813 - The rules to create pdf, dvi and ps output from Texinfo files now
814 works better with modern 'texi2dvi' script, by explicitly passing
815 it the '--clean' option to ensure stray auxiliary files are not
816 left to clutter the build directory.
818 - Automake can now generate silenced rules for texinfo outputs.
820 - Some auxiliary files that are automatically distributed by Automake
821 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
822 C sources) might now be listed in the DIST_COMMON variable in many
823 Makefile.in files, rather than in the top-level one.
825 - Messages of types warning or error from 'automake' and 'aclocal'
826 are now prefixed with the respective type, and presence of -Werror
829 - Automake's early configure-time sanity check now tries to avoid
830 sleeping for a second, which slowed down cached configure runs
831 noticeably. In that case, it will check back at the end of the
832 configure script to ensure that at least one second has passed, to
833 avoid time stamp issues with makefile rules rerunning autotools
836 - The warnings in the category 'extra-portability' are now enabled by
837 '-Wall'. In previous versions, one has to use '-Wextra-portability'
842 - Various minor bugfixes for recent or long-standing bugs.
844 * Bugs introduced by 1.11:
846 - The AM_COND_IF macro also works if the shell expression for the
847 conditional is no longer valid for the condition.
849 - The automake-provided parallel testsuite harness no longer fails
850 with BSD make used in parallel mode when there are test scripts in
851 a subdirectory, like in:
853 TESTS = sub/foo.test sub/bar.test
855 * Long-standing bugs:
857 - Automake's own build system finally have a real "installcheck" target.
859 - Vala-related cleanup rules are now more complete, and work better in
862 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
863 now automatically distributed also if the directory of the auxiliary
864 files coincides with the top-level directory.
866 - Automake now detects the presence of the '-d' flag in the various
867 '*YFLAGS' variables even when their definitions involve indirections
868 through other variables, such as in:
870 AM_YFLAGS = $(foo_opts)
872 - Automake now complains if a '*YFLAGS' variable has any conditional
873 content, not only a conditional definition.
875 - Explicit enabling and/or disabling of Automake warning categories
876 through the '-W...' options now always takes precedence over the
877 implicit warning level implied by Automake strictness (foreign, gnu
878 or gnits), regardless of the order in which such strictness and
879 warning flags appear. For example, a setting like:
880 AUTOMAKE_OPTIONS = -Wall --foreign
881 will cause the warnings in category 'portability' to be enabled, even
882 if those warnings are by default disabled in 'foreign' strictness.
884 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
886 Bugs fixed in 1.11.5:
888 * Bugs introduced by 1.11.3:
890 - Vala files with '.vapi' extension are now recognized and handled
891 correctly again. See automake bug#11222.
893 - Vala support work again for projects that contain some program
894 built from '.vala' (and possibly '.c') sources and some other
895 program built from '.c' sources *only*. See automake bug#11229.
897 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
901 * Miscellaneous changes:
903 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
904 symbol index) modifiers as well as the "s" action, as the symbol index
905 is created unconditionally by Microsoft lib. Also, the "q" (quick)
906 action is now a synonym for "r" (replace). Also, the script has been
907 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
909 - When the 'compile' script is used to wrap MSVC, it now accepts an
910 optional space between the -I, -L and -l options and their respective
911 arguments, for better POSIX compliance.
913 - There is an initial, experimental support for automatic dependency
914 tracking with tcc (the Tiny C Compiler). Its associated depmode is
915 currently recognized as "icc" (but this and other details are likely
916 to change in future versions).
918 - Automatic dependency tracking now works also with the IBM XL C/C++
919 compilers, thanks to the new new depmode 'xlc'.
921 Bugs fixed in 1.11.4:
923 * Bugs introduced by 1.11.2:
925 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
926 no longer cause spurious failures upon "make install".
928 - The user can now instruct the 'uninstall-info' rule not to update
929 the '${infodir}/dir' file by exporting the environment variable
930 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
931 with how the 'install-info' rule operates since automake 1.11.2.
933 * Long-standing bugs:
935 - It is now possible for a foo_SOURCES variable to hold Vala sources
936 together with C header files, as well as with sources and headers for
937 other supported languages (e.g., C++). Previously, only mixing C and
938 Vala sources was supported.
940 - If "aclocal --install" is used, and the first directory specified with
941 '-I' is non-existent, aclocal will now create it before trying to copy
944 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
945 install rules to create an empty $(foodir) directory; for example, if
946 Makefile.am contains something like:
950 pkglibexec_SCRIPTS += bar.sh
953 the $(pkglibexec) directory will not be created upon "make install".
955 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
959 * Miscellaneous changes:
961 - Automake's own build system is more silent by default, making use of
962 the 'silent-rules' option.
964 - The master copy of the 'gnupload' script is now maintained in gnulib,
967 - The 'missing' script no longer tries to wrap calls to 'tar'.
969 - "make dist" no longer wraps 'tar' invocations with the 'missing'
970 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
971 shouldn't be using BTW ;-) no longer invokes the 'missing' script
972 to wrap tar, but simply invokes the 'tar' program itself.
974 - "make dist" can now create lzip-compressed tarballs.
976 - In the Automake info documentation, the Top node and the nodes about
977 the invocation of the automake and aclocal programs have been renamed;
978 now, calling "info automake" will open the Top node, while calling
979 "info automake-invocation" and "info aclocal-invocation" will access
980 the nodes about the invocation of respectively automake and aclocal.
982 - Automake is now distributed as a gzip-compressed and an xz-compressed
983 tarball. Previously, bzip2 was used instead of xz.
985 - The last relics of Python 1.5 support have been removed from the
986 AM_PATH_PYTHON macro.
988 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
989 and adds them to the normal list of dependencies, but without
990 overwriting the foo_DEPENDENCIES variable, which is normally computed
993 Bugs fixed in 1.11.3:
995 * Bugs introduced by 1.11.2:
997 - Automake now correctly recognizes the prefix/primary combination
998 'pkglibexec_SCRIPTS' as valid.
1000 - The parallel-tests harness no longer trips on sed implementations
1001 with stricter limits on the length of input lines (problem seen at
1002 least on Solaris 8).
1004 * Long-standing bugs:
1006 - The "deleted header file problem" for *.am files is avoided by stub
1007 rules. This allows 'make' to trigger a rerun of 'automake' also if
1008 some previously needed '.am' file has been removed.
1010 - The 'silent-rules' option now generates working makefiles even
1011 for the uncommon 'make' implementations that do not support the
1012 nested-variables extension to POSIX 2008. For such 'make'
1013 implementations, whether a build is silent is determined at
1014 configure time, and cannot be overridden at make time with
1015 "make V=0" or "make V=1".
1017 - Vala support now works better in VPATH setups.
1019 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1023 * Changes to aclocal:
1025 - The `--acdir' option is deprecated. Now you should use the new options
1026 `--automake-acdir' and `--system-acdir' instead.
1028 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1029 colon-separated list of additional directories to search after the
1030 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1031 and before the system acdir (by default ${prefix}/share/aclocal).
1033 * Miscellaneous changes:
1035 - The Automake support for automatic de-ANSI-fication has been
1036 deprecated. It will probably be removed in the next major Automake
1039 - The `lzma' compression scheme and associated automake option `dist-lzma'
1040 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1042 - You may adjust the compression options used in dist-xz and dist-bzip2.
1043 The default is now merely -e for xz, but still -9 for bzip; you may
1044 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1045 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1047 - The `compile' script now converts some options for MSVC for a better
1048 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1050 - The py-compile script now accepts empty arguments passed to the options
1051 `--destdir' and `--basedir', and complains about unrecognized options.
1052 Moreover, a non-option argument or a special `--' argument terminates
1053 the list of options.
1055 - A developer that needs to pass specific flags to configure at "make
1056 distcheck" time can now, and indeed is advised to, do so by defining
1057 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1058 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1059 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1060 user; still, the old Makefile.am files that used to define it will
1061 still continue to work as before.
1063 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1064 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1065 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1066 is run with -Wextra-portability and -Werror.
1068 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1069 file generated by automake-provided rules by defining the special make
1070 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1072 - The `install-info' rule can now be instructed not to create/update
1073 the `${infodir}/dir' file, by exporting the new environment variable
1074 `AM_UPDATE_INFO_DIR' to the value "no".
1076 Bugs fixed in 1.11.2:
1078 * Bugs introduced by 1.11:
1080 - The parallel-tests driver no longer produces erroneous results with
1081 Tru64/OSF 5.1 sh upon unreadable log files.
1083 - The `parallel-tests' test driver does not report spurious successes
1084 when used with concurrent FreeBSD make (e.g., "make check -j3").
1086 - When the parallel-tests driver is in use, automake now explicitly
1087 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1088 instead of issuing confusing and apparently unrelated error messages
1089 (e.g., "non-POSIX variable name", "bad characters in variable name",
1090 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1091 silently producing broken `Makefile.in' files.
1093 - The `silent-rules' option now truly silences all compile rules, even
1094 when dependency tracking is disabled. Also, when `silent-rules' is
1095 not used, `make' output no longer contains spurious backslash-only
1096 lines, thus once again matching what Automake did before 1.11.
1098 - The AM_COND_IF macro also works if the shell expression for the
1099 conditional is no longer valid for the condition.
1101 * Long-standing bugs:
1103 - The order of Yacc and Lex flags is fixed to be consistent with other
1104 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1105 $(LFLAGS), so that the user variables override the developer variables.
1107 - "make distcheck" now correctly complains also when "make uninstall"
1108 leaves one and only one file installed in $(prefix).
1110 - A "make uninstall" issued before a "make install", or after a mere
1111 "make install-data" or a mere "make install-exec" does not spuriously
1114 - Automake now warns about more primary/directory invalid combinations,
1115 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1117 - Rules generated by Automake now try harder to not change any files when
1118 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1119 Yacc source files and the rule to update config.h.
1121 - Several scripts and the parallel-tests testsuite driver now exit with
1122 the right exit status upon receiving a signal.
1124 - A per-Makefile.am setting of -Werror does not erroneously carry over
1125 to the handling of other Makefile.am files.
1127 - The code for automatic dependency tracking works around a Solaris
1128 make bug triggered by sources containing repeated slashes when the
1129 `subdir-objects' option was used.
1131 - The makedepend and hp depmodes now work better with VPATH builds.
1133 - Java sources specified with check_JAVA are no longer compiled for
1134 "make all", but only for "make check".
1136 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1137 and error out if `javadir' is undefined, instead of silently producing
1138 a broken Makefile.in.
1140 - aclocal and automake now honour the configure-time definitions of
1141 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1143 - The `install-info' recipe no longer tries to guess whether the
1144 `install-info' program is from Debian or from GNU, and adaptively
1145 change its behaviour; this has proven to be frail and easy to
1148 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1150 Bugs fixed in 1.11.1:
1152 - Lots of minor bugfixes.
1154 * Bugs introduced by 1.11:
1156 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1157 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1159 * Long standing bugs:
1161 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1162 even if the `--prefix' argument pointed outside of a system directory.
1163 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1164 `get_python_lib' function if it points outside the configured prefix,
1165 unless the `--prefix' argument was either `/usr' or below `/System'.
1167 - The testsuite does not try to change the mode of `ltmain.sh' files from
1168 a Libtool installation (symlinked to test directories) any more.
1170 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1171 tools are preferred in a cross-compile setup.
1173 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1174 This fixes a race condition where untrusted users could modify files
1175 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1176 build directory was world-searchable. This is CVE-2009-4029.
1178 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1182 * Version requirements:
1184 - Autoconf 2.62 or greater is required.
1186 * Changes to aclocal:
1188 - The autoconf version check implemented by aclocal in aclocal.m4
1189 (and new in Automake 1.10) is degraded to a warning. This helps
1190 in the common case where the Autoconf versions used are compatible.
1192 * Changes to automake:
1194 - The automake program can run multiple threads for creating most
1195 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1196 with interpreter-based threads enabled. Set the environment variable
1197 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1198 enable this experimental feature.
1200 * Changes to Libtool support:
1202 - Libtool generic flags are now passed to the install and uninstall
1205 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1206 config.lt is removed correctly now.
1208 * Languages changes:
1210 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1211 Fortran, and Ratfor).
1213 - For files with extension .f90, .f95, .f03, or .f08, the flag
1214 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1216 - Files with extension .sx are also treated as preprocessed assembler.
1218 - The default source file extension (.c) can be overridden with
1219 AM_DEFAULT_SOURCE_EXT now.
1221 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1224 - AM_PATH_PYTHON honors python's idea about the site directory.
1226 - There is initial support for the Vala programming language, when using
1227 Vala 0.7.0 or later.
1229 * Miscellaneous changes:
1231 - Automake development is done in a git repository on Savannah now, see
1233 http://git.sv.gnu.org/gitweb/?p=automake.git
1235 A read-only CVS mirror is provided at
1237 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1238 checkout -d automake HEAD
1240 - "make dist" can now create xz-compressed tarballs,
1241 as well as (deprecated?) lzma-compressed tarballs.
1243 - `automake --add-missing' will by default install the GPLv3 file as
1244 COPYING if it is missing. It will also warn that the license file
1245 should be added to source control. Note that Automake will never
1246 overwrite an existing COPYING file, even when the `--force-missing'
1249 - The manual is now distributed under the terms of the GNU FDL 1.3.
1251 - Automake ships and installs man pages for automake and aclocal now.
1253 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1255 - install-sh supports -C, which does not update the installed file
1256 (and its time stamps) if the contents did not change.
1258 - The `gnupload' script has been revamped.
1260 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1262 - The targets `install' and `uninstall' are more efficient now, in that
1263 for example multiple files from one Automake variable such as
1264 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1265 invocation if they do not have to be renamed.
1267 Both install and uninstall may sometimes enter (`cd' into) the target
1268 installation directory now, when no build-local scripts are used.
1270 Both install and uninstall do not fail anymore but do nothing if an
1271 installation directory variable like `bindir' is set to the empty string.
1273 For built-in rules, `make install' now fails reliably if installation
1274 of a file failed. Conversely, `make uninstall' even succeeds when
1275 issued multiple times.
1277 These changes may need some adjustments from users: For example,
1278 some `install' programs refuse to install multiple copies of the
1279 same file in one invocation, so you may need to remove duplicate
1280 entries from file lists.
1282 Also, within one set of files, say, nobase_data_DATA, the order of
1283 installation may be changed, or even unstable among different hosts,
1284 due to the use of associative arrays in awk. The increased use of
1285 awk matches a similar move in Autoconf to provide for better scaling.
1287 Further, most undocumented per-rule install command variables such as
1288 binSCRIPT_INSTALL have been removed because they are not needed any
1289 more. Packages which use them should be using the appropriate one of
1290 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1291 counterpart, depending on the type of files and the need for automatic
1292 target directory creation.
1294 - The "deleted header file problem" for *.m4 files is avoided by
1295 stub rules. This allows `make' to trigger a rerun of `aclocal'
1296 also if some previously needed macro file has been removed.
1298 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1299 an otherwise up to date tree.
1301 - The `color-tests' option causes colored test result output on terminals.
1303 - The `parallel-tests' option enables a new test driver that allows for
1304 parallel test execution, inter-test dependencies, lazy test execution
1305 for unit-testing, re-testing only failed tests, and formatted result output
1306 as RST (reStructuredText) and HTML. Enabling this option may require some
1307 changes to your test suite setup; see the manual for details.
1309 - The `silent-rules' option enables Linux kernel-style silent build output.
1310 This option requires the widely supported but non-POSIX `make' feature
1311 of recursive variable expansion, so do not use it if your package needs
1312 to build with `make' implementations that do not support it.
1314 To enable less verbose build output, the developer has to use the Automake
1315 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1316 macro. The user may then set the default verbosity by passing the
1317 `--enable-silent-rules' option to `configure'. At `make' run time, this
1318 default may be overridden using `make V=0' for less verbose, and `make V=1'
1319 for backward-compatible verbose output.
1321 - New prefix `notrans_' for manpages which should not be transformed
1322 by --program-transform.
1324 - New macro AM_COND_IF for conditional evaluation and conditional
1327 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1328 remove the file in a non-VPATH build. Such setups work with Autoconf
1331 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1332 the default setting.
1334 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1335 useful especially for multi-line values.
1337 - Automake's early configure-time sanity check now diagnoses an
1338 unsafe absolute source directory name and makes configure fail.
1340 - The Automake macros and rules cope better with whitespace in the
1341 current directory name, as long as the relative path to `configure'
1342 does not contain whitespace. To this end, the values of `$(MISSING)'
1343 and `$(install_sh)' may contain suitable quoting, and their expansion
1344 might need `eval'uation if used outside of a makefile. These
1345 undocumented variables may be used in several documented macros such
1346 as $(AUTOCONF) or $(MAKEINFO).
1350 * Long-standing bugs:
1352 - Fix aix dependency tracking for libtool objects.
1354 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1355 unnecessary use of the `compile' script.
1357 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1358 correct `-rpath' argument is used now.
1360 - `config.status --file=Makefile depfiles' now also works with the
1361 extra quoting used internally by Autoconf 2.62 and newer
1362 (it used to work only without the `--file=' bit).
1364 - The `missing' script works better with versioned tool names.
1366 - Semantics for `missing help2man' have been revamped:
1368 Previously, if `help2man' was not present, `missing help2man' would have
1369 the following semantics: if some man page was out of date but present, then
1370 a warning would be printed, but the exit status was 0. If the man page was
1371 not present at all, then `missing' would create a replacement man page
1372 containing an error message, and exit with a status of 2. This does not play
1373 well with `make': the next run will see this particular man page as being up
1374 to date, and will only error out on the next generated man page, if any;
1375 repeat until all pages are done. This was not desirable.
1377 These are the new semantics: if some man page is not present, and help2man
1378 is not either, then `missing' will warn and generate the replacement page
1379 containing the error message, but exit successfully. However, `make dist'
1380 will ensure that no such bogus man pages are packaged into a tarball.
1382 - Targets provided by automake behave better with `make -n', in that they
1383 take care not to create files.
1385 - `config.status Makefile... depfiles' works fine again in the presence of
1386 disabled dependency tracking.
1388 - The default no-op recursive rules for these targets also work with BSD make
1389 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1391 - `make distcheck' works also when both a directory and some file below it
1392 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1394 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1395 `make mostlyclean' any more; only the LaTeX by-products are.
1397 - Renamed objects also work with the `subdir-objects' option and
1398 source file languages which Automake does not know itself.
1400 - `automake' now correctly complains about variable assignments which are
1401 preceded by a comment, extend over multiple lines with backslash-escaped
1402 newlines, and end in a comment sign. Previous versions would silently
1403 and wrongly ignore such assignments completely.
1405 * Bugs introduced by 1.10:
1407 - Fix output of dummy dependency files in presence of post-processed
1408 Makefile.in's again, but also cope with long lines.
1410 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1411 that have been declared as programs in the same Makefile.
1412 This is for consistency with the analogous change to TESTS in 1.10.
1414 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1415 followed by directories containing config headers.
1417 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1421 * Version requirements:
1423 - Autoconf 2.60 or greater is required.
1425 - Perl 5.6 or greater is required.
1427 * Changes to aclocal:
1429 - aclocal now also supports -Wmumble and -Wno-mumble options.
1431 - `dirlist' entries (for the aclocal search path) may use shell
1432 wildcards such as `*', `?', or `[...]'.
1434 - aclocal supports an --install option that will cause system-wide
1435 third-party macros to be installed in the local directory
1436 specified with the first -I flag. This option also uses #serial
1437 lines in M4 files to upgrade local macros.
1439 The new aclocal options --dry-run and --diff help to review changes
1440 before they are installed.
1442 - aclocal now outputs an autoconf version check in aclocal.m4 in
1443 projects using automake.
1445 For a few years, automake and aclocal have been calling autoconf
1446 (or its underlying engine autom4te) to accurately retrieve the
1447 data they need from configure.ac and its siblings. Doing so can
1448 only work if all autotools use the same version of autoconf. For
1449 instance a Makefile.in generated by automake for one version of
1450 autoconf may stop working if configure is regenerated with another
1451 version of autoconf, and vice versa.
1453 This new version check ensures that the whole build system has
1454 been generated using the same autoconf version.
1456 * Support for new Autoconf macros:
1458 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1460 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1461 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1462 in different directories. However, only one instance of such a
1463 library objects directory is supported.
1465 * Change to Libtool support:
1467 - Libtool generic flags (those that go before the --mode=MODE option)
1468 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1470 * Yacc and Lex changes:
1472 - The rebuild rules for distributed Yacc and Lex output will avoid
1473 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1476 - ylwrap is now always used for lex and yacc source files,
1477 regardless of whether there is more than one source per directory.
1479 * Languages changes:
1481 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1482 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1483 tracking, unlike non-preprocessed assembler (*.s).
1485 - subdir-object mode works now with Assembler. Automake assumes
1486 that the compiler understands `-c -o'.
1488 - Preprocessed assembler (*.S) compilation now also honors
1489 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1491 - Improved support for Objective C:
1492 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1493 - A new section of the manual documents the support.
1495 - New support for Unified Parallel C:
1496 - AM_PROG_UPC looks for a UPC compiler.
1497 - A new section of the manual documents the support.
1499 - Per-target flags are now correctly handled in link rules.
1501 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1502 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1503 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1504 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1506 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1507 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1508 is expected to work (and actually works during compilation).
1510 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1511 "in addition to" breaks backward compatibility with older versions.
1512 If your package used both variables, as in
1514 AM_LDFLAGS = common flags
1515 bin_PROGRAMS = a b c
1516 a_LDFLAGS = more flags
1519 and assumed *_LDFLAGS would sum up, you should rewrite it as
1521 AM_LDFLAGS = common flags
1522 bin_PROGRAMS = a b c
1523 a_LDFLAGS = $(AM_LDFLAGS) more flags
1526 This new behavior of *_LDFLAGS is more coherent with other
1527 per-target variables, and the way *_LDFLAGS variables were
1528 considered internally.
1530 * New installation targets:
1532 - New targets mandated by GNU Coding Standards:
1537 By default they will only install Texinfo manuals.
1538 You can customize them with *-local variants:
1544 - The undocumented recursive target `uninstall-info' no longer exists.
1545 (`uninstall' is in charge of removing all possible documentation
1546 flavors, including optional formats such as dvi, ps, or info even
1547 when `no-installinfo' is used.)
1549 * Miscellaneous changes:
1551 - Automake no longer complains if input files for AC_CONFIG_FILES
1552 are specified using shell variables.
1554 - clean, distribution, or rebuild rules are normally disabled for
1555 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1556 AC_CONFIG_LINK specified using shell variables. However, if these
1557 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1558 be able to output rules anyway.
1559 (See the Automake documentation for AC_CONFIG_FILES.)
1561 - $(EXEEXT) is automatically appended to filenames of TESTS
1562 that have been declared as programs in the same Makefile.
1563 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1565 - `-Wportability' has finally been turned on by default for `gnu' and
1566 `gnits' strictness. This means, automake will complain about %-rules
1567 or $(GNU Make functions) unless you switch to `foreign' strictness or
1568 use `-Wno-portability'.
1570 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1571 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1572 $(mkdir_p) variable is still defined (to the same value as
1573 $(MKDIR_P)) but should be considered obsolete. If you are using
1574 $(mkdir_p) in some of your rules, please plan to update them to
1575 $(MKDIR_P) at some point.
1577 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1578 They still work in this release, but may be withdrawn in a future one.
1580 - Inline compilation rules for gcc3-style dependency tracking are
1583 - Automake installs a "Hello World!" example package in $(docdir).
1584 This example is used throughout the new "Autotools Introduction"
1585 chapter of the manual.
1587 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1591 * Makefile.in bloat reduction:
1593 - Inference rules are used to compile sources in subdirectories when
1594 the `subdir-objects' option is used and no per-target flags are
1595 used. This should reduce the size of some projects a lot, because
1596 Automake used to output an explicit rule for each such object in
1599 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1600 object that must be built with explicit rules. It just outputs
1601 the rules required to build the kind of object considered: either
1602 the two .o and .obj rules for usual objects, or the .lo rule for
1605 * Change to Libtool support:
1607 - Libtool tags are used with libtool versions that support them.
1608 (I.e., with Libtool 1.5 or greater.)
1610 - Automake is now able to handle setups where a libtool library is
1611 conditionally installed in different directories, as in
1614 lib_LTLIBRARIES = liba.la
1616 pkglib_LTLIBRARIES = liba.la
1618 liba_la_SOURCES = ...
1620 * Changes to aclocal:
1622 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1623 really evaluated, before it decides to include them in aclocal.m4.
1624 This solves nasty problems with conditional redefinitions of
1625 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1626 *.m4 files to be included in any project using these macros.
1627 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1628 most famous instance of this bug.)
1630 - Do not complain about missing conditionally AC_REQUIREd macros
1631 that are not actually used. In 1.8.x aclocal would correctly
1632 determine which of these macros were really needed (and include
1633 only these in the package); unfortunately it would also require
1634 all of them to be present in order to run. This created
1635 situations were aclocal would not work on a tarball distributing
1636 all the macros it uses. For instance running aclocal on a project
1637 containing only the subset of the Gettext macros in use by the
1638 project did not work, because gettext conditionally requires other
1641 * Portability improvements:
1643 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1644 tar-pax. The new option filename-length-max=99 helps diagnosing
1645 filenames that are too long for tar-v7. (PR/414)
1647 - Variables augmented with `+=' are now automatically flattened (i.e.,
1648 trailing backslashes removed) and then wrapped around 80 columns
1649 (adding trailing backslashes). In previous versions, a long series
1655 would result in a single-line definition of VAR that could possibly
1656 exceed the maximum line length of some make implementations.
1658 Non-augmented variables are still output as they are defined in
1663 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1664 Works the same as the old Fortran 77 implementation; just replace
1665 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1666 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1668 - Support for conditional _LISP.
1670 - Support for conditional -hook and -local rules (PR/428).
1672 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1674 - Automake will not write any Makefile.ins after the first error it
1675 encounters. The previous Makefile.ins (if any) will be left in
1676 place. (Warnings will not prevent output, but remember they can
1677 be turned into errors with -Werror.)
1679 - The restriction that SUBDIRS must contain direct children is gone.
1682 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1683 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1685 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1687 Bugs fixed in 1.8.5:
1689 * Long-standing bugs:
1691 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1692 so that `make distclean' and `make maintainer-clean' can work.
1694 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1696 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1698 - Polish diagnostic when no input file is found.
1700 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1702 Bugs fixed in 1.8.4:
1704 * Long-standing bugs:
1706 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1707 overridden by the user.
1709 - Honor PATH_SEPARATOR in various places of the Automake package, for
1712 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1715 - Fix install-sh so it can install the `mv' binary... using `mv'.
1717 - Fix tru64 dependency tracking for libtool objects.
1719 - Work around Exuberant Ctags when creating a TAGS files in a directory
1720 without files to scan but with subdirectories to include.
1722 * Bugs introduced by 1.8:
1724 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1725 not defined in the same conditions as the _LDADD that uses it.
1727 - Do not warn when JAVAROOT is overridden, this is legitimate.
1729 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1731 Bugs fixed in 1.8.3:
1733 * Long-standing bugs:
1735 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1736 or any of the other *dir variables contain a space.
1738 Please note that Automake does not and cannot support spaces in
1739 filenames that are involved during the build. This change affects
1740 only installation paths, so that `make install' does not bomb out
1741 in packages configured with
1742 ./configure --prefix '/c/Program Files'
1744 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1745 POSIXLY_CORRECT is set.
1747 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1748 since Autoconf 2.54, which defines LIBOBJS itself.
1750 - Fix a potential (but unlikely) race condition in parallel elisp
1751 builds. (Introduced in 1.7.3.)
1753 - Do not assume that users override _DEPENDENCIES in all conditions
1754 where Automake will try to define them.
1756 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1757 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1760 This fix also affects the $(mkdir_p) variable defined since
1761 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1762 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1764 - Secure temporary directory creation in `make distcheck'. (PR/413)
1766 - Do not generate two build rules for `parser.h' when the
1767 parser appears in two different conditionals.
1769 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1770 checking. Usually ./configure will not pick this shell; so this
1771 fix only helps cases where the shell is forced to /bin/sh.
1773 * Bugs introduced by 1.8:
1775 - In some situations (hand-written `m4_include's), aclocal would
1776 call the `File::Spec->rel2abs' method, which was only introduced
1777 in Perl 5.6. This new version reestablish support Perl 5.005.
1779 It is likely that the next major Automake releases will require at
1780 least Perl 5.6. Consider upgrading your development environment
1781 if you are still using the five-year-old Perl 5.005.
1783 - Automake would sometimes fail to define rules for targets listed
1784 in variables defined in multiple conditions. For instance on
1790 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1791 `b.$(OBJEXT): b.c' rule.
1793 * New sections in manual:
1795 - Third-Party Makefiles: how to interface third party Makefiles.
1796 - Upgrading: upgrading packages to newer Automake versions.
1797 - Multiple Outputs: handling tools that produce many outputs.
1799 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1803 * A (well known) portability bug slipped in the changes made to
1804 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1805 install anything on Tru64.
1807 * Fix install rules for conditionally built python files. (This never
1810 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1814 * Bugs introduced by 1.8:
1816 - Fix Config.pm import error with old Perl versions (at least
1817 5.005_03). One symptom is that aclocal could not find its macro
1820 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1821 created by `make install' are always world readable, even if the
1822 installer happens to have an overly restrictive umask (e.g. 077).
1823 This was a mistake and has been reverted. There are at least two
1824 reasons why we must not use `-m 0755':
1825 - it causes special bits like SGID to be ignored,
1826 - it may be too restrictive (some setups expect 775 directories).
1828 - Fix aclocal to honor definitions located in files which have been
1829 m4_included manually. aclocal 1.8 had been updated to check
1830 m4_included files for new requirements, but forgot that these
1831 m4_included files can also provide new definitions.
1833 Note that if you have such a setup, we recommend you get rid of
1834 it. In the past, there was a reason to m4_include files manually:
1835 aclocal used to duplicate entire M4 files into aclocal.m4, even
1836 files that were distributed. Some packages were therefore
1837 m4_including the distributed file directly, and playing some
1838 tricks to ensure aclocal would not copy that file to aclocal.m4,
1839 in order to limit the amount of duplication. Since aclocal 1.8.x
1840 will precisely output m4_includes for local M4 files, we recommend
1841 that you clean up your setup, removing all manual m4_includes and
1842 letting aclocal output them.
1844 - Output detailed menus in the Info version if the Automake manual,
1845 so that Emacs can locate the indexes.
1847 - configure.ac and configure were listed twice in DIST_COMMON (an
1848 internal variable where Automake lists configury files to
1849 distribute). This was harmless, but unaesthetic.
1851 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1852 This was an issue only in the Automake package itself, not in
1855 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1856 DEST:SRC. This was wrong, as some packages do
1857 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1860 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1861 argument. This caused two kinds of failures:
1862 - Rules installing data in a conditionally defined directory
1863 failed when that directory was undefined. In this case no
1864 argument was supplied.
1865 - `make installdirs' failed, because several directories were
1866 passed to $(mkdir_p). This was an issue only on platform
1867 were $(mkdir_p) is implemented with `install-sh -d'.
1868 $(mkdir_p) as been changed to accept 0 or more arguments, as
1871 * Long-standing bugs:
1873 - Fix an unexpected diagnostic occurring when users attempt
1874 to override some internal variables that Automake appends to.
1876 - aclocal now scans configure.ac for macro definitions (PR/319).
1878 - Fix a portability issue with OSF1/Tru64 Make. If a directory
1879 distributes files which are outside itself (this usually occurs
1880 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
1881 from a parent package), then `make distcheck' fails due to an
1882 optimization performed by OSF1/Tru64 Make in its VPATH handling.
1883 (tests/subpkg2.test failure)
1885 - Fix another portability issue with Sun and OSF1/Tru64 Make.
1886 In a VPATH-build configuration, `make install' would install
1887 nobase_ files to wrong locations.
1889 - Fix a Perl `uninitialized value' diagnostic occurring when
1890 automake complains that a Texinfo file does not have a
1891 @setfilename statement.
1893 - Erase config.status.lineno during `make distclean'. This file
1894 can be created by config.status. Automake already knew about
1895 configure.lineno, but forgot config.status.lineno.
1897 - Distribute all files, even those which are built and installed
1898 conditionally. This change affects files listed in conditionally
1899 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
1900 as well as those listed in conditionally defined dist_*_DATA,
1901 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
1903 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
1904 doesn't conform to POSIX.
1906 - Normalize help strings for configure variables and options added
1911 - Check for python2.4 in AM_PATH_PYTHON.
1913 * Spurious failures in test suite:
1915 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
1916 tests/ltconv.test: fix failures with CVS Libtool.
1917 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
1918 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
1919 fix failures with old Texinfo versions.
1921 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1927 - The NEWS file is more verbose.
1931 - Autoconf 2.58 or greater is required.
1935 - Default source file names in the absence of a _SOURCES declaration
1936 are made by removing any target extension before appending `.c', so
1937 to make the libtool module `foo.la' from `foo.c', you only need to
1940 lib_LTLIBRARIES = foo.la
1941 foo_la_LDFLAGS = -module
1943 For backward compatibility, foo_la.c will be used instead of
1944 foo.c if this file exists or is the explicit target of a rule.
1945 However -Wobsolete will warn about this deprecated naming.
1947 - AR's `cru' flags are now set in a global ARFLAGS variable instead
1948 of being hard-coded in each $(AR) invocation, so they can be
1949 substituted from configure.ac. This has been requested by people
1950 dealing with non-POSIX ar implementations.
1952 - New warning option: -Woverride. This will warn about any user
1953 target or variable definitions which override Automake
1956 - Texinfo rules back up and restore info files when makeinfo fails.
1958 - Texinfo rules now support the `html' target.
1959 Running this requires Texinfo 4.0 or greater.
1961 `html' is a new recursive target, so if your package mixes
1962 hand-crafted `Makefile.in's with Automake-generated
1963 `Makefile.in's, you should adjust the former to support (or
1964 ignore) this target so that `make html' recurses successfully. If
1965 you had a custom `html' rule in your `Makefile.am', it's better to
1966 rename it as `html-local', otherwise your rule will override
1967 Automake's new rule (you can check that by running `automake
1968 -Woverride') and that will stop the recursion to subdirectories.
1970 Last but not least, this `html' rule is declared PHONY, even when
1971 overridden. Fortunately, it appears that few packages use a
1972 non-PHONY `html' rule.
1974 - Any file which is m4_included from configure.ac will appear as a
1975 configure and Makefile.in dependency, and will be automatically
1978 - The rules for rebuilding Makefiles and Makefile.ins will now
1979 rebuild all Makefiles and all Makefile.ins at once when one of
1980 configure's dependencies has changed. This is considerably faster
1981 than previous implementations, where config.status and automake
1982 were run separately in each directory (this still happens when you
1983 change a Makefile.am locally, without touching configure.ac or
1984 friends). Doing this also solves a longstanding issue: these
1985 rebuild rules failed to work when adding new directories to the
1986 tree, forcing you to run automake manually.
1988 - For similar reasons, the rules to rebuild configure,
1989 config.status, and aclocal.m4 are now defined in all directories.
1990 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
1991 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
1992 should better define them in all directories. This is easily done
1993 using an AC_SUBST (make sure you prefix these dependencies with
1994 $(top_srcdir) since this variable will appear at different
1995 levels of the build tree).
1997 - aclocal will now use `m4_include' instead of copying local m4
1998 files into aclocal.m4. (Local m4 files are those you ship with
1999 your project, other files will be copied as usual.)
2001 Because m4_included files are automatically distributed, it means
2002 for most projects there is no point in EXTRA_DISTing the list of
2003 m4 files which are used. (You can probably get rid of
2004 m4/Makefile.am if you had one.)
2006 - aclocal will avoid touching aclocal.m4 when possible, so that
2007 Autom4te's cache isn't needlessly invalidated. This behavior can
2008 be switched off with the new `--force' option.
2010 - aclocal now uses Autoconf's --trace to detect macros which are
2011 actually used and will no longer include unused macros simply
2012 because they where mentioned. This was often the case for macros
2013 called conditionally.
2015 - New options no-dist and no-dist-gzip.
2017 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2018 py-compile, and ylwrap, now all understand --version and --help.
2020 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2021 links as part of the distclean target and including source files in
2024 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2025 argument. The latter can be used to override the default behavior
2026 (which is to abort).
2028 - Automake will exit with $? = 63 on version mismatch. (So does
2029 Autoconf 2.58) missing knows this, and in this case it will
2030 emulate the tools as if they were absent. Because older versions
2031 of Automake and Autoconf did not use this exit code, this change
2032 will only be useful in projects generated with future versions of
2035 - When using AC_CONFIG_FILES with multiple input files, Automake
2036 generates the first ".in" input file for which a ".am" exists.
2037 (Former versions would try to use only the first input file.)
2039 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2040 idiom to disable byte-compilation of lisp_LISP files, it is
2041 recommended that you switch to using lisp_DATA. Note that
2042 this is not strictly equivalent: lisp_DATA will install elisp
2043 files even if emacs is not installed, while *_LISP do not
2044 install anything unless emacs is found.
2046 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2047 available. This selection is achieved through the Makefile
2048 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2049 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2050 `$(install_sh) -m 0755 -d'.
2054 - Because `mkdir -p' is available on most platforms, and we can use
2055 `install-sh -d' when it is not, the use of the mkinstalldirs
2056 script is being phased out. `automake --add-missing' no longer
2057 installs it, and if you remove mkinstalldirs from your package,
2058 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2060 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2061 gettextize and autopoint will install it when needed. Automake
2062 will continue to define the $(mkinstalldirs) and to distribute
2063 mkinstalldirs when this script is in the source tree.
2065 - AM_PROG_CC_STDC is now empty. The content of this macro was
2066 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2067 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2068 renaming should be safe, even if you have to support several,
2069 versions of Automake, because AC_PROG_CC defines this variable
2070 since Autoconf 2.54.)
2072 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2073 variable to override the aclocal.m4 dependencies computed
2074 (inaccurately) by older versions of Automake. Because Automake
2075 now tracks configure's m4 dependencies accurately (see m4_include
2076 above), the use of ACLOCAL_M4_SOURCES should be considered
2077 obsolete and will be flagged as such when running `automake
2082 - Defining programs conditionally using Automake conditionals no
2083 longer leads to a combinatorial explosion. The following
2084 construct used to be troublesome when used with dozens of
2099 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2101 - Due to implementation constraints, previous versions of Automake
2102 proscribed multiple conditional definitions of some variables
2112 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2113 This restriction has been lifted, and these variables now
2114 support multiple conditional definitions as do other variables.
2116 - Cleanup the definitions of $(distdir) and $(top_distdir).
2117 $(top_distdir) now points to the root of the distribution
2118 directory created during `make dist', as it did in Automake 1.4,
2119 not to the root of the build tree as it did in intervening
2120 versions. Furthermore these two variables are now only defined in
2121 the top level Makefile, and passed to sub-directories when running
2124 - The --no-force option now correctly checks the Makefile.in's
2125 dependencies before deciding not to update it.
2127 - Do not assume that make files are called Makefile in cleaning rules.
2129 - Update .info files in the source tree, not in the build tree. This
2130 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2131 used to update these files in the build tree (previous versions did
2132 it in the source tree too), and it caused several problems, varying
2133 from mere annoyance to portability issues.
2135 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2136 when --add-missing and --force-missing are used. For backward
2137 compatibility --add-missing will continue to install COPYING (in
2138 `gnu' strictness) when none of these three files exist, but this
2139 use is deprecated: you should better choose a license yourself and
2140 install it once for all in your source tree (and in your code
2143 - Fix ylwrap so that it does not overwrite header files that haven't
2144 changed, as the inline rule already does.
2146 - User-defined rules override automake-defined rules for the same
2147 targets, even when rules do not have commands. This is not new
2148 (and was documented), however some of the automake-generated
2149 rules have escaped this principle in former Automake versions.
2150 Rules for the following targets are affected by this fix:
2152 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2153 info, info-am, install-data-am, install-exec-am, install-info,
2154 install-info-am, install-man, installcheck-am, maintainer-clean,
2155 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2156 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2158 Practically it means that an attempt to supplement the dependencies
2159 of some target, as in
2161 clean: my-clean-rule
2163 will now *silently override* the automake definition of the
2164 rule for this target. Running `automake -Woverride' will diagnose
2165 all such overriding definitions.
2167 It should be noted that almost all of these targets support a *-local
2168 variant that is meant to supplement the automake-defined rule
2169 (See node `Extending' in the manual). The above rule should
2172 clean-local: my-clean-rule
2174 These *-local targets have been documented since at least
2175 Automake 1.2, so you should not fear the change if you have
2176 to support multiple automake versions.
2180 - The Automake manual is now distributed under the terms of the GNU FDL.
2182 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2184 - core dumps are no longer removed by the cleaning rules. There are
2185 at least three reasons for this:
2186 1. These files should not be created by any build step,
2187 so their removal do not fit any of the cleaning rules.
2188 Actually, they may be precious to the developer.
2189 2. If such file is created during a build, then it's clearly a
2190 bug Automake should not hide. Not removing the file will
2191 cause `make distcheck' to complain about its presence.
2192 3. Operating systems have different naming conventions for
2193 core dump files. A core file on one system might be a
2194 completely legitimate data file on another system.
2196 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2197 defined by Automake. This means that any definition in the
2198 environment will be used, unless overridden in the Makefile.am or
2199 on the command line. The old behavior, where these variables were
2200 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2201 AC_ARG_VARing each variable from configure.ac.
2203 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2204 documented. (The is not a new feature, these variables have
2205 been there since at least Automake 1.4.)
2207 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2209 Bugs fixed in 1.7.9:
2210 * Fix install-strip to work with nobase_ binaries.
2211 * Fix renaming of #line directives in ylwrap.
2212 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2214 Bugs fixed in 1.7.8:
2215 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2216 * Fix detection of Debian's install-info, broken since version 1.5.
2217 (Debian bug #213524).
2218 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2219 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2221 Bugs fixed in 1.7.7:
2222 * The implementation of automake's --no-force option is unreliable,
2223 so this option is ignored in this version. A real fix will appear in
2224 Automake 1.8. (Debian Bug #206299)
2225 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2226 argument is given. (PR/399)
2227 * Do not warn about leading `_' in variable names, even with -Wportability.
2228 * Support user redefinitions of TEXINFO_TEX.
2229 * depcomp: support AIX Compiler version 6.
2230 * Fix missing rebuilds during `make dist' with BSD make.
2231 (Could produce tarballs containing out-of-date files.)
2232 * Resurrect multilib support.
2233 * Noteworthy manual updates:
2234 - Extending aclocal: how to write m4 macros that won't trigger warnings
2236 - A Shared Library: Rewrite and split into subsections.
2238 Bugs fixed in 1.7.6:
2239 * Fix depcomp's icc mode for ICC 7.1.
2240 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2241 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2242 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2243 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2244 * Remove Latin-1 characters from elisp-comp.
2245 * Update the manual's @dircategory to match the Free Software Directory.
2247 Bugs fixed in 1.7.5:
2248 * Update install-sh's license to remove an advertising clause.
2249 (Debian bug #191717)
2250 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2251 that caused invalid Makefile.ins to be generated.
2252 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2253 * New FAQ entry: renamed objects.
2255 Bugs fixed in 1.7.4:
2256 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2257 the Emacs implementation)
2258 * Fix output of aclocal.m4 dependencies in subdirectories.
2259 * Use `mv -f' instead of `mv' in fastdep rules.
2260 * Upgrade mdate-sh to work on OS/2.
2261 * Don't byte-compile elisp files when ELCFILES is set empty.
2262 (this documented feature was broken by 1.7.3)
2263 * Diagnose trailing backslashes on last line of Makefile.am.
2264 * Diagnose whitespace following trailing backslashes.
2265 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2266 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2268 * `make install' will build `BUILT_SOURCES' first.
2269 * Minor documentation fixes.
2271 Bugs fixed in 1.7.3:
2272 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2273 * Query distutils for `pythondir' and `pythonexecdir', instead of
2274 using an hardcoded path. This should allow builds on 64-bit
2275 distributions that usually use lib64/ instead of lib/.
2276 * AM_PATH_PYTHON will also search for python2.3.
2277 * elisp files are now built all at once instead of one by one. Besides
2278 incurring a speed-up, this is required to support interdependent elisp files.
2279 * Support for DJGPP:
2280 - `make distcheck' will now work in `_inst/' and `_build' instead
2281 of `=inst/' and `=build/'
2282 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2283 - install/uninstall `*.i[0-9][0-9]'-style info files
2284 - more changes that affect only the Automake package (not its output)
2285 * Fix some incompatibilities with upcoming perl-5.10.
2286 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2287 PACKAGE and VERSION.
2289 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2290 is troublesome with gcc and Solaris compilers. (PR/385)
2291 - makedepend mode: work with Libtool. (PR/385 too)
2293 * better support for unusual gettext setups, such as multiple po/ directories
2295 - Flag missing po/ and intl/ directories as warnings, not errors.
2296 - Disable these warnings if po/ does not exist.
2297 * Noteworthy manual updates:
2299 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2301 - Document `AM_YFLAGS = -d'. (PR/382)
2303 Bugs fixed in 1.7.2:
2304 * Fix installation and uninstallation of Info files built in subdirectories.
2305 * Do not run `./configure --with-included-gettext' during `make distcheck'
2306 if AM_GNU_GETTEXT([external]) is used.
2307 * Correctly uninstall renamed man pages.
2308 * Do not strip escaped newline in variables defined in one condition
2309 and augmented in another condition.
2310 * Fix ansi2knr rules for LIBOBJS sources.
2311 * Clean all known Texinfo index files, not only those which appear to
2312 be used, because we cannot know which indexes are used in included files.
2313 (PR/375, Debian Bug #168671)
2314 * Honor only the first @setfilename seen in a Texinfo file.
2315 * Treat "required file X not found" diagnostics as errors (exit status 1).
2316 * Don't complain that a required file is not found when it is a Makefile
2318 * Don't use single suffix inference rules when building `.info'-less
2319 Info files, for the sake of Solaris make.
2320 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2321 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2322 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2323 * Fix building of deansified files from subdirectories. (PR/370)
2324 * Add missing `fi' in the .c->.obj rules.
2325 * Improve install-sh to work even when names contain spaces or certain
2326 (but not all) shell metachars.
2327 * Fix the following spurious failures in the test suite:
2328 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2329 * Noteworthy manual updates:
2330 - Augment the section about BUILT_SOURCES.
2331 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2333 Bugs fixed in 1.7.1:
2334 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2336 * Aclocal should now recognize macro names containing parentheses, e.g.
2337 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2338 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2340 * Install Python files even if they were built. (PR/369)
2341 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2342 version might not be defined in the latter. (PR/358)
2343 * Reorder arguments passed to a couple of commands, so things works
2344 when POSIXLY_CORRECT=1.
2345 * Fix a regex that can cause Perl to segfault on large input.
2347 * Fix distribution of packages that have some sources defined conditionally,
2348 as in the `Conditional compilation using Automake conditionals' example
2350 * Fix spurious test suite failures on IRIX.
2351 * Don't report a required variable as undefined if it has been
2352 defined conditionally for the "right" conditions.
2353 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2354 `make distcheck' fails.
2355 * Fix distribution of included Makefile fragment, so we don't create
2356 spurious directories in the distribution. (PR/366)
2357 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2360 * Autoconf 2.54 is required.
2361 * `aclocal' and `automake' will no longer warn about obsolete
2362 configure macros. This is done by `autoconf -Wobsolete'.
2363 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2364 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2365 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2366 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2367 `configure.ac' for you.
2368 * Support for per-program and per-library `_CPPFLAGS'.
2369 * New `ctags' target (builds CTAGS files).
2370 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2371 (see `automake --help' or the manual for a list of them).
2372 * Honor the WARNINGS environment variable.
2373 * Omit the call to depcomp when using gcc3: call the compiler directly.
2374 * A new option, std-options, tests that programs support --help and --version
2375 when `make installcheck' is run. This is enabled by --gnits.
2376 * Texinfo rules now support the `ps' and `pdf' targets.
2377 * Info files are now created in the build directory, not the source directory.
2378 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2380 * `make distcheck' will enforce DESTDIR support by attempting
2382 * `+=' can be used in conditionals, even if the augmented variable
2383 was defined for another condition.
2384 * Makefile fragments (inserted with `include') are always distributed.
2385 * Use Autoconf's --trace interface to inspect configure.ac and get
2386 a more accurate view of it.
2387 * Add support for extending aclocal's default macro search path
2388 using a `dirlist' file within the aclocal directory.
2389 * automake --output-dir is deprecated.
2390 * The part of the distcheck target that checks whether uninstall actually
2391 removes all installed files has been moved in a separate target,
2392 distuninstallcheck, so it can be overridden easily.
2396 * Support for AM_INIT_GETTEXT([external])
2397 * Bug fixes, including:
2398 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2399 - nobase_ programs and scripts honor --program-transform correctly.
2400 - Erase configure.lineno during `make distclean'.
2401 - Erase YACC and LEX outputs during `make maintainer-clean'.
2404 * Many bug fixes, including:
2405 - Requiring the current version works.
2406 - Fix "$@" portability issues (for Zsh).
2407 - Fix output of dummy dependency files in presence of post-processed
2409 - Don't compute dependencies in background to avoid races with libtool.
2410 - Fix handling of _OBJECTS variables for targets sharing source variables.
2411 - Check dependency mode for Java when AM_PROG_GCJ is used.
2414 * automake --output-dir is deprecated
2415 * Many bug fixes, including:
2416 - Don't choke on AM_LDFLAGS definitions.
2417 - Clean libtool objects from subdirectories.
2418 - Allow configure variables with reserved suffix and unknown prefix
2419 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2420 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2423 * Autoconf 2.52 is required.
2424 * automake no longer run libtoolize.
2425 This is the job of autoreconf (from GNU Autoconf).
2426 * `dist' generates all the archive flavors, as did `dist-all'.
2427 * `dist-gzip' generates the Gzip tar file only.
2428 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2429 explosion. Makefile.in's keep a reasonable size.
2430 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2431 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2433 * `#line' of Lex and Yacc files are properly set.
2434 * EXTRA_DIST can contain generated directories.
2435 * Support for dot-less extensions in suffix rules.
2436 * The part of the distcheck target that checks whether distclean actually
2437 cleans all built files has been moved in a separate target, distcleancheck,
2438 so it can be overridden easily.
2439 * `make distcheck' will pass additional options defined in
2440 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2441 * Fixed CDPATH portability problems, in particular for MacOS X.
2442 * Fixed handling of nobase_ targets.
2443 * Fixed support of implicit rules leading to .lo objects.
2444 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2445 * Added uninstall-hook target
2446 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2447 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2448 (Note that "pkgname" is not "tarname", see the manual for details.)
2449 It is also possible to pass a list of global Automake options as
2450 first argument to this new form of AM_INIT_AUTOMAKE.
2451 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2452 to be a real assembler.
2453 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2454 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2455 * aclocal and automake are also installed with the version number
2456 appended, and some of the install directory names have changed.
2457 This lets you have multiple versions installed simultaneously.
2458 * Support for parsers and lexers in subdirectories.
2461 * Support for `configure.ac'.
2462 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2463 * `make dist-all' is much faster.
2464 * Allows '@' AC_SUBSTs in macro names.
2465 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2466 * User-side dependency tracking. Developers no longer need GNU make
2468 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2469 * Most files are correctly handled if they appear in subdirs
2470 For instance, a _DATA file can appear in a subdir
2471 * GNU tar is no longer required for `make dist'
2472 * Added support for `dist_' and `nodist_' prefixes
2473 * Added support for `nobase_' prefix
2474 * Compiled Java support
2475 * Support for per-executable and per-library compilation flags
2479 * Added support for the Fortran 77 programming language.
2480 * Re-indexed the Automake Texinfo manual.
2481 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2482 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2483 * Support for latest autoconf, including support for objext
2484 * Can now put `.' in SUBDIRS to control build order
2485 * `include' command and `+=' support for macro assignment
2486 * Dependency tracking no long susceptible to deleted header file problem
2487 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2492 * Better Cygwin32 support
2493 * Support for suffix rules with _SOURCES variables
2494 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2495 * @LEXLIB@ no longer required when lex source seen
2496 Lex support in `missing', and new lex macro. Update your missing script.
2497 * Built-in support for assembly
2498 * aclocal gives error if `AM_' macro not found
2499 * Passed YFLAGS, not YACCFLAGS, to yacc
2500 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2501 * Dependencies computed as a side effect of compilation
2502 * Preliminary support for Java
2503 * DESTDIR support at "make install" time
2504 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2508 * Better DejaGnu support
2509 * Added no-installinfo option
2510 * Added Emacs Lisp support
2511 * Added --no-force option
2512 * Included `aclocal' program
2513 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2514 * Now uses `AM_' macro names everywhere
2515 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2516 ansi2knr now works correctly on K&R sources
2517 * Better C++, yacc, lex support
2518 * Will compute _DEPENDENCIES variables automatically if not supplied
2519 * Will interpolate $(...) and ${...} when examining contents of a variable
2520 * .deps files now in build directory, not source directory; dependency
2521 handling generally rewritten
2522 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2523 * can now put config.h into a subdir
2524 * Added dist-all target
2525 * Support for install-info program (see texinfo 3.9)
2526 * Support for "yacc -d"
2527 * configure substitutions are automatically discovered and included
2528 in generated Makefile.in
2529 * Special --cygnus mode
2530 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2531 when making distribution. Some dependencies are auto-ignored.
2532 * Changed how libraries are specified in _LIBRARIES variable
2533 * Full libtool support, from Gord Matzigkeit
2534 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2535 AM_CONFIG_HEADER handles it automatically
2536 * Texinfo output files no longer need .info extension
2537 * Added `missing' support
2539 * Conditionals in Makefile.am, from Ian Taylor
2543 * distcheck target runs install and installcheck targets
2544 * Added preliminary support for DejaGnu.
2549 * More libtool fixes from Gord Matzigkeit; libtool support is still
2551 * Added support for jm_MAINTAINER_MODE
2553 * New "distcheck" target
2557 * mkinstalldirs and mdate-sh now appear in directory specified by
2559 * Removed DIST_SUBDIRS, DIST_OTHER
2560 * AC_ARG_PROGRAM only required when an actual program exists
2561 * dist-hook target now run before distribution packaged up; idea from
2562 Dieter Baron. Other hooks exist, too.
2563 * Preliminary (unfinished) support for libtool
2564 * Added short option names.
2565 * Better "dist" support when gluing together multiple packages
2569 * Documentation updates (many from François Pinard)
2570 * strictness `normal' now renamed to `foreign'
2571 * Renamed --install-missing to --add-missing
2572 * Now handles AC_CONFIG_AUX_DIR
2573 * Now handles TESTS macro
2574 * DIST_OTHER renamed to EXTRA_DIST
2575 * DIST_SUBDIRS is deprecated
2576 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2577 * Better error messages in many cases
2578 * Program names are canonicalized
2579 * Added "check" prefix; from Gord Matzigkeit
2583 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2584 * Beginnings of a test suite
2585 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2586 * Doesn't print anything when running
2587 * Beginnings of MAINT_CHARSET support
2588 * Can specify version in AUTOMAKE_OPTIONS
2589 * Most errors recognizable by Emacs' M-x next-error
2590 * Added --verbose option
2591 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2592 configure-generated names
2593 * Required macros now distributed in aclocal.m4
2595 * --strictness=gnu is default
2599 * More sophisticated configure.in scanning; now understands ALLOCA and
2600 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2601 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2602 * CONFIG_HEADER variable now obsolete
2603 * Can handle multiple Texinfo sources
2604 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2605 * HEADERS variable no longer needed; now can put .h files directly into
2606 foo_SOURCES variable.
2607 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2608 corresponding ".in" files are included in the distribution.
2611 * Added --gnu and --gnits options
2612 * More standards checking
2614 * Cleaned up 'dist' targets
2615 * Added AUTOMAKE_OPTIONS variable and several options
2616 * Now scans configure.in to get some information (preliminary)
2619 * Works with Perl 4 again
2622 * Added --install-missing option.
2623 * Pretty-prints generated macros and rules
2624 * Comments in Makefile.am are placed more intelligently in Makefile.in
2625 * Generates .PHONY target
2626 * Rule or macro in Makefile.am now overrides contents of Automake file
2627 * Substantial cleanups from François Pinard
2631 * Works with Perl 4 again.
2634 * New uniform naming scheme.
2635 * --strictness option
2637 * '.c' files corresponding to '.y' or '.l' files are automatically
2639 * Many bug fixes and cleanups
2642 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2645 * Bug fixes in 'clean' code.
2646 * Now generates 'installdirs' target.
2647 * man page installation reworked.
2648 * 'make dist' no longer re-creates all Makefile.in's.
2651 * Reimplemented in Perl
2652 * Added --amdir option (for debugging)
2653 * Texinfo support cleaned up.
2654 * Automatic de-ANSI-fication cleaned up.
2655 * Cleaned up 'clean' targets.
2658 * Automatic dependency tracking
2659 * More documentation
2660 * New variables DATA and PACKAGEDATA
2661 * SCRIPTS installed using $(INSTALL_SCRIPT)
2662 * No longer uses double-colon rules
2664 * Changes in advance of internationalization
2668 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2670 This program is free software; you can redistribute it and/or modify
2671 it under the terms of the GNU General Public License as published by
2672 the Free Software Foundation; either version 2, or (at your option)
2675 This program is distributed in the hope that it will be useful,
2676 but WITHOUT ANY WARRANTY; without even the implied warranty of
2677 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2678 GNU General Public License for more details.
2680 You should have received a copy of the GNU General Public License
2681 along with this program. If not, see <http://www.gnu.org/licenses/>.