3 * WARNING: Future backward-incompatibilities!
5 - Automake 1.14 will require Autoconf 2.70 or later (which is still
6 unreleased at the moment of writing, but is planned to be released
7 before Automake 1.14 is).
9 - Automake 1.14 will drop support for the long-deprecated 'configure.in'
10 name for the Autoconf input file. You are advised to start using
11 recommended name 'configure.ac' instead, ASAP.
13 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated
14 in Automake 1.14 (where it will raise warnings in the "obsolete"
15 category). You are advised to start relying on the new Automake
16 support for AC_CONFIG_MACRO_DIRS instead (which was introduced in
19 - Support for IRIX and the SGI C/C++ compilers will be removed in
20 Automake 1.14: they have seen their last release in 2006, and SGI
21 is expected to retire support from them in December 2013; see
22 <http://www.sgi.com/services/support/irix_mips_support.html> for
25 - Future versions of Automake might remove support for MS-DOS and
26 Windows 95/98/ME (support for them was offered by relying on the
27 DJGPP project). Note however that both Cygwin and MSYS/MinGW on
28 modern Windows versions will continue to be fully supported.
30 - Support for the long-deprecated INCLUDES variable will be removed
31 altogether in Automake 1.14. The AM_CPPFLAGS variable should be
34 - Automake-provided scripts and makefile recipes might (finally!)
35 start assuming a POSIX shell in Automake 1.14.
37 - Starting from Automake 1.14, third-party m4 files located in the
38 system-wide aclocal directory, as well as in any directory listed
39 in the ACLOCAL_PATH environment variable, will take precedence
40 over "built-in" Automake macros. For example (assuming Automake
41 is installed in the /usr/local hierarchy), a definition of the
42 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
43 should take precedence over the same-named automake-provided macro
44 (defined in '/usr/local/share/aclocal-1.14/vala.m4').
46 * Obsolescent features:
48 - Use of suffix-less info files (that can be specified through the
49 '@setfilename' macro in Texinfo input files) is discouraged, and
50 its use will raise warnings in the 'obsolete' category.
52 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
53 is discouraged, and its use will raise warnings in the 'obsolete'
54 category. You are advised to simply use the '.texi' extension
57 * Documentation fixes:
59 - The long-deprecated but still supported two-arguments invocation form
60 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
61 thing to do, given that support for such an usage might need to remain
62 in place for a unspecified amount of time in order to cater for people
63 who want to define the version number for their package dynamically at
64 configure runtime (unfortunately, Autoconf does not yet support this
65 scenario, so we cannot delegate the work to it).
69 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
70 again, as they did in Automake 1.12.x (albeit printing runtime
71 warnings in the 'obsolete' category). Removing them has turned
72 out to be a very bad idea, because it complicated distro packing
73 enormously. Making them issue fatal warnings, as we did in
74 Automake 1.13, has turned out to be a similarly very bad idea,
75 for exactly the same reason.
77 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
83 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
84 causes a clear and helpful error message, instead of obscure ones
85 (issue introduced in Automake 1.13).
87 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
93 - ylwrap renames properly header guards in generated header files
94 (*.h), instead of leaving Y_TAB_H.
96 - ylwrap now also converts header guards in implementation files
97 (*.c). Because ylwrap failed to rename properly #include in the
98 implementation files, current versions of Bison (e.g., 2.7)
99 duplicate the generated header file in the implementation file.
100 The header guard then protects the implementation file from
101 duplicate definitions from the header file.
103 * Version requirements:
105 - Autoconf 2.65 or greater is now required.
107 - The rules to build PDF and DVI output from Texinfo input now
108 require Texinfo 4.9 or later.
112 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
113 option) has been removed. See discussion about automake bug#11034
114 for more background: <http://debbugs.gnu.org/11034>.
116 - The deprecated aclocal option '--acdir' has been removed. You
117 should use the options '--automake-acdir' and '--system-acdir'
118 instead (which have been introduced in Automake 1.11.2).
120 - The following long-obsolete m4 macros have been removed:
122 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
123 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
124 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
125 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
126 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
127 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
128 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
129 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
130 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
131 of the now-removed automatic de-ANSI-fication
134 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
136 - Use of the long-deprecated two- and three-arguments invocation forms
137 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
138 though (albeit with a warning in the 'obsolete' category), to cater
139 for people who want to define the version number for their package
140 dynamically (e.g., from the current VCS revision). We'll have to
141 continue this support until Autoconf itself is fixed to allow better
142 support for such dynamic version numbers.
144 * Elisp byte-compilation:
146 - The byte compilation of '.el' files into '.elc' files is now done
147 with a suffix rule. This has simplified the compilation process, and
148 more importantly made it less brittle. The downside is that emacs is
149 now invoked once for each '.el' files, which cause some noticeable
150 slowdowns. These should however be mitigated on multicore machines
151 (which are becoming the norm today) if concurrent make ("make -j")
154 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
155 files in the same subdirectory; for example, byte-compiling of file
156 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
157 'foo.elc'. This behaviour is backward-incompatible with older
158 Automake versions, but it is more natural and more sane. See also
161 - The Emacs invocation performing byte-compilation of '.el' files honors
162 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
163 one is developer-reserved and the latter one user-reserved.
165 - The 'elisp-comp' script, once provided by Automake, has been rendered
166 obsoleted by the just-described changes, and thus removed.
168 * Changes to Automake-generated testsuite harnesses:
170 - The parallel testsuite harness (previously only enabled by the
171 'parallel-tests' option) is the default one; the older serial
172 testsuite harness will still be available through the use of the
173 'serial-tests' option (introduced in Automake 1.12).
175 - The 'color-tests' option is now unconditionally activated by default.
176 In particular, this means that testsuite output is now colorized by
177 default if the attached terminal seems to support ANSI escapes, and
178 that the user can force output colorization by setting the variable
179 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
180 for backward-compatibility, although it's a handled as a no-op now.
182 * Silent rules support:
184 - Support for silent rules is now always active in Automake-generated
185 Makefiles. So, although the verbose output is still the default,
186 the user can now always use "./configure --enable-silent-rules" or
187 "make V=0" to enable quieter output in the package he's building.
189 - The 'silent-rules' option has now become a no-op, preserved for
190 backward-compatibility only. In particular, its use no longer
191 disables the warnings in the 'portability-recursive' category.
195 - The rules to build PDF and DVI files from Texinfo input now require
196 Texinfo 4.9 or later.
198 - The rules to build PDF and DVI files from Texinfo input now use the
199 '--build-dir' option, to keep the auxiliary files used by texi2dvi
200 and texi2pdf around without cluttering the build directory, and to
201 make it possible to run the "dvi" and "pdf" recipes in parallel.
203 * Automatic remake rules and 'missing' script:
205 - The 'missing' script no longer tries to update the timestamp of
206 out-of-date files that require a maintainer-specific tool to be
207 remade, in case the user lacks such a tool (or has a too-old version
208 of it). It just gives a useful warning, and in some cases also a
209 tip about how to obtain such a tool.
211 - The missing script has thus become useless as a (poor) way to work
212 around the sketched-timestamps issues that can happen for projects
213 that keep generated files committed in their VCS repository. Such
214 projects are now encouraged to write a custom "fix-timestamps.sh"
215 script to avoid such issues; a simple example is provided in the
216 "CVS and generated files" chapter of the automake manual.
220 - The user can now define his own recursive targets that recurse
221 in the directories specified in $(SUBDIRS). This can be done by
222 specifying the name of such targets in invocations of the new
223 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
227 - Any failure in the recipe of the "tags", "ctags", "cscope" or
228 "cscopelist" targets in a subdirectory is now propagated to the
229 top-level make invocation.
231 - Tags are correctly computed also for files in _SOURCES variables that
232 only list files with non-standard suffixes (see automake bug#12372).
234 * Improvements to aclocal and related rebuilds rules:
236 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
237 are now traced by aclocal, and can be used to declare the local m4
238 include directories. Formerly, one had to specify it with an explicit
239 '-I' option to the 'aclocal' invocation.
241 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
242 Automake versions will warn about its use, and later version will
243 remove support for it altogether.
245 * The depcomp script:
247 - Dropped support for libtool 1.4.
249 - Various internal refactorings. They should cause no visible change,
250 but the chance for regression is there anyway, so please report any
251 unexpected or suspicious behaviour.
253 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
254 This should cause no problem, since icc 8.0 has been released in
255 December 2003 -- almost nine years ago.
257 - Support for tcc (the Tiny C Compiler) has been improved, and is now
258 handled through a dedicated 'tcc' mode.
262 - ylwrap generates header guards with a single '_' for series of non
263 alphabetic characters, instead of several. This is what Bison >=
266 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
268 Bugs fixed in 1.12.6:
270 * Python-related bugs:
272 - The default installation location for python modules has been improved
273 for Python 3 on Debian and Ubuntu systems, changing from:
275 ${prefix}/lib/python3/dist-packages
279 ${prefix}/lib/python3.x/site-packages
281 This change should ensure modules installed using the default ${prefix}
282 "/usr/local" are found by default by system python 3.x installations.
283 See automake bug#10227.
285 - Python byte-compilation supports the new layout mandated by PEP-3147,
286 with its __pycache__ directory (automake bug#8847).
288 * Build system issues:
290 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
291 Automake's own build system works correctly again (bug introduced
296 - The Vala-related tests has been changed to adjust to the removal of
297 the 'posix' profile in the valac compiler. See automake bug#12934
300 - Some spurious testsuite failures related to older tools and systems
303 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
309 - The AM_PROG_VALAC macro has been enhanced to takes two further
310 optional arguments; it's signature now being
312 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
313 [ACTION-IF-NOT-FOUND])
315 - By default, AM_PROG_VALAC no longer aborts the configure invocation
316 if the Vala compiler found is too old, but simply prints a warning
317 messages (as it did when the Vala compiler was not found). This
318 should avoid unnecessary difficulties for end users that just want
319 to compile the unmodified, distributed Vala-generated C sources,
320 but happens to have an old Vala compiler in their PATH. This fixes
323 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
324 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
325 This is a better default, because with it a triggered makefile rule
326 invoking a Vala compilation will clearly fail with an informative error
327 message like "valac: command not found", rather than silently, with
328 the error possibly going unnoticed or triggering harder-to-diagnose
329 fallout failures in later steps.
331 * Miscellaneous changes:
333 - automake and aclocal no longer honours the 'perllibdir' environment
334 variable. That had always been intended only as an hack required in
335 the testsuite, not meant for any use beyond that.
337 Bugs fixed in 1.12.5:
339 * Long-standing bugs:
341 - Automake no longer generates spurious remake rules invoking autoheader
342 to regenerate the template corresponding to header files specified after
343 the first one in AC_CONFIG_HEADERS (automake bug#12495).
345 - When wrapping Microsoft tools, the 'compile' script falls back to
346 finding classic 'libname.a' style libraries when 'name.lib' and
347 'name.dll.lib' aren't available.
349 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
353 * Warnings and deprecations:
355 - Warnings in the 'obsolete' category are enabled by default both in
356 automake and aclocal.
358 * Miscellaneous changes:
360 - Some testsuite weaknesses and spurious failures have been fixed.
362 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
366 * Miscellaneous changes:
368 - The '.m4' files provided by Automake no longer define serial numbers.
369 This should cause no difference in the behaviour of aclocal though.
371 - Some testsuite weaknesses and spurious failures have been fixed.
373 - There is initial support for automatic dependency tracking with the
374 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
376 Bugs fixed in 1.12.3:
378 * Long-standing bugs:
380 - Instead of renaming only self-references of files (typically for
381 #lines), ylwrap now also renames references to the other generated
382 files. This fixes support for GLR and C++ parsers from Bison (PR
383 automake/491 and automake bug#7648): 'parser.c' now properly
384 #includes 'parser.h' instead of 'y.tab.h'.
386 - Generated files unknown to ylwrap are now preserved. This fixes
387 C++ support for Bison (automake bug#7648): location.hh and the
388 like are no longer discarded.
390 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
394 * Warnings and deprecations:
396 - Automake now issues a warning (in the 'portability' category) if
397 'configure.in' is used instead of 'configure.ac' as the Autoconf
398 input file. Such a warning will also be present in the next
399 Autoconf version (2.70).
403 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
404 order (as done by the other recursive rules), rather than in the
405 inverse order. They used to do that in order to work a round a
406 limitation in an older implementation of the automatic dependency
407 tracking support, but that limitation had been lifted years ago
408 already, when the automatic dependency tracking based on side-effects
409 of compilation had been introduced.
411 - Cleaning rules for compiled objects (both "plain" and libtool) work
412 better when subdir objects are involved, not triggering a distinct
413 'rm' invocation for each such object. They do so by removing *any*
414 compiled object file that is in the same directory of a subdir
415 object. See automake bug#10697.
417 * Silent rules support:
419 - A new predefined $(AM_V_P) make variable is provided; it expands
420 to a shell conditional that can be used in recipes to know whether
421 make is being run in silent or verbose mode.
423 Bugs fixed in 1.12.2:
425 * SECURITY VULNERABILITIES!
427 - The 'distcheck' recipe no longer grants temporary world-write
428 permissions on the extracted distdir. Even if such rights were
429 only granted for a vanishingly small time window, the implied
430 race condition proved to be enough to allow a local attacker
431 to run arbitrary code with the privileges of the user running
432 "make distcheck". This is CVE-2012-3386.
434 * Long-standing bugs:
436 - The "recheck" targets behaves better in the face of build failures
437 related to previously failed tests. For example, if a test is a
438 compiled program that must be rerun by "make recheck", and its
439 compilation fails, it will still be rerun by further "make recheck"
440 invocations. See automake bug#11791.
442 * Bugs introduced by 1.12.1:
444 - Automake provides once again the '$(mkdir_p)' make variable and the
445 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
446 for better backward-compatibility.
448 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
452 * New supported languages:
454 - Support for Objective C++ has been added; it should work similarly to
455 the support for Objective C.
457 * Deprecated obsolescent features:
459 - Use of the long-deprecated two- and three-arguments invocation forms
460 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
461 category. Starting from some future major Automake release (likely
462 post-1.13), such usages will no longer be allowed.
464 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
465 now deprecated (its use triggers a warning in the 'obsolete' category).
466 It will be removed in the next major Automake release (1.13).
468 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
469 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
470 m4 macro are deprecated, eliciting a warning in the 'obsolete'
473 * Miscellaneous changes:
475 - The Automake test cases now require a proper POSIX-conforming shell.
476 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
477 be accepted. In most cases, the user shouldn't have to specify such
478 POSIX shell explicitly, since it will be looked up at configure time.
479 Still, when this lookup fails, or when the user wants to override its
480 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
481 to the shell that will be used to run the Automake test cases).
483 Bugs fixed in 1.12.1:
485 * Bugs introduced by 1.12:
487 - Several weaknesses in Automake's own build system and test suite
490 * Bugs introduced by 1.11.3:
492 - When given non-option arguments, aclocal rejects them, instead of
493 silently ignoring them.
495 * Long-standing bugs:
497 - When the 'color-tests' option is in use, forcing of colored testsuite
498 output through "AM_COLOR_TESTS=always" works even if the terminal is
499 a non-ANSI one, i.e., if the TERM environment variable has a value of
502 - Several inefficiencies and poor performances in the implementation
503 of the parallel-tests 'check' and 'recheck' targets have been fixed.
505 - The post-processing of output "#line" directives done the ylwrap
506 script is more faithful w.r.t. files in a subdirectory; for example,
507 if the processed file is "src/grammar.y", ylwrap will correctly
508 produce directives like:
509 #line 7 "src/grammar.y"
514 * Bugs with new Perl versions:
516 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
518 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
522 * Obsolete features removed:
524 - The never documented nor truly used script 'acinstall' has been
527 - Support for automatic de-ANSI-fication has been removed.
529 - The support for the "obscure" multilib feature has been removed
530 from Automake core (but remains available in the 'contrib/'
531 directory of the Automake distribution).
533 - Support for ".log -> .html" conversion and the check-html and
534 recheck-html targets has been removed from Automake core (but
535 remains available in the 'contrib/' directory of the Automake
538 - The deprecated 'lzma' compression format for distribution archives
539 has been removed, in favor of 'xz' and 'lzip'.
541 - The obsolete AM_WITH_REGEX macro has been removed.
543 - The long-deprecated options '--output-dir', '--Werror' and
544 '--Wno-error' have been removed.
546 - The chapter on the history of Automake has been moved out of the
547 reference manual, into a new dedicated Texinfo file.
551 - New 'cscope' target to build a cscope database for the source tree.
553 * Changes to Automake-generated testsuite harnesses:
555 - The new automake option 'serial-tests' has been introduced. It can
556 be used to explicitly instruct automake to use the older serial
557 testsuite harness. This is still the default at the moment, but it
558 might change in future versions.
560 - The 'recheck' target (provided by the parallel testsuite harness) now
561 depends on the 'all' target. This allows for a better user-experience
562 in test-driven development. See automake bug#11252.
564 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
565 and unexpected or internal error, or a failure to set up the test case
566 scenario) have their outcome reported as an 'ERROR' now. Previous
567 versions of automake reported such an outcome as a 'FAIL' (the only
568 difference with normal failures being that hard errors were counted
569 as failures even when the test originating them was listed in
572 - The testsuite summary displayed by the parallel-test harness has a
573 completely new format, that always list the numbers of passed, failed,
574 xfailed, xpassed, skipped and errored tests, even when these numbers
575 are zero (but using smart coloring when the color-tests option is in
578 - The default testsuite driver offered by the 'parallel-tests' option is
579 now implemented (partly at least) with the help of automake-provided
580 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
581 on code in the generated Makefile.in.
582 This has two noteworthy implications. The first one is that projects
583 using the 'parallel-tests' option should now either run automake with
584 the '--add-missing' option, or manually copy the 'test-driver' script
585 into their tree. The second, and more important, implication is that
586 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
587 no longer be used to define a test runner, and the command specified
588 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
589 program or script. For example, this is still a valid usage (albeit
592 TESTS_ENVIRONMENT = \
593 if test -n '$(STRICT_TESTS)'; then \
594 maybe_errexit='-e'; \
598 LOG_COMPILER = $(SHELL) $$maybe_errexit
600 OTOH, this is no longer a valid usage:
602 TESTS_ENVIRONMENT = \
603 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
607 TESTS_ENVIRONMENT = \
608 run_with_perl_or_shell () \
610 if grep -q '^#!.*perl' $$1; then
616 LOG_COMPILER = run_with_perl_or_shell
618 - The package authors can now use customary testsuite drivers within
619 the framework provided by the 'parallel-tests' testsuite harness.
620 Consistently with the existing syntax, this can be done by defining
621 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
623 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
624 to redirect/define file descriptors used by the test scripts.
626 - The parallel-tests harness generates now, in addition the '.log' files
627 holding the output produced by the test scripts, a new set of '.trs'
628 files, holding "metadata" derived by the execution of the test scripts;
629 among such metadata are the outcomes of the test cases run by a script.
631 - Initial and still experimental support for the TAP test protocol is
634 * Changes to Yacc and Lex support:
636 - C source and header files derived from non-distributed Yacc and/or
637 Lex sources are now removed by a simple "make clean" (while they were
638 previously removed only by "make maintainer-clean").
640 - Slightly backward-incompatible change, relevant only for use of Yacc
641 with C++: the extensions of the header files produced by the Yacc
642 rules are now modelled after the extension of the corresponding
643 sources. For example, yacc files named "foo.y++" and "bar.yy" will
644 produce header files named "foo.h++" and "bar.hh" respectively, where
645 they would have previously produced header files named simply "foo.h"
646 and "bar.h". This change offers better compatibility with 'bison -o'.
648 * Miscellaneous changes:
650 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
651 rather than 1, if the vala compiler found is too old.
653 - The build system of Automake itself now avoids the use of make
654 recursion as much as possible.
656 - Automake now prefers to quote 'like this' or "like this", rather
657 than `like this', in diagnostic message and generated Makefiles,
658 to accommodate the new GNU Coding Standards recommendations.
660 - Automake has a new option '--print-libdir' that prints the path of the
661 directory containing the Automake-provided scripts and data files.
663 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
665 - The rules to create pdf, dvi and ps output from Texinfo files now
666 works better with modern 'texi2dvi' script, by explicitly passing
667 it the '--clean' option to ensure stray auxiliary files are not
668 left to clutter the build directory.
670 - Automake can now generate silenced rules for texinfo outputs.
672 - Some auxiliary files that are automatically distributed by Automake
673 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
674 C sources) might now be listed in the DIST_COMMON variable in many
675 Makefile.in files, rather than in the top-level one.
677 - Messages of types warning or error from 'automake' and 'aclocal'
678 are now prefixed with the respective type, and presence of -Werror
681 - Automake's early configure-time sanity check now tries to avoid
682 sleeping for a second, which slowed down cached configure runs
683 noticeably. In that case, it will check back at the end of the
684 configure script to ensure that at least one second has passed, to
685 avoid time stamp issues with makefile rules rerunning autotools
688 - The warnings in the category 'extra-portability' are now enabled by
689 '-Wall'. In previous versions, one has to use '-Wextra-portability'
694 - Various minor bugfixes for recent or long-standing bugs.
696 * Bugs introduced by 1.11:
698 - The AM_COND_IF macro also works if the shell expression for the
699 conditional is no longer valid for the condition.
701 - The automake-provided parallel testsuite harness no longer fails
702 with BSD make used in parallel mode when there are test scripts in
703 a subdirectory, like in:
705 TESTS = sub/foo.test sub/bar.test
707 * Long-standing bugs:
709 - Automake's own build system finally have a real "installcheck" target.
711 - Vala-related cleanup rules are now more complete, and work better in
714 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
715 now automatically distributed also if the directory of the auxiliary
716 files coincides with the top-level directory.
718 - Automake now detects the presence of the '-d' flag in the various
719 '*YFLAGS' variables even when their definitions involve indirections
720 through other variables, such as in:
722 AM_YFLAGS = $(foo_opts)
724 - Automake now complains if a '*YFLAGS' variable has any conditional
725 content, not only a conditional definition.
727 - Explicit enabling and/or disabling of Automake warning categories
728 through the '-W...' options now always takes precedence over the
729 implicit warning level implied by Automake strictness (foreign, gnu
730 or gnits), regardless of the order in which such strictness and
731 warning flags appear. For example, a setting like:
732 AUTOMAKE_OPTIONS = -Wall --foreign
733 will cause the warnings in category 'portability' to be enabled, even
734 if those warnings are by default disabled in 'foreign' strictness.
736 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
738 Bugs fixed in 1.11.5:
740 * Bugs introduced by 1.11.3:
742 - Vala files with '.vapi' extension are now recognized and handled
743 correctly again. See automake bug#11222.
745 - Vala support work again for projects that contain some program
746 built from '.vala' (and possibly '.c') sources and some other
747 program built from '.c' sources *only*. See automake bug#11229.
749 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
753 * Miscellaneous changes:
755 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
756 symbol index) modifiers as well as the "s" action, as the symbol index
757 is created unconditionally by Microsoft lib. Also, the "q" (quick)
758 action is now a synonym for "r" (replace). Also, the script has been
759 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
761 - When the 'compile' script is used to wrap MSVC, it now accepts an
762 optional space between the -I, -L and -l options and their respective
763 arguments, for better POSIX compliance.
765 - There is an initial, experimental support for automatic dependency
766 tracking with tcc (the Tiny C Compiler). Its associated depmode is
767 currently recognized as "icc" (but this and other details are likely
768 to change in future versions).
770 - Automatic dependency tracking now works also with the IBM XL C/C++
771 compilers, thanks to the new new depmode 'xlc'.
773 Bugs fixed in 1.11.4:
775 * Bugs introduced by 1.11.2:
777 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
778 no longer cause spurious failures upon "make install".
780 - The user can now instruct the 'uninstall-info' rule not to update
781 the '${infodir}/dir' file by exporting the environment variable
782 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
783 with how the 'install-info' rule operates since automake 1.11.2.
785 * Long-standing bugs:
787 - It is now possible for a foo_SOURCES variable to hold Vala sources
788 together with C header files, as well as with sources and headers for
789 other supported languages (e.g., C++). Previously, only mixing C and
790 Vala sources was supported.
792 - If "aclocal --install" is used, and the first directory specified with
793 '-I' is non-existent, aclocal will now create it before trying to copy
796 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
797 install rules to create an empty $(foodir) directory; for example, if
798 Makefile.am contains something like:
802 pkglibexec_SCRIPTS += bar.sh
805 the $(pkglibexec) directory will not be created upon "make install".
807 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
811 * Miscellaneous changes:
813 - Automake's own build system is more silent by default, making use of
814 the 'silent-rules' option.
816 - The master copy of the 'gnupload' script is now maintained in gnulib,
819 - The 'missing' script no longer tries to wrap calls to 'tar'.
821 - "make dist" no longer wraps 'tar' invocations with the 'missing'
822 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
823 shouldn't be using BTW ;-) no longer invokes the 'missing' script
824 to wrap tar, but simply invokes the 'tar' program itself.
826 - "make dist" can now create lzip-compressed tarballs.
828 - In the Automake info documentation, the Top node and the nodes about
829 the invocation of the automake and aclocal programs have been renamed;
830 now, calling "info automake" will open the Top node, while calling
831 "info automake-invocation" and "info aclocal-invocation" will access
832 the nodes about the invocation of respectively automake and aclocal.
834 - Automake is now distributed as a gzip-compressed and an xz-compressed
835 tarball. Previously, bzip2 was used instead of xz.
837 - The last relics of Python 1.5 support have been removed from the
838 AM_PATH_PYTHON macro.
840 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
841 and adds them to the normal list of dependencies, but without
842 overwriting the foo_DEPENDENCIES variable, which is normally computed
845 Bugs fixed in 1.11.3:
847 * Bugs introduced by 1.11.2:
849 - Automake now correctly recognizes the prefix/primary combination
850 'pkglibexec_SCRIPTS' as valid.
852 - The parallel-tests harness no longer trips on sed implementations
853 with stricter limits on the length of input lines (problem seen at
856 * Long-standing bugs:
858 - The "deleted header file problem" for *.am files is avoided by stub
859 rules. This allows 'make' to trigger a rerun of 'automake' also if
860 some previously needed '.am' file has been removed.
862 - The 'silent-rules' option now generates working makefiles even
863 for the uncommon 'make' implementations that do not support the
864 nested-variables extension to POSIX 2008. For such 'make'
865 implementations, whether a build is silent is determined at
866 configure time, and cannot be overridden at make time with
867 "make V=0" or "make V=1".
869 - Vala support now works better in VPATH setups.
871 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
875 * Changes to aclocal:
877 - The `--acdir' option is deprecated. Now you should use the new options
878 `--automake-acdir' and `--system-acdir' instead.
880 - The `ACLOCAL_PATH' environment variable is now interpreted as a
881 colon-separated list of additional directories to search after the
882 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
883 and before the system acdir (by default ${prefix}/share/aclocal).
885 * Miscellaneous changes:
887 - The Automake support for automatic de-ANSI-fication has been
888 deprecated. It will probably be removed in the next major Automake
891 - The `lzma' compression scheme and associated automake option `dist-lzma'
892 is obsoleted by `xz' and `dist-xz' due to upstream changes.
894 - You may adjust the compression options used in dist-xz and dist-bzip2.
895 The default is now merely -e for xz, but still -9 for bzip; you may
896 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
897 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
899 - The `compile' script now converts some options for MSVC for a better
900 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
902 - The py-compile script now accepts empty arguments passed to the options
903 `--destdir' and `--basedir', and complains about unrecognized options.
904 Moreover, a non-option argument or a special `--' argument terminates
907 - A developer that needs to pass specific flags to configure at "make
908 distcheck" time can now, and indeed is advised to, do so by defining
909 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
910 instead of the old DISTCHECK_CONFIGURE_FLAGS.
911 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
912 user; still, the old Makefile.am files that used to define it will
913 still continue to work as before.
915 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
916 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
917 This new macro is required for LIBRARIES and LTLIBRARIES when automake
918 is run with -Wextra-portability and -Werror.
920 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
921 file generated by automake-provided rules by defining the special make
922 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
924 - The `install-info' rule can now be instructed not to create/update
925 the `${infodir}/dir' file, by exporting the new environment variable
926 `AM_UPDATE_INFO_DIR' to the value "no".
928 Bugs fixed in 1.11.2:
930 * Bugs introduced by 1.11:
932 - The parallel-tests driver no longer produces erroneous results with
933 Tru64/OSF 5.1 sh upon unreadable log files.
935 - The `parallel-tests' test driver does not report spurious successes
936 when used with concurrent FreeBSD make (e.g., "make check -j3").
938 - When the parallel-tests driver is in use, automake now explicitly
939 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
940 instead of issuing confusing and apparently unrelated error messages
941 (e.g., "non-POSIX variable name", "bad characters in variable name",
942 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
943 silently producing broken `Makefile.in' files.
945 - The `silent-rules' option now truly silences all compile rules, even
946 when dependency tracking is disabled. Also, when `silent-rules' is
947 not used, `make' output no longer contains spurious backslash-only
948 lines, thus once again matching what Automake did before 1.11.
950 - The AM_COND_IF macro also works if the shell expression for the
951 conditional is no longer valid for the condition.
953 * Long-standing bugs:
955 - The order of Yacc and Lex flags is fixed to be consistent with other
956 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
957 $(LFLAGS), so that the user variables override the developer variables.
959 - "make distcheck" now correctly complains also when "make uninstall"
960 leaves one and only one file installed in $(prefix).
962 - A "make uninstall" issued before a "make install", or after a mere
963 "make install-data" or a mere "make install-exec" does not spuriously
966 - Automake now warns about more primary/directory invalid combinations,
967 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
969 - Rules generated by Automake now try harder to not change any files when
970 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
971 Yacc source files and the rule to update config.h.
973 - Several scripts and the parallel-tests testsuite driver now exit with
974 the right exit status upon receiving a signal.
976 - A per-Makefile.am setting of -Werror does not erroneously carry over
977 to the handling of other Makefile.am files.
979 - The code for automatic dependency tracking works around a Solaris
980 make bug triggered by sources containing repeated slashes when the
981 `subdir-objects' option was used.
983 - The makedepend and hp depmodes now work better with VPATH builds.
985 - Java sources specified with check_JAVA are no longer compiled for
986 "make all", but only for "make check".
988 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
989 and error out if `javadir' is undefined, instead of silently producing
990 a broken Makefile.in.
992 - aclocal and automake now honour the configure-time definitions of
993 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
995 - The `install-info' recipe no longer tries to guess whether the
996 `install-info' program is from Debian or from GNU, and adaptively
997 change its behaviour; this has proven to be frail and easy to
1000 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1002 Bugs fixed in 1.11.1:
1004 - Lots of minor bugfixes.
1006 * Bugs introduced by 1.11:
1008 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1009 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1011 * Long standing bugs:
1013 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1014 even if the `--prefix' argument pointed outside of a system directory.
1015 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1016 `get_python_lib' function if it points outside the configured prefix,
1017 unless the `--prefix' argument was either `/usr' or below `/System'.
1019 - The testsuite does not try to change the mode of `ltmain.sh' files from
1020 a Libtool installation (symlinked to test directories) any more.
1022 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1023 tools are preferred in a cross-compile setup.
1025 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1026 This fixes a race condition where untrusted users could modify files
1027 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1028 build directory was world-searchable. This is CVE-2009-4029.
1030 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1034 * Version requirements:
1036 - Autoconf 2.62 or greater is required.
1038 * Changes to aclocal:
1040 - The autoconf version check implemented by aclocal in aclocal.m4
1041 (and new in Automake 1.10) is degraded to a warning. This helps
1042 in the common case where the Autoconf versions used are compatible.
1044 * Changes to automake:
1046 - The automake program can run multiple threads for creating most
1047 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1048 with interpreter-based threads enabled. Set the environment variable
1049 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1050 enable this experimental feature.
1052 * Changes to Libtool support:
1054 - Libtool generic flags are now passed to the install and uninstall
1057 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1058 config.lt is removed correctly now.
1060 * Languages changes:
1062 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1063 Fortran, and Ratfor).
1065 - For files with extension .f90, .f95, .f03, or .f08, the flag
1066 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1068 - Files with extension .sx are also treated as preprocessed assembler.
1070 - The default source file extension (.c) can be overridden with
1071 AM_DEFAULT_SOURCE_EXT now.
1073 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1076 - AM_PATH_PYTHON honors python's idea about the site directory.
1078 - There is initial support for the Vala programming language, when using
1079 Vala 0.7.0 or later.
1081 * Miscellaneous changes:
1083 - Automake development is done in a git repository on Savannah now, see
1085 http://git.sv.gnu.org/gitweb/?p=automake.git
1087 A read-only CVS mirror is provided at
1089 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1090 checkout -d automake HEAD
1092 - "make dist" can now create xz-compressed tarballs,
1093 as well as (deprecated?) lzma-compressed tarballs.
1095 - `automake --add-missing' will by default install the GPLv3 file as
1096 COPYING if it is missing. It will also warn that the license file
1097 should be added to source control. Note that Automake will never
1098 overwrite an existing COPYING file, even when the `--force-missing'
1101 - The manual is now distributed under the terms of the GNU FDL 1.3.
1103 - Automake ships and installs man pages for automake and aclocal now.
1105 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1107 - install-sh supports -C, which does not update the installed file
1108 (and its time stamps) if the contents did not change.
1110 - The `gnupload' script has been revamped.
1112 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1114 - The targets `install' and `uninstall' are more efficient now, in that
1115 for example multiple files from one Automake variable such as
1116 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1117 invocation if they do not have to be renamed.
1119 Both install and uninstall may sometimes enter (`cd' into) the target
1120 installation directory now, when no build-local scripts are used.
1122 Both install and uninstall do not fail anymore but do nothing if an
1123 installation directory variable like `bindir' is set to the empty string.
1125 For built-in rules, `make install' now fails reliably if installation
1126 of a file failed. Conversely, `make uninstall' even succeeds when
1127 issued multiple times.
1129 These changes may need some adjustments from users: For example,
1130 some `install' programs refuse to install multiple copies of the
1131 same file in one invocation, so you may need to remove duplicate
1132 entries from file lists.
1134 Also, within one set of files, say, nobase_data_DATA, the order of
1135 installation may be changed, or even unstable among different hosts,
1136 due to the use of associative arrays in awk. The increased use of
1137 awk matches a similar move in Autoconf to provide for better scaling.
1139 Further, most undocumented per-rule install command variables such as
1140 binSCRIPT_INSTALL have been removed because they are not needed any
1141 more. Packages which use them should be using the appropriate one of
1142 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1143 counterpart, depending on the type of files and the need for automatic
1144 target directory creation.
1146 - The "deleted header file problem" for *.m4 files is avoided by
1147 stub rules. This allows `make' to trigger a rerun of `aclocal'
1148 also if some previously needed macro file has been removed.
1150 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1151 an otherwise up to date tree.
1153 - The `color-tests' option causes colored test result output on terminals.
1155 - The `parallel-tests' option enables a new test driver that allows for
1156 parallel test execution, inter-test dependencies, lazy test execution
1157 for unit-testing, re-testing only failed tests, and formatted result output
1158 as RST (reStructuredText) and HTML. Enabling this option may require some
1159 changes to your test suite setup; see the manual for details.
1161 - The `silent-rules' option enables Linux kernel-style silent build output.
1162 This option requires the widely supported but non-POSIX `make' feature
1163 of recursive variable expansion, so do not use it if your package needs
1164 to build with `make' implementations that do not support it.
1166 To enable less verbose build output, the developer has to use the Automake
1167 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1168 macro. The user may then set the default verbosity by passing the
1169 `--enable-silent-rules' option to `configure'. At `make' run time, this
1170 default may be overridden using `make V=0' for less verbose, and `make V=1'
1171 for backward-compatible verbose output.
1173 - New prefix `notrans_' for manpages which should not be transformed
1174 by --program-transform.
1176 - New macro AM_COND_IF for conditional evaluation and conditional
1179 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1180 remove the file in a non-VPATH build. Such setups work with Autoconf
1183 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1184 the default setting.
1186 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1187 useful especially for multi-line values.
1189 - Automake's early configure-time sanity check now diagnoses an
1190 unsafe absolute source directory name and makes configure fail.
1192 - The Automake macros and rules cope better with whitespace in the
1193 current directory name, as long as the relative path to `configure'
1194 does not contain whitespace. To this end, the values of `$(MISSING)'
1195 and `$(install_sh)' may contain suitable quoting, and their expansion
1196 might need `eval'uation if used outside of a makefile. These
1197 undocumented variables may be used in several documented macros such
1198 as $(AUTOCONF) or $(MAKEINFO).
1202 * Long-standing bugs:
1204 - Fix aix dependency tracking for libtool objects.
1206 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1207 unnecessary use of the `compile' script.
1209 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1210 correct `-rpath' argument is used now.
1212 - `config.status --file=Makefile depfiles' now also works with the
1213 extra quoting used internally by Autoconf 2.62 and newer
1214 (it used to work only without the `--file=' bit).
1216 - The `missing' script works better with versioned tool names.
1218 - Semantics for `missing help2man' have been revamped:
1220 Previously, if `help2man' was not present, `missing help2man' would have
1221 the following semantics: if some man page was out of date but present, then
1222 a warning would be printed, but the exit status was 0. If the man page was
1223 not present at all, then `missing' would create a replacement man page
1224 containing an error message, and exit with a status of 2. This does not play
1225 well with `make': the next run will see this particular man page as being up
1226 to date, and will only error out on the next generated man page, if any;
1227 repeat until all pages are done. This was not desirable.
1229 These are the new semantics: if some man page is not present, and help2man
1230 is not either, then `missing' will warn and generate the replacement page
1231 containing the error message, but exit successfully. However, `make dist'
1232 will ensure that no such bogus man pages are packaged into a tarball.
1234 - Targets provided by automake behave better with `make -n', in that they
1235 take care not to create files.
1237 - `config.status Makefile... depfiles' works fine again in the presence of
1238 disabled dependency tracking.
1240 - The default no-op recursive rules for these targets also work with BSD make
1241 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1243 - `make distcheck' works also when both a directory and some file below it
1244 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1246 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1247 `make mostlyclean' any more; only the LaTeX by-products are.
1249 - Renamed objects also work with the `subdir-objects' option and
1250 source file languages which Automake does not know itself.
1252 - `automake' now correctly complains about variable assignments which are
1253 preceded by a comment, extend over multiple lines with backslash-escaped
1254 newlines, and end in a comment sign. Previous versions would silently
1255 and wrongly ignore such assignments completely.
1257 * Bugs introduced by 1.10:
1259 - Fix output of dummy dependency files in presence of post-processed
1260 Makefile.in's again, but also cope with long lines.
1262 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1263 that have been declared as programs in the same Makefile.
1264 This is for consistency with the analogous change to TESTS in 1.10.
1266 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1267 followed by directories containing config headers.
1269 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1273 * Version requirements:
1275 - Autoconf 2.60 or greater is required.
1277 - Perl 5.6 or greater is required.
1279 * Changes to aclocal:
1281 - aclocal now also supports -Wmumble and -Wno-mumble options.
1283 - `dirlist' entries (for the aclocal search path) may use shell
1284 wildcards such as `*', `?', or `[...]'.
1286 - aclocal supports an --install option that will cause system-wide
1287 third-party macros to be installed in the local directory
1288 specified with the first -I flag. This option also uses #serial
1289 lines in M4 files to upgrade local macros.
1291 The new aclocal options --dry-run and --diff help to review changes
1292 before they are installed.
1294 - aclocal now outputs an autoconf version check in aclocal.m4 in
1295 projects using automake.
1297 For a few years, automake and aclocal have been calling autoconf
1298 (or its underlying engine autom4te) to accurately retrieve the
1299 data they need from configure.ac and its siblings. Doing so can
1300 only work if all autotools use the same version of autoconf. For
1301 instance a Makefile.in generated by automake for one version of
1302 autoconf may stop working if configure is regenerated with another
1303 version of autoconf, and vice versa.
1305 This new version check ensures that the whole build system has
1306 been generated using the same autoconf version.
1308 * Support for new Autoconf macros:
1310 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1312 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1313 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1314 in different directories. However, only one instance of such a
1315 library objects directory is supported.
1317 * Change to Libtool support:
1319 - Libtool generic flags (those that go before the --mode=MODE option)
1320 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1322 * Yacc and Lex changes:
1324 - The rebuild rules for distributed Yacc and Lex output will avoid
1325 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1328 - ylwrap is now always used for lex and yacc source files,
1329 regardless of whether there is more than one source per directory.
1331 * Languages changes:
1333 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1334 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1335 tracking, unlike non-preprocessed assembler (*.s).
1337 - subdir-object mode works now with Assembler. Automake assumes
1338 that the compiler understands `-c -o'.
1340 - Preprocessed assembler (*.S) compilation now also honors
1341 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1343 - Improved support for Objective C:
1344 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1345 - A new section of the manual documents the support.
1347 - New support for Unified Parallel C:
1348 - AM_PROG_UPC looks for a UPC compiler.
1349 - A new section of the manual documents the support.
1351 - Per-target flags are now correctly handled in link rules.
1353 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1354 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1355 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1356 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1358 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1359 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1360 is expected to work (and actually works during compilation).
1362 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1363 "in addition to" breaks backward compatibility with older versions.
1364 If your package used both variables, as in
1366 AM_LDFLAGS = common flags
1367 bin_PROGRAMS = a b c
1368 a_LDFLAGS = more flags
1371 and assumed *_LDFLAGS would sum up, you should rewrite it as
1373 AM_LDFLAGS = common flags
1374 bin_PROGRAMS = a b c
1375 a_LDFLAGS = $(AM_LDFLAGS) more flags
1378 This new behavior of *_LDFLAGS is more coherent with other
1379 per-target variables, and the way *_LDFLAGS variables were
1380 considered internally.
1382 * New installation targets:
1384 - New targets mandated by GNU Coding Standards:
1389 By default they will only install Texinfo manuals.
1390 You can customize them with *-local variants:
1396 - The undocumented recursive target `uninstall-info' no longer exists.
1397 (`uninstall' is in charge of removing all possible documentation
1398 flavors, including optional formats such as dvi, ps, or info even
1399 when `no-installinfo' is used.)
1401 * Miscellaneous changes:
1403 - Automake no longer complains if input files for AC_CONFIG_FILES
1404 are specified using shell variables.
1406 - clean, distribution, or rebuild rules are normally disabled for
1407 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1408 AC_CONFIG_LINK specified using shell variables. However, if these
1409 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1410 be able to output rules anyway.
1411 (See the Automake documentation for AC_CONFIG_FILES.)
1413 - $(EXEEXT) is automatically appended to filenames of TESTS
1414 that have been declared as programs in the same Makefile.
1415 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1417 - `-Wportability' has finally been turned on by default for `gnu' and
1418 `gnits' strictness. This means, automake will complain about %-rules
1419 or $(GNU Make functions) unless you switch to `foreign' strictness or
1420 use `-Wno-portability'.
1422 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1423 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1424 $(mkdir_p) variable is still defined (to the same value as
1425 $(MKDIR_P)) but should be considered obsolete. If you are using
1426 $(mkdir_p) in some of your rules, please plan to update them to
1427 $(MKDIR_P) at some point.
1429 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1430 They still work in this release, but may be withdrawn in a future one.
1432 - Inline compilation rules for gcc3-style dependency tracking are
1435 - Automake installs a "Hello World!" example package in $(docdir).
1436 This example is used throughout the new "Autotools Introduction"
1437 chapter of the manual.
1439 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1443 * Makefile.in bloat reduction:
1445 - Inference rules are used to compile sources in subdirectories when
1446 the `subdir-objects' option is used and no per-target flags are
1447 used. This should reduce the size of some projects a lot, because
1448 Automake used to output an explicit rule for each such object in
1451 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1452 object that must be built with explicit rules. It just outputs
1453 the rules required to build the kind of object considered: either
1454 the two .o and .obj rules for usual objects, or the .lo rule for
1457 * Change to Libtool support:
1459 - Libtool tags are used with libtool versions that support them.
1460 (I.e., with Libtool 1.5 or greater.)
1462 - Automake is now able to handle setups where a libtool library is
1463 conditionally installed in different directories, as in
1466 lib_LTLIBRARIES = liba.la
1468 pkglib_LTLIBRARIES = liba.la
1470 liba_la_SOURCES = ...
1472 * Changes to aclocal:
1474 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1475 really evaluated, before it decides to include them in aclocal.m4.
1476 This solves nasty problems with conditional redefinitions of
1477 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1478 *.m4 files to be included in any project using these macros.
1479 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1480 most famous instance of this bug.)
1482 - Do not complain about missing conditionally AC_REQUIREd macros
1483 that are not actually used. In 1.8.x aclocal would correctly
1484 determine which of these macros were really needed (and include
1485 only these in the package); unfortunately it would also require
1486 all of them to be present in order to run. This created
1487 situations were aclocal would not work on a tarball distributing
1488 all the macros it uses. For instance running aclocal on a project
1489 containing only the subset of the Gettext macros in use by the
1490 project did not work, because gettext conditionally requires other
1493 * Portability improvements:
1495 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1496 tar-pax. The new option filename-length-max=99 helps diagnosing
1497 filenames that are too long for tar-v7. (PR/414)
1499 - Variables aumented with `+=' are now automatically flattened (i.e.,
1500 trailing backslashes removed) and then wrapped around 80 colummns
1501 (adding trailing backslashes). In previous versions, a long series
1507 would result in a single-line definition of VAR that could possibly
1508 exceed the maximum line length of some make implementations.
1510 Non-augmented variables are still output as they are defined in
1515 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1516 Works the same as the old Fortran 77 implementation; just replace
1517 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1518 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1520 - Support for conditional _LISP.
1522 - Support for conditional -hook and -local rules (PR/428).
1524 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1526 - Automake will not write any Makefile.ins after the first error it
1527 encounters. The previous Makefile.ins (if any) will be left in
1528 place. (Warnings will not prevent output, but remember they can
1529 be turned into errors with -Werror.)
1531 - The restriction that SUBDIRS must contain direct children is gone.
1534 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1535 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1537 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1539 Bugs fixed in 1.8.5:
1541 * Long-standing bugs:
1543 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1544 so that `make distclean' and `make maintainer-clean' can work.
1546 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1548 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1550 - Polish diagnostic when no input file is found.
1552 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1554 Bugs fixed in 1.8.4:
1556 * Long-standing bugs:
1558 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1559 overridden by the user.
1561 - Honor PATH_SEPARATOR in various places of the Automake package, for
1564 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1567 - Fix install-sh so it can install the `mv' binary... using `mv'.
1569 - Fix tru64 dependency tracking for libtool objects.
1571 - Work around Exuberant Ctags when creating a TAGS files in a directory
1572 without files to scan but with subdirectories to include.
1574 * Bugs introduced by 1.8:
1576 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1577 not defined in the same conditions as the _LDADD that uses it.
1579 - Do not warn when JAVAROOT is overridden, this is legitimate.
1581 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1583 Bugs fixed in 1.8.3:
1585 * Long-standing bugs:
1587 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1588 or any of the other *dir variables contain a space.
1590 Please note that Automake does not and cannot support spaces in
1591 filenames that are involved during the build. This change affects
1592 only installation paths, so that `make install' does not bomb out
1593 in packages configured with
1594 ./configure --prefix '/c/Program Files'
1596 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1597 POSIXLY_CORRECT is set.
1599 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1600 since Autoconf 2.54, which defines LIBOBJS itself.
1602 - Fix a potential (but unlikely) race condition in parallel elisp
1603 builds. (Introduced in 1.7.3.)
1605 - Do not assume that users override _DEPENDENCIES in all conditions
1606 where Automake will try to define them.
1608 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1609 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1612 This fix also affects the $(mkdir_p) variable defined since
1613 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1614 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1616 - Secure temporary directory creation in `make distcheck'. (PR/413)
1618 - Do not generate two build rules for `parser.h' when the
1619 parser appears in two different conditionals.
1621 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1622 checking. Usually ./configure will not pick this shell; so this
1623 fix only helps cases where the shell is forced to /bin/sh.
1625 * Bugs introduced by 1.8:
1627 - In some situations (hand-written `m4_include's), aclocal would
1628 call the `File::Spec->rel2abs' method, which was only introduced
1629 in Perl 5.6. This new version reestablish support Perl 5.005.
1631 It is likely that the next major Automake releases will require at
1632 least Perl 5.6. Consider upgrading your development environment
1633 if you are still using the five-year-old Perl 5.005.
1635 - Automake would sometimes fail to define rules for targets listed
1636 in variables defined in multiple conditions. For instance on
1642 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1643 `b.$(OBJEXT): b.c' rule.
1645 * New sections in manual:
1647 - Third-Party Makefiles: how to interface third party Makefiles.
1648 - Upgrading: upgrading packages to newer Automake versions.
1649 - Multiple Outputs: handling tools that produce many outputs.
1651 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1655 * A (well known) portability bug slipped in the changes made to
1656 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1657 install anything on Tru64.
1659 * Fix install rules for conditionally built python files. (This never
1662 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1666 * Bugs introduced by 1.8:
1668 - Fix Config.pm import error with old Perl versions (at least
1669 5.005_03). One symptom is that aclocal could not find its macro
1672 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1673 created by `make install' are always world readable, even if the
1674 installer happens to have an overly restrictive umask (e.g. 077).
1675 This was a mistake and has been reverted. There are at least two
1676 reasons why we must not use `-m 0755':
1677 - it causes special bits like SGID to be ignored,
1678 - it may be too restrictive (some setups expect 775 directories).
1680 - Fix aclocal to honor definitions located in files which have been
1681 m4_included manually. aclocal 1.8 had been updated to check
1682 m4_included files for new requirements, but forgot that these
1683 m4_included files can also provide new definitions.
1685 Note that if you have such a setup, we recommend you get rid of
1686 it. In the past, there was a reason to m4_include files manually:
1687 aclocal used to duplicate entire M4 files into aclocal.m4, even
1688 files that were distributed. Some packages were therefore
1689 m4_including the distributed file directly, and playing some
1690 tricks to ensure aclocal would not copy that file to aclocal.m4,
1691 in order to limit the amount of duplication. Since aclocal 1.8.x
1692 will precisely output m4_includes for local M4 files, we recommend
1693 that you clean up your setup, removing all manual m4_includes and
1694 letting aclocal output them.
1696 - Output detailed menus in the Info version if the Automake manual,
1697 so that Emacs can locate the indexes.
1699 - configure.ac and configure were listed twice in DIST_COMMON (an
1700 internal variable where Automake lists configury files to
1701 distribute). This was harmless, but unaesthetic.
1703 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1704 This was an issue only in the Automake package itself, not in
1707 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1708 DEST:SRC. This was wrong, as some packages do
1709 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1712 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1713 argument. This caused two kinds of failures:
1714 - Rules installing data in a conditionally defined directory
1715 failed when that directory was undefined. In this case no
1716 argument was supplied.
1717 - `make installdirs' failed, because several directories were
1718 passed to $(mkdir_p). This was an issue only on platform
1719 were $(mkdir_p) is implemented with `install-sh -d'.
1720 $(mkdir_p) as been changed to accept 0 or more arguments, as
1723 * Long-standing bugs:
1725 - Fix an unexpected diagnostic occurring when users attempt
1726 to override some internal variables that Automake appends to.
1728 - aclocal now scans configure.ac for macro definitions (PR/319).
1730 - Fix a portability issue with OSF1/Tru64 Make. If a directory
1731 distributes files which are outside itself (this usually occurs
1732 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
1733 from a parent package), then `make distcheck' fails due to an
1734 optimization performed by OSF1/Tru64 Make in its VPATH handling.
1735 (tests/subpkg2.test failure)
1737 - Fix another portability issue with Sun and OSF1/Tru64 Make.
1738 In a VPATH-build configuration, `make install' would install
1739 nobase_ files to wrong locations.
1741 - Fix a Perl `uninitialized value' diagnostic occurring when
1742 automake complains that a Texinfo file does not have a
1743 @setfilename statement.
1745 - Erase config.status.lineno during `make distclean'. This file
1746 can be created by config.status. Automake already knew about
1747 configure.lineno, but forgot config.status.lineno.
1749 - Distribute all files, even those which are built and installed
1750 conditionally. This change affects files listed in conditionally
1751 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
1752 as well as those listed in conditionally defined dist_*_DATA,
1753 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
1755 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
1756 doesn't conform to POSIX.
1758 - Normalize help strings for configure variables and options added
1763 - Check for python2.4 in AM_PATH_PYTHON.
1765 * Spurious failures in test suite:
1767 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
1768 tests/ltconv.test: fix failures with CVS Libtool.
1769 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
1770 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
1771 fix failures with old Texinfo versions.
1773 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1779 - The NEWS file is more verbose.
1783 - Autoconf 2.58 or greater is required.
1787 - Default source file names in the absence of a _SOURCES declaration
1788 are made by removing any target extension before appending `.c', so
1789 to make the libtool module `foo.la' from `foo.c', you only need to
1792 lib_LTLIBRARIES = foo.la
1793 foo_la_LDFLAGS = -module
1795 For backward compatibility, foo_la.c will be used instead of
1796 foo.c if this file exists or is the explicit target of a rule.
1797 However -Wobsolete will warn about this deprecated naming.
1799 - AR's `cru' flags are now set in a global ARFLAGS variable instead
1800 of being hard-coded in each $(AR) invocation, so they can be
1801 substituted from configure.ac. This has been requested by people
1802 dealing with non-POSIX ar implementations.
1804 - New warning option: -Woverride. This will warn about any user
1805 target or variable definitions which override Automake
1808 - Texinfo rules back up and restore info files when makeinfo fails.
1810 - Texinfo rules now support the `html' target.
1811 Running this requires Texinfo 4.0 or greater.
1813 `html' is a new recursive target, so if your package mixes
1814 hand-crafted `Makefile.in's with Automake-generated
1815 `Makefile.in's, you should adjust the former to support (or
1816 ignore) this target so that `make html' recurses successfully. If
1817 you had a custom `html' rule in your `Makefile.am', it's better to
1818 rename it as `html-local', otherwise your rule will override
1819 Automake's new rule (you can check that by running `automake
1820 -Woverride') and that will stop the recursion to subdirectories.
1822 Last but not least, this `html' rule is declared PHONY, even when
1823 overridden. Fortunately, it appears that few packages use a
1824 non-PHONY `html' rule.
1826 - Any file which is m4_included from configure.ac will appear as a
1827 configure and Makefile.in dependency, and will be automatically
1830 - The rules for rebuilding Makefiles and Makefile.ins will now
1831 rebuild all Makefiles and all Makefile.ins at once when one of
1832 configure's dependencies has changed. This is considerably faster
1833 than previous implementations, where config.status and automake
1834 were run separately in each directory (this still happens when you
1835 change a Makefile.am locally, without touching configure.ac or
1836 friends). Doing this also solves a longstanding issue: these
1837 rebuild rules failed to work when adding new directories to the
1838 tree, forcing you to run automake manually.
1840 - For similar reasons, the rules to rebuild configure,
1841 config.status, and aclocal.m4 are now defined in all directories.
1842 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
1843 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
1844 should better define them in all directories. This is easily done
1845 using an AC_SUBST (make sure you prefix these dependencies with
1846 $(top_srcdir) since this variable will appear at different
1847 levels of the build tree).
1849 - aclocal will now use `m4_include' instead of copying local m4
1850 files into aclocal.m4. (Local m4 files are those you ship with
1851 your project, other files will be copied as usual.)
1853 Because m4_included files are automatically distributed, it means
1854 for most projects there is no point in EXTRA_DISTing the list of
1855 m4 files which are used. (You can probably get rid of
1856 m4/Makefile.am if you had one.)
1858 - aclocal will avoid touching aclocal.m4 when possible, so that
1859 Autom4te's cache isn't needlessly invalidated. This behavior can
1860 be switched off with the new `--force' option.
1862 - aclocal now uses Autoconf's --trace to detect macros which are
1863 actually used and will no longer include unused macros simply
1864 because they where mentioned. This was often the case for macros
1865 called conditionally.
1867 - New options no-dist and no-dist-gzip.
1869 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
1870 py-compile, and ylwrap, now all understand --version and --help.
1872 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
1873 links as part of the distclean target and including source files in
1876 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
1877 argument. The latter can be used to override the default behavior
1878 (which is to abort).
1880 - Automake will exit with $? = 63 on version mismatch. (So does
1881 Autoconf 2.58) missing knows this, and in this case it will
1882 emulate the tools as if they were absent. Because older versions
1883 of Automake and Autoconf did not use this exit code, this change
1884 will only be useful in projects generated with future versions of
1887 - When using AC_CONFIG_FILES with multiple input files, Automake
1888 generates the first ".in" input file for which a ".am" exists.
1889 (Former versions would try to use only the first input file.)
1891 - lisp_DATA is now allowed. If you are using the empty ELCFILES
1892 idiom to disable byte-compilation of lisp_LISP files, it is
1893 recommended that you switch to using lisp_DATA. Note that
1894 this is not strictly equivalent: lisp_DATA will install elisp
1895 files even if emacs is not installed, while *_LISP do not
1896 install anything unless emacs is found.
1898 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
1899 available. This selection is achieved through the Makefile
1900 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
1901 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
1902 `$(install_sh) -m 0755 -d'.
1906 - Because `mkdir -p' is available on most platforms, and we can use
1907 `install-sh -d' when it is not, the use of the mkinstalldirs
1908 script is being phased out. `automake --add-missing' no longer
1909 installs it, and if you remove mkinstalldirs from your package,
1910 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
1912 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
1913 gettextize and autopoint will install it when needed. Automake
1914 will continue to define the $(mkinstalldirs) and to distribute
1915 mkinstalldirs when this script is in the source tree.
1917 - AM_PROG_CC_STDC is now empty. The content of this macro was
1918 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
1919 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
1920 renaming should be safe, even if you have to support several,
1921 versions of Automake, because AC_PROG_CC defines this variable
1922 since Autoconf 2.54.)
1924 - Some users where using the undocumented ACLOCAL_M4_SOURCES
1925 variable to override the aclocal.m4 dependencies computed
1926 (inaccurately) by older versions of Automake. Because Automake
1927 now tracks configure's m4 dependencies accurately (see m4_include
1928 above), the use of ACLOCAL_M4_SOURCES should be considered
1929 obsolete and will be flagged as such when running `automake
1934 - Defining programs conditionally using Automake conditionals no
1935 longer leads to a combinatorial explosion. The following
1936 construct used to be troublesome when used with dozens of
1951 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
1953 - Due to implementation constraints, previous versions of Automake
1954 proscribed multiple conditional definitions of some variables
1964 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
1965 This restriction has been lifted, and these variables now
1966 support multiple conditional definitions as do other variables.
1968 - Cleanup the definitions of $(distdir) and $(top_distdir).
1969 $(top_distdir) now points to the root of the distribution
1970 directory created during `make dist', as it did in Automake 1.4,
1971 not to the root of the build tree as it did in intervening
1972 versions. Furthermore these two variables are now only defined in
1973 the top level Makefile, and passed to sub-directories when running
1976 - The --no-force option now correctly checks the Makefile.in's
1977 dependencies before deciding not to update it.
1979 - Do not assume that make files are called Makefile in cleaning rules.
1981 - Update .info files in the source tree, not in the build tree. This
1982 is what the GNU Coding Standard recommend. Only Automake 1.7.x
1983 used to update these files in the build tree (previous versions did
1984 it in the source tree too), and it caused several problems, varying
1985 from mere annoyance to portability issues.
1987 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
1988 when --add-missing and --force-missing are used. For backward
1989 compatibility --add-missing will continue to install COPYING (in
1990 `gnu' strictness) when none of these three files exist, but this
1991 use is deprecated: you should better choose a license yourself and
1992 install it once for all in your source tree (and in your code
1995 - Fix ylwrap so that it does not overwrite header files that haven't
1996 changed, as the inline rule already does.
1998 - User-defined rules override automake-defined rules for the same
1999 targets, even when rules do not have commands. This is not new
2000 (and was documented), however some of the automake-generated
2001 rules have escaped this principle in former Automake versions.
2002 Rules for the following targets are affected by this fix:
2004 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2005 info, info-am, install-data-am, install-exec-am, install-info,
2006 install-info-am, install-man, installcheck-am, maintainer-clean,
2007 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2008 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2010 Practically it means that an attempt to supplement the dependencies
2011 of some target, as in
2013 clean: my-clean-rule
2015 will now *silently override* the automake definition of the
2016 rule for this target. Running `automake -Woverride' will diagnose
2017 all such overriding definitions.
2019 It should be noted that almost all of these targets support a *-local
2020 variant that is meant to supplement the automake-defined rule
2021 (See node `Extending' in the manual). The above rule should
2024 clean-local: my-clean-rule
2026 These *-local targets have been documented since at least
2027 Automake 1.2, so you should not fear the change if you have
2028 to support multiple automake versions.
2032 - The Automake manual is now distributed under the terms of the GNU FDL.
2034 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2036 - core dumps are no longer removed by the cleaning rules. There are
2037 at least three reasons for this:
2038 1. These files should not be created by any build step,
2039 so their removal do not fit any of the cleaning rules.
2040 Actually, they may be precious to the developer.
2041 2. If such file is created during a build, then it's clearly a
2042 bug Automake should not hide. Not removing the file will
2043 cause `make distcheck' to complain about its presence.
2044 3. Operating systems have different naming conventions for
2045 core dump files. A core file on one system might be a
2046 completely legitimate data file on another system.
2048 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2049 defined by Automake. This means that any definition in the
2050 environment will be used, unless overridden in the Makefile.am or
2051 on the command line. The old behavior, where these variables were
2052 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2053 AC_ARG_VARing each variable from configure.ac.
2055 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2056 documented. (The is not a new feature, these variables have
2057 been there since at least Automake 1.4.)
2059 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2061 Bugs fixed in 1.7.9:
2062 * Fix install-strip to work with nobase_ binaries.
2063 * Fix renaming of #line directives in ylwrap.
2064 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2066 Bugs fixed in 1.7.8:
2067 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2068 * Fix detection of Debian's install-info, broken since version 1.5.
2069 (Debian bug #213524).
2070 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2071 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2073 Bugs fixed in 1.7.7:
2074 * The implementation of automake's --no-force option is unreliable,
2075 so this option is ignored in this version. A real fix will appear in
2076 Automake 1.8. (Debian Bug #206299)
2077 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2078 argument is given. (PR/399)
2079 * Do not warn about leading `_' in variable names, even with -Wportability.
2080 * Support user redefinitions of TEXINFO_TEX.
2081 * depcomp: support AIX Compiler version 6.
2082 * Fix missing rebuilds during `make dist' with BSD make.
2083 (Could produce tarballs containing out-of-date files.)
2084 * Resurrect multilib support.
2085 * Noteworthy manual updates:
2086 - Extending aclocal: how to write m4 macros that won't trigger warnings
2088 - A Shared Library: Rewrite and split into subsections.
2090 Bugs fixed in 1.7.6:
2091 * Fix depcomp's icc mode for ICC 7.1.
2092 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2093 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2094 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2095 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2096 * Remove Latin-1 characters from elisp-comp.
2097 * Update the manual's @dircategory to match the Free Software Directory.
2099 Bugs fixed in 1.7.5:
2100 * Update install-sh's license to remove an advertising clause.
2101 (Debian bug #191717)
2102 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2103 that caused invalid Makefile.ins to be generated.
2104 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2105 * New FAQ entry: renamed objects.
2107 Bugs fixed in 1.7.4:
2108 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2109 the Emacs implementation)
2110 * Fix output of aclocal.m4 dependencies in subdirectories.
2111 * Use `mv -f' instead of `mv' in fastdep rules.
2112 * Upgrade mdate-sh to work on OS/2.
2113 * Don't byte-compile elisp files when ELCFILES is set empty.
2114 (this documented feature was broken by 1.7.3)
2115 * Diagnose trailing backslashes on last line of Makefile.am.
2116 * Diagnose whitespace following trailing backslashes.
2117 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2118 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2120 * `make install' will build `BUILT_SOURCES' first.
2121 * Minor documentation fixes.
2123 Bugs fixed in 1.7.3:
2124 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2125 * Query distutils for `pythondir' and `pythonexecdir', instead of
2126 using an hardcoded path. This should allow builds on 64-bit
2127 distributions that usually use lib64/ instead of lib/.
2128 * AM_PATH_PYTHON will also search for python2.3.
2129 * elisp files are now built all at once instead of one by one. Besides
2130 incurring a speed-up, this is required to support interdependent elisp files.
2131 * Support for DJGPP:
2132 - `make distcheck' will now work in `_inst/' and `_build' instead
2133 of `=inst/' and `=build/'
2134 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2135 - install/uninstall `*.i[0-9][0-9]'-style info files
2136 - more changes that affect only the Automake package (not its output)
2137 * Fix some incompatibilities with upcoming perl-5.10.
2138 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2139 PACKAGE and VERSION.
2141 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2142 is troublesome with gcc and Solaris compilers. (PR/385)
2143 - makedepend mode: work with Libtool. (PR/385 too)
2145 * better support for unusual gettext setups, such as multiple po/ directories
2147 - Flag missing po/ and intl/ directories as warnings, not errors.
2148 - Disable these warnings if po/ does not exist.
2149 * Noteworthy manual updates:
2151 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2153 - Document `AM_YFLAGS = -d'. (PR/382)
2155 Bugs fixed in 1.7.2:
2156 * Fix installation and uninstallation of Info files built in subdirectories.
2157 * Do not run `./configure --with-included-gettext' during `make distcheck'
2158 if AM_GNU_GETTEXT([external]) is used.
2159 * Correctly uninstall renamed man pages.
2160 * Do not strip escaped newline in variables defined in one condition
2161 and augmented in another condition.
2162 * Fix ansi2knr rules for LIBOBJS sources.
2163 * Clean all known Texinfo index files, not only those which appear to
2164 be used, because we cannot know which indexes are used in included files.
2165 (PR/375, Debian Bug #168671)
2166 * Honor only the first @setfilename seen in a Texinfo file.
2167 * Treat "required file X not found" diagnostics as errors (exit status 1).
2168 * Don't complain that a required file is not found when it is a Makefile
2170 * Don't use single suffix inference rules when building `.info'-less
2171 Info files, for the sake of Solaris make.
2172 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2173 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2174 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2175 * Fix building of deansified files from subdirectories. (PR/370)
2176 * Add missing `fi' in the .c->.obj rules.
2177 * Improve install-sh to work even when names contain spaces or certain
2178 (but not all) shell metachars.
2179 * Fix the following spurious failures in the test suite:
2180 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2181 * Noteworthy manual updates:
2182 - Augment the section about BUILT_SOURCES.
2183 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2185 Bugs fixed in 1.7.1:
2186 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2188 * Aclocal should now recognize macro names containing parentheses, e.g.
2189 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2190 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2192 * Install Python files even if they were built. (PR/369)
2193 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2194 version might not be defined in the latter. (PR/358)
2195 * Reorder arguments passed to a couple of commands, so things works
2196 when POSIXLY_CORRECT=1.
2197 * Fix a regex that can cause Perl to segfault on large input.
2199 * Fix distribution of packages that have some sources defined conditionally,
2200 as in the `Conditional compilation using Automake conditionals' example
2202 * Fix spurious test suite failures on IRIX.
2203 * Don't report a required variable as undefined if it has been
2204 defined conditionally for the "right" conditions.
2205 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2206 `make distcheck' fails.
2207 * Fix distribution of included Makefile fragment, so we don't create
2208 spurious directories in the distribution. (PR/366)
2209 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2212 * Autoconf 2.54 is required.
2213 * `aclocal' and `automake' will no longer warn about obsolete
2214 configure macros. This is done by `autoconf -Wobsolete'.
2215 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2216 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2217 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2218 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2219 `configure.ac' for you.
2220 * Support for per-program and per-library `_CPPFLAGS'.
2221 * New `ctags' target (builds CTAGS files).
2222 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2223 (see `automake --help' or the manual for a list of them).
2224 * Honor the WARNINGS environment variable.
2225 * Omit the call to depcomp when using gcc3: call the compiler directly.
2226 * A new option, std-options, tests that programs support --help and --version
2227 when `make installcheck' is run. This is enabled by --gnits.
2228 * Texinfo rules now support the `ps' and `pdf' targets.
2229 * Info files are now created in the build directory, not the source directory.
2230 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2232 * `make distcheck' will enforce DESTDIR support by attempting
2234 * `+=' can be used in conditionals, even if the augmented variable
2235 was defined for another condition.
2236 * Makefile fragments (inserted with `include') are always distributed.
2237 * Use Autoconf's --trace interface to inspect configure.ac and get
2238 a more accurate view of it.
2239 * Add support for extending aclocal's default macro search path
2240 using a `dirlist' file within the aclocal directory.
2241 * automake --output-dir is deprecated.
2242 * The part of the distcheck target that checks whether uninstall actually
2243 removes all installed files has been moved in a separate target,
2244 distuninstallcheck, so it can be overridden easily.
2248 * Support for AM_INIT_GETTEXT([external])
2249 * Bug fixes, including:
2250 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2251 - nobase_ programs and scripts honor --program-transform correctly.
2252 - Erase configure.lineno during `make distclean'.
2253 - Erase YACC and LEX outputs during `make maintainer-clean'.
2256 * Many bug fixes, including:
2257 - Requiring the current version works.
2258 - Fix "$@" portability issues (for Zsh).
2259 - Fix output of dummy dependency files in presence of post-processed
2261 - Don't compute dependencies in background to avoid races with libtool.
2262 - Fix handling of _OBJECTS variables for targets sharing source variables.
2263 - Check dependency mode for Java when AM_PROG_GCJ is used.
2266 * automake --output-dir is deprecated
2267 * Many bug fixes, including:
2268 - Don't choke on AM_LDFLAGS definitions.
2269 - Clean libtool objects from subdirectories.
2270 - Allow configure variables with reserved suffix and unknown prefix
2271 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2272 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2275 * Autoconf 2.52 is required.
2276 * automake no longer run libtoolize.
2277 This is the job of autoreconf (from GNU Autoconf).
2278 * `dist' generates all the archive flavors, as did `dist-all'.
2279 * `dist-gzip' generates the Gzip tar file only.
2280 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2281 explosion. Makefile.in's keep a reasonable size.
2282 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2283 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2285 * `#line' of Lex and Yacc files are properly set.
2286 * EXTRA_DIST can contain generated directories.
2287 * Support for dot-less extensions in suffix rules.
2288 * The part of the distcheck target that checks whether distclean actually
2289 cleans all built files has been moved in a separate target, distcleancheck,
2290 so it can be overridden easily.
2291 * `make distcheck' will pass additional options defined in
2292 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2293 * Fixed CDPATH portability problems, in particular for MacOS X.
2294 * Fixed handling of nobase_ targets.
2295 * Fixed support of implicit rules leading to .lo objects.
2296 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2297 * Added uninstall-hook target
2298 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2299 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2300 (Note that "pkgname" is not "tarname", see the manual for details.)
2301 It is also possible to pass a list of global Automake options as
2302 first argument to this new form of AM_INIT_AUTOMAKE.
2303 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2304 to be a real assembler.
2305 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2306 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2307 * aclocal and automake are also installed with the version number
2308 appended, and some of the install directory names have changed.
2309 This lets you have multiple versions installed simultaneously.
2310 * Support for parsers and lexers in subdirectories.
2313 * Support for `configure.ac'.
2314 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2315 * `make dist-all' is much faster.
2316 * Allows '@' AC_SUBSTs in macro names.
2317 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2318 * User-side dependency tracking. Developers no longer need GNU make
2320 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2321 * Most files are correctly handled if they appear in subdirs
2322 For instance, a _DATA file can appear in a subdir
2323 * GNU tar is no longer required for `make dist'
2324 * Added support for `dist_' and `nodist_' prefixes
2325 * Added support for `nobase_' prefix
2326 * Compiled Java support
2327 * Support for per-executable and per-library compilation flags
2331 * Added support for the Fortran 77 programming language.
2332 * Re-indexed the Automake Texinfo manual.
2333 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2334 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2335 * Support for latest autoconf, including support for objext
2336 * Can now put `.' in SUBDIRS to control build order
2337 * `include' command and `+=' support for macro assignment
2338 * Dependency tracking no long susceptible to deleted header file problem
2339 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2344 * Better Cygwin32 support
2345 * Support for suffix rules with _SOURCES variables
2346 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2347 * @LEXLIB@ no longer required when lex source seen
2348 Lex support in `missing', and new lex macro. Update your missing script.
2349 * Built-in support for assembly
2350 * aclocal gives error if `AM_' macro not found
2351 * Passed YFLAGS, not YACCFLAGS, to yacc
2352 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2353 * Dependencies computed as a side effect of compilation
2354 * Preliminary support for Java
2355 * DESTDIR support at "make install" time
2356 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2360 * Better DejaGnu support
2361 * Added no-installinfo option
2362 * Added Emacs Lisp support
2363 * Added --no-force option
2364 * Included `aclocal' program
2365 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2366 * Now uses `AM_' macro names everywhere
2367 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2368 ansi2knr now works correctly on K&R sources
2369 * Better C++, yacc, lex support
2370 * Will compute _DEPENDENCIES variables automatically if not supplied
2371 * Will interpolate $(...) and ${...} when examining contents of a variable
2372 * .deps files now in build directory, not source directory; dependency
2373 handling generally rewritten
2374 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2375 * can now put config.h into a subdir
2376 * Added dist-all target
2377 * Support for install-info program (see texinfo 3.9)
2378 * Support for "yacc -d"
2379 * configure substitutions are automatically discovered and included
2380 in generated Makefile.in
2381 * Special --cygnus mode
2382 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2383 when making distribution. Some dependencies are auto-ignored.
2384 * Changed how libraries are specified in _LIBRARIES variable
2385 * Full libtool support, from Gord Matzigkeit
2386 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2387 AM_CONFIG_HEADER handles it automatically
2388 * Texinfo output files no longer need .info extension
2389 * Added `missing' support
2391 * Conditionals in Makefile.am, from Ian Taylor
2395 * distcheck target runs install and installcheck targets
2396 * Added preliminary support for DejaGnu.
2401 * More libtool fixes from Gord Matzigkeit; libtool support is still
2403 * Added support for jm_MAINTAINER_MODE
2405 * New "distcheck" target
2409 * mkinstalldirs and mdate-sh now appear in directory specified by
2411 * Removed DIST_SUBDIRS, DIST_OTHER
2412 * AC_ARG_PROGRAM only required when an actual program exists
2413 * dist-hook target now run before distribution packaged up; idea from
2414 Dieter Baron. Other hooks exist, too.
2415 * Preliminary (unfinished) support for libtool
2416 * Added short option names.
2417 * Better "dist" support when gluing together multiple packages
2421 * Documentation updates (many from François Pinard)
2422 * strictness `normal' now renamed to `foreign'
2423 * Renamed --install-missing to --add-missing
2424 * Now handles AC_CONFIG_AUX_DIR
2425 * Now handles TESTS macro
2426 * DIST_OTHER renamed to EXTRA_DIST
2427 * DIST_SUBDIRS is deprecated
2428 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2429 * Better error messages in many cases
2430 * Program names are canonicalized
2431 * Added "check" prefix; from Gord Matzigkeit
2435 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2436 * Beginnings of a test suite
2437 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2438 * Doesn't print anything when running
2439 * Beginnings of MAINT_CHARSET support
2440 * Can specify version in AUTOMAKE_OPTIONS
2441 * Most errors recognizable by Emacs' M-x next-error
2442 * Added --verbose option
2443 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2444 configure-generated names
2445 * Required macros now distributed in aclocal.m4
2447 * --strictness=gnu is default
2451 * More sophisticated configure.in scanning; now understands ALLOCA and
2452 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2453 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2454 * CONFIG_HEADER variable now obsolete
2455 * Can handle multiple Texinfo sources
2456 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2457 * HEADERS variable no longer needed; now can put .h files directly into
2458 foo_SOURCES variable.
2459 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2460 corresponding ".in" files are included in the distribution.
2463 * Added --gnu and --gnits options
2464 * More standards checking
2466 * Cleaned up 'dist' targets
2467 * Added AUTOMAKE_OPTIONS variable and several options
2468 * Now scans configure.in to get some information (preliminary)
2471 * Works with Perl 4 again
2474 * Added --install-missing option.
2475 * Pretty-prints generated macros and rules
2476 * Comments in Makefile.am are placed more intelligently in Makefile.in
2477 * Generates .PHONY target
2478 * Rule or macro in Makefile.am now overrides contents of Automake file
2479 * Substantial cleanups from François Pinard
2483 * Works with Perl 4 again.
2486 * New uniform naming scheme.
2487 * --strictness option
2489 * '.c' files corresponding to '.y' or '.l' files are automatically
2491 * Many bug fixes and cleanups
2494 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2497 * Bug fixes in 'clean' code.
2498 * Now generates 'installdirs' target.
2499 * man page installation reworked.
2500 * 'make dist' no longer re-creates all Makefile.in's.
2503 * Reimplemented in Perl
2504 * Added --amdir option (for debugging)
2505 * Texinfo support cleaned up.
2506 * Automatic de-ANSI-fication cleaned up.
2507 * Cleaned up 'clean' targets.
2510 * Automatic dependency tracking
2511 * More documentation
2512 * New variables DATA and PACKAGEDATA
2513 * SCRIPTS installed using $(INSTALL_SCRIPT)
2514 * No longer uses double-colon rules
2516 * Changes in advance of internationalization
2520 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2522 This program is free software; you can redistribute it and/or modify
2523 it under the terms of the GNU General Public License as published by
2524 the Free Software Foundation; either version 2, or (at your option)
2527 This program is distributed in the hope that it will be useful,
2528 but WITHOUT ANY WARRANTY; without even the implied warranty of
2529 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2530 GNU General Public License for more details.
2532 You should have received a copy of the GNU General Public License
2533 along with this program. If not, see <http://www.gnu.org/licenses/>.
projects / platform / upstream / automake.git / blob