1 * WARNING: Future backward-incompatibilities!
3 - Makefile recipes generated by Automake 2.0 will expect to use an
4 'rm' program that doesn't complain when called without any non-option
5 argument if the '-f' option is given (so that commands like "rm -f"
6 and "rm -rf" will act as a no-op, instead of raising usage errors).
7 This behavior of 'rm' is very widespread in the wild, and it will be
8 required in the next POSIX version:
10 <http://austingroupbugs.net/view.php?id=542>
12 Accordingly, AM_INIT_AUTOMAKE now expands some shell code that checks
13 that the default 'rm' program in PATH satisfies this requirement,
14 aborting the configure process if this is not the case. For the
15 moment, it's still possible to force the configuration process to
16 succeed even with a broken 'rm', that that will no longer be the case
19 - Automake 2.0 will require Autoconf 2.70 or later (which is still
20 unreleased at the moment of writing, but is planned to be released
21 before Automake 2.0 is).
23 - Automake 2.0 will drop support for the long-deprecated 'configure.in'
24 name for the Autoconf input file. You are advised to start using the
25 recommended name 'configure.ac' instead, ASAP.
27 - The ACLOCAL_AMFLAGS special make variable will be fully deprecated in
28 Automake 2.0: it will raise warnings in the "obsolete" category (but
29 still no hard error of course, for compatibilities with the many, many
30 packages that still relies on that variable). You are advised to
31 start relying on the new Automake support for AC_CONFIG_MACRO_DIRS
32 instead (which was introduced in Automake 1.13).
34 - Automake 2.0 will remove support for automatic dependency tracking
35 with the SGI C/C++ compilers on IRIX. The SGI depmode has been
36 reported broken "in the wild" already, and we don't think investing
37 time in debugging and fixing is worthwhile, especially considering
38 that SGI has last updated those compilers in 2006, and retired
39 support for them in December 2013:
40 <http://www.sgi.com/services/support/irix_mips_support.html>
42 - Automake 2.0 will remove support for MS-DOS and Windows 95/98/ME
43 (support for them was offered by relying on the DJGPP project).
44 Note however that both Cygwin and MSYS/MinGW on modern Windows
45 versions will continue to be fully supported.
47 - Automake-provided scripts and makefile recipes might (finally!)
48 start assuming a POSIX shell in Automake 2.0. There still is no
49 certainty about this though: we'd first like to wait and see
50 whether future Autoconf versions will be enhanced to guarantee
51 that such a shell is always found and provided by the checks in
54 - Starting from Automake 2.0, third-party m4 files located in the
55 system-wide aclocal directory, as well as in any directory listed
56 in the ACLOCAL_PATH environment variable, will take precedence
57 over "built-in" Automake macros. For example (assuming Automake
58 is installed in the /usr/local hierarchy), a definition of the
59 AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
60 should take precedence over the same-named automake-provided macro
61 (defined in '/usr/local/share/aclocal-2.0/vala.m4').
63 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
67 * Miscellaneous changes
69 - When subdir-objects is in effect, Automake will now construct
70 shorter object file names when no programs and libraries name
71 clashes are encountered. This should make the discouraged use of
72 'foo_SHORTNAME' unnecessary in many cases.
76 - Automatic dependency tracking has been fixed to work also when the
77 'subdir-object' option is used and some 'foo_SOURCES' definition
78 contains unexpanded references to make variables, as in, e.g.:
80 a_src = sources/libs/aaa
82 foo_SOURCES = $(a_src)/bar.c $(b_src)/baz.c
84 With such a setup, the created makefile fragment containing dependency
85 tracking information will be correctly placed under the directories
86 named 'sources/libs/aaa/.deps' and 'sources/bbb/.deps', rather than
87 mistakenly under directories named (literally!) '$(src_a)/.deps' and
88 '$(src_b)/.deps' (this was the first part of automake bug#13928).
90 Notice that in order to fix this bug we had to slightly change the
91 semantics of how config.status bootstraps the makefile fragments
92 required for the dependency tracking to work: rather than attempting
93 to parse the Makefiles via grep and sed trickeries only, we actually
94 invoke 'make' on a slightly preprocessed version of those Makefiles,
95 using a private target that is only meant to bootstrap the required
98 - The 'subdir-object' option no longer causes object files corresponding
99 to source files specified with an explicit '$(srcdir)' component to be
100 placed in the source tree rather than in the build tree.
102 For example, if Makefile.am contains:
104 AUTOMAKE_OPTIONS = subdir-objects
105 foo_SOURCES = $(srcdir)/foo.c $(srcdir)/s/bar.c $(top_srcdir)/baz.c
107 then "make all" will create 'foo.o' and 's/bar.o' in $(builddir) rather
108 than in $(srcdir), and will create 'baz.o' in $(top_builddir) rather
109 than in $(top_srcdir).
111 This was the second part of automake bug#13928.
113 - Installed 'aclocal' m4 macros can now accept installation directories
114 containing '@' characters (automake bug#20903)
116 - "./configure && make dist" no longer fails when a distributed file depends
117 on one from BUILT_SOURCES.
119 - When combining AC_LIBOBJ or AC_FUNC_ALLOCA with the
120 "--disable-dependency-tracking" configure option in an out of source
121 build, the build sub-directory defined by AC_CONFIG_LIBOBJ_DIR is now
122 properly created. (automake bug#27781)
124 - The time printed by 'mdate-sh' is now using the UTC time zone to support
125 the reproducible build effort. (automake bug#20314)
127 - The elisp byte-compilation rule now uses byte-compile-dest-file-function,
128 rather than byte-compile-dest-file, which was obsoleted in 2009. We expect
129 that Emacs-26 will continue to support the old function, but will complain
130 loudly, and that Emacs-27 will remove support for it altogether.
134 - A custom testsuite driver for the Guile Scheme SRFI-64 API has been added
135 to the "contrib" section. This allows a more convenient way to test Guile
136 code without having to use low primitives such as exit status. See
137 SRFI-64 API specification for more details:
138 <https://srfi.schemers.org/srfi-64/srfi-64.html>
140 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
146 - The code has been adapted to remove a warning present since Perl
147 5.22 stating that "Unescaped left brace in regex is deprecated".
148 This warning has become an hard error in Perl 5.26 (bug#22372).
150 - The generated Makefiles do not rely on the obsolescent GZIP
151 environment variable which was used for passing arguments to
152 'gzip'. Compatibility with old versions has been
153 preserved. (bug#20132)
155 * Miscellaneous changes:
157 - Support the Windows version of the Intel C Compiler (icl) in the
158 'compile' script in the same way the (compatible) Microsoft C
159 Compiler is supported.
161 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
165 * Improvements and refactorings in the install-sh script:
167 - It has been modernized, and now makes the following assumptions
169 (1) a working 'dirname' program is available;
170 (2) the ${var:-value} shell parameters substitution works;
171 (3) the "set -f" and "set +f" shell commands work, and, respectively,
172 disable and enable shell globbing.
174 - The script implements stricter error checking, and now it complains
175 and bails out if any of the following expectations is not met:
176 (1) the options -d and -t are never used together;
177 (2) the argument passed to option -t is a directory;
178 (3) if there are two or more SOURCEFILE arguments, the
179 DESTINATION argument must be a directory.
181 * Automake-generated testsuites:
183 - The default test-driver used by the Automake-generated testsuites
184 now appends the result and exit status of each "plain" test to the
185 associated log file (automake bug#11814).
187 - The perl implementation of the TAP testsuite driver is no longer
188 installed in the Automake's scripts directory, and is instead just
189 distributed as a "contrib" addition. There should be no reason to
190 use this implementation anyway in real packages, since the awk+shell
191 implementation of the TAP driver (which is documented in the manual)
192 is more portable and has feature parity with the perl implementation.
194 - The rule generating 'test-suite.log' no longer risk incurring in an
195 extra useless "make all" recursive invocation in some corner cases
196 (automake bug#16302).
200 - Automake bug#18286: "make distcheck" could sometimes fail to detect
201 files missing from the distribution tarball, especially in those cases
202 where both the generated files and their dependencies are explicitly
203 in $(srcdir). An important example of this are *generated* makefile
204 fragments included at Automake time in Makefile.am; e.g.:
207 $(srcdir)/fragment.am: $(srcdir)/data.txt $(srcdir)/preproc.sh
208 cd $(srcdir) && $(SHELL) preproc.sh <data.txt >fragment.am
209 include $(srcdir)/fragment.am
212 If the use forgot to add data.txt and/or preproc.sh in the distribution
213 tarball, "make distcheck" would have erroneously succeeded! This issue
216 - As a consequence of the previous change, "make distcheck" will run
217 using '$(distdir)/_build/sub' as the build directory, rather than
218 simply '$(distdir)/_build' (as it was the case for Automake 1.14 and
219 earlier). Consequently, the './configure' and 'make' invocations
220 issued by the distcheck recipe now have $(srcdir) equal to '../..',
221 rather than to just '..'. Dependent and similar variables (e.g.,
222 '$(top_srcdir)') are also changed accordingly.
224 Thus, Makefiles that made assumptions about the exact values of the
225 build and source directories used by "make distcheck" will have to
226 be adjusted. Notice that making such assumptions was a bad and
227 unsupported practice anyway, since the exact locations of those
228 directories should be considered implementation details, and we
229 reserve the right to change them at any time.
231 * Miscellaneous bugs fixed:
233 - The expansion of AM_INIT_AUTOMAKE ends once again with a trailing
234 newline (bug#16841). Regression introduced in Automake 1.14.
236 - We no longer risk to use '$ac_aux_dir' before it's defined (see
237 automake bug#15981). Bug introduced in Automake 1.14.
239 - The code used to detect whether the currently used make is GNU make
240 or not (relying on the private macro 'am__is_gnu_make') no longer
241 risks causing "Arg list too long" for projects using automatic
242 dependency tracking and having a ton of source files (bug#18744).
244 - Automake tries to offer a more deterministic output for generated
245 Makefiles, in the face of the newly-introduced randomization for
246 hash keys order in Perl 5.18.
248 - In older Automake versions, if a user defined one single Makefile
249 fragment (say 'foo.am') to be included via Automake includes in
250 his main Makefile.am, and defined a custom make rule to generate that
251 file from other data, Automake used to spuriously complain with some
252 message like "... overrides Automake target '$(srcdir)/foo.am".
253 This bug is now fixed.
255 - The user can now extend the special .PRECIOUS target, the same way
256 he could already do with the .MAKE .and .PHONY targets.
258 - Some confusing typos have been fixed in the manual and in few warning
259 messages (automake bug#16827 and bug#16997).
261 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
267 - The user is no longer allowed to override the --srcdir nor the --prefix
268 configure options used by "make distcheck" (bug#14991).
270 - Fixed a gross inefficiency in the recipes for installing byte-compiled
271 python files, that was causing an O(N^2) performance on the number N of
272 files, instead of the expected O(N) performance. Note that this bug
273 was only relevant when the number of python files was high (which is
274 unusual in practice).
276 - Automake try to offer a more deterministic output for warning messages,
277 in the face of the newly-introduced randomization for hash keys order
280 - The 'test-driver' script now actually error out with a clear error
281 message on the most common invalid usages.
283 - Several spurious failures/hangs in the testsuite (bugs #14706, #14707,
284 #14760, #14911, #15181, #15237).
286 * Documentation fixes:
288 - Fixed typos in the 'fix-timestamp.sh' example script that made it
291 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
295 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
297 - The 'compile' script is now unconditionally required for all packages
298 that perform C compilation (if you are using the '--add-missing'
299 option, automake will fetch that script for you, so you shouldn't
300 need any explicit adjustment). This new behaviour is needed to avoid
301 obscure errors when the 'subdir-objects' option is used, and the
302 compiler is an inferior one that doesn't grasp the combined use of
303 both the "-c -o" options; see discussion about automake bug#13378 for
305 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
306 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
308 - The next major Automake version (2.0) will unconditionally activate
309 the 'subdir-objects' option. In order to smooth out the transition,
310 we now give a warning (in the category 'unsupported') whenever a
311 source file is present in a subdirectory but the 'subdir-object' is
312 not enabled. For example, the following usage will trigger such a
315 bin_PROGRAMS = sub/foo
316 sub_foo_SOURCES = sub/main.c sub/bar.c
318 - Automake will automatically enhance the autoconf-provided macro
319 AC_PROG_CC to force it to check, at configure time, that the
320 C compiler supports the combined use of both the '-c' and '-o'
321 options. The result of this check is saved in the cache variable
322 'am_cv_prog_cc_c_o', and said result can be overridden by
323 pre-defining that variable.
325 - The AM_PROG_CC_C_O macro can still be called, albeit that should no
326 longer be necessary. This macro is now just a thin wrapper around the
327 Automake-enhanced AC_PROG_CC. This means, among the other things,
328 that its behaviour is changed in three ways:
330 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
331 macro behind the scenes.
333 2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
334 and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
335 dynamically computed only at configure runtime (really!) from
336 the content of the '$CC' variable.
338 3. It no longer automatically AC_DEFINE the C preprocessor
339 symbol 'NO_MINUS_C_MINUS_O'.
343 - Automake can now be instructed to place '.info' files generated from
344 Texinfo input in the builddir rather than in the srcdir; this is done
345 specifying the new automake option 'info-in-builddir'. This feature
346 was requested by the developers of GCC, GDB, GNU binutils and the GNU
347 bfd library. See the extensive discussion about automake bug#11034
350 - For quite a long time, Automake has been implementing an undocumented
351 hack which ensured that '.info' files which appeared to be cleaned
352 (by being listed in the CLEANFILES or DISTCLEANFILES variables) were
353 built in the builddir rather than in the srcdir; this hack was
354 introduced to ensure better backward-compatibility with package
355 such as Texinfo, which do things like:
357 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
358 DISTCLEANFILES = texinfo texinfo-* info*.info*
359 # Do not create info files for distribution.
363 in order not to distribute generated '.info' files.
365 Now that we have the 'info-in-builddir' option that explicitly causes
366 generated '.info' files to be placed in the builddir, this hack should
367 be longer necessary, so we deprecate it with runtime warnings.
368 It will be removed altogether in Automake 2.0.
370 * Relative directory in Makefile fragments:
372 - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
373 (and their short versions, '%D%' and '%C%' respectively) can now be used
374 in an included Makefile fragment. The former is substituted with the
375 relative directory of the included fragment (compared to the top-level
376 including Makefile), and the latter with the canonicalized version of
377 the same relative directory.
380 bin_PROGRAMS = # will be updated by included Makefile fragments
381 include src/Makefile.inc
383 # in 'src/Makefile.inc':
384 bin_PROGRAMS += %reldir%/foo
385 %canon_reldir%_foo_SOURCES = %reldir%/bar.c
387 This should be especially useful for packages using a non-recursive
390 * Deprecated distribution formats:
392 - The 'shar' and 'compress' distribution formats are deprecated, and
393 scheduled for removal in Automake 2.0. Accordingly, the use of the
394 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
395 (in the 'obsolete' category), and the recipes of the Automake-generated
396 targets 'dist-shar' and 'dist-tarZ' will unconditionally display
397 (non-fatal) warnings at make runtime.
399 * New configure runtime warnings about "rm -f" support:
401 - To simplify transition to Automake 2.0, the shell code expanded by
402 AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
403 'rm' program in PATH doesn't complain when called without any
404 non-option argument if the '-f' option is given (so that commands like
405 "rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
406 If this is not the case, the configure script is aborted, to call the
407 attention of the user on the issue, and invite him to fix his PATH.
408 The checked 'rm' behavior is very widespread in the wild, and will be
409 required by future POSIX versions:
411 <http://austingroupbugs.net/view.php?id=542>
413 The user can still force the configure process to complete even in the
414 presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
415 environment variable to "yes". And the generated Makefiles should
416 still work correctly even when such broken 'rm' is used. But note
417 that this will no longer be the case with Automake 2.0 though, so, if
418 you encounter the warning, please report it to us ASAP (and try to fix
419 your environment as well).
421 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
427 - Fix a minor regression introduced in Automake 1.13.3: when two or more
428 user-defined suffix rules were present in a single Makefile.am,
429 automake would needlessly include definition of some make variables
430 related to C compilation in the generated Makefile.in (bug#14560).
432 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
436 * Documentation fixes:
438 - The documentation no longer mistakenly reports that the obsolete
439 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
440 to be removed in Automake 2.0.
444 - Byte-compilation of Emacs lisp files could fail spuriously on
445 Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
447 - If the same user-defined suffixes were transformed into different
448 Automake-known suffixes in different Makefile.am files in the same
449 project, automake could get confused and generate inconsistent
450 Makefiles (automake bug#14441).
451 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
452 and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
453 would have mistakenly placed into 'Makefile.in' rules to compile
454 "*.c" files into object files, and into 'sub/Makefile.in' rules to
455 compile "*.cc" files into object files --- rather than the other
456 way around. This is now fixed.
460 - The test cases no longer have the executable bit set. This should
461 make it clear that they are not meant to be run directly; as
462 explained in t/README, they can only be run through the custom
463 'runtest' script, or by a "make check" invocation.
465 - The testsuite has seen the introduction of a new helper function
466 'run_make', and several related changes. These serve a two-fold
469 1. Remove brittleness due to the use of "make -e" in test cases.
471 2. Seamlessly allow the use of parallel make ("make -j...") in the
472 test cases, even where redirection of make output is involved
473 (see automake bug#11413 for a description of the subtle issues
476 - Several spurious failures have been fixed (they hit especially
477 MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
478 #14498, #14499, #14500, #14501, #14517 and #14528.
480 - Some other minor miscellaneous changes and fixlets.
482 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
486 * Documentation fixes:
488 - The long-deprecated but still supported two-arguments invocation form
489 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
490 thing to do, given that support for such usage might need to remain
491 in place for an unspecified amount of time in order to cater to people
492 who want to define the version number for their package dynamically at
493 configure runtime (unfortunately, Autoconf does not yet support this
494 scenario, so we cannot delegate the work to it).
496 - The serial testsuite harness is no longer reported as "deprecated",
497 but as "discouraged". We have no plan to remove it, nor to make its
498 use cause runtime warnings.
500 - The parallel testsuite is no longer reported as "experimental"; it
501 is well tested, and should be stable now.
503 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
504 'dist-tarZ' options are obsolescent, and their use is deprecated
505 in the documentation.
507 - Other minor miscellaneous fixes and improvements; in particular,
508 some improvements in cross-references.
510 * Obsolescent features:
512 - Use of suffix-less info files (that can be specified through the
513 '@setfilename' macro in Texinfo input files) is discouraged, and
514 its use will raise warnings in the 'obsolete' category. Simply
515 use the '.info' extension for all your info files, transforming
518 @setfilename myprogram
522 @setfilename myprogram.info
524 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
525 is discouraged, and its use will raise warnings in the 'obsolete'
526 category. You are advised to simply use the '.texi' extension
531 - When the 'ustar' option is used, the generated configure script no
532 longer risks hanging during the tests for the availability of the
533 'pax' utility, even if the user running configure has a UID or GID
534 that requires more than 21 bits to be represented.
535 See automake bug#8343 and bug#13588.
537 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
538 again, as they did in Automake 1.12.x (albeit printing runtime
539 warnings in the 'obsolete' category). Removing them has turned
540 out to be a very bad idea, because it complicated distro packing
541 enormously. Making them issue fatal warnings, as we did in
542 Automake 1.13, has turned out to be a similarly very bad idea,
543 for exactly the same reason.
545 - aclocal will no longer error out if the first local m4 directory
546 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
547 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
548 a warning in the 'unsupported' category. This is done to support
549 some pre-existing real-world usages. See automake bug#13514.
551 - aclocal will no longer consider directories for extra m4 files more
552 than once, even if they are specified multiple times. This ensures
553 packages that specify both
555 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
556 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
558 will work correctly, even when the 'm4' directory contains no
559 package-specific files, but is used only to install third-party
560 m4 files (as can happen with e.g., "libtoolize --install").
561 See automake bug#13514.
563 - Analysis of make flags in Automake-generated rules has been made more
564 robust, and more future-proof. For example, in presence of make that
565 (like '-I') take an argument, the characters in said argument will no
566 longer be spuriously considered as a set of additional make options.
567 In particular, automake-generated rules will no longer spuriously
568 believe to be running in dry mode ("make -n") if run with an invocation
569 like "make -I noob"; nor will they believe to be running in keep-going
570 mode ("make -k") if run with an invocation like "make -I kool"
571 (automake bug#12554).
573 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
579 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
580 causes a clear and helpful error message, instead of obscure ones
581 (issue introduced in Automake 1.13).
583 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
589 - ylwrap renames properly header guards in generated header files
590 (*.h), instead of leaving Y_TAB_H.
592 - ylwrap now also converts header guards in implementation files
593 (*.c). Because ylwrap failed to rename properly #include in the
594 implementation files, current versions of Bison (e.g., 2.7)
595 duplicate the generated header file in the implementation file.
596 The header guard then protects the implementation file from
597 duplicate definitions from the header file.
599 * Version requirements:
601 - Autoconf 2.65 or greater is now required.
603 - The rules to build PDF and DVI output from Texinfo input now
604 require Texinfo 4.9 or later.
608 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
609 option) has been removed. See discussion about automake bug#11034
610 for more background: <https://debbugs.gnu.org/11034>.
612 - The deprecated aclocal option '--acdir' has been removed. You
613 should use the options '--automake-acdir' and '--system-acdir'
614 instead (which have been introduced in Automake 1.11.2).
616 - The following long-obsolete m4 macros have been removed:
618 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
619 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
620 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
621 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
622 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
623 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
624 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
625 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
626 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
627 of the now-removed automatic de-ANSI-fication
630 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
632 - Use of the long-deprecated two- and three-arguments invocation forms
633 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
634 though (albeit with a warning in the 'obsolete' category), to cater
635 for people who want to define the version number for their package
636 dynamically (e.g., from the current VCS revision). We'll have to
637 continue this support until Autoconf itself is fixed to allow better
638 support for such dynamic version numbers.
640 * Elisp byte-compilation:
642 - The byte compilation of '.el' files into '.elc' files is now done
643 with a suffix rule. This has simplified the compilation process, and
644 more importantly made it less brittle. The downside is that emacs is
645 now invoked once for each '.el' files, which cause some noticeable
646 slowdowns. These should however be mitigated on multicore machines
647 (which are becoming the norm today) if concurrent make ("make -j")
650 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
651 files in the same subdirectory; for example, byte-compiling of file
652 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
653 'foo.elc'. This behaviour is backward-incompatible with older
654 Automake versions, but it is more natural and more sane. See also
657 - The Emacs invocation performing byte-compilation of '.el' files honors
658 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
659 one is developer-reserved and the latter one user-reserved.
661 - The 'elisp-comp' script, once provided by Automake, has been rendered
662 obsoleted by the just-described changes, and thus removed.
664 * Changes to Automake-generated testsuite harnesses:
666 - The parallel testsuite harness (previously only enabled by the
667 'parallel-tests' option) is the default one; the older serial
668 testsuite harness will still be available through the use of the
669 'serial-tests' option (introduced in Automake 1.12).
671 - The 'color-tests' option is now unconditionally activated by default.
672 In particular, this means that testsuite output is now colorized by
673 default if the attached terminal seems to support ANSI escapes, and
674 that the user can force output colorization by setting the variable
675 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
676 for backward-compatibility, although it's a handled as a no-op now.
678 * Silent rules support:
680 - Support for silent rules is now always active in Automake-generated
681 Makefiles. So, although the verbose output is still the default,
682 the user can now always use "./configure --enable-silent-rules" or
683 "make V=0" to enable quieter output in the package he's building.
685 - The 'silent-rules' option has now become a no-op, preserved for
686 backward-compatibility only. In particular, its use no longer
687 disables the warnings in the 'portability-recursive' category.
691 - The rules to build PDF and DVI files from Texinfo input now require
692 Texinfo 4.9 or later.
694 - The rules to build PDF and DVI files from Texinfo input now use the
695 '--build-dir' option, to keep the auxiliary files used by texi2dvi
696 and texi2pdf around without cluttering the build directory, and to
697 make it possible to run the "dvi" and "pdf" recipes in parallel.
699 * Automatic remake rules and 'missing' script:
701 - The 'missing' script no longer tries to update the timestamp of
702 out-of-date files that require a maintainer-specific tool to be
703 remade, in case the user lacks such a tool (or has a too-old version
704 of it). It just gives a useful warning, and in some cases also a
705 tip about how to obtain such a tool.
707 - The missing script has thus become useless as a (poor) way to work
708 around the sketched-timestamps issues that can happen for projects
709 that keep generated files committed in their VCS repository. Such
710 projects are now encouraged to write a custom "fix-timestamps.sh"
711 script to avoid such issues; a simple example is provided in the
712 "CVS and generated files" chapter of the automake manual.
716 - The user can now define his own recursive targets that recurse
717 in the directories specified in $(SUBDIRS). This can be done by
718 specifying the name of such targets in invocations of the new
719 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
723 - Any failure in the recipe of the "tags", "ctags", "cscope" or
724 "cscopelist" targets in a subdirectory is now propagated to the
725 top-level make invocation.
727 - Tags are correctly computed also for files in _SOURCES variables that
728 only list files with non-standard suffixes (see automake bug#12372).
730 * Improvements to aclocal and related rebuilds rules:
732 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
733 are now traced by aclocal, and can be used to declare the local m4
734 include directories. Formerly, one had to specify it with an explicit
735 '-I' option to the 'aclocal' invocation.
737 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
738 Automake versions will warn about its use, and later version will
739 remove support for it altogether.
741 * The depcomp script:
743 - Dropped support for libtool 1.4.
745 - Various internal refactorings. They should cause no visible change,
746 but the chance for regression is there anyway, so please report any
747 unexpected or suspicious behaviour.
749 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
750 This should cause no problem, since icc 8.0 has been released in
751 December 2003 -- almost nine years ago.
753 - Support for tcc (the Tiny C Compiler) has been improved, and is now
754 handled through a dedicated 'tcc' mode.
758 - ylwrap generates header guards with a single '_' for series of non
759 alphabetic characters, instead of several. This is what Bison >=
762 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
764 Bugs fixed in 1.12.6:
766 * Python-related bugs:
768 - The default installation location for python modules has been improved
769 for Python 3 on Debian and Ubuntu systems, changing from:
771 ${prefix}/lib/python3/dist-packages
775 ${prefix}/lib/python3.x/site-packages
777 This change should ensure modules installed using the default ${prefix}
778 "/usr/local" are found by default by system python 3.x installations.
779 See automake bug#10227.
781 - Python byte-compilation supports the new layout mandated by PEP-3147,
782 with its __pycache__ directory (automake bug#8847).
784 * Build system issues:
786 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
787 Automake's own build system works correctly again (bug introduced
792 - The Vala-related tests has been changed to adjust to the removal of
793 the 'posix' profile in the valac compiler. See automake bug#12934
796 - Some spurious testsuite failures related to older tools and systems
799 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
805 - The AM_PROG_VALAC macro has been enhanced to takes two further
806 optional arguments; it's signature now being
808 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
809 [ACTION-IF-NOT-FOUND])
811 - By default, AM_PROG_VALAC no longer aborts the configure invocation
812 if the Vala compiler found is too old, but simply prints a warning
813 messages (as it did when the Vala compiler was not found). This
814 should avoid unnecessary difficulties for end users that just want
815 to compile the unmodified, distributed Vala-generated C sources,
816 but happens to have an old Vala compiler in their PATH. This fixes
819 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
820 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
821 This is a better default, because with it a triggered makefile rule
822 invoking a Vala compilation will clearly fail with an informative error
823 message like "valac: command not found", rather than silently, with
824 the error possibly going unnoticed or triggering harder-to-diagnose
825 fallout failures in later steps.
827 * Miscellaneous changes:
829 - automake and aclocal no longer honours the 'perllibdir' environment
830 variable. That had always been intended only as an hack required in
831 the testsuite, not meant for any use beyond that.
833 Bugs fixed in 1.12.5:
835 * Long-standing bugs:
837 - Automake no longer generates spurious remake rules invoking autoheader
838 to regenerate the template corresponding to header files specified after
839 the first one in AC_CONFIG_HEADERS (automake bug#12495).
841 - When wrapping Microsoft tools, the 'compile' script falls back to
842 finding classic 'libname.a' style libraries when 'name.lib' and
843 'name.dll.lib' aren't available.
845 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
849 * Warnings and deprecations:
851 - Warnings in the 'obsolete' category are enabled by default both in
852 automake and aclocal.
854 * Miscellaneous changes:
856 - Some testsuite weaknesses and spurious failures have been fixed.
858 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
862 * Miscellaneous changes:
864 - The '.m4' files provided by Automake no longer define serial numbers.
865 This should cause no difference in the behaviour of aclocal though.
867 - Some testsuite weaknesses and spurious failures have been fixed.
869 - There is initial support for automatic dependency tracking with the
870 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
872 Bugs fixed in 1.12.3:
874 * Long-standing bugs:
876 - Instead of renaming only self-references of files (typically for
877 #lines), ylwrap now also renames references to the other generated
878 files. This fixes support for GLR and C++ parsers from Bison (PR
879 automake/491 and automake bug#7648): 'parser.c' now properly
880 #includes 'parser.h' instead of 'y.tab.h'.
882 - Generated files unknown to ylwrap are now preserved. This fixes
883 C++ support for Bison (automake bug#7648): location.hh and the
884 like are no longer discarded.
886 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
890 * Warnings and deprecations:
892 - Automake now issues a warning (in the 'portability' category) if
893 'configure.in' is used instead of 'configure.ac' as the Autoconf
894 input file. Such a warning will also be present in the next
895 Autoconf version (2.70).
899 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
900 order (as done by the other recursive rules), rather than in the
901 inverse order. They used to do that in order to work a round a
902 limitation in an older implementation of the automatic dependency
903 tracking support, but that limitation had been lifted years ago
904 already, when the automatic dependency tracking based on side-effects
905 of compilation had been introduced.
907 - Cleaning rules for compiled objects (both "plain" and libtool) work
908 better when subdir objects are involved, not triggering a distinct
909 'rm' invocation for each such object. They do so by removing *any*
910 compiled object file that is in the same directory of a subdir
911 object. See automake bug#10697.
913 * Silent rules support:
915 - A new predefined $(AM_V_P) make variable is provided; it expands
916 to a shell conditional that can be used in recipes to know whether
917 make is being run in silent or verbose mode.
919 Bugs fixed in 1.12.2:
921 * SECURITY VULNERABILITIES!
923 - The 'distcheck' recipe no longer grants temporary world-write
924 permissions on the extracted distdir. Even if such rights were
925 only granted for a vanishingly small time window, the implied
926 race condition proved to be enough to allow a local attacker
927 to run arbitrary code with the privileges of the user running
928 "make distcheck". This is CVE-2012-3386.
930 * Long-standing bugs:
932 - The "recheck" targets behaves better in the face of build failures
933 related to previously failed tests. For example, if a test is a
934 compiled program that must be rerun by "make recheck", and its
935 compilation fails, it will still be rerun by further "make recheck"
936 invocations. See automake bug#11791.
938 * Bugs introduced by 1.12.1:
940 - Automake provides once again the '$(mkdir_p)' make variable and the
941 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
942 for better backward-compatibility.
944 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
948 * New supported languages:
950 - Support for Objective C++ has been added; it should work similarly to
951 the support for Objective C.
953 * Deprecated obsolescent features:
955 - Use of the long-deprecated two- and three-arguments invocation forms
956 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
957 category. Starting from some future major Automake release (likely
958 post-1.13), such usages will no longer be allowed.
960 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
961 now deprecated (its use triggers a warning in the 'obsolete' category).
962 It will be removed in the next major Automake release (1.13).
964 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
965 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
966 m4 macro are deprecated, eliciting a warning in the 'obsolete'
969 * Miscellaneous changes:
971 - The Automake test cases now require a proper POSIX-conforming shell.
972 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
973 be accepted. In most cases, the user shouldn't have to specify such
974 POSIX shell explicitly, since it will be looked up at configure time.
975 Still, when this lookup fails, or when the user wants to override its
976 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
977 to the shell that will be used to run the Automake test cases).
979 Bugs fixed in 1.12.1:
981 * Bugs introduced by 1.12:
983 - Several weaknesses in Automake's own build system and test suite
986 * Bugs introduced by 1.11.3:
988 - When given non-option arguments, aclocal rejects them, instead of
989 silently ignoring them.
991 * Long-standing bugs:
993 - When the 'color-tests' option is in use, forcing of colored testsuite
994 output through "AM_COLOR_TESTS=always" works even if the terminal is
995 a non-ANSI one, i.e., if the TERM environment variable has a value of
998 - Several inefficiencies and poor performances in the implementation
999 of the parallel-tests 'check' and 'recheck' targets have been fixed.
1001 - The post-processing of output "#line" directives done the ylwrap
1002 script is more faithful w.r.t. files in a subdirectory; for example,
1003 if the processed file is "src/grammar.y", ylwrap will correctly
1004 produce directives like:
1005 #line 7 "src/grammar.y"
1010 * Bugs with new Perl versions:
1012 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
1014 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1018 * Obsolete features removed:
1020 - The never documented nor truly used script 'acinstall' has been
1023 - Support for automatic de-ANSI-fication has been removed.
1025 - The support for the "obscure" multilib feature has been removed
1026 from Automake core (but remains available in the 'contrib/'
1027 directory of the Automake distribution).
1029 - Support for ".log -> .html" conversion and the check-html and
1030 recheck-html targets has been removed from Automake core (but
1031 remains available in the 'contrib/' directory of the Automake
1034 - The deprecated 'lzma' compression format for distribution archives
1035 has been removed, in favor of 'xz' and 'lzip'.
1037 - The obsolete AM_WITH_REGEX macro has been removed.
1039 - The long-deprecated options '--output-dir', '--Werror' and
1040 '--Wno-error' have been removed.
1042 - The chapter on the history of Automake has been moved out of the
1043 reference manual, into a new dedicated Texinfo file.
1047 - New 'cscope' target to build a cscope database for the source tree.
1049 * Changes to Automake-generated testsuite harnesses:
1051 - The new automake option 'serial-tests' has been introduced. It can
1052 be used to explicitly instruct automake to use the older serial
1053 testsuite harness. This is still the default at the moment, but it
1054 might change in future versions.
1056 - The 'recheck' target (provided by the parallel testsuite harness) now
1057 depends on the 'all' target. This allows for a better user-experience
1058 in test-driven development. See automake bug#11252.
1060 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
1061 and unexpected or internal error, or a failure to set up the test case
1062 scenario) have their outcome reported as an 'ERROR' now. Previous
1063 versions of automake reported such an outcome as a 'FAIL' (the only
1064 difference with normal failures being that hard errors were counted
1065 as failures even when the test originating them was listed in
1068 - The testsuite summary displayed by the parallel-test harness has a
1069 completely new format, that always list the numbers of passed, failed,
1070 xfailed, xpassed, skipped and errored tests, even when these numbers
1071 are zero (but using smart coloring when the color-tests option is in
1074 - The default testsuite driver offered by the 'parallel-tests' option is
1075 now implemented (partly at least) with the help of automake-provided
1076 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
1077 on code in the generated Makefile.in.
1078 This has two noteworthy implications. The first one is that projects
1079 using the 'parallel-tests' option should now either run automake with
1080 the '--add-missing' option, or manually copy the 'test-driver' script
1081 into their tree. The second, and more important, implication is that
1082 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
1083 no longer be used to define a test runner, and the command specified
1084 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
1085 program or script. For example, this is still a valid usage (albeit
1086 a little contorted):
1088 TESTS_ENVIRONMENT = \
1089 if test -n '$(STRICT_TESTS)'; then \
1090 maybe_errexit='-e'; \
1094 LOG_COMPILER = $(SHELL) $$maybe_errexit
1096 OTOH, this is no longer a valid usage:
1098 TESTS_ENVIRONMENT = \
1099 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
1103 TESTS_ENVIRONMENT = \
1104 run_with_perl_or_shell () \
1106 if grep -q '^#!.*perl' $$1; then
1112 LOG_COMPILER = run_with_perl_or_shell
1114 - The package authors can now use customary testsuite drivers within
1115 the framework provided by the 'parallel-tests' testsuite harness.
1116 Consistently with the existing syntax, this can be done by defining
1117 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
1119 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
1120 to redirect/define file descriptors used by the test scripts.
1122 - The parallel-tests harness generates now, in addition the '.log' files
1123 holding the output produced by the test scripts, a new set of '.trs'
1124 files, holding "metadata" derived by the execution of the test scripts;
1125 among such metadata are the outcomes of the test cases run by a script.
1127 - Initial and still experimental support for the TAP test protocol is
1130 * Changes to Yacc and Lex support:
1132 - C source and header files derived from non-distributed Yacc and/or
1133 Lex sources are now removed by a simple "make clean" (while they were
1134 previously removed only by "make maintainer-clean").
1136 - Slightly backward-incompatible change, relevant only for use of Yacc
1137 with C++: the extensions of the header files produced by the Yacc
1138 rules are now modelled after the extension of the corresponding
1139 sources. For example, yacc files named "foo.y++" and "bar.yy" will
1140 produce header files named "foo.h++" and "bar.hh" respectively, where
1141 they would have previously produced header files named simply "foo.h"
1142 and "bar.h". This change offers better compatibility with 'bison -o'.
1144 * Miscellaneous changes:
1146 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
1147 rather than 1, if the vala compiler found is too old.
1149 - The build system of Automake itself now avoids the use of make
1150 recursion as much as possible.
1152 - Automake now prefers to quote 'like this' or "like this", rather
1153 than `like this', in diagnostic message and generated Makefiles,
1154 to accommodate the new GNU Coding Standards recommendations.
1156 - Automake has a new option '--print-libdir' that prints the path of the
1157 directory containing the Automake-provided scripts and data files.
1159 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
1161 - The rules to create pdf, dvi and ps output from Texinfo files now
1162 works better with modern 'texi2dvi' script, by explicitly passing
1163 it the '--clean' option to ensure stray auxiliary files are not
1164 left to clutter the build directory.
1166 - Automake can now generate silenced rules for texinfo outputs.
1168 - Some auxiliary files that are automatically distributed by Automake
1169 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
1170 C sources) might now be listed in the DIST_COMMON variable in many
1171 Makefile.in files, rather than in the top-level one.
1173 - Messages of types warning or error from 'automake' and 'aclocal'
1174 are now prefixed with the respective type, and presence of -Werror
1177 - Automake's early configure-time sanity check now tries to avoid
1178 sleeping for a second, which slowed down cached configure runs
1179 noticeably. In that case, it will check back at the end of the
1180 configure script to ensure that at least one second has passed, to
1181 avoid time stamp issues with makefile rules rerunning autotools
1184 - The warnings in the category 'extra-portability' are now enabled by
1185 '-Wall'. In previous versions, one has to use '-Wextra-portability'
1190 - Various minor bugfixes for recent or long-standing bugs.
1192 * Bugs introduced by 1.11:
1194 - The AM_COND_IF macro also works if the shell expression for the
1195 conditional is no longer valid for the condition.
1197 - The automake-provided parallel testsuite harness no longer fails
1198 with BSD make used in parallel mode when there are test scripts in
1199 a subdirectory, like in:
1201 TESTS = sub/foo.test sub/bar.test
1203 * Long-standing bugs:
1205 - Automake's own build system finally have a real "installcheck" target.
1207 - Vala-related cleanup rules are now more complete, and work better in
1210 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
1211 now automatically distributed also if the directory of the auxiliary
1212 files coincides with the top-level directory.
1214 - Automake now detects the presence of the '-d' flag in the various
1215 '*YFLAGS' variables even when their definitions involve indirections
1216 through other variables, such as in:
1218 AM_YFLAGS = $(foo_opts)
1220 - Automake now complains if a '*YFLAGS' variable has any conditional
1221 content, not only a conditional definition.
1223 - Explicit enabling and/or disabling of Automake warning categories
1224 through the '-W...' options now always takes precedence over the
1225 implicit warning level implied by Automake strictness (foreign, gnu
1226 or gnits), regardless of the order in which such strictness and
1227 warning flags appear. For example, a setting like:
1228 AUTOMAKE_OPTIONS = -Wall --foreign
1229 will cause the warnings in category 'portability' to be enabled, even
1230 if those warnings are by default disabled in 'foreign' strictness.
1232 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1234 Bugs fixed in 1.11.5:
1236 * Bugs introduced by 1.11.3:
1238 - Vala files with '.vapi' extension are now recognized and handled
1239 correctly again. See automake bug#11222.
1241 - Vala support work again for projects that contain some program
1242 built from '.vala' (and possibly '.c') sources and some other
1243 program built from '.c' sources *only*. See automake bug#11229.
1245 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1249 * Miscellaneous changes:
1251 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
1252 symbol index) modifiers as well as the "s" action, as the symbol index
1253 is created unconditionally by Microsoft lib. Also, the "q" (quick)
1254 action is now a synonym for "r" (replace). Also, the script has been
1255 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
1257 - When the 'compile' script is used to wrap MSVC, it now accepts an
1258 optional space between the -I, -L and -l options and their respective
1259 arguments, for better POSIX compliance.
1261 - There is an initial, experimental support for automatic dependency
1262 tracking with tcc (the Tiny C Compiler). Its associated depmode is
1263 currently recognized as "icc" (but this and other details are likely
1264 to change in future versions).
1266 - Automatic dependency tracking now works also with the IBM XL C/C++
1267 compilers, thanks to the new new depmode 'xlc'.
1269 Bugs fixed in 1.11.4:
1271 * Bugs introduced by 1.11.2:
1273 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
1274 no longer cause spurious failures upon "make install".
1276 - The user can now instruct the 'uninstall-info' rule not to update
1277 the '${infodir}/dir' file by exporting the environment variable
1278 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
1279 with how the 'install-info' rule operates since automake 1.11.2.
1281 * Long-standing bugs:
1283 - It is now possible for a foo_SOURCES variable to hold Vala sources
1284 together with C header files, as well as with sources and headers for
1285 other supported languages (e.g., C++). Previously, only mixing C and
1286 Vala sources was supported.
1288 - If "aclocal --install" is used, and the first directory specified with
1289 '-I' is non-existent, aclocal will now create it before trying to copy
1292 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
1293 install rules to create an empty $(foodir) directory; for example, if
1294 Makefile.am contains something like:
1296 pkglibexec_SCRIPTS =
1298 pkglibexec_SCRIPTS += bar.sh
1301 the $(pkglibexec) directory will not be created upon "make install".
1303 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1307 * Miscellaneous changes:
1309 - Automake's own build system is more silent by default, making use of
1310 the 'silent-rules' option.
1312 - The master copy of the 'gnupload' script is now maintained in gnulib,
1315 - The 'missing' script no longer tries to wrap calls to 'tar'.
1317 - "make dist" no longer wraps 'tar' invocations with the 'missing'
1318 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
1319 shouldn't be using BTW ;-) no longer invokes the 'missing' script
1320 to wrap tar, but simply invokes the 'tar' program itself.
1322 - "make dist" can now create lzip-compressed tarballs.
1324 - In the Automake info documentation, the Top node and the nodes about
1325 the invocation of the automake and aclocal programs have been renamed;
1326 now, calling "info automake" will open the Top node, while calling
1327 "info automake-invocation" and "info aclocal-invocation" will access
1328 the nodes about the invocation of respectively automake and aclocal.
1330 - Automake is now distributed as a gzip-compressed and an xz-compressed
1331 tarball. Previously, bzip2 was used instead of xz.
1333 - The last relics of Python 1.5 support have been removed from the
1334 AM_PATH_PYTHON macro.
1336 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
1337 and adds them to the normal list of dependencies, but without
1338 overwriting the foo_DEPENDENCIES variable, which is normally computed
1341 Bugs fixed in 1.11.3:
1343 * Bugs introduced by 1.11.2:
1345 - Automake now correctly recognizes the prefix/primary combination
1346 'pkglibexec_SCRIPTS' as valid.
1348 - The parallel-tests harness no longer trips on sed implementations
1349 with stricter limits on the length of input lines (problem seen at
1350 least on Solaris 8).
1352 * Long-standing bugs:
1354 - The "deleted header file problem" for *.am files is avoided by stub
1355 rules. This allows 'make' to trigger a rerun of 'automake' also if
1356 some previously needed '.am' file has been removed.
1358 - The 'silent-rules' option now generates working makefiles even
1359 for the uncommon 'make' implementations that do not support the
1360 nested-variables extension to POSIX 2008. For such 'make'
1361 implementations, whether a build is silent is determined at
1362 configure time, and cannot be overridden at make time with
1363 "make V=0" or "make V=1".
1365 - Vala support now works better in VPATH setups.
1367 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1371 * Changes to aclocal:
1373 - The `--acdir' option is deprecated. Now you should use the new options
1374 `--automake-acdir' and `--system-acdir' instead.
1376 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1377 colon-separated list of additional directories to search after the
1378 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1379 and before the system acdir (by default ${prefix}/share/aclocal).
1381 * Miscellaneous changes:
1383 - The Automake support for automatic de-ANSI-fication has been
1384 deprecated. It will probably be removed in the next major Automake
1387 - The `lzma' compression scheme and associated automake option `dist-lzma'
1388 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1390 - You may adjust the compression options used in dist-xz and dist-bzip2.
1391 The default is now merely -e for xz, but still -9 for bzip; you may
1392 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1393 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1395 - The `compile' script now converts some options for MSVC for a better
1396 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1398 - The py-compile script now accepts empty arguments passed to the options
1399 `--destdir' and `--basedir', and complains about unrecognized options.
1400 Moreover, a non-option argument or a special `--' argument terminates
1401 the list of options.
1403 - A developer that needs to pass specific flags to configure at "make
1404 distcheck" time can now, and indeed is advised to, do so by defining
1405 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1406 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1407 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1408 user; still, the old Makefile.am files that used to define it will
1409 still continue to work as before.
1411 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1412 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1413 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1414 is run with -Wextra-portability and -Werror.
1416 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1417 file generated by automake-provided rules by defining the special make
1418 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1420 - The `install-info' rule can now be instructed not to create/update
1421 the `${infodir}/dir' file, by exporting the new environment variable
1422 `AM_UPDATE_INFO_DIR' to the value "no".
1424 Bugs fixed in 1.11.2:
1426 * Bugs introduced by 1.11:
1428 - The parallel-tests driver no longer produces erroneous results with
1429 Tru64/OSF 5.1 sh upon unreadable log files.
1431 - The `parallel-tests' test driver does not report spurious successes
1432 when used with concurrent FreeBSD make (e.g., "make check -j3").
1434 - When the parallel-tests driver is in use, automake now explicitly
1435 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1436 instead of issuing confusing and apparently unrelated error messages
1437 (e.g., "non-POSIX variable name", "bad characters in variable name",
1438 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1439 silently producing broken `Makefile.in' files.
1441 - The `silent-rules' option now truly silences all compile rules, even
1442 when dependency tracking is disabled. Also, when `silent-rules' is
1443 not used, `make' output no longer contains spurious backslash-only
1444 lines, thus once again matching what Automake did before 1.11.
1446 - The AM_COND_IF macro also works if the shell expression for the
1447 conditional is no longer valid for the condition.
1449 * Long-standing bugs:
1451 - The order of Yacc and Lex flags is fixed to be consistent with other
1452 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1453 $(LFLAGS), so that the user variables override the developer variables.
1455 - "make distcheck" now correctly complains also when "make uninstall"
1456 leaves one and only one file installed in $(prefix).
1458 - A "make uninstall" issued before a "make install", or after a mere
1459 "make install-data" or a mere "make install-exec" does not spuriously
1462 - Automake now warns about more primary/directory invalid combinations,
1463 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1465 - Rules generated by Automake now try harder to not change any files when
1466 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1467 Yacc source files and the rule to update config.h.
1469 - Several scripts and the parallel-tests testsuite driver now exit with
1470 the right exit status upon receiving a signal.
1472 - A per-Makefile.am setting of -Werror does not erroneously carry over
1473 to the handling of other Makefile.am files.
1475 - The code for automatic dependency tracking works around a Solaris
1476 make bug triggered by sources containing repeated slashes when the
1477 `subdir-objects' option was used.
1479 - The makedepend and hp depmodes now work better with VPATH builds.
1481 - Java sources specified with check_JAVA are no longer compiled for
1482 "make all", but only for "make check".
1484 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1485 and error out if `javadir' is undefined, instead of silently producing
1486 a broken Makefile.in.
1488 - aclocal and automake now honour the configure-time definitions of
1489 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1491 - The `install-info' recipe no longer tries to guess whether the
1492 `install-info' program is from Debian or from GNU, and adaptively
1493 change its behaviour; this has proven to be frail and easy to
1496 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1498 Bugs fixed in 1.11.1:
1500 - Lots of minor bugfixes.
1502 * Bugs introduced by 1.11:
1504 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1505 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1507 * Long standing bugs:
1509 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1510 even if the `--prefix' argument pointed outside of a system directory.
1511 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1512 `get_python_lib' function if it points outside the configured prefix,
1513 unless the `--prefix' argument was either `/usr' or below `/System'.
1515 - The testsuite does not try to change the mode of `ltmain.sh' files from
1516 a Libtool installation (symlinked to test directories) any more.
1518 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1519 tools are preferred in a cross-compile setup.
1521 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1522 This fixes a race condition where untrusted users could modify files
1523 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1524 build directory was world-searchable. This is CVE-2009-4029.
1526 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1530 * Version requirements:
1532 - Autoconf 2.62 or greater is required.
1534 * Changes to aclocal:
1536 - The autoconf version check implemented by aclocal in aclocal.m4
1537 (and new in Automake 1.10) is degraded to a warning. This helps
1538 in the common case where the Autoconf versions used are compatible.
1540 * Changes to automake:
1542 - The automake program can run multiple threads for creating most
1543 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1544 with interpreter-based threads enabled. Set the environment variable
1545 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1546 enable this experimental feature.
1548 * Changes to Libtool support:
1550 - Libtool generic flags are now passed to the install and uninstall
1553 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1554 config.lt is removed correctly now.
1556 * Languages changes:
1558 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1559 Fortran, and Ratfor).
1561 - For files with extension .f90, .f95, .f03, or .f08, the flag
1562 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1564 - Files with extension .sx are also treated as preprocessed assembler.
1566 - The default source file extension (.c) can be overridden with
1567 AM_DEFAULT_SOURCE_EXT now.
1569 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1572 - AM_PATH_PYTHON honors python's idea about the site directory.
1574 - There is initial support for the Vala programming language, when using
1575 Vala 0.7.0 or later.
1577 * Miscellaneous changes:
1579 - Automake development is done in a git repository on Savannah now, see
1581 https://git.sv.gnu.org/gitweb/?p=automake.git
1583 A read-only CVS mirror is provided at
1585 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1586 checkout -d automake HEAD
1588 - "make dist" can now create xz-compressed tarballs,
1589 as well as (deprecated?) lzma-compressed tarballs.
1591 - `automake --add-missing' will by default install the GPLv3 file as
1592 COPYING if it is missing. It will also warn that the license file
1593 should be added to source control. Note that Automake will never
1594 overwrite an existing COPYING file, even when the `--force-missing'
1597 - The manual is now distributed under the terms of the GNU FDL 1.3.
1599 - Automake ships and installs man pages for automake and aclocal now.
1601 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1603 - install-sh supports -C, which does not update the installed file
1604 (and its time stamps) if the contents did not change.
1606 - The `gnupload' script has been revamped.
1608 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1610 - The targets `install' and `uninstall' are more efficient now, in that
1611 for example multiple files from one Automake variable such as
1612 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1613 invocation if they do not have to be renamed.
1615 Both install and uninstall may sometimes enter (`cd' into) the target
1616 installation directory now, when no build-local scripts are used.
1618 Both install and uninstall do not fail anymore but do nothing if an
1619 installation directory variable like `bindir' is set to the empty string.
1621 For built-in rules, `make install' now fails reliably if installation
1622 of a file failed. Conversely, `make uninstall' even succeeds when
1623 issued multiple times.
1625 These changes may need some adjustments from users: For example,
1626 some `install' programs refuse to install multiple copies of the
1627 same file in one invocation, so you may need to remove duplicate
1628 entries from file lists.
1630 Also, within one set of files, say, nobase_data_DATA, the order of
1631 installation may be changed, or even unstable among different hosts,
1632 due to the use of associative arrays in awk. The increased use of
1633 awk matches a similar move in Autoconf to provide for better scaling.
1635 Further, most undocumented per-rule install command variables such as
1636 binSCRIPT_INSTALL have been removed because they are not needed any
1637 more. Packages which use them should be using the appropriate one of
1638 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1639 counterpart, depending on the type of files and the need for automatic
1640 target directory creation.
1642 - The "deleted header file problem" for *.m4 files is avoided by
1643 stub rules. This allows `make' to trigger a rerun of `aclocal'
1644 also if some previously needed macro file has been removed.
1646 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1647 an otherwise up to date tree.
1649 - The `color-tests' option causes colored test result output on terminals.
1651 - The `parallel-tests' option enables a new test driver that allows for
1652 parallel test execution, inter-test dependencies, lazy test execution
1653 for unit-testing, re-testing only failed tests, and formatted result output
1654 as RST (reStructuredText) and HTML. Enabling this option may require some
1655 changes to your test suite setup; see the manual for details.
1657 - The `silent-rules' option enables Linux kernel-style silent build output.
1658 This option requires the widely supported but non-POSIX `make' feature
1659 of recursive variable expansion, so do not use it if your package needs
1660 to build with `make' implementations that do not support it.
1662 To enable less verbose build output, the developer has to use the Automake
1663 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1664 macro. The user may then set the default verbosity by passing the
1665 `--enable-silent-rules' option to `configure'. At `make' run time, this
1666 default may be overridden using `make V=0' for less verbose, and `make V=1'
1667 for backward-compatible verbose output.
1669 - New prefix `notrans_' for manpages which should not be transformed
1670 by --program-transform.
1672 - New macro AM_COND_IF for conditional evaluation and conditional
1675 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1676 remove the file in a non-VPATH build. Such setups work with Autoconf
1679 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1680 the default setting.
1682 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1683 useful especially for multi-line values.
1685 - Automake's early configure-time sanity check now diagnoses an
1686 unsafe absolute source directory name and makes configure fail.
1688 - The Automake macros and rules cope better with whitespace in the
1689 current directory name, as long as the relative path to `configure'
1690 does not contain whitespace. To this end, the values of `$(MISSING)'
1691 and `$(install_sh)' may contain suitable quoting, and their expansion
1692 might need `eval'uation if used outside of a makefile. These
1693 undocumented variables may be used in several documented macros such
1694 as $(AUTOCONF) or $(MAKEINFO).
1698 * Long-standing bugs:
1700 - Fix aix dependency tracking for libtool objects.
1702 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1703 unnecessary use of the `compile' script.
1705 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1706 correct `-rpath' argument is used now.
1708 - `config.status --file=Makefile depfiles' now also works with the
1709 extra quoting used internally by Autoconf 2.62 and newer
1710 (it used to work only without the `--file=' bit).
1712 - The `missing' script works better with versioned tool names.
1714 - Semantics for `missing help2man' have been revamped:
1716 Previously, if `help2man' was not present, `missing help2man' would have
1717 the following semantics: if some man page was out of date but present, then
1718 a warning would be printed, but the exit status was 0. If the man page was
1719 not present at all, then `missing' would create a replacement man page
1720 containing an error message, and exit with a status of 2. This does not play
1721 well with `make': the next run will see this particular man page as being up
1722 to date, and will only error out on the next generated man page, if any;
1723 repeat until all pages are done. This was not desirable.
1725 These are the new semantics: if some man page is not present, and help2man
1726 is not either, then `missing' will warn and generate the replacement page
1727 containing the error message, but exit successfully. However, `make dist'
1728 will ensure that no such bogus man pages are packaged into a tarball.
1730 - Targets provided by automake behave better with `make -n', in that they
1731 take care not to create files.
1733 - `config.status Makefile... depfiles' works fine again in the presence of
1734 disabled dependency tracking.
1736 - The default no-op recursive rules for these targets also work with BSD make
1737 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1739 - `make distcheck' works also when both a directory and some file below it
1740 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1742 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1743 `make mostlyclean' any more; only the LaTeX by-products are.
1745 - Renamed objects also work with the `subdir-objects' option and
1746 source file languages which Automake does not know itself.
1748 - `automake' now correctly complains about variable assignments which are
1749 preceded by a comment, extend over multiple lines with backslash-escaped
1750 newlines, and end in a comment sign. Previous versions would silently
1751 and wrongly ignore such assignments completely.
1753 * Bugs introduced by 1.10:
1755 - Fix output of dummy dependency files in presence of post-processed
1756 Makefile.in's again, but also cope with long lines.
1758 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1759 that have been declared as programs in the same Makefile.
1760 This is for consistency with the analogous change to TESTS in 1.10.
1762 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1763 followed by directories containing config headers.
1765 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1769 * Version requirements:
1771 - Autoconf 2.60 or greater is required.
1773 - Perl 5.6 or greater is required.
1775 * Changes to aclocal:
1777 - aclocal now also supports -Wmumble and -Wno-mumble options.
1779 - `dirlist' entries (for the aclocal search path) may use shell
1780 wildcards such as `*', `?', or `[...]'.
1782 - aclocal supports an --install option that will cause system-wide
1783 third-party macros to be installed in the local directory
1784 specified with the first -I flag. This option also uses #serial
1785 lines in M4 files to upgrade local macros.
1787 The new aclocal options --dry-run and --diff help to review changes
1788 before they are installed.
1790 - aclocal now outputs an autoconf version check in aclocal.m4 in
1791 projects using automake.
1793 For a few years, automake and aclocal have been calling autoconf
1794 (or its underlying engine autom4te) to accurately retrieve the
1795 data they need from configure.ac and its siblings. Doing so can
1796 only work if all autotools use the same version of autoconf. For
1797 instance a Makefile.in generated by automake for one version of
1798 autoconf may stop working if configure is regenerated with another
1799 version of autoconf, and vice versa.
1801 This new version check ensures that the whole build system has
1802 been generated using the same autoconf version.
1804 * Support for new Autoconf macros:
1806 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1808 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1809 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1810 in different directories. However, only one instance of such a
1811 library objects directory is supported.
1813 * Change to Libtool support:
1815 - Libtool generic flags (those that go before the --mode=MODE option)
1816 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1818 * Yacc and Lex changes:
1820 - The rebuild rules for distributed Yacc and Lex output will avoid
1821 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1824 - ylwrap is now always used for lex and yacc source files,
1825 regardless of whether there is more than one source per directory.
1827 * Languages changes:
1829 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1830 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1831 tracking, unlike non-preprocessed assembler (*.s).
1833 - subdir-object mode works now with Assembler. Automake assumes
1834 that the compiler understands `-c -o'.
1836 - Preprocessed assembler (*.S) compilation now also honors
1837 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1839 - Improved support for Objective C:
1840 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1841 - A new section of the manual documents the support.
1843 - New support for Unified Parallel C:
1844 - AM_PROG_UPC looks for a UPC compiler.
1845 - A new section of the manual documents the support.
1847 - Per-target flags are now correctly handled in link rules.
1849 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1850 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1851 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1852 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1854 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1855 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1856 is expected to work (and actually works during compilation).
1858 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1859 "in addition to" breaks backward compatibility with older versions.
1860 If your package used both variables, as in
1862 AM_LDFLAGS = common flags
1863 bin_PROGRAMS = a b c
1864 a_LDFLAGS = more flags
1867 and assumed *_LDFLAGS would sum up, you should rewrite it as
1869 AM_LDFLAGS = common flags
1870 bin_PROGRAMS = a b c
1871 a_LDFLAGS = $(AM_LDFLAGS) more flags
1874 This new behavior of *_LDFLAGS is more coherent with other
1875 per-target variables, and the way *_LDFLAGS variables were
1876 considered internally.
1878 * New installation targets:
1880 - New targets mandated by GNU Coding Standards:
1885 By default they will only install Texinfo manuals.
1886 You can customize them with *-local variants:
1892 - The undocumented recursive target `uninstall-info' no longer exists.
1893 (`uninstall' is in charge of removing all possible documentation
1894 flavors, including optional formats such as dvi, ps, or info even
1895 when `no-installinfo' is used.)
1897 * Miscellaneous changes:
1899 - Automake no longer complains if input files for AC_CONFIG_FILES
1900 are specified using shell variables.
1902 - clean, distribution, or rebuild rules are normally disabled for
1903 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1904 AC_CONFIG_LINK specified using shell variables. However, if these
1905 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1906 be able to output rules anyway.
1907 (See the Automake documentation for AC_CONFIG_FILES.)
1909 - $(EXEEXT) is automatically appended to filenames of TESTS
1910 that have been declared as programs in the same Makefile.
1911 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1913 - `-Wportability' has finally been turned on by default for `gnu' and
1914 `gnits' strictness. This means, automake will complain about %-rules
1915 or $(GNU Make functions) unless you switch to `foreign' strictness or
1916 use `-Wno-portability'.
1918 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1919 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1920 $(mkdir_p) variable is still defined (to the same value as
1921 $(MKDIR_P)) but should be considered obsolete. If you are using
1922 $(mkdir_p) in some of your rules, please plan to update them to
1923 $(MKDIR_P) at some point.
1925 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1926 They still work in this release, but may be withdrawn in a future one.
1928 - Inline compilation rules for gcc3-style dependency tracking are
1931 - Automake installs a "Hello World!" example package in $(docdir).
1932 This example is used throughout the new "Autotools Introduction"
1933 chapter of the manual.
1935 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1939 * Makefile.in bloat reduction:
1941 - Inference rules are used to compile sources in subdirectories when
1942 the `subdir-objects' option is used and no per-target flags are
1943 used. This should reduce the size of some projects a lot, because
1944 Automake used to output an explicit rule for each such object in
1947 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1948 object that must be built with explicit rules. It just outputs
1949 the rules required to build the kind of object considered: either
1950 the two .o and .obj rules for usual objects, or the .lo rule for
1953 * Change to Libtool support:
1955 - Libtool tags are used with libtool versions that support them.
1956 (I.e., with Libtool 1.5 or greater.)
1958 - Automake is now able to handle setups where a libtool library is
1959 conditionally installed in different directories, as in
1962 lib_LTLIBRARIES = liba.la
1964 pkglib_LTLIBRARIES = liba.la
1966 liba_la_SOURCES = ...
1968 * Changes to aclocal:
1970 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1971 really evaluated, before it decides to include them in aclocal.m4.
1972 This solves nasty problems with conditional redefinitions of
1973 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1974 *.m4 files to be included in any project using these macros.
1975 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1976 most famous instance of this bug.)
1978 - Do not complain about missing conditionally AC_REQUIREd macros
1979 that are not actually used. In 1.8.x aclocal would correctly
1980 determine which of these macros were really needed (and include
1981 only these in the package); unfortunately it would also require
1982 all of them to be present in order to run. This created
1983 situations were aclocal would not work on a tarball distributing
1984 all the macros it uses. For instance running aclocal on a project
1985 containing only the subset of the Gettext macros in use by the
1986 project did not work, because gettext conditionally requires other
1989 * Portability improvements:
1991 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1992 tar-pax. The new option filename-length-max=99 helps diagnosing
1993 filenames that are too long for tar-v7. (PR/414)
1995 - Variables augmented with `+=' are now automatically flattened (i.e.,
1996 trailing backslashes removed) and then wrapped around 80 columns
1997 (adding trailing backslashes). In previous versions, a long series
2003 would result in a single-line definition of VAR that could possibly
2004 exceed the maximum line length of some make implementations.
2006 Non-augmented variables are still output as they are defined in
2011 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
2012 Works the same as the old Fortran 77 implementation; just replace
2013 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
2014 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
2016 - Support for conditional _LISP.
2018 - Support for conditional -hook and -local rules (PR/428).
2020 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
2022 - Automake will not write any Makefile.ins after the first error it
2023 encounters. The previous Makefile.ins (if any) will be left in
2024 place. (Warnings will not prevent output, but remember they can
2025 be turned into errors with -Werror.)
2027 - The restriction that SUBDIRS must contain direct children is gone.
2030 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
2031 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
2033 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2035 Bugs fixed in 1.8.5:
2037 * Long-standing bugs:
2039 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
2040 so that `make distclean' and `make maintainer-clean' can work.
2042 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
2044 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
2046 - Polish diagnostic when no input file is found.
2048 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2050 Bugs fixed in 1.8.4:
2052 * Long-standing bugs:
2054 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
2055 overridden by the user.
2057 - Honor PATH_SEPARATOR in various places of the Automake package, for
2060 - Adjust dependency tracking mode detection to ICC 8.0's new output.
2063 - Fix install-sh so it can install the `mv' binary... using `mv'.
2065 - Fix tru64 dependency tracking for libtool objects.
2067 - Work around Exuberant Ctags when creating a TAGS files in a directory
2068 without files to scan but with subdirectories to include.
2070 * Bugs introduced by 1.8:
2072 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
2073 not defined in the same conditions as the _LDADD that uses it.
2075 - Do not warn when JAVAROOT is overridden, this is legitimate.
2077 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2079 Bugs fixed in 1.8.3:
2081 * Long-standing bugs:
2083 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
2084 or any of the other *dir variables contain a space.
2086 Please note that Automake does not and cannot support spaces in
2087 filenames that are involved during the build. This change affects
2088 only installation paths, so that `make install' does not bomb out
2089 in packages configured with
2090 ./configure --prefix '/c/Program Files'
2092 - Fix the depfiles output so it works with GNU sed (<4.1) even when
2093 POSIXLY_CORRECT is set.
2095 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
2096 since Autoconf 2.54, which defines LIBOBJS itself.
2098 - Fix a potential (but unlikely) race condition in parallel elisp
2099 builds. (Introduced in 1.7.3.)
2101 - Do not assume that users override _DEPENDENCIES in all conditions
2102 where Automake will try to define them.
2104 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
2105 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
2108 This fix also affects the $(mkdir_p) variable defined since
2109 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
2110 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
2112 - Secure temporary directory creation in `make distcheck'. (PR/413)
2114 - Do not generate two build rules for `parser.h' when the
2115 parser appears in two different conditionals.
2117 - Work around a Solaris 8 /bin/sh bug in the test for dependency
2118 checking. Usually ./configure will not pick this shell; so this
2119 fix only helps cases where the shell is forced to /bin/sh.
2121 * Bugs introduced by 1.8:
2123 - In some situations (hand-written `m4_include's), aclocal would
2124 call the `File::Spec->rel2abs' method, which was only introduced
2125 in Perl 5.6. This new version reestablish support Perl 5.005.
2127 It is likely that the next major Automake releases will require at
2128 least Perl 5.6. Consider upgrading your development environment
2129 if you are still using the five-year-old Perl 5.005.
2131 - Automake would sometimes fail to define rules for targets listed
2132 in variables defined in multiple conditions. For instance on
2138 it would define only the `a.$(OBJEXT): a.c' rule and omit the
2139 `b.$(OBJEXT): b.c' rule.
2141 * New sections in manual:
2143 - Third-Party Makefiles: how to interface third party Makefiles.
2144 - Upgrading: upgrading packages to newer Automake versions.
2145 - Multiple Outputs: handling tools that produce many outputs.
2147 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2151 * A (well known) portability bug slipped in the changes made to
2152 install-sh in Automake 1.8.1. The broken install-sh would refuse to
2153 install anything on Tru64.
2155 * Fix install rules for conditionally built python files. (This never
2158 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2162 * Bugs introduced by 1.8:
2164 - Fix Config.pm import error with old Perl versions (at least
2165 5.005_03). One symptom is that aclocal could not find its macro
2168 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
2169 created by `make install' are always world readable, even if the
2170 installer happens to have an overly restrictive umask (e.g. 077).
2171 This was a mistake and has been reverted. There are at least two
2172 reasons why we must not use `-m 0755':
2173 - it causes special bits like SGID to be ignored,
2174 - it may be too restrictive (some setups expect 775 directories).
2176 - Fix aclocal to honor definitions located in files which have been
2177 m4_included manually. aclocal 1.8 had been updated to check
2178 m4_included files for new requirements, but forgot that these
2179 m4_included files can also provide new definitions.
2181 Note that if you have such a setup, we recommend you get rid of
2182 it. In the past, there was a reason to m4_include files manually:
2183 aclocal used to duplicate entire M4 files into aclocal.m4, even
2184 files that were distributed. Some packages were therefore
2185 m4_including the distributed file directly, and playing some
2186 tricks to ensure aclocal would not copy that file to aclocal.m4,
2187 in order to limit the amount of duplication. Since aclocal 1.8.x
2188 will precisely output m4_includes for local M4 files, we recommend
2189 that you clean up your setup, removing all manual m4_includes and
2190 letting aclocal output them.
2192 - Output detailed menus in the Info version if the Automake manual,
2193 so that Emacs can locate the indexes.
2195 - configure.ac and configure were listed twice in DIST_COMMON (an
2196 internal variable where Automake lists configury files to
2197 distribute). This was harmless, but unaesthetic.
2199 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
2200 This was an issue only in the Automake package itself, not in
2203 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
2204 DEST:SRC. This was wrong, as some packages do
2205 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
2208 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
2209 argument. This caused two kinds of failures:
2210 - Rules installing data in a conditionally defined directory
2211 failed when that directory was undefined. In this case no
2212 argument was supplied.
2213 - `make installdirs' failed, because several directories were
2214 passed to $(mkdir_p). This was an issue only on platform
2215 were $(mkdir_p) is implemented with `install-sh -d'.
2216 $(mkdir_p) as been changed to accept 0 or more arguments, as
2219 * Long-standing bugs:
2221 - Fix an unexpected diagnostic occurring when users attempt
2222 to override some internal variables that Automake appends to.
2224 - aclocal now scans configure.ac for macro definitions (PR/319).
2226 - Fix a portability issue with OSF1/Tru64 Make. If a directory
2227 distributes files which are outside itself (this usually occurs
2228 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
2229 from a parent package), then `make distcheck' fails due to an
2230 optimization performed by OSF1/Tru64 Make in its VPATH handling.
2231 (tests/subpkg2.test failure)
2233 - Fix another portability issue with Sun and OSF1/Tru64 Make.
2234 In a VPATH-build configuration, `make install' would install
2235 nobase_ files to wrong locations.
2237 - Fix a Perl `uninitialized value' diagnostic occurring when
2238 automake complains that a Texinfo file does not have a
2239 @setfilename statement.
2241 - Erase config.status.lineno during `make distclean'. This file
2242 can be created by config.status. Automake already knew about
2243 configure.lineno, but forgot config.status.lineno.
2245 - Distribute all files, even those which are built and installed
2246 conditionally. This change affects files listed in conditionally
2247 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
2248 as well as those listed in conditionally defined dist_*_DATA,
2249 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
2251 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
2252 doesn't conform to POSIX.
2254 - Normalize help strings for configure variables and options added
2259 - Check for python2.4 in AM_PATH_PYTHON.
2261 * Spurious failures in test suite:
2263 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
2264 tests/ltconv.test: fix failures with CVS Libtool.
2265 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
2266 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
2267 fix failures with old Texinfo versions.
2269 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2275 - The NEWS file is more verbose.
2279 - Autoconf 2.58 or greater is required.
2283 - Default source file names in the absence of a _SOURCES declaration
2284 are made by removing any target extension before appending `.c', so
2285 to make the libtool module `foo.la' from `foo.c', you only need to
2288 lib_LTLIBRARIES = foo.la
2289 foo_la_LDFLAGS = -module
2291 For backward compatibility, foo_la.c will be used instead of
2292 foo.c if this file exists or is the explicit target of a rule.
2293 However -Wobsolete will warn about this deprecated naming.
2295 - AR's `cru' flags are now set in a global ARFLAGS variable instead
2296 of being hard-coded in each $(AR) invocation, so they can be
2297 substituted from configure.ac. This has been requested by people
2298 dealing with non-POSIX ar implementations.
2300 - New warning option: -Woverride. This will warn about any user
2301 target or variable definitions which override Automake
2304 - Texinfo rules back up and restore info files when makeinfo fails.
2306 - Texinfo rules now support the `html' target.
2307 Running this requires Texinfo 4.0 or greater.
2309 `html' is a new recursive target, so if your package mixes
2310 hand-crafted `Makefile.in's with Automake-generated
2311 `Makefile.in's, you should adjust the former to support (or
2312 ignore) this target so that `make html' recurses successfully. If
2313 you had a custom `html' rule in your `Makefile.am', it's better to
2314 rename it as `html-local', otherwise your rule will override
2315 Automake's new rule (you can check that by running `automake
2316 -Woverride') and that will stop the recursion to subdirectories.
2318 Last but not least, this `html' rule is declared PHONY, even when
2319 overridden. Fortunately, it appears that few packages use a
2320 non-PHONY `html' rule.
2322 - Any file which is m4_included from configure.ac will appear as a
2323 configure and Makefile.in dependency, and will be automatically
2326 - The rules for rebuilding Makefiles and Makefile.ins will now
2327 rebuild all Makefiles and all Makefile.ins at once when one of
2328 configure's dependencies has changed. This is considerably faster
2329 than previous implementations, where config.status and automake
2330 were run separately in each directory (this still happens when you
2331 change a Makefile.am locally, without touching configure.ac or
2332 friends). Doing this also solves a longstanding issue: these
2333 rebuild rules failed to work when adding new directories to the
2334 tree, forcing you to run automake manually.
2336 - For similar reasons, the rules to rebuild configure,
2337 config.status, and aclocal.m4 are now defined in all directories.
2338 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
2339 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
2340 should better define them in all directories. This is easily done
2341 using an AC_SUBST (make sure you prefix these dependencies with
2342 $(top_srcdir) since this variable will appear at different
2343 levels of the build tree).
2345 - aclocal will now use `m4_include' instead of copying local m4
2346 files into aclocal.m4. (Local m4 files are those you ship with
2347 your project, other files will be copied as usual.)
2349 Because m4_included files are automatically distributed, it means
2350 for most projects there is no point in EXTRA_DISTing the list of
2351 m4 files which are used. (You can probably get rid of
2352 m4/Makefile.am if you had one.)
2354 - aclocal will avoid touching aclocal.m4 when possible, so that
2355 Autom4te's cache isn't needlessly invalidated. This behavior can
2356 be switched off with the new `--force' option.
2358 - aclocal now uses Autoconf's --trace to detect macros which are
2359 actually used and will no longer include unused macros simply
2360 because they where mentioned. This was often the case for macros
2361 called conditionally.
2363 - New options no-dist and no-dist-gzip.
2365 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2366 py-compile, and ylwrap, now all understand --version and --help.
2368 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2369 links as part of the distclean target and including source files in
2372 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2373 argument. The latter can be used to override the default behavior
2374 (which is to abort).
2376 - Automake will exit with $? = 63 on version mismatch. (So does
2377 Autoconf 2.58) missing knows this, and in this case it will
2378 emulate the tools as if they were absent. Because older versions
2379 of Automake and Autoconf did not use this exit code, this change
2380 will only be useful in projects generated with future versions of
2383 - When using AC_CONFIG_FILES with multiple input files, Automake
2384 generates the first ".in" input file for which a ".am" exists.
2385 (Former versions would try to use only the first input file.)
2387 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2388 idiom to disable byte-compilation of lisp_LISP files, it is
2389 recommended that you switch to using lisp_DATA. Note that
2390 this is not strictly equivalent: lisp_DATA will install elisp
2391 files even if emacs is not installed, while *_LISP do not
2392 install anything unless emacs is found.
2394 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2395 available. This selection is achieved through the Makefile
2396 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2397 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2398 `$(install_sh) -m 0755 -d'.
2402 - Because `mkdir -p' is available on most platforms, and we can use
2403 `install-sh -d' when it is not, the use of the mkinstalldirs
2404 script is being phased out. `automake --add-missing' no longer
2405 installs it, and if you remove mkinstalldirs from your package,
2406 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2408 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2409 gettextize and autopoint will install it when needed. Automake
2410 will continue to define the $(mkinstalldirs) and to distribute
2411 mkinstalldirs when this script is in the source tree.
2413 - AM_PROG_CC_STDC is now empty. The content of this macro was
2414 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2415 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2416 renaming should be safe, even if you have to support several,
2417 versions of Automake, because AC_PROG_CC defines this variable
2418 since Autoconf 2.54.)
2420 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2421 variable to override the aclocal.m4 dependencies computed
2422 (inaccurately) by older versions of Automake. Because Automake
2423 now tracks configure's m4 dependencies accurately (see m4_include
2424 above), the use of ACLOCAL_M4_SOURCES should be considered
2425 obsolete and will be flagged as such when running `automake
2430 - Defining programs conditionally using Automake conditionals no
2431 longer leads to a combinatorial explosion. The following
2432 construct used to be troublesome when used with dozens of
2447 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2449 - Due to implementation constraints, previous versions of Automake
2450 proscribed multiple conditional definitions of some variables
2460 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2461 This restriction has been lifted, and these variables now
2462 support multiple conditional definitions as do other variables.
2464 - Cleanup the definitions of $(distdir) and $(top_distdir).
2465 $(top_distdir) now points to the root of the distribution
2466 directory created during `make dist', as it did in Automake 1.4,
2467 not to the root of the build tree as it did in intervening
2468 versions. Furthermore these two variables are now only defined in
2469 the top level Makefile, and passed to sub-directories when running
2472 - The --no-force option now correctly checks the Makefile.in's
2473 dependencies before deciding not to update it.
2475 - Do not assume that make files are called Makefile in cleaning rules.
2477 - Update .info files in the source tree, not in the build tree. This
2478 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2479 used to update these files in the build tree (previous versions did
2480 it in the source tree too), and it caused several problems, varying
2481 from mere annoyance to portability issues.
2483 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2484 when --add-missing and --force-missing are used. For backward
2485 compatibility --add-missing will continue to install COPYING (in
2486 `gnu' strictness) when none of these three files exist, but this
2487 use is deprecated: you should better choose a license yourself and
2488 install it once for all in your source tree (and in your code
2491 - Fix ylwrap so that it does not overwrite header files that haven't
2492 changed, as the inline rule already does.
2494 - User-defined rules override automake-defined rules for the same
2495 targets, even when rules do not have commands. This is not new
2496 (and was documented), however some of the automake-generated
2497 rules have escaped this principle in former Automake versions.
2498 Rules for the following targets are affected by this fix:
2500 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2501 info, info-am, install-data-am, install-exec-am, install-info,
2502 install-info-am, install-man, installcheck-am, maintainer-clean,
2503 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2504 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2506 Practically it means that an attempt to supplement the dependencies
2507 of some target, as in
2509 clean: my-clean-rule
2511 will now *silently override* the automake definition of the
2512 rule for this target. Running `automake -Woverride' will diagnose
2513 all such overriding definitions.
2515 It should be noted that almost all of these targets support a *-local
2516 variant that is meant to supplement the automake-defined rule
2517 (See node `Extending' in the manual). The above rule should
2520 clean-local: my-clean-rule
2522 These *-local targets have been documented since at least
2523 Automake 1.2, so you should not fear the change if you have
2524 to support multiple automake versions.
2528 - The Automake manual is now distributed under the terms of the GNU FDL.
2530 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2532 - core dumps are no longer removed by the cleaning rules. There are
2533 at least three reasons for this:
2534 1. These files should not be created by any build step,
2535 so their removal do not fit any of the cleaning rules.
2536 Actually, they may be precious to the developer.
2537 2. If such file is created during a build, then it's clearly a
2538 bug Automake should not hide. Not removing the file will
2539 cause `make distcheck' to complain about its presence.
2540 3. Operating systems have different naming conventions for
2541 core dump files. A core file on one system might be a
2542 completely legitimate data file on another system.
2544 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2545 defined by Automake. This means that any definition in the
2546 environment will be used, unless overridden in the Makefile.am or
2547 on the command line. The old behavior, where these variables were
2548 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2549 AC_ARG_VARing each variable from configure.ac.
2551 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2552 documented. (The is not a new feature, these variables have
2553 been there since at least Automake 1.4.)
2555 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2557 Bugs fixed in 1.7.9:
2558 * Fix install-strip to work with nobase_ binaries.
2559 * Fix renaming of #line directives in ylwrap.
2560 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2562 Bugs fixed in 1.7.8:
2563 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2564 * Fix detection of Debian's install-info, broken since version 1.5.
2565 (Debian bug #213524).
2566 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2567 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2569 Bugs fixed in 1.7.7:
2570 * The implementation of automake's --no-force option is unreliable,
2571 so this option is ignored in this version. A real fix will appear in
2572 Automake 1.8. (Debian Bug #206299)
2573 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2574 argument is given. (PR/399)
2575 * Do not warn about leading `_' in variable names, even with -Wportability.
2576 * Support user redefinitions of TEXINFO_TEX.
2577 * depcomp: support AIX Compiler version 6.
2578 * Fix missing rebuilds during `make dist' with BSD make.
2579 (Could produce tarballs containing out-of-date files.)
2580 * Resurrect multilib support.
2581 * Noteworthy manual updates:
2582 - Extending aclocal: how to write m4 macros that won't trigger warnings
2584 - A Shared Library: Rewrite and split into subsections.
2586 Bugs fixed in 1.7.6:
2587 * Fix depcomp's icc mode for ICC 7.1.
2588 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2589 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2590 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2591 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2592 * Remove Latin-1 characters from elisp-comp.
2593 * Update the manual's @dircategory to match the Free Software Directory.
2595 Bugs fixed in 1.7.5:
2596 * Update install-sh's license to remove an advertising clause.
2597 (Debian bug #191717)
2598 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2599 that caused invalid Makefile.ins to be generated.
2600 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2601 * New FAQ entry: renamed objects.
2603 Bugs fixed in 1.7.4:
2604 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2605 the Emacs implementation)
2606 * Fix output of aclocal.m4 dependencies in subdirectories.
2607 * Use `mv -f' instead of `mv' in fastdep rules.
2608 * Upgrade mdate-sh to work on OS/2.
2609 * Don't byte-compile elisp files when ELCFILES is set empty.
2610 (this documented feature was broken by 1.7.3)
2611 * Diagnose trailing backslashes on last line of Makefile.am.
2612 * Diagnose whitespace following trailing backslashes.
2613 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2614 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2616 * `make install' will build `BUILT_SOURCES' first.
2617 * Minor documentation fixes.
2619 Bugs fixed in 1.7.3:
2620 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2621 * Query distutils for `pythondir' and `pythonexecdir', instead of
2622 using an hardcoded path. This should allow builds on 64-bit
2623 distributions that usually use lib64/ instead of lib/.
2624 * AM_PATH_PYTHON will also search for python2.3.
2625 * elisp files are now built all at once instead of one by one. Besides
2626 incurring a speed-up, this is required to support interdependent elisp files.
2627 * Support for DJGPP:
2628 - `make distcheck' will now work in `_inst/' and `_build' instead
2629 of `=inst/' and `=build/'
2630 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2631 - install/uninstall `*.i[0-9][0-9]'-style info files
2632 - more changes that affect only the Automake package (not its output)
2633 * Fix some incompatibilities with upcoming perl-5.10.
2634 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2635 PACKAGE and VERSION.
2637 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2638 is troublesome with gcc and Solaris compilers. (PR/385)
2639 - makedepend mode: work with Libtool. (PR/385 too)
2641 * better support for unusual gettext setups, such as multiple po/ directories
2643 - Flag missing po/ and intl/ directories as warnings, not errors.
2644 - Disable these warnings if po/ does not exist.
2645 * Noteworthy manual updates:
2647 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2649 - Document `AM_YFLAGS = -d'. (PR/382)
2651 Bugs fixed in 1.7.2:
2652 * Fix installation and uninstallation of Info files built in subdirectories.
2653 * Do not run `./configure --with-included-gettext' during `make distcheck'
2654 if AM_GNU_GETTEXT([external]) is used.
2655 * Correctly uninstall renamed man pages.
2656 * Do not strip escaped newline in variables defined in one condition
2657 and augmented in another condition.
2658 * Fix ansi2knr rules for LIBOBJS sources.
2659 * Clean all known Texinfo index files, not only those which appear to
2660 be used, because we cannot know which indexes are used in included files.
2661 (PR/375, Debian Bug #168671)
2662 * Honor only the first @setfilename seen in a Texinfo file.
2663 * Treat "required file X not found" diagnostics as errors (exit status 1).
2664 * Don't complain that a required file is not found when it is a Makefile
2666 * Don't use single suffix inference rules when building `.info'-less
2667 Info files, for the sake of Solaris make.
2668 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2669 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2670 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2671 * Fix building of deansified files from subdirectories. (PR/370)
2672 * Add missing `fi' in the .c->.obj rules.
2673 * Improve install-sh to work even when names contain spaces or certain
2674 (but not all) shell metachars.
2675 * Fix the following spurious failures in the test suite:
2676 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2677 * Noteworthy manual updates:
2678 - Augment the section about BUILT_SOURCES.
2679 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2681 Bugs fixed in 1.7.1:
2682 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2684 * Aclocal should now recognize macro names containing parentheses, e.g.
2685 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2686 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2688 * Install Python files even if they were built. (PR/369)
2689 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2690 version might not be defined in the latter. (PR/358)
2691 * Reorder arguments passed to a couple of commands, so things works
2692 when POSIXLY_CORRECT=1.
2693 * Fix a regex that can cause Perl to segfault on large input.
2695 * Fix distribution of packages that have some sources defined conditionally,
2696 as in the `Conditional compilation using Automake conditionals' example
2698 * Fix spurious test suite failures on IRIX.
2699 * Don't report a required variable as undefined if it has been
2700 defined conditionally for the "right" conditions.
2701 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2702 `make distcheck' fails.
2703 * Fix distribution of included Makefile fragment, so we don't create
2704 spurious directories in the distribution. (PR/366)
2705 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2708 * Autoconf 2.54 is required.
2709 * `aclocal' and `automake' will no longer warn about obsolete
2710 configure macros. This is done by `autoconf -Wobsolete'.
2711 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2712 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2713 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2714 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2715 `configure.ac' for you.
2716 * Support for per-program and per-library `_CPPFLAGS'.
2717 * New `ctags' target (builds CTAGS files).
2718 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2719 (see `automake --help' or the manual for a list of them).
2720 * Honor the WARNINGS environment variable.
2721 * Omit the call to depcomp when using gcc3: call the compiler directly.
2722 * A new option, std-options, tests that programs support --help and --version
2723 when `make installcheck' is run. This is enabled by --gnits.
2724 * Texinfo rules now support the `ps' and `pdf' targets.
2725 * Info files are now created in the build directory, not the source directory.
2726 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2728 * `make distcheck' will enforce DESTDIR support by attempting
2730 * `+=' can be used in conditionals, even if the augmented variable
2731 was defined for another condition.
2732 * Makefile fragments (inserted with `include') are always distributed.
2733 * Use Autoconf's --trace interface to inspect configure.ac and get
2734 a more accurate view of it.
2735 * Add support for extending aclocal's default macro search path
2736 using a `dirlist' file within the aclocal directory.
2737 * automake --output-dir is deprecated.
2738 * The part of the distcheck target that checks whether uninstall actually
2739 removes all installed files has been moved in a separate target,
2740 distuninstallcheck, so it can be overridden easily.
2744 * Support for AM_INIT_GETTEXT([external])
2745 * Bug fixes, including:
2746 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2747 - nobase_ programs and scripts honor --program-transform correctly.
2748 - Erase configure.lineno during `make distclean'.
2749 - Erase YACC and LEX outputs during `make maintainer-clean'.
2752 * Many bug fixes, including:
2753 - Requiring the current version works.
2754 - Fix "$@" portability issues (for Zsh).
2755 - Fix output of dummy dependency files in presence of post-processed
2757 - Don't compute dependencies in background to avoid races with libtool.
2758 - Fix handling of _OBJECTS variables for targets sharing source variables.
2759 - Check dependency mode for Java when AM_PROG_GCJ is used.
2762 * automake --output-dir is deprecated
2763 * Many bug fixes, including:
2764 - Don't choke on AM_LDFLAGS definitions.
2765 - Clean libtool objects from subdirectories.
2766 - Allow configure variables with reserved suffix and unknown prefix
2767 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2768 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2771 * Autoconf 2.52 is required.
2772 * automake no longer run libtoolize.
2773 This is the job of autoreconf (from GNU Autoconf).
2774 * `dist' generates all the archive flavors, as did `dist-all'.
2775 * `dist-gzip' generates the Gzip tar file only.
2776 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2777 explosion. Makefile.in's keep a reasonable size.
2778 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2779 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2781 * `#line' of Lex and Yacc files are properly set.
2782 * EXTRA_DIST can contain generated directories.
2783 * Support for dot-less extensions in suffix rules.
2784 * The part of the distcheck target that checks whether distclean actually
2785 cleans all built files has been moved in a separate target, distcleancheck,
2786 so it can be overridden easily.
2787 * `make distcheck' will pass additional options defined in
2788 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2789 * Fixed CDPATH portability problems, in particular for MacOS X.
2790 * Fixed handling of nobase_ targets.
2791 * Fixed support of implicit rules leading to .lo objects.
2792 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2793 * Added uninstall-hook target
2794 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2795 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2796 (Note that "pkgname" is not "tarname", see the manual for details.)
2797 It is also possible to pass a list of global Automake options as
2798 first argument to this new form of AM_INIT_AUTOMAKE.
2799 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2800 to be a real assembler.
2801 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2802 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2803 * aclocal and automake are also installed with the version number
2804 appended, and some of the install directory names have changed.
2805 This lets you have multiple versions installed simultaneously.
2806 * Support for parsers and lexers in subdirectories.
2809 * Support for `configure.ac'.
2810 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2811 * `make dist-all' is much faster.
2812 * Allows '@' AC_SUBSTs in macro names.
2813 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2814 * User-side dependency tracking. Developers no longer need GNU make
2816 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2817 * Most files are correctly handled if they appear in subdirs
2818 For instance, a _DATA file can appear in a subdir
2819 * GNU tar is no longer required for `make dist'
2820 * Added support for `dist_' and `nodist_' prefixes
2821 * Added support for `nobase_' prefix
2822 * Compiled Java support
2823 * Support for per-executable and per-library compilation flags
2827 * Added support for the Fortran 77 programming language.
2828 * Re-indexed the Automake Texinfo manual.
2829 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2830 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2831 * Support for latest autoconf, including support for objext
2832 * Can now put `.' in SUBDIRS to control build order
2833 * `include' command and `+=' support for macro assignment
2834 * Dependency tracking no long susceptible to deleted header file problem
2835 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2840 * Better Cygwin32 support
2841 * Support for suffix rules with _SOURCES variables
2842 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2843 * @LEXLIB@ no longer required when lex source seen
2844 Lex support in `missing', and new lex macro. Update your missing script.
2845 * Built-in support for assembly
2846 * aclocal gives error if `AM_' macro not found
2847 * Passed YFLAGS, not YACCFLAGS, to yacc
2848 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2849 * Dependencies computed as a side effect of compilation
2850 * Preliminary support for Java
2851 * DESTDIR support at "make install" time
2852 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2856 * Better DejaGnu support
2857 * Added no-installinfo option
2858 * Added Emacs Lisp support
2859 * Added --no-force option
2860 * Included `aclocal' program
2861 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2862 * Now uses `AM_' macro names everywhere
2863 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2864 ansi2knr now works correctly on K&R sources
2865 * Better C++, yacc, lex support
2866 * Will compute _DEPENDENCIES variables automatically if not supplied
2867 * Will interpolate $(...) and ${...} when examining contents of a variable
2868 * .deps files now in build directory, not source directory; dependency
2869 handling generally rewritten
2870 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2871 * can now put config.h into a subdir
2872 * Added dist-all target
2873 * Support for install-info program (see texinfo 3.9)
2874 * Support for "yacc -d"
2875 * configure substitutions are automatically discovered and included
2876 in generated Makefile.in
2877 * Special --cygnus mode
2878 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2879 when making distribution. Some dependencies are auto-ignored.
2880 * Changed how libraries are specified in _LIBRARIES variable
2881 * Full libtool support, from Gord Matzigkeit
2882 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2883 AM_CONFIG_HEADER handles it automatically
2884 * Texinfo output files no longer need .info extension
2885 * Added `missing' support
2887 * Conditionals in Makefile.am, from Ian Taylor
2891 * distcheck target runs install and installcheck targets
2892 * Added preliminary support for DejaGnu.
2897 * More libtool fixes from Gord Matzigkeit; libtool support is still
2899 * Added support for jm_MAINTAINER_MODE
2901 * New "distcheck" target
2905 * mkinstalldirs and mdate-sh now appear in directory specified by
2907 * Removed DIST_SUBDIRS, DIST_OTHER
2908 * AC_ARG_PROGRAM only required when an actual program exists
2909 * dist-hook target now run before distribution packaged up; idea from
2910 Dieter Baron. Other hooks exist, too.
2911 * Preliminary (unfinished) support for libtool
2912 * Added short option names.
2913 * Better "dist" support when gluing together multiple packages
2917 * Documentation updates (many from François Pinard)
2918 * strictness `normal' now renamed to `foreign'
2919 * Renamed --install-missing to --add-missing
2920 * Now handles AC_CONFIG_AUX_DIR
2921 * Now handles TESTS macro
2922 * DIST_OTHER renamed to EXTRA_DIST
2923 * DIST_SUBDIRS is deprecated
2924 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2925 * Better error messages in many cases
2926 * Program names are canonicalized
2927 * Added "check" prefix; from Gord Matzigkeit
2931 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2932 * Beginnings of a test suite
2933 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2934 * Doesn't print anything when running
2935 * Beginnings of MAINT_CHARSET support
2936 * Can specify version in AUTOMAKE_OPTIONS
2937 * Most errors recognizable by Emacs' M-x next-error
2938 * Added --verbose option
2939 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2940 configure-generated names
2941 * Required macros now distributed in aclocal.m4
2943 * --strictness=gnu is default
2947 * More sophisticated configure.in scanning; now understands ALLOCA and
2948 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2949 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2950 * CONFIG_HEADER variable now obsolete
2951 * Can handle multiple Texinfo sources
2952 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2953 * HEADERS variable no longer needed; now can put .h files directly into
2954 foo_SOURCES variable.
2955 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2956 corresponding ".in" files are included in the distribution.
2959 * Added --gnu and --gnits options
2960 * More standards checking
2962 * Cleaned up 'dist' targets
2963 * Added AUTOMAKE_OPTIONS variable and several options
2964 * Now scans configure.in to get some information (preliminary)
2967 * Works with Perl 4 again
2970 * Added --install-missing option.
2971 * Pretty-prints generated macros and rules
2972 * Comments in Makefile.am are placed more intelligently in Makefile.in
2973 * Generates .PHONY target
2974 * Rule or macro in Makefile.am now overrides contents of Automake file
2975 * Substantial cleanups from François Pinard
2979 * Works with Perl 4 again.
2982 * New uniform naming scheme.
2983 * --strictness option
2985 * '.c' files corresponding to '.y' or '.l' files are automatically
2987 * Many bug fixes and cleanups
2990 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2993 * Bug fixes in 'clean' code.
2994 * Now generates 'installdirs' target.
2995 * man page installation reworked.
2996 * 'make dist' no longer re-creates all Makefile.in's.
2999 * Reimplemented in Perl
3000 * Added --amdir option (for debugging)
3001 * Texinfo support cleaned up.
3002 * Automatic de-ANSI-fication cleaned up.
3003 * Cleaned up 'clean' targets.
3006 * Automatic dependency tracking
3007 * More documentation
3008 * New variables DATA and PACKAGEDATA
3009 * SCRIPTS installed using $(INSTALL_SCRIPT)
3010 * No longer uses double-colon rules
3012 * Changes in advance of internationalization
3016 Copyright (C) 1995-2018 Free Software Foundation, Inc.
3018 This program is free software; you can redistribute it and/or modify
3019 it under the terms of the GNU General Public License as published by
3020 the Free Software Foundation; either version 2, or (at your option)
3023 This program is distributed in the hope that it will be useful,
3024 but WITHOUT ANY WARRANTY; without even the implied warranty of
3025 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
3026 GNU General Public License for more details.
3028 You should have received a copy of the GNU General Public License
3029 along with this program. If not, see <https://www.gnu.org/licenses/>.