3 * WARNING: Future backward-incompatibilities!
5 - Automake 1.14 will likely require Autoconf 2.70 or later (which is
6 still unreleased at the moment of writing, but is planned to be
7 released before Automake 1.14 is).
9 - Automake 1.14 will likely drop support for the long-deprecated
10 'configure.in' name for the Autoconf input file. You are advised
11 to use the recommended name 'configure.ac' instead.
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 is introduced with
23 this release; see below for more information).
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').
54 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
55 causes a clear and helpful error message, instead of obscure ones
56 (issue introduced in Automake 1.13).
58 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
64 - ylwrap renames properly header guards in generated header files
65 (*.h), instead of leaving Y_TAB_H.
67 - ylwrap now also converts header guards in implementation files
68 (*.c). Because ylwrap failed to rename properly #include in the
69 implementation files, current versions of Bison (e.g., 2.7)
70 duplicate the generated header file in the implementation file.
71 The header guard then protects the implementation file from
72 duplicate definitions from the header file.
74 * Version requirements:
76 - Autoconf 2.65 or greater is now required.
78 - The rules to build PDF and DVI output from Texinfo input now
79 require Texinfo 4.9 or later.
83 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
84 option) has been removed. See discussion about automake bug#11034
85 for more background: <http://debbugs.gnu.org/11034>.
87 - The deprecated aclocal option '--acdir' has been removed. You
88 should use the options '--automake-acdir' and '--system-acdir'
89 instead (which have been introduced in Automake 1.11.2).
91 - The following long-obsolete m4 macros have been removed:
93 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
94 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
95 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
96 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
97 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
98 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
99 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
100 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
101 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
102 of the now-removed automatic de-ANSI-fication
105 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
107 - Use of the long-deprecated two- and three-arguments invocation forms
108 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
109 though (albeit with a warning in the 'obsolete' category), to cater
110 for people who want to define the version number for their package
111 dynamically (e.g., from the current VCS revision). We'll have to
112 continue this support until Autoconf itself is fixed to allow better
113 support for such dynamic version numbers.
115 * Elisp byte-compilation:
117 - The byte compilation of '.el' files into '.elc' files is now done
118 with a suffix rule. This has simplified the compilation process, and
119 more importantly made it less brittle. The downside is that emacs is
120 now invoked once for each '.el' files, which cause some noticeable
121 slowdowns. These should however be mitigated on multicore machines
122 (which are becoming the norm today) if concurrent make ("make -j")
125 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
126 files in the same subdirectory; for example, byte-compiling of file
127 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
128 'foo.elc'. This behaviour is backward-incompatible with older
129 Automake versions, but it is more natural and more sane. See also
132 - The Emacs invocation performing byte-compilation of '.el' files honors
133 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
134 one is developer-reserved and the latter one user-reserved.
136 - The 'elisp-comp' script, once provided by Automake, has been rendered
137 obsoleted by the just-described changes, and thus removed.
139 * Changes to Automake-generated testsuite harnesses:
141 - The parallel testsuite harness (previously only enabled by the
142 'parallel-tests' option) is the default one; the older serial
143 testsuite harness will still be available through the use of the
144 'serial-tests' option (introduced in Automake 1.12).
146 - The 'color-tests' option is now unconditionally activated by default.
147 In particular, this means that testsuite output is now colorized by
148 default if the attached terminal seems to support ANSI escapes, and
149 that the user can force output colorization by setting the variable
150 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
151 for backward-compatibility, although it's a handled as a no-op now.
153 * Silent rules support:
155 - Support for silent rules is now always active in Automake-generated
156 Makefiles. So, although the verbose output is still the default,
157 the user can now always use "./configure --enable-silent-rules" or
158 "make V=0" to enable quieter output in the package he's building.
160 - The 'silent-rules' option has now become a no-op, preserved for
161 backward-compatibility only. In particular, its use no longer
162 disables the warnings in the 'portability-recursive' category.
166 - The rules to build PDF and DVI files from Texinfo input now require
167 Texinfo 4.9 or later.
169 - The rules to build PDF and DVI files from Texinfo input now use the
170 '--build-dir' option, to keep the auxiliary files used by texi2dvi
171 and texi2pdf around without cluttering the build directory, and to
172 make it possible to run the "dvi" and "pdf" recipes in parallel.
174 * Automatic remake rules and 'missing' script:
176 - The 'missing' script no longer tries to update the timestamp of
177 out-of-date files that require a maintainer-specific tool to be
178 remade, in case the user lacks such a tool (or has a too-old version
179 of it). It just gives a useful warning, and in some cases also a
180 tip about how to obtain such a tool.
182 - The missing script has thus become useless as a (poor) way to work
183 around the sketched-timestamps issues that can happen for projects
184 that keep generated files committed in their VCS repository. Such
185 projects are now encouraged to write a custom "fix-timestamps.sh"
186 script to avoid such issues; a simple example is provided in the
187 "CVS and generated files" chapter of the automake manual.
191 - The user can now define his own recursive targets that recurse
192 in the directories specified in $(SUBDIRS). This can be done by
193 specifying the name of such targets in invocations of the new
194 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
198 - Any failure in the recipe of the "tags", "ctags", "cscope" or
199 "cscopelist" targets in a subdirectory is now propagated to the
200 top-level make invocation.
202 - Tags are correctly computed also for files in _SOURCES variables that
203 only list files with non-standard suffixes (see automake bug#12372).
205 * Improvements to aclocal and related rebuilds rules:
207 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
208 are now traced by aclocal, and can be used to declare the local m4
209 include directories. Formerly, one had to specify it with an explicit
210 '-I' option to the 'aclocal' invocation.
212 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
213 Automake versions will warn about its use, and later version will
214 remove support for it altogether.
216 * The depcomp script:
218 - Dropped support for libtool 1.4.
220 - Various internal refactorings. They should cause no visible change,
221 but the chance for regression is there anyway, so please report any
222 unexpected or suspicious behaviour.
224 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
225 This should cause no problem, since icc 8.0 has been released in
226 December 2003 -- almost nine years ago.
228 - Support for tcc (the Tiny C Compiler) has been improved, and is now
229 handled through a dedicated 'tcc' mode.
233 - ylwrap generates header guards with a single '_' for series of non
234 alphabetic characters, instead of several. This is what Bison >=
237 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
239 Bugs fixed in 1.12.6:
241 * Python-related bugs:
243 - The default installation location for python modules has been improved
244 for Python 3 on Debian and Ubuntu systems, changing from:
246 ${prefix}/lib/python3/dist-packages
250 ${prefix}/lib/python3.x/site-packages
252 This change should ensure modules installed using the default ${prefix}
253 "/usr/local" are found by default by system python 3.x installations.
254 See automake bug#10227.
256 - Python byte-compilation supports the new layout mandated by PEP-3147,
257 with its __pycache__ directory (automake bug#8847).
259 * Build system issues:
261 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
262 Automake's own build system works correctly again (bug introduced
267 - The Vala-related tests has been changed to adjust to the removal of
268 the 'posix' profile in the valac compiler. See automake bug#12934
271 - Some spurious testsuite failures related to older tools and systems
274 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
280 - The AM_PROG_VALAC macro has been enhanced to takes two further
281 optional arguments; it's signature now being
283 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
284 [ACTION-IF-NOT-FOUND])
286 - By default, AM_PROG_VALAC no longer aborts the configure invocation
287 if the Vala compiler found is too old, but simply prints a warning
288 messages (as it did when the Vala compiler was not found). This
289 should avoid unnecessary difficulties for end users that just want
290 to compile the unmodified, distributed Vala-generated C sources,
291 but happens to have an old Vala compiler in their PATH. This fixes
294 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
295 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
296 This is a better default, because with it a triggered makefile rule
297 invoking a Vala compilation will clearly fail with an informative error
298 message like "valac: command not found", rather than silently, with
299 the error possibly going unnoticed or triggering harder-to-diagnose
300 fallout failures in later steps.
302 * Miscellaneous changes:
304 - automake and aclocal no longer honours the 'perllibdir' environment
305 variable. That had always been intended only as an hack required in
306 the testsuite, not meant for any use beyond that.
308 Bugs fixed in 1.12.5:
310 * Long-standing bugs:
312 - Automake no longer generates spurious remake rules invoking autoheader
313 to regenerate the template corresponding to header files specified after
314 the first one in AC_CONFIG_HEADERS (automake bug#12495).
316 - When wrapping Microsoft tools, the 'compile' script falls back to
317 finding classic 'libname.a' style libraries when 'name.lib' and
318 'name.dll.lib' aren't available.
320 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
324 * Warnings and deprecations:
326 - Warnings in the 'obsolete' category are enabled by default both in
327 automake and aclocal.
329 * Miscellaneous changes:
331 - Some testsuite weaknesses and spurious failures have been fixed.
333 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
337 * Miscellaneous changes:
339 - The '.m4' files provided by Automake no longer define serial numbers.
340 This should cause no difference in the behaviour of aclocal though.
342 - Some testsuite weaknesses and spurious failures have been fixed.
344 - There is initial support for automatic dependency tracking with the
345 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
347 Bugs fixed in 1.12.3:
349 * Long-standing bugs:
351 - Instead of renaming only self-references of files (typically for
352 #lines), ylwrap now also renames references to the other generated
353 files. This fixes support for GLR and C++ parsers from Bison (PR
354 automake/491 and automake bug#7648): 'parser.c' now properly
355 #includes 'parser.h' instead of 'y.tab.h'.
357 - Generated files unknown to ylwrap are now preserved. This fixes
358 C++ support for Bison (automake bug#7648): location.hh and the
359 like are no longer discarded.
361 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
365 * Warnings and deprecations:
367 - Automake now issues a warning (in the 'portability' category) if
368 'configure.in' is used instead of 'configure.ac' as the Autoconf
369 input file. Such a warning will also be present in the next
370 Autoconf version (2.70).
374 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
375 order (as done by the other recursive rules), rather than in the
376 inverse order. They used to do that in order to work a round a
377 limitation in an older implementation of the automatic dependency
378 tracking support, but that limitation had been lifted years ago
379 already, when the automatic dependency tracking based on side-effects
380 of compilation had been introduced.
382 - Cleaning rules for compiled objects (both "plain" and libtool) work
383 better when subdir objects are involved, not triggering a distinct
384 'rm' invocation for each such object. They do so by removing *any*
385 compiled object file that is in the same directory of a subdir
386 object. See automake bug#10697.
388 * Silent rules support:
390 - A new predefined $(AM_V_P) make variable is provided; it expands
391 to a shell conditional that can be used in recipes to know whether
392 make is being run in silent or verbose mode.
394 Bugs fixed in 1.12.2:
396 * SECURITY VULNERABILITIES!
398 - The 'distcheck' recipe no longer grants temporary world-write
399 permissions on the extracted distdir. Even if such rights were
400 only granted for a vanishingly small time window, the implied
401 race condition proved to be enough to allow a local attacker
402 to run arbitrary code with the privileges of the user running
403 "make distcheck". This is CVE-2012-3386.
405 * Long-standing bugs:
407 - The "recheck" targets behaves better in the face of build failures
408 related to previously failed tests. For example, if a test is a
409 compiled program that must be rerun by "make recheck", and its
410 compilation fails, it will still be rerun by further "make recheck"
411 invocations. See automake bug#11791.
413 * Bugs introduced by 1.12.1:
415 - Automake provides once again the '$(mkdir_p)' make variable and the
416 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
417 for better backward-compatibility.
419 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
423 * New supported languages:
425 - Support for Objective C++ has been added; it should work similarly to
426 the support for Objective C.
428 * Deprecated obsolescent features:
430 - Use of the long-deprecated two- and three-arguments invocation forms
431 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
432 category. Starting from some future major Automake release (likely
433 post-1.13), such usages will no longer be allowed.
435 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
436 now deprecated (its use triggers a warning in the 'obsolete' category).
437 It will be removed in the next major Automake release (1.13).
439 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
440 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
441 m4 macro are deprecated, eliciting a warning in the 'obsolete'
444 * Miscellaneous changes:
446 - The Automake test cases now require a proper POSIX-conforming shell.
447 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
448 be accepted. In most cases, the user shouldn't have to specify such
449 POSIX shell explicitly, since it will be looked up at configure time.
450 Still, when this lookup fails, or when the user wants to override its
451 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
452 to the shell that will be used to run the Automake test cases).
454 Bugs fixed in 1.12.1:
456 * Bugs introduced by 1.12:
458 - Several weaknesses in Automake's own build system and test suite
461 * Bugs introduced by 1.11.3:
463 - When given non-option arguments, aclocal rejects them, instead of
464 silently ignoring them.
466 * Long-standing bugs:
468 - When the 'color-tests' option is in use, forcing of colored testsuite
469 output through "AM_COLOR_TESTS=always" works even if the terminal is
470 a non-ANSI one, i.e., if the TERM environment variable has a value of
473 - Several inefficiencies and poor performances in the implementation
474 of the parallel-tests 'check' and 'recheck' targets have been fixed.
476 - The post-processing of output "#line" directives done the ylwrap
477 script is more faithful w.r.t. files in a subdirectory; for example,
478 if the processed file is "src/grammar.y", ylwrap will correctly
479 produce directives like:
480 #line 7 "src/grammar.y"
485 * Bugs with new Perl versions:
487 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
489 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
493 * Obsolete features removed:
495 - The never documented nor truly used script 'acinstall' has been
498 - Support for automatic de-ANSI-fication has been removed.
500 - The support for the "obscure" multilib feature has been removed
501 from Automake core (but remains available in the 'contrib/'
502 directory of the Automake distribution).
504 - Support for ".log -> .html" conversion and the check-html and
505 recheck-html targets has been removed from Automake core (but
506 remains available in the 'contrib/' directory of the Automake
509 - The deprecated 'lzma' compression format for distribution archives
510 has been removed, in favor of 'xz' and 'lzip'.
512 - The obsolete AM_WITH_REGEX macro has been removed.
514 - The long-deprecated options '--output-dir', '--Werror' and
515 '--Wno-error' have been removed.
517 - The chapter on the history of Automake has been moved out of the
518 reference manual, into a new dedicated Texinfo file.
522 - New 'cscope' target to build a cscope database for the source tree.
524 * Changes to Automake-generated testsuite harnesses:
526 - The new automake option 'serial-tests' has been introduced. It can
527 be used to explicitly instruct automake to use the older serial
528 testsuite harness. This is still the default at the moment, but it
529 might change in future versions.
531 - The 'recheck' target (provided by the parallel testsuite harness) now
532 depends on the 'all' target. This allows for a better user-experience
533 in test-driven development. See automake bug#11252.
535 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
536 and unexpected or internal error, or a failure to set up the test case
537 scenario) have their outcome reported as an 'ERROR' now. Previous
538 versions of automake reported such an outcome as a 'FAIL' (the only
539 difference with normal failures being that hard errors were counted
540 as failures even when the test originating them was listed in
543 - The testsuite summary displayed by the parallel-test harness has a
544 completely new format, that always list the numbers of passed, failed,
545 xfailed, xpassed, skipped and errored tests, even when these numbers
546 are zero (but using smart coloring when the color-tests option is in
549 - The default testsuite driver offered by the 'parallel-tests' option is
550 now implemented (partly at least) with the help of automake-provided
551 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
552 on code in the generated Makefile.in.
553 This has two noteworthy implications. The first one is that projects
554 using the 'parallel-tests' option should now either run automake with
555 the '--add-missing' option, or manually copy the 'test-driver' script
556 into their tree. The second, and more important, implication is that
557 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
558 no longer be used to define a test runner, and the command specified
559 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
560 program or script. For example, this is still a valid usage (albeit
563 TESTS_ENVIRONMENT = \
564 if test -n '$(STRICT_TESTS)'; then \
565 maybe_errexit='-e'; \
569 LOG_COMPILER = $(SHELL) $$maybe_errexit
571 OTOH, this is no longer a valid usage:
573 TESTS_ENVIRONMENT = \
574 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
578 TESTS_ENVIRONMENT = \
579 run_with_perl_or_shell () \
581 if grep -q '^#!.*perl' $$1; then
587 LOG_COMPILER = run_with_perl_or_shell
589 - The package authors can now use customary testsuite drivers within
590 the framework provided by the 'parallel-tests' testsuite harness.
591 Consistently with the existing syntax, this can be done by defining
592 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
594 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
595 to redirect/define file descriptors used by the test scripts.
597 - The parallel-tests harness generates now, in addition the '.log' files
598 holding the output produced by the test scripts, a new set of '.trs'
599 files, holding "metadata" derived by the execution of the test scripts;
600 among such metadata are the outcomes of the test cases run by a script.
602 - Initial and still experimental support for the TAP test protocol is
605 * Changes to Yacc and Lex support:
607 - C source and header files derived from non-distributed Yacc and/or
608 Lex sources are now removed by a simple "make clean" (while they were
609 previously removed only by "make maintainer-clean").
611 - Slightly backward-incompatible change, relevant only for use of Yacc
612 with C++: the extensions of the header files produced by the Yacc
613 rules are now modelled after the extension of the corresponding
614 sources. For example, yacc files named "foo.y++" and "bar.yy" will
615 produce header files named "foo.h++" and "bar.hh" respectively, where
616 they would have previously produced header files named simply "foo.h"
617 and "bar.h". This change offers better compatibility with 'bison -o'.
619 * Miscellaneous changes:
621 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
622 rather than 1, if the vala compiler found is too old.
624 - The build system of Automake itself now avoids the use of make
625 recursion as much as possible.
627 - Automake now prefers to quote 'like this' or "like this", rather
628 than `like this', in diagnostic message and generated Makefiles,
629 to accommodate the new GNU Coding Standards recommendations.
631 - Automake has a new option '--print-libdir' that prints the path of the
632 directory containing the Automake-provided scripts and data files.
634 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
636 - The rules to create pdf, dvi and ps output from Texinfo files now
637 works better with modern 'texi2dvi' script, by explicitly passing
638 it the '--clean' option to ensure stray auxiliary files are not
639 left to clutter the build directory.
641 - Automake can now generate silenced rules for texinfo outputs.
643 - Some auxiliary files that are automatically distributed by Automake
644 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
645 C sources) might now be listed in the DIST_COMMON variable in many
646 Makefile.in files, rather than in the top-level one.
648 - Messages of types warning or error from 'automake' and 'aclocal'
649 are now prefixed with the respective type, and presence of -Werror
652 - Automake's early configure-time sanity check now tries to avoid
653 sleeping for a second, which slowed down cached configure runs
654 noticeably. In that case, it will check back at the end of the
655 configure script to ensure that at least one second has passed, to
656 avoid time stamp issues with makefile rules rerunning autotools
659 - The warnings in the category 'extra-portability' are now enabled by
660 '-Wall'. In previous versions, one has to use '-Wextra-portability'
665 - Various minor bugfixes for recent or long-standing bugs.
667 * Bugs introduced by 1.11:
669 - The AM_COND_IF macro also works if the shell expression for the
670 conditional is no longer valid for the condition.
672 - The automake-provided parallel testsuite harness no longer fails
673 with BSD make used in parallel mode when there are test scripts in
674 a subdirectory, like in:
676 TESTS = sub/foo.test sub/bar.test
678 * Long-standing bugs:
680 - Automake's own build system finally have a real "installcheck" target.
682 - Vala-related cleanup rules are now more complete, and work better in
685 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
686 now automatically distributed also if the directory of the auxiliary
687 files coincides with the top-level directory.
689 - Automake now detects the presence of the '-d' flag in the various
690 '*YFLAGS' variables even when their definitions involve indirections
691 through other variables, such as in:
693 AM_YFLAGS = $(foo_opts)
695 - Automake now complains if a '*YFLAGS' variable has any conditional
696 content, not only a conditional definition.
698 - Explicit enabling and/or disabling of Automake warning categories
699 through the '-W...' options now always takes precedence over the
700 implicit warning level implied by Automake strictness (foreign, gnu
701 or gnits), regardless of the order in which such strictness and
702 warning flags appear. For example, a setting like:
703 AUTOMAKE_OPTIONS = -Wall --foreign
704 will cause the warnings in category 'portability' to be enabled, even
705 if those warnings are by default disabled in 'foreign' strictness.
707 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
709 Bugs fixed in 1.11.5:
711 * Bugs introduced by 1.11.3:
713 - Vala files with '.vapi' extension are now recognized and handled
714 correctly again. See automake bug#11222.
716 - Vala support work again for projects that contain some program
717 built from '.vala' (and possibly '.c') sources and some other
718 program built from '.c' sources *only*. See automake bug#11229.
720 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
724 * Miscellaneous changes:
726 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
727 symbol index) modifiers as well as the "s" action, as the symbol index
728 is created unconditionally by Microsoft lib. Also, the "q" (quick)
729 action is now a synonym for "r" (replace). Also, the script has been
730 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
732 - When the 'compile' script is used to wrap MSVC, it now accepts an
733 optional space between the -I, -L and -l options and their respective
734 arguments, for better POSIX compliance.
736 - There is an initial, experimental support for automatic dependency
737 tracking with tcc (the Tiny C Compiler). Its associated depmode is
738 currently recognized as "icc" (but this and other details are likely
739 to change in future versions).
741 - Automatic dependency tracking now works also with the IBM XL C/C++
742 compilers, thanks to the new new depmode 'xlc'.
744 Bugs fixed in 1.11.4:
746 * Bugs introduced by 1.11.2:
748 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
749 no longer cause spurious failures upon "make install".
751 - The user can now instruct the 'uninstall-info' rule not to update
752 the '${infodir}/dir' file by exporting the environment variable
753 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
754 with how the 'install-info' rule operates since automake 1.11.2.
756 * Long-standing bugs:
758 - It is now possible for a foo_SOURCES variable to hold Vala sources
759 together with C header files, as well as with sources and headers for
760 other supported languages (e.g., C++). Previously, only mixing C and
761 Vala sources was supported.
763 - If "aclocal --install" is used, and the first directory specified with
764 '-I' is non-existent, aclocal will now create it before trying to copy
767 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
768 install rules to create an empty $(foodir) directory; for example, if
769 Makefile.am contains something like:
773 pkglibexec_SCRIPTS += bar.sh
776 the $(pkglibexec) directory will not be created upon "make install".
778 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
782 * Miscellaneous changes:
784 - Automake's own build system is more silent by default, making use of
785 the 'silent-rules' option.
787 - The master copy of the 'gnupload' script is now maintained in gnulib,
790 - The 'missing' script no longer tries to wrap calls to 'tar'.
792 - "make dist" no longer wraps 'tar' invocations with the 'missing'
793 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
794 shouldn't be using BTW ;-) no longer invokes the 'missing' script
795 to wrap tar, but simply invokes the 'tar' program itself.
797 - "make dist" can now create lzip-compressed tarballs.
799 - In the Automake info documentation, the Top node and the nodes about
800 the invocation of the automake and aclocal programs have been renamed;
801 now, calling "info automake" will open the Top node, while calling
802 "info automake-invocation" and "info aclocal-invocation" will access
803 the nodes about the invocation of respectively automake and aclocal.
805 - Automake is now distributed as a gzip-compressed and an xz-compressed
806 tarball. Previously, bzip2 was used instead of xz.
808 - The last relics of Python 1.5 support have been removed from the
809 AM_PATH_PYTHON macro.
811 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
812 and adds them to the normal list of dependencies, but without
813 overwriting the foo_DEPENDENCIES variable, which is normally computed
816 Bugs fixed in 1.11.3:
818 * Bugs introduced by 1.11.2:
820 - Automake now correctly recognizes the prefix/primary combination
821 'pkglibexec_SCRIPTS' as valid.
823 - The parallel-tests harness no longer trips on sed implementations
824 with stricter limits on the length of input lines (problem seen at
827 * Long-standing bugs:
829 - The "deleted header file problem" for *.am files is avoided by stub
830 rules. This allows 'make' to trigger a rerun of 'automake' also if
831 some previously needed '.am' file has been removed.
833 - The 'silent-rules' option now generates working makefiles even
834 for the uncommon 'make' implementations that do not support the
835 nested-variables extension to POSIX 2008. For such 'make'
836 implementations, whether a build is silent is determined at
837 configure time, and cannot be overridden at make time with
838 "make V=0" or "make V=1".
840 - Vala support now works better in VPATH setups.
842 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
846 * Changes to aclocal:
848 - The `--acdir' option is deprecated. Now you should use the new options
849 `--automake-acdir' and `--system-acdir' instead.
851 - The `ACLOCAL_PATH' environment variable is now interpreted as a
852 colon-separated list of additional directories to search after the
853 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
854 and before the system acdir (by default ${prefix}/share/aclocal).
856 * Miscellaneous changes:
858 - The Automake support for automatic de-ANSI-fication has been
859 deprecated. It will probably be removed in the next major Automake
862 - The `lzma' compression scheme and associated automake option `dist-lzma'
863 is obsoleted by `xz' and `dist-xz' due to upstream changes.
865 - You may adjust the compression options used in dist-xz and dist-bzip2.
866 The default is now merely -e for xz, but still -9 for bzip; you may
867 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
868 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
870 - The `compile' script now converts some options for MSVC for a better
871 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
873 - The py-compile script now accepts empty arguments passed to the options
874 `--destdir' and `--basedir', and complains about unrecognized options.
875 Moreover, a non-option argument or a special `--' argument terminates
878 - A developer that needs to pass specific flags to configure at "make
879 distcheck" time can now, and indeed is advised to, do so by defining
880 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
881 instead of the old DISTCHECK_CONFIGURE_FLAGS.
882 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
883 user; still, the old Makefile.am files that used to define it will
884 still continue to work as before.
886 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
887 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
888 This new macro is required for LIBRARIES and LTLIBRARIES when automake
889 is run with -Wextra-portability and -Werror.
891 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
892 file generated by automake-provided rules by defining the special make
893 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
895 - The `install-info' rule can now be instructed not to create/update
896 the `${infodir}/dir' file, by exporting the new environment variable
897 `AM_UPDATE_INFO_DIR' to the value "no".
899 Bugs fixed in 1.11.2:
901 * Bugs introduced by 1.11:
903 - The parallel-tests driver no longer produces erroneous results with
904 Tru64/OSF 5.1 sh upon unreadable log files.
906 - The `parallel-tests' test driver does not report spurious successes
907 when used with concurrent FreeBSD make (e.g., "make check -j3").
909 - When the parallel-tests driver is in use, automake now explicitly
910 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
911 instead of issuing confusing and apparently unrelated error messages
912 (e.g., "non-POSIX variable name", "bad characters in variable name",
913 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
914 silently producing broken `Makefile.in' files.
916 - The `silent-rules' option now truly silences all compile rules, even
917 when dependency tracking is disabled. Also, when `silent-rules' is
918 not used, `make' output no longer contains spurious backslash-only
919 lines, thus once again matching what Automake did before 1.11.
921 - The AM_COND_IF macro also works if the shell expression for the
922 conditional is no longer valid for the condition.
924 * Long-standing bugs:
926 - The order of Yacc and Lex flags is fixed to be consistent with other
927 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
928 $(LFLAGS), so that the user variables override the developer variables.
930 - "make distcheck" now correctly complains also when "make uninstall"
931 leaves one and only one file installed in $(prefix).
933 - A "make uninstall" issued before a "make install", or after a mere
934 "make install-data" or a mere "make install-exec" does not spuriously
937 - Automake now warns about more primary/directory invalid combinations,
938 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
940 - Rules generated by Automake now try harder to not change any files when
941 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
942 Yacc source files and the rule to update config.h.
944 - Several scripts and the parallel-tests testsuite driver now exit with
945 the right exit status upon receiving a signal.
947 - A per-Makefile.am setting of -Werror does not erroneously carry over
948 to the handling of other Makefile.am files.
950 - The code for automatic dependency tracking works around a Solaris
951 make bug triggered by sources containing repeated slashes when the
952 `subdir-objects' option was used.
954 - The makedepend and hp depmodes now work better with VPATH builds.
956 - Java sources specified with check_JAVA are no longer compiled for
957 "make all", but only for "make check".
959 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
960 and error out if `javadir' is undefined, instead of silently producing
961 a broken Makefile.in.
963 - aclocal and automake now honour the configure-time definitions of
964 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
966 - The `install-info' recipe no longer tries to guess whether the
967 `install-info' program is from Debian or from GNU, and adaptively
968 change its behaviour; this has proven to be frail and easy to
971 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
973 Bugs fixed in 1.11.1:
975 - Lots of minor bugfixes.
977 * Bugs introduced by 1.11:
979 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
980 trailing white space in the test list (`TESTS = foo $(EMPTY)').
982 * Long standing bugs:
984 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
985 even if the `--prefix' argument pointed outside of a system directory.
986 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
987 `get_python_lib' function if it points outside the configured prefix,
988 unless the `--prefix' argument was either `/usr' or below `/System'.
990 - The testsuite does not try to change the mode of `ltmain.sh' files from
991 a Libtool installation (symlinked to test directories) any more.
993 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
994 tools are preferred in a cross-compile setup.
996 - The distribution is tarred up with mode 755 now by the `dist*' targets.
997 This fixes a race condition where untrusted users could modify files
998 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
999 build directory was world-searchable. This is CVE-2009-4029.
1001 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1005 * Version requirements:
1007 - Autoconf 2.62 or greater is required.
1009 * Changes to aclocal:
1011 - The autoconf version check implemented by aclocal in aclocal.m4
1012 (and new in Automake 1.10) is degraded to a warning. This helps
1013 in the common case where the Autoconf versions used are compatible.
1015 * Changes to automake:
1017 - The automake program can run multiple threads for creating most
1018 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1019 with interpreter-based threads enabled. Set the environment variable
1020 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1021 enable this experimental feature.
1023 * Changes to Libtool support:
1025 - Libtool generic flags are now passed to the install and uninstall
1028 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1029 config.lt is removed correctly now.
1031 * Languages changes:
1033 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1034 Fortran, and Ratfor).
1036 - For files with extension .f90, .f95, .f03, or .f08, the flag
1037 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1039 - Files with extension .sx are also treated as preprocessed assembler.
1041 - The default source file extension (.c) can be overridden with
1042 AM_DEFAULT_SOURCE_EXT now.
1044 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1047 - AM_PATH_PYTHON honors python's idea about the site directory.
1049 - There is initial support for the Vala programming language, when using
1050 Vala 0.7.0 or later.
1052 * Miscellaneous changes:
1054 - Automake development is done in a git repository on Savannah now, see
1056 http://git.sv.gnu.org/gitweb/?p=automake.git
1058 A read-only CVS mirror is provided at
1060 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1061 checkout -d automake HEAD
1063 - "make dist" can now create xz-compressed tarballs,
1064 as well as (deprecated?) lzma-compressed tarballs.
1066 - `automake --add-missing' will by default install the GPLv3 file as
1067 COPYING if it is missing. It will also warn that the license file
1068 should be added to source control. Note that Automake will never
1069 overwrite an existing COPYING file, even when the `--force-missing'
1072 - The manual is now distributed under the terms of the GNU FDL 1.3.
1074 - Automake ships and installs man pages for automake and aclocal now.
1076 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1078 - install-sh supports -C, which does not update the installed file
1079 (and its time stamps) if the contents did not change.
1081 - The `gnupload' script has been revamped.
1083 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1085 - The targets `install' and `uninstall' are more efficient now, in that
1086 for example multiple files from one Automake variable such as
1087 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1088 invocation if they do not have to be renamed.
1090 Both install and uninstall may sometimes enter (`cd' into) the target
1091 installation directory now, when no build-local scripts are used.
1093 Both install and uninstall do not fail anymore but do nothing if an
1094 installation directory variable like `bindir' is set to the empty string.
1096 For built-in rules, `make install' now fails reliably if installation
1097 of a file failed. Conversely, `make uninstall' even succeeds when
1098 issued multiple times.
1100 These changes may need some adjustments from users: For example,
1101 some `install' programs refuse to install multiple copies of the
1102 same file in one invocation, so you may need to remove duplicate
1103 entries from file lists.
1105 Also, within one set of files, say, nobase_data_DATA, the order of
1106 installation may be changed, or even unstable among different hosts,
1107 due to the use of associative arrays in awk. The increased use of
1108 awk matches a similar move in Autoconf to provide for better scaling.
1110 Further, most undocumented per-rule install command variables such as
1111 binSCRIPT_INSTALL have been removed because they are not needed any
1112 more. Packages which use them should be using the appropriate one of
1113 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1114 counterpart, depending on the type of files and the need for automatic
1115 target directory creation.
1117 - The "deleted header file problem" for *.m4 files is avoided by
1118 stub rules. This allows `make' to trigger a rerun of `aclocal'
1119 also if some previously needed macro file has been removed.
1121 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1122 an otherwise up to date tree.
1124 - The `color-tests' option causes colored test result output on terminals.
1126 - The `parallel-tests' option enables a new test driver that allows for
1127 parallel test execution, inter-test dependencies, lazy test execution
1128 for unit-testing, re-testing only failed tests, and formatted result output
1129 as RST (reStructuredText) and HTML. Enabling this option may require some
1130 changes to your test suite setup; see the manual for details.
1132 - The `silent-rules' option enables Linux kernel-style silent build output.
1133 This option requires the widely supported but non-POSIX `make' feature
1134 of recursive variable expansion, so do not use it if your package needs
1135 to build with `make' implementations that do not support it.
1137 To enable less verbose build output, the developer has to use the Automake
1138 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1139 macro. The user may then set the default verbosity by passing the
1140 `--enable-silent-rules' option to `configure'. At `make' run time, this
1141 default may be overridden using `make V=0' for less verbose, and `make V=1'
1142 for backward-compatible verbose output.
1144 - New prefix `notrans_' for manpages which should not be transformed
1145 by --program-transform.
1147 - New macro AM_COND_IF for conditional evaluation and conditional
1150 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1151 remove the file in a non-VPATH build. Such setups work with Autoconf
1154 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1155 the default setting.
1157 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1158 useful especially for multi-line values.
1160 - Automake's early configure-time sanity check now diagnoses an
1161 unsafe absolute source directory name and makes configure fail.
1163 - The Automake macros and rules cope better with whitespace in the
1164 current directory name, as long as the relative path to `configure'
1165 does not contain whitespace. To this end, the values of `$(MISSING)'
1166 and `$(install_sh)' may contain suitable quoting, and their expansion
1167 might need `eval'uation if used outside of a makefile. These
1168 undocumented variables may be used in several documented macros such
1169 as $(AUTOCONF) or $(MAKEINFO).
1173 * Long-standing bugs:
1175 - Fix aix dependency tracking for libtool objects.
1177 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1178 unnecessary use of the `compile' script.
1180 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1181 correct `-rpath' argument is used now.
1183 - `config.status --file=Makefile depfiles' now also works with the
1184 extra quoting used internally by Autoconf 2.62 and newer
1185 (it used to work only without the `--file=' bit).
1187 - The `missing' script works better with versioned tool names.
1189 - Semantics for `missing help2man' have been revamped:
1191 Previously, if `help2man' was not present, `missing help2man' would have
1192 the following semantics: if some man page was out of date but present, then
1193 a warning would be printed, but the exit status was 0. If the man page was
1194 not present at all, then `missing' would create a replacement man page
1195 containing an error message, and exit with a status of 2. This does not play
1196 well with `make': the next run will see this particular man page as being up
1197 to date, and will only error out on the next generated man page, if any;
1198 repeat until all pages are done. This was not desirable.
1200 These are the new semantics: if some man page is not present, and help2man
1201 is not either, then `missing' will warn and generate the replacement page
1202 containing the error message, but exit successfully. However, `make dist'
1203 will ensure that no such bogus man pages are packaged into a tarball.
1205 - Targets provided by automake behave better with `make -n', in that they
1206 take care not to create files.
1208 - `config.status Makefile... depfiles' works fine again in the presence of
1209 disabled dependency tracking.
1211 - The default no-op recursive rules for these targets also work with BSD make
1212 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1214 - `make distcheck' works also when both a directory and some file below it
1215 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1217 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1218 `make mostlyclean' any more; only the LaTeX by-products are.
1220 - Renamed objects also work with the `subdir-objects' option and
1221 source file languages which Automake does not know itself.
1223 - `automake' now correctly complains about variable assignments which are
1224 preceded by a comment, extend over multiple lines with backslash-escaped
1225 newlines, and end in a comment sign. Previous versions would silently
1226 and wrongly ignore such assignments completely.
1228 * Bugs introduced by 1.10:
1230 - Fix output of dummy dependency files in presence of post-processed
1231 Makefile.in's again, but also cope with long lines.
1233 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1234 that have been declared as programs in the same Makefile.
1235 This is for consistency with the analogous change to TESTS in 1.10.
1237 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1238 followed by directories containing config headers.
1240 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1244 * Version requirements:
1246 - Autoconf 2.60 or greater is required.
1248 - Perl 5.6 or greater is required.
1250 * Changes to aclocal:
1252 - aclocal now also supports -Wmumble and -Wno-mumble options.
1254 - `dirlist' entries (for the aclocal search path) may use shell
1255 wildcards such as `*', `?', or `[...]'.
1257 - aclocal supports an --install option that will cause system-wide
1258 third-party macros to be installed in the local directory
1259 specified with the first -I flag. This option also uses #serial
1260 lines in M4 files to upgrade local macros.
1262 The new aclocal options --dry-run and --diff help to review changes
1263 before they are installed.
1265 - aclocal now outputs an autoconf version check in aclocal.m4 in
1266 projects using automake.
1268 For a few years, automake and aclocal have been calling autoconf
1269 (or its underlying engine autom4te) to accurately retrieve the
1270 data they need from configure.ac and its siblings. Doing so can
1271 only work if all autotools use the same version of autoconf. For
1272 instance a Makefile.in generated by automake for one version of
1273 autoconf may stop working if configure is regenerated with another
1274 version of autoconf, and vice versa.
1276 This new version check ensures that the whole build system has
1277 been generated using the same autoconf version.
1279 * Support for new Autoconf macros:
1281 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1283 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1284 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1285 in different directories. However, only one instance of such a
1286 library objects directory is supported.
1288 * Change to Libtool support:
1290 - Libtool generic flags (those that go before the --mode=MODE option)
1291 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1293 * Yacc and Lex changes:
1295 - The rebuild rules for distributed Yacc and Lex output will avoid
1296 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1299 - ylwrap is now always used for lex and yacc source files,
1300 regardless of whether there is more than one source per directory.
1302 * Languages changes:
1304 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1305 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1306 tracking, unlike non-preprocessed assembler (*.s).
1308 - subdir-object mode works now with Assembler. Automake assumes
1309 that the compiler understands `-c -o'.
1311 - Preprocessed assembler (*.S) compilation now also honors
1312 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1314 - Improved support for Objective C:
1315 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1316 - A new section of the manual documents the support.
1318 - New support for Unified Parallel C:
1319 - AM_PROG_UPC looks for a UPC compiler.
1320 - A new section of the manual documents the support.
1322 - Per-target flags are now correctly handled in link rules.
1324 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1325 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1326 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1327 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1329 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1330 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1331 is expected to work (and actually works during compilation).
1333 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1334 "in addition to" breaks backward compatibility with older versions.
1335 If your package used both variables, as in
1337 AM_LDFLAGS = common flags
1338 bin_PROGRAMS = a b c
1339 a_LDFLAGS = more flags
1342 and assumed *_LDFLAGS would sum up, you should rewrite it as
1344 AM_LDFLAGS = common flags
1345 bin_PROGRAMS = a b c
1346 a_LDFLAGS = $(AM_LDFLAGS) more flags
1349 This new behavior of *_LDFLAGS is more coherent with other
1350 per-target variables, and the way *_LDFLAGS variables were
1351 considered internally.
1353 * New installation targets:
1355 - New targets mandated by GNU Coding Standards:
1360 By default they will only install Texinfo manuals.
1361 You can customize them with *-local variants:
1367 - The undocumented recursive target `uninstall-info' no longer exists.
1368 (`uninstall' is in charge of removing all possible documentation
1369 flavors, including optional formats such as dvi, ps, or info even
1370 when `no-installinfo' is used.)
1372 * Miscellaneous changes:
1374 - Automake no longer complains if input files for AC_CONFIG_FILES
1375 are specified using shell variables.
1377 - clean, distribution, or rebuild rules are normally disabled for
1378 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1379 AC_CONFIG_LINK specified using shell variables. However, if these
1380 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1381 be able to output rules anyway.
1382 (See the Automake documentation for AC_CONFIG_FILES.)
1384 - $(EXEEXT) is automatically appended to filenames of TESTS
1385 that have been declared as programs in the same Makefile.
1386 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1388 - `-Wportability' has finally been turned on by default for `gnu' and
1389 `gnits' strictness. This means, automake will complain about %-rules
1390 or $(GNU Make functions) unless you switch to `foreign' strictness or
1391 use `-Wno-portability'.
1393 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1394 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1395 $(mkdir_p) variable is still defined (to the same value as
1396 $(MKDIR_P)) but should be considered obsolete. If you are using
1397 $(mkdir_p) in some of your rules, please plan to update them to
1398 $(MKDIR_P) at some point.
1400 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1401 They still work in this release, but may be withdrawn in a future one.
1403 - Inline compilation rules for gcc3-style dependency tracking are
1406 - Automake installs a "Hello World!" example package in $(docdir).
1407 This example is used throughout the new "Autotools Introduction"
1408 chapter of the manual.
1410 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1414 * Makefile.in bloat reduction:
1416 - Inference rules are used to compile sources in subdirectories when
1417 the `subdir-objects' option is used and no per-target flags are
1418 used. This should reduce the size of some projects a lot, because
1419 Automake used to output an explicit rule for each such object in
1422 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1423 object that must be built with explicit rules. It just outputs
1424 the rules required to build the kind of object considered: either
1425 the two .o and .obj rules for usual objects, or the .lo rule for
1428 * Change to Libtool support:
1430 - Libtool tags are used with libtool versions that support them.
1431 (I.e., with Libtool 1.5 or greater.)
1433 - Automake is now able to handle setups where a libtool library is
1434 conditionally installed in different directories, as in
1437 lib_LTLIBRARIES = liba.la
1439 pkglib_LTLIBRARIES = liba.la
1441 liba_la_SOURCES = ...
1443 * Changes to aclocal:
1445 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1446 really evaluated, before it decides to include them in aclocal.m4.
1447 This solves nasty problems with conditional redefinitions of
1448 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1449 *.m4 files to be included in any project using these macros.
1450 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1451 most famous instance of this bug.)
1453 - Do not complain about missing conditionally AC_REQUIREd macros
1454 that are not actually used. In 1.8.x aclocal would correctly
1455 determine which of these macros were really needed (and include
1456 only these in the package); unfortunately it would also require
1457 all of them to be present in order to run. This created
1458 situations were aclocal would not work on a tarball distributing
1459 all the macros it uses. For instance running aclocal on a project
1460 containing only the subset of the Gettext macros in use by the
1461 project did not work, because gettext conditionally requires other
1464 * Portability improvements:
1466 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1467 tar-pax. The new option filename-length-max=99 helps diagnosing
1468 filenames that are too long for tar-v7. (PR/414)
1470 - Variables aumented with `+=' are now automatically flattened (i.e.,
1471 trailing backslashes removed) and then wrapped around 80 colummns
1472 (adding trailing backslashes). In previous versions, a long series
1478 would result in a single-line definition of VAR that could possibly
1479 exceed the maximum line length of some make implementations.
1481 Non-augmented variables are still output as they are defined in
1486 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1487 Works the same as the old Fortran 77 implementation; just replace
1488 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1489 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1491 - Support for conditional _LISP.
1493 - Support for conditional -hook and -local rules (PR/428).
1495 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1497 - Automake will not write any Makefile.ins after the first error it
1498 encounters. The previous Makefile.ins (if any) will be left in
1499 place. (Warnings will not prevent output, but remember they can
1500 be turned into errors with -Werror.)
1502 - The restriction that SUBDIRS must contain direct children is gone.
1505 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1506 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1508 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1510 Bugs fixed in 1.8.5:
1512 * Long-standing bugs:
1514 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1515 so that `make distclean' and `make maintainer-clean' can work.
1517 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1519 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1521 - Polish diagnostic when no input file is found.
1523 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1525 Bugs fixed in 1.8.4:
1527 * Long-standing bugs:
1529 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1530 overridden by the user.
1532 - Honor PATH_SEPARATOR in various places of the Automake package, for
1535 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1538 - Fix install-sh so it can install the `mv' binary... using `mv'.
1540 - Fix tru64 dependency tracking for libtool objects.
1542 - Work around Exuberant Ctags when creating a TAGS files in a directory
1543 without files to scan but with subdirectories to include.
1545 * Bugs introduced by 1.8:
1547 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1548 not defined in the same conditions as the _LDADD that uses it.
1550 - Do not warn when JAVAROOT is overridden, this is legitimate.
1552 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1554 Bugs fixed in 1.8.3:
1556 * Long-standing bugs:
1558 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1559 or any of the other *dir variables contain a space.
1561 Please note that Automake does not and cannot support spaces in
1562 filenames that are involved during the build. This change affects
1563 only installation paths, so that `make install' does not bomb out
1564 in packages configured with
1565 ./configure --prefix '/c/Program Files'
1567 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1568 POSIXLY_CORRECT is set.
1570 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1571 since Autoconf 2.54, which defines LIBOBJS itself.
1573 - Fix a potential (but unlikely) race condition in parallel elisp
1574 builds. (Introduced in 1.7.3.)
1576 - Do not assume that users override _DEPENDENCIES in all conditions
1577 where Automake will try to define them.
1579 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1580 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1583 This fix also affects the $(mkdir_p) variable defined since
1584 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1585 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1587 - Secure temporary directory creation in `make distcheck'. (PR/413)
1589 - Do not generate two build rules for `parser.h' when the
1590 parser appears in two different conditionals.
1592 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1593 checking. Usually ./configure will not pick this shell; so this
1594 fix only helps cases where the shell is forced to /bin/sh.
1596 * Bugs introduced by 1.8:
1598 - In some situations (hand-written `m4_include's), aclocal would
1599 call the `File::Spec->rel2abs' method, which was only introduced
1600 in Perl 5.6. This new version reestablish support Perl 5.005.
1602 It is likely that the next major Automake releases will require at
1603 least Perl 5.6. Consider upgrading your development environment
1604 if you are still using the five-year-old Perl 5.005.
1606 - Automake would sometimes fail to define rules for targets listed
1607 in variables defined in multiple conditions. For instance on
1613 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1614 `b.$(OBJEXT): b.c' rule.
1616 * New sections in manual:
1618 - Third-Party Makefiles: how to interface third party Makefiles.
1619 - Upgrading: upgrading packages to newer Automake versions.
1620 - Multiple Outputs: handling tools that produce many outputs.
1622 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1626 * A (well known) portability bug slipped in the changes made to
1627 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1628 install anything on Tru64.
1630 * Fix install rules for conditionally built python files. (This never
1633 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1637 * Bugs introduced by 1.8:
1639 - Fix Config.pm import error with old Perl versions (at least
1640 5.005_03). One symptom is that aclocal could not find its macro
1643 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1644 created by `make install' are always world readable, even if the
1645 installer happens to have an overly restrictive umask (e.g. 077).
1646 This was a mistake and has been reverted. There are at least two
1647 reasons why we must not use `-m 0755':
1648 - it causes special bits like SGID to be ignored,
1649 - it may be too restrictive (some setups expect 775 directories).
1651 - Fix aclocal to honor definitions located in files which have been
1652 m4_included manually. aclocal 1.8 had been updated to check
1653 m4_included files for new requirements, but forgot that these
1654 m4_included files can also provide new definitions.
1656 Note that if you have such a setup, we recommend you get rid of
1657 it. In the past, there was a reason to m4_include files manually:
1658 aclocal used to duplicate entire M4 files into aclocal.m4, even
1659 files that were distributed. Some packages were therefore
1660 m4_including the distributed file directly, and playing some
1661 tricks to ensure aclocal would not copy that file to aclocal.m4,
1662 in order to limit the amount of duplication. Since aclocal 1.8.x
1663 will precisely output m4_includes for local M4 files, we recommend
1664 that you clean up your setup, removing all manual m4_includes and
1665 letting aclocal output them.
1667 - Output detailed menus in the Info version if the Automake manual,
1668 so that Emacs can locate the indexes.
1670 - configure.ac and configure were listed twice in DIST_COMMON (an
1671 internal variable where Automake lists configury files to
1672 distribute). This was harmless, but unaesthetic.
1674 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1675 This was an issue only in the Automake package itself, not in
1678 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1679 DEST:SRC. This was wrong, as some packages do
1680 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1683 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1684 argument. This caused two kinds of failures:
1685 - Rules installing data in a conditionally defined directory
1686 failed when that directory was undefined. In this case no
1687 argument was supplied.
1688 - `make installdirs' failed, because several directories were
1689 passed to $(mkdir_p). This was an issue only on platform
1690 were $(mkdir_p) is implemented with `install-sh -d'.
1691 $(mkdir_p) as been changed to accept 0 or more arguments, as
1694 * Long-standing bugs:
1696 - Fix an unexpected diagnostic occurring when users attempt
1697 to override some internal variables that Automake appends to.
1699 - aclocal now scans configure.ac for macro definitions (PR/319).
1701 - Fix a portability issue with OSF1/Tru64 Make. If a directory
1702 distributes files which are outside itself (this usually occurs
1703 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
1704 from a parent package), then `make distcheck' fails due to an
1705 optimization performed by OSF1/Tru64 Make in its VPATH handling.
1706 (tests/subpkg2.test failure)
1708 - Fix another portability issue with Sun and OSF1/Tru64 Make.
1709 In a VPATH-build configuration, `make install' would install
1710 nobase_ files to wrong locations.
1712 - Fix a Perl `uninitialized value' diagnostic occurring when
1713 automake complains that a Texinfo file does not have a
1714 @setfilename statement.
1716 - Erase config.status.lineno during `make distclean'. This file
1717 can be created by config.status. Automake already knew about
1718 configure.lineno, but forgot config.status.lineno.
1720 - Distribute all files, even those which are built and installed
1721 conditionally. This change affects files listed in conditionally
1722 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
1723 as well as those listed in conditionally defined dist_*_DATA,
1724 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
1726 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
1727 doesn't conform to POSIX.
1729 - Normalize help strings for configure variables and options added
1734 - Check for python2.4 in AM_PATH_PYTHON.
1736 * Spurious failures in test suite:
1738 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
1739 tests/ltconv.test: fix failures with CVS Libtool.
1740 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
1741 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
1742 fix failures with old Texinfo versions.
1744 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1750 - The NEWS file is more verbose.
1754 - Autoconf 2.58 or greater is required.
1758 - Default source file names in the absence of a _SOURCES declaration
1759 are made by removing any target extension before appending `.c', so
1760 to make the libtool module `foo.la' from `foo.c', you only need to
1763 lib_LTLIBRARIES = foo.la
1764 foo_la_LDFLAGS = -module
1766 For backward compatibility, foo_la.c will be used instead of
1767 foo.c if this file exists or is the explicit target of a rule.
1768 However -Wobsolete will warn about this deprecated naming.
1770 - AR's `cru' flags are now set in a global ARFLAGS variable instead
1771 of being hard-coded in each $(AR) invocation, so they can be
1772 substituted from configure.ac. This has been requested by people
1773 dealing with non-POSIX ar implementations.
1775 - New warning option: -Woverride. This will warn about any user
1776 target or variable definitions which override Automake
1779 - Texinfo rules back up and restore info files when makeinfo fails.
1781 - Texinfo rules now support the `html' target.
1782 Running this requires Texinfo 4.0 or greater.
1784 `html' is a new recursive target, so if your package mixes
1785 hand-crafted `Makefile.in's with Automake-generated
1786 `Makefile.in's, you should adjust the former to support (or
1787 ignore) this target so that `make html' recurses successfully. If
1788 you had a custom `html' rule in your `Makefile.am', it's better to
1789 rename it as `html-local', otherwise your rule will override
1790 Automake's new rule (you can check that by running `automake
1791 -Woverride') and that will stop the recursion to subdirectories.
1793 Last but not least, this `html' rule is declared PHONY, even when
1794 overridden. Fortunately, it appears that few packages use a
1795 non-PHONY `html' rule.
1797 - Any file which is m4_included from configure.ac will appear as a
1798 configure and Makefile.in dependency, and will be automatically
1801 - The rules for rebuilding Makefiles and Makefile.ins will now
1802 rebuild all Makefiles and all Makefile.ins at once when one of
1803 configure's dependencies has changed. This is considerably faster
1804 than previous implementations, where config.status and automake
1805 were run separately in each directory (this still happens when you
1806 change a Makefile.am locally, without touching configure.ac or
1807 friends). Doing this also solves a longstanding issue: these
1808 rebuild rules failed to work when adding new directories to the
1809 tree, forcing you to run automake manually.
1811 - For similar reasons, the rules to rebuild configure,
1812 config.status, and aclocal.m4 are now defined in all directories.
1813 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
1814 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
1815 should better define them in all directories. This is easily done
1816 using an AC_SUBST (make sure you prefix these dependencies with
1817 $(top_srcdir) since this variable will appear at different
1818 levels of the build tree).
1820 - aclocal will now use `m4_include' instead of copying local m4
1821 files into aclocal.m4. (Local m4 files are those you ship with
1822 your project, other files will be copied as usual.)
1824 Because m4_included files are automatically distributed, it means
1825 for most projects there is no point in EXTRA_DISTing the list of
1826 m4 files which are used. (You can probably get rid of
1827 m4/Makefile.am if you had one.)
1829 - aclocal will avoid touching aclocal.m4 when possible, so that
1830 Autom4te's cache isn't needlessly invalidated. This behavior can
1831 be switched off with the new `--force' option.
1833 - aclocal now uses Autoconf's --trace to detect macros which are
1834 actually used and will no longer include unused macros simply
1835 because they where mentioned. This was often the case for macros
1836 called conditionally.
1838 - New options no-dist and no-dist-gzip.
1840 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
1841 py-compile, and ylwrap, now all understand --version and --help.
1843 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
1844 links as part of the distclean target and including source files in
1847 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
1848 argument. The latter can be used to override the default behavior
1849 (which is to abort).
1851 - Automake will exit with $? = 63 on version mismatch. (So does
1852 Autoconf 2.58) missing knows this, and in this case it will
1853 emulate the tools as if they were absent. Because older versions
1854 of Automake and Autoconf did not use this exit code, this change
1855 will only be useful in projects generated with future versions of
1858 - When using AC_CONFIG_FILES with multiple input files, Automake
1859 generates the first ".in" input file for which a ".am" exists.
1860 (Former versions would try to use only the first input file.)
1862 - lisp_DATA is now allowed. If you are using the empty ELCFILES
1863 idiom to disable byte-compilation of lisp_LISP files, it is
1864 recommended that you switch to using lisp_DATA. Note that
1865 this is not strictly equivalent: lisp_DATA will install elisp
1866 files even if emacs is not installed, while *_LISP do not
1867 install anything unless emacs is found.
1869 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
1870 available. This selection is achieved through the Makefile
1871 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
1872 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
1873 `$(install_sh) -m 0755 -d'.
1877 - Because `mkdir -p' is available on most platforms, and we can use
1878 `install-sh -d' when it is not, the use of the mkinstalldirs
1879 script is being phased out. `automake --add-missing' no longer
1880 installs it, and if you remove mkinstalldirs from your package,
1881 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
1883 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
1884 gettextize and autopoint will install it when needed. Automake
1885 will continue to define the $(mkinstalldirs) and to distribute
1886 mkinstalldirs when this script is in the source tree.
1888 - AM_PROG_CC_STDC is now empty. The content of this macro was
1889 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
1890 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
1891 renaming should be safe, even if you have to support several,
1892 versions of Automake, because AC_PROG_CC defines this variable
1893 since Autoconf 2.54.)
1895 - Some users where using the undocumented ACLOCAL_M4_SOURCES
1896 variable to override the aclocal.m4 dependencies computed
1897 (inaccurately) by older versions of Automake. Because Automake
1898 now tracks configure's m4 dependencies accurately (see m4_include
1899 above), the use of ACLOCAL_M4_SOURCES should be considered
1900 obsolete and will be flagged as such when running `automake
1905 - Defining programs conditionally using Automake conditionals no
1906 longer leads to a combinatorial explosion. The following
1907 construct used to be troublesome when used with dozens of
1922 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
1924 - Due to implementation constraints, previous versions of Automake
1925 proscribed multiple conditional definitions of some variables
1935 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
1936 This restriction has been lifted, and these variables now
1937 support multiple conditional definitions as do other variables.
1939 - Cleanup the definitions of $(distdir) and $(top_distdir).
1940 $(top_distdir) now points to the root of the distribution
1941 directory created during `make dist', as it did in Automake 1.4,
1942 not to the root of the build tree as it did in intervening
1943 versions. Furthermore these two variables are now only defined in
1944 the top level Makefile, and passed to sub-directories when running
1947 - The --no-force option now correctly checks the Makefile.in's
1948 dependencies before deciding not to update it.
1950 - Do not assume that make files are called Makefile in cleaning rules.
1952 - Update .info files in the source tree, not in the build tree. This
1953 is what the GNU Coding Standard recommend. Only Automake 1.7.x
1954 used to update these files in the build tree (previous versions did
1955 it in the source tree too), and it caused several problems, varying
1956 from mere annoyance to portability issues.
1958 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
1959 when --add-missing and --force-missing are used. For backward
1960 compatibility --add-missing will continue to install COPYING (in
1961 `gnu' strictness) when none of these three files exist, but this
1962 use is deprecated: you should better choose a license yourself and
1963 install it once for all in your source tree (and in your code
1966 - Fix ylwrap so that it does not overwrite header files that haven't
1967 changed, as the inline rule already does.
1969 - User-defined rules override automake-defined rules for the same
1970 targets, even when rules do not have commands. This is not new
1971 (and was documented), however some of the automake-generated
1972 rules have escaped this principle in former Automake versions.
1973 Rules for the following targets are affected by this fix:
1975 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
1976 info, info-am, install-data-am, install-exec-am, install-info,
1977 install-info-am, install-man, installcheck-am, maintainer-clean,
1978 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
1979 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
1981 Practically it means that an attempt to supplement the dependencies
1982 of some target, as in
1984 clean: my-clean-rule
1986 will now *silently override* the automake definition of the
1987 rule for this target. Running `automake -Woverride' will diagnose
1988 all such overriding definitions.
1990 It should be noted that almost all of these targets support a *-local
1991 variant that is meant to supplement the automake-defined rule
1992 (See node `Extending' in the manual). The above rule should
1995 clean-local: my-clean-rule
1997 These *-local targets have been documented since at least
1998 Automake 1.2, so you should not fear the change if you have
1999 to support multiple automake versions.
2003 - The Automake manual is now distributed under the terms of the GNU FDL.
2005 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2007 - core dumps are no longer removed by the cleaning rules. There are
2008 at least three reasons for this:
2009 1. These files should not be created by any build step,
2010 so their removal do not fit any of the cleaning rules.
2011 Actually, they may be precious to the developer.
2012 2. If such file is created during a build, then it's clearly a
2013 bug Automake should not hide. Not removing the file will
2014 cause `make distcheck' to complain about its presence.
2015 3. Operating systems have different naming conventions for
2016 core dump files. A core file on one system might be a
2017 completely legitimate data file on another system.
2019 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2020 defined by Automake. This means that any definition in the
2021 environment will be used, unless overridden in the Makefile.am or
2022 on the command line. The old behavior, where these variables were
2023 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2024 AC_ARG_VARing each variable from configure.ac.
2026 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2027 documented. (The is not a new feature, these variables have
2028 been there since at least Automake 1.4.)
2030 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2032 Bugs fixed in 1.7.9:
2033 * Fix install-strip to work with nobase_ binaries.
2034 * Fix renaming of #line directives in ylwrap.
2035 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2037 Bugs fixed in 1.7.8:
2038 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2039 * Fix detection of Debian's install-info, broken since version 1.5.
2040 (Debian bug #213524).
2041 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2042 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2044 Bugs fixed in 1.7.7:
2045 * The implementation of automake's --no-force option is unreliable,
2046 so this option is ignored in this version. A real fix will appear in
2047 Automake 1.8. (Debian Bug #206299)
2048 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2049 argument is given. (PR/399)
2050 * Do not warn about leading `_' in variable names, even with -Wportability.
2051 * Support user redefinitions of TEXINFO_TEX.
2052 * depcomp: support AIX Compiler version 6.
2053 * Fix missing rebuilds during `make dist' with BSD make.
2054 (Could produce tarballs containing out-of-date files.)
2055 * Resurrect multilib support.
2056 * Noteworthy manual updates:
2057 - Extending aclocal: how to write m4 macros that won't trigger warnings
2059 - A Shared Library: Rewrite and split into subsections.
2061 Bugs fixed in 1.7.6:
2062 * Fix depcomp's icc mode for ICC 7.1.
2063 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2064 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2065 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2066 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2067 * Remove Latin-1 characters from elisp-comp.
2068 * Update the manual's @dircategory to match the Free Software Directory.
2070 Bugs fixed in 1.7.5:
2071 * Update install-sh's license to remove an advertising clause.
2072 (Debian bug #191717)
2073 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2074 that caused invalid Makefile.ins to be generated.
2075 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2076 * New FAQ entry: renamed objects.
2078 Bugs fixed in 1.7.4:
2079 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2080 the Emacs implementation)
2081 * Fix output of aclocal.m4 dependencies in subdirectories.
2082 * Use `mv -f' instead of `mv' in fastdep rules.
2083 * Upgrade mdate-sh to work on OS/2.
2084 * Don't byte-compile elisp files when ELCFILES is set empty.
2085 (this documented feature was broken by 1.7.3)
2086 * Diagnose trailing backslashes on last line of Makefile.am.
2087 * Diagnose whitespace following trailing backslashes.
2088 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2089 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2091 * `make install' will build `BUILT_SOURCES' first.
2092 * Minor documentation fixes.
2094 Bugs fixed in 1.7.3:
2095 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2096 * Query distutils for `pythondir' and `pythonexecdir', instead of
2097 using an hardcoded path. This should allow builds on 64-bit
2098 distributions that usually use lib64/ instead of lib/.
2099 * AM_PATH_PYTHON will also search for python2.3.
2100 * elisp files are now built all at once instead of one by one. Besides
2101 incurring a speed-up, this is required to support interdependent elisp files.
2102 * Support for DJGPP:
2103 - `make distcheck' will now work in `_inst/' and `_build' instead
2104 of `=inst/' and `=build/'
2105 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2106 - install/uninstall `*.i[0-9][0-9]'-style info files
2107 - more changes that affect only the Automake package (not its output)
2108 * Fix some incompatibilities with upcoming perl-5.10.
2109 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2110 PACKAGE and VERSION.
2112 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2113 is troublesome with gcc and Solaris compilers. (PR/385)
2114 - makedepend mode: work with Libtool. (PR/385 too)
2116 * better support for unusual gettext setups, such as multiple po/ directories
2118 - Flag missing po/ and intl/ directories as warnings, not errors.
2119 - Disable these warnings if po/ does not exist.
2120 * Noteworthy manual updates:
2122 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2124 - Document `AM_YFLAGS = -d'. (PR/382)
2126 Bugs fixed in 1.7.2:
2127 * Fix installation and uninstallation of Info files built in subdirectories.
2128 * Do not run `./configure --with-included-gettext' during `make distcheck'
2129 if AM_GNU_GETTEXT([external]) is used.
2130 * Correctly uninstall renamed man pages.
2131 * Do not strip escaped newline in variables defined in one condition
2132 and augmented in another condition.
2133 * Fix ansi2knr rules for LIBOBJS sources.
2134 * Clean all known Texinfo index files, not only those which appear to
2135 be used, because we cannot know which indexes are used in included files.
2136 (PR/375, Debian Bug #168671)
2137 * Honor only the first @setfilename seen in a Texinfo file.
2138 * Treat "required file X not found" diagnostics as errors (exit status 1).
2139 * Don't complain that a required file is not found when it is a Makefile
2141 * Don't use single suffix inference rules when building `.info'-less
2142 Info files, for the sake of Solaris make.
2143 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2144 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2145 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2146 * Fix building of deansified files from subdirectories. (PR/370)
2147 * Add missing `fi' in the .c->.obj rules.
2148 * Improve install-sh to work even when names contain spaces or certain
2149 (but not all) shell metachars.
2150 * Fix the following spurious failures in the test suite:
2151 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2152 * Noteworthy manual updates:
2153 - Augment the section about BUILT_SOURCES.
2154 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2156 Bugs fixed in 1.7.1:
2157 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2159 * Aclocal should now recognize macro names containing parentheses, e.g.
2160 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2161 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2163 * Install Python files even if they were built. (PR/369)
2164 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2165 version might not be defined in the latter. (PR/358)
2166 * Reorder arguments passed to a couple of commands, so things works
2167 when POSIXLY_CORRECT=1.
2168 * Fix a regex that can cause Perl to segfault on large input.
2170 * Fix distribution of packages that have some sources defined conditionally,
2171 as in the `Conditional compilation using Automake conditionals' example
2173 * Fix spurious test suite failures on IRIX.
2174 * Don't report a required variable as undefined if it has been
2175 defined conditionally for the "right" conditions.
2176 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2177 `make distcheck' fails.
2178 * Fix distribution of included Makefile fragment, so we don't create
2179 spurious directories in the distribution. (PR/366)
2180 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2183 * Autoconf 2.54 is required.
2184 * `aclocal' and `automake' will no longer warn about obsolete
2185 configure macros. This is done by `autoconf -Wobsolete'.
2186 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2187 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2188 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2189 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2190 `configure.ac' for you.
2191 * Support for per-program and per-library `_CPPFLAGS'.
2192 * New `ctags' target (builds CTAGS files).
2193 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2194 (see `automake --help' or the manual for a list of them).
2195 * Honor the WARNINGS environment variable.
2196 * Omit the call to depcomp when using gcc3: call the compiler directly.
2197 * A new option, std-options, tests that programs support --help and --version
2198 when `make installcheck' is run. This is enabled by --gnits.
2199 * Texinfo rules now support the `ps' and `pdf' targets.
2200 * Info files are now created in the build directory, not the source directory.
2201 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2203 * `make distcheck' will enforce DESTDIR support by attempting
2205 * `+=' can be used in conditionals, even if the augmented variable
2206 was defined for another condition.
2207 * Makefile fragments (inserted with `include') are always distributed.
2208 * Use Autoconf's --trace interface to inspect configure.ac and get
2209 a more accurate view of it.
2210 * Add support for extending aclocal's default macro search path
2211 using a `dirlist' file within the aclocal directory.
2212 * automake --output-dir is deprecated.
2213 * The part of the distcheck target that checks whether uninstall actually
2214 removes all installed files has been moved in a separate target,
2215 distuninstallcheck, so it can be overridden easily.
2219 * Support for AM_INIT_GETTEXT([external])
2220 * Bug fixes, including:
2221 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2222 - nobase_ programs and scripts honor --program-transform correctly.
2223 - Erase configure.lineno during `make distclean'.
2224 - Erase YACC and LEX outputs during `make maintainer-clean'.
2227 * Many bug fixes, including:
2228 - Requiring the current version works.
2229 - Fix "$@" portability issues (for Zsh).
2230 - Fix output of dummy dependency files in presence of post-processed
2232 - Don't compute dependencies in background to avoid races with libtool.
2233 - Fix handling of _OBJECTS variables for targets sharing source variables.
2234 - Check dependency mode for Java when AM_PROG_GCJ is used.
2237 * automake --output-dir is deprecated
2238 * Many bug fixes, including:
2239 - Don't choke on AM_LDFLAGS definitions.
2240 - Clean libtool objects from subdirectories.
2241 - Allow configure variables with reserved suffix and unknown prefix
2242 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2243 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2246 * Autoconf 2.52 is required.
2247 * automake no longer run libtoolize.
2248 This is the job of autoreconf (from GNU Autoconf).
2249 * `dist' generates all the archive flavors, as did `dist-all'.
2250 * `dist-gzip' generates the Gzip tar file only.
2251 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2252 explosion. Makefile.in's keep a reasonable size.
2253 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2254 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2256 * `#line' of Lex and Yacc files are properly set.
2257 * EXTRA_DIST can contain generated directories.
2258 * Support for dot-less extensions in suffix rules.
2259 * The part of the distcheck target that checks whether distclean actually
2260 cleans all built files has been moved in a separate target, distcleancheck,
2261 so it can be overridden easily.
2262 * `make distcheck' will pass additional options defined in
2263 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2264 * Fixed CDPATH portability problems, in particular for MacOS X.
2265 * Fixed handling of nobase_ targets.
2266 * Fixed support of implicit rules leading to .lo objects.
2267 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2268 * Added uninstall-hook target
2269 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2270 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2271 (Note that "pkgname" is not "tarname", see the manual for details.)
2272 It is also possible to pass a list of global Automake options as
2273 first argument to this new form of AM_INIT_AUTOMAKE.
2274 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2275 to be a real assembler.
2276 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2277 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2278 * aclocal and automake are also installed with the version number
2279 appended, and some of the install directory names have changed.
2280 This lets you have multiple versions installed simultaneously.
2281 * Support for parsers and lexers in subdirectories.
2284 * Support for `configure.ac'.
2285 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2286 * `make dist-all' is much faster.
2287 * Allows '@' AC_SUBSTs in macro names.
2288 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2289 * User-side dependency tracking. Developers no longer need GNU make
2291 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2292 * Most files are correctly handled if they appear in subdirs
2293 For instance, a _DATA file can appear in a subdir
2294 * GNU tar is no longer required for `make dist'
2295 * Added support for `dist_' and `nodist_' prefixes
2296 * Added support for `nobase_' prefix
2297 * Compiled Java support
2298 * Support for per-executable and per-library compilation flags
2302 * Added support for the Fortran 77 programming language.
2303 * Re-indexed the Automake Texinfo manual.
2304 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2305 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2306 * Support for latest autoconf, including support for objext
2307 * Can now put `.' in SUBDIRS to control build order
2308 * `include' command and `+=' support for macro assignment
2309 * Dependency tracking no long susceptible to deleted header file problem
2310 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2315 * Better Cygwin32 support
2316 * Support for suffix rules with _SOURCES variables
2317 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2318 * @LEXLIB@ no longer required when lex source seen
2319 Lex support in `missing', and new lex macro. Update your missing script.
2320 * Built-in support for assembly
2321 * aclocal gives error if `AM_' macro not found
2322 * Passed YFLAGS, not YACCFLAGS, to yacc
2323 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2324 * Dependencies computed as a side effect of compilation
2325 * Preliminary support for Java
2326 * DESTDIR support at "make install" time
2327 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2331 * Better DejaGnu support
2332 * Added no-installinfo option
2333 * Added Emacs Lisp support
2334 * Added --no-force option
2335 * Included `aclocal' program
2336 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2337 * Now uses `AM_' macro names everywhere
2338 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2339 ansi2knr now works correctly on K&R sources
2340 * Better C++, yacc, lex support
2341 * Will compute _DEPENDENCIES variables automatically if not supplied
2342 * Will interpolate $(...) and ${...} when examining contents of a variable
2343 * .deps files now in build directory, not source directory; dependency
2344 handling generally rewritten
2345 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2346 * can now put config.h into a subdir
2347 * Added dist-all target
2348 * Support for install-info program (see texinfo 3.9)
2349 * Support for "yacc -d"
2350 * configure substitutions are automatically discovered and included
2351 in generated Makefile.in
2352 * Special --cygnus mode
2353 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2354 when making distribution. Some dependencies are auto-ignored.
2355 * Changed how libraries are specified in _LIBRARIES variable
2356 * Full libtool support, from Gord Matzigkeit
2357 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2358 AM_CONFIG_HEADER handles it automatically
2359 * Texinfo output files no longer need .info extension
2360 * Added `missing' support
2362 * Conditionals in Makefile.am, from Ian Taylor
2366 * distcheck target runs install and installcheck targets
2367 * Added preliminary support for DejaGnu.
2372 * More libtool fixes from Gord Matzigkeit; libtool support is still
2374 * Added support for jm_MAINTAINER_MODE
2376 * New "distcheck" target
2380 * mkinstalldirs and mdate-sh now appear in directory specified by
2382 * Removed DIST_SUBDIRS, DIST_OTHER
2383 * AC_ARG_PROGRAM only required when an actual program exists
2384 * dist-hook target now run before distribution packaged up; idea from
2385 Dieter Baron. Other hooks exist, too.
2386 * Preliminary (unfinished) support for libtool
2387 * Added short option names.
2388 * Better "dist" support when gluing together multiple packages
2392 * Documentation updates (many from François Pinard)
2393 * strictness `normal' now renamed to `foreign'
2394 * Renamed --install-missing to --add-missing
2395 * Now handles AC_CONFIG_AUX_DIR
2396 * Now handles TESTS macro
2397 * DIST_OTHER renamed to EXTRA_DIST
2398 * DIST_SUBDIRS is deprecated
2399 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2400 * Better error messages in many cases
2401 * Program names are canonicalized
2402 * Added "check" prefix; from Gord Matzigkeit
2406 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2407 * Beginnings of a test suite
2408 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2409 * Doesn't print anything when running
2410 * Beginnings of MAINT_CHARSET support
2411 * Can specify version in AUTOMAKE_OPTIONS
2412 * Most errors recognizable by Emacs' M-x next-error
2413 * Added --verbose option
2414 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2415 configure-generated names
2416 * Required macros now distributed in aclocal.m4
2418 * --strictness=gnu is default
2422 * More sophisticated configure.in scanning; now understands ALLOCA and
2423 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2424 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2425 * CONFIG_HEADER variable now obsolete
2426 * Can handle multiple Texinfo sources
2427 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2428 * HEADERS variable no longer needed; now can put .h files directly into
2429 foo_SOURCES variable.
2430 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2431 corresponding ".in" files are included in the distribution.
2434 * Added --gnu and --gnits options
2435 * More standards checking
2437 * Cleaned up 'dist' targets
2438 * Added AUTOMAKE_OPTIONS variable and several options
2439 * Now scans configure.in to get some information (preliminary)
2442 * Works with Perl 4 again
2445 * Added --install-missing option.
2446 * Pretty-prints generated macros and rules
2447 * Comments in Makefile.am are placed more intelligently in Makefile.in
2448 * Generates .PHONY target
2449 * Rule or macro in Makefile.am now overrides contents of Automake file
2450 * Substantial cleanups from François Pinard
2454 * Works with Perl 4 again.
2457 * New uniform naming scheme.
2458 * --strictness option
2460 * '.c' files corresponding to '.y' or '.l' files are automatically
2462 * Many bug fixes and cleanups
2465 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2468 * Bug fixes in 'clean' code.
2469 * Now generates 'installdirs' target.
2470 * man page installation reworked.
2471 * 'make dist' no longer re-creates all Makefile.in's.
2474 * Reimplemented in Perl
2475 * Added --amdir option (for debugging)
2476 * Texinfo support cleaned up.
2477 * Automatic de-ANSI-fication cleaned up.
2478 * Cleaned up 'clean' targets.
2481 * Automatic dependency tracking
2482 * More documentation
2483 * New variables DATA and PACKAGEDATA
2484 * SCRIPTS installed using $(INSTALL_SCRIPT)
2485 * No longer uses double-colon rules
2487 * Changes in advance of internationalization
2491 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2493 This program is free software; you can redistribute it and/or modify
2494 it under the terms of the GNU General Public License as published by
2495 the Free Software Foundation; either version 2, or (at your option)
2498 This program is distributed in the hope that it will be useful,
2499 but WITHOUT ANY WARRANTY; without even the implied warranty of
2500 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2501 GNU General Public License for more details.
2503 You should have received a copy of the GNU General Public License
2504 along with this program. If not, see <http://www.gnu.org/licenses/>.