1 * WARNING: New versioning scheme for Automake.
3 - Starting with this version onward, Automake will use an update and
4 more rational versioning scheme, one that will allow users to know
5 which kind of changes can be expected from a new version, based on
8 + Micro versions (e.g., 1.13.3, 2.0.1, 3.2.8) will introduce only
9 documentation updates and bug and regression fixes; they will
10 not introduce new features, nor any backward-incompatibility (any
11 such incompatibility would be considered a bug, to be fixed with
12 a further micro release).
14 + Minor versions (e.g., 1.14, 2.1) can introduce new backward
15 compatible features; the only backward-incompatibilities allowed
16 in such a release are new *non-fatal* deprecations and warnings,
17 and possibly fixes for old or non-trivial bugs (or even inefficient
18 behaviours) that could unfortunately have been seen, and used, by
19 some developers as "corner case features". Possible disruptions
20 caused by this kind of fixes should hopefully be quite rare.
22 + Major versions (now expected to be released every 18 or 24 months,
23 and not more often) can introduce new big features (possibly with
24 rough edges and not-fully-stabilized APIs), removal of deprecated
25 features, backward-incompatible changes of behaviour, and possibly
26 major refactorings (that, while ideally transparent to the user,
27 could introduce new bugs). Incompatibilities should however not
28 be introduced gratuitously and abruptly; a proper deprecation path
29 should be duly implemented in the preceding minor releases.
31 - According to this new scheme, the next major version of Automake
32 (the one that has until now been labelled as '1.14') will actually
33 become "Automake 2.0". Automake 1.14 will be the next minor version,
34 which will introduce new features, deprecations and bug fixes, but
35 no real backward incompatibility.
37 - See discussion about automake bug#13578 for more details and
38 background: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578>
40 * WARNING: Future backward-incompatibilities!
42 - Makefile recipes generated by Automake 2.0 will expect to use an
43 'rm' program that doesn't complain when called without any non-option
44 argument if the '-f' option is given (so that commands like "rm -f"
45 and "rm -rf" will act as a no-op, instead of raising usage errors).
46 Accordingly, AM_INIT_AUTOMAKE will expand new shell code checking
47 that the default 'rm' program in PATH satisfies this requirement, and
48 aborting the configure process if this is not the case. This behavior
49 of 'rm' is very widespread in the wild, and it will be required in the
51 <http://austingroupbugs.net/view.php?id=542>
53 - Automake 2.0 will require Autoconf 2.70 or later (which is still
54 unreleased at the moment of writing, but is planned to be released
55 before Automake 2.0 is).
57 - Automake 2.0 will drop support for the long-deprecated 'configure.in'
58 name for the Autoconf input file. You are advised to start using the
59 recommended name 'configure.ac' instead, ASAP.
61 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated
62 in Automake 2.0 (where it will raise warnings in the "obsolete"
63 category). You are advised to start relying on the new Automake
64 support for AC_CONFIG_MACRO_DIRS instead (which was introduced in
67 - Automake 2.0 will remove support for automatic dependency tracking
68 with the SGI C/C++ compilers on IRIX. The SGI depmode has been
69 reported broken "in the wild" already, and we don't think investing
70 time in debugging and fixing is worthwhile, especially considering
71 that SGI has last updated those compilers in 2006, and is expected
72 to retire support for them in December 2013:
73 <http://www.sgi.com/services/support/irix_mips_support.html>
75 - Future versions of Automake might remove support for MS-DOS and
76 Windows 95/98/ME (support for them was offered by relying on the
77 DJGPP project). Note however that both Cygwin and MSYS/MinGW on
78 modern Windows versions will continue to be fully supported.
80 - Automake-provided scripts and makefile recipes might (finally!)
81 start assuming a POSIX shell in Automake 2.0.
83 - Starting from Automake 2.0, third-party m4 files located in the
84 system-wide aclocal directory, as well as in any directory listed
85 in the ACLOCAL_PATH environment variable, will take precedence
86 over "built-in" Automake macros. For example (assuming Automake
87 is installed in the /usr/local hierarchy), a definition of the
88 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
89 should take precedence over the same-named automake-provided macro
90 (defined in '/usr/local/share/aclocal-2.0/vala.m4').
92 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
96 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
98 - The 'compile' script is now unconditionally required for all
99 packages that perform C compilation (note that if you are using
100 the '--add-missing' option, automake will fetch that script for
101 you, so you shouldn't need any explicit adjustment).
102 This new behaviour is needed to avoid obscure errors when the
103 'subdir-objects' option is used, and the compiler is an inferior
104 one that doesn't grasp the combined use of both the "-c -o"
105 options; see discussion about automake bug#13378 for more details:
106 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
107 <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
109 - The next major Automake version (2.0) will unconditionally turn on
110 the 'subdir-objects' option. In order to smooth out the transition,
111 we now give a warning (in the category 'unsupported') whenever a
112 source file is present in a subdirectory but the 'subdir-object' is
113 not enabled. For example, the following usage will trigger such a
114 warning (of course, assuming the 'subdir-objects' option is off):
116 bin_PROGRAMS = sub/foo
117 sub_foo_SOURCES = sub/main.c sub/bar.c
119 - Automake will automatically enhance the AC_PROG_CC autoconf macro
120 to make it check, at configure time, that the C compiler supports
121 the combined use of both the "-c -o" options. The result of this
122 check is saved in the cache variable 'am_cv_prog_cc_c_o', and said
123 result can be overridden by pre-defining that variable.
125 - The AM_PROG_CC_C_O can still be called, but that should no longer
126 be necessary. This macro is now just a thin wrapper around the
127 Automake-enhanced AC_PROG_CC. This means, among the other things,
128 that its behaviour is changed in three ways:
130 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
131 macros behind the scenes.
133 2. It caches the check result in the 'am_cv_prog_cc_c_o'variable,
134 and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name
135 in only dynamically computed at configure runtime (sic!) from
136 the content of the '$CC' variable.
138 3. It no longer automatically AC_DEFINE the C preprocessor
139 symbol 'NO_MINUS_C_MINUS_O'.
143 - Automake can now be instructed to place '.info' files generated from
144 Texinfo input in the builddir rather than in the srcdir; this is done
145 specifying the new automake option 'info-in-builddir'. This feature
146 was requested by the developers of GCC, GDB, GNU binutils and the GNU
147 bfd library. See the extensive discussion about automake bug#11034
150 - For quite a long time, Automake has been implementing an undocumented
151 hack which ensured that '.info' files which appeared to be cleaned
152 (by e.g. being listed in the CLEANFILES or DISTCLEANFILES variables)
153 were built in the builddir rather than in the srcdir; this hack was
154 introduced to ensure better backward-compatibility with packages such
155 as Texinfo, which did things like:
157 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
158 DISTCLEANFILES = texinfo texinfo-* info*.info*
159 # Do not create info files for distribution.
163 in order not to distribute generated '.info' files.
165 Now that we have the 'info-in-builddir' option that explicitly causes
166 generated '.info' files to be placed in the builddir, this hack should
167 be longer necessary, so we deprecate it with runtime warnings. It will
168 likely be removed altogether in Automake 2.0.
170 * Relative directory in Makefile fragments:
172 - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
173 (and their short versions, '%D%' and '%C%' respectively) can now be used
174 in an included Makefile fragment. The former is substituted with the
175 relative directory of the included fragment (compared to the top level
176 including Makefile), and the latter with the canonicalized version of
177 the same relative directory:
179 bin_PROGRAMS += %reldir%/foo
180 %canon_reldir%_foo_SOURCES = %reldir%/bar.c
182 * Deprecated distribution formats:
184 - The 'shar' and 'compress' distribution formats are deprecated, and
185 scheduled for removal in Automake 2.0. Accordingly, the use of the
186 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
187 (in the 'obsolete' category), and the recipes for the Automake-generated
188 targets 'dist-shar' and 'dist-tarZ' will unconditionally display
189 (non-fatal) warnings at make runtime.
191 * New configure runtime warnings about "rm -f" support:
193 - To simplify transition to Automake 2.0, the shell code expanded by
194 AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
195 'rm' program in PATH doesn't complain when called without any
196 non-option argument if the '-f' option is given (so that commands
197 like "rm -f" and "rm -rf" act as a no-op, instead of raising usage
198 error). If this is not the case,
199 the configure script is aborted, to call the attention of the user
200 on the issue, and invite him to fix his PATH. The checked 'rm'
201 behavior is very widespread in the wild, and will be required by
202 future POSIX version:
204 <http://austingroupbugs.net/view.php?id=542>
206 The user can still force the configure process to complete even in the
207 presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
208 environment variable to "yes". And the generated Makefiles should
209 still work correctly even when such broken 'rm' is used. But note
210 that this will no longer be the case with Automake 2.0 though, so, if
211 you encounter the warning, please report it to us ASAP (and try to fix
212 your environment as well).
214 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
218 * Documentation fixes:
220 - The documentation no longer mistakenly reports that the obsolete
221 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
222 to be removed in Automake 2.0.
226 - Byte-compilation of Emacs lisp files could fail spuriously on Solaris,
227 when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
229 - The same user-defined suffix being transformed into different
230 Automake-known suffixes in different Makefiles could confuse automake
231 and make it generate inconsistent Makefiles (automake bug#14441).
232 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule, and
233 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake would
234 have mistakenly put into 'Makefile.in' rules to compile *.c files
235 into object files, and into 'sub/Makefile.in' rules to compile *.cc
236 files into object files --- rather than the other way around.
241 - The test cases no longer have the executable bit set. This should
242 make it clear that they are not meant to be run directly; as
243 explained in t/README, they can only be run through the custom
244 'runtest' script, or by a "make check" invocation.
246 - The testsuite has seen the introduction of a new helper function
247 'run_make', and several related changes. These serve a two-fold
250 1. Removing brittleness due to the use of "make -e" in test cases.
252 2. Seamlessly allowing the use of parallel make ("make -j...") in
253 the test cases, even where redirection of make output is involved
254 (see automake bug#11413 for a description of the subtle issues in
257 - Few spurious failures have been fixed (they hit especially MinGW/MSYS).
258 See automake bugs #14493, #14494, #14495, #14498, #14499, #14500 and
261 - Some other minor miscellaneous changes and fixlets.
263 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
267 * Documentation fixes:
269 - The long-deprecated but still supported two-arguments invocation form
270 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
271 thing to do, given that support for such usage might need to remain
272 in place for an unspecified amount of time in order to cater to people
273 who want to define the version number for their package dynamically at
274 configure runtime (unfortunately, Autoconf does not yet support this
275 scenario, so we cannot delegate the work to it).
277 - The serial testsuite harness is no longer reported as "deprecated",
278 but as "discouraged". We have no plan to remove it, nor to make its
279 use cause runtime warnings.
281 - The parallel testsuite is no longer reported as "experimental"; it
282 is well tested, and should be stable now.
284 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
285 'dist-tarZ' options are obsolescent, and their use is deprecated
286 in the documentation.
288 - Other minor miscellaneous fixes and improvements; in particular,
289 some improvements in cross-references.
291 * Obsolescent features:
293 - Use of suffix-less info files (that can be specified through the
294 '@setfilename' macro in Texinfo input files) is discouraged, and
295 its use will raise warnings in the 'obsolete' category. Simply
296 use the '.info' extension for all your info files, transforming
299 @setfilename myprogram
303 @setfilename myprogram.info
305 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
306 is discouraged, and its use will raise warnings in the 'obsolete'
307 category. You are advised to simply use the '.texi' extension
312 - When the 'ustar' option is used, the generated configure script no
313 longer risks hanging during the tests for the availability of the
314 'pax' utility, even if the user running configure has a UID or GID
315 that requires more than 21 bits to be represented.
316 See automake bug#8343 and bug#13588.
318 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
319 again, as they did in Automake 1.12.x (albeit printing runtime
320 warnings in the 'obsolete' category). Removing them has turned
321 out to be a very bad idea, because it complicated distro packing
322 enormously. Making them issue fatal warnings, as we did in
323 Automake 1.13, has turned out to be a similarly very bad idea,
324 for exactly the same reason.
326 - aclocal will no longer error out if the first local m4 directory
327 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
328 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
329 a warning in the 'unsupported' category. This is done to support
330 some pre-existing real-world usages. See automake bug#13514.
332 - aclocal will no longer consider directories for extra m4 files more
333 than once, even if they are specified multiple times. This ensures
334 packages that specify both
336 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
337 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
339 will work correctly, even when the 'm4' directory contains no
340 package-specific files, but is used only to install third-party
341 m4 files (as can happen with e.g., "libtoolize --install").
342 See automake bug#13514.
344 - Analysis of make flags in Automake-generated rules has been made more
345 robust, and more future-proof. For example, in presence of make that
346 (like '-I') take an argument, the characters in said argument will no
347 longer be spuriously considered as a set of additional make options.
348 In particular, automake-generated rules will no longer spuriously
349 believe to be running in dry mode ("make -n") if run with an invocation
350 like "make -I noob"; nor will they believe to be running in keep-going
351 mode ("make -k") if run with an invocation like "make -I kool"
352 (automake bug#12554).
354 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
360 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
361 causes a clear and helpful error message, instead of obscure ones
362 (issue introduced in Automake 1.13).
364 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
370 - ylwrap renames properly header guards in generated header files
371 (*.h), instead of leaving Y_TAB_H.
373 - ylwrap now also converts header guards in implementation files
374 (*.c). Because ylwrap failed to rename properly #include in the
375 implementation files, current versions of Bison (e.g., 2.7)
376 duplicate the generated header file in the implementation file.
377 The header guard then protects the implementation file from
378 duplicate definitions from the header file.
380 * Version requirements:
382 - Autoconf 2.65 or greater is now required.
384 - The rules to build PDF and DVI output from Texinfo input now
385 require Texinfo 4.9 or later.
389 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
390 option) has been removed. See discussion about automake bug#11034
391 for more background: <http://debbugs.gnu.org/11034>.
393 - The deprecated aclocal option '--acdir' has been removed. You
394 should use the options '--automake-acdir' and '--system-acdir'
395 instead (which have been introduced in Automake 1.11.2).
397 - The following long-obsolete m4 macros have been removed:
399 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
400 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
401 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
402 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
403 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
404 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
405 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
406 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
407 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
408 of the now-removed automatic de-ANSI-fication
411 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
413 - Use of the long-deprecated two- and three-arguments invocation forms
414 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
415 though (albeit with a warning in the 'obsolete' category), to cater
416 for people who want to define the version number for their package
417 dynamically (e.g., from the current VCS revision). We'll have to
418 continue this support until Autoconf itself is fixed to allow better
419 support for such dynamic version numbers.
421 * Elisp byte-compilation:
423 - The byte compilation of '.el' files into '.elc' files is now done
424 with a suffix rule. This has simplified the compilation process, and
425 more importantly made it less brittle. The downside is that emacs is
426 now invoked once for each '.el' files, which cause some noticeable
427 slowdowns. These should however be mitigated on multicore machines
428 (which are becoming the norm today) if concurrent make ("make -j")
431 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
432 files in the same subdirectory; for example, byte-compiling of file
433 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
434 'foo.elc'. This behaviour is backward-incompatible with older
435 Automake versions, but it is more natural and more sane. See also
438 - The Emacs invocation performing byte-compilation of '.el' files honors
439 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
440 one is developer-reserved and the latter one user-reserved.
442 - The 'elisp-comp' script, once provided by Automake, has been rendered
443 obsoleted by the just-described changes, and thus removed.
445 * Changes to Automake-generated testsuite harnesses:
447 - The parallel testsuite harness (previously only enabled by the
448 'parallel-tests' option) is the default one; the older serial
449 testsuite harness will still be available through the use of the
450 'serial-tests' option (introduced in Automake 1.12).
452 - The 'color-tests' option is now unconditionally activated by default.
453 In particular, this means that testsuite output is now colorized by
454 default if the attached terminal seems to support ANSI escapes, and
455 that the user can force output colorization by setting the variable
456 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
457 for backward-compatibility, although it's a handled as a no-op now.
459 * Silent rules support:
461 - Support for silent rules is now always active in Automake-generated
462 Makefiles. So, although the verbose output is still the default,
463 the user can now always use "./configure --enable-silent-rules" or
464 "make V=0" to enable quieter output in the package he's building.
466 - The 'silent-rules' option has now become a no-op, preserved for
467 backward-compatibility only. In particular, its use no longer
468 disables the warnings in the 'portability-recursive' category.
472 - The rules to build PDF and DVI files from Texinfo input now require
473 Texinfo 4.9 or later.
475 - The rules to build PDF and DVI files from Texinfo input now use the
476 '--build-dir' option, to keep the auxiliary files used by texi2dvi
477 and texi2pdf around without cluttering the build directory, and to
478 make it possible to run the "dvi" and "pdf" recipes in parallel.
480 * Automatic remake rules and 'missing' script:
482 - The 'missing' script no longer tries to update the timestamp of
483 out-of-date files that require a maintainer-specific tool to be
484 remade, in case the user lacks such a tool (or has a too-old version
485 of it). It just gives a useful warning, and in some cases also a
486 tip about how to obtain such a tool.
488 - The missing script has thus become useless as a (poor) way to work
489 around the sketched-timestamps issues that can happen for projects
490 that keep generated files committed in their VCS repository. Such
491 projects are now encouraged to write a custom "fix-timestamps.sh"
492 script to avoid such issues; a simple example is provided in the
493 "CVS and generated files" chapter of the automake manual.
497 - The user can now define his own recursive targets that recurse
498 in the directories specified in $(SUBDIRS). This can be done by
499 specifying the name of such targets in invocations of the new
500 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
504 - Any failure in the recipe of the "tags", "ctags", "cscope" or
505 "cscopelist" targets in a subdirectory is now propagated to the
506 top-level make invocation.
508 - Tags are correctly computed also for files in _SOURCES variables that
509 only list files with non-standard suffixes (see automake bug#12372).
511 * Improvements to aclocal and related rebuilds rules:
513 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
514 are now traced by aclocal, and can be used to declare the local m4
515 include directories. Formerly, one had to specify it with an explicit
516 '-I' option to the 'aclocal' invocation.
518 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
519 Automake versions will warn about its use, and later version will
520 remove support for it altogether.
522 * The depcomp script:
524 - Dropped support for libtool 1.4.
526 - Various internal refactorings. They should cause no visible change,
527 but the chance for regression is there anyway, so please report any
528 unexpected or suspicious behaviour.
530 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
531 This should cause no problem, since icc 8.0 has been released in
532 December 2003 -- almost nine years ago.
534 - Support for tcc (the Tiny C Compiler) has been improved, and is now
535 handled through a dedicated 'tcc' mode.
539 - ylwrap generates header guards with a single '_' for series of non
540 alphabetic characters, instead of several. This is what Bison >=
543 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
545 Bugs fixed in 1.12.6:
547 * Python-related bugs:
549 - The default installation location for python modules has been improved
550 for Python 3 on Debian and Ubuntu systems, changing from:
552 ${prefix}/lib/python3/dist-packages
556 ${prefix}/lib/python3.x/site-packages
558 This change should ensure modules installed using the default ${prefix}
559 "/usr/local" are found by default by system python 3.x installations.
560 See automake bug#10227.
562 - Python byte-compilation supports the new layout mandated by PEP-3147,
563 with its __pycache__ directory (automake bug#8847).
565 * Build system issues:
567 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
568 Automake's own build system works correctly again (bug introduced
573 - The Vala-related tests has been changed to adjust to the removal of
574 the 'posix' profile in the valac compiler. See automake bug#12934
577 - Some spurious testsuite failures related to older tools and systems
580 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
586 - The AM_PROG_VALAC macro has been enhanced to takes two further
587 optional arguments; it's signature now being
589 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
590 [ACTION-IF-NOT-FOUND])
592 - By default, AM_PROG_VALAC no longer aborts the configure invocation
593 if the Vala compiler found is too old, but simply prints a warning
594 messages (as it did when the Vala compiler was not found). This
595 should avoid unnecessary difficulties for end users that just want
596 to compile the unmodified, distributed Vala-generated C sources,
597 but happens to have an old Vala compiler in their PATH. This fixes
600 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
601 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
602 This is a better default, because with it a triggered makefile rule
603 invoking a Vala compilation will clearly fail with an informative error
604 message like "valac: command not found", rather than silently, with
605 the error possibly going unnoticed or triggering harder-to-diagnose
606 fallout failures in later steps.
608 * Miscellaneous changes:
610 - automake and aclocal no longer honours the 'perllibdir' environment
611 variable. That had always been intended only as an hack required in
612 the testsuite, not meant for any use beyond that.
614 Bugs fixed in 1.12.5:
616 * Long-standing bugs:
618 - Automake no longer generates spurious remake rules invoking autoheader
619 to regenerate the template corresponding to header files specified after
620 the first one in AC_CONFIG_HEADERS (automake bug#12495).
622 - When wrapping Microsoft tools, the 'compile' script falls back to
623 finding classic 'libname.a' style libraries when 'name.lib' and
624 'name.dll.lib' aren't available.
626 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
630 * Warnings and deprecations:
632 - Warnings in the 'obsolete' category are enabled by default both in
633 automake and aclocal.
635 * Miscellaneous changes:
637 - Some testsuite weaknesses and spurious failures have been fixed.
639 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
643 * Miscellaneous changes:
645 - The '.m4' files provided by Automake no longer define serial numbers.
646 This should cause no difference in the behaviour of aclocal though.
648 - Some testsuite weaknesses and spurious failures have been fixed.
650 - There is initial support for automatic dependency tracking with the
651 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
653 Bugs fixed in 1.12.3:
655 * Long-standing bugs:
657 - Instead of renaming only self-references of files (typically for
658 #lines), ylwrap now also renames references to the other generated
659 files. This fixes support for GLR and C++ parsers from Bison (PR
660 automake/491 and automake bug#7648): 'parser.c' now properly
661 #includes 'parser.h' instead of 'y.tab.h'.
663 - Generated files unknown to ylwrap are now preserved. This fixes
664 C++ support for Bison (automake bug#7648): location.hh and the
665 like are no longer discarded.
667 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
671 * Warnings and deprecations:
673 - Automake now issues a warning (in the 'portability' category) if
674 'configure.in' is used instead of 'configure.ac' as the Autoconf
675 input file. Such a warning will also be present in the next
676 Autoconf version (2.70).
680 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
681 order (as done by the other recursive rules), rather than in the
682 inverse order. They used to do that in order to work a round a
683 limitation in an older implementation of the automatic dependency
684 tracking support, but that limitation had been lifted years ago
685 already, when the automatic dependency tracking based on side-effects
686 of compilation had been introduced.
688 - Cleaning rules for compiled objects (both "plain" and libtool) work
689 better when subdir objects are involved, not triggering a distinct
690 'rm' invocation for each such object. They do so by removing *any*
691 compiled object file that is in the same directory of a subdir
692 object. See automake bug#10697.
694 * Silent rules support:
696 - A new predefined $(AM_V_P) make variable is provided; it expands
697 to a shell conditional that can be used in recipes to know whether
698 make is being run in silent or verbose mode.
700 Bugs fixed in 1.12.2:
702 * SECURITY VULNERABILITIES!
704 - The 'distcheck' recipe no longer grants temporary world-write
705 permissions on the extracted distdir. Even if such rights were
706 only granted for a vanishingly small time window, the implied
707 race condition proved to be enough to allow a local attacker
708 to run arbitrary code with the privileges of the user running
709 "make distcheck". This is CVE-2012-3386.
711 * Long-standing bugs:
713 - The "recheck" targets behaves better in the face of build failures
714 related to previously failed tests. For example, if a test is a
715 compiled program that must be rerun by "make recheck", and its
716 compilation fails, it will still be rerun by further "make recheck"
717 invocations. See automake bug#11791.
719 * Bugs introduced by 1.12.1:
721 - Automake provides once again the '$(mkdir_p)' make variable and the
722 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
723 for better backward-compatibility.
725 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
729 * New supported languages:
731 - Support for Objective C++ has been added; it should work similarly to
732 the support for Objective C.
734 * Deprecated obsolescent features:
736 - Use of the long-deprecated two- and three-arguments invocation forms
737 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
738 category. Starting from some future major Automake release (likely
739 post-1.13), such usages will no longer be allowed.
741 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
742 now deprecated (its use triggers a warning in the 'obsolete' category).
743 It will be removed in the next major Automake release (1.13).
745 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
746 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
747 m4 macro are deprecated, eliciting a warning in the 'obsolete'
750 * Miscellaneous changes:
752 - The Automake test cases now require a proper POSIX-conforming shell.
753 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
754 be accepted. In most cases, the user shouldn't have to specify such
755 POSIX shell explicitly, since it will be looked up at configure time.
756 Still, when this lookup fails, or when the user wants to override its
757 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
758 to the shell that will be used to run the Automake test cases).
760 Bugs fixed in 1.12.1:
762 * Bugs introduced by 1.12:
764 - Several weaknesses in Automake's own build system and test suite
767 * Bugs introduced by 1.11.3:
769 - When given non-option arguments, aclocal rejects them, instead of
770 silently ignoring them.
772 * Long-standing bugs:
774 - When the 'color-tests' option is in use, forcing of colored testsuite
775 output through "AM_COLOR_TESTS=always" works even if the terminal is
776 a non-ANSI one, i.e., if the TERM environment variable has a value of
779 - Several inefficiencies and poor performances in the implementation
780 of the parallel-tests 'check' and 'recheck' targets have been fixed.
782 - The post-processing of output "#line" directives done the ylwrap
783 script is more faithful w.r.t. files in a subdirectory; for example,
784 if the processed file is "src/grammar.y", ylwrap will correctly
785 produce directives like:
786 #line 7 "src/grammar.y"
791 * Bugs with new Perl versions:
793 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
795 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
799 * Obsolete features removed:
801 - The never documented nor truly used script 'acinstall' has been
804 - Support for automatic de-ANSI-fication has been removed.
806 - The support for the "obscure" multilib feature has been removed
807 from Automake core (but remains available in the 'contrib/'
808 directory of the Automake distribution).
810 - Support for ".log -> .html" conversion and the check-html and
811 recheck-html targets has been removed from Automake core (but
812 remains available in the 'contrib/' directory of the Automake
815 - The deprecated 'lzma' compression format for distribution archives
816 has been removed, in favor of 'xz' and 'lzip'.
818 - The obsolete AM_WITH_REGEX macro has been removed.
820 - The long-deprecated options '--output-dir', '--Werror' and
821 '--Wno-error' have been removed.
823 - The chapter on the history of Automake has been moved out of the
824 reference manual, into a new dedicated Texinfo file.
828 - New 'cscope' target to build a cscope database for the source tree.
830 * Changes to Automake-generated testsuite harnesses:
832 - The new automake option 'serial-tests' has been introduced. It can
833 be used to explicitly instruct automake to use the older serial
834 testsuite harness. This is still the default at the moment, but it
835 might change in future versions.
837 - The 'recheck' target (provided by the parallel testsuite harness) now
838 depends on the 'all' target. This allows for a better user-experience
839 in test-driven development. See automake bug#11252.
841 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
842 and unexpected or internal error, or a failure to set up the test case
843 scenario) have their outcome reported as an 'ERROR' now. Previous
844 versions of automake reported such an outcome as a 'FAIL' (the only
845 difference with normal failures being that hard errors were counted
846 as failures even when the test originating them was listed in
849 - The testsuite summary displayed by the parallel-test harness has a
850 completely new format, that always list the numbers of passed, failed,
851 xfailed, xpassed, skipped and errored tests, even when these numbers
852 are zero (but using smart coloring when the color-tests option is in
855 - The default testsuite driver offered by the 'parallel-tests' option is
856 now implemented (partly at least) with the help of automake-provided
857 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
858 on code in the generated Makefile.in.
859 This has two noteworthy implications. The first one is that projects
860 using the 'parallel-tests' option should now either run automake with
861 the '--add-missing' option, or manually copy the 'test-driver' script
862 into their tree. The second, and more important, implication is that
863 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
864 no longer be used to define a test runner, and the command specified
865 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
866 program or script. For example, this is still a valid usage (albeit
869 TESTS_ENVIRONMENT = \
870 if test -n '$(STRICT_TESTS)'; then \
871 maybe_errexit='-e'; \
875 LOG_COMPILER = $(SHELL) $$maybe_errexit
877 OTOH, this is no longer a valid usage:
879 TESTS_ENVIRONMENT = \
880 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
884 TESTS_ENVIRONMENT = \
885 run_with_perl_or_shell () \
887 if grep -q '^#!.*perl' $$1; then
893 LOG_COMPILER = run_with_perl_or_shell
895 - The package authors can now use customary testsuite drivers within
896 the framework provided by the 'parallel-tests' testsuite harness.
897 Consistently with the existing syntax, this can be done by defining
898 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
900 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
901 to redirect/define file descriptors used by the test scripts.
903 - The parallel-tests harness generates now, in addition the '.log' files
904 holding the output produced by the test scripts, a new set of '.trs'
905 files, holding "metadata" derived by the execution of the test scripts;
906 among such metadata are the outcomes of the test cases run by a script.
908 - Initial and still experimental support for the TAP test protocol is
911 * Changes to Yacc and Lex support:
913 - C source and header files derived from non-distributed Yacc and/or
914 Lex sources are now removed by a simple "make clean" (while they were
915 previously removed only by "make maintainer-clean").
917 - Slightly backward-incompatible change, relevant only for use of Yacc
918 with C++: the extensions of the header files produced by the Yacc
919 rules are now modelled after the extension of the corresponding
920 sources. For example, yacc files named "foo.y++" and "bar.yy" will
921 produce header files named "foo.h++" and "bar.hh" respectively, where
922 they would have previously produced header files named simply "foo.h"
923 and "bar.h". This change offers better compatibility with 'bison -o'.
925 * Miscellaneous changes:
927 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
928 rather than 1, if the vala compiler found is too old.
930 - The build system of Automake itself now avoids the use of make
931 recursion as much as possible.
933 - Automake now prefers to quote 'like this' or "like this", rather
934 than `like this', in diagnostic message and generated Makefiles,
935 to accommodate the new GNU Coding Standards recommendations.
937 - Automake has a new option '--print-libdir' that prints the path of the
938 directory containing the Automake-provided scripts and data files.
940 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
942 - The rules to create pdf, dvi and ps output from Texinfo files now
943 works better with modern 'texi2dvi' script, by explicitly passing
944 it the '--clean' option to ensure stray auxiliary files are not
945 left to clutter the build directory.
947 - Automake can now generate silenced rules for texinfo outputs.
949 - Some auxiliary files that are automatically distributed by Automake
950 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
951 C sources) might now be listed in the DIST_COMMON variable in many
952 Makefile.in files, rather than in the top-level one.
954 - Messages of types warning or error from 'automake' and 'aclocal'
955 are now prefixed with the respective type, and presence of -Werror
958 - Automake's early configure-time sanity check now tries to avoid
959 sleeping for a second, which slowed down cached configure runs
960 noticeably. In that case, it will check back at the end of the
961 configure script to ensure that at least one second has passed, to
962 avoid time stamp issues with makefile rules rerunning autotools
965 - The warnings in the category 'extra-portability' are now enabled by
966 '-Wall'. In previous versions, one has to use '-Wextra-portability'
971 - Various minor bugfixes for recent or long-standing bugs.
973 * Bugs introduced by 1.11:
975 - The AM_COND_IF macro also works if the shell expression for the
976 conditional is no longer valid for the condition.
978 - The automake-provided parallel testsuite harness no longer fails
979 with BSD make used in parallel mode when there are test scripts in
980 a subdirectory, like in:
982 TESTS = sub/foo.test sub/bar.test
984 * Long-standing bugs:
986 - Automake's own build system finally have a real "installcheck" target.
988 - Vala-related cleanup rules are now more complete, and work better in
991 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
992 now automatically distributed also if the directory of the auxiliary
993 files coincides with the top-level directory.
995 - Automake now detects the presence of the '-d' flag in the various
996 '*YFLAGS' variables even when their definitions involve indirections
997 through other variables, such as in:
999 AM_YFLAGS = $(foo_opts)
1001 - Automake now complains if a '*YFLAGS' variable has any conditional
1002 content, not only a conditional definition.
1004 - Explicit enabling and/or disabling of Automake warning categories
1005 through the '-W...' options now always takes precedence over the
1006 implicit warning level implied by Automake strictness (foreign, gnu
1007 or gnits), regardless of the order in which such strictness and
1008 warning flags appear. For example, a setting like:
1009 AUTOMAKE_OPTIONS = -Wall --foreign
1010 will cause the warnings in category 'portability' to be enabled, even
1011 if those warnings are by default disabled in 'foreign' strictness.
1013 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1015 Bugs fixed in 1.11.5:
1017 * Bugs introduced by 1.11.3:
1019 - Vala files with '.vapi' extension are now recognized and handled
1020 correctly again. See automake bug#11222.
1022 - Vala support work again for projects that contain some program
1023 built from '.vala' (and possibly '.c') sources and some other
1024 program built from '.c' sources *only*. See automake bug#11229.
1026 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1030 * Miscellaneous changes:
1032 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
1033 symbol index) modifiers as well as the "s" action, as the symbol index
1034 is created unconditionally by Microsoft lib. Also, the "q" (quick)
1035 action is now a synonym for "r" (replace). Also, the script has been
1036 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
1038 - When the 'compile' script is used to wrap MSVC, it now accepts an
1039 optional space between the -I, -L and -l options and their respective
1040 arguments, for better POSIX compliance.
1042 - There is an initial, experimental support for automatic dependency
1043 tracking with tcc (the Tiny C Compiler). Its associated depmode is
1044 currently recognized as "icc" (but this and other details are likely
1045 to change in future versions).
1047 - Automatic dependency tracking now works also with the IBM XL C/C++
1048 compilers, thanks to the new new depmode 'xlc'.
1050 Bugs fixed in 1.11.4:
1052 * Bugs introduced by 1.11.2:
1054 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
1055 no longer cause spurious failures upon "make install".
1057 - The user can now instruct the 'uninstall-info' rule not to update
1058 the '${infodir}/dir' file by exporting the environment variable
1059 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
1060 with how the 'install-info' rule operates since automake 1.11.2.
1062 * Long-standing bugs:
1064 - It is now possible for a foo_SOURCES variable to hold Vala sources
1065 together with C header files, as well as with sources and headers for
1066 other supported languages (e.g., C++). Previously, only mixing C and
1067 Vala sources was supported.
1069 - If "aclocal --install" is used, and the first directory specified with
1070 '-I' is non-existent, aclocal will now create it before trying to copy
1073 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
1074 install rules to create an empty $(foodir) directory; for example, if
1075 Makefile.am contains something like:
1077 pkglibexec_SCRIPTS =
1079 pkglibexec_SCRIPTS += bar.sh
1082 the $(pkglibexec) directory will not be created upon "make install".
1084 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1088 * Miscellaneous changes:
1090 - Automake's own build system is more silent by default, making use of
1091 the 'silent-rules' option.
1093 - The master copy of the 'gnupload' script is now maintained in gnulib,
1096 - The 'missing' script no longer tries to wrap calls to 'tar'.
1098 - "make dist" no longer wraps 'tar' invocations with the 'missing'
1099 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
1100 shouldn't be using BTW ;-) no longer invokes the 'missing' script
1101 to wrap tar, but simply invokes the 'tar' program itself.
1103 - "make dist" can now create lzip-compressed tarballs.
1105 - In the Automake info documentation, the Top node and the nodes about
1106 the invocation of the automake and aclocal programs have been renamed;
1107 now, calling "info automake" will open the Top node, while calling
1108 "info automake-invocation" and "info aclocal-invocation" will access
1109 the nodes about the invocation of respectively automake and aclocal.
1111 - Automake is now distributed as a gzip-compressed and an xz-compressed
1112 tarball. Previously, bzip2 was used instead of xz.
1114 - The last relics of Python 1.5 support have been removed from the
1115 AM_PATH_PYTHON macro.
1117 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
1118 and adds them to the normal list of dependencies, but without
1119 overwriting the foo_DEPENDENCIES variable, which is normally computed
1122 Bugs fixed in 1.11.3:
1124 * Bugs introduced by 1.11.2:
1126 - Automake now correctly recognizes the prefix/primary combination
1127 'pkglibexec_SCRIPTS' as valid.
1129 - The parallel-tests harness no longer trips on sed implementations
1130 with stricter limits on the length of input lines (problem seen at
1131 least on Solaris 8).
1133 * Long-standing bugs:
1135 - The "deleted header file problem" for *.am files is avoided by stub
1136 rules. This allows 'make' to trigger a rerun of 'automake' also if
1137 some previously needed '.am' file has been removed.
1139 - The 'silent-rules' option now generates working makefiles even
1140 for the uncommon 'make' implementations that do not support the
1141 nested-variables extension to POSIX 2008. For such 'make'
1142 implementations, whether a build is silent is determined at
1143 configure time, and cannot be overridden at make time with
1144 "make V=0" or "make V=1".
1146 - Vala support now works better in VPATH setups.
1148 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1152 * Changes to aclocal:
1154 - The `--acdir' option is deprecated. Now you should use the new options
1155 `--automake-acdir' and `--system-acdir' instead.
1157 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1158 colon-separated list of additional directories to search after the
1159 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1160 and before the system acdir (by default ${prefix}/share/aclocal).
1162 * Miscellaneous changes:
1164 - The Automake support for automatic de-ANSI-fication has been
1165 deprecated. It will probably be removed in the next major Automake
1168 - The `lzma' compression scheme and associated automake option `dist-lzma'
1169 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1171 - You may adjust the compression options used in dist-xz and dist-bzip2.
1172 The default is now merely -e for xz, but still -9 for bzip; you may
1173 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1174 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1176 - The `compile' script now converts some options for MSVC for a better
1177 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1179 - The py-compile script now accepts empty arguments passed to the options
1180 `--destdir' and `--basedir', and complains about unrecognized options.
1181 Moreover, a non-option argument or a special `--' argument terminates
1182 the list of options.
1184 - A developer that needs to pass specific flags to configure at "make
1185 distcheck" time can now, and indeed is advised to, do so by defining
1186 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1187 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1188 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1189 user; still, the old Makefile.am files that used to define it will
1190 still continue to work as before.
1192 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1193 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1194 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1195 is run with -Wextra-portability and -Werror.
1197 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1198 file generated by automake-provided rules by defining the special make
1199 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1201 - The `install-info' rule can now be instructed not to create/update
1202 the `${infodir}/dir' file, by exporting the new environment variable
1203 `AM_UPDATE_INFO_DIR' to the value "no".
1205 Bugs fixed in 1.11.2:
1207 * Bugs introduced by 1.11:
1209 - The parallel-tests driver no longer produces erroneous results with
1210 Tru64/OSF 5.1 sh upon unreadable log files.
1212 - The `parallel-tests' test driver does not report spurious successes
1213 when used with concurrent FreeBSD make (e.g., "make check -j3").
1215 - When the parallel-tests driver is in use, automake now explicitly
1216 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1217 instead of issuing confusing and apparently unrelated error messages
1218 (e.g., "non-POSIX variable name", "bad characters in variable name",
1219 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1220 silently producing broken `Makefile.in' files.
1222 - The `silent-rules' option now truly silences all compile rules, even
1223 when dependency tracking is disabled. Also, when `silent-rules' is
1224 not used, `make' output no longer contains spurious backslash-only
1225 lines, thus once again matching what Automake did before 1.11.
1227 - The AM_COND_IF macro also works if the shell expression for the
1228 conditional is no longer valid for the condition.
1230 * Long-standing bugs:
1232 - The order of Yacc and Lex flags is fixed to be consistent with other
1233 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1234 $(LFLAGS), so that the user variables override the developer variables.
1236 - "make distcheck" now correctly complains also when "make uninstall"
1237 leaves one and only one file installed in $(prefix).
1239 - A "make uninstall" issued before a "make install", or after a mere
1240 "make install-data" or a mere "make install-exec" does not spuriously
1243 - Automake now warns about more primary/directory invalid combinations,
1244 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1246 - Rules generated by Automake now try harder to not change any files when
1247 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1248 Yacc source files and the rule to update config.h.
1250 - Several scripts and the parallel-tests testsuite driver now exit with
1251 the right exit status upon receiving a signal.
1253 - A per-Makefile.am setting of -Werror does not erroneously carry over
1254 to the handling of other Makefile.am files.
1256 - The code for automatic dependency tracking works around a Solaris
1257 make bug triggered by sources containing repeated slashes when the
1258 `subdir-objects' option was used.
1260 - The makedepend and hp depmodes now work better with VPATH builds.
1262 - Java sources specified with check_JAVA are no longer compiled for
1263 "make all", but only for "make check".
1265 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1266 and error out if `javadir' is undefined, instead of silently producing
1267 a broken Makefile.in.
1269 - aclocal and automake now honour the configure-time definitions of
1270 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1272 - The `install-info' recipe no longer tries to guess whether the
1273 `install-info' program is from Debian or from GNU, and adaptively
1274 change its behaviour; this has proven to be frail and easy to
1277 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1279 Bugs fixed in 1.11.1:
1281 - Lots of minor bugfixes.
1283 * Bugs introduced by 1.11:
1285 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1286 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1288 * Long standing bugs:
1290 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1291 even if the `--prefix' argument pointed outside of a system directory.
1292 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1293 `get_python_lib' function if it points outside the configured prefix,
1294 unless the `--prefix' argument was either `/usr' or below `/System'.
1296 - The testsuite does not try to change the mode of `ltmain.sh' files from
1297 a Libtool installation (symlinked to test directories) any more.
1299 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1300 tools are preferred in a cross-compile setup.
1302 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1303 This fixes a race condition where untrusted users could modify files
1304 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1305 build directory was world-searchable. This is CVE-2009-4029.
1307 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1311 * Version requirements:
1313 - Autoconf 2.62 or greater is required.
1315 * Changes to aclocal:
1317 - The autoconf version check implemented by aclocal in aclocal.m4
1318 (and new in Automake 1.10) is degraded to a warning. This helps
1319 in the common case where the Autoconf versions used are compatible.
1321 * Changes to automake:
1323 - The automake program can run multiple threads for creating most
1324 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1325 with interpreter-based threads enabled. Set the environment variable
1326 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1327 enable this experimental feature.
1329 * Changes to Libtool support:
1331 - Libtool generic flags are now passed to the install and uninstall
1334 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1335 config.lt is removed correctly now.
1337 * Languages changes:
1339 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1340 Fortran, and Ratfor).
1342 - For files with extension .f90, .f95, .f03, or .f08, the flag
1343 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1345 - Files with extension .sx are also treated as preprocessed assembler.
1347 - The default source file extension (.c) can be overridden with
1348 AM_DEFAULT_SOURCE_EXT now.
1350 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1353 - AM_PATH_PYTHON honors python's idea about the site directory.
1355 - There is initial support for the Vala programming language, when using
1356 Vala 0.7.0 or later.
1358 * Miscellaneous changes:
1360 - Automake development is done in a git repository on Savannah now, see
1362 http://git.sv.gnu.org/gitweb/?p=automake.git
1364 A read-only CVS mirror is provided at
1366 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1367 checkout -d automake HEAD
1369 - "make dist" can now create xz-compressed tarballs,
1370 as well as (deprecated?) lzma-compressed tarballs.
1372 - `automake --add-missing' will by default install the GPLv3 file as
1373 COPYING if it is missing. It will also warn that the license file
1374 should be added to source control. Note that Automake will never
1375 overwrite an existing COPYING file, even when the `--force-missing'
1378 - The manual is now distributed under the terms of the GNU FDL 1.3.
1380 - Automake ships and installs man pages for automake and aclocal now.
1382 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1384 - install-sh supports -C, which does not update the installed file
1385 (and its time stamps) if the contents did not change.
1387 - The `gnupload' script has been revamped.
1389 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1391 - The targets `install' and `uninstall' are more efficient now, in that
1392 for example multiple files from one Automake variable such as
1393 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1394 invocation if they do not have to be renamed.
1396 Both install and uninstall may sometimes enter (`cd' into) the target
1397 installation directory now, when no build-local scripts are used.
1399 Both install and uninstall do not fail anymore but do nothing if an
1400 installation directory variable like `bindir' is set to the empty string.
1402 For built-in rules, `make install' now fails reliably if installation
1403 of a file failed. Conversely, `make uninstall' even succeeds when
1404 issued multiple times.
1406 These changes may need some adjustments from users: For example,
1407 some `install' programs refuse to install multiple copies of the
1408 same file in one invocation, so you may need to remove duplicate
1409 entries from file lists.
1411 Also, within one set of files, say, nobase_data_DATA, the order of
1412 installation may be changed, or even unstable among different hosts,
1413 due to the use of associative arrays in awk. The increased use of
1414 awk matches a similar move in Autoconf to provide for better scaling.
1416 Further, most undocumented per-rule install command variables such as
1417 binSCRIPT_INSTALL have been removed because they are not needed any
1418 more. Packages which use them should be using the appropriate one of
1419 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1420 counterpart, depending on the type of files and the need for automatic
1421 target directory creation.
1423 - The "deleted header file problem" for *.m4 files is avoided by
1424 stub rules. This allows `make' to trigger a rerun of `aclocal'
1425 also if some previously needed macro file has been removed.
1427 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1428 an otherwise up to date tree.
1430 - The `color-tests' option causes colored test result output on terminals.
1432 - The `parallel-tests' option enables a new test driver that allows for
1433 parallel test execution, inter-test dependencies, lazy test execution
1434 for unit-testing, re-testing only failed tests, and formatted result output
1435 as RST (reStructuredText) and HTML. Enabling this option may require some
1436 changes to your test suite setup; see the manual for details.
1438 - The `silent-rules' option enables Linux kernel-style silent build output.
1439 This option requires the widely supported but non-POSIX `make' feature
1440 of recursive variable expansion, so do not use it if your package needs
1441 to build with `make' implementations that do not support it.
1443 To enable less verbose build output, the developer has to use the Automake
1444 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1445 macro. The user may then set the default verbosity by passing the
1446 `--enable-silent-rules' option to `configure'. At `make' run time, this
1447 default may be overridden using `make V=0' for less verbose, and `make V=1'
1448 for backward-compatible verbose output.
1450 - New prefix `notrans_' for manpages which should not be transformed
1451 by --program-transform.
1453 - New macro AM_COND_IF for conditional evaluation and conditional
1456 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1457 remove the file in a non-VPATH build. Such setups work with Autoconf
1460 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1461 the default setting.
1463 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1464 useful especially for multi-line values.
1466 - Automake's early configure-time sanity check now diagnoses an
1467 unsafe absolute source directory name and makes configure fail.
1469 - The Automake macros and rules cope better with whitespace in the
1470 current directory name, as long as the relative path to `configure'
1471 does not contain whitespace. To this end, the values of `$(MISSING)'
1472 and `$(install_sh)' may contain suitable quoting, and their expansion
1473 might need `eval'uation if used outside of a makefile. These
1474 undocumented variables may be used in several documented macros such
1475 as $(AUTOCONF) or $(MAKEINFO).
1479 * Long-standing bugs:
1481 - Fix aix dependency tracking for libtool objects.
1483 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1484 unnecessary use of the `compile' script.
1486 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1487 correct `-rpath' argument is used now.
1489 - `config.status --file=Makefile depfiles' now also works with the
1490 extra quoting used internally by Autoconf 2.62 and newer
1491 (it used to work only without the `--file=' bit).
1493 - The `missing' script works better with versioned tool names.
1495 - Semantics for `missing help2man' have been revamped:
1497 Previously, if `help2man' was not present, `missing help2man' would have
1498 the following semantics: if some man page was out of date but present, then
1499 a warning would be printed, but the exit status was 0. If the man page was
1500 not present at all, then `missing' would create a replacement man page
1501 containing an error message, and exit with a status of 2. This does not play
1502 well with `make': the next run will see this particular man page as being up
1503 to date, and will only error out on the next generated man page, if any;
1504 repeat until all pages are done. This was not desirable.
1506 These are the new semantics: if some man page is not present, and help2man
1507 is not either, then `missing' will warn and generate the replacement page
1508 containing the error message, but exit successfully. However, `make dist'
1509 will ensure that no such bogus man pages are packaged into a tarball.
1511 - Targets provided by automake behave better with `make -n', in that they
1512 take care not to create files.
1514 - `config.status Makefile... depfiles' works fine again in the presence of
1515 disabled dependency tracking.
1517 - The default no-op recursive rules for these targets also work with BSD make
1518 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1520 - `make distcheck' works also when both a directory and some file below it
1521 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1523 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1524 `make mostlyclean' any more; only the LaTeX by-products are.
1526 - Renamed objects also work with the `subdir-objects' option and
1527 source file languages which Automake does not know itself.
1529 - `automake' now correctly complains about variable assignments which are
1530 preceded by a comment, extend over multiple lines with backslash-escaped
1531 newlines, and end in a comment sign. Previous versions would silently
1532 and wrongly ignore such assignments completely.
1534 * Bugs introduced by 1.10:
1536 - Fix output of dummy dependency files in presence of post-processed
1537 Makefile.in's again, but also cope with long lines.
1539 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1540 that have been declared as programs in the same Makefile.
1541 This is for consistency with the analogous change to TESTS in 1.10.
1543 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1544 followed by directories containing config headers.
1546 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1550 * Version requirements:
1552 - Autoconf 2.60 or greater is required.
1554 - Perl 5.6 or greater is required.
1556 * Changes to aclocal:
1558 - aclocal now also supports -Wmumble and -Wno-mumble options.
1560 - `dirlist' entries (for the aclocal search path) may use shell
1561 wildcards such as `*', `?', or `[...]'.
1563 - aclocal supports an --install option that will cause system-wide
1564 third-party macros to be installed in the local directory
1565 specified with the first -I flag. This option also uses #serial
1566 lines in M4 files to upgrade local macros.
1568 The new aclocal options --dry-run and --diff help to review changes
1569 before they are installed.
1571 - aclocal now outputs an autoconf version check in aclocal.m4 in
1572 projects using automake.
1574 For a few years, automake and aclocal have been calling autoconf
1575 (or its underlying engine autom4te) to accurately retrieve the
1576 data they need from configure.ac and its siblings. Doing so can
1577 only work if all autotools use the same version of autoconf. For
1578 instance a Makefile.in generated by automake for one version of
1579 autoconf may stop working if configure is regenerated with another
1580 version of autoconf, and vice versa.
1582 This new version check ensures that the whole build system has
1583 been generated using the same autoconf version.
1585 * Support for new Autoconf macros:
1587 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1589 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1590 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1591 in different directories. However, only one instance of such a
1592 library objects directory is supported.
1594 * Change to Libtool support:
1596 - Libtool generic flags (those that go before the --mode=MODE option)
1597 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1599 * Yacc and Lex changes:
1601 - The rebuild rules for distributed Yacc and Lex output will avoid
1602 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1605 - ylwrap is now always used for lex and yacc source files,
1606 regardless of whether there is more than one source per directory.
1608 * Languages changes:
1610 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1611 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1612 tracking, unlike non-preprocessed assembler (*.s).
1614 - subdir-object mode works now with Assembler. Automake assumes
1615 that the compiler understands `-c -o'.
1617 - Preprocessed assembler (*.S) compilation now also honors
1618 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1620 - Improved support for Objective C:
1621 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1622 - A new section of the manual documents the support.
1624 - New support for Unified Parallel C:
1625 - AM_PROG_UPC looks for a UPC compiler.
1626 - A new section of the manual documents the support.
1628 - Per-target flags are now correctly handled in link rules.
1630 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1631 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1632 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1633 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1635 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1636 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1637 is expected to work (and actually works during compilation).
1639 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1640 "in addition to" breaks backward compatibility with older versions.
1641 If your package used both variables, as in
1643 AM_LDFLAGS = common flags
1644 bin_PROGRAMS = a b c
1645 a_LDFLAGS = more flags
1648 and assumed *_LDFLAGS would sum up, you should rewrite it as
1650 AM_LDFLAGS = common flags
1651 bin_PROGRAMS = a b c
1652 a_LDFLAGS = $(AM_LDFLAGS) more flags
1655 This new behavior of *_LDFLAGS is more coherent with other
1656 per-target variables, and the way *_LDFLAGS variables were
1657 considered internally.
1659 * New installation targets:
1661 - New targets mandated by GNU Coding Standards:
1666 By default they will only install Texinfo manuals.
1667 You can customize them with *-local variants:
1673 - The undocumented recursive target `uninstall-info' no longer exists.
1674 (`uninstall' is in charge of removing all possible documentation
1675 flavors, including optional formats such as dvi, ps, or info even
1676 when `no-installinfo' is used.)
1678 * Miscellaneous changes:
1680 - Automake no longer complains if input files for AC_CONFIG_FILES
1681 are specified using shell variables.
1683 - clean, distribution, or rebuild rules are normally disabled for
1684 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1685 AC_CONFIG_LINK specified using shell variables. However, if these
1686 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1687 be able to output rules anyway.
1688 (See the Automake documentation for AC_CONFIG_FILES.)
1690 - $(EXEEXT) is automatically appended to filenames of TESTS
1691 that have been declared as programs in the same Makefile.
1692 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1694 - `-Wportability' has finally been turned on by default for `gnu' and
1695 `gnits' strictness. This means, automake will complain about %-rules
1696 or $(GNU Make functions) unless you switch to `foreign' strictness or
1697 use `-Wno-portability'.
1699 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1700 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1701 $(mkdir_p) variable is still defined (to the same value as
1702 $(MKDIR_P)) but should be considered obsolete. If you are using
1703 $(mkdir_p) in some of your rules, please plan to update them to
1704 $(MKDIR_P) at some point.
1706 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1707 They still work in this release, but may be withdrawn in a future one.
1709 - Inline compilation rules for gcc3-style dependency tracking are
1712 - Automake installs a "Hello World!" example package in $(docdir).
1713 This example is used throughout the new "Autotools Introduction"
1714 chapter of the manual.
1716 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1720 * Makefile.in bloat reduction:
1722 - Inference rules are used to compile sources in subdirectories when
1723 the `subdir-objects' option is used and no per-target flags are
1724 used. This should reduce the size of some projects a lot, because
1725 Automake used to output an explicit rule for each such object in
1728 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1729 object that must be built with explicit rules. It just outputs
1730 the rules required to build the kind of object considered: either
1731 the two .o and .obj rules for usual objects, or the .lo rule for
1734 * Change to Libtool support:
1736 - Libtool tags are used with libtool versions that support them.
1737 (I.e., with Libtool 1.5 or greater.)
1739 - Automake is now able to handle setups where a libtool library is
1740 conditionally installed in different directories, as in
1743 lib_LTLIBRARIES = liba.la
1745 pkglib_LTLIBRARIES = liba.la
1747 liba_la_SOURCES = ...
1749 * Changes to aclocal:
1751 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1752 really evaluated, before it decides to include them in aclocal.m4.
1753 This solves nasty problems with conditional redefinitions of
1754 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1755 *.m4 files to be included in any project using these macros.
1756 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1757 most famous instance of this bug.)
1759 - Do not complain about missing conditionally AC_REQUIREd macros
1760 that are not actually used. In 1.8.x aclocal would correctly
1761 determine which of these macros were really needed (and include
1762 only these in the package); unfortunately it would also require
1763 all of them to be present in order to run. This created
1764 situations were aclocal would not work on a tarball distributing
1765 all the macros it uses. For instance running aclocal on a project
1766 containing only the subset of the Gettext macros in use by the
1767 project did not work, because gettext conditionally requires other
1770 * Portability improvements:
1772 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1773 tar-pax. The new option filename-length-max=99 helps diagnosing
1774 filenames that are too long for tar-v7. (PR/414)
1776 - Variables augmented with `+=' are now automatically flattened (i.e.,
1777 trailing backslashes removed) and then wrapped around 80 columns
1778 (adding trailing backslashes). In previous versions, a long series
1784 would result in a single-line definition of VAR that could possibly
1785 exceed the maximum line length of some make implementations.
1787 Non-augmented variables are still output as they are defined in
1792 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1793 Works the same as the old Fortran 77 implementation; just replace
1794 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1795 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1797 - Support for conditional _LISP.
1799 - Support for conditional -hook and -local rules (PR/428).
1801 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1803 - Automake will not write any Makefile.ins after the first error it
1804 encounters. The previous Makefile.ins (if any) will be left in
1805 place. (Warnings will not prevent output, but remember they can
1806 be turned into errors with -Werror.)
1808 - The restriction that SUBDIRS must contain direct children is gone.
1811 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1812 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1814 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1816 Bugs fixed in 1.8.5:
1818 * Long-standing bugs:
1820 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1821 so that `make distclean' and `make maintainer-clean' can work.
1823 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1825 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1827 - Polish diagnostic when no input file is found.
1829 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1831 Bugs fixed in 1.8.4:
1833 * Long-standing bugs:
1835 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1836 overridden by the user.
1838 - Honor PATH_SEPARATOR in various places of the Automake package, for
1841 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1844 - Fix install-sh so it can install the `mv' binary... using `mv'.
1846 - Fix tru64 dependency tracking for libtool objects.
1848 - Work around Exuberant Ctags when creating a TAGS files in a directory
1849 without files to scan but with subdirectories to include.
1851 * Bugs introduced by 1.8:
1853 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1854 not defined in the same conditions as the _LDADD that uses it.
1856 - Do not warn when JAVAROOT is overridden, this is legitimate.
1858 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1860 Bugs fixed in 1.8.3:
1862 * Long-standing bugs:
1864 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1865 or any of the other *dir variables contain a space.
1867 Please note that Automake does not and cannot support spaces in
1868 filenames that are involved during the build. This change affects
1869 only installation paths, so that `make install' does not bomb out
1870 in packages configured with
1871 ./configure --prefix '/c/Program Files'
1873 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1874 POSIXLY_CORRECT is set.
1876 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1877 since Autoconf 2.54, which defines LIBOBJS itself.
1879 - Fix a potential (but unlikely) race condition in parallel elisp
1880 builds. (Introduced in 1.7.3.)
1882 - Do not assume that users override _DEPENDENCIES in all conditions
1883 where Automake will try to define them.
1885 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1886 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1889 This fix also affects the $(mkdir_p) variable defined since
1890 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1891 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1893 - Secure temporary directory creation in `make distcheck'. (PR/413)
1895 - Do not generate two build rules for `parser.h' when the
1896 parser appears in two different conditionals.
1898 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1899 checking. Usually ./configure will not pick this shell; so this
1900 fix only helps cases where the shell is forced to /bin/sh.
1902 * Bugs introduced by 1.8:
1904 - In some situations (hand-written `m4_include's), aclocal would
1905 call the `File::Spec->rel2abs' method, which was only introduced
1906 in Perl 5.6. This new version reestablish support Perl 5.005.
1908 It is likely that the next major Automake releases will require at
1909 least Perl 5.6. Consider upgrading your development environment
1910 if you are still using the five-year-old Perl 5.005.
1912 - Automake would sometimes fail to define rules for targets listed
1913 in variables defined in multiple conditions. For instance on
1919 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1920 `b.$(OBJEXT): b.c' rule.
1922 * New sections in manual:
1924 - Third-Party Makefiles: how to interface third party Makefiles.
1925 - Upgrading: upgrading packages to newer Automake versions.
1926 - Multiple Outputs: handling tools that produce many outputs.
1928 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1932 * A (well known) portability bug slipped in the changes made to
1933 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1934 install anything on Tru64.
1936 * Fix install rules for conditionally built python files. (This never
1939 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1943 * Bugs introduced by 1.8:
1945 - Fix Config.pm import error with old Perl versions (at least
1946 5.005_03). One symptom is that aclocal could not find its macro
1949 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1950 created by `make install' are always world readable, even if the
1951 installer happens to have an overly restrictive umask (e.g. 077).
1952 This was a mistake and has been reverted. There are at least two
1953 reasons why we must not use `-m 0755':
1954 - it causes special bits like SGID to be ignored,
1955 - it may be too restrictive (some setups expect 775 directories).
1957 - Fix aclocal to honor definitions located in files which have been
1958 m4_included manually. aclocal 1.8 had been updated to check
1959 m4_included files for new requirements, but forgot that these
1960 m4_included files can also provide new definitions.
1962 Note that if you have such a setup, we recommend you get rid of
1963 it. In the past, there was a reason to m4_include files manually:
1964 aclocal used to duplicate entire M4 files into aclocal.m4, even
1965 files that were distributed. Some packages were therefore
1966 m4_including the distributed file directly, and playing some
1967 tricks to ensure aclocal would not copy that file to aclocal.m4,
1968 in order to limit the amount of duplication. Since aclocal 1.8.x
1969 will precisely output m4_includes for local M4 files, we recommend
1970 that you clean up your setup, removing all manual m4_includes and
1971 letting aclocal output them.
1973 - Output detailed menus in the Info version if the Automake manual,
1974 so that Emacs can locate the indexes.
1976 - configure.ac and configure were listed twice in DIST_COMMON (an
1977 internal variable where Automake lists configury files to
1978 distribute). This was harmless, but unaesthetic.
1980 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1981 This was an issue only in the Automake package itself, not in
1984 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1985 DEST:SRC. This was wrong, as some packages do
1986 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1989 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1990 argument. This caused two kinds of failures:
1991 - Rules installing data in a conditionally defined directory
1992 failed when that directory was undefined. In this case no
1993 argument was supplied.
1994 - `make installdirs' failed, because several directories were
1995 passed to $(mkdir_p). This was an issue only on platform
1996 were $(mkdir_p) is implemented with `install-sh -d'.
1997 $(mkdir_p) as been changed to accept 0 or more arguments, as
2000 * Long-standing bugs:
2002 - Fix an unexpected diagnostic occurring when users attempt
2003 to override some internal variables that Automake appends to.
2005 - aclocal now scans configure.ac for macro definitions (PR/319).
2007 - Fix a portability issue with OSF1/Tru64 Make. If a directory
2008 distributes files which are outside itself (this usually occurs
2009 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
2010 from a parent package), then `make distcheck' fails due to an
2011 optimization performed by OSF1/Tru64 Make in its VPATH handling.
2012 (tests/subpkg2.test failure)
2014 - Fix another portability issue with Sun and OSF1/Tru64 Make.
2015 In a VPATH-build configuration, `make install' would install
2016 nobase_ files to wrong locations.
2018 - Fix a Perl `uninitialized value' diagnostic occurring when
2019 automake complains that a Texinfo file does not have a
2020 @setfilename statement.
2022 - Erase config.status.lineno during `make distclean'. This file
2023 can be created by config.status. Automake already knew about
2024 configure.lineno, but forgot config.status.lineno.
2026 - Distribute all files, even those which are built and installed
2027 conditionally. This change affects files listed in conditionally
2028 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
2029 as well as those listed in conditionally defined dist_*_DATA,
2030 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
2032 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
2033 doesn't conform to POSIX.
2035 - Normalize help strings for configure variables and options added
2040 - Check for python2.4 in AM_PATH_PYTHON.
2042 * Spurious failures in test suite:
2044 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
2045 tests/ltconv.test: fix failures with CVS Libtool.
2046 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
2047 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
2048 fix failures with old Texinfo versions.
2050 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2056 - The NEWS file is more verbose.
2060 - Autoconf 2.58 or greater is required.
2064 - Default source file names in the absence of a _SOURCES declaration
2065 are made by removing any target extension before appending `.c', so
2066 to make the libtool module `foo.la' from `foo.c', you only need to
2069 lib_LTLIBRARIES = foo.la
2070 foo_la_LDFLAGS = -module
2072 For backward compatibility, foo_la.c will be used instead of
2073 foo.c if this file exists or is the explicit target of a rule.
2074 However -Wobsolete will warn about this deprecated naming.
2076 - AR's `cru' flags are now set in a global ARFLAGS variable instead
2077 of being hard-coded in each $(AR) invocation, so they can be
2078 substituted from configure.ac. This has been requested by people
2079 dealing with non-POSIX ar implementations.
2081 - New warning option: -Woverride. This will warn about any user
2082 target or variable definitions which override Automake
2085 - Texinfo rules back up and restore info files when makeinfo fails.
2087 - Texinfo rules now support the `html' target.
2088 Running this requires Texinfo 4.0 or greater.
2090 `html' is a new recursive target, so if your package mixes
2091 hand-crafted `Makefile.in's with Automake-generated
2092 `Makefile.in's, you should adjust the former to support (or
2093 ignore) this target so that `make html' recurses successfully. If
2094 you had a custom `html' rule in your `Makefile.am', it's better to
2095 rename it as `html-local', otherwise your rule will override
2096 Automake's new rule (you can check that by running `automake
2097 -Woverride') and that will stop the recursion to subdirectories.
2099 Last but not least, this `html' rule is declared PHONY, even when
2100 overridden. Fortunately, it appears that few packages use a
2101 non-PHONY `html' rule.
2103 - Any file which is m4_included from configure.ac will appear as a
2104 configure and Makefile.in dependency, and will be automatically
2107 - The rules for rebuilding Makefiles and Makefile.ins will now
2108 rebuild all Makefiles and all Makefile.ins at once when one of
2109 configure's dependencies has changed. This is considerably faster
2110 than previous implementations, where config.status and automake
2111 were run separately in each directory (this still happens when you
2112 change a Makefile.am locally, without touching configure.ac or
2113 friends). Doing this also solves a longstanding issue: these
2114 rebuild rules failed to work when adding new directories to the
2115 tree, forcing you to run automake manually.
2117 - For similar reasons, the rules to rebuild configure,
2118 config.status, and aclocal.m4 are now defined in all directories.
2119 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
2120 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
2121 should better define them in all directories. This is easily done
2122 using an AC_SUBST (make sure you prefix these dependencies with
2123 $(top_srcdir) since this variable will appear at different
2124 levels of the build tree).
2126 - aclocal will now use `m4_include' instead of copying local m4
2127 files into aclocal.m4. (Local m4 files are those you ship with
2128 your project, other files will be copied as usual.)
2130 Because m4_included files are automatically distributed, it means
2131 for most projects there is no point in EXTRA_DISTing the list of
2132 m4 files which are used. (You can probably get rid of
2133 m4/Makefile.am if you had one.)
2135 - aclocal will avoid touching aclocal.m4 when possible, so that
2136 Autom4te's cache isn't needlessly invalidated. This behavior can
2137 be switched off with the new `--force' option.
2139 - aclocal now uses Autoconf's --trace to detect macros which are
2140 actually used and will no longer include unused macros simply
2141 because they where mentioned. This was often the case for macros
2142 called conditionally.
2144 - New options no-dist and no-dist-gzip.
2146 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2147 py-compile, and ylwrap, now all understand --version and --help.
2149 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2150 links as part of the distclean target and including source files in
2153 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2154 argument. The latter can be used to override the default behavior
2155 (which is to abort).
2157 - Automake will exit with $? = 63 on version mismatch. (So does
2158 Autoconf 2.58) missing knows this, and in this case it will
2159 emulate the tools as if they were absent. Because older versions
2160 of Automake and Autoconf did not use this exit code, this change
2161 will only be useful in projects generated with future versions of
2164 - When using AC_CONFIG_FILES with multiple input files, Automake
2165 generates the first ".in" input file for which a ".am" exists.
2166 (Former versions would try to use only the first input file.)
2168 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2169 idiom to disable byte-compilation of lisp_LISP files, it is
2170 recommended that you switch to using lisp_DATA. Note that
2171 this is not strictly equivalent: lisp_DATA will install elisp
2172 files even if emacs is not installed, while *_LISP do not
2173 install anything unless emacs is found.
2175 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2176 available. This selection is achieved through the Makefile
2177 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2178 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2179 `$(install_sh) -m 0755 -d'.
2183 - Because `mkdir -p' is available on most platforms, and we can use
2184 `install-sh -d' when it is not, the use of the mkinstalldirs
2185 script is being phased out. `automake --add-missing' no longer
2186 installs it, and if you remove mkinstalldirs from your package,
2187 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2189 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2190 gettextize and autopoint will install it when needed. Automake
2191 will continue to define the $(mkinstalldirs) and to distribute
2192 mkinstalldirs when this script is in the source tree.
2194 - AM_PROG_CC_STDC is now empty. The content of this macro was
2195 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2196 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2197 renaming should be safe, even if you have to support several,
2198 versions of Automake, because AC_PROG_CC defines this variable
2199 since Autoconf 2.54.)
2201 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2202 variable to override the aclocal.m4 dependencies computed
2203 (inaccurately) by older versions of Automake. Because Automake
2204 now tracks configure's m4 dependencies accurately (see m4_include
2205 above), the use of ACLOCAL_M4_SOURCES should be considered
2206 obsolete and will be flagged as such when running `automake
2211 - Defining programs conditionally using Automake conditionals no
2212 longer leads to a combinatorial explosion. The following
2213 construct used to be troublesome when used with dozens of
2228 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2230 - Due to implementation constraints, previous versions of Automake
2231 proscribed multiple conditional definitions of some variables
2241 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2242 This restriction has been lifted, and these variables now
2243 support multiple conditional definitions as do other variables.
2245 - Cleanup the definitions of $(distdir) and $(top_distdir).
2246 $(top_distdir) now points to the root of the distribution
2247 directory created during `make dist', as it did in Automake 1.4,
2248 not to the root of the build tree as it did in intervening
2249 versions. Furthermore these two variables are now only defined in
2250 the top level Makefile, and passed to sub-directories when running
2253 - The --no-force option now correctly checks the Makefile.in's
2254 dependencies before deciding not to update it.
2256 - Do not assume that make files are called Makefile in cleaning rules.
2258 - Update .info files in the source tree, not in the build tree. This
2259 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2260 used to update these files in the build tree (previous versions did
2261 it in the source tree too), and it caused several problems, varying
2262 from mere annoyance to portability issues.
2264 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2265 when --add-missing and --force-missing are used. For backward
2266 compatibility --add-missing will continue to install COPYING (in
2267 `gnu' strictness) when none of these three files exist, but this
2268 use is deprecated: you should better choose a license yourself and
2269 install it once for all in your source tree (and in your code
2272 - Fix ylwrap so that it does not overwrite header files that haven't
2273 changed, as the inline rule already does.
2275 - User-defined rules override automake-defined rules for the same
2276 targets, even when rules do not have commands. This is not new
2277 (and was documented), however some of the automake-generated
2278 rules have escaped this principle in former Automake versions.
2279 Rules for the following targets are affected by this fix:
2281 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2282 info, info-am, install-data-am, install-exec-am, install-info,
2283 install-info-am, install-man, installcheck-am, maintainer-clean,
2284 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2285 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2287 Practically it means that an attempt to supplement the dependencies
2288 of some target, as in
2290 clean: my-clean-rule
2292 will now *silently override* the automake definition of the
2293 rule for this target. Running `automake -Woverride' will diagnose
2294 all such overriding definitions.
2296 It should be noted that almost all of these targets support a *-local
2297 variant that is meant to supplement the automake-defined rule
2298 (See node `Extending' in the manual). The above rule should
2301 clean-local: my-clean-rule
2303 These *-local targets have been documented since at least
2304 Automake 1.2, so you should not fear the change if you have
2305 to support multiple automake versions.
2309 - The Automake manual is now distributed under the terms of the GNU FDL.
2311 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2313 - core dumps are no longer removed by the cleaning rules. There are
2314 at least three reasons for this:
2315 1. These files should not be created by any build step,
2316 so their removal do not fit any of the cleaning rules.
2317 Actually, they may be precious to the developer.
2318 2. If such file is created during a build, then it's clearly a
2319 bug Automake should not hide. Not removing the file will
2320 cause `make distcheck' to complain about its presence.
2321 3. Operating systems have different naming conventions for
2322 core dump files. A core file on one system might be a
2323 completely legitimate data file on another system.
2325 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2326 defined by Automake. This means that any definition in the
2327 environment will be used, unless overridden in the Makefile.am or
2328 on the command line. The old behavior, where these variables were
2329 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2330 AC_ARG_VARing each variable from configure.ac.
2332 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2333 documented. (The is not a new feature, these variables have
2334 been there since at least Automake 1.4.)
2336 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2338 Bugs fixed in 1.7.9:
2339 * Fix install-strip to work with nobase_ binaries.
2340 * Fix renaming of #line directives in ylwrap.
2341 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2343 Bugs fixed in 1.7.8:
2344 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2345 * Fix detection of Debian's install-info, broken since version 1.5.
2346 (Debian bug #213524).
2347 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2348 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2350 Bugs fixed in 1.7.7:
2351 * The implementation of automake's --no-force option is unreliable,
2352 so this option is ignored in this version. A real fix will appear in
2353 Automake 1.8. (Debian Bug #206299)
2354 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2355 argument is given. (PR/399)
2356 * Do not warn about leading `_' in variable names, even with -Wportability.
2357 * Support user redefinitions of TEXINFO_TEX.
2358 * depcomp: support AIX Compiler version 6.
2359 * Fix missing rebuilds during `make dist' with BSD make.
2360 (Could produce tarballs containing out-of-date files.)
2361 * Resurrect multilib support.
2362 * Noteworthy manual updates:
2363 - Extending aclocal: how to write m4 macros that won't trigger warnings
2365 - A Shared Library: Rewrite and split into subsections.
2367 Bugs fixed in 1.7.6:
2368 * Fix depcomp's icc mode for ICC 7.1.
2369 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2370 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2371 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2372 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2373 * Remove Latin-1 characters from elisp-comp.
2374 * Update the manual's @dircategory to match the Free Software Directory.
2376 Bugs fixed in 1.7.5:
2377 * Update install-sh's license to remove an advertising clause.
2378 (Debian bug #191717)
2379 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2380 that caused invalid Makefile.ins to be generated.
2381 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2382 * New FAQ entry: renamed objects.
2384 Bugs fixed in 1.7.4:
2385 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2386 the Emacs implementation)
2387 * Fix output of aclocal.m4 dependencies in subdirectories.
2388 * Use `mv -f' instead of `mv' in fastdep rules.
2389 * Upgrade mdate-sh to work on OS/2.
2390 * Don't byte-compile elisp files when ELCFILES is set empty.
2391 (this documented feature was broken by 1.7.3)
2392 * Diagnose trailing backslashes on last line of Makefile.am.
2393 * Diagnose whitespace following trailing backslashes.
2394 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2395 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2397 * `make install' will build `BUILT_SOURCES' first.
2398 * Minor documentation fixes.
2400 Bugs fixed in 1.7.3:
2401 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2402 * Query distutils for `pythondir' and `pythonexecdir', instead of
2403 using an hardcoded path. This should allow builds on 64-bit
2404 distributions that usually use lib64/ instead of lib/.
2405 * AM_PATH_PYTHON will also search for python2.3.
2406 * elisp files are now built all at once instead of one by one. Besides
2407 incurring a speed-up, this is required to support interdependent elisp files.
2408 * Support for DJGPP:
2409 - `make distcheck' will now work in `_inst/' and `_build' instead
2410 of `=inst/' and `=build/'
2411 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2412 - install/uninstall `*.i[0-9][0-9]'-style info files
2413 - more changes that affect only the Automake package (not its output)
2414 * Fix some incompatibilities with upcoming perl-5.10.
2415 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2416 PACKAGE and VERSION.
2418 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2419 is troublesome with gcc and Solaris compilers. (PR/385)
2420 - makedepend mode: work with Libtool. (PR/385 too)
2422 * better support for unusual gettext setups, such as multiple po/ directories
2424 - Flag missing po/ and intl/ directories as warnings, not errors.
2425 - Disable these warnings if po/ does not exist.
2426 * Noteworthy manual updates:
2428 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2430 - Document `AM_YFLAGS = -d'. (PR/382)
2432 Bugs fixed in 1.7.2:
2433 * Fix installation and uninstallation of Info files built in subdirectories.
2434 * Do not run `./configure --with-included-gettext' during `make distcheck'
2435 if AM_GNU_GETTEXT([external]) is used.
2436 * Correctly uninstall renamed man pages.
2437 * Do not strip escaped newline in variables defined in one condition
2438 and augmented in another condition.
2439 * Fix ansi2knr rules for LIBOBJS sources.
2440 * Clean all known Texinfo index files, not only those which appear to
2441 be used, because we cannot know which indexes are used in included files.
2442 (PR/375, Debian Bug #168671)
2443 * Honor only the first @setfilename seen in a Texinfo file.
2444 * Treat "required file X not found" diagnostics as errors (exit status 1).
2445 * Don't complain that a required file is not found when it is a Makefile
2447 * Don't use single suffix inference rules when building `.info'-less
2448 Info files, for the sake of Solaris make.
2449 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2450 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2451 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2452 * Fix building of deansified files from subdirectories. (PR/370)
2453 * Add missing `fi' in the .c->.obj rules.
2454 * Improve install-sh to work even when names contain spaces or certain
2455 (but not all) shell metachars.
2456 * Fix the following spurious failures in the test suite:
2457 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2458 * Noteworthy manual updates:
2459 - Augment the section about BUILT_SOURCES.
2460 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2462 Bugs fixed in 1.7.1:
2463 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2465 * Aclocal should now recognize macro names containing parentheses, e.g.
2466 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2467 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2469 * Install Python files even if they were built. (PR/369)
2470 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2471 version might not be defined in the latter. (PR/358)
2472 * Reorder arguments passed to a couple of commands, so things works
2473 when POSIXLY_CORRECT=1.
2474 * Fix a regex that can cause Perl to segfault on large input.
2476 * Fix distribution of packages that have some sources defined conditionally,
2477 as in the `Conditional compilation using Automake conditionals' example
2479 * Fix spurious test suite failures on IRIX.
2480 * Don't report a required variable as undefined if it has been
2481 defined conditionally for the "right" conditions.
2482 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2483 `make distcheck' fails.
2484 * Fix distribution of included Makefile fragment, so we don't create
2485 spurious directories in the distribution. (PR/366)
2486 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2489 * Autoconf 2.54 is required.
2490 * `aclocal' and `automake' will no longer warn about obsolete
2491 configure macros. This is done by `autoconf -Wobsolete'.
2492 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2493 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2494 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2495 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2496 `configure.ac' for you.
2497 * Support for per-program and per-library `_CPPFLAGS'.
2498 * New `ctags' target (builds CTAGS files).
2499 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2500 (see `automake --help' or the manual for a list of them).
2501 * Honor the WARNINGS environment variable.
2502 * Omit the call to depcomp when using gcc3: call the compiler directly.
2503 * A new option, std-options, tests that programs support --help and --version
2504 when `make installcheck' is run. This is enabled by --gnits.
2505 * Texinfo rules now support the `ps' and `pdf' targets.
2506 * Info files are now created in the build directory, not the source directory.
2507 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2509 * `make distcheck' will enforce DESTDIR support by attempting
2511 * `+=' can be used in conditionals, even if the augmented variable
2512 was defined for another condition.
2513 * Makefile fragments (inserted with `include') are always distributed.
2514 * Use Autoconf's --trace interface to inspect configure.ac and get
2515 a more accurate view of it.
2516 * Add support for extending aclocal's default macro search path
2517 using a `dirlist' file within the aclocal directory.
2518 * automake --output-dir is deprecated.
2519 * The part of the distcheck target that checks whether uninstall actually
2520 removes all installed files has been moved in a separate target,
2521 distuninstallcheck, so it can be overridden easily.
2525 * Support for AM_INIT_GETTEXT([external])
2526 * Bug fixes, including:
2527 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2528 - nobase_ programs and scripts honor --program-transform correctly.
2529 - Erase configure.lineno during `make distclean'.
2530 - Erase YACC and LEX outputs during `make maintainer-clean'.
2533 * Many bug fixes, including:
2534 - Requiring the current version works.
2535 - Fix "$@" portability issues (for Zsh).
2536 - Fix output of dummy dependency files in presence of post-processed
2538 - Don't compute dependencies in background to avoid races with libtool.
2539 - Fix handling of _OBJECTS variables for targets sharing source variables.
2540 - Check dependency mode for Java when AM_PROG_GCJ is used.
2543 * automake --output-dir is deprecated
2544 * Many bug fixes, including:
2545 - Don't choke on AM_LDFLAGS definitions.
2546 - Clean libtool objects from subdirectories.
2547 - Allow configure variables with reserved suffix and unknown prefix
2548 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2549 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2552 * Autoconf 2.52 is required.
2553 * automake no longer run libtoolize.
2554 This is the job of autoreconf (from GNU Autoconf).
2555 * `dist' generates all the archive flavors, as did `dist-all'.
2556 * `dist-gzip' generates the Gzip tar file only.
2557 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2558 explosion. Makefile.in's keep a reasonable size.
2559 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2560 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2562 * `#line' of Lex and Yacc files are properly set.
2563 * EXTRA_DIST can contain generated directories.
2564 * Support for dot-less extensions in suffix rules.
2565 * The part of the distcheck target that checks whether distclean actually
2566 cleans all built files has been moved in a separate target, distcleancheck,
2567 so it can be overridden easily.
2568 * `make distcheck' will pass additional options defined in
2569 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2570 * Fixed CDPATH portability problems, in particular for MacOS X.
2571 * Fixed handling of nobase_ targets.
2572 * Fixed support of implicit rules leading to .lo objects.
2573 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2574 * Added uninstall-hook target
2575 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2576 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2577 (Note that "pkgname" is not "tarname", see the manual for details.)
2578 It is also possible to pass a list of global Automake options as
2579 first argument to this new form of AM_INIT_AUTOMAKE.
2580 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2581 to be a real assembler.
2582 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2583 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2584 * aclocal and automake are also installed with the version number
2585 appended, and some of the install directory names have changed.
2586 This lets you have multiple versions installed simultaneously.
2587 * Support for parsers and lexers in subdirectories.
2590 * Support for `configure.ac'.
2591 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2592 * `make dist-all' is much faster.
2593 * Allows '@' AC_SUBSTs in macro names.
2594 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2595 * User-side dependency tracking. Developers no longer need GNU make
2597 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2598 * Most files are correctly handled if they appear in subdirs
2599 For instance, a _DATA file can appear in a subdir
2600 * GNU tar is no longer required for `make dist'
2601 * Added support for `dist_' and `nodist_' prefixes
2602 * Added support for `nobase_' prefix
2603 * Compiled Java support
2604 * Support for per-executable and per-library compilation flags
2608 * Added support for the Fortran 77 programming language.
2609 * Re-indexed the Automake Texinfo manual.
2610 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2611 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2612 * Support for latest autoconf, including support for objext
2613 * Can now put `.' in SUBDIRS to control build order
2614 * `include' command and `+=' support for macro assignment
2615 * Dependency tracking no long susceptible to deleted header file problem
2616 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2621 * Better Cygwin32 support
2622 * Support for suffix rules with _SOURCES variables
2623 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2624 * @LEXLIB@ no longer required when lex source seen
2625 Lex support in `missing', and new lex macro. Update your missing script.
2626 * Built-in support for assembly
2627 * aclocal gives error if `AM_' macro not found
2628 * Passed YFLAGS, not YACCFLAGS, to yacc
2629 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2630 * Dependencies computed as a side effect of compilation
2631 * Preliminary support for Java
2632 * DESTDIR support at "make install" time
2633 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2637 * Better DejaGnu support
2638 * Added no-installinfo option
2639 * Added Emacs Lisp support
2640 * Added --no-force option
2641 * Included `aclocal' program
2642 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2643 * Now uses `AM_' macro names everywhere
2644 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2645 ansi2knr now works correctly on K&R sources
2646 * Better C++, yacc, lex support
2647 * Will compute _DEPENDENCIES variables automatically if not supplied
2648 * Will interpolate $(...) and ${...} when examining contents of a variable
2649 * .deps files now in build directory, not source directory; dependency
2650 handling generally rewritten
2651 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2652 * can now put config.h into a subdir
2653 * Added dist-all target
2654 * Support for install-info program (see texinfo 3.9)
2655 * Support for "yacc -d"
2656 * configure substitutions are automatically discovered and included
2657 in generated Makefile.in
2658 * Special --cygnus mode
2659 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2660 when making distribution. Some dependencies are auto-ignored.
2661 * Changed how libraries are specified in _LIBRARIES variable
2662 * Full libtool support, from Gord Matzigkeit
2663 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2664 AM_CONFIG_HEADER handles it automatically
2665 * Texinfo output files no longer need .info extension
2666 * Added `missing' support
2668 * Conditionals in Makefile.am, from Ian Taylor
2672 * distcheck target runs install and installcheck targets
2673 * Added preliminary support for DejaGnu.
2678 * More libtool fixes from Gord Matzigkeit; libtool support is still
2680 * Added support for jm_MAINTAINER_MODE
2682 * New "distcheck" target
2686 * mkinstalldirs and mdate-sh now appear in directory specified by
2688 * Removed DIST_SUBDIRS, DIST_OTHER
2689 * AC_ARG_PROGRAM only required when an actual program exists
2690 * dist-hook target now run before distribution packaged up; idea from
2691 Dieter Baron. Other hooks exist, too.
2692 * Preliminary (unfinished) support for libtool
2693 * Added short option names.
2694 * Better "dist" support when gluing together multiple packages
2698 * Documentation updates (many from François Pinard)
2699 * strictness `normal' now renamed to `foreign'
2700 * Renamed --install-missing to --add-missing
2701 * Now handles AC_CONFIG_AUX_DIR
2702 * Now handles TESTS macro
2703 * DIST_OTHER renamed to EXTRA_DIST
2704 * DIST_SUBDIRS is deprecated
2705 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2706 * Better error messages in many cases
2707 * Program names are canonicalized
2708 * Added "check" prefix; from Gord Matzigkeit
2712 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2713 * Beginnings of a test suite
2714 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2715 * Doesn't print anything when running
2716 * Beginnings of MAINT_CHARSET support
2717 * Can specify version in AUTOMAKE_OPTIONS
2718 * Most errors recognizable by Emacs' M-x next-error
2719 * Added --verbose option
2720 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2721 configure-generated names
2722 * Required macros now distributed in aclocal.m4
2724 * --strictness=gnu is default
2728 * More sophisticated configure.in scanning; now understands ALLOCA and
2729 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2730 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2731 * CONFIG_HEADER variable now obsolete
2732 * Can handle multiple Texinfo sources
2733 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2734 * HEADERS variable no longer needed; now can put .h files directly into
2735 foo_SOURCES variable.
2736 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2737 corresponding ".in" files are included in the distribution.
2740 * Added --gnu and --gnits options
2741 * More standards checking
2743 * Cleaned up 'dist' targets
2744 * Added AUTOMAKE_OPTIONS variable and several options
2745 * Now scans configure.in to get some information (preliminary)
2748 * Works with Perl 4 again
2751 * Added --install-missing option.
2752 * Pretty-prints generated macros and rules
2753 * Comments in Makefile.am are placed more intelligently in Makefile.in
2754 * Generates .PHONY target
2755 * Rule or macro in Makefile.am now overrides contents of Automake file
2756 * Substantial cleanups from François Pinard
2760 * Works with Perl 4 again.
2763 * New uniform naming scheme.
2764 * --strictness option
2766 * '.c' files corresponding to '.y' or '.l' files are automatically
2768 * Many bug fixes and cleanups
2771 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2774 * Bug fixes in 'clean' code.
2775 * Now generates 'installdirs' target.
2776 * man page installation reworked.
2777 * 'make dist' no longer re-creates all Makefile.in's.
2780 * Reimplemented in Perl
2781 * Added --amdir option (for debugging)
2782 * Texinfo support cleaned up.
2783 * Automatic de-ANSI-fication cleaned up.
2784 * Cleaned up 'clean' targets.
2787 * Automatic dependency tracking
2788 * More documentation
2789 * New variables DATA and PACKAGEDATA
2790 * SCRIPTS installed using $(INSTALL_SCRIPT)
2791 * No longer uses double-colon rules
2793 * Changes in advance of internationalization
2797 Copyright (C) 1995-2013 Free Software Foundation, Inc.
2799 This program is free software; you can redistribute it and/or modify
2800 it under the terms of the GNU General Public License as published by
2801 the Free Software Foundation; either version 2, or (at your option)
2804 This program is distributed in the hope that it will be useful,
2805 but WITHOUT ANY WARRANTY; without even the implied warranty of
2806 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2807 GNU General Public License for more details.
2809 You should have received a copy of the GNU General Public License
2810 along with this program. If not, see <http://www.gnu.org/licenses/>.