3 * WARNING: Future backward-incompatibilities!
5 - Automake 1.14 will likely require Autoconf 2.70 or later (which is
6 still unreleased at the moment of writing, but is planned to be
7 released before Automake 1.14 is).
9 - Automake 1.14 will likely drop support for the long-deprecated
10 'configure.in' name for the Autoconf input file. You are advised
11 to use the recommended name 'configure.ac' instead.
13 - The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will
14 be removed in Automake 1.14. The $(mkdir_p) make variable and the
15 @mkdir_p@ substitution will still remain available (as aliases of
16 $(MKDIR_P)) for the moment, for better backward compatibility; but
17 you are advised to stop using ASAP.
19 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated
20 in Automake 1.14 (where it will raise warnings in the "obsolete"
21 category). You are advised to start relying on the new Automake
22 support for AC_CONFIG_MACRO_DIRS instead (which is introduced with
23 this release; see below for more information).
25 - Support for IRIX and the SGI C/C++ compilers will be removed in
26 Automake 1.14: they have seen their last release in 2006, and SGI
27 is expected to retire support from them in December 2013; see
28 <http://www.sgi.com/services/support/irix_mips_support.html> for
31 - Future versions of Automake might remove support for MS-DOS and
32 Windows 95/98/ME (support for them was offered by relying on the
33 DJGPP project). Note however that both Cygwin and MSYS/MinGW on
34 modern Windows versions will continue to be fully supported.
36 - Support for the long-deprecated INCLUDES variable will be removed
37 altogether in Automake 1.14. The AM_CPPFLAGS variable should be
40 - Automake-provided scripts and makefile recipes might (finally!)
41 start assuming a POSIX shell in Automake 1.14.
43 - Starting from Automake 1.14, third-party m4 files located in the
44 system-wide aclocal directory, as well as in any directory listed
45 in the ACLOCAL_PATH environment variable, will take precedence
46 over "built-in" Automake macros. For example (assuming Automake
47 is installed in the /usr/local hierarchy), a definition of the
48 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
49 should take precedence over the same-named automake-provided macro
50 (defined in '/usr/local/share/aclocal-1.14/vala.m4').
52 * Version requirements:
54 - Autoconf 2.65 or greater is now required.
56 - The rules to build PDF and DVI output from Texinfo input now
57 require Texinfo 4.9 or later.
61 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
62 option) has been removed. See discussion about automake bug#11034
63 for more background: <debbugs.gnu.org/11034>.
65 - The deprecated aclocal option '--acdir' has been removed. You
66 should use the options '--automake-acdir' and '--system-acdir'
67 instead (which have been introduced in Automake 1.11.2).
69 - The following long-obsolete m4 macros have been removed:
71 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
72 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
73 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
74 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
75 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
76 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
77 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
78 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
79 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
80 of the now-removed automatic de-ANSI-fication
83 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
85 - Use of the long-deprecated two- and three-arguments invocation forms
86 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
87 though (albeit with a warning in the 'obsolete' category), to cater
88 for people who want to define the version number for their package
89 dynamically (e.g., from the current VCS revision). We'll have to
90 continue this support until Autoconf itself is fixed to allow better
91 support for such dynamic version numbers.
93 * Elisp byte-compilation:
95 - The byte compilation of '.el' files into '.elc' files is now done
96 with a suffix rule. This has simplified the compilation process, and
97 more importantly made it less brittle. The downside is that emacs is
98 now invoked once for each '.el' files, which cause some noticeable
99 slowdowns. These should however be mitigated on multicore machines
100 (which are becoming the norm today) if concurrent make ("make -j")
103 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
104 files in the same subdirectory; for example, byte-compiling of file
105 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
106 'foo.elc'. This behaviour is backward-incompatible with older
107 Automake versions, but it is more natural and more sane. See also
110 - The Emacs invocation performing byte-compilation of '.el' files honors
111 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
112 one is developer-reserved and the latter one user-reserved.
114 - The 'elisp-comp' script, once provided by Automake, has been rendered
115 obsoleted by the just-described changes, and thus removed.
117 * Changes to Automake-generated testsuite harnesses:
119 - The parallel testsuite harness (previously only enabled by the
120 'parallel-tests' option) is the default one; the older serial
121 testsuite harness will still be available through the use of the
122 'serial-tests' option (introduced in Automake 1.12).
124 - The 'color-tests' option is now unconditionally activated by default.
125 In particular, this means that testsuite output is now colorized by
126 default if the attached terminal seems to support ANSI escapes, and
127 that the user can force output colorization by setting the variable
128 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
129 for backward-compatibility, although it's a handled as a no-op now.
131 * Silent rules support:
133 - Support for silent rules is now always active in Automake-generated
134 Makefiles. So, although the verbose output is still the default,
135 the user can now always use "./configure --enable-silent-rules" or
136 "make V=0" to enable quieter output in the package he's building.
138 - The 'silent-rules' option has now become a no-op, preserved for
139 backward-compatibility only. In particular, its use no longer
140 disables the warnings in the 'portability-recursive' category.
144 - The rules to build PDF and DVI files from Texinfo input now require
145 Texinfo 4.9 or later.
147 - The rules to build PDF and DVI files from Texinfo input now use the
148 '--build-dir' option, to keep the auxiliary files used by texi2dvi
149 and texi2pdf around without cluttering the build directory, and to
150 make it possible to run the "dvi" and "pdf" recipes in parallel.
152 * Automatic remake rules and 'missing' script:
154 - The 'missing' script no longer tries to update the timestamp of
155 out-of-date files that require a maintainer-specific tool to be
156 remade, in case the user lacks such a tool (or has a too-old version
157 of it). It just gives a useful warning, and in some cases also a
158 tip about how to obtain such a tool.
160 - The missing script has thus become useless as a (poor) way to work
161 around the sketched-timestamps issues that can happen for projects
162 that keep generated files committed in their VCS repository. Such
163 projects are now encouraged to write a custom "fix-timestamps.sh"
164 script to avoid such issues; a simple example is provided in the
165 "CVS and generated files" chapter of the automake manual.
169 - The user can now define his own recursive targets that recurse
170 in the directories specified in $(SUBDIRS). This can be done by
171 specifying the name of such targets in invocations of the new
172 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
176 - Any failure in the recipe of the "tags", "ctags", "cscope" or
177 "cscopelist" targets in a subdirectory is now propagated to the
178 top-level make invocation.
180 - Tags are correctly computed also for files in _SOURCES variables that
181 only list files with non-standard suffixes (see automake bug#12372).
183 * Improvements to aclocal and related rebuilds rules:
185 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
186 are now traced by aclocal, and can be used to declare the local m4
187 include directories. Formerly, one had to specify it with an explicit
188 '-I' option to the 'aclocal' invocation.
190 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
191 Automake versions will warn about its use, and later version will
192 remove support for it altogether.
194 * The depcomp script:
196 - Dropped support for libtool 1.4.
198 - Various internal refactorings. They should cause no visible change,
199 but the chance for regression is there anyway, so please report any
200 unexpected or suspicious behaviour.
202 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
203 This should cause no problem, since icc 8.0 has been released in
204 December 2003 -- almost nine years ago.
206 - Support for tcc (the Tiny C Compiler) has been improved, and is now
207 handled through a dedicated 'tcc' mode.
209 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
211 Bugs fixed in 1.12.6:
213 * Python-related bugs:
215 - The default installation location for python modules has been improved
216 for Python 3 on Debian and Ubuntu systems, changing from:
218 ${prefix}/lib/python3/dist-packages
222 ${prefix}/lib/python3.x/site-packages
224 This change should ensure modules installed using the default ${prefix}
225 "/usr/local" are found by default by system python 3.x installations.
226 See automake bug#10227.
228 - Python byte-compilation supports the new layout mandated by PEP-3147,
229 with its __pycache__ directory (automake bug#8847).
231 * Build system issues:
233 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
234 Automake's own build system works correctly again (bug introduced
239 - The Vala-related tests has been changed to adjust to the removal of
240 the 'posix' profile in the valac compiler. See automake bug#12934
243 - Some spurious testsuite failures related to older tools and systems
246 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
252 - The AM_PROG_VALAC macro has been enhanced to takes two further
253 optional arguments; it's signature now being
255 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
256 [ACTION-IF-NOT-FOUND])
258 - By default, AM_PROG_VALAC no longer aborts the configure invocation
259 if the Vala compiler found is too old, but simply prints a warning
260 messages (as it did when the Vala compiler was not found). This
261 should avoid unnecessary difficulties for end users that just want
262 to compile the unmodified, distributed Vala-generated C sources,
263 but happens to have an old Vala compiler in their PATH. This fixes
266 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
267 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
268 This is a better default, because with it a triggered makefile rule
269 invoking a Vala compilation will clearly fail with an informative error
270 message like "valac: command not found", rather than silently, with
271 the error possibly going unnoticed or triggering harder-to-diagnose
272 fallout failures in later steps.
274 * Miscellaneous changes:
276 - automake and aclocal no longer honours the 'perllibdir' environment
277 variable. That had always been intended only as an hack required in
278 the testsuite, not meant for any use beyond that.
280 Bugs fixed in 1.12.5:
282 * Long-standing bugs:
284 - Automake no longer generates spurious remake rules invoking autoheader
285 to regenerate the template corresponding to header files specified after
286 the first one in AC_CONFIG_HEADERS (automake bug#12495).
288 - When wrapping Microsoft tools, the 'compile' script falls back to
289 finding classic 'libname.a' style libraries when 'name.lib' and
290 'name.dll.lib' aren't available.
292 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
296 * Warnings and deprecations:
298 - Warnings in the 'obsolete' category are enabled by default both in
299 automake and aclocal.
301 * Miscellaneous changes:
303 - Some testsuite weaknesses and spurious failures have been fixed.
305 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
309 * Miscellaneous changes:
311 - The '.m4' files provided by Automake no longer define serial numbers.
312 This should cause no difference in the behaviour of aclocal though.
314 - Some testsuite weaknesses and spurious failures have been fixed.
316 - There is initial support for automatic dependency tracking with the
317 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
319 Bugs fixed in 1.12.3:
321 * Long-standing bugs:
323 - Instead of renaming only self-references of files (typically for
324 #lines), ylwrap now also renames references to the other generated
325 files. This fixes support for GLR and C++ parsers from Bison (PR
326 automake/491 and automake bug#7648): 'parser.c' now properly
327 #includes 'parser.h' instead of 'y.tab.h'.
329 - Generated files unknown to ylwrap are now preserved. This fixes
330 C++ support for Bison (automake bug#7648): location.hh and the
331 like are no longer discarded.
333 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
337 * Warnings and deprecations:
339 - Automake now issues a warning (in the 'portability' category) if
340 'configure.in' is used instead of 'configure.ac' as the Autoconf
341 input file. Such a warning will also be present in the next
342 Autoconf version (2.70).
346 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
347 order (as done by the other recursive rules), rather than in the
348 inverse order. They used to do that in order to work a round a
349 limitation in an older implementation of the automatic dependency
350 tracking support, but that limitation had been lifted years ago
351 already, when the automatic dependency tracking based on side-effects
352 of compilation had been introduced.
354 - Cleaning rules for compiled objects (both "plain" and libtool) work
355 better when subdir objects are involved, not triggering a distinct
356 'rm' invocation for each such object. They do so by removing *any*
357 compiled object file that is in the same directory of a subdir
358 object. See automake bug#10697.
360 * Silent rules support:
362 - A new predefined $(AM_V_P) make variable is provided; it expands
363 to a shell conditional that can be used in recipes to know whether
364 make is being run in silent or verbose mode.
366 Bugs fixed in 1.12.2:
368 * SECURITY VULNERABILITIES!
370 - The 'distcheck' recipe no longer grants temporary world-write
371 permissions on the extracted distdir. Even if such rights were
372 only granted for a vanishingly small time window, the implied
373 race condition proved to be enough to allow a local attacker
374 to run arbitrary code with the privileges of the user running
375 "make distcheck". This is CVE-2012-3386.
377 * Long-standing bugs:
379 - The "recheck" targets behaves better in the face of build failures
380 related to previously failed tests. For example, if a test is a
381 compiled program that must be rerun by "make recheck", and its
382 compilation fails, it will still be rerun by further "make recheck"
383 invocations. See automake bug#11791.
385 * Bugs introduced by 1.12.1:
387 - Automake provides once again the '$(mkdir_p)' make variable and the
388 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
389 for better backward-compatibility.
391 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
395 * New supported languages:
397 - Support for Objective C++ has been added; it should work similarly to
398 the support for Objective C.
400 * Deprecated obsolescent features:
402 - Use of the long-deprecated two- and three-arguments invocation forms
403 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
404 category. Starting from some future major Automake release (likely
405 post-1.13), such usages will no longer be allowed.
407 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
408 now deprecated (its use triggers a warning in the 'obsolete' category).
409 It will be removed in the next major Automake release (1.13).
411 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
412 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
413 m4 macro are deprecated, eliciting a warning in the 'obsolete'
416 * Miscellaneous changes:
418 - The Automake test cases now require a proper POSIX-conforming shell.
419 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
420 be accepted. In most cases, the user shouldn't have to specify such
421 POSIX shell explicitly, since it will be looked up at configure time.
422 Still, when this lookup fails, or when the user wants to override its
423 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
424 to the shell that will be used to run the Automake test cases).
426 Bugs fixed in 1.12.1:
428 * Bugs introduced by 1.12:
430 - Several weaknesses in Automake's own build system and test suite
433 * Bugs introduced by 1.11.3:
435 - When given non-option arguments, aclocal rejects them, instead of
436 silently ignoring them.
438 * Long-standing bugs:
440 - When the 'color-tests' option is in use, forcing of colored testsuite
441 output through "AM_COLOR_TESTS=always" works even if the terminal is
442 a non-ANSI one, i.e., if the TERM environment variable has a value of
445 - Several inefficiencies and poor performances in the implementation
446 of the parallel-tests 'check' and 'recheck' targets have been fixed.
448 - The post-processing of output "#line" directives done the ylwrap
449 script is more faithful w.r.t. files in a subdirectory; for example,
450 if the processed file is "src/grammar.y", ylwrap will correctly
451 produce directives like:
452 #line 7 "src/grammar.y"
457 * Bugs with new Perl versions:
459 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
461 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
465 * Obsolete features removed:
467 - The never documented nor truly used script 'acinstall' has been
470 - Support for automatic de-ANSI-fication has been removed.
472 - The support for the "obscure" multilib feature has been removed
473 from Automake core (but remains available in the 'contrib/'
474 directory of the Automake distribution).
476 - Support for ".log -> .html" conversion and the check-html and
477 recheck-html targets has been removed from Automake core (but
478 remains available in the 'contrib/' directory of the Automake
481 - The deprecated 'lzma' compression format for distribution archives
482 has been removed, in favor of 'xz' and 'lzip'.
484 - The obsolete AM_WITH_REGEX macro has been removed.
486 - The long-deprecated options '--output-dir', '--Werror' and
487 '--Wno-error' have been removed.
489 - The chapter on the history of Automake has been moved out of the
490 reference manual, into a new dedicated Texinfo file.
494 - New 'cscope' target to build a cscope database for the source tree.
496 * Changes to Automake-generated testsuite harnesses:
498 - The new automake option 'serial-tests' has been introduced. It can
499 be used to explicitly instruct automake to use the older serial
500 testsuite harness. This is still the default at the moment, but it
501 might change in future versions.
503 - The 'recheck' target (provided by the parallel testsuite harness) now
504 depends on the 'all' target. This allows for a better user-experience
505 in test-driven development. See automake bug#11252.
507 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
508 and unexpected or internal error, or a failure to set up the test case
509 scenario) have their outcome reported as an 'ERROR' now. Previous
510 versions of automake reported such an outcome as a 'FAIL' (the only
511 difference with normal failures being that hard errors were counted
512 as failures even when the test originating them was listed in
515 - The testsuite summary displayed by the parallel-test harness has a
516 completely new format, that always list the numbers of passed, failed,
517 xfailed, xpassed, skipped and errored tests, even when these numbers
518 are zero (but using smart coloring when the color-tests option is in
521 - The default testsuite driver offered by the 'parallel-tests' option is
522 now implemented (partly at least) with the help of automake-provided
523 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
524 on code in the generated Makefile.in.
525 This has two noteworthy implications. The first one is that projects
526 using the 'parallel-tests' option should now either run automake with
527 the '--add-missing' option, or manually copy the 'test-driver' script
528 into their tree. The second, and more important, implication is that
529 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
530 no longer be used to define a test runner, and the command specified
531 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
532 program or script. For example, this is still a valid usage (albeit
535 TESTS_ENVIRONMENT = \
536 if test -n '$(STRICT_TESTS)'; then \
537 maybe_errexit='-e'; \
541 LOG_COMPILER = $(SHELL) $$maybe_errexit
543 OTOH, this is no longer a valid usage:
545 TESTS_ENVIRONMENT = \
546 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
550 TESTS_ENVIRONMENT = \
551 run_with_perl_or_shell () \
553 if grep -q '^#!.*perl' $$1; then
559 LOG_COMPILER = run_with_perl_or_shell
561 - The package authors can now use customary testsuite drivers within
562 the framework provided by the 'parallel-tests' testsuite harness.
563 Consistently with the existing syntax, this can be done by defining
564 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
566 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
567 to redirect/define file descriptors used by the test scripts.
569 - The parallel-tests harness generates now, in addition the '.log' files
570 holding the output produced by the test scripts, a new set of '.trs'
571 files, holding "metadata" derived by the execution of the test scripts;
572 among such metadata are the outcomes of the test cases run by a script.
574 - Initial and still experimental support for the TAP test protocol is
577 * Changes to Yacc and Lex support:
579 - C source and header files derived from non-distributed Yacc and/or
580 Lex sources are now removed by a simple "make clean" (while they were
581 previously removed only by "make maintainer-clean").
583 - Slightly backward-incompatible change, relevant only for use of Yacc
584 with C++: the extensions of the header files produced by the Yacc
585 rules are now modelled after the extension of the corresponding
586 sources. For example, yacc files named "foo.y++" and "bar.yy" will
587 produce header files named "foo.h++" and "bar.hh" respectively, where
588 they would have previously produced header files named simply "foo.h"
589 and "bar.h". This change offers better compatibility with 'bison -o'.
591 * Miscellaneous changes:
593 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
594 rather than 1, if the vala compiler found is too old.
596 - The build system of Automake itself now avoids the use of make
597 recursion as much as possible.
599 - Automake now prefers to quote 'like this' or "like this", rather
600 than `like this', in diagnostic message and generated Makefiles,
601 to accommodate the new GNU Coding Standards recommendations.
603 - Automake has a new option '--print-libdir' that prints the path of the
604 directory containing the Automake-provided scripts and data files.
606 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
608 - The rules to create pdf, dvi and ps output from Texinfo files now
609 works better with modern 'texi2dvi' script, by explicitly passing
610 it the '--clean' option to ensure stray auxiliary files are not
611 left to clutter the build directory.
613 - Automake can now generate silenced rules for texinfo outputs.
615 - Some auxiliary files that are automatically distributed by Automake
616 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
617 C sources) might now be listed in the DIST_COMMON variable in many
618 Makefile.in files, rather than in the top-level one.
620 - Messages of types warning or error from 'automake' and 'aclocal'
621 are now prefixed with the respective type, and presence of -Werror
624 - Automake's early configure-time sanity check now tries to avoid
625 sleeping for a second, which slowed down cached configure runs
626 noticeably. In that case, it will check back at the end of the
627 configure script to ensure that at least one second has passed, to
628 avoid time stamp issues with makefile rules rerunning autotools
631 - The warnings in the category 'extra-portability' are now enabled by
632 '-Wall'. In previous versions, one has to use '-Wextra-portability'
637 - Various minor bugfixes for recent or long-standing bugs.
639 * Bugs introduced by 1.11:
641 - The AM_COND_IF macro also works if the shell expression for the
642 conditional is no longer valid for the condition.
644 - The automake-provided parallel testsuite harness no longer fails
645 with BSD make used in parallel mode when there are test scripts in
646 a subdirectory, like in:
648 TESTS = sub/foo.test sub/bar.test
650 * Long-standing bugs:
652 - Automake's own build system finally have a real "installcheck" target.
654 - Vala-related cleanup rules are now more complete, and work better in
657 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
658 now automatically distributed also if the directory of the auxiliary
659 files coincides with the top-level directory.
661 - Automake now detects the presence of the '-d' flag in the various
662 '*YFLAGS' variables even when their definitions involve indirections
663 through other variables, such as in:
665 AM_YFLAGS = $(foo_opts)
667 - Automake now complains if a '*YFLAGS' variable has any conditional
668 content, not only a conditional definition.
670 - Explicit enabling and/or disabling of Automake warning categories
671 through the '-W...' options now always takes precedence over the
672 implicit warning level implied by Automake strictness (foreign, gnu
673 or gnits), regardless of the order in which such strictness and
674 warning flags appear. For example, a setting like:
675 AUTOMAKE_OPTIONS = -Wall --foreign
676 will cause the warnings in category 'portability' to be enabled, even
677 if those warnings are by default disabled in 'foreign' strictness.
679 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
681 Bugs fixed in 1.11.5:
683 * Bugs introduced by 1.11.3:
685 - Vala files with '.vapi' extension are now recognized and handled
686 correctly again. See automake bug#11222.
688 - Vala support work again for projects that contain some program
689 built from '.vala' (and possibly '.c') sources and some other
690 program built from '.c' sources *only*. See automake bug#11229.
692 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
696 * Miscellaneous changes:
698 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
699 symbol index) modifiers as well as the "s" action, as the symbol index
700 is created unconditionally by Microsoft lib. Also, the "q" (quick)
701 action is now a synonym for "r" (replace). Also, the script has been
702 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
704 - When the 'compile' script is used to wrap MSVC, it now accepts an
705 optional space between the -I, -L and -l options and their respective
706 arguments, for better POSIX compliance.
708 - There is an initial, experimental support for automatic dependency
709 tracking with tcc (the Tiny C Compiler). Its associated depmode is
710 currently recognized as "icc" (but this and other details are likely
711 to change in future versions).
713 - Automatic dependency tracking now works also with the IBM XL C/C++
714 compilers, thanks to the new new depmode 'xlc'.
716 Bugs fixed in 1.11.4:
718 * Bugs introduced by 1.11.2:
720 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
721 no longer cause spurious failures upon "make install".
723 - The user can now instruct the 'uninstall-info' rule not to update
724 the '${infodir}/dir' file by exporting the environment variable
725 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
726 with how the 'install-info' rule operates since automake 1.11.2.
728 * Long-standing bugs:
730 - It is now possible for a foo_SOURCES variable to hold Vala sources
731 together with C header files, as well as with sources and headers for
732 other supported languages (e.g., C++). Previously, only mixing C and
733 Vala sources was supported.
735 - If "aclocal --install" is used, and the first directory specified with
736 '-I' is non-existent, aclocal will now create it before trying to copy
739 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
740 install rules to create an empty $(foodir) directory; for example, if
741 Makefile.am contains something like:
745 pkglibexec_SCRIPTS += bar.sh
748 the $(pkglibexec) directory will not be created upon "make install".
750 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
754 * Miscellaneous changes:
756 - Automake's own build system is more silent by default, making use of
757 the 'silent-rules' option.
759 - The master copy of the 'gnupload' script is now maintained in gnulib,
762 - The 'missing' script no longer tries to wrap calls to 'tar'.
764 - "make dist" no longer wraps 'tar' invocations with the 'missing'
765 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
766 shouldn't be using BTW ;-) no longer invokes the 'missing' script
767 to wrap tar, but simply invokes the 'tar' program itself.
769 - "make dist" can now create lzip-compressed tarballs.
771 - In the Automake info documentation, the Top node and the nodes about
772 the invocation of the automake and aclocal programs have been renamed;
773 now, calling "info automake" will open the Top node, while calling
774 "info automake-invocation" and "info aclocal-invocation" will access
775 the nodes about the invocation of respectively automake and aclocal.
777 - Automake is now distributed as a gzip-compressed and an xz-compressed
778 tarball. Previously, bzip2 was used instead of xz.
780 - The last relics of Python 1.5 support have been removed from the
781 AM_PATH_PYTHON macro.
783 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
784 and adds them to the normal list of dependencies, but without
785 overwriting the foo_DEPENDENCIES variable, which is normally computed
788 Bugs fixed in 1.11.3:
790 * Bugs introduced by 1.11.2:
792 - Automake now correctly recognizes the prefix/primary combination
793 'pkglibexec_SCRIPTS' as valid.
795 - The parallel-tests harness no longer trips on sed implementations
796 with stricter limits on the length of input lines (problem seen at
799 * Long-standing bugs:
801 - The "deleted header file problem" for *.am files is avoided by stub
802 rules. This allows 'make' to trigger a rerun of 'automake' also if
803 some previously needed '.am' file has been removed.
805 - The 'silent-rules' option now generates working makefiles even
806 for the uncommon 'make' implementations that do not support the
807 nested-variables extension to POSIX 2008. For such 'make'
808 implementations, whether a build is silent is determined at
809 configure time, and cannot be overridden at make time with
810 "make V=0" or "make V=1".
812 - Vala support now works better in VPATH setups.
814 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
818 * Changes to aclocal:
820 - The `--acdir' option is deprecated. Now you should use the new options
821 `--automake-acdir' and `--system-acdir' instead.
823 - The `ACLOCAL_PATH' environment variable is now interpreted as a
824 colon-separated list of additional directories to search after the
825 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
826 and before the system acdir (by default ${prefix}/share/aclocal).
828 * Miscellaneous changes:
830 - The Automake support for automatic de-ANSI-fication has been
831 deprecated. It will probably be removed in the next major Automake
834 - The `lzma' compression scheme and associated automake option `dist-lzma'
835 is obsoleted by `xz' and `dist-xz' due to upstream changes.
837 - You may adjust the compression options used in dist-xz and dist-bzip2.
838 The default is now merely -e for xz, but still -9 for bzip; you may
839 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
840 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
842 - The `compile' script now converts some options for MSVC for a better
843 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
845 - The py-compile script now accepts empty arguments passed to the options
846 `--destdir' and `--basedir', and complains about unrecognized options.
847 Moreover, a non-option argument or a special `--' argument terminates
850 - A developer that needs to pass specific flags to configure at "make
851 distcheck" time can now, and indeed is advised to, do so by defining
852 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
853 instead of the old DISTCHECK_CONFIGURE_FLAGS.
854 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
855 user; still, the old Makefile.am files that used to define it will
856 still continue to work as before.
858 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
859 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
860 This new macro is required for LIBRARIES and LTLIBRARIES when automake
861 is run with -Wextra-portability and -Werror.
863 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
864 file generated by automake-provided rules by defining the special make
865 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
867 - The `install-info' rule can now be instructed not to create/update
868 the `${infodir}/dir' file, by exporting the new environment variable
869 `AM_UPDATE_INFO_DIR' to the value "no".
871 Bugs fixed in 1.11.2:
873 * Bugs introduced by 1.11:
875 - The parallel-tests driver no longer produces erroneous results with
876 Tru64/OSF 5.1 sh upon unreadable log files.
878 - The `parallel-tests' test driver does not report spurious successes
879 when used with concurrent FreeBSD make (e.g., "make check -j3").
881 - When the parallel-tests driver is in use, automake now explicitly
882 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
883 instead of issuing confusing and apparently unrelated error messages
884 (e.g., "non-POSIX variable name", "bad characters in variable name",
885 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
886 silently producing broken `Makefile.in' files.
888 - The `silent-rules' option now truly silences all compile rules, even
889 when dependency tracking is disabled. Also, when `silent-rules' is
890 not used, `make' output no longer contains spurious backslash-only
891 lines, thus once again matching what Automake did before 1.11.
893 - The AM_COND_IF macro also works if the shell expression for the
894 conditional is no longer valid for the condition.
896 * Long-standing bugs:
898 - The order of Yacc and Lex flags is fixed to be consistent with other
899 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
900 $(LFLAGS), so that the user variables override the developer variables.
902 - "make distcheck" now correctly complains also when "make uninstall"
903 leaves one and only one file installed in $(prefix).
905 - A "make uninstall" issued before a "make install", or after a mere
906 "make install-data" or a mere "make install-exec" does not spuriously
909 - Automake now warns about more primary/directory invalid combinations,
910 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
912 - Rules generated by Automake now try harder to not change any files when
913 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
914 Yacc source files and the rule to update config.h.
916 - Several scripts and the parallel-tests testsuite driver now exit with
917 the right exit status upon receiving a signal.
919 - A per-Makefile.am setting of -Werror does not erroneously carry over
920 to the handling of other Makefile.am files.
922 - The code for automatic dependency tracking works around a Solaris
923 make bug triggered by sources containing repeated slashes when the
924 `subdir-objects' option was used.
926 - The makedepend and hp depmodes now work better with VPATH builds.
928 - Java sources specified with check_JAVA are no longer compiled for
929 "make all", but only for "make check".
931 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
932 and error out if `javadir' is undefined, instead of silently producing
933 a broken Makefile.in.
935 - aclocal and automake now honour the configure-time definitions of
936 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
938 - The `install-info' recipe no longer tries to guess whether the
939 `install-info' program is from Debian or from GNU, and adaptively
940 change its behaviour; this has proven to be frail and easy to
943 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
945 Bugs fixed in 1.11.1:
947 - Lots of minor bugfixes.
949 * Bugs introduced by 1.11:
951 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
952 trailing white space in the test list (`TESTS = foo $(EMPTY)').
954 * Long standing bugs:
956 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
957 even if the `--prefix' argument pointed outside of a system directory.
958 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
959 `get_python_lib' function if it points outside the configured prefix,
960 unless the `--prefix' argument was either `/usr' or below `/System'.
962 - The testsuite does not try to change the mode of `ltmain.sh' files from
963 a Libtool installation (symlinked to test directories) any more.
965 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
966 tools are preferred in a cross-compile setup.
968 - The distribution is tarred up with mode 755 now by the `dist*' targets.
969 This fixes a race condition where untrusted users could modify files
970 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
971 build directory was world-searchable. This is CVE-2009-4029.
973 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
977 * Version requirements:
979 - Autoconf 2.62 or greater is required.
981 * Changes to aclocal:
983 - The autoconf version check implemented by aclocal in aclocal.m4
984 (and new in Automake 1.10) is degraded to a warning. This helps
985 in the common case where the Autoconf versions used are compatible.
987 * Changes to automake:
989 - The automake program can run multiple threads for creating most
990 Makefile.in files concurrently, if at least Perl 5.7.2 is available
991 with interpreter-based threads enabled. Set the environment variable
992 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
993 enable this experimental feature.
995 * Changes to Libtool support:
997 - Libtool generic flags are now passed to the install and uninstall
1000 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1001 config.lt is removed correctly now.
1003 * Languages changes:
1005 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1006 Fortran, and Ratfor).
1008 - For files with extension .f90, .f95, .f03, or .f08, the flag
1009 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1011 - Files with extension .sx are also treated as preprocessed assembler.
1013 - The default source file extension (.c) can be overridden with
1014 AM_DEFAULT_SOURCE_EXT now.
1016 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1019 - AM_PATH_PYTHON honors python's idea about the site directory.
1021 - There is initial support for the Vala programming language, when using
1022 Vala 0.7.0 or later.
1024 * Miscellaneous changes:
1026 - Automake development is done in a git repository on Savannah now, see
1028 http://git.sv.gnu.org/gitweb/?p=automake.git
1030 A read-only CVS mirror is provided at
1032 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1033 checkout -d automake HEAD
1035 - "make dist" can now create xz-compressed tarballs,
1036 as well as (deprecated?) lzma-compressed tarballs.
1038 - `automake --add-missing' will by default install the GPLv3 file as
1039 COPYING if it is missing. It will also warn that the license file
1040 should be added to source control. Note that Automake will never
1041 overwrite an existing COPYING file, even when the `--force-missing'
1044 - The manual is now distributed under the terms of the GNU FDL 1.3.
1046 - Automake ships and installs man pages for automake and aclocal now.
1048 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1050 - install-sh supports -C, which does not update the installed file
1051 (and its time stamps) if the contents did not change.
1053 - The `gnupload' script has been revamped.
1055 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1057 - The targets `install' and `uninstall' are more efficient now, in that
1058 for example multiple files from one Automake variable such as
1059 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1060 invocation if they do not have to be renamed.
1062 Both install and uninstall may sometimes enter (`cd' into) the target
1063 installation directory now, when no build-local scripts are used.
1065 Both install and uninstall do not fail anymore but do nothing if an
1066 installation directory variable like `bindir' is set to the empty string.
1068 For built-in rules, `make install' now fails reliably if installation
1069 of a file failed. Conversely, `make uninstall' even succeeds when
1070 issued multiple times.
1072 These changes may need some adjustments from users: For example,
1073 some `install' programs refuse to install multiple copies of the
1074 same file in one invocation, so you may need to remove duplicate
1075 entries from file lists.
1077 Also, within one set of files, say, nobase_data_DATA, the order of
1078 installation may be changed, or even unstable among different hosts,
1079 due to the use of associative arrays in awk. The increased use of
1080 awk matches a similar move in Autoconf to provide for better scaling.
1082 Further, most undocumented per-rule install command variables such as
1083 binSCRIPT_INSTALL have been removed because they are not needed any
1084 more. Packages which use them should be using the appropriate one of
1085 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1086 counterpart, depending on the type of files and the need for automatic
1087 target directory creation.
1089 - The "deleted header file problem" for *.m4 files is avoided by
1090 stub rules. This allows `make' to trigger a rerun of `aclocal'
1091 also if some previously needed macro file has been removed.
1093 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1094 an otherwise up to date tree.
1096 - The `color-tests' option causes colored test result output on terminals.
1098 - The `parallel-tests' option enables a new test driver that allows for
1099 parallel test execution, inter-test dependencies, lazy test execution
1100 for unit-testing, re-testing only failed tests, and formatted result output
1101 as RST (reStructuredText) and HTML. Enabling this option may require some
1102 changes to your test suite setup; see the manual for details.
1104 - The `silent-rules' option enables Linux kernel-style silent build output.
1105 This option requires the widely supported but non-POSIX `make' feature
1106 of recursive variable expansion, so do not use it if your package needs
1107 to build with `make' implementations that do not support it.
1109 To enable less verbose build output, the developer has to use the Automake
1110 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1111 macro. The user may then set the default verbosity by passing the
1112 `--enable-silent-rules' option to `configure'. At `make' run time, this
1113 default may be overridden using `make V=0' for less verbose, and `make V=1'
1114 for backward-compatible verbose output.
1116 - New prefix `notrans_' for manpages which should not be transformed
1117 by --program-transform.
1119 - New macro AM_COND_IF for conditional evaluation and conditional
1122 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1123 remove the file in a non-VPATH build. Such setups work with Autoconf
1126 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1127 the default setting.
1129 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1130 useful especially for multi-line values.
1132 - Automake's early configure-time sanity check now diagnoses an
1133 unsafe absolute source directory name and makes configure fail.
1135 - The Automake macros and rules cope better with whitespace in the
1136 current directory name, as long as the relative path to `configure'
1137 does not contain whitespace. To this end, the values of `$(MISSING)'
1138 and `$(install_sh)' may contain suitable quoting, and their expansion
1139 might need `eval'uation if used outside of a makefile. These
1140 undocumented variables may be used in several documented macros such
1141 as $(AUTOCONF) or $(MAKEINFO).
1145 * Long-standing bugs:
1147 - Fix aix dependency tracking for libtool objects.
1149 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1150 unnecessary use of the `compile' script.
1152 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1153 correct `-rpath' argument is used now.
1155 - `config.status --file=Makefile depfiles' now also works with the
1156 extra quoting used internally by Autoconf 2.62 and newer
1157 (it used to work only without the `--file=' bit).
1159 - The `missing' script works better with versioned tool names.
1161 - Semantics for `missing help2man' have been revamped:
1163 Previously, if `help2man' was not present, `missing help2man' would have
1164 the following semantics: if some man page was out of date but present, then
1165 a warning would be printed, but the exit status was 0. If the man page was
1166 not present at all, then `missing' would create a replacement man page
1167 containing an error message, and exit with a status of 2. This does not play
1168 well with `make': the next run will see this particular man page as being up
1169 to date, and will only error out on the next generated man page, if any;
1170 repeat until all pages are done. This was not desirable.
1172 These are the new semantics: if some man page is not present, and help2man
1173 is not either, then `missing' will warn and generate the replacement page
1174 containing the error message, but exit successfully. However, `make dist'
1175 will ensure that no such bogus man pages are packaged into a tarball.
1177 - Targets provided by automake behave better with `make -n', in that they
1178 take care not to create files.
1180 - `config.status Makefile... depfiles' works fine again in the presence of
1181 disabled dependency tracking.
1183 - The default no-op recursive rules for these targets also work with BSD make
1184 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1186 - `make distcheck' works also when both a directory and some file below it
1187 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1189 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1190 `make mostlyclean' any more; only the LaTeX by-products are.
1192 - Renamed objects also work with the `subdir-objects' option and
1193 source file languages which Automake does not know itself.
1195 - `automake' now correctly complains about variable assignments which are
1196 preceded by a comment, extend over multiple lines with backslash-escaped
1197 newlines, and end in a comment sign. Previous versions would silently
1198 and wrongly ignore such assignments completely.
1200 * Bugs introduced by 1.10:
1202 - Fix output of dummy dependency files in presence of post-processed
1203 Makefile.in's again, but also cope with long lines.
1205 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1206 that have been declared as programs in the same Makefile.
1207 This is for consistency with the analogous change to TESTS in 1.10.
1209 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1210 followed by directories containing config headers.
1212 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1216 * Version requirements:
1218 - Autoconf 2.60 or greater is required.
1220 - Perl 5.6 or greater is required.
1222 * Changes to aclocal:
1224 - aclocal now also supports -Wmumble and -Wno-mumble options.
1226 - `dirlist' entries (for the aclocal search path) may use shell
1227 wildcards such as `*', `?', or `[...]'.
1229 - aclocal supports an --install option that will cause system-wide
1230 third-party macros to be installed in the local directory
1231 specified with the first -I flag. This option also uses #serial
1232 lines in M4 files to upgrade local macros.
1234 The new aclocal options --dry-run and --diff help to review changes
1235 before they are installed.
1237 - aclocal now outputs an autoconf version check in aclocal.m4 in
1238 projects using automake.
1240 For a few years, automake and aclocal have been calling autoconf
1241 (or its underlying engine autom4te) to accurately retrieve the
1242 data they need from configure.ac and its siblings. Doing so can
1243 only work if all autotools use the same version of autoconf. For
1244 instance a Makefile.in generated by automake for one version of
1245 autoconf may stop working if configure is regenerated with another
1246 version of autoconf, and vice versa.
1248 This new version check ensures that the whole build system has
1249 been generated using the same autoconf version.
1251 * Support for new Autoconf macros:
1253 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1255 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1256 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1257 in different directories. However, only one instance of such a
1258 library objects directory is supported.
1260 * Change to Libtool support:
1262 - Libtool generic flags (those that go before the --mode=MODE option)
1263 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1265 * Yacc and Lex changes:
1267 - The rebuild rules for distributed Yacc and Lex output will avoid
1268 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1271 - ylwrap is now always used for lex and yacc source files,
1272 regardless of whether there is more than one source per directory.
1274 * Languages changes:
1276 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1277 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1278 tracking, unlike non-preprocessed assembler (*.s).
1280 - subdir-object mode works now with Assembler. Automake assumes
1281 that the compiler understands `-c -o'.
1283 - Preprocessed assembler (*.S) compilation now also honors
1284 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1286 - Improved support for Objective C:
1287 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1288 - A new section of the manual documents the support.
1290 - New support for Unified Parallel C:
1291 - AM_PROG_UPC looks for a UPC compiler.
1292 - A new section of the manual documents the support.
1294 - Per-target flags are now correctly handled in link rules.
1296 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1297 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1298 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1299 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1301 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1302 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1303 is expected to work (and actually works during compilation).
1305 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1306 "in addition to" breaks backward compatibility with older versions.
1307 If your package used both variables, as in
1309 AM_LDFLAGS = common flags
1310 bin_PROGRAMS = a b c
1311 a_LDFLAGS = more flags
1314 and assumed *_LDFLAGS would sum up, you should rewrite it as
1316 AM_LDFLAGS = common flags
1317 bin_PROGRAMS = a b c
1318 a_LDFLAGS = $(AM_LDFLAGS) more flags
1321 This new behavior of *_LDFLAGS is more coherent with other
1322 per-target variables, and the way *_LDFLAGS variables were
1323 considered internally.
1325 * New installation targets:
1327 - New targets mandated by GNU Coding Standards:
1332 By default they will only install Texinfo manuals.
1333 You can customize them with *-local variants:
1339 - The undocumented recursive target `uninstall-info' no longer exists.
1340 (`uninstall' is in charge of removing all possible documentation
1341 flavors, including optional formats such as dvi, ps, or info even
1342 when `no-installinfo' is used.)
1344 * Miscellaneous changes:
1346 - Automake no longer complains if input files for AC_CONFIG_FILES
1347 are specified using shell variables.
1349 - clean, distribution, or rebuild rules are normally disabled for
1350 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1351 AC_CONFIG_LINK specified using shell variables. However, if these
1352 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1353 be able to output rules anyway.
1354 (See the Automake documentation for AC_CONFIG_FILES.)
1356 - $(EXEEXT) is automatically appended to filenames of TESTS
1357 that have been declared as programs in the same Makefile.
1358 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1360 - `-Wportability' has finally been turned on by default for `gnu' and
1361 `gnits' strictness. This means, automake will complain about %-rules
1362 or $(GNU Make functions) unless you switch to `foreign' strictness or
1363 use `-Wno-portability'.
1365 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1366 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1367 $(mkdir_p) variable is still defined (to the same value as
1368 $(MKDIR_P)) but should be considered obsolete. If you are using
1369 $(mkdir_p) in some of your rules, please plan to update them to
1370 $(MKDIR_P) at some point.
1372 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1373 They still work in this release, but may be withdrawn in a future one.
1375 - Inline compilation rules for gcc3-style dependency tracking are
1378 - Automake installs a "Hello World!" example package in $(docdir).
1379 This example is used throughout the new "Autotools Introduction"
1380 chapter of the manual.
1382 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1386 * Makefile.in bloat reduction:
1388 - Inference rules are used to compile sources in subdirectories when
1389 the `subdir-objects' option is used and no per-target flags are
1390 used. This should reduce the size of some projects a lot, because
1391 Automake used to output an explicit rule for each such object in
1394 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1395 object that must be built with explicit rules. It just outputs
1396 the rules required to build the kind of object considered: either
1397 the two .o and .obj rules for usual objects, or the .lo rule for
1400 * Change to Libtool support:
1402 - Libtool tags are used with libtool versions that support them.
1403 (I.e., with Libtool 1.5 or greater.)
1405 - Automake is now able to handle setups where a libtool library is
1406 conditionally installed in different directories, as in
1409 lib_LTLIBRARIES = liba.la
1411 pkglib_LTLIBRARIES = liba.la
1413 liba_la_SOURCES = ...
1415 * Changes to aclocal:
1417 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1418 really evaluated, before it decides to include them in aclocal.m4.
1419 This solves nasty problems with conditional redefinitions of
1420 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1421 *.m4 files to be included in any project using these macros.
1422 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1423 most famous instance of this bug.)
1425 - Do not complain about missing conditionally AC_REQUIREd macros
1426 that are not actually used. In 1.8.x aclocal would correctly
1427 determine which of these macros were really needed (and include
1428 only these in the package); unfortunately it would also require
1429 all of them to be present in order to run. This created
1430 situations were aclocal would not work on a tarball distributing
1431 all the macros it uses. For instance running aclocal on a project
1432 containing only the subset of the Gettext macros in use by the
1433 project did not work, because gettext conditionally requires other
1436 * Portability improvements:
1438 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1439 tar-pax. The new option filename-length-max=99 helps diagnosing
1440 filenames that are too long for tar-v7. (PR/414)
1442 - Variables aumented with `+=' are now automatically flattened (i.e.,
1443 trailing backslashes removed) and then wrapped around 80 colummns
1444 (adding trailing backslashes). In previous versions, a long series
1450 would result in a single-line definition of VAR that could possibly
1451 exceed the maximum line length of some make implementations.
1453 Non-augmented variables are still output as they are defined in
1458 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1459 Works the same as the old Fortran 77 implementation; just replace
1460 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1461 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1463 - Support for conditional _LISP.
1465 - Support for conditional -hook and -local rules (PR/428).
1467 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1469 - Automake will not write any Makefile.ins after the first error it
1470 encounters. The previous Makefile.ins (if any) will be left in
1471 place. (Warnings will not prevent output, but remember they can
1472 be turned into errors with -Werror.)
1474 - The restriction that SUBDIRS must contain direct children is gone.
1477 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1478 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1480 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1482 Bugs fixed in 1.8.5:
1484 * Long-standing bugs:
1486 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1487 so that `make distclean' and `make maintainer-clean' can work.
1489 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1491 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1493 - Polish diagnostic when no input file is found.
1495 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1497 Bugs fixed in 1.8.4:
1499 * Long-standing bugs:
1501 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1502 overridden by the user.
1504 - Honor PATH_SEPARATOR in various places of the Automake package, for
1507 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1510 - Fix install-sh so it can install the `mv' binary... using `mv'.
1512 - Fix tru64 dependency tracking for libtool objects.
1514 - Work around Exuberant Ctags when creating a TAGS files in a directory
1515 without files to scan but with subdirectories to include.
1517 * Bugs introduced by 1.8:
1519 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1520 not defined in the same conditions as the _LDADD that uses it.
1522 - Do not warn when JAVAROOT is overridden, this is legitimate.
1524 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1526 Bugs fixed in 1.8.3:
1528 * Long-standing bugs:
1530 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1531 or any of the other *dir variables contain a space.
1533 Please note that Automake does not and cannot support spaces in
1534 filenames that are involved during the build. This change affects
1535 only installation paths, so that `make install' does not bomb out
1536 in packages configured with
1537 ./configure --prefix '/c/Program Files'
1539 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1540 POSIXLY_CORRECT is set.
1542 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1543 since Autoconf 2.54, which defines LIBOBJS itself.
1545 - Fix a potential (but unlikely) race condition in parallel elisp
1546 builds. (Introduced in 1.7.3.)
1548 - Do not assume that users override _DEPENDENCIES in all conditions
1549 where Automake will try to define them.
1551 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1552 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1555 This fix also affects the $(mkdir_p) variable defined since
1556 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1557 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1559 - Secure temporary directory creation in `make distcheck'. (PR/413)
1561 - Do not generate two build rules for `parser.h' when the
1562 parser appears in two different conditionals.
1564 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1565 checking. Usually ./configure will not pick this shell; so this
1566 fix only helps cases where the shell is forced to /bin/sh.
1568 * Bugs introduced by 1.8:
1570 - In some situations (hand-written `m4_include's), aclocal would
1571 call the `File::Spec->rel2abs' method, which was only introduced
1572 in Perl 5.6. This new version reestablish support Perl 5.005.
1574 It is likely that the next major Automake releases will require at
1575 least Perl 5.6. Consider upgrading your development environment
1576 if you are still using the five-year-old Perl 5.005.
1578 - Automake would sometimes fail to define rules for targets listed
1579 in variables defined in multiple conditions. For instance on
1585 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1586 `b.$(OBJEXT): b.c' rule.
1588 * New sections in manual:
1590 - Third-Party Makefiles: how to interface third party Makefiles.
1591 - Upgrading: upgrading packages to newer Automake versions.
1592 - Multiple Outputs: handling tools that produce many outputs.
1594 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1598 * A (well known) portability bug slipped in the changes made to
1599 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1600 install anything on Tru64.
1602 * Fix install rules for conditionally built python files. (This never
1605 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1609 * Bugs introduced by 1.8:
1611 - Fix Config.pm import error with old Perl versions (at least
1612 5.005_03). One symptom is that aclocal could not find its macro
1615 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1616 created by `make install' are always world readable, even if the
1617 installer happens to have an overly restrictive umask (e.g. 077).
1618 This was a mistake and has been reverted. There are at least two
1619 reasons why we must not use `-m 0755':
1620 - it causes special bits like SGID to be ignored,
1621 - it may be too restrictive (some setups expect 775 directories).
1623 - Fix aclocal to honor definitions located in files which have been
1624 m4_included manually. aclocal 1.8 had been updated to check
1625 m4_included files for new requirements, but forgot that these
1626 m4_included files can also provide new definitions.
1628 Note that if you have such a setup, we recommend you get rid of
1629 it. In the past, there was a reason to m4_include files manually:
1630 aclocal used to duplicate entire M4 files into aclocal.m4, even
1631 files that were distributed. Some packages were therefore
1632 m4_including the distributed file directly, and playing some
1633 tricks to ensure aclocal would not copy that file to aclocal.m4,
1634 in order to limit the amount of duplication. Since aclocal 1.8.x
1635 will precisely output m4_includes for local M4 files, we recommend
1636 that you clean up your setup, removing all manual m4_includes and
1637 letting aclocal output them.
1639 - Output detailed menus in the Info version if the Automake manual,
1640 so that Emacs can locate the indexes.
1642 - configure.ac and configure were listed twice in DIST_COMMON (an
1643 internal variable where Automake lists configury files to
1644 distribute). This was harmless, but unaesthetic.
1646 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1647 This was an issue only in the Automake package itself, not in
1650 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1651 DEST:SRC. This was wrong, as some packages do
1652 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1655 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1656 argument. This caused two kinds of failures:
1657 - Rules installing data in a conditionally defined directory
1658 failed when that directory was undefined. In this case no
1659 argument was supplied.
1660 - `make installdirs' failed, because several directories were
1661 passed to $(mkdir_p). This was an issue only on platform
1662 were $(mkdir_p) is implemented with `install-sh -d'.
1663 $(mkdir_p) as been changed to accept 0 or more arguments, as
1666 * Long-standing bugs:
1668 - Fix an unexpected diagnostic occurring when users attempt
1669 to override some internal variables that Automake appends to.
1671 - aclocal now scans configure.ac for macro definitions (PR/319).
1673 - Fix a portability issue with OSF1/Tru64 Make. If a directory
1674 distributes files which are outside itself (this usually occurs
1675 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
1676 from a parent package), then `make distcheck' fails due to an
1677 optimization performed by OSF1/Tru64 Make in its VPATH handling.
1678 (tests/subpkg2.test failure)
1680 - Fix another portability issue with Sun and OSF1/Tru64 Make.
1681 In a VPATH-build configuration, `make install' would install
1682 nobase_ files to wrong locations.
1684 - Fix a Perl `uninitialized value' diagnostic occurring when
1685 automake complains that a Texinfo file does not have a
1686 @setfilename statement.
1688 - Erase config.status.lineno during `make distclean'. This file
1689 can be created by config.status. Automake already knew about
1690 configure.lineno, but forgot config.status.lineno.
1692 - Distribute all files, even those which are built and installed
1693 conditionally. This change affects files listed in conditionally
1694 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
1695 as well as those listed in conditionally defined dist_*_DATA,
1696 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
1698 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
1699 doesn't conform to POSIX.
1701 - Normalize help strings for configure variables and options added
1706 - Check for python2.4 in AM_PATH_PYTHON.
1708 * Spurious failures in test suite:
1710 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
1711 tests/ltconv.test: fix failures with CVS Libtool.
1712 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
1713 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
1714 fix failures with old Texinfo versions.
1716 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1722 - The NEWS file is more verbose.
1726 - Autoconf 2.58 or greater is required.
1730 - Default source file names in the absence of a _SOURCES declaration
1731 are made by removing any target extension before appending `.c', so
1732 to make the libtool module `foo.la' from `foo.c', you only need to
1735 lib_LTLIBRARIES = foo.la
1736 foo_la_LDFLAGS = -module
1738 For backward compatibility, foo_la.c will be used instead of
1739 foo.c if this file exists or is the explicit target of a rule.
1740 However -Wobsolete will warn about this deprecated naming.
1742 - AR's `cru' flags are now set in a global ARFLAGS variable instead
1743 of being hard-coded in each $(AR) invocation, so they can be
1744 substituted from configure.ac. This has been requested by people
1745 dealing with non-POSIX ar implementations.
1747 - New warning option: -Woverride. This will warn about any user
1748 target or variable definitions which override Automake
1751 - Texinfo rules back up and restore info files when makeinfo fails.
1753 - Texinfo rules now support the `html' target.
1754 Running this requires Texinfo 4.0 or greater.
1756 `html' is a new recursive target, so if your package mixes
1757 hand-crafted `Makefile.in's with Automake-generated
1758 `Makefile.in's, you should adjust the former to support (or
1759 ignore) this target so that `make html' recurses successfully. If
1760 you had a custom `html' rule in your `Makefile.am', it's better to
1761 rename it as `html-local', otherwise your rule will override
1762 Automake's new rule (you can check that by running `automake
1763 -Woverride') and that will stop the recursion to subdirectories.
1765 Last but not least, this `html' rule is declared PHONY, even when
1766 overridden. Fortunately, it appears that few packages use a
1767 non-PHONY `html' rule.
1769 - Any file which is m4_included from configure.ac will appear as a
1770 configure and Makefile.in dependency, and will be automatically
1773 - The rules for rebuilding Makefiles and Makefile.ins will now
1774 rebuild all Makefiles and all Makefile.ins at once when one of
1775 configure's dependencies has changed. This is considerably faster
1776 than previous implementations, where config.status and automake
1777 were run separately in each directory (this still happens when you
1778 change a Makefile.am locally, without touching configure.ac or
1779 friends). Doing this also solves a longstanding issue: these
1780 rebuild rules failed to work when adding new directories to the
1781 tree, forcing you to run automake manually.
1783 - For similar reasons, the rules to rebuild configure,
1784 config.status, and aclocal.m4 are now defined in all directories.
1785 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
1786 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
1787 should better define them in all directories. This is easily done
1788 using an AC_SUBST (make sure you prefix these dependencies with
1789 $(top_srcdir) since this variable will appear at different
1790 levels of the build tree).
1792 - aclocal will now use `m4_include' instead of copying local m4
1793 files into aclocal.m4. (Local m4 files are those you ship with
1794 your project, other files will be copied as usual.)
1796 Because m4_included files are automatically distributed, it means
1797 for most projects there is no point in EXTRA_DISTing the list of
1798 m4 files which are used. (You can probably get rid of
1799 m4/Makefile.am if you had one.)
1801 - aclocal will avoid touching aclocal.m4 when possible, so that
1802 Autom4te's cache isn't needlessly invalidated. This behavior can
1803 be switched off with the new `--force' option.
1805 - aclocal now uses Autoconf's --trace to detect macros which are
1806 actually used and will no longer include unused macros simply
1807 because they where mentioned. This was often the case for macros
1808 called conditionally.
1810 - New options no-dist and no-dist-gzip.
1812 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
1813 py-compile, and ylwrap, now all understand --version and --help.
1815 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
1816 links as part of the distclean target and including source files in
1819 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
1820 argument. The latter can be used to override the default behavior
1821 (which is to abort).
1823 - Automake will exit with $? = 63 on version mismatch. (So does
1824 Autoconf 2.58) missing knows this, and in this case it will
1825 emulate the tools as if they were absent. Because older versions
1826 of Automake and Autoconf did not use this exit code, this change
1827 will only be useful in projects generated with future versions of
1830 - When using AC_CONFIG_FILES with multiple input files, Automake
1831 generates the first ".in" input file for which a ".am" exists.
1832 (Former versions would try to use only the first input file.)
1834 - lisp_DATA is now allowed. If you are using the empty ELCFILES
1835 idiom to disable byte-compilation of lisp_LISP files, it is
1836 recommended that you switch to using lisp_DATA. Note that
1837 this is not strictly equivalent: lisp_DATA will install elisp
1838 files even if emacs is not installed, while *_LISP do not
1839 install anything unless emacs is found.
1841 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
1842 available. This selection is achieved through the Makefile
1843 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
1844 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
1845 `$(install_sh) -m 0755 -d'.
1849 - Because `mkdir -p' is available on most platforms, and we can use
1850 `install-sh -d' when it is not, the use of the mkinstalldirs
1851 script is being phased out. `automake --add-missing' no longer
1852 installs it, and if you remove mkinstalldirs from your package,
1853 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
1855 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
1856 gettextize and autopoint will install it when needed. Automake
1857 will continue to define the $(mkinstalldirs) and to distribute
1858 mkinstalldirs when this script is in the source tree.
1860 - AM_PROG_CC_STDC is now empty. The content of this macro was
1861 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
1862 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
1863 renaming should be safe, even if you have to support several,
1864 versions of Automake, because AC_PROG_CC defines this variable
1865 since Autoconf 2.54.)
1867 - Some users where using the undocumented ACLOCAL_M4_SOURCES
1868 variable to override the aclocal.m4 dependencies computed
1869 (inaccurately) by older versions of Automake. Because Automake
1870 now tracks configure's m4 dependencies accurately (see m4_include
1871 above), the use of ACLOCAL_M4_SOURCES should be considered
1872 obsolete and will be flagged as such when running `automake
1877 - Defining programs conditionally using Automake conditionals no
1878 longer leads to a combinatorial explosion. The following
1879 construct used to be troublesome when used with dozens of
1894 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
1896 - Due to implementation constraints, previous versions of Automake
1897 proscribed multiple conditional definitions of some variables
1907 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
1908 This restriction has been lifted, and these variables now
1909 support multiple conditional definitions as do other variables.
1911 - Cleanup the definitions of $(distdir) and $(top_distdir).
1912 $(top_distdir) now points to the root of the distribution
1913 directory created during `make dist', as it did in Automake 1.4,
1914 not to the root of the build tree as it did in intervening
1915 versions. Furthermore these two variables are now only defined in
1916 the top level Makefile, and passed to sub-directories when running
1919 - The --no-force option now correctly checks the Makefile.in's
1920 dependencies before deciding not to update it.
1922 - Do not assume that make files are called Makefile in cleaning rules.
1924 - Update .info files in the source tree, not in the build tree. This
1925 is what the GNU Coding Standard recommend. Only Automake 1.7.x
1926 used to update these files in the build tree (previous versions did
1927 it in the source tree too), and it caused several problems, varying
1928 from mere annoyance to portability issues.
1930 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
1931 when --add-missing and --force-missing are used. For backward
1932 compatibility --add-missing will continue to install COPYING (in
1933 `gnu' strictness) when none of these three files exist, but this
1934 use is deprecated: you should better choose a license yourself and
1935 install it once for all in your source tree (and in your code
1938 - Fix ylwrap so that it does not overwrite header files that haven't
1939 changed, as the inline rule already does.
1941 - User-defined rules override automake-defined rules for the same
1942 targets, even when rules do not have commands. This is not new
1943 (and was documented), however some of the automake-generated
1944 rules have escaped this principle in former Automake versions.
1945 Rules for the following targets are affected by this fix:
1947 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
1948 info, info-am, install-data-am, install-exec-am, install-info,
1949 install-info-am, install-man, installcheck-am, maintainer-clean,
1950 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
1951 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
1953 Practically it means that an attempt to supplement the dependencies
1954 of some target, as in
1956 clean: my-clean-rule
1958 will now *silently override* the automake definition of the
1959 rule for this target. Running `automake -Woverride' will diagnose
1960 all such overriding definitions.
1962 It should be noted that almost all of these targets support a *-local
1963 variant that is meant to supplement the automake-defined rule
1964 (See node `Extending' in the manual). The above rule should
1967 clean-local: my-clean-rule
1969 These *-local targets have been documented since at least
1970 Automake 1.2, so you should not fear the change if you have
1971 to support multiple automake versions.
1975 - The Automake manual is now distributed under the terms of the GNU FDL.
1977 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
1979 - core dumps are no longer removed by the cleaning rules. There are
1980 at least three reasons for this:
1981 1. These files should not be created by any build step,
1982 so their removal do not fit any of the cleaning rules.
1983 Actually, they may be precious to the developer.
1984 2. If such file is created during a build, then it's clearly a
1985 bug Automake should not hide. Not removing the file will
1986 cause `make distcheck' to complain about its presence.
1987 3. Operating systems have different naming conventions for
1988 core dump files. A core file on one system might be a
1989 completely legitimate data file on another system.
1991 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
1992 defined by Automake. This means that any definition in the
1993 environment will be used, unless overridden in the Makefile.am or
1994 on the command line. The old behavior, where these variables were
1995 defined empty in each Makefile, can be obtained by AC_SUBSTing or
1996 AC_ARG_VARing each variable from configure.ac.
1998 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
1999 documented. (The is not a new feature, these variables have
2000 been there since at least Automake 1.4.)
2002 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2004 Bugs fixed in 1.7.9:
2005 * Fix install-strip to work with nobase_ binaries.
2006 * Fix renaming of #line directives in ylwrap.
2007 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2009 Bugs fixed in 1.7.8:
2010 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2011 * Fix detection of Debian's install-info, broken since version 1.5.
2012 (Debian bug #213524).
2013 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2014 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2016 Bugs fixed in 1.7.7:
2017 * The implementation of automake's --no-force option is unreliable,
2018 so this option is ignored in this version. A real fix will appear in
2019 Automake 1.8. (Debian Bug #206299)
2020 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2021 argument is given. (PR/399)
2022 * Do not warn about leading `_' in variable names, even with -Wportability.
2023 * Support user redefinitions of TEXINFO_TEX.
2024 * depcomp: support AIX Compiler version 6.
2025 * Fix missing rebuilds during `make dist' with BSD make.
2026 (Could produce tarballs containing out-of-date files.)
2027 * Resurrect multilib support.
2028 * Noteworthy manual updates:
2029 - Extending aclocal: how to write m4 macros that won't trigger warnings
2031 - A Shared Library: Rewrite and split into subsections.
2033 Bugs fixed in 1.7.6:
2034 * Fix depcomp's icc mode for ICC 7.1.
2035 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2036 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2037 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2038 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2039 * Remove Latin-1 characters from elisp-comp.
2040 * Update the manual's @dircategory to match the Free Software Directory.
2042 Bugs fixed in 1.7.5:
2043 * Update install-sh's license to remove an advertising clause.
2044 (Debian bug #191717)
2045 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2046 that caused invalid Makefile.ins to be generated.
2047 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2048 * New FAQ entry: renamed objects.
2050 Bugs fixed in 1.7.4:
2051 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2052 the Emacs implementation)
2053 * Fix output of aclocal.m4 dependencies in subdirectories.
2054 * Use `mv -f' instead of `mv' in fastdep rules.
2055 * Upgrade mdate-sh to work on OS/2.
2056 * Don't byte-compile elisp files when ELCFILES is set empty.
2057 (this documented feature was broken by 1.7.3)
2058 * Diagnose trailing backslashes on last line of Makefile.am.
2059 * Diagnose whitespace following trailing backslashes.
2060 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2061 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2063 * `make install' will build `BUILT_SOURCES' first.
2064 * Minor documentation fixes.
2066 Bugs fixed in 1.7.3:
2067 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2068 * Query distutils for `pythondir' and `pythonexecdir', instead of
2069 using an hardcoded path. This should allow builds on 64-bit
2070 distributions that usually use lib64/ instead of lib/.
2071 * AM_PATH_PYTHON will also search for python2.3.
2072 * elisp files are now built all at once instead of one by one. Besides
2073 incurring a speed-up, this is required to support interdependent elisp files.
2074 * Support for DJGPP:
2075 - `make distcheck' will now work in `_inst/' and `_build' instead
2076 of `=inst/' and `=build/'
2077 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2078 - install/uninstall `*.i[0-9][0-9]'-style info files
2079 - more changes that affect only the Automake package (not its output)
2080 * Fix some incompatibilities with upcoming perl-5.10.
2081 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2082 PACKAGE and VERSION.
2084 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2085 is troublesome with gcc and Solaris compilers. (PR/385)
2086 - makedepend mode: work with Libtool. (PR/385 too)
2088 * better support for unusual gettext setups, such as multiple po/ directories
2090 - Flag missing po/ and intl/ directories as warnings, not errors.
2091 - Disable these warnings if po/ does not exist.
2092 * Noteworthy manual updates:
2094 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2096 - Document `AM_YFLAGS = -d'. (PR/382)
2098 Bugs fixed in 1.7.2:
2099 * Fix installation and uninstallation of Info files built in subdirectories.
2100 * Do not run `./configure --with-included-gettext' during `make distcheck'
2101 if AM_GNU_GETTEXT([external]) is used.
2102 * Correctly uninstall renamed man pages.
2103 * Do not strip escaped newline in variables defined in one condition
2104 and augmented in another condition.
2105 * Fix ansi2knr rules for LIBOBJS sources.
2106 * Clean all known Texinfo index files, not only those which appear to
2107 be used, because we cannot know which indexes are used in included files.
2108 (PR/375, Debian Bug #168671)
2109 * Honor only the first @setfilename seen in a Texinfo file.
2110 * Treat "required file X not found" diagnostics as errors (exit status 1).
2111 * Don't complain that a required file is not found when it is a Makefile
2113 * Don't use single suffix inference rules when building `.info'-less
2114 Info files, for the sake of Solaris make.
2115 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2116 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2117 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2118 * Fix building of deansified files from subdirectories. (PR/370)
2119 * Add missing `fi' in the .c->.obj rules.
2120 * Improve install-sh to work even when names contain spaces or certain
2121 (but not all) shell metachars.
2122 * Fix the following spurious failures in the test suite:
2123 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2124 * Noteworthy manual updates:
2125 - Augment the section about BUILT_SOURCES.
2126 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2128 Bugs fixed in 1.7.1:
2129 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2131 * Aclocal should now recognize macro names containing parentheses, e.g.
2132 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2133 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2135 * Install Python files even if they were built. (PR/369)
2136 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2137 version might not be defined in the latter. (PR/358)
2138 * Reorder arguments passed to a couple of commands, so things works
2139 when POSIXLY_CORRECT=1.
2140 * Fix a regex that can cause Perl to segfault on large input.
2142 * Fix distribution of packages that have some sources defined conditionally,
2143 as in the `Conditional compilation using Automake conditionals' example
2145 * Fix spurious test suite failures on IRIX.
2146 * Don't report a required variable as undefined if it has been
2147 defined conditionally for the "right" conditions.
2148 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2149 `make distcheck' fails.
2150 * Fix distribution of included Makefile fragment, so we don't create
2151 spurious directories in the distribution. (PR/366)
2152 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2155 * Autoconf 2.54 is required.
2156 * `aclocal' and `automake' will no longer warn about obsolete
2157 configure macros. This is done by `autoconf -Wobsolete'.
2158 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2159 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2160 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2161 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2162 `configure.ac' for you.
2163 * Support for per-program and per-library `_CPPFLAGS'.
2164 * New `ctags' target (builds CTAGS files).
2165 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2166 (see `automake --help' or the manual for a list of them).
2167 * Honor the WARNINGS environment variable.
2168 * Omit the call to depcomp when using gcc3: call the compiler directly.
2169 * A new option, std-options, tests that programs support --help and --version
2170 when `make installcheck' is run. This is enabled by --gnits.
2171 * Texinfo rules now support the `ps' and `pdf' targets.
2172 * Info files are now created in the build directory, not the source directory.
2173 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2175 * `make distcheck' will enforce DESTDIR support by attempting
2177 * `+=' can be used in conditionals, even if the augmented variable
2178 was defined for another condition.
2179 * Makefile fragments (inserted with `include') are always distributed.
2180 * Use Autoconf's --trace interface to inspect configure.ac and get
2181 a more accurate view of it.
2182 * Add support for extending aclocal's default macro search path
2183 using a `dirlist' file within the aclocal directory.
2184 * automake --output-dir is deprecated.
2185 * The part of the distcheck target that checks whether uninstall actually
2186 removes all installed files has been moved in a separate target,
2187 distuninstallcheck, so it can be overridden easily.
2191 * Support for AM_INIT_GETTEXT([external])
2192 * Bug fixes, including:
2193 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2194 - nobase_ programs and scripts honor --program-transform correctly.
2195 - Erase configure.lineno during `make distclean'.
2196 - Erase YACC and LEX outputs during `make maintainer-clean'.
2199 * Many bug fixes, including:
2200 - Requiring the current version works.
2201 - Fix "$@" portability issues (for Zsh).
2202 - Fix output of dummy dependency files in presence of post-processed
2204 - Don't compute dependencies in background to avoid races with libtool.
2205 - Fix handling of _OBJECTS variables for targets sharing source variables.
2206 - Check dependency mode for Java when AM_PROG_GCJ is used.
2209 * automake --output-dir is deprecated
2210 * Many bug fixes, including:
2211 - Don't choke on AM_LDFLAGS definitions.
2212 - Clean libtool objects from subdirectories.
2213 - Allow configure variables with reserved suffix and unknown prefix
2214 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2215 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2218 * Autoconf 2.52 is required.
2219 * automake no longer run libtoolize.
2220 This is the job of autoreconf (from GNU Autoconf).
2221 * `dist' generates all the archive flavors, as did `dist-all'.
2222 * `dist-gzip' generates the Gzip tar file only.
2223 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2224 explosion. Makefile.in's keep a reasonable size.
2225 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2226 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2228 * `#line' of Lex and Yacc files are properly set.
2229 * EXTRA_DIST can contain generated directories.
2230 * Support for dot-less extensions in suffix rules.
2231 * The part of the distcheck target that checks whether distclean actually
2232 cleans all built files has been moved in a separate target, distcleancheck,
2233 so it can be overridden easily.
2234 * `make distcheck' will pass additional options defined in
2235 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2236 * Fixed CDPATH portability problems, in particular for MacOS X.
2237 * Fixed handling of nobase_ targets.
2238 * Fixed support of implicit rules leading to .lo objects.
2239 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2240 * Added uninstall-hook target
2241 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2242 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2243 (Note that "pkgname" is not "tarname", see the manual for details.)
2244 It is also possible to pass a list of global Automake options as
2245 first argument to this new form of AM_INIT_AUTOMAKE.
2246 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2247 to be a real assembler.
2248 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2249 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2250 * aclocal and automake are also installed with the version number
2251 appended, and some of the install directory names have changed.
2252 This lets you have multiple versions installed simultaneously.
2253 * Support for parsers and lexers in subdirectories.
2256 * Support for `configure.ac'.
2257 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2258 * `make dist-all' is much faster.
2259 * Allows '@' AC_SUBSTs in macro names.
2260 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2261 * User-side dependency tracking. Developers no longer need GNU make
2263 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2264 * Most files are correctly handled if they appear in subdirs
2265 For instance, a _DATA file can appear in a subdir
2266 * GNU tar is no longer required for `make dist'
2267 * Added support for `dist_' and `nodist_' prefixes
2268 * Added support for `nobase_' prefix
2269 * Compiled Java support
2270 * Support for per-executable and per-library compilation flags
2274 * Added support for the Fortran 77 programming language.
2275 * Re-indexed the Automake Texinfo manual.
2276 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2277 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2278 * Support for latest autoconf, including support for objext
2279 * Can now put `.' in SUBDIRS to control build order
2280 * `include' command and `+=' support for macro assignment
2281 * Dependency tracking no long susceptible to deleted header file problem
2282 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2287 * Better Cygwin32 support
2288 * Support for suffix rules with _SOURCES variables
2289 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2290 * @LEXLIB@ no longer required when lex source seen
2291 Lex support in `missing', and new lex macro. Update your missing script.
2292 * Built-in support for assembly
2293 * aclocal gives error if `AM_' macro not found
2294 * Passed YFLAGS, not YACCFLAGS, to yacc
2295 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2296 * Dependencies computed as a side effect of compilation
2297 * Preliminary support for Java
2298 * DESTDIR support at "make install" time
2299 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2303 * Better DejaGnu support
2304 * Added no-installinfo option
2305 * Added Emacs Lisp support
2306 * Added --no-force option
2307 * Included `aclocal' program
2308 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2309 * Now uses `AM_' macro names everywhere
2310 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2311 ansi2knr now works correctly on K&R sources
2312 * Better C++, yacc, lex support
2313 * Will compute _DEPENDENCIES variables automatically if not supplied
2314 * Will interpolate $(...) and ${...} when examining contents of a variable
2315 * .deps files now in build directory, not source directory; dependency
2316 handling generally rewritten
2317 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2318 * can now put config.h into a subdir
2319 * Added dist-all target
2320 * Support for install-info program (see texinfo 3.9)
2321 * Support for "yacc -d"
2322 * configure substitutions are automatically discovered and included
2323 in generated Makefile.in
2324 * Special --cygnus mode
2325 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2326 when making distribution. Some dependencies are auto-ignored.
2327 * Changed how libraries are specified in _LIBRARIES variable
2328 * Full libtool support, from Gord Matzigkeit
2329 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2330 AM_CONFIG_HEADER handles it automatically
2331 * Texinfo output files no longer need .info extension
2332 * Added `missing' support
2334 * Conditionals in Makefile.am, from Ian Taylor
2338 * distcheck target runs install and installcheck targets
2339 * Added preliminary support for DejaGnu.
2344 * More libtool fixes from Gord Matzigkeit; libtool support is still
2346 * Added support for jm_MAINTAINER_MODE
2348 * New "distcheck" target
2352 * mkinstalldirs and mdate-sh now appear in directory specified by
2354 * Removed DIST_SUBDIRS, DIST_OTHER
2355 * AC_ARG_PROGRAM only required when an actual program exists
2356 * dist-hook target now run before distribution packaged up; idea from
2357 Dieter Baron. Other hooks exist, too.
2358 * Preliminary (unfinished) support for libtool
2359 * Added short option names.
2360 * Better "dist" support when gluing together multiple packages
2364 * Documentation updates (many from François Pinard)
2365 * strictness `normal' now renamed to `foreign'
2366 * Renamed --install-missing to --add-missing
2367 * Now handles AC_CONFIG_AUX_DIR
2368 * Now handles TESTS macro
2369 * DIST_OTHER renamed to EXTRA_DIST
2370 * DIST_SUBDIRS is deprecated
2371 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2372 * Better error messages in many cases
2373 * Program names are canonicalized
2374 * Added "check" prefix; from Gord Matzigkeit
2378 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2379 * Beginnings of a test suite
2380 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2381 * Doesn't print anything when running
2382 * Beginnings of MAINT_CHARSET support
2383 * Can specify version in AUTOMAKE_OPTIONS
2384 * Most errors recognizable by Emacs' M-x next-error
2385 * Added --verbose option
2386 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2387 configure-generated names
2388 * Required macros now distributed in aclocal.m4
2390 * --strictness=gnu is default
2394 * More sophisticated configure.in scanning; now understands ALLOCA and
2395 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2396 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2397 * CONFIG_HEADER variable now obsolete
2398 * Can handle multiple Texinfo sources
2399 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2400 * HEADERS variable no longer needed; now can put .h files directly into
2401 foo_SOURCES variable.
2402 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2403 corresponding ".in" files are included in the distribution.
2406 * Added --gnu and --gnits options
2407 * More standards checking
2409 * Cleaned up 'dist' targets
2410 * Added AUTOMAKE_OPTIONS variable and several options
2411 * Now scans configure.in to get some information (preliminary)
2414 * Works with Perl 4 again
2417 * Added --install-missing option.
2418 * Pretty-prints generated macros and rules
2419 * Comments in Makefile.am are placed more intelligently in Makefile.in
2420 * Generates .PHONY target
2421 * Rule or macro in Makefile.am now overrides contents of Automake file
2422 * Substantial cleanups from François Pinard
2426 * Works with Perl 4 again.
2429 * New uniform naming scheme.
2430 * --strictness option
2432 * '.c' files corresponding to '.y' or '.l' files are automatically
2434 * Many bug fixes and cleanups
2437 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2440 * Bug fixes in 'clean' code.
2441 * Now generates 'installdirs' target.
2442 * man page installation reworked.
2443 * 'make dist' no longer re-creates all Makefile.in's.
2446 * Reimplemented in Perl
2447 * Added --amdir option (for debugging)
2448 * Texinfo support cleaned up.
2449 * Automatic de-ANSI-fication cleaned up.
2450 * Cleaned up 'clean' targets.
2453 * Automatic dependency tracking
2454 * More documentation
2455 * New variables DATA and PACKAGEDATA
2456 * SCRIPTS installed using $(INSTALL_SCRIPT)
2457 * No longer uses double-colon rules
2459 * Changes in advance of internationalization
2463 Copyright (C) 1995-2012 Free Software Foundation, Inc.
2465 This program is free software; you can redistribute it and/or modify
2466 it under the terms of the GNU General Public License as published by
2467 the Free Software Foundation; either version 2, or (at your option)
2470 This program is distributed in the hope that it will be useful,
2471 but WITHOUT ANY WARRANTY; without even the implied warranty of
2472 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2473 GNU General Public License for more details.
2475 You should have received a copy of the GNU General Public License
2476 along with this program. If not, see <http://www.gnu.org/licenses/>.
projects / platform / upstream / automake.git / blob