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". This kind of fixes
20 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 and deprecation, but no backward
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 - Automake 2.0 will require Autoconf 2.70 or later (which is still
43 unreleased at the moment of writing, but is planned to be released
44 before Automake 2.0 is).
46 - Automake 2.0 will drop support for the long-deprecated 'configure.in'
47 name for the Autoconf input file. You are advised to start using the
48 recommended name 'configure.ac' instead, ASAP.
50 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated
51 in Automake 2.0 (where it will raise warnings in the "obsolete"
52 category). You are advised to start relying on the new Automake
53 support for AC_CONFIG_MACRO_DIRS instead (which was introduced in
56 - Automake 2.0 will remove support for automatic dependency tracking
57 with the SGI C/C++ compilers on IRIX. The SGI depmode has been
58 reported broken "in the wild" already, and we don't think investing
59 time in debugging and fixing is worthwhile, especially considering
60 that SGI has last updated those compilers in 2006, and is expected
61 to retire support for them in December 2013:
62 <http://www.sgi.com/services/support/irix_mips_support.html>
64 - Future versions of Automake might remove support for MS-DOS and
65 Windows 95/98/ME (support for them was offered by relying on the
66 DJGPP project). Note however that both Cygwin and MSYS/MinGW on
67 modern Windows versions will continue to be fully supported.
69 - Automake-provided scripts and makefile recipes might (finally!)
70 start assuming a POSIX shell in Automake 2.0.
72 - Starting from Automake 2.0, third-party m4 files located in the
73 system-wide aclocal directory, as well as in any directory listed
74 in the ACLOCAL_PATH environment variable, will take precedence
75 over "built-in" Automake macros. For example (assuming Automake
76 is installed in the /usr/local hierarchy), a definition of the
77 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
78 should take precedence over the same-named automake-provided macro
79 (defined in '/usr/local/share/aclocal-2.0/vala.m4').
81 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
85 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
87 - The 'compile' script is now unconditionally required for all
88 packages that perform C compilation (note that if you are using
89 the '--add-missing' option, automake will fetch that script for
90 you, so you shouldn't need any explicit adjustment).
91 This new behaviour is needed to avoid obscure errors when the
92 'subdir-objects' option is used, and the compiler is an inferior
93 one that doesn't grasp the combined use of both the "-c -o"
94 options; see discussion about automake bug#13378 for more details:
95 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
96 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
98 - Automake will automatically enhance the AC_PROG_CC autoconf macro
99 to make it check, at configure time, that the C compiler supports
100 the combined use of both the "-c -o" options. This "rewrite" of
101 AC_PROG_CC is only meant to be temporary, since future Autoconf
102 versions should provide all the features Automake needs.
104 - The AM_PROG_CC_C_O is no longer useful, and its use is a no-op
105 now. Future Automake versions might start warning that this
106 macro is obsolete. For better backward-compatibility, this macro
107 still sets a proper 'ac_cv_prog_cc_*_c_o' cache variable, and
108 define the 'NO_MINUS_C_MINUS_O' C preprocessor symbol, but you
109 should really stop relying on that.
113 - Automake can now be instructed to place '.info' files generated from
114 Texinfo input in the builddir rather than in the srcdir; this is done
115 specifying the new automake option 'info-in-builddir'. This feature
116 was requested by the developers of GCC, GDB, GNU binutils and the GNU
117 bfd library. See the extensive discussion about automake bug#11034
120 - For quite a long time, Automake has been implementing an undocumented
121 hack which ensured that '.info' files which appeared to be cleaned
122 (by e.g. being listed in the CLEANFILES or DISTCLEANFILES variables)
123 were built in the builddir rather than in the srcdir; this hack was
124 introduced to ensure better backward-compatibility with packages such
125 as Texinfo, which did things like:
127 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
128 DISTCLEANFILES = texinfo texinfo-* info*.info*
129 # Do not create info files for distribution.
133 in order not to distribute generated '.info' files.
135 Now that we have the 'info-in-builddir' option that explicitly causes
136 generated '.info' files to be placed in the builddir, this hack should
137 be longer necessary, so we deprecate it with runtime warnings. It will
138 likely be removed altogether in Automake 1.14.
140 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
144 * Documentation fixes:
146 - The long-deprecated but still supported two-arguments invocation form
147 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
148 thing to do, given that support for such an usage might need to remain
149 in place for a unspecified amount of time in order to cater for people
150 who want to define the version number for their package dynamically at
151 configure runtime (unfortunately, Autoconf does not yet support this
152 scenario, so we cannot delegate the work to it).
154 - The serial testsuite harness is no longer reported as "deprecated",
155 but as "discouraged". We have no plan to remove it, not to make its
156 use cause runtime warnings.
158 - The parallel testsuite is no longer reported as "experimental"; it
159 is well tested, and should be stable now.
161 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
162 'dist-tarZ' options are obsolescent, and their use is deprecated
163 in the documentation.
165 - Other minor miscellaneous fixes and improvements; in particular,
166 some improvements in cross-references.
168 * Obsolescent features:
170 - Use of suffix-less info files (that can be specified through the
171 '@setfilename' macro in Texinfo input files) is discouraged, and
172 its use will raise warnings in the 'obsolete' category. Simply
173 use the '.info' extension for all your info files, transforming
176 @setfilename myprogram
180 @setfilename myprogram.info
182 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
183 is discouraged, and its use will raise warnings in the 'obsolete'
184 category. You are advised to simply use the '.texi' extension
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 no longer error out if the first local m4 directory (as
198 specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
199 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it merely report a
200 warning in the 'unsupported' category. This is done to support
201 some pre-existing real-world usages; refer to automake bug#13514
204 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
210 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
211 causes a clear and helpful error message, instead of obscure ones
212 (issue introduced in Automake 1.13).
214 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
220 - ylwrap renames properly header guards in generated header files
221 (*.h), instead of leaving Y_TAB_H.
223 - ylwrap now also converts header guards in implementation files
224 (*.c). Because ylwrap failed to rename properly #include in the
225 implementation files, current versions of Bison (e.g., 2.7)
226 duplicate the generated header file in the implementation file.
227 The header guard then protects the implementation file from
228 duplicate definitions from the header file.
230 * Version requirements:
232 - Autoconf 2.65 or greater is now required.
234 - The rules to build PDF and DVI output from Texinfo input now
235 require Texinfo 4.9 or later.
239 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
240 option) has been removed. See discussion about automake bug#11034
241 for more background: <http://debbugs.gnu.org/11034>.
243 - The deprecated aclocal option '--acdir' has been removed. You
244 should use the options '--automake-acdir' and '--system-acdir'
245 instead (which have been introduced in Automake 1.11.2).
247 - The following long-obsolete m4 macros have been removed:
249 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
250 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
251 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
252 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
253 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
254 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
255 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
256 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
257 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
258 of the now-removed automatic de-ANSI-fication
261 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
263 - Use of the long-deprecated two- and three-arguments invocation forms
264 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
265 though (albeit with a warning in the 'obsolete' category), to cater
266 for people who want to define the version number for their package
267 dynamically (e.g., from the current VCS revision). We'll have to
268 continue this support until Autoconf itself is fixed to allow better
269 support for such dynamic version numbers.
271 * Elisp byte-compilation:
273 - The byte compilation of '.el' files into '.elc' files is now done
274 with a suffix rule. This has simplified the compilation process, and
275 more importantly made it less brittle. The downside is that emacs is
276 now invoked once for each '.el' files, which cause some noticeable
277 slowdowns. These should however be mitigated on multicore machines
278 (which are becoming the norm today) if concurrent make ("make -j")
281 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
282 files in the same subdirectory; for example, byte-compiling of file
283 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
284 'foo.elc'. This behaviour is backward-incompatible with older
285 Automake versions, but it is more natural and more sane. See also
288 - The Emacs invocation performing byte-compilation of '.el' files honors
289 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
290 one is developer-reserved and the latter one user-reserved.
292 - The 'elisp-comp' script, once provided by Automake, has been rendered
293 obsoleted by the just-described changes, and thus removed.
295 * Changes to Automake-generated testsuite harnesses:
297 - The parallel testsuite harness (previously only enabled by the
298 'parallel-tests' option) is the default one; the older serial
299 testsuite harness will still be available through the use of the
300 'serial-tests' option (introduced in Automake 1.12).
302 - The 'color-tests' option is now unconditionally activated by default.
303 In particular, this means that testsuite output is now colorized by
304 default if the attached terminal seems to support ANSI escapes, and
305 that the user can force output colorization by setting the variable
306 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
307 for backward-compatibility, although it's a handled as a no-op now.
309 * Silent rules support:
311 - Support for silent rules is now always active in Automake-generated
312 Makefiles. So, although the verbose output is still the default,
313 the user can now always use "./configure --enable-silent-rules" or
314 "make V=0" to enable quieter output in the package he's building.
316 - The 'silent-rules' option has now become a no-op, preserved for
317 backward-compatibility only. In particular, its use no longer
318 disables the warnings in the 'portability-recursive' category.
322 - The rules to build PDF and DVI files from Texinfo input now require
323 Texinfo 4.9 or later.
325 - The rules to build PDF and DVI files from Texinfo input now use the
326 '--build-dir' option, to keep the auxiliary files used by texi2dvi
327 and texi2pdf around without cluttering the build directory, and to
328 make it possible to run the "dvi" and "pdf" recipes in parallel.
330 * Automatic remake rules and 'missing' script:
332 - The 'missing' script no longer tries to update the timestamp of
333 out-of-date files that require a maintainer-specific tool to be
334 remade, in case the user lacks such a tool (or has a too-old version
335 of it). It just gives a useful warning, and in some cases also a
336 tip about how to obtain such a tool.
338 - The missing script has thus become useless as a (poor) way to work
339 around the sketched-timestamps issues that can happen for projects
340 that keep generated files committed in their VCS repository. Such
341 projects are now encouraged to write a custom "fix-timestamps.sh"
342 script to avoid such issues; a simple example is provided in the
343 "CVS and generated files" chapter of the automake manual.
347 - The user can now define his own recursive targets that recurse
348 in the directories specified in $(SUBDIRS). This can be done by
349 specifying the name of such targets in invocations of the new
350 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
354 - Any failure in the recipe of the "tags", "ctags", "cscope" or
355 "cscopelist" targets in a subdirectory is now propagated to the
356 top-level make invocation.
358 - Tags are correctly computed also for files in _SOURCES variables that
359 only list files with non-standard suffixes (see automake bug#12372).
361 * Improvements to aclocal and related rebuilds rules:
363 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
364 are now traced by aclocal, and can be used to declare the local m4
365 include directories. Formerly, one had to specify it with an explicit
366 '-I' option to the 'aclocal' invocation.
368 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
369 Automake versions will warn about its use, and later version will
370 remove support for it altogether.
372 * The depcomp script:
374 - Dropped support for libtool 1.4.
376 - Various internal refactorings. They should cause no visible change,
377 but the chance for regression is there anyway, so please report any
378 unexpected or suspicious behaviour.
380 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
381 This should cause no problem, since icc 8.0 has been released in
382 December 2003 -- almost nine years ago.
384 - Support for tcc (the Tiny C Compiler) has been improved, and is now
385 handled through a dedicated 'tcc' mode.
389 - ylwrap generates header guards with a single '_' for series of non
390 alphabetic characters, instead of several. This is what Bison >=
393 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
395 Bugs fixed in 1.12.6:
397 * Python-related bugs:
399 - The default installation location for python modules has been improved
400 for Python 3 on Debian and Ubuntu systems, changing from:
402 ${prefix}/lib/python3/dist-packages
406 ${prefix}/lib/python3.x/site-packages
408 This change should ensure modules installed using the default ${prefix}
409 "/usr/local" are found by default by system python 3.x installations.
410 See automake bug#10227.
412 - Python byte-compilation supports the new layout mandated by PEP-3147,
413 with its __pycache__ directory (automake bug#8847).
415 * Build system issues:
417 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
418 Automake's own build system works correctly again (bug introduced
423 - The Vala-related tests has been changed to adjust to the removal of
424 the 'posix' profile in the valac compiler. See automake bug#12934
427 - Some spurious testsuite failures related to older tools and systems
430 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
436 - The AM_PROG_VALAC macro has been enhanced to takes two further
437 optional arguments; it's signature now being
439 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
440 [ACTION-IF-NOT-FOUND])
442 - By default, AM_PROG_VALAC no longer aborts the configure invocation
443 if the Vala compiler found is too old, but simply prints a warning
444 messages (as it did when the Vala compiler was not found). This
445 should avoid unnecessary difficulties for end users that just want
446 to compile the unmodified, distributed Vala-generated C sources,
447 but happens to have an old Vala compiler in their PATH. This fixes
450 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
451 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
452 This is a better default, because with it a triggered makefile rule
453 invoking a Vala compilation will clearly fail with an informative error
454 message like "valac: command not found", rather than silently, with
455 the error possibly going unnoticed or triggering harder-to-diagnose
456 fallout failures in later steps.
458 * Miscellaneous changes:
460 - automake and aclocal no longer honours the 'perllibdir' environment
461 variable. That had always been intended only as an hack required in
462 the testsuite, not meant for any use beyond that.
464 Bugs fixed in 1.12.5:
466 * Long-standing bugs:
468 - Automake no longer generates spurious remake rules invoking autoheader
469 to regenerate the template corresponding to header files specified after
470 the first one in AC_CONFIG_HEADERS (automake bug#12495).
472 - When wrapping Microsoft tools, the 'compile' script falls back to
473 finding classic 'libname.a' style libraries when 'name.lib' and
474 'name.dll.lib' aren't available.
476 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
480 * Warnings and deprecations:
482 - Warnings in the 'obsolete' category are enabled by default both in
483 automake and aclocal.
485 * Miscellaneous changes:
487 - Some testsuite weaknesses and spurious failures have been fixed.
489 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
493 * Miscellaneous changes:
495 - The '.m4' files provided by Automake no longer define serial numbers.
496 This should cause no difference in the behaviour of aclocal though.
498 - Some testsuite weaknesses and spurious failures have been fixed.
500 - There is initial support for automatic dependency tracking with the
501 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
503 Bugs fixed in 1.12.3:
505 * Long-standing bugs:
507 - Instead of renaming only self-references of files (typically for
508 #lines), ylwrap now also renames references to the other generated
509 files. This fixes support for GLR and C++ parsers from Bison (PR
510 automake/491 and automake bug#7648): 'parser.c' now properly
511 #includes 'parser.h' instead of 'y.tab.h'.
513 - Generated files unknown to ylwrap are now preserved. This fixes
514 C++ support for Bison (automake bug#7648): location.hh and the
515 like are no longer discarded.
517 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
521 * Warnings and deprecations:
523 - Automake now issues a warning (in the 'portability' category) if
524 'configure.in' is used instead of 'configure.ac' as the Autoconf
525 input file. Such a warning will also be present in the next
526 Autoconf version (2.70).
530 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
531 order (as done by the other recursive rules), rather than in the
532 inverse order. They used to do that in order to work a round a
533 limitation in an older implementation of the automatic dependency
534 tracking support, but that limitation had been lifted years ago
535 already, when the automatic dependency tracking based on side-effects
536 of compilation had been introduced.
538 - Cleaning rules for compiled objects (both "plain" and libtool) work
539 better when subdir objects are involved, not triggering a distinct
540 'rm' invocation for each such object. They do so by removing *any*
541 compiled object file that is in the same directory of a subdir
542 object. See automake bug#10697.
544 * Silent rules support:
546 - A new predefined $(AM_V_P) make variable is provided; it expands
547 to a shell conditional that can be used in recipes to know whether
548 make is being run in silent or verbose mode.
550 Bugs fixed in 1.12.2:
552 * SECURITY VULNERABILITIES!
554 - The 'distcheck' recipe no longer grants temporary world-write
555 permissions on the extracted distdir. Even if such rights were
556 only granted for a vanishingly small time window, the implied
557 race condition proved to be enough to allow a local attacker
558 to run arbitrary code with the privileges of the user running
559 "make distcheck". This is CVE-2012-3386.
561 * Long-standing bugs:
563 - The "recheck" targets behaves better in the face of build failures
564 related to previously failed tests. For example, if a test is a
565 compiled program that must be rerun by "make recheck", and its
566 compilation fails, it will still be rerun by further "make recheck"
567 invocations. See automake bug#11791.
569 * Bugs introduced by 1.12.1:
571 - Automake provides once again the '$(mkdir_p)' make variable and the
572 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
573 for better backward-compatibility.
575 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
579 * New supported languages:
581 - Support for Objective C++ has been added; it should work similarly to
582 the support for Objective C.
584 * Deprecated obsolescent features:
586 - Use of the long-deprecated two- and three-arguments invocation forms
587 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
588 category. Starting from some future major Automake release (likely
589 post-1.13), such usages will no longer be allowed.
591 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
592 now deprecated (its use triggers a warning in the 'obsolete' category).
593 It will be removed in the next major Automake release (1.13).
595 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
596 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
597 m4 macro are deprecated, eliciting a warning in the 'obsolete'
600 * Miscellaneous changes:
602 - The Automake test cases now require a proper POSIX-conforming shell.
603 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
604 be accepted. In most cases, the user shouldn't have to specify such
605 POSIX shell explicitly, since it will be looked up at configure time.
606 Still, when this lookup fails, or when the user wants to override its
607 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
608 to the shell that will be used to run the Automake test cases).
610 Bugs fixed in 1.12.1:
612 * Bugs introduced by 1.12:
614 - Several weaknesses in Automake's own build system and test suite
617 * Bugs introduced by 1.11.3:
619 - When given non-option arguments, aclocal rejects them, instead of
620 silently ignoring them.
622 * Long-standing bugs:
624 - When the 'color-tests' option is in use, forcing of colored testsuite
625 output through "AM_COLOR_TESTS=always" works even if the terminal is
626 a non-ANSI one, i.e., if the TERM environment variable has a value of
629 - Several inefficiencies and poor performances in the implementation
630 of the parallel-tests 'check' and 'recheck' targets have been fixed.
632 - The post-processing of output "#line" directives done the ylwrap
633 script is more faithful w.r.t. files in a subdirectory; for example,
634 if the processed file is "src/grammar.y", ylwrap will correctly
635 produce directives like:
636 #line 7 "src/grammar.y"
641 * Bugs with new Perl versions:
643 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
645 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
649 * Obsolete features removed:
651 - The never documented nor truly used script 'acinstall' has been
654 - Support for automatic de-ANSI-fication has been removed.
656 - The support for the "obscure" multilib feature has been removed
657 from Automake core (but remains available in the 'contrib/'
658 directory of the Automake distribution).
660 - Support for ".log -> .html" conversion and the check-html and
661 recheck-html targets has been removed from Automake core (but
662 remains available in the 'contrib/' directory of the Automake
665 - The deprecated 'lzma' compression format for distribution archives
666 has been removed, in favor of 'xz' and 'lzip'.
668 - The obsolete AM_WITH_REGEX macro has been removed.
670 - The long-deprecated options '--output-dir', '--Werror' and
671 '--Wno-error' have been removed.
673 - The chapter on the history of Automake has been moved out of the
674 reference manual, into a new dedicated Texinfo file.
678 - New 'cscope' target to build a cscope database for the source tree.
680 * Changes to Automake-generated testsuite harnesses:
682 - The new automake option 'serial-tests' has been introduced. It can
683 be used to explicitly instruct automake to use the older serial
684 testsuite harness. This is still the default at the moment, but it
685 might change in future versions.
687 - The 'recheck' target (provided by the parallel testsuite harness) now
688 depends on the 'all' target. This allows for a better user-experience
689 in test-driven development. See automake bug#11252.
691 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
692 and unexpected or internal error, or a failure to set up the test case
693 scenario) have their outcome reported as an 'ERROR' now. Previous
694 versions of automake reported such an outcome as a 'FAIL' (the only
695 difference with normal failures being that hard errors were counted
696 as failures even when the test originating them was listed in
699 - The testsuite summary displayed by the parallel-test harness has a
700 completely new format, that always list the numbers of passed, failed,
701 xfailed, xpassed, skipped and errored tests, even when these numbers
702 are zero (but using smart coloring when the color-tests option is in
705 - The default testsuite driver offered by the 'parallel-tests' option is
706 now implemented (partly at least) with the help of automake-provided
707 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
708 on code in the generated Makefile.in.
709 This has two noteworthy implications. The first one is that projects
710 using the 'parallel-tests' option should now either run automake with
711 the '--add-missing' option, or manually copy the 'test-driver' script
712 into their tree. The second, and more important, implication is that
713 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
714 no longer be used to define a test runner, and the command specified
715 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
716 program or script. For example, this is still a valid usage (albeit
719 TESTS_ENVIRONMENT = \
720 if test -n '$(STRICT_TESTS)'; then \
721 maybe_errexit='-e'; \
725 LOG_COMPILER = $(SHELL) $$maybe_errexit
727 OTOH, this is no longer a valid usage:
729 TESTS_ENVIRONMENT = \
730 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
734 TESTS_ENVIRONMENT = \
735 run_with_perl_or_shell () \
737 if grep -q '^#!.*perl' $$1; then
743 LOG_COMPILER = run_with_perl_or_shell
745 - The package authors can now use customary testsuite drivers within
746 the framework provided by the 'parallel-tests' testsuite harness.
747 Consistently with the existing syntax, this can be done by defining
748 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
750 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
751 to redirect/define file descriptors used by the test scripts.
753 - The parallel-tests harness generates now, in addition the '.log' files
754 holding the output produced by the test scripts, a new set of '.trs'
755 files, holding "metadata" derived by the execution of the test scripts;
756 among such metadata are the outcomes of the test cases run by a script.
758 - Initial and still experimental support for the TAP test protocol is
761 * Changes to Yacc and Lex support:
763 - C source and header files derived from non-distributed Yacc and/or
764 Lex sources are now removed by a simple "make clean" (while they were
765 previously removed only by "make maintainer-clean").
767 - Slightly backward-incompatible change, relevant only for use of Yacc
768 with C++: the extensions of the header files produced by the Yacc
769 rules are now modelled after the extension of the corresponding
770 sources. For example, yacc files named "foo.y++" and "bar.yy" will
771 produce header files named "foo.h++" and "bar.hh" respectively, where
772 they would have previously produced header files named simply "foo.h"
773 and "bar.h". This change offers better compatibility with 'bison -o'.
775 * Miscellaneous changes:
777 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
778 rather than 1, if the vala compiler found is too old.
780 - The build system of Automake itself now avoids the use of make
781 recursion as much as possible.
783 - Automake now prefers to quote 'like this' or "like this", rather
784 than `like this', in diagnostic message and generated Makefiles,
785 to accommodate the new GNU Coding Standards recommendations.
787 - Automake has a new option '--print-libdir' that prints the path of the
788 directory containing the Automake-provided scripts and data files.
790 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
792 - The rules to create pdf, dvi and ps output from Texinfo files now
793 works better with modern 'texi2dvi' script, by explicitly passing
794 it the '--clean' option to ensure stray auxiliary files are not
795 left to clutter the build directory.
797 - Automake can now generate silenced rules for texinfo outputs.
799 - Some auxiliary files that are automatically distributed by Automake
800 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
801 C sources) might now be listed in the DIST_COMMON variable in many
802 Makefile.in files, rather than in the top-level one.
804 - Messages of types warning or error from 'automake' and 'aclocal'
805 are now prefixed with the respective type, and presence of -Werror
808 - Automake's early configure-time sanity check now tries to avoid
809 sleeping for a second, which slowed down cached configure runs
810 noticeably. In that case, it will check back at the end of the
811 configure script to ensure that at least one second has passed, to
812 avoid time stamp issues with makefile rules rerunning autotools
815 - The warnings in the category 'extra-portability' are now enabled by
816 '-Wall'. In previous versions, one has to use '-Wextra-portability'
821 - Various minor bugfixes for recent or long-standing bugs.
823 * Bugs introduced by 1.11:
825 - The AM_COND_IF macro also works if the shell expression for the
826 conditional is no longer valid for the condition.
828 - The automake-provided parallel testsuite harness no longer fails
829 with BSD make used in parallel mode when there are test scripts in
830 a subdirectory, like in:
832 TESTS = sub/foo.test sub/bar.test
834 * Long-standing bugs:
836 - Automake's own build system finally have a real "installcheck" target.
838 - Vala-related cleanup rules are now more complete, and work better in
841 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
842 now automatically distributed also if the directory of the auxiliary
843 files coincides with the top-level directory.
845 - Automake now detects the presence of the '-d' flag in the various
846 '*YFLAGS' variables even when their definitions involve indirections
847 through other variables, such as in:
849 AM_YFLAGS = $(foo_opts)
851 - Automake now complains if a '*YFLAGS' variable has any conditional
852 content, not only a conditional definition.
854 - Explicit enabling and/or disabling of Automake warning categories
855 through the '-W...' options now always takes precedence over the
856 implicit warning level implied by Automake strictness (foreign, gnu
857 or gnits), regardless of the order in which such strictness and
858 warning flags appear. For example, a setting like:
859 AUTOMAKE_OPTIONS = -Wall --foreign
860 will cause the warnings in category 'portability' to be enabled, even
861 if those warnings are by default disabled in 'foreign' strictness.
863 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
865 Bugs fixed in 1.11.5:
867 * Bugs introduced by 1.11.3:
869 - Vala files with '.vapi' extension are now recognized and handled
870 correctly again. See automake bug#11222.
872 - Vala support work again for projects that contain some program
873 built from '.vala' (and possibly '.c') sources and some other
874 program built from '.c' sources *only*. See automake bug#11229.
876 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
880 * Miscellaneous changes:
882 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
883 symbol index) modifiers as well as the "s" action, as the symbol index
884 is created unconditionally by Microsoft lib. Also, the "q" (quick)
885 action is now a synonym for "r" (replace). Also, the script has been
886 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
888 - When the 'compile' script is used to wrap MSVC, it now accepts an
889 optional space between the -I, -L and -l options and their respective
890 arguments, for better POSIX compliance.
892 - There is an initial, experimental support for automatic dependency
893 tracking with tcc (the Tiny C Compiler). Its associated depmode is
894 currently recognized as "icc" (but this and other details are likely
895 to change in future versions).
897 - Automatic dependency tracking now works also with the IBM XL C/C++
898 compilers, thanks to the new new depmode 'xlc'.
900 Bugs fixed in 1.11.4:
902 * Bugs introduced by 1.11.2:
904 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
905 no longer cause spurious failures upon "make install".
907 - The user can now instruct the 'uninstall-info' rule not to update
908 the '${infodir}/dir' file by exporting the environment variable
909 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
910 with how the 'install-info' rule operates since automake 1.11.2.
912 * Long-standing bugs:
914 - It is now possible for a foo_SOURCES variable to hold Vala sources
915 together with C header files, as well as with sources and headers for
916 other supported languages (e.g., C++). Previously, only mixing C and
917 Vala sources was supported.
919 - If "aclocal --install" is used, and the first directory specified with
920 '-I' is non-existent, aclocal will now create it before trying to copy
923 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
924 install rules to create an empty $(foodir) directory; for example, if
925 Makefile.am contains something like:
929 pkglibexec_SCRIPTS += bar.sh
932 the $(pkglibexec) directory will not be created upon "make install".
934 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
938 * Miscellaneous changes:
940 - Automake's own build system is more silent by default, making use of
941 the 'silent-rules' option.
943 - The master copy of the 'gnupload' script is now maintained in gnulib,
946 - The 'missing' script no longer tries to wrap calls to 'tar'.
948 - "make dist" no longer wraps 'tar' invocations with the 'missing'
949 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
950 shouldn't be using BTW ;-) no longer invokes the 'missing' script
951 to wrap tar, but simply invokes the 'tar' program itself.
953 - "make dist" can now create lzip-compressed tarballs.
955 - In the Automake info documentation, the Top node and the nodes about
956 the invocation of the automake and aclocal programs have been renamed;
957 now, calling "info automake" will open the Top node, while calling
958 "info automake-invocation" and "info aclocal-invocation" will access
959 the nodes about the invocation of respectively automake and aclocal.
961 - Automake is now distributed as a gzip-compressed and an xz-compressed
962 tarball. Previously, bzip2 was used instead of xz.
964 - The last relics of Python 1.5 support have been removed from the
965 AM_PATH_PYTHON macro.
967 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
968 and adds them to the normal list of dependencies, but without
969 overwriting the foo_DEPENDENCIES variable, which is normally computed
972 Bugs fixed in 1.11.3:
974 * Bugs introduced by 1.11.2:
976 - Automake now correctly recognizes the prefix/primary combination
977 'pkglibexec_SCRIPTS' as valid.
979 - The parallel-tests harness no longer trips on sed implementations
980 with stricter limits on the length of input lines (problem seen at
983 * Long-standing bugs:
985 - The "deleted header file problem" for *.am files is avoided by stub
986 rules. This allows 'make' to trigger a rerun of 'automake' also if
987 some previously needed '.am' file has been removed.
989 - The 'silent-rules' option now generates working makefiles even
990 for the uncommon 'make' implementations that do not support the
991 nested-variables extension to POSIX 2008. For such 'make'
992 implementations, whether a build is silent is determined at
993 configure time, and cannot be overridden at make time with
994 "make V=0" or "make V=1".
996 - Vala support now works better in VPATH setups.
998 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1002 * Changes to aclocal:
1004 - The `--acdir' option is deprecated. Now you should use the new options
1005 `--automake-acdir' and `--system-acdir' instead.
1007 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1008 colon-separated list of additional directories to search after the
1009 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1010 and before the system acdir (by default ${prefix}/share/aclocal).
1012 * Miscellaneous changes:
1014 - The Automake support for automatic de-ANSI-fication has been
1015 deprecated. It will probably be removed in the next major Automake
1018 - The `lzma' compression scheme and associated automake option `dist-lzma'
1019 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1021 - You may adjust the compression options used in dist-xz and dist-bzip2.
1022 The default is now merely -e for xz, but still -9 for bzip; you may
1023 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1024 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1026 - The `compile' script now converts some options for MSVC for a better
1027 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1029 - The py-compile script now accepts empty arguments passed to the options
1030 `--destdir' and `--basedir', and complains about unrecognized options.
1031 Moreover, a non-option argument or a special `--' argument terminates
1032 the list of options.
1034 - A developer that needs to pass specific flags to configure at "make
1035 distcheck" time can now, and indeed is advised to, do so by defining
1036 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1037 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1038 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1039 user; still, the old Makefile.am files that used to define it will
1040 still continue to work as before.
1042 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1043 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1044 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1045 is run with -Wextra-portability and -Werror.
1047 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1048 file generated by automake-provided rules by defining the special make
1049 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1051 - The `install-info' rule can now be instructed not to create/update
1052 the `${infodir}/dir' file, by exporting the new environment variable
1053 `AM_UPDATE_INFO_DIR' to the value "no".
1055 Bugs fixed in 1.11.2:
1057 * Bugs introduced by 1.11:
1059 - The parallel-tests driver no longer produces erroneous results with
1060 Tru64/OSF 5.1 sh upon unreadable log files.
1062 - The `parallel-tests' test driver does not report spurious successes
1063 when used with concurrent FreeBSD make (e.g., "make check -j3").
1065 - When the parallel-tests driver is in use, automake now explicitly
1066 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1067 instead of issuing confusing and apparently unrelated error messages
1068 (e.g., "non-POSIX variable name", "bad characters in variable name",
1069 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1070 silently producing broken `Makefile.in' files.
1072 - The `silent-rules' option now truly silences all compile rules, even
1073 when dependency tracking is disabled. Also, when `silent-rules' is
1074 not used, `make' output no longer contains spurious backslash-only
1075 lines, thus once again matching what Automake did before 1.11.
1077 - The AM_COND_IF macro also works if the shell expression for the
1078 conditional is no longer valid for the condition.
1080 * Long-standing bugs:
1082 - The order of Yacc and Lex flags is fixed to be consistent with other
1083 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1084 $(LFLAGS), so that the user variables override the developer variables.
1086 - "make distcheck" now correctly complains also when "make uninstall"
1087 leaves one and only one file installed in $(prefix).
1089 - A "make uninstall" issued before a "make install", or after a mere
1090 "make install-data" or a mere "make install-exec" does not spuriously
1093 - Automake now warns about more primary/directory invalid combinations,
1094 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1096 - Rules generated by Automake now try harder to not change any files when
1097 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1098 Yacc source files and the rule to update config.h.
1100 - Several scripts and the parallel-tests testsuite driver now exit with
1101 the right exit status upon receiving a signal.
1103 - A per-Makefile.am setting of -Werror does not erroneously carry over
1104 to the handling of other Makefile.am files.
1106 - The code for automatic dependency tracking works around a Solaris
1107 make bug triggered by sources containing repeated slashes when the
1108 `subdir-objects' option was used.
1110 - The makedepend and hp depmodes now work better with VPATH builds.
1112 - Java sources specified with check_JAVA are no longer compiled for
1113 "make all", but only for "make check".
1115 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1116 and error out if `javadir' is undefined, instead of silently producing
1117 a broken Makefile.in.
1119 - aclocal and automake now honour the configure-time definitions of
1120 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1122 - The `install-info' recipe no longer tries to guess whether the
1123 `install-info' program is from Debian or from GNU, and adaptively
1124 change its behaviour; this has proven to be frail and easy to
1127 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1129 Bugs fixed in 1.11.1:
1131 - Lots of minor bugfixes.
1133 * Bugs introduced by 1.11:
1135 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1136 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1138 * Long standing bugs:
1140 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1141 even if the `--prefix' argument pointed outside of a system directory.
1142 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1143 `get_python_lib' function if it points outside the configured prefix,
1144 unless the `--prefix' argument was either `/usr' or below `/System'.
1146 - The testsuite does not try to change the mode of `ltmain.sh' files from
1147 a Libtool installation (symlinked to test directories) any more.
1149 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1150 tools are preferred in a cross-compile setup.
1152 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1153 This fixes a race condition where untrusted users could modify files
1154 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1155 build directory was world-searchable. This is CVE-2009-4029.
1157 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1161 * Version requirements:
1163 - Autoconf 2.62 or greater is required.
1165 * Changes to aclocal:
1167 - The autoconf version check implemented by aclocal in aclocal.m4
1168 (and new in Automake 1.10) is degraded to a warning. This helps
1169 in the common case where the Autoconf versions used are compatible.
1171 * Changes to automake:
1173 - The automake program can run multiple threads for creating most
1174 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1175 with interpreter-based threads enabled. Set the environment variable
1176 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1177 enable this experimental feature.
1179 * Changes to Libtool support:
1181 - Libtool generic flags are now passed to the install and uninstall
1184 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1185 config.lt is removed correctly now.
1187 * Languages changes:
1189 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1190 Fortran, and Ratfor).
1192 - For files with extension .f90, .f95, .f03, or .f08, the flag
1193 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1195 - Files with extension .sx are also treated as preprocessed assembler.
1197 - The default source file extension (.c) can be overridden with
1198 AM_DEFAULT_SOURCE_EXT now.
1200 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1203 - AM_PATH_PYTHON honors python's idea about the site directory.
1205 - There is initial support for the Vala programming language, when using
1206 Vala 0.7.0 or later.
1208 * Miscellaneous changes:
1210 - Automake development is done in a git repository on Savannah now, see
1212 http://git.sv.gnu.org/gitweb/?p=automake.git
1214 A read-only CVS mirror is provided at
1216 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1217 checkout -d automake HEAD
1219 - "make dist" can now create xz-compressed tarballs,
1220 as well as (deprecated?) lzma-compressed tarballs.
1222 - `automake --add-missing' will by default install the GPLv3 file as
1223 COPYING if it is missing. It will also warn that the license file
1224 should be added to source control. Note that Automake will never
1225 overwrite an existing COPYING file, even when the `--force-missing'
1228 - The manual is now distributed under the terms of the GNU FDL 1.3.
1230 - Automake ships and installs man pages for automake and aclocal now.
1232 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1234 - install-sh supports -C, which does not update the installed file
1235 (and its time stamps) if the contents did not change.
1237 - The `gnupload' script has been revamped.
1239 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1241 - The targets `install' and `uninstall' are more efficient now, in that
1242 for example multiple files from one Automake variable such as
1243 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1244 invocation if they do not have to be renamed.
1246 Both install and uninstall may sometimes enter (`cd' into) the target
1247 installation directory now, when no build-local scripts are used.
1249 Both install and uninstall do not fail anymore but do nothing if an
1250 installation directory variable like `bindir' is set to the empty string.
1252 For built-in rules, `make install' now fails reliably if installation
1253 of a file failed. Conversely, `make uninstall' even succeeds when
1254 issued multiple times.
1256 These changes may need some adjustments from users: For example,
1257 some `install' programs refuse to install multiple copies of the
1258 same file in one invocation, so you may need to remove duplicate
1259 entries from file lists.
1261 Also, within one set of files, say, nobase_data_DATA, the order of
1262 installation may be changed, or even unstable among different hosts,
1263 due to the use of associative arrays in awk. The increased use of
1264 awk matches a similar move in Autoconf to provide for better scaling.
1266 Further, most undocumented per-rule install command variables such as
1267 binSCRIPT_INSTALL have been removed because they are not needed any
1268 more. Packages which use them should be using the appropriate one of
1269 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1270 counterpart, depending on the type of files and the need for automatic
1271 target directory creation.
1273 - The "deleted header file problem" for *.m4 files is avoided by
1274 stub rules. This allows `make' to trigger a rerun of `aclocal'
1275 also if some previously needed macro file has been removed.
1277 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1278 an otherwise up to date tree.
1280 - The `color-tests' option causes colored test result output on terminals.
1282 - The `parallel-tests' option enables a new test driver that allows for
1283 parallel test execution, inter-test dependencies, lazy test execution
1284 for unit-testing, re-testing only failed tests, and formatted result output
1285 as RST (reStructuredText) and HTML. Enabling this option may require some
1286 changes to your test suite setup; see the manual for details.
1288 - The `silent-rules' option enables Linux kernel-style silent build output.
1289 This option requires the widely supported but non-POSIX `make' feature
1290 of recursive variable expansion, so do not use it if your package needs
1291 to build with `make' implementations that do not support it.
1293 To enable less verbose build output, the developer has to use the Automake
1294 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1295 macro. The user may then set the default verbosity by passing the
1296 `--enable-silent-rules' option to `configure'. At `make' run time, this
1297 default may be overridden using `make V=0' for less verbose, and `make V=1'
1298 for backward-compatible verbose output.
1300 - New prefix `notrans_' for manpages which should not be transformed
1301 by --program-transform.
1303 - New macro AM_COND_IF for conditional evaluation and conditional
1306 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1307 remove the file in a non-VPATH build. Such setups work with Autoconf
1310 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1311 the default setting.
1313 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1314 useful especially for multi-line values.
1316 - Automake's early configure-time sanity check now diagnoses an
1317 unsafe absolute source directory name and makes configure fail.
1319 - The Automake macros and rules cope better with whitespace in the
1320 current directory name, as long as the relative path to `configure'
1321 does not contain whitespace. To this end, the values of `$(MISSING)'
1322 and `$(install_sh)' may contain suitable quoting, and their expansion
1323 might need `eval'uation if used outside of a makefile. These
1324 undocumented variables may be used in several documented macros such
1325 as $(AUTOCONF) or $(MAKEINFO).
1329 * Long-standing bugs:
1331 - Fix aix dependency tracking for libtool objects.
1333 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1334 unnecessary use of the `compile' script.
1336 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1337 correct `-rpath' argument is used now.
1339 - `config.status --file=Makefile depfiles' now also works with the
1340 extra quoting used internally by Autoconf 2.62 and newer
1341 (it used to work only without the `--file=' bit).
1343 - The `missing' script works better with versioned tool names.
1345 - Semantics for `missing help2man' have been revamped:
1347 Previously, if `help2man' was not present, `missing help2man' would have
1348 the following semantics: if some man page was out of date but present, then
1349 a warning would be printed, but the exit status was 0. If the man page was
1350 not present at all, then `missing' would create a replacement man page
1351 containing an error message, and exit with a status of 2. This does not play
1352 well with `make': the next run will see this particular man page as being up
1353 to date, and will only error out on the next generated man page, if any;
1354 repeat until all pages are done. This was not desirable.
1356 These are the new semantics: if some man page is not present, and help2man
1357 is not either, then `missing' will warn and generate the replacement page
1358 containing the error message, but exit successfully. However, `make dist'
1359 will ensure that no such bogus man pages are packaged into a tarball.
1361 - Targets provided by automake behave better with `make -n', in that they
1362 take care not to create files.
1364 - `config.status Makefile... depfiles' works fine again in the presence of
1365 disabled dependency tracking.
1367 - The default no-op recursive rules for these targets also work with BSD make
1368 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1370 - `make distcheck' works also when both a directory and some file below it
1371 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1373 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1374 `make mostlyclean' any more; only the LaTeX by-products are.
1376 - Renamed objects also work with the `subdir-objects' option and
1377 source file languages which Automake does not know itself.
1379 - `automake' now correctly complains about variable assignments which are
1380 preceded by a comment, extend over multiple lines with backslash-escaped
1381 newlines, and end in a comment sign. Previous versions would silently
1382 and wrongly ignore such assignments completely.
1384 * Bugs introduced by 1.10:
1386 - Fix output of dummy dependency files in presence of post-processed
1387 Makefile.in's again, but also cope with long lines.
1389 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1390 that have been declared as programs in the same Makefile.
1391 This is for consistency with the analogous change to TESTS in 1.10.
1393 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1394 followed by directories containing config headers.
1396 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1400 * Version requirements:
1402 - Autoconf 2.60 or greater is required.
1404 - Perl 5.6 or greater is required.
1406 * Changes to aclocal:
1408 - aclocal now also supports -Wmumble and -Wno-mumble options.
1410 - `dirlist' entries (for the aclocal search path) may use shell
1411 wildcards such as `*', `?', or `[...]'.
1413 - aclocal supports an --install option that will cause system-wide
1414 third-party macros to be installed in the local directory
1415 specified with the first -I flag. This option also uses #serial
1416 lines in M4 files to upgrade local macros.
1418 The new aclocal options --dry-run and --diff help to review changes
1419 before they are installed.
1421 - aclocal now outputs an autoconf version check in aclocal.m4 in
1422 projects using automake.
1424 For a few years, automake and aclocal have been calling autoconf
1425 (or its underlying engine autom4te) to accurately retrieve the
1426 data they need from configure.ac and its siblings. Doing so can
1427 only work if all autotools use the same version of autoconf. For
1428 instance a Makefile.in generated by automake for one version of
1429 autoconf may stop working if configure is regenerated with another
1430 version of autoconf, and vice versa.
1432 This new version check ensures that the whole build system has
1433 been generated using the same autoconf version.
1435 * Support for new Autoconf macros:
1437 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1439 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1440 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1441 in different directories. However, only one instance of such a
1442 library objects directory is supported.
1444 * Change to Libtool support:
1446 - Libtool generic flags (those that go before the --mode=MODE option)
1447 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1449 * Yacc and Lex changes:
1451 - The rebuild rules for distributed Yacc and Lex output will avoid
1452 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1455 - ylwrap is now always used for lex and yacc source files,
1456 regardless of whether there is more than one source per directory.
1458 * Languages changes:
1460 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1461 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1462 tracking, unlike non-preprocessed assembler (*.s).
1464 - subdir-object mode works now with Assembler. Automake assumes
1465 that the compiler understands `-c -o'.
1467 - Preprocessed assembler (*.S) compilation now also honors
1468 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1470 - Improved support for Objective C:
1471 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1472 - A new section of the manual documents the support.
1474 - New support for Unified Parallel C:
1475 - AM_PROG_UPC looks for a UPC compiler.
1476 - A new section of the manual documents the support.
1478 - Per-target flags are now correctly handled in link rules.
1480 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1481 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1482 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1483 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1485 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1486 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1487 is expected to work (and actually works during compilation).
1489 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1490 "in addition to" breaks backward compatibility with older versions.
1491 If your package used both variables, as in
1493 AM_LDFLAGS = common flags
1494 bin_PROGRAMS = a b c
1495 a_LDFLAGS = more flags
1498 and assumed *_LDFLAGS would sum up, you should rewrite it as
1500 AM_LDFLAGS = common flags
1501 bin_PROGRAMS = a b c
1502 a_LDFLAGS = $(AM_LDFLAGS) more flags
1505 This new behavior of *_LDFLAGS is more coherent with other
1506 per-target variables, and the way *_LDFLAGS variables were
1507 considered internally.
1509 * New installation targets:
1511 - New targets mandated by GNU Coding Standards:
1516 By default they will only install Texinfo manuals.
1517 You can customize them with *-local variants:
1523 - The undocumented recursive target `uninstall-info' no longer exists.
1524 (`uninstall' is in charge of removing all possible documentation
1525 flavors, including optional formats such as dvi, ps, or info even
1526 when `no-installinfo' is used.)
1528 * Miscellaneous changes:
1530 - Automake no longer complains if input files for AC_CONFIG_FILES
1531 are specified using shell variables.
1533 - clean, distribution, or rebuild rules are normally disabled for
1534 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1535 AC_CONFIG_LINK specified using shell variables. However, if these
1536 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1537 be able to output rules anyway.
1538 (See the Automake documentation for AC_CONFIG_FILES.)
1540 - $(EXEEXT) is automatically appended to filenames of TESTS
1541 that have been declared as programs in the same Makefile.
1542 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1544 - `-Wportability' has finally been turned on by default for `gnu' and
1545 `gnits' strictness. This means, automake will complain about %-rules
1546 or $(GNU Make functions) unless you switch to `foreign' strictness or
1547 use `-Wno-portability'.
1549 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1550 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1551 $(mkdir_p) variable is still defined (to the same value as
1552 $(MKDIR_P)) but should be considered obsolete. If you are using
1553 $(mkdir_p) in some of your rules, please plan to update them to
1554 $(MKDIR_P) at some point.
1556 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1557 They still work in this release, but may be withdrawn in a future one.
1559 - Inline compilation rules for gcc3-style dependency tracking are
1562 - Automake installs a "Hello World!" example package in $(docdir).
1563 This example is used throughout the new "Autotools Introduction"
1564 chapter of the manual.
1566 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1570 * Makefile.in bloat reduction:
1572 - Inference rules are used to compile sources in subdirectories when
1573 the `subdir-objects' option is used and no per-target flags are
1574 used. This should reduce the size of some projects a lot, because
1575 Automake used to output an explicit rule for each such object in
1578 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1579 object that must be built with explicit rules. It just outputs
1580 the rules required to build the kind of object considered: either
1581 the two .o and .obj rules for usual objects, or the .lo rule for
1584 * Change to Libtool support:
1586 - Libtool tags are used with libtool versions that support them.
1587 (I.e., with Libtool 1.5 or greater.)
1589 - Automake is now able to handle setups where a libtool library is
1590 conditionally installed in different directories, as in
1593 lib_LTLIBRARIES = liba.la
1595 pkglib_LTLIBRARIES = liba.la
1597 liba_la_SOURCES = ...
1599 * Changes to aclocal:
1601 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1602 really evaluated, before it decides to include them in aclocal.m4.
1603 This solves nasty problems with conditional redefinitions of
1604 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1605 *.m4 files to be included in any project using these macros.
1606 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1607 most famous instance of this bug.)
1609 - Do not complain about missing conditionally AC_REQUIREd macros
1610 that are not actually used. In 1.8.x aclocal would correctly
1611 determine which of these macros were really needed (and include
1612 only these in the package); unfortunately it would also require
1613 all of them to be present in order to run. This created
1614 situations were aclocal would not work on a tarball distributing
1615 all the macros it uses. For instance running aclocal on a project
1616 containing only the subset of the Gettext macros in use by the
1617 project did not work, because gettext conditionally requires other
1620 * Portability improvements:
1622 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1623 tar-pax. The new option filename-length-max=99 helps diagnosing
1624 filenames that are too long for tar-v7. (PR/414)
1626 - Variables aumented with `+=' are now automatically flattened (i.e.,
1627 trailing backslashes removed) and then wrapped around 80 colummns
1628 (adding trailing backslashes). In previous versions, a long series
1634 would result in a single-line definition of VAR that could possibly
1635 exceed the maximum line length of some make implementations.
1637 Non-augmented variables are still output as they are defined in
1642 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1643 Works the same as the old Fortran 77 implementation; just replace
1644 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1645 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1647 - Support for conditional _LISP.
1649 - Support for conditional -hook and -local rules (PR/428).
1651 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1653 - Automake will not write any Makefile.ins after the first error it
1654 encounters. The previous Makefile.ins (if any) will be left in
1655 place. (Warnings will not prevent output, but remember they can
1656 be turned into errors with -Werror.)
1658 - The restriction that SUBDIRS must contain direct children is gone.
1661 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1662 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1664 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1666 Bugs fixed in 1.8.5:
1668 * Long-standing bugs:
1670 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1671 so that `make distclean' and `make maintainer-clean' can work.
1673 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1675 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1677 - Polish diagnostic when no input file is found.
1679 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1681 Bugs fixed in 1.8.4:
1683 * Long-standing bugs:
1685 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1686 overridden by the user.
1688 - Honor PATH_SEPARATOR in various places of the Automake package, for
1691 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1694 - Fix install-sh so it can install the `mv' binary... using `mv'.
1696 - Fix tru64 dependency tracking for libtool objects.
1698 - Work around Exuberant Ctags when creating a TAGS files in a directory
1699 without files to scan but with subdirectories to include.
1701 * Bugs introduced by 1.8:
1703 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1704 not defined in the same conditions as the _LDADD that uses it.
1706 - Do not warn when JAVAROOT is overridden, this is legitimate.
1708 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1710 Bugs fixed in 1.8.3:
1712 * Long-standing bugs:
1714 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1715 or any of the other *dir variables contain a space.
1717 Please note that Automake does not and cannot support spaces in
1718 filenames that are involved during the build. This change affects
1719 only installation paths, so that `make install' does not bomb out
1720 in packages configured with
1721 ./configure --prefix '/c/Program Files'
1723 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1724 POSIXLY_CORRECT is set.
1726 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1727 since Autoconf 2.54, which defines LIBOBJS itself.
1729 - Fix a potential (but unlikely) race condition in parallel elisp
1730 builds. (Introduced in 1.7.3.)
1732 - Do not assume that users override _DEPENDENCIES in all conditions
1733 where Automake will try to define them.
1735 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1736 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1739 This fix also affects the $(mkdir_p) variable defined since
1740 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1741 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1743 - Secure temporary directory creation in `make distcheck'. (PR/413)
1745 - Do not generate two build rules for `parser.h' when the
1746 parser appears in two different conditionals.
1748 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1749 checking. Usually ./configure will not pick this shell; so this
1750 fix only helps cases where the shell is forced to /bin/sh.
1752 * Bugs introduced by 1.8:
1754 - In some situations (hand-written `m4_include's), aclocal would
1755 call the `File::Spec->rel2abs' method, which was only introduced
1756 in Perl 5.6. This new version reestablish support Perl 5.005.
1758 It is likely that the next major Automake releases will require at
1759 least Perl 5.6. Consider upgrading your development environment
1760 if you are still using the five-year-old Perl 5.005.
1762 - Automake would sometimes fail to define rules for targets listed
1763 in variables defined in multiple conditions. For instance on
1769 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1770 `b.$(OBJEXT): b.c' rule.
1772 * New sections in manual:
1774 - Third-Party Makefiles: how to interface third party Makefiles.
1775 - Upgrading: upgrading packages to newer Automake versions.
1776 - Multiple Outputs: handling tools that produce many outputs.
1778 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1782 * A (well known) portability bug slipped in the changes made to
1783 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1784 install anything on Tru64.
1786 * Fix install rules for conditionally built python files. (This never
1789 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1793 * Bugs introduced by 1.8:
1795 - Fix Config.pm import error with old Perl versions (at least
1796 5.005_03). One symptom is that aclocal could not find its macro
1799 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1800 created by `make install' are always world readable, even if the
1801 installer happens to have an overly restrictive umask (e.g. 077).
1802 This was a mistake and has been reverted. There are at least two
1803 reasons why we must not use `-m 0755':
1804 - it causes special bits like SGID to be ignored,
1805 - it may be too restrictive (some setups expect 775 directories).
1807 - Fix aclocal to honor definitions located in files which have been
1808 m4_included manually. aclocal 1.8 had been updated to check
1809 m4_included files for new requirements, but forgot that these
1810 m4_included files can also provide new definitions.
1812 Note that if you have such a setup, we recommend you get rid of
1813 it. In the past, there was a reason to m4_include files manually:
1814 aclocal used to duplicate entire M4 files into aclocal.m4, even
1815 files that were distributed. Some packages were therefore
1816 m4_including the distributed file directly, and playing some
1817 tricks to ensure aclocal would not copy that file to aclocal.m4,
1818 in order to limit the amount of duplication. Since aclocal 1.8.x
1819 will precisely output m4_includes for local M4 files, we recommend
1820 that you clean up your setup, removing all manual m4_includes and
1821 letting aclocal output them.
1823 - Output detailed menus in the Info version if the Automake manual,
1824 so that Emacs can locate the indexes.
1826 - configure.ac and configure were listed twice in DIST_COMMON (an
1827 internal variable where Automake lists configury files to
1828 distribute). This was harmless, but unaesthetic.
1830 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1831 This was an issue only in the Automake package itself, not in
1834 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1835 DEST:SRC. This was wrong, as some packages do
1836 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1839 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1840 argument. This caused two kinds of failures:
1841 - Rules installing data in a conditionally defined directory
1842 failed when that directory was undefined. In this case no
1843 argument was supplied.
1844 - `make installdirs' failed, because several directories were
1845 passed to $(mkdir_p). This was an issue only on platform
1846 were $(mkdir_p) is implemented with `install-sh -d'.
1847 $(mkdir_p) as been changed to accept 0 or more arguments, as
1850 * Long-standing bugs:
1852 - Fix an unexpected diagnostic occurring when users attempt
1853 to override some internal variables that Automake appends to.
1855 - aclocal now scans configure.ac for macro definitions (PR/319).
1857 - Fix a portability issue with OSF1/Tru64 Make. If a directory
1858 distributes files which are outside itself (this usually occurs
1859 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
1860 from a parent package), then `make distcheck' fails due to an
1861 optimization performed by OSF1/Tru64 Make in its VPATH handling.
1862 (tests/subpkg2.test failure)
1864 - Fix another portability issue with Sun and OSF1/Tru64 Make.
1865 In a VPATH-build configuration, `make install' would install
1866 nobase_ files to wrong locations.
1868 - Fix a Perl `uninitialized value' diagnostic occurring when
1869 automake complains that a Texinfo file does not have a
1870 @setfilename statement.
1872 - Erase config.status.lineno during `make distclean'. This file
1873 can be created by config.status. Automake already knew about
1874 configure.lineno, but forgot config.status.lineno.
1876 - Distribute all files, even those which are built and installed
1877 conditionally. This change affects files listed in conditionally
1878 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
1879 as well as those listed in conditionally defined dist_*_DATA,
1880 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
1882 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
1883 doesn't conform to POSIX.
1885 - Normalize help strings for configure variables and options added
1890 - Check for python2.4 in AM_PATH_PYTHON.
1892 * Spurious failures in test suite:
1894 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
1895 tests/ltconv.test: fix failures with CVS Libtool.
1896 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
1897 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
1898 fix failures with old Texinfo versions.
1900 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1906 - The NEWS file is more verbose.
1910 - Autoconf 2.58 or greater is required.
1914 - Default source file names in the absence of a _SOURCES declaration
1915 are made by removing any target extension before appending `.c', so
1916 to make the libtool module `foo.la' from `foo.c', you only need to
1919 lib_LTLIBRARIES = foo.la
1920 foo_la_LDFLAGS = -module
1922 For backward compatibility, foo_la.c will be used instead of
1923 foo.c if this file exists or is the explicit target of a rule.
1924 However -Wobsolete will warn about this deprecated naming.
1926 - AR's `cru' flags are now set in a global ARFLAGS variable instead
1927 of being hard-coded in each $(AR) invocation, so they can be
1928 substituted from configure.ac. This has been requested by people
1929 dealing with non-POSIX ar implementations.
1931 - New warning option: -Woverride. This will warn about any user
1932 target or variable definitions which override Automake
1935 - Texinfo rules back up and restore info files when makeinfo fails.
1937 - Texinfo rules now support the `html' target.
1938 Running this requires Texinfo 4.0 or greater.
1940 `html' is a new recursive target, so if your package mixes
1941 hand-crafted `Makefile.in's with Automake-generated
1942 `Makefile.in's, you should adjust the former to support (or
1943 ignore) this target so that `make html' recurses successfully. If
1944 you had a custom `html' rule in your `Makefile.am', it's better to
1945 rename it as `html-local', otherwise your rule will override
1946 Automake's new rule (you can check that by running `automake
1947 -Woverride') and that will stop the recursion to subdirectories.
1949 Last but not least, this `html' rule is declared PHONY, even when
1950 overridden. Fortunately, it appears that few packages use a
1951 non-PHONY `html' rule.
1953 - Any file which is m4_included from configure.ac will appear as a
1954 configure and Makefile.in dependency, and will be automatically
1957 - The rules for rebuilding Makefiles and Makefile.ins will now
1958 rebuild all Makefiles and all Makefile.ins at once when one of
1959 configure's dependencies has changed. This is considerably faster
1960 than previous implementations, where config.status and automake
1961 were run separately in each directory (this still happens when you
1962 change a Makefile.am locally, without touching configure.ac or
1963 friends). Doing this also solves a longstanding issue: these
1964 rebuild rules failed to work when adding new directories to the
1965 tree, forcing you to run automake manually.
1967 - For similar reasons, the rules to rebuild configure,
1968 config.status, and aclocal.m4 are now defined in all directories.
1969 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
1970 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
1971 should better define them in all directories. This is easily done
1972 using an AC_SUBST (make sure you prefix these dependencies with
1973 $(top_srcdir) since this variable will appear at different
1974 levels of the build tree).
1976 - aclocal will now use `m4_include' instead of copying local m4
1977 files into aclocal.m4. (Local m4 files are those you ship with
1978 your project, other files will be copied as usual.)
1980 Because m4_included files are automatically distributed, it means
1981 for most projects there is no point in EXTRA_DISTing the list of
1982 m4 files which are used. (You can probably get rid of
1983 m4/Makefile.am if you had one.)
1985 - aclocal will avoid touching aclocal.m4 when possible, so that
1986 Autom4te's cache isn't needlessly invalidated. This behavior can
1987 be switched off with the new `--force' option.
1989 - aclocal now uses Autoconf's --trace to detect macros which are
1990 actually used and will no longer include unused macros simply
1991 because they where mentioned. This was often the case for macros
1992 called conditionally.
1994 - New options no-dist and no-dist-gzip.
1996 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
1997 py-compile, and ylwrap, now all understand --version and --help.
1999 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2000 links as part of the distclean target and including source files in
2003 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2004 argument. The latter can be used to override the default behavior
2005 (which is to abort).
2007 - Automake will exit with $? = 63 on version mismatch. (So does
2008 Autoconf 2.58) missing knows this, and in this case it will
2009 emulate the tools as if they were absent. Because older versions
2010 of Automake and Autoconf did not use this exit code, this change
2011 will only be useful in projects generated with future versions of
2014 - When using AC_CONFIG_FILES with multiple input files, Automake
2015 generates the first ".in" input file for which a ".am" exists.
2016 (Former versions would try to use only the first input file.)
2018 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2019 idiom to disable byte-compilation of lisp_LISP files, it is
2020 recommended that you switch to using lisp_DATA. Note that
2021 this is not strictly equivalent: lisp_DATA will install elisp
2022 files even if emacs is not installed, while *_LISP do not
2023 install anything unless emacs is found.
2025 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2026 available. This selection is achieved through the Makefile
2027 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2028 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2029 `$(install_sh) -m 0755 -d'.
2033 - Because `mkdir -p' is available on most platforms, and we can use
2034 `install-sh -d' when it is not, the use of the mkinstalldirs
2035 script is being phased out. `automake --add-missing' no longer
2036 installs it, and if you remove mkinstalldirs from your package,
2037 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2039 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2040 gettextize and autopoint will install it when needed. Automake
2041 will continue to define the $(mkinstalldirs) and to distribute
2042 mkinstalldirs when this script is in the source tree.
2044 - AM_PROG_CC_STDC is now empty. The content of this macro was
2045 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2046 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2047 renaming should be safe, even if you have to support several,
2048 versions of Automake, because AC_PROG_CC defines this variable
2049 since Autoconf 2.54.)
2051 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2052 variable to override the aclocal.m4 dependencies computed
2053 (inaccurately) by older versions of Automake. Because Automake
2054 now tracks configure's m4 dependencies accurately (see m4_include
2055 above), the use of ACLOCAL_M4_SOURCES should be considered
2056 obsolete and will be flagged as such when running `automake
2061 - Defining programs conditionally using Automake conditionals no
2062 longer leads to a combinatorial explosion. The following
2063 construct used to be troublesome when used with dozens of
2078 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2080 - Due to implementation constraints, previous versions of Automake
2081 proscribed multiple conditional definitions of some variables
2091 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2092 This restriction has been lifted, and these variables now
2093 support multiple conditional definitions as do other variables.
2095 - Cleanup the definitions of $(distdir) and $(top_distdir).
2096 $(top_distdir) now points to the root of the distribution
2097 directory created during `make dist', as it did in Automake 1.4,
2098 not to the root of the build tree as it did in intervening
2099 versions. Furthermore these two variables are now only defined in
2100 the top level Makefile, and passed to sub-directories when running
2103 - The --no-force option now correctly checks the Makefile.in's
2104 dependencies before deciding not to update it.
2106 - Do not assume that make files are called Makefile in cleaning rules.
2108 - Update .info files in the source tree, not in the build tree. This
2109 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2110 used to update these files in the build tree (previous versions did
2111 it in the source tree too), and it caused several problems, varying
2112 from mere annoyance to portability issues.
2114 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2115 when --add-missing and --force-missing are used. For backward
2116 compatibility --add-missing will continue to install COPYING (in
2117 `gnu' strictness) when none of these three files exist, but this
2118 use is deprecated: you should better choose a license yourself and
2119 install it once for all in your source tree (and in your code
2122 - Fix ylwrap so that it does not overwrite header files that haven't
2123 changed, as the inline rule already does.
2125 - User-defined rules override automake-defined rules for the same
2126 targets, even when rules do not have commands. This is not new
2127 (and was documented), however some of the automake-generated
2128 rules have escaped this principle in former Automake versions.
2129 Rules for the following targets are affected by this fix:
2131 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2132 info, info-am, install-data-am, install-exec-am, install-info,
2133 install-info-am, install-man, installcheck-am, maintainer-clean,
2134 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2135 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2137 Practically it means that an attempt to supplement the dependencies
2138 of some target, as in
2140 clean: my-clean-rule
2142 will now *silently override* the automake definition of the
2143 rule for this target. Running `automake -Woverride' will diagnose
2144 all such overriding definitions.
2146 It should be noted that almost all of these targets support a *-local
2147 variant that is meant to supplement the automake-defined rule
2148 (See node `Extending' in the manual). The above rule should
2151 clean-local: my-clean-rule
2153 These *-local targets have been documented since at least
2154 Automake 1.2, so you should not fear the change if you have
2155 to support multiple automake versions.
2159 - The Automake manual is now distributed under the terms of the GNU FDL.
2161 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2163 - core dumps are no longer removed by the cleaning rules. There are
2164 at least three reasons for this:
2165 1. These files should not be created by any build step,
2166 so their removal do not fit any of the cleaning rules.
2167 Actually, they may be precious to the developer.
2168 2. If such file is created during a build, then it's clearly a
2169 bug Automake should not hide. Not removing the file will
2170 cause `make distcheck' to complain about its presence.
2171 3. Operating systems have different naming conventions for
2172 core dump files. A core file on one system might be a
2173 completely legitimate data file on another system.
2175 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2176 defined by Automake. This means that any definition in the
2177 environment will be used, unless overridden in the Makefile.am or
2178 on the command line. The old behavior, where these variables were
2179 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2180 AC_ARG_VARing each variable from configure.ac.
2182 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2183 documented. (The is not a new feature, these variables have
2184 been there since at least Automake 1.4.)
2186 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2188 Bugs fixed in 1.7.9:
2189 * Fix install-strip to work with nobase_ binaries.
2190 * Fix renaming of #line directives in ylwrap.
2191 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2193 Bugs fixed in 1.7.8:
2194 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2195 * Fix detection of Debian's install-info, broken since version 1.5.
2196 (Debian bug #213524).
2197 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2198 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2200 Bugs fixed in 1.7.7:
2201 * The implementation of automake's --no-force option is unreliable,
2202 so this option is ignored in this version. A real fix will appear in
2203 Automake 1.8. (Debian Bug #206299)
2204 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2205 argument is given. (PR/399)
2206 * Do not warn about leading `_' in variable names, even with -Wportability.
2207 * Support user redefinitions of TEXINFO_TEX.
2208 * depcomp: support AIX Compiler version 6.
2209 * Fix missing rebuilds during `make dist' with BSD make.
2210 (Could produce tarballs containing out-of-date files.)
2211 * Resurrect multilib support.
2212 * Noteworthy manual updates:
2213 - Extending aclocal: how to write m4 macros that won't trigger warnings
2215 - A Shared Library: Rewrite and split into subsections.
2217 Bugs fixed in 1.7.6:
2218 * Fix depcomp's icc mode for ICC 7.1.
2219 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2220 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2221 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2222 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2223 * Remove Latin-1 characters from elisp-comp.
2224 * Update the manual's @dircategory to match the Free Software Directory.
2226 Bugs fixed in 1.7.5:
2227 * Update install-sh's license to remove an advertising clause.
2228 (Debian bug #191717)
2229 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2230 that caused invalid Makefile.ins to be generated.
2231 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2232 * New FAQ entry: renamed objects.
2234 Bugs fixed in 1.7.4:
2235 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2236 the Emacs implementation)
2237 * Fix output of aclocal.m4 dependencies in subdirectories.
2238 * Use `mv -f' instead of `mv' in fastdep rules.
2239 * Upgrade mdate-sh to work on OS/2.
2240 * Don't byte-compile elisp files when ELCFILES is set empty.
2241 (this documented feature was broken by 1.7.3)
2242 * Diagnose trailing backslashes on last line of Makefile.am.
2243 * Diagnose whitespace following trailing backslashes.
2244 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2245 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2247 * `make install' will build `BUILT_SOURCES' first.
2248 * Minor documentation fixes.
2250 Bugs fixed in 1.7.3:
2251 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2252 * Query distutils for `pythondir' and `pythonexecdir', instead of
2253 using an hardcoded path. This should allow builds on 64-bit
2254 distributions that usually use lib64/ instead of lib/.
2255 * AM_PATH_PYTHON will also search for python2.3.
2256 * elisp files are now built all at once instead of one by one. Besides
2257 incurring a speed-up, this is required to support interdependent elisp files.
2258 * Support for DJGPP:
2259 - `make distcheck' will now work in `_inst/' and `_build' instead
2260 of `=inst/' and `=build/'
2261 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2262 - install/uninstall `*.i[0-9][0-9]'-style info files
2263 - more changes that affect only the Automake package (not its output)
2264 * Fix some incompatibilities with upcoming perl-5.10.
2265 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2266 PACKAGE and VERSION.
2268 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2269 is troublesome with gcc and Solaris compilers. (PR/385)
2270 - makedepend mode: work with Libtool. (PR/385 too)
2272 * better support for unusual gettext setups, such as multiple po/ directories
2274 - Flag missing po/ and intl/ directories as warnings, not errors.
2275 - Disable these warnings if po/ does not exist.
2276 * Noteworthy manual updates:
2278 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2280 - Document `AM_YFLAGS = -d'. (PR/382)
2282 Bugs fixed in 1.7.2:
2283 * Fix installation and uninstallation of Info files built in subdirectories.
2284 * Do not run `./configure --with-included-gettext' during `make distcheck'
2285 if AM_GNU_GETTEXT([external]) is used.
2286 * Correctly uninstall renamed man pages.
2287 * Do not strip escaped newline in variables defined in one condition
2288 and augmented in another condition.
2289 * Fix ansi2knr rules for LIBOBJS sources.
2290 * Clean all known Texinfo index files, not only those which appear to
2291 be used, because we cannot know which indexes are used in included files.
2292 (PR/375, Debian Bug #168671)
2293 * Honor only the first @setfilename seen in a Texinfo file.
2294 * Treat "required file X not found" diagnostics as errors (exit status 1).
2295 * Don't complain that a required file is not found when it is a Makefile
2297 * Don't use single suffix inference rules when building `.info'-less
2298 Info files, for the sake of Solaris make.
2299 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2300 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2301 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2302 * Fix building of deansified files from subdirectories. (PR/370)
2303 * Add missing `fi' in the .c->.obj rules.
2304 * Improve install-sh to work even when names contain spaces or certain
2305 (but not all) shell metachars.
2306 * Fix the following spurious failures in the test suite:
2307 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2308 * Noteworthy manual updates:
2309 - Augment the section about BUILT_SOURCES.
2310 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2312 Bugs fixed in 1.7.1:
2313 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2315 * Aclocal should now recognize macro names containing parentheses, e.g.
2316 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2317 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2319 * Install Python files even if they were built. (PR/369)
2320 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2321 version might not be defined in the latter. (PR/358)
2322 * Reorder arguments passed to a couple of commands, so things works
2323 when POSIXLY_CORRECT=1.
2324 * Fix a regex that can cause Perl to segfault on large input.
2326 * Fix distribution of packages that have some sources defined conditionally,
2327 as in the `Conditional compilation using Automake conditionals' example
2329 * Fix spurious test suite failures on IRIX.
2330 * Don't report a required variable as undefined if it has been
2331 defined conditionally for the "right" conditions.
2332 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2333 `make distcheck' fails.
2334 * Fix distribution of included Makefile fragment, so we don't create
2335 spurious directories in the distribution. (PR/366)
2336 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2339 * Autoconf 2.54 is required.
2340 * `aclocal' and `automake' will no longer warn about obsolete
2341 configure macros. This is done by `autoconf -Wobsolete'.
2342 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2343 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2344 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2345 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2346 `configure.ac' for you.
2347 * Support for per-program and per-library `_CPPFLAGS'.
2348 * New `ctags' target (builds CTAGS files).
2349 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2350 (see `automake --help' or the manual for a list of them).
2351 * Honor the WARNINGS environment variable.
2352 * Omit the call to depcomp when using gcc3: call the compiler directly.
2353 * A new option, std-options, tests that programs support --help and --version
2354 when `make installcheck' is run. This is enabled by --gnits.
2355 * Texinfo rules now support the `ps' and `pdf' targets.
2356 * Info files are now created in the build directory, not the source directory.
2357 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2359 * `make distcheck' will enforce DESTDIR support by attempting
2361 * `+=' can be used in conditionals, even if the augmented variable
2362 was defined for another condition.
2363 * Makefile fragments (inserted with `include') are always distributed.
2364 * Use Autoconf's --trace interface to inspect configure.ac and get
2365 a more accurate view of it.
2366 * Add support for extending aclocal's default macro search path
2367 using a `dirlist' file within the aclocal directory.
2368 * automake --output-dir is deprecated.
2369 * The part of the distcheck target that checks whether uninstall actually
2370 removes all installed files has been moved in a separate target,
2371 distuninstallcheck, so it can be overridden easily.
2375 * Support for AM_INIT_GETTEXT([external])
2376 * Bug fixes, including:
2377 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2378 - nobase_ programs and scripts honor --program-transform correctly.
2379 - Erase configure.lineno during `make distclean'.
2380 - Erase YACC and LEX outputs during `make maintainer-clean'.
2383 * Many bug fixes, including:
2384 - Requiring the current version works.
2385 - Fix "$@" portability issues (for Zsh).
2386 - Fix output of dummy dependency files in presence of post-processed
2388 - Don't compute dependencies in background to avoid races with libtool.
2389 - Fix handling of _OBJECTS variables for targets sharing source variables.
2390 - Check dependency mode for Java when AM_PROG_GCJ is used.
2393 * automake --output-dir is deprecated
2394 * Many bug fixes, including:
2395 - Don't choke on AM_LDFLAGS definitions.
2396 - Clean libtool objects from subdirectories.
2397 - Allow configure variables with reserved suffix and unknown prefix
2398 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2399 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2402 * Autoconf 2.52 is required.
2403 * automake no longer run libtoolize.
2404 This is the job of autoreconf (from GNU Autoconf).
2405 * `dist' generates all the archive flavors, as did `dist-all'.
2406 * `dist-gzip' generates the Gzip tar file only.
2407 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2408 explosion. Makefile.in's keep a reasonable size.
2409 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2410 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2412 * `#line' of Lex and Yacc files are properly set.
2413 * EXTRA_DIST can contain generated directories.
2414 * Support for dot-less extensions in suffix rules.
2415 * The part of the distcheck target that checks whether distclean actually
2416 cleans all built files has been moved in a separate target, distcleancheck,
2417 so it can be overridden easily.
2418 * `make distcheck' will pass additional options defined in
2419 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2420 * Fixed CDPATH portability problems, in particular for MacOS X.
2421 * Fixed handling of nobase_ targets.
2422 * Fixed support of implicit rules leading to .lo objects.
2423 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2424 * Added uninstall-hook target
2425 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2426 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2427 (Note that "pkgname" is not "tarname", see the manual for details.)
2428 It is also possible to pass a list of global Automake options as
2429 first argument to this new form of AM_INIT_AUTOMAKE.
2430 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2431 to be a real assembler.
2432 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2433 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2434 * aclocal and automake are also installed with the version number
2435 appended, and some of the install directory names have changed.
2436 This lets you have multiple versions installed simultaneously.
2437 * Support for parsers and lexers in subdirectories.
2440 * Support for `configure.ac'.
2441 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2442 * `make dist-all' is much faster.
2443 * Allows '@' AC_SUBSTs in macro names.
2444 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2445 * User-side dependency tracking. Developers no longer need GNU make
2447 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2448 * Most files are correctly handled if they appear in subdirs
2449 For instance, a _DATA file can appear in a subdir
2450 * GNU tar is no longer required for `make dist'
2451 * Added support for `dist_' and `nodist_' prefixes
2452 * Added support for `nobase_' prefix
2453 * Compiled Java support
2454 * Support for per-executable and per-library compilation flags
2458 * Added support for the Fortran 77 programming language.
2459 * Re-indexed the Automake Texinfo manual.
2460 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2461 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2462 * Support for latest autoconf, including support for objext
2463 * Can now put `.' in SUBDIRS to control build order
2464 * `include' command and `+=' support for macro assignment
2465 * Dependency tracking no long susceptible to deleted header file problem
2466 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2471 * Better Cygwin32 support
2472 * Support for suffix rules with _SOURCES variables
2473 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2474 * @LEXLIB@ no longer required when lex source seen
2475 Lex support in `missing', and new lex macro. Update your missing script.
2476 * Built-in support for assembly
2477 * aclocal gives error if `AM_' macro not found
2478 * Passed YFLAGS, not YACCFLAGS, to yacc
2479 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2480 * Dependencies computed as a side effect of compilation
2481 * Preliminary support for Java
2482 * DESTDIR support at "make install" time
2483 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2487 * Better DejaGnu support
2488 * Added no-installinfo option
2489 * Added Emacs Lisp support
2490 * Added --no-force option
2491 * Included `aclocal' program
2492 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2493 * Now uses `AM_' macro names everywhere
2494 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2495 ansi2knr now works correctly on K&R sources
2496 * Better C++, yacc, lex support
2497 * Will compute _DEPENDENCIES variables automatically if not supplied
2498 * Will interpolate $(...) and ${...} when examining contents of a variable
2499 * .deps files now in build directory, not source directory; dependency
2500 handling generally rewritten
2501 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2502 * can now put config.h into a subdir
2503 * Added dist-all target
2504 * Support for install-info program (see texinfo 3.9)
2505 * Support for "yacc -d"
2506 * configure substitutions are automatically discovered and included
2507 in generated Makefile.in
2508 * Special --cygnus mode
2509 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2510 when making distribution. Some dependencies are auto-ignored.
2511 * Changed how libraries are specified in _LIBRARIES variable
2512 * Full libtool support, from Gord Matzigkeit
2513 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2514 AM_CONFIG_HEADER handles it automatically
2515 * Texinfo output files no longer need .info extension
2516 * Added `missing' support
2518 * Conditionals in Makefile.am, from Ian Taylor
2522 * distcheck target runs install and installcheck targets
2523 * Added preliminary support for DejaGnu.
2528 * More libtool fixes from Gord Matzigkeit; libtool support is still
2530 * Added support for jm_MAINTAINER_MODE
2532 * New "distcheck" target
2536 * mkinstalldirs and mdate-sh now appear in directory specified by
2538 * Removed DIST_SUBDIRS, DIST_OTHER
2539 * AC_ARG_PROGRAM only required when an actual program exists
2540 * dist-hook target now run before distribution packaged up; idea from
2541 Dieter Baron. Other hooks exist, too.
2542 * Preliminary (unfinished) support for libtool
2543 * Added short option names.
2544 * Better "dist" support when gluing together multiple packages
2548 * Documentation updates (many from François Pinard)
2549 * strictness `normal' now renamed to `foreign'
2550 * Renamed --install-missing to --add-missing
2551 * Now handles AC_CONFIG_AUX_DIR
2552 * Now handles TESTS macro
2553 * DIST_OTHER renamed to EXTRA_DIST
2554 * DIST_SUBDIRS is deprecated
2555 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2556 * Better error messages in many cases
2557 * Program names are canonicalized
2558 * Added "check" prefix; from Gord Matzigkeit
2562 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2563 * Beginnings of a test suite
2564 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2565 * Doesn't print anything when running
2566 * Beginnings of MAINT_CHARSET support
2567 * Can specify version in AUTOMAKE_OPTIONS
2568 * Most errors recognizable by Emacs' M-x next-error
2569 * Added --verbose option
2570 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2571 configure-generated names
2572 * Required macros now distributed in aclocal.m4
2574 * --strictness=gnu is default
2578 * More sophisticated configure.in scanning; now understands ALLOCA and
2579 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2580 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2581 * CONFIG_HEADER variable now obsolete
2582 * Can handle multiple Texinfo sources
2583 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2584 * HEADERS variable no longer needed; now can put .h files directly into
2585 foo_SOURCES variable.
2586 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2587 corresponding ".in" files are included in the distribution.
2590 * Added --gnu and --gnits options
2591 * More standards checking
2593 * Cleaned up 'dist' targets
2594 * Added AUTOMAKE_OPTIONS variable and several options
2595 * Now scans configure.in to get some information (preliminary)
2598 * Works with Perl 4 again
2601 * Added --install-missing option.
2602 * Pretty-prints generated macros and rules
2603 * Comments in Makefile.am are placed more intelligently in Makefile.in
2604 * Generates .PHONY target
2605 * Rule or macro in Makefile.am now overrides contents of Automake file
2606 * Substantial cleanups from François Pinard
2610 * Works with Perl 4 again.
2613 * New uniform naming scheme.
2614 * --strictness option
2616 * '.c' files corresponding to '.y' or '.l' files are automatically
2618 * Many bug fixes and cleanups
2621 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2624 * Bug fixes in 'clean' code.
2625 * Now generates 'installdirs' target.
2626 * man page installation reworked.
2627 * 'make dist' no longer re-creates all Makefile.in's.
2630 * Reimplemented in Perl
2631 * Added --amdir option (for debugging)
2632 * Texinfo support cleaned up.
2633 * Automatic de-ANSI-fication cleaned up.
2634 * Cleaned up 'clean' targets.
2637 * Automatic dependency tracking
2638 * More documentation
2639 * New variables DATA and PACKAGEDATA
2640 * SCRIPTS installed using $(INSTALL_SCRIPT)
2641 * No longer uses double-colon rules
2643 * Changes in advance of internationalization
2647 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2649 This program is free software; you can redistribute it and/or modify
2650 it under the terms of the GNU General Public License as published by
2651 the Free Software Foundation; either version 2, or (at your option)
2654 This program is distributed in the hope that it will be useful,
2655 but WITHOUT ANY WARRANTY; without even the implied warranty of
2656 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2657 GNU General Public License for more details.
2659 You should have received a copy of the GNU General Public License
2660 along with this program. If not, see <http://www.gnu.org/licenses/>.
projects / platform / upstream / automake.git / blob