3 * WARNING: Future backward-incompatibilities!
5 - Automake 1.14 will require Autoconf 2.70 or later (which is still
6 unreleased at the moment of writing, but is planned to be released
7 before Automake 1.14 is).
9 - Automake 1.14 will drop support for the long-deprecated 'configure.in'
10 name for the Autoconf input file. You are advised to start using
11 recommended name 'configure.ac' instead, ASAP.
13 - The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will
14 be removed in Automake 1.14. The $(mkdir_p) make variable and the
15 @mkdir_p@ substitution will still remain available (as aliases of
16 $(MKDIR_P)) for the moment, for better backward compatibility; but
17 you are advised to stop using ASAP.
19 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated
20 in Automake 1.14 (where it will raise warnings in the "obsolete"
21 category). You are advised to start relying on the new Automake
22 support for AC_CONFIG_MACRO_DIRS instead (which was introduced in
25 - Support for IRIX and the SGI C/C++ compilers will be removed in
26 Automake 1.14: they have seen their last release in 2006, and SGI
27 is expected to retire support from them in December 2013; see
28 <http://www.sgi.com/services/support/irix_mips_support.html> for
31 - Future versions of Automake might remove support for MS-DOS and
32 Windows 95/98/ME (support for them was offered by relying on the
33 DJGPP project). Note however that both Cygwin and MSYS/MinGW on
34 modern Windows versions will continue to be fully supported.
36 - Support for the long-deprecated INCLUDES variable will be removed
37 altogether in Automake 1.14. The AM_CPPFLAGS variable should be
40 - Automake-provided scripts and makefile recipes might (finally!)
41 start assuming a POSIX shell in Automake 1.14.
43 - Starting from Automake 1.14, third-party m4 files located in the
44 system-wide aclocal directory, as well as in any directory listed
45 in the ACLOCAL_PATH environment variable, will take precedence
46 over "built-in" Automake macros. For example (assuming Automake
47 is installed in the /usr/local hierarchy), a definition of the
48 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
49 should take precedence over the same-named automake-provided macro
50 (defined in '/usr/local/share/aclocal-1.14/vala.m4').
52 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
54 - The 'compile' script is now unconditionally required for all
55 packages that perform C compilation (note that if you are using
56 the '--add-missing' option, automake will fetch that script for
57 you, so you shouldn't need any explicit adjustment).
58 This new behaviour is needed to avoid obscure errors when the
59 'subdir-objects' option is used, and the compiler is an inferior
60 one that doesn't grasp the combined use of both the "-c -o"
61 options; see discussion about automake bug#13378 for more details:
62 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
63 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
65 - Automake will automatically enhance the AC_PROG_CC autoconf macro
66 to make it check, at configure time, that the C compiler supports
67 the combined use of both the "-c -o" options. This "rewrite" of
68 AC_PROG_CC is only meant to be temporary, since future Autoconf
69 versions should provide all the features Automake needs.
71 - The AM_PROG_CC_C_O is no longer useful, and its use is a no-op
72 now. Future Automake versions might start warning that this
73 macro is obsolete. For better backward-compatibility, this macro
74 still sets a proper 'ac_cv_prog_cc_*_c_o' cache variable, and
75 define the 'NO_MINUS_C_MINUS_O' C preprocessor symbol, but you
76 should really stop relying on that.
78 * Obsolescent features:
80 - Use of suffix-less info files (that can be specified through the
81 '@setfilename' macro in Texinfo input files) is discouraged, and
82 its use will raise warnings in the 'obsolete' category. Simply
83 use the '.info' extension for all your info files, transforming
86 @setfilename myprogram
90 @setfilename myprogram.info
92 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
93 is discouraged, and its use will raise warnings in the 'obsolete'
94 category. You are advised to simply use the '.texi' extension
97 * Documentation fixes:
99 - The long-deprecated but still supported two-arguments invocation form
100 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
101 thing to do, given that support for such an usage might need to remain
102 in place for a unspecified amount of time in order to cater for people
103 who want to define the version number for their package dynamically at
104 configure runtime (unfortunately, Autoconf does not yet support this
105 scenario, so we cannot delegate the work to it).
109 - Automake can now be instructed to place '.info' files generated from
110 Texinfo input in the builddir rather than in the srcdir; this is done
111 specifying the new automake option 'info-in-builddir'. This feature
112 was requested by the developers of GCC, GDB, GNU binutils and the GNU
113 bfd library. See the extensive discussion about automake bug#11034
116 - For quite a long time, Automake has been implementing an undocumented
117 hack which ensured that '.info' files which appeared to be cleaned
118 (by e.g. being listed in the CLEANFILES or DISTCLEANFILES variables)
119 were built in the builddir rather than in the srcdir; this hack was
120 introduced to ensure better backward-compatibility with packages such
121 as Texinfo, which did things like:
123 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
124 DISTCLEANFILES = texinfo texinfo-* info*.info*
125 # Do not create info files for distribution.
129 in order not to distribute generated '.info' files.
131 Now that we have the 'info-in-builddir' option that explicitly causes
132 generated '.info' files to be placed in the builddir, this hack should
133 be longer necessary, so we deprecate it with runtime warnings. It will
134 likely be removed altogether in Automake 1.14.
136 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
142 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
143 causes a clear and helpful error message, instead of obscure ones
144 (issue introduced in Automake 1.13).
146 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
152 - ylwrap renames properly header guards in generated header files
153 (*.h), instead of leaving Y_TAB_H.
155 - ylwrap now also converts header guards in implementation files
156 (*.c). Because ylwrap failed to rename properly #include in the
157 implementation files, current versions of Bison (e.g., 2.7)
158 duplicate the generated header file in the implementation file.
159 The header guard then protects the implementation file from
160 duplicate definitions from the header file.
162 * Version requirements:
164 - Autoconf 2.65 or greater is now required.
166 - The rules to build PDF and DVI output from Texinfo input now
167 require Texinfo 4.9 or later.
171 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
172 option) has been removed. See discussion about automake bug#11034
173 for more background: <http://debbugs.gnu.org/11034>.
175 - The deprecated aclocal option '--acdir' has been removed. You
176 should use the options '--automake-acdir' and '--system-acdir'
177 instead (which have been introduced in Automake 1.11.2).
179 - The following long-obsolete m4 macros have been removed:
181 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
182 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
183 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
184 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
185 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
186 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
187 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
188 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
189 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
190 of the now-removed automatic de-ANSI-fication
193 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
195 - Use of the long-deprecated two- and three-arguments invocation forms
196 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
197 though (albeit with a warning in the 'obsolete' category), to cater
198 for people who want to define the version number for their package
199 dynamically (e.g., from the current VCS revision). We'll have to
200 continue this support until Autoconf itself is fixed to allow better
201 support for such dynamic version numbers.
203 * Elisp byte-compilation:
205 - The byte compilation of '.el' files into '.elc' files is now done
206 with a suffix rule. This has simplified the compilation process, and
207 more importantly made it less brittle. The downside is that emacs is
208 now invoked once for each '.el' files, which cause some noticeable
209 slowdowns. These should however be mitigated on multicore machines
210 (which are becoming the norm today) if concurrent make ("make -j")
213 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
214 files in the same subdirectory; for example, byte-compiling of file
215 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
216 'foo.elc'. This behaviour is backward-incompatible with older
217 Automake versions, but it is more natural and more sane. See also
220 - The Emacs invocation performing byte-compilation of '.el' files honors
221 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
222 one is developer-reserved and the latter one user-reserved.
224 - The 'elisp-comp' script, once provided by Automake, has been rendered
225 obsoleted by the just-described changes, and thus removed.
227 * Changes to Automake-generated testsuite harnesses:
229 - The parallel testsuite harness (previously only enabled by the
230 'parallel-tests' option) is the default one; the older serial
231 testsuite harness will still be available through the use of the
232 'serial-tests' option (introduced in Automake 1.12).
234 - The 'color-tests' option is now unconditionally activated by default.
235 In particular, this means that testsuite output is now colorized by
236 default if the attached terminal seems to support ANSI escapes, and
237 that the user can force output colorization by setting the variable
238 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
239 for backward-compatibility, although it's a handled as a no-op now.
241 * Silent rules support:
243 - Support for silent rules is now always active in Automake-generated
244 Makefiles. So, although the verbose output is still the default,
245 the user can now always use "./configure --enable-silent-rules" or
246 "make V=0" to enable quieter output in the package he's building.
248 - The 'silent-rules' option has now become a no-op, preserved for
249 backward-compatibility only. In particular, its use no longer
250 disables the warnings in the 'portability-recursive' category.
254 - The rules to build PDF and DVI files from Texinfo input now require
255 Texinfo 4.9 or later.
257 - The rules to build PDF and DVI files from Texinfo input now use the
258 '--build-dir' option, to keep the auxiliary files used by texi2dvi
259 and texi2pdf around without cluttering the build directory, and to
260 make it possible to run the "dvi" and "pdf" recipes in parallel.
262 * Automatic remake rules and 'missing' script:
264 - The 'missing' script no longer tries to update the timestamp of
265 out-of-date files that require a maintainer-specific tool to be
266 remade, in case the user lacks such a tool (or has a too-old version
267 of it). It just gives a useful warning, and in some cases also a
268 tip about how to obtain such a tool.
270 - The missing script has thus become useless as a (poor) way to work
271 around the sketched-timestamps issues that can happen for projects
272 that keep generated files committed in their VCS repository. Such
273 projects are now encouraged to write a custom "fix-timestamps.sh"
274 script to avoid such issues; a simple example is provided in the
275 "CVS and generated files" chapter of the automake manual.
279 - The user can now define his own recursive targets that recurse
280 in the directories specified in $(SUBDIRS). This can be done by
281 specifying the name of such targets in invocations of the new
282 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
286 - Any failure in the recipe of the "tags", "ctags", "cscope" or
287 "cscopelist" targets in a subdirectory is now propagated to the
288 top-level make invocation.
290 - Tags are correctly computed also for files in _SOURCES variables that
291 only list files with non-standard suffixes (see automake bug#12372).
293 * Improvements to aclocal and related rebuilds rules:
295 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
296 are now traced by aclocal, and can be used to declare the local m4
297 include directories. Formerly, one had to specify it with an explicit
298 '-I' option to the 'aclocal' invocation.
300 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
301 Automake versions will warn about its use, and later version will
302 remove support for it altogether.
304 * The depcomp script:
306 - Dropped support for libtool 1.4.
308 - Various internal refactorings. They should cause no visible change,
309 but the chance for regression is there anyway, so please report any
310 unexpected or suspicious behaviour.
312 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
313 This should cause no problem, since icc 8.0 has been released in
314 December 2003 -- almost nine years ago.
316 - Support for tcc (the Tiny C Compiler) has been improved, and is now
317 handled through a dedicated 'tcc' mode.
321 - ylwrap generates header guards with a single '_' for series of non
322 alphabetic characters, instead of several. This is what Bison >=
325 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
327 Bugs fixed in 1.12.6:
329 * Python-related bugs:
331 - The default installation location for python modules has been improved
332 for Python 3 on Debian and Ubuntu systems, changing from:
334 ${prefix}/lib/python3/dist-packages
338 ${prefix}/lib/python3.x/site-packages
340 This change should ensure modules installed using the default ${prefix}
341 "/usr/local" are found by default by system python 3.x installations.
342 See automake bug#10227.
344 - Python byte-compilation supports the new layout mandated by PEP-3147,
345 with its __pycache__ directory (automake bug#8847).
347 * Build system issues:
349 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
350 Automake's own build system works correctly again (bug introduced
355 - The Vala-related tests has been changed to adjust to the removal of
356 the 'posix' profile in the valac compiler. See automake bug#12934
359 - Some spurious testsuite failures related to older tools and systems
362 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
368 - The AM_PROG_VALAC macro has been enhanced to takes two further
369 optional arguments; it's signature now being
371 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
372 [ACTION-IF-NOT-FOUND])
374 - By default, AM_PROG_VALAC no longer aborts the configure invocation
375 if the Vala compiler found is too old, but simply prints a warning
376 messages (as it did when the Vala compiler was not found). This
377 should avoid unnecessary difficulties for end users that just want
378 to compile the unmodified, distributed Vala-generated C sources,
379 but happens to have an old Vala compiler in their PATH. This fixes
382 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
383 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
384 This is a better default, because with it a triggered makefile rule
385 invoking a Vala compilation will clearly fail with an informative error
386 message like "valac: command not found", rather than silently, with
387 the error possibly going unnoticed or triggering harder-to-diagnose
388 fallout failures in later steps.
390 * Miscellaneous changes:
392 - automake and aclocal no longer honours the 'perllibdir' environment
393 variable. That had always been intended only as an hack required in
394 the testsuite, not meant for any use beyond that.
396 Bugs fixed in 1.12.5:
398 * Long-standing bugs:
400 - Automake no longer generates spurious remake rules invoking autoheader
401 to regenerate the template corresponding to header files specified after
402 the first one in AC_CONFIG_HEADERS (automake bug#12495).
404 - When wrapping Microsoft tools, the 'compile' script falls back to
405 finding classic 'libname.a' style libraries when 'name.lib' and
406 'name.dll.lib' aren't available.
408 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
412 * Warnings and deprecations:
414 - Warnings in the 'obsolete' category are enabled by default both in
415 automake and aclocal.
417 * Miscellaneous changes:
419 - Some testsuite weaknesses and spurious failures have been fixed.
421 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
425 * Miscellaneous changes:
427 - The '.m4' files provided by Automake no longer define serial numbers.
428 This should cause no difference in the behaviour of aclocal though.
430 - Some testsuite weaknesses and spurious failures have been fixed.
432 - There is initial support for automatic dependency tracking with the
433 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
435 Bugs fixed in 1.12.3:
437 * Long-standing bugs:
439 - Instead of renaming only self-references of files (typically for
440 #lines), ylwrap now also renames references to the other generated
441 files. This fixes support for GLR and C++ parsers from Bison (PR
442 automake/491 and automake bug#7648): 'parser.c' now properly
443 #includes 'parser.h' instead of 'y.tab.h'.
445 - Generated files unknown to ylwrap are now preserved. This fixes
446 C++ support for Bison (automake bug#7648): location.hh and the
447 like are no longer discarded.
449 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
453 * Warnings and deprecations:
455 - Automake now issues a warning (in the 'portability' category) if
456 'configure.in' is used instead of 'configure.ac' as the Autoconf
457 input file. Such a warning will also be present in the next
458 Autoconf version (2.70).
462 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
463 order (as done by the other recursive rules), rather than in the
464 inverse order. They used to do that in order to work a round a
465 limitation in an older implementation of the automatic dependency
466 tracking support, but that limitation had been lifted years ago
467 already, when the automatic dependency tracking based on side-effects
468 of compilation had been introduced.
470 - Cleaning rules for compiled objects (both "plain" and libtool) work
471 better when subdir objects are involved, not triggering a distinct
472 'rm' invocation for each such object. They do so by removing *any*
473 compiled object file that is in the same directory of a subdir
474 object. See automake bug#10697.
476 * Silent rules support:
478 - A new predefined $(AM_V_P) make variable is provided; it expands
479 to a shell conditional that can be used in recipes to know whether
480 make is being run in silent or verbose mode.
482 Bugs fixed in 1.12.2:
484 * SECURITY VULNERABILITIES!
486 - The 'distcheck' recipe no longer grants temporary world-write
487 permissions on the extracted distdir. Even if such rights were
488 only granted for a vanishingly small time window, the implied
489 race condition proved to be enough to allow a local attacker
490 to run arbitrary code with the privileges of the user running
491 "make distcheck". This is CVE-2012-3386.
493 * Long-standing bugs:
495 - The "recheck" targets behaves better in the face of build failures
496 related to previously failed tests. For example, if a test is a
497 compiled program that must be rerun by "make recheck", and its
498 compilation fails, it will still be rerun by further "make recheck"
499 invocations. See automake bug#11791.
501 * Bugs introduced by 1.12.1:
503 - Automake provides once again the '$(mkdir_p)' make variable and the
504 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
505 for better backward-compatibility.
507 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
511 * New supported languages:
513 - Support for Objective C++ has been added; it should work similarly to
514 the support for Objective C.
516 * Deprecated obsolescent features:
518 - Use of the long-deprecated two- and three-arguments invocation forms
519 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
520 category. Starting from some future major Automake release (likely
521 post-1.13), such usages will no longer be allowed.
523 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
524 now deprecated (its use triggers a warning in the 'obsolete' category).
525 It will be removed in the next major Automake release (1.13).
527 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
528 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
529 m4 macro are deprecated, eliciting a warning in the 'obsolete'
532 * Miscellaneous changes:
534 - The Automake test cases now require a proper POSIX-conforming shell.
535 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
536 be accepted. In most cases, the user shouldn't have to specify such
537 POSIX shell explicitly, since it will be looked up at configure time.
538 Still, when this lookup fails, or when the user wants to override its
539 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
540 to the shell that will be used to run the Automake test cases).
542 Bugs fixed in 1.12.1:
544 * Bugs introduced by 1.12:
546 - Several weaknesses in Automake's own build system and test suite
549 * Bugs introduced by 1.11.3:
551 - When given non-option arguments, aclocal rejects them, instead of
552 silently ignoring them.
554 * Long-standing bugs:
556 - When the 'color-tests' option is in use, forcing of colored testsuite
557 output through "AM_COLOR_TESTS=always" works even if the terminal is
558 a non-ANSI one, i.e., if the TERM environment variable has a value of
561 - Several inefficiencies and poor performances in the implementation
562 of the parallel-tests 'check' and 'recheck' targets have been fixed.
564 - The post-processing of output "#line" directives done the ylwrap
565 script is more faithful w.r.t. files in a subdirectory; for example,
566 if the processed file is "src/grammar.y", ylwrap will correctly
567 produce directives like:
568 #line 7 "src/grammar.y"
573 * Bugs with new Perl versions:
575 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
577 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
581 * Obsolete features removed:
583 - The never documented nor truly used script 'acinstall' has been
586 - Support for automatic de-ANSI-fication has been removed.
588 - The support for the "obscure" multilib feature has been removed
589 from Automake core (but remains available in the 'contrib/'
590 directory of the Automake distribution).
592 - Support for ".log -> .html" conversion and the check-html and
593 recheck-html targets has been removed from Automake core (but
594 remains available in the 'contrib/' directory of the Automake
597 - The deprecated 'lzma' compression format for distribution archives
598 has been removed, in favor of 'xz' and 'lzip'.
600 - The obsolete AM_WITH_REGEX macro has been removed.
602 - The long-deprecated options '--output-dir', '--Werror' and
603 '--Wno-error' have been removed.
605 - The chapter on the history of Automake has been moved out of the
606 reference manual, into a new dedicated Texinfo file.
610 - New 'cscope' target to build a cscope database for the source tree.
612 * Changes to Automake-generated testsuite harnesses:
614 - The new automake option 'serial-tests' has been introduced. It can
615 be used to explicitly instruct automake to use the older serial
616 testsuite harness. This is still the default at the moment, but it
617 might change in future versions.
619 - The 'recheck' target (provided by the parallel testsuite harness) now
620 depends on the 'all' target. This allows for a better user-experience
621 in test-driven development. See automake bug#11252.
623 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
624 and unexpected or internal error, or a failure to set up the test case
625 scenario) have their outcome reported as an 'ERROR' now. Previous
626 versions of automake reported such an outcome as a 'FAIL' (the only
627 difference with normal failures being that hard errors were counted
628 as failures even when the test originating them was listed in
631 - The testsuite summary displayed by the parallel-test harness has a
632 completely new format, that always list the numbers of passed, failed,
633 xfailed, xpassed, skipped and errored tests, even when these numbers
634 are zero (but using smart coloring when the color-tests option is in
637 - The default testsuite driver offered by the 'parallel-tests' option is
638 now implemented (partly at least) with the help of automake-provided
639 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
640 on code in the generated Makefile.in.
641 This has two noteworthy implications. The first one is that projects
642 using the 'parallel-tests' option should now either run automake with
643 the '--add-missing' option, or manually copy the 'test-driver' script
644 into their tree. The second, and more important, implication is that
645 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
646 no longer be used to define a test runner, and the command specified
647 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
648 program or script. For example, this is still a valid usage (albeit
651 TESTS_ENVIRONMENT = \
652 if test -n '$(STRICT_TESTS)'; then \
653 maybe_errexit='-e'; \
657 LOG_COMPILER = $(SHELL) $$maybe_errexit
659 OTOH, this is no longer a valid usage:
661 TESTS_ENVIRONMENT = \
662 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
666 TESTS_ENVIRONMENT = \
667 run_with_perl_or_shell () \
669 if grep -q '^#!.*perl' $$1; then
675 LOG_COMPILER = run_with_perl_or_shell
677 - The package authors can now use customary testsuite drivers within
678 the framework provided by the 'parallel-tests' testsuite harness.
679 Consistently with the existing syntax, this can be done by defining
680 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
682 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
683 to redirect/define file descriptors used by the test scripts.
685 - The parallel-tests harness generates now, in addition the '.log' files
686 holding the output produced by the test scripts, a new set of '.trs'
687 files, holding "metadata" derived by the execution of the test scripts;
688 among such metadata are the outcomes of the test cases run by a script.
690 - Initial and still experimental support for the TAP test protocol is
693 * Changes to Yacc and Lex support:
695 - C source and header files derived from non-distributed Yacc and/or
696 Lex sources are now removed by a simple "make clean" (while they were
697 previously removed only by "make maintainer-clean").
699 - Slightly backward-incompatible change, relevant only for use of Yacc
700 with C++: the extensions of the header files produced by the Yacc
701 rules are now modelled after the extension of the corresponding
702 sources. For example, yacc files named "foo.y++" and "bar.yy" will
703 produce header files named "foo.h++" and "bar.hh" respectively, where
704 they would have previously produced header files named simply "foo.h"
705 and "bar.h". This change offers better compatibility with 'bison -o'.
707 * Miscellaneous changes:
709 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
710 rather than 1, if the vala compiler found is too old.
712 - The build system of Automake itself now avoids the use of make
713 recursion as much as possible.
715 - Automake now prefers to quote 'like this' or "like this", rather
716 than `like this', in diagnostic message and generated Makefiles,
717 to accommodate the new GNU Coding Standards recommendations.
719 - Automake has a new option '--print-libdir' that prints the path of the
720 directory containing the Automake-provided scripts and data files.
722 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
724 - The rules to create pdf, dvi and ps output from Texinfo files now
725 works better with modern 'texi2dvi' script, by explicitly passing
726 it the '--clean' option to ensure stray auxiliary files are not
727 left to clutter the build directory.
729 - Automake can now generate silenced rules for texinfo outputs.
731 - Some auxiliary files that are automatically distributed by Automake
732 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
733 C sources) might now be listed in the DIST_COMMON variable in many
734 Makefile.in files, rather than in the top-level one.
736 - Messages of types warning or error from 'automake' and 'aclocal'
737 are now prefixed with the respective type, and presence of -Werror
740 - Automake's early configure-time sanity check now tries to avoid
741 sleeping for a second, which slowed down cached configure runs
742 noticeably. In that case, it will check back at the end of the
743 configure script to ensure that at least one second has passed, to
744 avoid time stamp issues with makefile rules rerunning autotools
747 - The warnings in the category 'extra-portability' are now enabled by
748 '-Wall'. In previous versions, one has to use '-Wextra-portability'
753 - Various minor bugfixes for recent or long-standing bugs.
755 * Bugs introduced by 1.11:
757 - The AM_COND_IF macro also works if the shell expression for the
758 conditional is no longer valid for the condition.
760 - The automake-provided parallel testsuite harness no longer fails
761 with BSD make used in parallel mode when there are test scripts in
762 a subdirectory, like in:
764 TESTS = sub/foo.test sub/bar.test
766 * Long-standing bugs:
768 - Automake's own build system finally have a real "installcheck" target.
770 - Vala-related cleanup rules are now more complete, and work better in
773 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
774 now automatically distributed also if the directory of the auxiliary
775 files coincides with the top-level directory.
777 - Automake now detects the presence of the '-d' flag in the various
778 '*YFLAGS' variables even when their definitions involve indirections
779 through other variables, such as in:
781 AM_YFLAGS = $(foo_opts)
783 - Automake now complains if a '*YFLAGS' variable has any conditional
784 content, not only a conditional definition.
786 - Explicit enabling and/or disabling of Automake warning categories
787 through the '-W...' options now always takes precedence over the
788 implicit warning level implied by Automake strictness (foreign, gnu
789 or gnits), regardless of the order in which such strictness and
790 warning flags appear. For example, a setting like:
791 AUTOMAKE_OPTIONS = -Wall --foreign
792 will cause the warnings in category 'portability' to be enabled, even
793 if those warnings are by default disabled in 'foreign' strictness.
795 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
797 Bugs fixed in 1.11.5:
799 * Bugs introduced by 1.11.3:
801 - Vala files with '.vapi' extension are now recognized and handled
802 correctly again. See automake bug#11222.
804 - Vala support work again for projects that contain some program
805 built from '.vala' (and possibly '.c') sources and some other
806 program built from '.c' sources *only*. See automake bug#11229.
808 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
812 * Miscellaneous changes:
814 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
815 symbol index) modifiers as well as the "s" action, as the symbol index
816 is created unconditionally by Microsoft lib. Also, the "q" (quick)
817 action is now a synonym for "r" (replace). Also, the script has been
818 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
820 - When the 'compile' script is used to wrap MSVC, it now accepts an
821 optional space between the -I, -L and -l options and their respective
822 arguments, for better POSIX compliance.
824 - There is an initial, experimental support for automatic dependency
825 tracking with tcc (the Tiny C Compiler). Its associated depmode is
826 currently recognized as "icc" (but this and other details are likely
827 to change in future versions).
829 - Automatic dependency tracking now works also with the IBM XL C/C++
830 compilers, thanks to the new new depmode 'xlc'.
832 Bugs fixed in 1.11.4:
834 * Bugs introduced by 1.11.2:
836 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
837 no longer cause spurious failures upon "make install".
839 - The user can now instruct the 'uninstall-info' rule not to update
840 the '${infodir}/dir' file by exporting the environment variable
841 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
842 with how the 'install-info' rule operates since automake 1.11.2.
844 * Long-standing bugs:
846 - It is now possible for a foo_SOURCES variable to hold Vala sources
847 together with C header files, as well as with sources and headers for
848 other supported languages (e.g., C++). Previously, only mixing C and
849 Vala sources was supported.
851 - If "aclocal --install" is used, and the first directory specified with
852 '-I' is non-existent, aclocal will now create it before trying to copy
855 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
856 install rules to create an empty $(foodir) directory; for example, if
857 Makefile.am contains something like:
861 pkglibexec_SCRIPTS += bar.sh
864 the $(pkglibexec) directory will not be created upon "make install".
866 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
870 * Miscellaneous changes:
872 - Automake's own build system is more silent by default, making use of
873 the 'silent-rules' option.
875 - The master copy of the 'gnupload' script is now maintained in gnulib,
878 - The 'missing' script no longer tries to wrap calls to 'tar'.
880 - "make dist" no longer wraps 'tar' invocations with the 'missing'
881 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
882 shouldn't be using BTW ;-) no longer invokes the 'missing' script
883 to wrap tar, but simply invokes the 'tar' program itself.
885 - "make dist" can now create lzip-compressed tarballs.
887 - In the Automake info documentation, the Top node and the nodes about
888 the invocation of the automake and aclocal programs have been renamed;
889 now, calling "info automake" will open the Top node, while calling
890 "info automake-invocation" and "info aclocal-invocation" will access
891 the nodes about the invocation of respectively automake and aclocal.
893 - Automake is now distributed as a gzip-compressed and an xz-compressed
894 tarball. Previously, bzip2 was used instead of xz.
896 - The last relics of Python 1.5 support have been removed from the
897 AM_PATH_PYTHON macro.
899 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
900 and adds them to the normal list of dependencies, but without
901 overwriting the foo_DEPENDENCIES variable, which is normally computed
904 Bugs fixed in 1.11.3:
906 * Bugs introduced by 1.11.2:
908 - Automake now correctly recognizes the prefix/primary combination
909 'pkglibexec_SCRIPTS' as valid.
911 - The parallel-tests harness no longer trips on sed implementations
912 with stricter limits on the length of input lines (problem seen at
915 * Long-standing bugs:
917 - The "deleted header file problem" for *.am files is avoided by stub
918 rules. This allows 'make' to trigger a rerun of 'automake' also if
919 some previously needed '.am' file has been removed.
921 - The 'silent-rules' option now generates working makefiles even
922 for the uncommon 'make' implementations that do not support the
923 nested-variables extension to POSIX 2008. For such 'make'
924 implementations, whether a build is silent is determined at
925 configure time, and cannot be overridden at make time with
926 "make V=0" or "make V=1".
928 - Vala support now works better in VPATH setups.
930 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
934 * Changes to aclocal:
936 - The `--acdir' option is deprecated. Now you should use the new options
937 `--automake-acdir' and `--system-acdir' instead.
939 - The `ACLOCAL_PATH' environment variable is now interpreted as a
940 colon-separated list of additional directories to search after the
941 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
942 and before the system acdir (by default ${prefix}/share/aclocal).
944 * Miscellaneous changes:
946 - The Automake support for automatic de-ANSI-fication has been
947 deprecated. It will probably be removed in the next major Automake
950 - The `lzma' compression scheme and associated automake option `dist-lzma'
951 is obsoleted by `xz' and `dist-xz' due to upstream changes.
953 - You may adjust the compression options used in dist-xz and dist-bzip2.
954 The default is now merely -e for xz, but still -9 for bzip; you may
955 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
956 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
958 - The `compile' script now converts some options for MSVC for a better
959 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
961 - The py-compile script now accepts empty arguments passed to the options
962 `--destdir' and `--basedir', and complains about unrecognized options.
963 Moreover, a non-option argument or a special `--' argument terminates
966 - A developer that needs to pass specific flags to configure at "make
967 distcheck" time can now, and indeed is advised to, do so by defining
968 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
969 instead of the old DISTCHECK_CONFIGURE_FLAGS.
970 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
971 user; still, the old Makefile.am files that used to define it will
972 still continue to work as before.
974 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
975 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
976 This new macro is required for LIBRARIES and LTLIBRARIES when automake
977 is run with -Wextra-portability and -Werror.
979 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
980 file generated by automake-provided rules by defining the special make
981 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
983 - The `install-info' rule can now be instructed not to create/update
984 the `${infodir}/dir' file, by exporting the new environment variable
985 `AM_UPDATE_INFO_DIR' to the value "no".
987 Bugs fixed in 1.11.2:
989 * Bugs introduced by 1.11:
991 - The parallel-tests driver no longer produces erroneous results with
992 Tru64/OSF 5.1 sh upon unreadable log files.
994 - The `parallel-tests' test driver does not report spurious successes
995 when used with concurrent FreeBSD make (e.g., "make check -j3").
997 - When the parallel-tests driver is in use, automake now explicitly
998 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
999 instead of issuing confusing and apparently unrelated error messages
1000 (e.g., "non-POSIX variable name", "bad characters in variable name",
1001 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1002 silently producing broken `Makefile.in' files.
1004 - The `silent-rules' option now truly silences all compile rules, even
1005 when dependency tracking is disabled. Also, when `silent-rules' is
1006 not used, `make' output no longer contains spurious backslash-only
1007 lines, thus once again matching what Automake did before 1.11.
1009 - The AM_COND_IF macro also works if the shell expression for the
1010 conditional is no longer valid for the condition.
1012 * Long-standing bugs:
1014 - The order of Yacc and Lex flags is fixed to be consistent with other
1015 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1016 $(LFLAGS), so that the user variables override the developer variables.
1018 - "make distcheck" now correctly complains also when "make uninstall"
1019 leaves one and only one file installed in $(prefix).
1021 - A "make uninstall" issued before a "make install", or after a mere
1022 "make install-data" or a mere "make install-exec" does not spuriously
1025 - Automake now warns about more primary/directory invalid combinations,
1026 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1028 - Rules generated by Automake now try harder to not change any files when
1029 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1030 Yacc source files and the rule to update config.h.
1032 - Several scripts and the parallel-tests testsuite driver now exit with
1033 the right exit status upon receiving a signal.
1035 - A per-Makefile.am setting of -Werror does not erroneously carry over
1036 to the handling of other Makefile.am files.
1038 - The code for automatic dependency tracking works around a Solaris
1039 make bug triggered by sources containing repeated slashes when the
1040 `subdir-objects' option was used.
1042 - The makedepend and hp depmodes now work better with VPATH builds.
1044 - Java sources specified with check_JAVA are no longer compiled for
1045 "make all", but only for "make check".
1047 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1048 and error out if `javadir' is undefined, instead of silently producing
1049 a broken Makefile.in.
1051 - aclocal and automake now honour the configure-time definitions of
1052 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1054 - The `install-info' recipe no longer tries to guess whether the
1055 `install-info' program is from Debian or from GNU, and adaptively
1056 change its behaviour; this has proven to be frail and easy to
1059 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1061 Bugs fixed in 1.11.1:
1063 - Lots of minor bugfixes.
1065 * Bugs introduced by 1.11:
1067 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1068 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1070 * Long standing bugs:
1072 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1073 even if the `--prefix' argument pointed outside of a system directory.
1074 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1075 `get_python_lib' function if it points outside the configured prefix,
1076 unless the `--prefix' argument was either `/usr' or below `/System'.
1078 - The testsuite does not try to change the mode of `ltmain.sh' files from
1079 a Libtool installation (symlinked to test directories) any more.
1081 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1082 tools are preferred in a cross-compile setup.
1084 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1085 This fixes a race condition where untrusted users could modify files
1086 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1087 build directory was world-searchable. This is CVE-2009-4029.
1089 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1093 * Version requirements:
1095 - Autoconf 2.62 or greater is required.
1097 * Changes to aclocal:
1099 - The autoconf version check implemented by aclocal in aclocal.m4
1100 (and new in Automake 1.10) is degraded to a warning. This helps
1101 in the common case where the Autoconf versions used are compatible.
1103 * Changes to automake:
1105 - The automake program can run multiple threads for creating most
1106 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1107 with interpreter-based threads enabled. Set the environment variable
1108 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1109 enable this experimental feature.
1111 * Changes to Libtool support:
1113 - Libtool generic flags are now passed to the install and uninstall
1116 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1117 config.lt is removed correctly now.
1119 * Languages changes:
1121 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1122 Fortran, and Ratfor).
1124 - For files with extension .f90, .f95, .f03, or .f08, the flag
1125 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1127 - Files with extension .sx are also treated as preprocessed assembler.
1129 - The default source file extension (.c) can be overridden with
1130 AM_DEFAULT_SOURCE_EXT now.
1132 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1135 - AM_PATH_PYTHON honors python's idea about the site directory.
1137 - There is initial support for the Vala programming language, when using
1138 Vala 0.7.0 or later.
1140 * Miscellaneous changes:
1142 - Automake development is done in a git repository on Savannah now, see
1144 http://git.sv.gnu.org/gitweb/?p=automake.git
1146 A read-only CVS mirror is provided at
1148 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1149 checkout -d automake HEAD
1151 - "make dist" can now create xz-compressed tarballs,
1152 as well as (deprecated?) lzma-compressed tarballs.
1154 - `automake --add-missing' will by default install the GPLv3 file as
1155 COPYING if it is missing. It will also warn that the license file
1156 should be added to source control. Note that Automake will never
1157 overwrite an existing COPYING file, even when the `--force-missing'
1160 - The manual is now distributed under the terms of the GNU FDL 1.3.
1162 - Automake ships and installs man pages for automake and aclocal now.
1164 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1166 - install-sh supports -C, which does not update the installed file
1167 (and its time stamps) if the contents did not change.
1169 - The `gnupload' script has been revamped.
1171 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1173 - The targets `install' and `uninstall' are more efficient now, in that
1174 for example multiple files from one Automake variable such as
1175 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1176 invocation if they do not have to be renamed.
1178 Both install and uninstall may sometimes enter (`cd' into) the target
1179 installation directory now, when no build-local scripts are used.
1181 Both install and uninstall do not fail anymore but do nothing if an
1182 installation directory variable like `bindir' is set to the empty string.
1184 For built-in rules, `make install' now fails reliably if installation
1185 of a file failed. Conversely, `make uninstall' even succeeds when
1186 issued multiple times.
1188 These changes may need some adjustments from users: For example,
1189 some `install' programs refuse to install multiple copies of the
1190 same file in one invocation, so you may need to remove duplicate
1191 entries from file lists.
1193 Also, within one set of files, say, nobase_data_DATA, the order of
1194 installation may be changed, or even unstable among different hosts,
1195 due to the use of associative arrays in awk. The increased use of
1196 awk matches a similar move in Autoconf to provide for better scaling.
1198 Further, most undocumented per-rule install command variables such as
1199 binSCRIPT_INSTALL have been removed because they are not needed any
1200 more. Packages which use them should be using the appropriate one of
1201 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1202 counterpart, depending on the type of files and the need for automatic
1203 target directory creation.
1205 - The "deleted header file problem" for *.m4 files is avoided by
1206 stub rules. This allows `make' to trigger a rerun of `aclocal'
1207 also if some previously needed macro file has been removed.
1209 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1210 an otherwise up to date tree.
1212 - The `color-tests' option causes colored test result output on terminals.
1214 - The `parallel-tests' option enables a new test driver that allows for
1215 parallel test execution, inter-test dependencies, lazy test execution
1216 for unit-testing, re-testing only failed tests, and formatted result output
1217 as RST (reStructuredText) and HTML. Enabling this option may require some
1218 changes to your test suite setup; see the manual for details.
1220 - The `silent-rules' option enables Linux kernel-style silent build output.
1221 This option requires the widely supported but non-POSIX `make' feature
1222 of recursive variable expansion, so do not use it if your package needs
1223 to build with `make' implementations that do not support it.
1225 To enable less verbose build output, the developer has to use the Automake
1226 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1227 macro. The user may then set the default verbosity by passing the
1228 `--enable-silent-rules' option to `configure'. At `make' run time, this
1229 default may be overridden using `make V=0' for less verbose, and `make V=1'
1230 for backward-compatible verbose output.
1232 - New prefix `notrans_' for manpages which should not be transformed
1233 by --program-transform.
1235 - New macro AM_COND_IF for conditional evaluation and conditional
1238 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1239 remove the file in a non-VPATH build. Such setups work with Autoconf
1242 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1243 the default setting.
1245 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1246 useful especially for multi-line values.
1248 - Automake's early configure-time sanity check now diagnoses an
1249 unsafe absolute source directory name and makes configure fail.
1251 - The Automake macros and rules cope better with whitespace in the
1252 current directory name, as long as the relative path to `configure'
1253 does not contain whitespace. To this end, the values of `$(MISSING)'
1254 and `$(install_sh)' may contain suitable quoting, and their expansion
1255 might need `eval'uation if used outside of a makefile. These
1256 undocumented variables may be used in several documented macros such
1257 as $(AUTOCONF) or $(MAKEINFO).
1261 * Long-standing bugs:
1263 - Fix aix dependency tracking for libtool objects.
1265 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1266 unnecessary use of the `compile' script.
1268 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1269 correct `-rpath' argument is used now.
1271 - `config.status --file=Makefile depfiles' now also works with the
1272 extra quoting used internally by Autoconf 2.62 and newer
1273 (it used to work only without the `--file=' bit).
1275 - The `missing' script works better with versioned tool names.
1277 - Semantics for `missing help2man' have been revamped:
1279 Previously, if `help2man' was not present, `missing help2man' would have
1280 the following semantics: if some man page was out of date but present, then
1281 a warning would be printed, but the exit status was 0. If the man page was
1282 not present at all, then `missing' would create a replacement man page
1283 containing an error message, and exit with a status of 2. This does not play
1284 well with `make': the next run will see this particular man page as being up
1285 to date, and will only error out on the next generated man page, if any;
1286 repeat until all pages are done. This was not desirable.
1288 These are the new semantics: if some man page is not present, and help2man
1289 is not either, then `missing' will warn and generate the replacement page
1290 containing the error message, but exit successfully. However, `make dist'
1291 will ensure that no such bogus man pages are packaged into a tarball.
1293 - Targets provided by automake behave better with `make -n', in that they
1294 take care not to create files.
1296 - `config.status Makefile... depfiles' works fine again in the presence of
1297 disabled dependency tracking.
1299 - The default no-op recursive rules for these targets also work with BSD make
1300 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1302 - `make distcheck' works also when both a directory and some file below it
1303 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1305 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1306 `make mostlyclean' any more; only the LaTeX by-products are.
1308 - Renamed objects also work with the `subdir-objects' option and
1309 source file languages which Automake does not know itself.
1311 - `automake' now correctly complains about variable assignments which are
1312 preceded by a comment, extend over multiple lines with backslash-escaped
1313 newlines, and end in a comment sign. Previous versions would silently
1314 and wrongly ignore such assignments completely.
1316 * Bugs introduced by 1.10:
1318 - Fix output of dummy dependency files in presence of post-processed
1319 Makefile.in's again, but also cope with long lines.
1321 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1322 that have been declared as programs in the same Makefile.
1323 This is for consistency with the analogous change to TESTS in 1.10.
1325 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1326 followed by directories containing config headers.
1328 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1332 * Version requirements:
1334 - Autoconf 2.60 or greater is required.
1336 - Perl 5.6 or greater is required.
1338 * Changes to aclocal:
1340 - aclocal now also supports -Wmumble and -Wno-mumble options.
1342 - `dirlist' entries (for the aclocal search path) may use shell
1343 wildcards such as `*', `?', or `[...]'.
1345 - aclocal supports an --install option that will cause system-wide
1346 third-party macros to be installed in the local directory
1347 specified with the first -I flag. This option also uses #serial
1348 lines in M4 files to upgrade local macros.
1350 The new aclocal options --dry-run and --diff help to review changes
1351 before they are installed.
1353 - aclocal now outputs an autoconf version check in aclocal.m4 in
1354 projects using automake.
1356 For a few years, automake and aclocal have been calling autoconf
1357 (or its underlying engine autom4te) to accurately retrieve the
1358 data they need from configure.ac and its siblings. Doing so can
1359 only work if all autotools use the same version of autoconf. For
1360 instance a Makefile.in generated by automake for one version of
1361 autoconf may stop working if configure is regenerated with another
1362 version of autoconf, and vice versa.
1364 This new version check ensures that the whole build system has
1365 been generated using the same autoconf version.
1367 * Support for new Autoconf macros:
1369 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1371 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1372 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1373 in different directories. However, only one instance of such a
1374 library objects directory is supported.
1376 * Change to Libtool support:
1378 - Libtool generic flags (those that go before the --mode=MODE option)
1379 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1381 * Yacc and Lex changes:
1383 - The rebuild rules for distributed Yacc and Lex output will avoid
1384 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1387 - ylwrap is now always used for lex and yacc source files,
1388 regardless of whether there is more than one source per directory.
1390 * Languages changes:
1392 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1393 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1394 tracking, unlike non-preprocessed assembler (*.s).
1396 - subdir-object mode works now with Assembler. Automake assumes
1397 that the compiler understands `-c -o'.
1399 - Preprocessed assembler (*.S) compilation now also honors
1400 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1402 - Improved support for Objective C:
1403 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1404 - A new section of the manual documents the support.
1406 - New support for Unified Parallel C:
1407 - AM_PROG_UPC looks for a UPC compiler.
1408 - A new section of the manual documents the support.
1410 - Per-target flags are now correctly handled in link rules.
1412 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1413 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1414 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1415 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1417 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1418 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1419 is expected to work (and actually works during compilation).
1421 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1422 "in addition to" breaks backward compatibility with older versions.
1423 If your package used both variables, as in
1425 AM_LDFLAGS = common flags
1426 bin_PROGRAMS = a b c
1427 a_LDFLAGS = more flags
1430 and assumed *_LDFLAGS would sum up, you should rewrite it as
1432 AM_LDFLAGS = common flags
1433 bin_PROGRAMS = a b c
1434 a_LDFLAGS = $(AM_LDFLAGS) more flags
1437 This new behavior of *_LDFLAGS is more coherent with other
1438 per-target variables, and the way *_LDFLAGS variables were
1439 considered internally.
1441 * New installation targets:
1443 - New targets mandated by GNU Coding Standards:
1448 By default they will only install Texinfo manuals.
1449 You can customize them with *-local variants:
1455 - The undocumented recursive target `uninstall-info' no longer exists.
1456 (`uninstall' is in charge of removing all possible documentation
1457 flavors, including optional formats such as dvi, ps, or info even
1458 when `no-installinfo' is used.)
1460 * Miscellaneous changes:
1462 - Automake no longer complains if input files for AC_CONFIG_FILES
1463 are specified using shell variables.
1465 - clean, distribution, or rebuild rules are normally disabled for
1466 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1467 AC_CONFIG_LINK specified using shell variables. However, if these
1468 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1469 be able to output rules anyway.
1470 (See the Automake documentation for AC_CONFIG_FILES.)
1472 - $(EXEEXT) is automatically appended to filenames of TESTS
1473 that have been declared as programs in the same Makefile.
1474 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1476 - `-Wportability' has finally been turned on by default for `gnu' and
1477 `gnits' strictness. This means, automake will complain about %-rules
1478 or $(GNU Make functions) unless you switch to `foreign' strictness or
1479 use `-Wno-portability'.
1481 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1482 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1483 $(mkdir_p) variable is still defined (to the same value as
1484 $(MKDIR_P)) but should be considered obsolete. If you are using
1485 $(mkdir_p) in some of your rules, please plan to update them to
1486 $(MKDIR_P) at some point.
1488 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1489 They still work in this release, but may be withdrawn in a future one.
1491 - Inline compilation rules for gcc3-style dependency tracking are
1494 - Automake installs a "Hello World!" example package in $(docdir).
1495 This example is used throughout the new "Autotools Introduction"
1496 chapter of the manual.
1498 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1502 * Makefile.in bloat reduction:
1504 - Inference rules are used to compile sources in subdirectories when
1505 the `subdir-objects' option is used and no per-target flags are
1506 used. This should reduce the size of some projects a lot, because
1507 Automake used to output an explicit rule for each such object in
1510 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1511 object that must be built with explicit rules. It just outputs
1512 the rules required to build the kind of object considered: either
1513 the two .o and .obj rules for usual objects, or the .lo rule for
1516 * Change to Libtool support:
1518 - Libtool tags are used with libtool versions that support them.
1519 (I.e., with Libtool 1.5 or greater.)
1521 - Automake is now able to handle setups where a libtool library is
1522 conditionally installed in different directories, as in
1525 lib_LTLIBRARIES = liba.la
1527 pkglib_LTLIBRARIES = liba.la
1529 liba_la_SOURCES = ...
1531 * Changes to aclocal:
1533 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1534 really evaluated, before it decides to include them in aclocal.m4.
1535 This solves nasty problems with conditional redefinitions of
1536 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1537 *.m4 files to be included in any project using these macros.
1538 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1539 most famous instance of this bug.)
1541 - Do not complain about missing conditionally AC_REQUIREd macros
1542 that are not actually used. In 1.8.x aclocal would correctly
1543 determine which of these macros were really needed (and include
1544 only these in the package); unfortunately it would also require
1545 all of them to be present in order to run. This created
1546 situations were aclocal would not work on a tarball distributing
1547 all the macros it uses. For instance running aclocal on a project
1548 containing only the subset of the Gettext macros in use by the
1549 project did not work, because gettext conditionally requires other
1552 * Portability improvements:
1554 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1555 tar-pax. The new option filename-length-max=99 helps diagnosing
1556 filenames that are too long for tar-v7. (PR/414)
1558 - Variables aumented with `+=' are now automatically flattened (i.e.,
1559 trailing backslashes removed) and then wrapped around 80 colummns
1560 (adding trailing backslashes). In previous versions, a long series
1566 would result in a single-line definition of VAR that could possibly
1567 exceed the maximum line length of some make implementations.
1569 Non-augmented variables are still output as they are defined in
1574 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1575 Works the same as the old Fortran 77 implementation; just replace
1576 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1577 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1579 - Support for conditional _LISP.
1581 - Support for conditional -hook and -local rules (PR/428).
1583 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1585 - Automake will not write any Makefile.ins after the first error it
1586 encounters. The previous Makefile.ins (if any) will be left in
1587 place. (Warnings will not prevent output, but remember they can
1588 be turned into errors with -Werror.)
1590 - The restriction that SUBDIRS must contain direct children is gone.
1593 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1594 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1596 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1598 Bugs fixed in 1.8.5:
1600 * Long-standing bugs:
1602 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1603 so that `make distclean' and `make maintainer-clean' can work.
1605 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1607 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1609 - Polish diagnostic when no input file is found.
1611 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1613 Bugs fixed in 1.8.4:
1615 * Long-standing bugs:
1617 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1618 overridden by the user.
1620 - Honor PATH_SEPARATOR in various places of the Automake package, for
1623 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1626 - Fix install-sh so it can install the `mv' binary... using `mv'.
1628 - Fix tru64 dependency tracking for libtool objects.
1630 - Work around Exuberant Ctags when creating a TAGS files in a directory
1631 without files to scan but with subdirectories to include.
1633 * Bugs introduced by 1.8:
1635 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1636 not defined in the same conditions as the _LDADD that uses it.
1638 - Do not warn when JAVAROOT is overridden, this is legitimate.
1640 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1642 Bugs fixed in 1.8.3:
1644 * Long-standing bugs:
1646 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1647 or any of the other *dir variables contain a space.
1649 Please note that Automake does not and cannot support spaces in
1650 filenames that are involved during the build. This change affects
1651 only installation paths, so that `make install' does not bomb out
1652 in packages configured with
1653 ./configure --prefix '/c/Program Files'
1655 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1656 POSIXLY_CORRECT is set.
1658 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1659 since Autoconf 2.54, which defines LIBOBJS itself.
1661 - Fix a potential (but unlikely) race condition in parallel elisp
1662 builds. (Introduced in 1.7.3.)
1664 - Do not assume that users override _DEPENDENCIES in all conditions
1665 where Automake will try to define them.
1667 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1668 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1671 This fix also affects the $(mkdir_p) variable defined since
1672 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1673 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1675 - Secure temporary directory creation in `make distcheck'. (PR/413)
1677 - Do not generate two build rules for `parser.h' when the
1678 parser appears in two different conditionals.
1680 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1681 checking. Usually ./configure will not pick this shell; so this
1682 fix only helps cases where the shell is forced to /bin/sh.
1684 * Bugs introduced by 1.8:
1686 - In some situations (hand-written `m4_include's), aclocal would
1687 call the `File::Spec->rel2abs' method, which was only introduced
1688 in Perl 5.6. This new version reestablish support Perl 5.005.
1690 It is likely that the next major Automake releases will require at
1691 least Perl 5.6. Consider upgrading your development environment
1692 if you are still using the five-year-old Perl 5.005.
1694 - Automake would sometimes fail to define rules for targets listed
1695 in variables defined in multiple conditions. For instance on
1701 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1702 `b.$(OBJEXT): b.c' rule.
1704 * New sections in manual:
1706 - Third-Party Makefiles: how to interface third party Makefiles.
1707 - Upgrading: upgrading packages to newer Automake versions.
1708 - Multiple Outputs: handling tools that produce many outputs.
1710 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1714 * A (well known) portability bug slipped in the changes made to
1715 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1716 install anything on Tru64.
1718 * Fix install rules for conditionally built python files. (This never
1721 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1725 * Bugs introduced by 1.8:
1727 - Fix Config.pm import error with old Perl versions (at least
1728 5.005_03). One symptom is that aclocal could not find its macro
1731 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1732 created by `make install' are always world readable, even if the
1733 installer happens to have an overly restrictive umask (e.g. 077).
1734 This was a mistake and has been reverted. There are at least two
1735 reasons why we must not use `-m 0755':
1736 - it causes special bits like SGID to be ignored,
1737 - it may be too restrictive (some setups expect 775 directories).
1739 - Fix aclocal to honor definitions located in files which have been
1740 m4_included manually. aclocal 1.8 had been updated to check
1741 m4_included files for new requirements, but forgot that these
1742 m4_included files can also provide new definitions.
1744 Note that if you have such a setup, we recommend you get rid of
1745 it. In the past, there was a reason to m4_include files manually:
1746 aclocal used to duplicate entire M4 files into aclocal.m4, even
1747 files that were distributed. Some packages were therefore
1748 m4_including the distributed file directly, and playing some
1749 tricks to ensure aclocal would not copy that file to aclocal.m4,
1750 in order to limit the amount of duplication. Since aclocal 1.8.x
1751 will precisely output m4_includes for local M4 files, we recommend
1752 that you clean up your setup, removing all manual m4_includes and
1753 letting aclocal output them.
1755 - Output detailed menus in the Info version if the Automake manual,
1756 so that Emacs can locate the indexes.
1758 - configure.ac and configure were listed twice in DIST_COMMON (an
1759 internal variable where Automake lists configury files to
1760 distribute). This was harmless, but unaesthetic.
1762 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1763 This was an issue only in the Automake package itself, not in
1766 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1767 DEST:SRC. This was wrong, as some packages do
1768 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1771 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1772 argument. This caused two kinds of failures:
1773 - Rules installing data in a conditionally defined directory
1774 failed when that directory was undefined. In this case no
1775 argument was supplied.
1776 - `make installdirs' failed, because several directories were
1777 passed to $(mkdir_p). This was an issue only on platform
1778 were $(mkdir_p) is implemented with `install-sh -d'.
1779 $(mkdir_p) as been changed to accept 0 or more arguments, as
1782 * Long-standing bugs:
1784 - Fix an unexpected diagnostic occurring when users attempt
1785 to override some internal variables that Automake appends to.
1787 - aclocal now scans configure.ac for macro definitions (PR/319).
1789 - Fix a portability issue with OSF1/Tru64 Make. If a directory
1790 distributes files which are outside itself (this usually occurs
1791 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
1792 from a parent package), then `make distcheck' fails due to an
1793 optimization performed by OSF1/Tru64 Make in its VPATH handling.
1794 (tests/subpkg2.test failure)
1796 - Fix another portability issue with Sun and OSF1/Tru64 Make.
1797 In a VPATH-build configuration, `make install' would install
1798 nobase_ files to wrong locations.
1800 - Fix a Perl `uninitialized value' diagnostic occurring when
1801 automake complains that a Texinfo file does not have a
1802 @setfilename statement.
1804 - Erase config.status.lineno during `make distclean'. This file
1805 can be created by config.status. Automake already knew about
1806 configure.lineno, but forgot config.status.lineno.
1808 - Distribute all files, even those which are built and installed
1809 conditionally. This change affects files listed in conditionally
1810 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
1811 as well as those listed in conditionally defined dist_*_DATA,
1812 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
1814 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
1815 doesn't conform to POSIX.
1817 - Normalize help strings for configure variables and options added
1822 - Check for python2.4 in AM_PATH_PYTHON.
1824 * Spurious failures in test suite:
1826 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
1827 tests/ltconv.test: fix failures with CVS Libtool.
1828 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
1829 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
1830 fix failures with old Texinfo versions.
1832 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1838 - The NEWS file is more verbose.
1842 - Autoconf 2.58 or greater is required.
1846 - Default source file names in the absence of a _SOURCES declaration
1847 are made by removing any target extension before appending `.c', so
1848 to make the libtool module `foo.la' from `foo.c', you only need to
1851 lib_LTLIBRARIES = foo.la
1852 foo_la_LDFLAGS = -module
1854 For backward compatibility, foo_la.c will be used instead of
1855 foo.c if this file exists or is the explicit target of a rule.
1856 However -Wobsolete will warn about this deprecated naming.
1858 - AR's `cru' flags are now set in a global ARFLAGS variable instead
1859 of being hard-coded in each $(AR) invocation, so they can be
1860 substituted from configure.ac. This has been requested by people
1861 dealing with non-POSIX ar implementations.
1863 - New warning option: -Woverride. This will warn about any user
1864 target or variable definitions which override Automake
1867 - Texinfo rules back up and restore info files when makeinfo fails.
1869 - Texinfo rules now support the `html' target.
1870 Running this requires Texinfo 4.0 or greater.
1872 `html' is a new recursive target, so if your package mixes
1873 hand-crafted `Makefile.in's with Automake-generated
1874 `Makefile.in's, you should adjust the former to support (or
1875 ignore) this target so that `make html' recurses successfully. If
1876 you had a custom `html' rule in your `Makefile.am', it's better to
1877 rename it as `html-local', otherwise your rule will override
1878 Automake's new rule (you can check that by running `automake
1879 -Woverride') and that will stop the recursion to subdirectories.
1881 Last but not least, this `html' rule is declared PHONY, even when
1882 overridden. Fortunately, it appears that few packages use a
1883 non-PHONY `html' rule.
1885 - Any file which is m4_included from configure.ac will appear as a
1886 configure and Makefile.in dependency, and will be automatically
1889 - The rules for rebuilding Makefiles and Makefile.ins will now
1890 rebuild all Makefiles and all Makefile.ins at once when one of
1891 configure's dependencies has changed. This is considerably faster
1892 than previous implementations, where config.status and automake
1893 were run separately in each directory (this still happens when you
1894 change a Makefile.am locally, without touching configure.ac or
1895 friends). Doing this also solves a longstanding issue: these
1896 rebuild rules failed to work when adding new directories to the
1897 tree, forcing you to run automake manually.
1899 - For similar reasons, the rules to rebuild configure,
1900 config.status, and aclocal.m4 are now defined in all directories.
1901 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
1902 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
1903 should better define them in all directories. This is easily done
1904 using an AC_SUBST (make sure you prefix these dependencies with
1905 $(top_srcdir) since this variable will appear at different
1906 levels of the build tree).
1908 - aclocal will now use `m4_include' instead of copying local m4
1909 files into aclocal.m4. (Local m4 files are those you ship with
1910 your project, other files will be copied as usual.)
1912 Because m4_included files are automatically distributed, it means
1913 for most projects there is no point in EXTRA_DISTing the list of
1914 m4 files which are used. (You can probably get rid of
1915 m4/Makefile.am if you had one.)
1917 - aclocal will avoid touching aclocal.m4 when possible, so that
1918 Autom4te's cache isn't needlessly invalidated. This behavior can
1919 be switched off with the new `--force' option.
1921 - aclocal now uses Autoconf's --trace to detect macros which are
1922 actually used and will no longer include unused macros simply
1923 because they where mentioned. This was often the case for macros
1924 called conditionally.
1926 - New options no-dist and no-dist-gzip.
1928 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
1929 py-compile, and ylwrap, now all understand --version and --help.
1931 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
1932 links as part of the distclean target and including source files in
1935 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
1936 argument. The latter can be used to override the default behavior
1937 (which is to abort).
1939 - Automake will exit with $? = 63 on version mismatch. (So does
1940 Autoconf 2.58) missing knows this, and in this case it will
1941 emulate the tools as if they were absent. Because older versions
1942 of Automake and Autoconf did not use this exit code, this change
1943 will only be useful in projects generated with future versions of
1946 - When using AC_CONFIG_FILES with multiple input files, Automake
1947 generates the first ".in" input file for which a ".am" exists.
1948 (Former versions would try to use only the first input file.)
1950 - lisp_DATA is now allowed. If you are using the empty ELCFILES
1951 idiom to disable byte-compilation of lisp_LISP files, it is
1952 recommended that you switch to using lisp_DATA. Note that
1953 this is not strictly equivalent: lisp_DATA will install elisp
1954 files even if emacs is not installed, while *_LISP do not
1955 install anything unless emacs is found.
1957 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
1958 available. This selection is achieved through the Makefile
1959 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
1960 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
1961 `$(install_sh) -m 0755 -d'.
1965 - Because `mkdir -p' is available on most platforms, and we can use
1966 `install-sh -d' when it is not, the use of the mkinstalldirs
1967 script is being phased out. `automake --add-missing' no longer
1968 installs it, and if you remove mkinstalldirs from your package,
1969 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
1971 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
1972 gettextize and autopoint will install it when needed. Automake
1973 will continue to define the $(mkinstalldirs) and to distribute
1974 mkinstalldirs when this script is in the source tree.
1976 - AM_PROG_CC_STDC is now empty. The content of this macro was
1977 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
1978 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
1979 renaming should be safe, even if you have to support several,
1980 versions of Automake, because AC_PROG_CC defines this variable
1981 since Autoconf 2.54.)
1983 - Some users where using the undocumented ACLOCAL_M4_SOURCES
1984 variable to override the aclocal.m4 dependencies computed
1985 (inaccurately) by older versions of Automake. Because Automake
1986 now tracks configure's m4 dependencies accurately (see m4_include
1987 above), the use of ACLOCAL_M4_SOURCES should be considered
1988 obsolete and will be flagged as such when running `automake
1993 - Defining programs conditionally using Automake conditionals no
1994 longer leads to a combinatorial explosion. The following
1995 construct used to be troublesome when used with dozens of
2010 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2012 - Due to implementation constraints, previous versions of Automake
2013 proscribed multiple conditional definitions of some variables
2023 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2024 This restriction has been lifted, and these variables now
2025 support multiple conditional definitions as do other variables.
2027 - Cleanup the definitions of $(distdir) and $(top_distdir).
2028 $(top_distdir) now points to the root of the distribution
2029 directory created during `make dist', as it did in Automake 1.4,
2030 not to the root of the build tree as it did in intervening
2031 versions. Furthermore these two variables are now only defined in
2032 the top level Makefile, and passed to sub-directories when running
2035 - The --no-force option now correctly checks the Makefile.in's
2036 dependencies before deciding not to update it.
2038 - Do not assume that make files are called Makefile in cleaning rules.
2040 - Update .info files in the source tree, not in the build tree. This
2041 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2042 used to update these files in the build tree (previous versions did
2043 it in the source tree too), and it caused several problems, varying
2044 from mere annoyance to portability issues.
2046 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2047 when --add-missing and --force-missing are used. For backward
2048 compatibility --add-missing will continue to install COPYING (in
2049 `gnu' strictness) when none of these three files exist, but this
2050 use is deprecated: you should better choose a license yourself and
2051 install it once for all in your source tree (and in your code
2054 - Fix ylwrap so that it does not overwrite header files that haven't
2055 changed, as the inline rule already does.
2057 - User-defined rules override automake-defined rules for the same
2058 targets, even when rules do not have commands. This is not new
2059 (and was documented), however some of the automake-generated
2060 rules have escaped this principle in former Automake versions.
2061 Rules for the following targets are affected by this fix:
2063 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2064 info, info-am, install-data-am, install-exec-am, install-info,
2065 install-info-am, install-man, installcheck-am, maintainer-clean,
2066 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2067 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2069 Practically it means that an attempt to supplement the dependencies
2070 of some target, as in
2072 clean: my-clean-rule
2074 will now *silently override* the automake definition of the
2075 rule for this target. Running `automake -Woverride' will diagnose
2076 all such overriding definitions.
2078 It should be noted that almost all of these targets support a *-local
2079 variant that is meant to supplement the automake-defined rule
2080 (See node `Extending' in the manual). The above rule should
2083 clean-local: my-clean-rule
2085 These *-local targets have been documented since at least
2086 Automake 1.2, so you should not fear the change if you have
2087 to support multiple automake versions.
2091 - The Automake manual is now distributed under the terms of the GNU FDL.
2093 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2095 - core dumps are no longer removed by the cleaning rules. There are
2096 at least three reasons for this:
2097 1. These files should not be created by any build step,
2098 so their removal do not fit any of the cleaning rules.
2099 Actually, they may be precious to the developer.
2100 2. If such file is created during a build, then it's clearly a
2101 bug Automake should not hide. Not removing the file will
2102 cause `make distcheck' to complain about its presence.
2103 3. Operating systems have different naming conventions for
2104 core dump files. A core file on one system might be a
2105 completely legitimate data file on another system.
2107 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2108 defined by Automake. This means that any definition in the
2109 environment will be used, unless overridden in the Makefile.am or
2110 on the command line. The old behavior, where these variables were
2111 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2112 AC_ARG_VARing each variable from configure.ac.
2114 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2115 documented. (The is not a new feature, these variables have
2116 been there since at least Automake 1.4.)
2118 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2120 Bugs fixed in 1.7.9:
2121 * Fix install-strip to work with nobase_ binaries.
2122 * Fix renaming of #line directives in ylwrap.
2123 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2125 Bugs fixed in 1.7.8:
2126 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2127 * Fix detection of Debian's install-info, broken since version 1.5.
2128 (Debian bug #213524).
2129 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2130 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2132 Bugs fixed in 1.7.7:
2133 * The implementation of automake's --no-force option is unreliable,
2134 so this option is ignored in this version. A real fix will appear in
2135 Automake 1.8. (Debian Bug #206299)
2136 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2137 argument is given. (PR/399)
2138 * Do not warn about leading `_' in variable names, even with -Wportability.
2139 * Support user redefinitions of TEXINFO_TEX.
2140 * depcomp: support AIX Compiler version 6.
2141 * Fix missing rebuilds during `make dist' with BSD make.
2142 (Could produce tarballs containing out-of-date files.)
2143 * Resurrect multilib support.
2144 * Noteworthy manual updates:
2145 - Extending aclocal: how to write m4 macros that won't trigger warnings
2147 - A Shared Library: Rewrite and split into subsections.
2149 Bugs fixed in 1.7.6:
2150 * Fix depcomp's icc mode for ICC 7.1.
2151 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2152 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2153 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2154 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2155 * Remove Latin-1 characters from elisp-comp.
2156 * Update the manual's @dircategory to match the Free Software Directory.
2158 Bugs fixed in 1.7.5:
2159 * Update install-sh's license to remove an advertising clause.
2160 (Debian bug #191717)
2161 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2162 that caused invalid Makefile.ins to be generated.
2163 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2164 * New FAQ entry: renamed objects.
2166 Bugs fixed in 1.7.4:
2167 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2168 the Emacs implementation)
2169 * Fix output of aclocal.m4 dependencies in subdirectories.
2170 * Use `mv -f' instead of `mv' in fastdep rules.
2171 * Upgrade mdate-sh to work on OS/2.
2172 * Don't byte-compile elisp files when ELCFILES is set empty.
2173 (this documented feature was broken by 1.7.3)
2174 * Diagnose trailing backslashes on last line of Makefile.am.
2175 * Diagnose whitespace following trailing backslashes.
2176 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2177 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2179 * `make install' will build `BUILT_SOURCES' first.
2180 * Minor documentation fixes.
2182 Bugs fixed in 1.7.3:
2183 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2184 * Query distutils for `pythondir' and `pythonexecdir', instead of
2185 using an hardcoded path. This should allow builds on 64-bit
2186 distributions that usually use lib64/ instead of lib/.
2187 * AM_PATH_PYTHON will also search for python2.3.
2188 * elisp files are now built all at once instead of one by one. Besides
2189 incurring a speed-up, this is required to support interdependent elisp files.
2190 * Support for DJGPP:
2191 - `make distcheck' will now work in `_inst/' and `_build' instead
2192 of `=inst/' and `=build/'
2193 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2194 - install/uninstall `*.i[0-9][0-9]'-style info files
2195 - more changes that affect only the Automake package (not its output)
2196 * Fix some incompatibilities with upcoming perl-5.10.
2197 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2198 PACKAGE and VERSION.
2200 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2201 is troublesome with gcc and Solaris compilers. (PR/385)
2202 - makedepend mode: work with Libtool. (PR/385 too)
2204 * better support for unusual gettext setups, such as multiple po/ directories
2206 - Flag missing po/ and intl/ directories as warnings, not errors.
2207 - Disable these warnings if po/ does not exist.
2208 * Noteworthy manual updates:
2210 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2212 - Document `AM_YFLAGS = -d'. (PR/382)
2214 Bugs fixed in 1.7.2:
2215 * Fix installation and uninstallation of Info files built in subdirectories.
2216 * Do not run `./configure --with-included-gettext' during `make distcheck'
2217 if AM_GNU_GETTEXT([external]) is used.
2218 * Correctly uninstall renamed man pages.
2219 * Do not strip escaped newline in variables defined in one condition
2220 and augmented in another condition.
2221 * Fix ansi2knr rules for LIBOBJS sources.
2222 * Clean all known Texinfo index files, not only those which appear to
2223 be used, because we cannot know which indexes are used in included files.
2224 (PR/375, Debian Bug #168671)
2225 * Honor only the first @setfilename seen in a Texinfo file.
2226 * Treat "required file X not found" diagnostics as errors (exit status 1).
2227 * Don't complain that a required file is not found when it is a Makefile
2229 * Don't use single suffix inference rules when building `.info'-less
2230 Info files, for the sake of Solaris make.
2231 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2232 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2233 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2234 * Fix building of deansified files from subdirectories. (PR/370)
2235 * Add missing `fi' in the .c->.obj rules.
2236 * Improve install-sh to work even when names contain spaces or certain
2237 (but not all) shell metachars.
2238 * Fix the following spurious failures in the test suite:
2239 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2240 * Noteworthy manual updates:
2241 - Augment the section about BUILT_SOURCES.
2242 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2244 Bugs fixed in 1.7.1:
2245 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2247 * Aclocal should now recognize macro names containing parentheses, e.g.
2248 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2249 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2251 * Install Python files even if they were built. (PR/369)
2252 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2253 version might not be defined in the latter. (PR/358)
2254 * Reorder arguments passed to a couple of commands, so things works
2255 when POSIXLY_CORRECT=1.
2256 * Fix a regex that can cause Perl to segfault on large input.
2258 * Fix distribution of packages that have some sources defined conditionally,
2259 as in the `Conditional compilation using Automake conditionals' example
2261 * Fix spurious test suite failures on IRIX.
2262 * Don't report a required variable as undefined if it has been
2263 defined conditionally for the "right" conditions.
2264 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2265 `make distcheck' fails.
2266 * Fix distribution of included Makefile fragment, so we don't create
2267 spurious directories in the distribution. (PR/366)
2268 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2271 * Autoconf 2.54 is required.
2272 * `aclocal' and `automake' will no longer warn about obsolete
2273 configure macros. This is done by `autoconf -Wobsolete'.
2274 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2275 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2276 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2277 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2278 `configure.ac' for you.
2279 * Support for per-program and per-library `_CPPFLAGS'.
2280 * New `ctags' target (builds CTAGS files).
2281 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2282 (see `automake --help' or the manual for a list of them).
2283 * Honor the WARNINGS environment variable.
2284 * Omit the call to depcomp when using gcc3: call the compiler directly.
2285 * A new option, std-options, tests that programs support --help and --version
2286 when `make installcheck' is run. This is enabled by --gnits.
2287 * Texinfo rules now support the `ps' and `pdf' targets.
2288 * Info files are now created in the build directory, not the source directory.
2289 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2291 * `make distcheck' will enforce DESTDIR support by attempting
2293 * `+=' can be used in conditionals, even if the augmented variable
2294 was defined for another condition.
2295 * Makefile fragments (inserted with `include') are always distributed.
2296 * Use Autoconf's --trace interface to inspect configure.ac and get
2297 a more accurate view of it.
2298 * Add support for extending aclocal's default macro search path
2299 using a `dirlist' file within the aclocal directory.
2300 * automake --output-dir is deprecated.
2301 * The part of the distcheck target that checks whether uninstall actually
2302 removes all installed files has been moved in a separate target,
2303 distuninstallcheck, so it can be overridden easily.
2307 * Support for AM_INIT_GETTEXT([external])
2308 * Bug fixes, including:
2309 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2310 - nobase_ programs and scripts honor --program-transform correctly.
2311 - Erase configure.lineno during `make distclean'.
2312 - Erase YACC and LEX outputs during `make maintainer-clean'.
2315 * Many bug fixes, including:
2316 - Requiring the current version works.
2317 - Fix "$@" portability issues (for Zsh).
2318 - Fix output of dummy dependency files in presence of post-processed
2320 - Don't compute dependencies in background to avoid races with libtool.
2321 - Fix handling of _OBJECTS variables for targets sharing source variables.
2322 - Check dependency mode for Java when AM_PROG_GCJ is used.
2325 * automake --output-dir is deprecated
2326 * Many bug fixes, including:
2327 - Don't choke on AM_LDFLAGS definitions.
2328 - Clean libtool objects from subdirectories.
2329 - Allow configure variables with reserved suffix and unknown prefix
2330 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2331 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2334 * Autoconf 2.52 is required.
2335 * automake no longer run libtoolize.
2336 This is the job of autoreconf (from GNU Autoconf).
2337 * `dist' generates all the archive flavors, as did `dist-all'.
2338 * `dist-gzip' generates the Gzip tar file only.
2339 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2340 explosion. Makefile.in's keep a reasonable size.
2341 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2342 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2344 * `#line' of Lex and Yacc files are properly set.
2345 * EXTRA_DIST can contain generated directories.
2346 * Support for dot-less extensions in suffix rules.
2347 * The part of the distcheck target that checks whether distclean actually
2348 cleans all built files has been moved in a separate target, distcleancheck,
2349 so it can be overridden easily.
2350 * `make distcheck' will pass additional options defined in
2351 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2352 * Fixed CDPATH portability problems, in particular for MacOS X.
2353 * Fixed handling of nobase_ targets.
2354 * Fixed support of implicit rules leading to .lo objects.
2355 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2356 * Added uninstall-hook target
2357 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2358 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2359 (Note that "pkgname" is not "tarname", see the manual for details.)
2360 It is also possible to pass a list of global Automake options as
2361 first argument to this new form of AM_INIT_AUTOMAKE.
2362 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2363 to be a real assembler.
2364 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2365 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2366 * aclocal and automake are also installed with the version number
2367 appended, and some of the install directory names have changed.
2368 This lets you have multiple versions installed simultaneously.
2369 * Support for parsers and lexers in subdirectories.
2372 * Support for `configure.ac'.
2373 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2374 * `make dist-all' is much faster.
2375 * Allows '@' AC_SUBSTs in macro names.
2376 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2377 * User-side dependency tracking. Developers no longer need GNU make
2379 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2380 * Most files are correctly handled if they appear in subdirs
2381 For instance, a _DATA file can appear in a subdir
2382 * GNU tar is no longer required for `make dist'
2383 * Added support for `dist_' and `nodist_' prefixes
2384 * Added support for `nobase_' prefix
2385 * Compiled Java support
2386 * Support for per-executable and per-library compilation flags
2390 * Added support for the Fortran 77 programming language.
2391 * Re-indexed the Automake Texinfo manual.
2392 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2393 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2394 * Support for latest autoconf, including support for objext
2395 * Can now put `.' in SUBDIRS to control build order
2396 * `include' command and `+=' support for macro assignment
2397 * Dependency tracking no long susceptible to deleted header file problem
2398 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2403 * Better Cygwin32 support
2404 * Support for suffix rules with _SOURCES variables
2405 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2406 * @LEXLIB@ no longer required when lex source seen
2407 Lex support in `missing', and new lex macro. Update your missing script.
2408 * Built-in support for assembly
2409 * aclocal gives error if `AM_' macro not found
2410 * Passed YFLAGS, not YACCFLAGS, to yacc
2411 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2412 * Dependencies computed as a side effect of compilation
2413 * Preliminary support for Java
2414 * DESTDIR support at "make install" time
2415 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2419 * Better DejaGnu support
2420 * Added no-installinfo option
2421 * Added Emacs Lisp support
2422 * Added --no-force option
2423 * Included `aclocal' program
2424 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2425 * Now uses `AM_' macro names everywhere
2426 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2427 ansi2knr now works correctly on K&R sources
2428 * Better C++, yacc, lex support
2429 * Will compute _DEPENDENCIES variables automatically if not supplied
2430 * Will interpolate $(...) and ${...} when examining contents of a variable
2431 * .deps files now in build directory, not source directory; dependency
2432 handling generally rewritten
2433 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2434 * can now put config.h into a subdir
2435 * Added dist-all target
2436 * Support for install-info program (see texinfo 3.9)
2437 * Support for "yacc -d"
2438 * configure substitutions are automatically discovered and included
2439 in generated Makefile.in
2440 * Special --cygnus mode
2441 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2442 when making distribution. Some dependencies are auto-ignored.
2443 * Changed how libraries are specified in _LIBRARIES variable
2444 * Full libtool support, from Gord Matzigkeit
2445 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2446 AM_CONFIG_HEADER handles it automatically
2447 * Texinfo output files no longer need .info extension
2448 * Added `missing' support
2450 * Conditionals in Makefile.am, from Ian Taylor
2454 * distcheck target runs install and installcheck targets
2455 * Added preliminary support for DejaGnu.
2460 * More libtool fixes from Gord Matzigkeit; libtool support is still
2462 * Added support for jm_MAINTAINER_MODE
2464 * New "distcheck" target
2468 * mkinstalldirs and mdate-sh now appear in directory specified by
2470 * Removed DIST_SUBDIRS, DIST_OTHER
2471 * AC_ARG_PROGRAM only required when an actual program exists
2472 * dist-hook target now run before distribution packaged up; idea from
2473 Dieter Baron. Other hooks exist, too.
2474 * Preliminary (unfinished) support for libtool
2475 * Added short option names.
2476 * Better "dist" support when gluing together multiple packages
2480 * Documentation updates (many from François Pinard)
2481 * strictness `normal' now renamed to `foreign'
2482 * Renamed --install-missing to --add-missing
2483 * Now handles AC_CONFIG_AUX_DIR
2484 * Now handles TESTS macro
2485 * DIST_OTHER renamed to EXTRA_DIST
2486 * DIST_SUBDIRS is deprecated
2487 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2488 * Better error messages in many cases
2489 * Program names are canonicalized
2490 * Added "check" prefix; from Gord Matzigkeit
2494 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2495 * Beginnings of a test suite
2496 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2497 * Doesn't print anything when running
2498 * Beginnings of MAINT_CHARSET support
2499 * Can specify version in AUTOMAKE_OPTIONS
2500 * Most errors recognizable by Emacs' M-x next-error
2501 * Added --verbose option
2502 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2503 configure-generated names
2504 * Required macros now distributed in aclocal.m4
2506 * --strictness=gnu is default
2510 * More sophisticated configure.in scanning; now understands ALLOCA and
2511 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2512 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2513 * CONFIG_HEADER variable now obsolete
2514 * Can handle multiple Texinfo sources
2515 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2516 * HEADERS variable no longer needed; now can put .h files directly into
2517 foo_SOURCES variable.
2518 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2519 corresponding ".in" files are included in the distribution.
2522 * Added --gnu and --gnits options
2523 * More standards checking
2525 * Cleaned up 'dist' targets
2526 * Added AUTOMAKE_OPTIONS variable and several options
2527 * Now scans configure.in to get some information (preliminary)
2530 * Works with Perl 4 again
2533 * Added --install-missing option.
2534 * Pretty-prints generated macros and rules
2535 * Comments in Makefile.am are placed more intelligently in Makefile.in
2536 * Generates .PHONY target
2537 * Rule or macro in Makefile.am now overrides contents of Automake file
2538 * Substantial cleanups from François Pinard
2542 * Works with Perl 4 again.
2545 * New uniform naming scheme.
2546 * --strictness option
2548 * '.c' files corresponding to '.y' or '.l' files are automatically
2550 * Many bug fixes and cleanups
2553 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2556 * Bug fixes in 'clean' code.
2557 * Now generates 'installdirs' target.
2558 * man page installation reworked.
2559 * 'make dist' no longer re-creates all Makefile.in's.
2562 * Reimplemented in Perl
2563 * Added --amdir option (for debugging)
2564 * Texinfo support cleaned up.
2565 * Automatic de-ANSI-fication cleaned up.
2566 * Cleaned up 'clean' targets.
2569 * Automatic dependency tracking
2570 * More documentation
2571 * New variables DATA and PACKAGEDATA
2572 * SCRIPTS installed using $(INSTALL_SCRIPT)
2573 * No longer uses double-colon rules
2575 * Changes in advance of internationalization
2579 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2581 This program is free software; you can redistribute it and/or modify
2582 it under the terms of the GNU General Public License as published by
2583 the Free Software Foundation; either version 2, or (at your option)
2586 This program is distributed in the hope that it will be useful,
2587 but WITHOUT ANY WARRANTY; without even the implied warranty of
2588 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2589 GNU General Public License for more details.
2591 You should have received a copy of the GNU General Public License
2592 along with this program. If not, see <http://www.gnu.org/licenses/>.