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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
73 - 'install-sh' now ensures that nobody can cross privilege boundaries by
74 pre-creating symlink on the directory inside "/tmp".
76 - 'automake' does not depend on the 'none' subroutine of the List::Util
77 module anymore to support older Perl version. (automake bug#30631)
79 - A regression in AM_PYTHON_PATH causing the rejection of non literal
80 minimum version parameter hasn't been fixed. (automake bug#30616)
82 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
86 * Miscellaneous changes
88 - When subdir-objects is in effect, Automake will now construct
89 shorter object file names when no programs and libraries name
90 clashes are encountered. This should make the discouraged use of
91 'foo_SHORTNAME' unnecessary in many cases.
95 - Automatic dependency tracking has been fixed to work also when the
96 'subdir-object' option is used and some 'foo_SOURCES' definition
97 contains unexpanded references to make variables, as in, e.g.:
99 a_src = sources/libs/aaa
101 foo_SOURCES = $(a_src)/bar.c $(b_src)/baz.c
103 With such a setup, the created makefile fragment containing dependency
104 tracking information will be correctly placed under the directories
105 named 'sources/libs/aaa/.deps' and 'sources/bbb/.deps', rather than
106 mistakenly under directories named (literally!) '$(src_a)/.deps' and
107 '$(src_b)/.deps' (this was the first part of automake bug#13928).
109 Notice that in order to fix this bug we had to slightly change the
110 semantics of how config.status bootstraps the makefile fragments
111 required for the dependency tracking to work: rather than attempting
112 to parse the Makefiles via grep and sed trickeries only, we actually
113 invoke 'make' on a slightly preprocessed version of those Makefiles,
114 using a private target that is only meant to bootstrap the required
117 - The 'subdir-object' option no longer causes object files corresponding
118 to source files specified with an explicit '$(srcdir)' component to be
119 placed in the source tree rather than in the build tree.
121 For example, if Makefile.am contains:
123 AUTOMAKE_OPTIONS = subdir-objects
124 foo_SOURCES = $(srcdir)/foo.c $(srcdir)/s/bar.c $(top_srcdir)/baz.c
126 then "make all" will create 'foo.o' and 's/bar.o' in $(builddir) rather
127 than in $(srcdir), and will create 'baz.o' in $(top_builddir) rather
128 than in $(top_srcdir).
130 This was the second part of automake bug#13928.
132 - Installed 'aclocal' m4 macros can now accept installation directories
133 containing '@' characters (automake bug#20903)
135 - "./configure && make dist" no longer fails when a distributed file depends
136 on one from BUILT_SOURCES.
138 - When combining AC_LIBOBJ or AC_FUNC_ALLOCA with the
139 "--disable-dependency-tracking" configure option in an out of source
140 build, the build sub-directory defined by AC_CONFIG_LIBOBJ_DIR is now
141 properly created. (automake bug#27781)
143 - The time printed by 'mdate-sh' is now using the UTC time zone to support
144 the reproducible build effort. (automake bug#20314)
146 - The elisp byte-compilation rule now uses byte-compile-dest-file-function,
147 rather than byte-compile-dest-file, which was obsoleted in 2009. We expect
148 that Emacs-26 will continue to support the old function, but will complain
149 loudly, and that Emacs-27 will remove support for it altogether.
153 - A custom testsuite driver for the Guile Scheme SRFI-64 API has been added
154 to the "contrib" section. This allows a more convenient way to test Guile
155 code without having to use low primitives such as exit status. See
156 SRFI-64 API specification for more details:
157 <https://srfi.schemers.org/srfi-64/srfi-64.html>
159 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
165 - The code has been adapted to remove a warning present since Perl
166 5.22 stating that "Unescaped left brace in regex is deprecated".
167 This warning has become an hard error in Perl 5.26 (bug#22372).
169 - The generated Makefiles do not rely on the obsolescent GZIP
170 environment variable which was used for passing arguments to
171 'gzip'. Compatibility with old versions has been
172 preserved. (bug#20132)
174 * Miscellaneous changes:
176 - Support the Windows version of the Intel C Compiler (icl) in the
177 'compile' script in the same way the (compatible) Microsoft C
178 Compiler is supported.
180 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
184 * Improvements and refactorings in the install-sh script:
186 - It has been modernized, and now makes the following assumptions
188 (1) a working 'dirname' program is available;
189 (2) the ${var:-value} shell parameters substitution works;
190 (3) the "set -f" and "set +f" shell commands work, and, respectively,
191 disable and enable shell globbing.
193 - The script implements stricter error checking, and now it complains
194 and bails out if any of the following expectations is not met:
195 (1) the options -d and -t are never used together;
196 (2) the argument passed to option -t is a directory;
197 (3) if there are two or more SOURCEFILE arguments, the
198 DESTINATION argument must be a directory.
200 * Automake-generated testsuites:
202 - The default test-driver used by the Automake-generated testsuites
203 now appends the result and exit status of each "plain" test to the
204 associated log file (automake bug#11814).
206 - The perl implementation of the TAP testsuite driver is no longer
207 installed in the Automake's scripts directory, and is instead just
208 distributed as a "contrib" addition. There should be no reason to
209 use this implementation anyway in real packages, since the awk+shell
210 implementation of the TAP driver (which is documented in the manual)
211 is more portable and has feature parity with the perl implementation.
213 - The rule generating 'test-suite.log' no longer risk incurring in an
214 extra useless "make all" recursive invocation in some corner cases
215 (automake bug#16302).
219 - Automake bug#18286: "make distcheck" could sometimes fail to detect
220 files missing from the distribution tarball, especially in those cases
221 where both the generated files and their dependencies are explicitly
222 in $(srcdir). An important example of this are *generated* makefile
223 fragments included at Automake time in Makefile.am; e.g.:
226 $(srcdir)/fragment.am: $(srcdir)/data.txt $(srcdir)/preproc.sh
227 cd $(srcdir) && $(SHELL) preproc.sh <data.txt >fragment.am
228 include $(srcdir)/fragment.am
231 If the use forgot to add data.txt and/or preproc.sh in the distribution
232 tarball, "make distcheck" would have erroneously succeeded! This issue
235 - As a consequence of the previous change, "make distcheck" will run
236 using '$(distdir)/_build/sub' as the build directory, rather than
237 simply '$(distdir)/_build' (as it was the case for Automake 1.14 and
238 earlier). Consequently, the './configure' and 'make' invocations
239 issued by the distcheck recipe now have $(srcdir) equal to '../..',
240 rather than to just '..'. Dependent and similar variables (e.g.,
241 '$(top_srcdir)') are also changed accordingly.
243 Thus, Makefiles that made assumptions about the exact values of the
244 build and source directories used by "make distcheck" will have to
245 be adjusted. Notice that making such assumptions was a bad and
246 unsupported practice anyway, since the exact locations of those
247 directories should be considered implementation details, and we
248 reserve the right to change them at any time.
250 * Miscellaneous bugs fixed:
252 - The expansion of AM_INIT_AUTOMAKE ends once again with a trailing
253 newline (bug#16841). Regression introduced in Automake 1.14.
255 - We no longer risk to use '$ac_aux_dir' before it's defined (see
256 automake bug#15981). Bug introduced in Automake 1.14.
258 - The code used to detect whether the currently used make is GNU make
259 or not (relying on the private macro 'am__is_gnu_make') no longer
260 risks causing "Arg list too long" for projects using automatic
261 dependency tracking and having a ton of source files (bug#18744).
263 - Automake tries to offer a more deterministic output for generated
264 Makefiles, in the face of the newly-introduced randomization for
265 hash keys order in Perl 5.18.
267 - In older Automake versions, if a user defined one single Makefile
268 fragment (say 'foo.am') to be included via Automake includes in
269 his main Makefile.am, and defined a custom make rule to generate that
270 file from other data, Automake used to spuriously complain with some
271 message like "... overrides Automake target '$(srcdir)/foo.am".
272 This bug is now fixed.
274 - The user can now extend the special .PRECIOUS target, the same way
275 he could already do with the .MAKE .and .PHONY targets.
277 - Some confusing typos have been fixed in the manual and in few warning
278 messages (automake bug#16827 and bug#16997).
280 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
286 - The user is no longer allowed to override the --srcdir nor the --prefix
287 configure options used by "make distcheck" (bug#14991).
289 - Fixed a gross inefficiency in the recipes for installing byte-compiled
290 python files, that was causing an O(N^2) performance on the number N of
291 files, instead of the expected O(N) performance. Note that this bug
292 was only relevant when the number of python files was high (which is
293 unusual in practice).
295 - Automake try to offer a more deterministic output for warning messages,
296 in the face of the newly-introduced randomization for hash keys order
299 - The 'test-driver' script now actually error out with a clear error
300 message on the most common invalid usages.
302 - Several spurious failures/hangs in the testsuite (bugs #14706, #14707,
303 #14760, #14911, #15181, #15237).
305 * Documentation fixes:
307 - Fixed typos in the 'fix-timestamp.sh' example script that made it
310 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
314 * C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
316 - The 'compile' script is now unconditionally required for all packages
317 that perform C compilation (if you are using the '--add-missing'
318 option, automake will fetch that script for you, so you shouldn't
319 need any explicit adjustment). This new behaviour is needed to avoid
320 obscure errors when the 'subdir-objects' option is used, and the
321 compiler is an inferior one that doesn't grasp the combined use of
322 both the "-c -o" options; see discussion about automake bug#13378 for
324 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
325 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
327 - The next major Automake version (2.0) will unconditionally activate
328 the 'subdir-objects' option. In order to smooth out the transition,
329 we now give a warning (in the category 'unsupported') whenever a
330 source file is present in a subdirectory but the 'subdir-object' is
331 not enabled. For example, the following usage will trigger such a
334 bin_PROGRAMS = sub/foo
335 sub_foo_SOURCES = sub/main.c sub/bar.c
337 - Automake will automatically enhance the autoconf-provided macro
338 AC_PROG_CC to force it to check, at configure time, that the
339 C compiler supports the combined use of both the '-c' and '-o'
340 options. The result of this check is saved in the cache variable
341 'am_cv_prog_cc_c_o', and said result can be overridden by
342 pre-defining that variable.
344 - The AM_PROG_CC_C_O macro can still be called, albeit that should no
345 longer be necessary. This macro is now just a thin wrapper around the
346 Automake-enhanced AC_PROG_CC. This means, among the other things,
347 that its behaviour is changed in three ways:
349 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
350 macro behind the scenes.
352 2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
353 and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
354 dynamically computed only at configure runtime (really!) from
355 the content of the '$CC' variable.
357 3. It no longer automatically AC_DEFINE the C preprocessor
358 symbol 'NO_MINUS_C_MINUS_O'.
362 - Automake can now be instructed to place '.info' files generated from
363 Texinfo input in the builddir rather than in the srcdir; this is done
364 specifying the new automake option 'info-in-builddir'. This feature
365 was requested by the developers of GCC, GDB, GNU binutils and the GNU
366 bfd library. See the extensive discussion about automake bug#11034
369 - For quite a long time, Automake has been implementing an undocumented
370 hack which ensured that '.info' files which appeared to be cleaned
371 (by being listed in the CLEANFILES or DISTCLEANFILES variables) were
372 built in the builddir rather than in the srcdir; this hack was
373 introduced to ensure better backward-compatibility with package
374 such as Texinfo, which do things like:
376 info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
377 DISTCLEANFILES = texinfo texinfo-* info*.info*
378 # Do not create info files for distribution.
382 in order not to distribute generated '.info' files.
384 Now that we have the 'info-in-builddir' option that explicitly causes
385 generated '.info' files to be placed in the builddir, this hack should
386 be longer necessary, so we deprecate it with runtime warnings.
387 It will be removed altogether in Automake 2.0.
389 * Relative directory in Makefile fragments:
391 - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
392 (and their short versions, '%D%' and '%C%' respectively) can now be used
393 in an included Makefile fragment. The former is substituted with the
394 relative directory of the included fragment (compared to the top-level
395 including Makefile), and the latter with the canonicalized version of
396 the same relative directory.
399 bin_PROGRAMS = # will be updated by included Makefile fragments
400 include src/Makefile.inc
402 # in 'src/Makefile.inc':
403 bin_PROGRAMS += %reldir%/foo
404 %canon_reldir%_foo_SOURCES = %reldir%/bar.c
406 This should be especially useful for packages using a non-recursive
409 * Deprecated distribution formats:
411 - The 'shar' and 'compress' distribution formats are deprecated, and
412 scheduled for removal in Automake 2.0. Accordingly, the use of the
413 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
414 (in the 'obsolete' category), and the recipes of the Automake-generated
415 targets 'dist-shar' and 'dist-tarZ' will unconditionally display
416 (non-fatal) warnings at make runtime.
418 * New configure runtime warnings about "rm -f" support:
420 - To simplify transition to Automake 2.0, the shell code expanded by
421 AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
422 'rm' program in PATH doesn't complain when called without any
423 non-option argument if the '-f' option is given (so that commands like
424 "rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
425 If this is not the case, the configure script is aborted, to call the
426 attention of the user on the issue, and invite him to fix his PATH.
427 The checked 'rm' behavior is very widespread in the wild, and will be
428 required by future POSIX versions:
430 <http://austingroupbugs.net/view.php?id=542>
432 The user can still force the configure process to complete even in the
433 presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
434 environment variable to "yes". And the generated Makefiles should
435 still work correctly even when such broken 'rm' is used. But note
436 that this will no longer be the case with Automake 2.0 though, so, if
437 you encounter the warning, please report it to us ASAP (and try to fix
438 your environment as well).
440 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
446 - Fix a minor regression introduced in Automake 1.13.3: when two or more
447 user-defined suffix rules were present in a single Makefile.am,
448 automake would needlessly include definition of some make variables
449 related to C compilation in the generated Makefile.in (bug#14560).
451 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
455 * Documentation fixes:
457 - The documentation no longer mistakenly reports that the obsolete
458 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
459 to be removed in Automake 2.0.
463 - Byte-compilation of Emacs lisp files could fail spuriously on
464 Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
466 - If the same user-defined suffixes were transformed into different
467 Automake-known suffixes in different Makefile.am files in the same
468 project, automake could get confused and generate inconsistent
469 Makefiles (automake bug#14441).
470 For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
471 and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
472 would have mistakenly placed into 'Makefile.in' rules to compile
473 "*.c" files into object files, and into 'sub/Makefile.in' rules to
474 compile "*.cc" files into object files --- rather than the other
475 way around. This is now fixed.
479 - The test cases no longer have the executable bit set. This should
480 make it clear that they are not meant to be run directly; as
481 explained in t/README, they can only be run through the custom
482 'runtest' script, or by a "make check" invocation.
484 - The testsuite has seen the introduction of a new helper function
485 'run_make', and several related changes. These serve a two-fold
488 1. Remove brittleness due to the use of "make -e" in test cases.
490 2. Seamlessly allow the use of parallel make ("make -j...") in the
491 test cases, even where redirection of make output is involved
492 (see automake bug#11413 for a description of the subtle issues
495 - Several spurious failures have been fixed (they hit especially
496 MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
497 #14498, #14499, #14500, #14501, #14517 and #14528.
499 - Some other minor miscellaneous changes and fixlets.
501 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
505 * Documentation fixes:
507 - The long-deprecated but still supported two-arguments invocation form
508 of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
509 thing to do, given that support for such usage might need to remain
510 in place for an unspecified amount of time in order to cater to people
511 who want to define the version number for their package dynamically at
512 configure runtime (unfortunately, Autoconf does not yet support this
513 scenario, so we cannot delegate the work to it).
515 - The serial testsuite harness is no longer reported as "deprecated",
516 but as "discouraged". We have no plan to remove it, nor to make its
517 use cause runtime warnings.
519 - The parallel testsuite is no longer reported as "experimental"; it
520 is well tested, and should be stable now.
522 - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
523 'dist-tarZ' options are obsolescent, and their use is deprecated
524 in the documentation.
526 - Other minor miscellaneous fixes and improvements; in particular,
527 some improvements in cross-references.
529 * Obsolescent features:
531 - Use of suffix-less info files (that can be specified through the
532 '@setfilename' macro in Texinfo input files) is discouraged, and
533 its use will raise warnings in the 'obsolete' category. Simply
534 use the '.info' extension for all your info files, transforming
537 @setfilename myprogram
541 @setfilename myprogram.info
543 - Use of Texinfo input files with '.txi' or '.texinfo' extensions
544 is discouraged, and its use will raise warnings in the 'obsolete'
545 category. You are advised to simply use the '.texi' extension
550 - When the 'ustar' option is used, the generated configure script no
551 longer risks hanging during the tests for the availability of the
552 'pax' utility, even if the user running configure has a UID or GID
553 that requires more than 21 bits to be represented.
554 See automake bug#8343 and bug#13588.
556 - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
557 again, as they did in Automake 1.12.x (albeit printing runtime
558 warnings in the 'obsolete' category). Removing them has turned
559 out to be a very bad idea, because it complicated distro packing
560 enormously. Making them issue fatal warnings, as we did in
561 Automake 1.13, has turned out to be a similarly very bad idea,
562 for exactly the same reason.
564 - aclocal will no longer error out if the first local m4 directory
565 (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
566 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
567 a warning in the 'unsupported' category. This is done to support
568 some pre-existing real-world usages. See automake bug#13514.
570 - aclocal will no longer consider directories for extra m4 files more
571 than once, even if they are specified multiple times. This ensures
572 packages that specify both
574 AC_CONFIG_MACRO_DIR([m4]) in configure.ac
575 ACLOCAL_AMFLAGS = -I m4 in Makefile.am
577 will work correctly, even when the 'm4' directory contains no
578 package-specific files, but is used only to install third-party
579 m4 files (as can happen with e.g., "libtoolize --install").
580 See automake bug#13514.
582 - Analysis of make flags in Automake-generated rules has been made more
583 robust, and more future-proof. For example, in presence of make that
584 (like '-I') take an argument, the characters in said argument will no
585 longer be spuriously considered as a set of additional make options.
586 In particular, automake-generated rules will no longer spuriously
587 believe to be running in dry mode ("make -n") if run with an invocation
588 like "make -I noob"; nor will they believe to be running in keep-going
589 mode ("make -k") if run with an invocation like "make -I kool"
590 (automake bug#12554).
592 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
598 - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
599 causes a clear and helpful error message, instead of obscure ones
600 (issue introduced in Automake 1.13).
602 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
608 - ylwrap renames properly header guards in generated header files
609 (*.h), instead of leaving Y_TAB_H.
611 - ylwrap now also converts header guards in implementation files
612 (*.c). Because ylwrap failed to rename properly #include in the
613 implementation files, current versions of Bison (e.g., 2.7)
614 duplicate the generated header file in the implementation file.
615 The header guard then protects the implementation file from
616 duplicate definitions from the header file.
618 * Version requirements:
620 - Autoconf 2.65 or greater is now required.
622 - The rules to build PDF and DVI output from Texinfo input now
623 require Texinfo 4.9 or later.
627 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
628 option) has been removed. See discussion about automake bug#11034
629 for more background: <https://debbugs.gnu.org/11034>.
631 - The deprecated aclocal option '--acdir' has been removed. You
632 should use the options '--automake-acdir' and '--system-acdir'
633 instead (which have been introduced in Automake 1.11.2).
635 - The following long-obsolete m4 macros have been removed:
637 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
638 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
639 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
640 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
641 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
642 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
643 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
644 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
645 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
646 of the now-removed automatic de-ANSI-fication
649 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
651 - Use of the long-deprecated two- and three-arguments invocation forms
652 of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
653 though (albeit with a warning in the 'obsolete' category), to cater
654 for people who want to define the version number for their package
655 dynamically (e.g., from the current VCS revision). We'll have to
656 continue this support until Autoconf itself is fixed to allow better
657 support for such dynamic version numbers.
659 * Elisp byte-compilation:
661 - The byte compilation of '.el' files into '.elc' files is now done
662 with a suffix rule. This has simplified the compilation process, and
663 more importantly made it less brittle. The downside is that emacs is
664 now invoked once for each '.el' files, which cause some noticeable
665 slowdowns. These should however be mitigated on multicore machines
666 (which are becoming the norm today) if concurrent make ("make -j")
669 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
670 files in the same subdirectory; for example, byte-compiling of file
671 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
672 'foo.elc'. This behaviour is backward-incompatible with older
673 Automake versions, but it is more natural and more sane. See also
676 - The Emacs invocation performing byte-compilation of '.el' files honors
677 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
678 one is developer-reserved and the latter one user-reserved.
680 - The 'elisp-comp' script, once provided by Automake, has been rendered
681 obsoleted by the just-described changes, and thus removed.
683 * Changes to Automake-generated testsuite harnesses:
685 - The parallel testsuite harness (previously only enabled by the
686 'parallel-tests' option) is the default one; the older serial
687 testsuite harness will still be available through the use of the
688 'serial-tests' option (introduced in Automake 1.12).
690 - The 'color-tests' option is now unconditionally activated by default.
691 In particular, this means that testsuite output is now colorized by
692 default if the attached terminal seems to support ANSI escapes, and
693 that the user can force output colorization by setting the variable
694 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
695 for backward-compatibility, although it's a handled as a no-op now.
697 * Silent rules support:
699 - Support for silent rules is now always active in Automake-generated
700 Makefiles. So, although the verbose output is still the default,
701 the user can now always use "./configure --enable-silent-rules" or
702 "make V=0" to enable quieter output in the package he's building.
704 - The 'silent-rules' option has now become a no-op, preserved for
705 backward-compatibility only. In particular, its use no longer
706 disables the warnings in the 'portability-recursive' category.
710 - The rules to build PDF and DVI files from Texinfo input now require
711 Texinfo 4.9 or later.
713 - The rules to build PDF and DVI files from Texinfo input now use the
714 '--build-dir' option, to keep the auxiliary files used by texi2dvi
715 and texi2pdf around without cluttering the build directory, and to
716 make it possible to run the "dvi" and "pdf" recipes in parallel.
718 * Automatic remake rules and 'missing' script:
720 - The 'missing' script no longer tries to update the timestamp of
721 out-of-date files that require a maintainer-specific tool to be
722 remade, in case the user lacks such a tool (or has a too-old version
723 of it). It just gives a useful warning, and in some cases also a
724 tip about how to obtain such a tool.
726 - The missing script has thus become useless as a (poor) way to work
727 around the sketched-timestamps issues that can happen for projects
728 that keep generated files committed in their VCS repository. Such
729 projects are now encouraged to write a custom "fix-timestamps.sh"
730 script to avoid such issues; a simple example is provided in the
731 "CVS and generated files" chapter of the automake manual.
735 - The user can now define his own recursive targets that recurse
736 in the directories specified in $(SUBDIRS). This can be done by
737 specifying the name of such targets in invocations of the new
738 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
742 - Any failure in the recipe of the "tags", "ctags", "cscope" or
743 "cscopelist" targets in a subdirectory is now propagated to the
744 top-level make invocation.
746 - Tags are correctly computed also for files in _SOURCES variables that
747 only list files with non-standard suffixes (see automake bug#12372).
749 * Improvements to aclocal and related rebuilds rules:
751 - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
752 are now traced by aclocal, and can be used to declare the local m4
753 include directories. Formerly, one had to specify it with an explicit
754 '-I' option to the 'aclocal' invocation.
756 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
757 Automake versions will warn about its use, and later version will
758 remove support for it altogether.
760 * The depcomp script:
762 - Dropped support for libtool 1.4.
764 - Various internal refactorings. They should cause no visible change,
765 but the chance for regression is there anyway, so please report any
766 unexpected or suspicious behaviour.
768 - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
769 This should cause no problem, since icc 8.0 has been released in
770 December 2003 -- almost nine years ago.
772 - Support for tcc (the Tiny C Compiler) has been improved, and is now
773 handled through a dedicated 'tcc' mode.
777 - ylwrap generates header guards with a single '_' for series of non
778 alphabetic characters, instead of several. This is what Bison >=
781 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
783 Bugs fixed in 1.12.6:
785 * Python-related bugs:
787 - The default installation location for python modules has been improved
788 for Python 3 on Debian and Ubuntu systems, changing from:
790 ${prefix}/lib/python3/dist-packages
794 ${prefix}/lib/python3.x/site-packages
796 This change should ensure modules installed using the default ${prefix}
797 "/usr/local" are found by default by system python 3.x installations.
798 See automake bug#10227.
800 - Python byte-compilation supports the new layout mandated by PEP-3147,
801 with its __pycache__ directory (automake bug#8847).
803 * Build system issues:
805 - The maintainer rebuild rules for Makefiles and aclocal.m4 in
806 Automake's own build system works correctly again (bug introduced
811 - The Vala-related tests has been changed to adjust to the removal of
812 the 'posix' profile in the valac compiler. See automake bug#12934
815 - Some spurious testsuite failures related to older tools and systems
818 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
824 - The AM_PROG_VALAC macro has been enhanced to takes two further
825 optional arguments; it's signature now being
827 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
828 [ACTION-IF-NOT-FOUND])
830 - By default, AM_PROG_VALAC no longer aborts the configure invocation
831 if the Vala compiler found is too old, but simply prints a warning
832 messages (as it did when the Vala compiler was not found). This
833 should avoid unnecessary difficulties for end users that just want
834 to compile the unmodified, distributed Vala-generated C sources,
835 but happens to have an old Vala compiler in their PATH. This fixes
838 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
839 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
840 This is a better default, because with it a triggered makefile rule
841 invoking a Vala compilation will clearly fail with an informative error
842 message like "valac: command not found", rather than silently, with
843 the error possibly going unnoticed or triggering harder-to-diagnose
844 fallout failures in later steps.
846 * Miscellaneous changes:
848 - automake and aclocal no longer honours the 'perllibdir' environment
849 variable. That had always been intended only as an hack required in
850 the testsuite, not meant for any use beyond that.
852 Bugs fixed in 1.12.5:
854 * Long-standing bugs:
856 - Automake no longer generates spurious remake rules invoking autoheader
857 to regenerate the template corresponding to header files specified after
858 the first one in AC_CONFIG_HEADERS (automake bug#12495).
860 - When wrapping Microsoft tools, the 'compile' script falls back to
861 finding classic 'libname.a' style libraries when 'name.lib' and
862 'name.dll.lib' aren't available.
864 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
868 * Warnings and deprecations:
870 - Warnings in the 'obsolete' category are enabled by default both in
871 automake and aclocal.
873 * Miscellaneous changes:
875 - Some testsuite weaknesses and spurious failures have been fixed.
877 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
881 * Miscellaneous changes:
883 - The '.m4' files provided by Automake no longer define serial numbers.
884 This should cause no difference in the behaviour of aclocal though.
886 - Some testsuite weaknesses and spurious failures have been fixed.
888 - There is initial support for automatic dependency tracking with the
889 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
891 Bugs fixed in 1.12.3:
893 * Long-standing bugs:
895 - Instead of renaming only self-references of files (typically for
896 #lines), ylwrap now also renames references to the other generated
897 files. This fixes support for GLR and C++ parsers from Bison (PR
898 automake/491 and automake bug#7648): 'parser.c' now properly
899 #includes 'parser.h' instead of 'y.tab.h'.
901 - Generated files unknown to ylwrap are now preserved. This fixes
902 C++ support for Bison (automake bug#7648): location.hh and the
903 like are no longer discarded.
905 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
909 * Warnings and deprecations:
911 - Automake now issues a warning (in the 'portability' category) if
912 'configure.in' is used instead of 'configure.ac' as the Autoconf
913 input file. Such a warning will also be present in the next
914 Autoconf version (2.70).
918 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
919 order (as done by the other recursive rules), rather than in the
920 inverse order. They used to do that in order to work a round a
921 limitation in an older implementation of the automatic dependency
922 tracking support, but that limitation had been lifted years ago
923 already, when the automatic dependency tracking based on side-effects
924 of compilation had been introduced.
926 - Cleaning rules for compiled objects (both "plain" and libtool) work
927 better when subdir objects are involved, not triggering a distinct
928 'rm' invocation for each such object. They do so by removing *any*
929 compiled object file that is in the same directory of a subdir
930 object. See automake bug#10697.
932 * Silent rules support:
934 - A new predefined $(AM_V_P) make variable is provided; it expands
935 to a shell conditional that can be used in recipes to know whether
936 make is being run in silent or verbose mode.
938 Bugs fixed in 1.12.2:
940 * SECURITY VULNERABILITIES!
942 - The 'distcheck' recipe no longer grants temporary world-write
943 permissions on the extracted distdir. Even if such rights were
944 only granted for a vanishingly small time window, the implied
945 race condition proved to be enough to allow a local attacker
946 to run arbitrary code with the privileges of the user running
947 "make distcheck". This is CVE-2012-3386.
949 * Long-standing bugs:
951 - The "recheck" targets behaves better in the face of build failures
952 related to previously failed tests. For example, if a test is a
953 compiled program that must be rerun by "make recheck", and its
954 compilation fails, it will still be rerun by further "make recheck"
955 invocations. See automake bug#11791.
957 * Bugs introduced by 1.12.1:
959 - Automake provides once again the '$(mkdir_p)' make variable and the
960 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
961 for better backward-compatibility.
963 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
967 * New supported languages:
969 - Support for Objective C++ has been added; it should work similarly to
970 the support for Objective C.
972 * Deprecated obsolescent features:
974 - Use of the long-deprecated two- and three-arguments invocation forms
975 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
976 category. Starting from some future major Automake release (likely
977 post-1.13), such usages will no longer be allowed.
979 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
980 now deprecated (its use triggers a warning in the 'obsolete' category).
981 It will be removed in the next major Automake release (1.13).
983 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
984 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
985 m4 macro are deprecated, eliciting a warning in the 'obsolete'
988 * Miscellaneous changes:
990 - The Automake test cases now require a proper POSIX-conforming shell.
991 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
992 be accepted. In most cases, the user shouldn't have to specify such
993 POSIX shell explicitly, since it will be looked up at configure time.
994 Still, when this lookup fails, or when the user wants to override its
995 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
996 to the shell that will be used to run the Automake test cases).
998 Bugs fixed in 1.12.1:
1000 * Bugs introduced by 1.12:
1002 - Several weaknesses in Automake's own build system and test suite
1005 * Bugs introduced by 1.11.3:
1007 - When given non-option arguments, aclocal rejects them, instead of
1008 silently ignoring them.
1010 * Long-standing bugs:
1012 - When the 'color-tests' option is in use, forcing of colored testsuite
1013 output through "AM_COLOR_TESTS=always" works even if the terminal is
1014 a non-ANSI one, i.e., if the TERM environment variable has a value of
1017 - Several inefficiencies and poor performances in the implementation
1018 of the parallel-tests 'check' and 'recheck' targets have been fixed.
1020 - The post-processing of output "#line" directives done the ylwrap
1021 script is more faithful w.r.t. files in a subdirectory; for example,
1022 if the processed file is "src/grammar.y", ylwrap will correctly
1023 produce directives like:
1024 #line 7 "src/grammar.y"
1029 * Bugs with new Perl versions:
1031 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
1033 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1037 * Obsolete features removed:
1039 - The never documented nor truly used script 'acinstall' has been
1042 - Support for automatic de-ANSI-fication has been removed.
1044 - The support for the "obscure" multilib feature has been removed
1045 from Automake core (but remains available in the 'contrib/'
1046 directory of the Automake distribution).
1048 - Support for ".log -> .html" conversion and the check-html and
1049 recheck-html targets has been removed from Automake core (but
1050 remains available in the 'contrib/' directory of the Automake
1053 - The deprecated 'lzma' compression format for distribution archives
1054 has been removed, in favor of 'xz' and 'lzip'.
1056 - The obsolete AM_WITH_REGEX macro has been removed.
1058 - The long-deprecated options '--output-dir', '--Werror' and
1059 '--Wno-error' have been removed.
1061 - The chapter on the history of Automake has been moved out of the
1062 reference manual, into a new dedicated Texinfo file.
1066 - New 'cscope' target to build a cscope database for the source tree.
1068 * Changes to Automake-generated testsuite harnesses:
1070 - The new automake option 'serial-tests' has been introduced. It can
1071 be used to explicitly instruct automake to use the older serial
1072 testsuite harness. This is still the default at the moment, but it
1073 might change in future versions.
1075 - The 'recheck' target (provided by the parallel testsuite harness) now
1076 depends on the 'all' target. This allows for a better user-experience
1077 in test-driven development. See automake bug#11252.
1079 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
1080 and unexpected or internal error, or a failure to set up the test case
1081 scenario) have their outcome reported as an 'ERROR' now. Previous
1082 versions of automake reported such an outcome as a 'FAIL' (the only
1083 difference with normal failures being that hard errors were counted
1084 as failures even when the test originating them was listed in
1087 - The testsuite summary displayed by the parallel-test harness has a
1088 completely new format, that always list the numbers of passed, failed,
1089 xfailed, xpassed, skipped and errored tests, even when these numbers
1090 are zero (but using smart coloring when the color-tests option is in
1093 - The default testsuite driver offered by the 'parallel-tests' option is
1094 now implemented (partly at least) with the help of automake-provided
1095 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
1096 on code in the generated Makefile.in.
1097 This has two noteworthy implications. The first one is that projects
1098 using the 'parallel-tests' option should now either run automake with
1099 the '--add-missing' option, or manually copy the 'test-driver' script
1100 into their tree. The second, and more important, implication is that
1101 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
1102 no longer be used to define a test runner, and the command specified
1103 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
1104 program or script. For example, this is still a valid usage (albeit
1105 a little contorted):
1107 TESTS_ENVIRONMENT = \
1108 if test -n '$(STRICT_TESTS)'; then \
1109 maybe_errexit='-e'; \
1113 LOG_COMPILER = $(SHELL) $$maybe_errexit
1115 OTOH, this is no longer a valid usage:
1117 TESTS_ENVIRONMENT = \
1118 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
1122 TESTS_ENVIRONMENT = \
1123 run_with_perl_or_shell () \
1125 if grep -q '^#!.*perl' $$1; then
1131 LOG_COMPILER = run_with_perl_or_shell
1133 - The package authors can now use customary testsuite drivers within
1134 the framework provided by the 'parallel-tests' testsuite harness.
1135 Consistently with the existing syntax, this can be done by defining
1136 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
1138 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
1139 to redirect/define file descriptors used by the test scripts.
1141 - The parallel-tests harness generates now, in addition the '.log' files
1142 holding the output produced by the test scripts, a new set of '.trs'
1143 files, holding "metadata" derived by the execution of the test scripts;
1144 among such metadata are the outcomes of the test cases run by a script.
1146 - Initial and still experimental support for the TAP test protocol is
1149 * Changes to Yacc and Lex support:
1151 - C source and header files derived from non-distributed Yacc and/or
1152 Lex sources are now removed by a simple "make clean" (while they were
1153 previously removed only by "make maintainer-clean").
1155 - Slightly backward-incompatible change, relevant only for use of Yacc
1156 with C++: the extensions of the header files produced by the Yacc
1157 rules are now modelled after the extension of the corresponding
1158 sources. For example, yacc files named "foo.y++" and "bar.yy" will
1159 produce header files named "foo.h++" and "bar.hh" respectively, where
1160 they would have previously produced header files named simply "foo.h"
1161 and "bar.h". This change offers better compatibility with 'bison -o'.
1163 * Miscellaneous changes:
1165 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
1166 rather than 1, if the vala compiler found is too old.
1168 - The build system of Automake itself now avoids the use of make
1169 recursion as much as possible.
1171 - Automake now prefers to quote 'like this' or "like this", rather
1172 than `like this', in diagnostic message and generated Makefiles,
1173 to accommodate the new GNU Coding Standards recommendations.
1175 - Automake has a new option '--print-libdir' that prints the path of the
1176 directory containing the Automake-provided scripts and data files.
1178 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
1180 - The rules to create pdf, dvi and ps output from Texinfo files now
1181 works better with modern 'texi2dvi' script, by explicitly passing
1182 it the '--clean' option to ensure stray auxiliary files are not
1183 left to clutter the build directory.
1185 - Automake can now generate silenced rules for texinfo outputs.
1187 - Some auxiliary files that are automatically distributed by Automake
1188 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
1189 C sources) might now be listed in the DIST_COMMON variable in many
1190 Makefile.in files, rather than in the top-level one.
1192 - Messages of types warning or error from 'automake' and 'aclocal'
1193 are now prefixed with the respective type, and presence of -Werror
1196 - Automake's early configure-time sanity check now tries to avoid
1197 sleeping for a second, which slowed down cached configure runs
1198 noticeably. In that case, it will check back at the end of the
1199 configure script to ensure that at least one second has passed, to
1200 avoid time stamp issues with makefile rules rerunning autotools
1203 - The warnings in the category 'extra-portability' are now enabled by
1204 '-Wall'. In previous versions, one has to use '-Wextra-portability'
1209 - Various minor bugfixes for recent or long-standing bugs.
1211 * Bugs introduced by 1.11:
1213 - The AM_COND_IF macro also works if the shell expression for the
1214 conditional is no longer valid for the condition.
1216 - The automake-provided parallel testsuite harness no longer fails
1217 with BSD make used in parallel mode when there are test scripts in
1218 a subdirectory, like in:
1220 TESTS = sub/foo.test sub/bar.test
1222 * Long-standing bugs:
1224 - Automake's own build system finally have a real "installcheck" target.
1226 - Vala-related cleanup rules are now more complete, and work better in
1229 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
1230 now automatically distributed also if the directory of the auxiliary
1231 files coincides with the top-level directory.
1233 - Automake now detects the presence of the '-d' flag in the various
1234 '*YFLAGS' variables even when their definitions involve indirections
1235 through other variables, such as in:
1237 AM_YFLAGS = $(foo_opts)
1239 - Automake now complains if a '*YFLAGS' variable has any conditional
1240 content, not only a conditional definition.
1242 - Explicit enabling and/or disabling of Automake warning categories
1243 through the '-W...' options now always takes precedence over the
1244 implicit warning level implied by Automake strictness (foreign, gnu
1245 or gnits), regardless of the order in which such strictness and
1246 warning flags appear. For example, a setting like:
1247 AUTOMAKE_OPTIONS = -Wall --foreign
1248 will cause the warnings in category 'portability' to be enabled, even
1249 if those warnings are by default disabled in 'foreign' strictness.
1251 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1253 Bugs fixed in 1.11.5:
1255 * Bugs introduced by 1.11.3:
1257 - Vala files with '.vapi' extension are now recognized and handled
1258 correctly again. See automake bug#11222.
1260 - Vala support work again for projects that contain some program
1261 built from '.vala' (and possibly '.c') sources and some other
1262 program built from '.c' sources *only*. See automake bug#11229.
1264 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1268 * Miscellaneous changes:
1270 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
1271 symbol index) modifiers as well as the "s" action, as the symbol index
1272 is created unconditionally by Microsoft lib. Also, the "q" (quick)
1273 action is now a synonym for "r" (replace). Also, the script has been
1274 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
1276 - When the 'compile' script is used to wrap MSVC, it now accepts an
1277 optional space between the -I, -L and -l options and their respective
1278 arguments, for better POSIX compliance.
1280 - There is an initial, experimental support for automatic dependency
1281 tracking with tcc (the Tiny C Compiler). Its associated depmode is
1282 currently recognized as "icc" (but this and other details are likely
1283 to change in future versions).
1285 - Automatic dependency tracking now works also with the IBM XL C/C++
1286 compilers, thanks to the new new depmode 'xlc'.
1288 Bugs fixed in 1.11.4:
1290 * Bugs introduced by 1.11.2:
1292 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
1293 no longer cause spurious failures upon "make install".
1295 - The user can now instruct the 'uninstall-info' rule not to update
1296 the '${infodir}/dir' file by exporting the environment variable
1297 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
1298 with how the 'install-info' rule operates since automake 1.11.2.
1300 * Long-standing bugs:
1302 - It is now possible for a foo_SOURCES variable to hold Vala sources
1303 together with C header files, as well as with sources and headers for
1304 other supported languages (e.g., C++). Previously, only mixing C and
1305 Vala sources was supported.
1307 - If "aclocal --install" is used, and the first directory specified with
1308 '-I' is non-existent, aclocal will now create it before trying to copy
1311 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
1312 install rules to create an empty $(foodir) directory; for example, if
1313 Makefile.am contains something like:
1315 pkglibexec_SCRIPTS =
1317 pkglibexec_SCRIPTS += bar.sh
1320 the $(pkglibexec) directory will not be created upon "make install".
1322 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1326 * Miscellaneous changes:
1328 - Automake's own build system is more silent by default, making use of
1329 the 'silent-rules' option.
1331 - The master copy of the 'gnupload' script is now maintained in gnulib,
1334 - The 'missing' script no longer tries to wrap calls to 'tar'.
1336 - "make dist" no longer wraps 'tar' invocations with the 'missing'
1337 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
1338 shouldn't be using BTW ;-) no longer invokes the 'missing' script
1339 to wrap tar, but simply invokes the 'tar' program itself.
1341 - "make dist" can now create lzip-compressed tarballs.
1343 - In the Automake info documentation, the Top node and the nodes about
1344 the invocation of the automake and aclocal programs have been renamed;
1345 now, calling "info automake" will open the Top node, while calling
1346 "info automake-invocation" and "info aclocal-invocation" will access
1347 the nodes about the invocation of respectively automake and aclocal.
1349 - Automake is now distributed as a gzip-compressed and an xz-compressed
1350 tarball. Previously, bzip2 was used instead of xz.
1352 - The last relics of Python 1.5 support have been removed from the
1353 AM_PATH_PYTHON macro.
1355 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
1356 and adds them to the normal list of dependencies, but without
1357 overwriting the foo_DEPENDENCIES variable, which is normally computed
1360 Bugs fixed in 1.11.3:
1362 * Bugs introduced by 1.11.2:
1364 - Automake now correctly recognizes the prefix/primary combination
1365 'pkglibexec_SCRIPTS' as valid.
1367 - The parallel-tests harness no longer trips on sed implementations
1368 with stricter limits on the length of input lines (problem seen at
1369 least on Solaris 8).
1371 * Long-standing bugs:
1373 - The "deleted header file problem" for *.am files is avoided by stub
1374 rules. This allows 'make' to trigger a rerun of 'automake' also if
1375 some previously needed '.am' file has been removed.
1377 - The 'silent-rules' option now generates working makefiles even
1378 for the uncommon 'make' implementations that do not support the
1379 nested-variables extension to POSIX 2008. For such 'make'
1380 implementations, whether a build is silent is determined at
1381 configure time, and cannot be overridden at make time with
1382 "make V=0" or "make V=1".
1384 - Vala support now works better in VPATH setups.
1386 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1390 * Changes to aclocal:
1392 - The `--acdir' option is deprecated. Now you should use the new options
1393 `--automake-acdir' and `--system-acdir' instead.
1395 - The `ACLOCAL_PATH' environment variable is now interpreted as a
1396 colon-separated list of additional directories to search after the
1397 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
1398 and before the system acdir (by default ${prefix}/share/aclocal).
1400 * Miscellaneous changes:
1402 - The Automake support for automatic de-ANSI-fication has been
1403 deprecated. It will probably be removed in the next major Automake
1406 - The `lzma' compression scheme and associated automake option `dist-lzma'
1407 is obsoleted by `xz' and `dist-xz' due to upstream changes.
1409 - You may adjust the compression options used in dist-xz and dist-bzip2.
1410 The default is now merely -e for xz, but still -9 for bzip; you may
1411 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
1412 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
1414 - The `compile' script now converts some options for MSVC for a better
1415 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
1417 - The py-compile script now accepts empty arguments passed to the options
1418 `--destdir' and `--basedir', and complains about unrecognized options.
1419 Moreover, a non-option argument or a special `--' argument terminates
1420 the list of options.
1422 - A developer that needs to pass specific flags to configure at "make
1423 distcheck" time can now, and indeed is advised to, do so by defining
1424 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
1425 instead of the old DISTCHECK_CONFIGURE_FLAGS.
1426 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
1427 user; still, the old Makefile.am files that used to define it will
1428 still continue to work as before.
1430 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
1431 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
1432 This new macro is required for LIBRARIES and LTLIBRARIES when automake
1433 is run with -Wextra-portability and -Werror.
1435 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
1436 file generated by automake-provided rules by defining the special make
1437 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
1439 - The `install-info' rule can now be instructed not to create/update
1440 the `${infodir}/dir' file, by exporting the new environment variable
1441 `AM_UPDATE_INFO_DIR' to the value "no".
1443 Bugs fixed in 1.11.2:
1445 * Bugs introduced by 1.11:
1447 - The parallel-tests driver no longer produces erroneous results with
1448 Tru64/OSF 5.1 sh upon unreadable log files.
1450 - The `parallel-tests' test driver does not report spurious successes
1451 when used with concurrent FreeBSD make (e.g., "make check -j3").
1453 - When the parallel-tests driver is in use, automake now explicitly
1454 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
1455 instead of issuing confusing and apparently unrelated error messages
1456 (e.g., "non-POSIX variable name", "bad characters in variable name",
1457 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
1458 silently producing broken `Makefile.in' files.
1460 - The `silent-rules' option now truly silences all compile rules, even
1461 when dependency tracking is disabled. Also, when `silent-rules' is
1462 not used, `make' output no longer contains spurious backslash-only
1463 lines, thus once again matching what Automake did before 1.11.
1465 - The AM_COND_IF macro also works if the shell expression for the
1466 conditional is no longer valid for the condition.
1468 * Long-standing bugs:
1470 - The order of Yacc and Lex flags is fixed to be consistent with other
1471 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
1472 $(LFLAGS), so that the user variables override the developer variables.
1474 - "make distcheck" now correctly complains also when "make uninstall"
1475 leaves one and only one file installed in $(prefix).
1477 - A "make uninstall" issued before a "make install", or after a mere
1478 "make install-data" or a mere "make install-exec" does not spuriously
1481 - Automake now warns about more primary/directory invalid combinations,
1482 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
1484 - Rules generated by Automake now try harder to not change any files when
1485 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
1486 Yacc source files and the rule to update config.h.
1488 - Several scripts and the parallel-tests testsuite driver now exit with
1489 the right exit status upon receiving a signal.
1491 - A per-Makefile.am setting of -Werror does not erroneously carry over
1492 to the handling of other Makefile.am files.
1494 - The code for automatic dependency tracking works around a Solaris
1495 make bug triggered by sources containing repeated slashes when the
1496 `subdir-objects' option was used.
1498 - The makedepend and hp depmodes now work better with VPATH builds.
1500 - Java sources specified with check_JAVA are no longer compiled for
1501 "make all", but only for "make check".
1503 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
1504 and error out if `javadir' is undefined, instead of silently producing
1505 a broken Makefile.in.
1507 - aclocal and automake now honour the configure-time definitions of
1508 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
1510 - The `install-info' recipe no longer tries to guess whether the
1511 `install-info' program is from Debian or from GNU, and adaptively
1512 change its behaviour; this has proven to be frail and easy to
1515 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1517 Bugs fixed in 1.11.1:
1519 - Lots of minor bugfixes.
1521 * Bugs introduced by 1.11:
1523 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
1524 trailing white space in the test list (`TESTS = foo $(EMPTY)').
1526 * Long standing bugs:
1528 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
1529 even if the `--prefix' argument pointed outside of a system directory.
1530 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
1531 `get_python_lib' function if it points outside the configured prefix,
1532 unless the `--prefix' argument was either `/usr' or below `/System'.
1534 - The testsuite does not try to change the mode of `ltmain.sh' files from
1535 a Libtool installation (symlinked to test directories) any more.
1537 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
1538 tools are preferred in a cross-compile setup.
1540 - The distribution is tarred up with mode 755 now by the `dist*' targets.
1541 This fixes a race condition where untrusted users could modify files
1542 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
1543 build directory was world-searchable. This is CVE-2009-4029.
1545 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1549 * Version requirements:
1551 - Autoconf 2.62 or greater is required.
1553 * Changes to aclocal:
1555 - The autoconf version check implemented by aclocal in aclocal.m4
1556 (and new in Automake 1.10) is degraded to a warning. This helps
1557 in the common case where the Autoconf versions used are compatible.
1559 * Changes to automake:
1561 - The automake program can run multiple threads for creating most
1562 Makefile.in files concurrently, if at least Perl 5.7.2 is available
1563 with interpreter-based threads enabled. Set the environment variable
1564 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
1565 enable this experimental feature.
1567 * Changes to Libtool support:
1569 - Libtool generic flags are now passed to the install and uninstall
1572 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
1573 config.lt is removed correctly now.
1575 * Languages changes:
1577 - subdir-object mode works now with Fortran (F77, FC, preprocessed
1578 Fortran, and Ratfor).
1580 - For files with extension .f90, .f95, .f03, or .f08, the flag
1581 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
1583 - Files with extension .sx are also treated as preprocessed assembler.
1585 - The default source file extension (.c) can be overridden with
1586 AM_DEFAULT_SOURCE_EXT now.
1588 - Python 3.0 is supported now, Python releases prior to 2.0 are no
1591 - AM_PATH_PYTHON honors python's idea about the site directory.
1593 - There is initial support for the Vala programming language, when using
1594 Vala 0.7.0 or later.
1596 * Miscellaneous changes:
1598 - Automake development is done in a git repository on Savannah now, see
1600 https://git.sv.gnu.org/gitweb/?p=automake.git
1602 A read-only CVS mirror is provided at
1604 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
1605 checkout -d automake HEAD
1607 - "make dist" can now create xz-compressed tarballs,
1608 as well as (deprecated?) lzma-compressed tarballs.
1610 - `automake --add-missing' will by default install the GPLv3 file as
1611 COPYING if it is missing. It will also warn that the license file
1612 should be added to source control. Note that Automake will never
1613 overwrite an existing COPYING file, even when the `--force-missing'
1616 - The manual is now distributed under the terms of the GNU FDL 1.3.
1618 - Automake ships and installs man pages for automake and aclocal now.
1620 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1622 - install-sh supports -C, which does not update the installed file
1623 (and its time stamps) if the contents did not change.
1625 - The `gnupload' script has been revamped.
1627 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1629 - The targets `install' and `uninstall' are more efficient now, in that
1630 for example multiple files from one Automake variable such as
1631 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1632 invocation if they do not have to be renamed.
1634 Both install and uninstall may sometimes enter (`cd' into) the target
1635 installation directory now, when no build-local scripts are used.
1637 Both install and uninstall do not fail anymore but do nothing if an
1638 installation directory variable like `bindir' is set to the empty string.
1640 For built-in rules, `make install' now fails reliably if installation
1641 of a file failed. Conversely, `make uninstall' even succeeds when
1642 issued multiple times.
1644 These changes may need some adjustments from users: For example,
1645 some `install' programs refuse to install multiple copies of the
1646 same file in one invocation, so you may need to remove duplicate
1647 entries from file lists.
1649 Also, within one set of files, say, nobase_data_DATA, the order of
1650 installation may be changed, or even unstable among different hosts,
1651 due to the use of associative arrays in awk. The increased use of
1652 awk matches a similar move in Autoconf to provide for better scaling.
1654 Further, most undocumented per-rule install command variables such as
1655 binSCRIPT_INSTALL have been removed because they are not needed any
1656 more. Packages which use them should be using the appropriate one of
1657 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1658 counterpart, depending on the type of files and the need for automatic
1659 target directory creation.
1661 - The "deleted header file problem" for *.m4 files is avoided by
1662 stub rules. This allows `make' to trigger a rerun of `aclocal'
1663 also if some previously needed macro file has been removed.
1665 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1666 an otherwise up to date tree.
1668 - The `color-tests' option causes colored test result output on terminals.
1670 - The `parallel-tests' option enables a new test driver that allows for
1671 parallel test execution, inter-test dependencies, lazy test execution
1672 for unit-testing, re-testing only failed tests, and formatted result output
1673 as RST (reStructuredText) and HTML. Enabling this option may require some
1674 changes to your test suite setup; see the manual for details.
1676 - The `silent-rules' option enables Linux kernel-style silent build output.
1677 This option requires the widely supported but non-POSIX `make' feature
1678 of recursive variable expansion, so do not use it if your package needs
1679 to build with `make' implementations that do not support it.
1681 To enable less verbose build output, the developer has to use the Automake
1682 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1683 macro. The user may then set the default verbosity by passing the
1684 `--enable-silent-rules' option to `configure'. At `make' run time, this
1685 default may be overridden using `make V=0' for less verbose, and `make V=1'
1686 for backward-compatible verbose output.
1688 - New prefix `notrans_' for manpages which should not be transformed
1689 by --program-transform.
1691 - New macro AM_COND_IF for conditional evaluation and conditional
1694 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1695 remove the file in a non-VPATH build. Such setups work with Autoconf
1698 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1699 the default setting.
1701 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1702 useful especially for multi-line values.
1704 - Automake's early configure-time sanity check now diagnoses an
1705 unsafe absolute source directory name and makes configure fail.
1707 - The Automake macros and rules cope better with whitespace in the
1708 current directory name, as long as the relative path to `configure'
1709 does not contain whitespace. To this end, the values of `$(MISSING)'
1710 and `$(install_sh)' may contain suitable quoting, and their expansion
1711 might need `eval'uation if used outside of a makefile. These
1712 undocumented variables may be used in several documented macros such
1713 as $(AUTOCONF) or $(MAKEINFO).
1717 * Long-standing bugs:
1719 - Fix aix dependency tracking for libtool objects.
1721 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1722 unnecessary use of the `compile' script.
1724 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1725 correct `-rpath' argument is used now.
1727 - `config.status --file=Makefile depfiles' now also works with the
1728 extra quoting used internally by Autoconf 2.62 and newer
1729 (it used to work only without the `--file=' bit).
1731 - The `missing' script works better with versioned tool names.
1733 - Semantics for `missing help2man' have been revamped:
1735 Previously, if `help2man' was not present, `missing help2man' would have
1736 the following semantics: if some man page was out of date but present, then
1737 a warning would be printed, but the exit status was 0. If the man page was
1738 not present at all, then `missing' would create a replacement man page
1739 containing an error message, and exit with a status of 2. This does not play
1740 well with `make': the next run will see this particular man page as being up
1741 to date, and will only error out on the next generated man page, if any;
1742 repeat until all pages are done. This was not desirable.
1744 These are the new semantics: if some man page is not present, and help2man
1745 is not either, then `missing' will warn and generate the replacement page
1746 containing the error message, but exit successfully. However, `make dist'
1747 will ensure that no such bogus man pages are packaged into a tarball.
1749 - Targets provided by automake behave better with `make -n', in that they
1750 take care not to create files.
1752 - `config.status Makefile... depfiles' works fine again in the presence of
1753 disabled dependency tracking.
1755 - The default no-op recursive rules for these targets also work with BSD make
1756 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1758 - `make distcheck' works also when both a directory and some file below it
1759 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1761 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1762 `make mostlyclean' any more; only the LaTeX by-products are.
1764 - Renamed objects also work with the `subdir-objects' option and
1765 source file languages which Automake does not know itself.
1767 - `automake' now correctly complains about variable assignments which are
1768 preceded by a comment, extend over multiple lines with backslash-escaped
1769 newlines, and end in a comment sign. Previous versions would silently
1770 and wrongly ignore such assignments completely.
1772 * Bugs introduced by 1.10:
1774 - Fix output of dummy dependency files in presence of post-processed
1775 Makefile.in's again, but also cope with long lines.
1777 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1778 that have been declared as programs in the same Makefile.
1779 This is for consistency with the analogous change to TESTS in 1.10.
1781 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1782 followed by directories containing config headers.
1784 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1788 * Version requirements:
1790 - Autoconf 2.60 or greater is required.
1792 - Perl 5.6 or greater is required.
1794 * Changes to aclocal:
1796 - aclocal now also supports -Wmumble and -Wno-mumble options.
1798 - `dirlist' entries (for the aclocal search path) may use shell
1799 wildcards such as `*', `?', or `[...]'.
1801 - aclocal supports an --install option that will cause system-wide
1802 third-party macros to be installed in the local directory
1803 specified with the first -I flag. This option also uses #serial
1804 lines in M4 files to upgrade local macros.
1806 The new aclocal options --dry-run and --diff help to review changes
1807 before they are installed.
1809 - aclocal now outputs an autoconf version check in aclocal.m4 in
1810 projects using automake.
1812 For a few years, automake and aclocal have been calling autoconf
1813 (or its underlying engine autom4te) to accurately retrieve the
1814 data they need from configure.ac and its siblings. Doing so can
1815 only work if all autotools use the same version of autoconf. For
1816 instance a Makefile.in generated by automake for one version of
1817 autoconf may stop working if configure is regenerated with another
1818 version of autoconf, and vice versa.
1820 This new version check ensures that the whole build system has
1821 been generated using the same autoconf version.
1823 * Support for new Autoconf macros:
1825 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1827 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1828 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1829 in different directories. However, only one instance of such a
1830 library objects directory is supported.
1832 * Change to Libtool support:
1834 - Libtool generic flags (those that go before the --mode=MODE option)
1835 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1837 * Yacc and Lex changes:
1839 - The rebuild rules for distributed Yacc and Lex output will avoid
1840 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1843 - ylwrap is now always used for lex and yacc source files,
1844 regardless of whether there is more than one source per directory.
1846 * Languages changes:
1848 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1849 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1850 tracking, unlike non-preprocessed assembler (*.s).
1852 - subdir-object mode works now with Assembler. Automake assumes
1853 that the compiler understands `-c -o'.
1855 - Preprocessed assembler (*.S) compilation now also honors
1856 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1858 - Improved support for Objective C:
1859 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1860 - A new section of the manual documents the support.
1862 - New support for Unified Parallel C:
1863 - AM_PROG_UPC looks for a UPC compiler.
1864 - A new section of the manual documents the support.
1866 - Per-target flags are now correctly handled in link rules.
1868 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1869 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1870 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1871 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1873 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1874 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1875 is expected to work (and actually works during compilation).
1877 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1878 "in addition to" breaks backward compatibility with older versions.
1879 If your package used both variables, as in
1881 AM_LDFLAGS = common flags
1882 bin_PROGRAMS = a b c
1883 a_LDFLAGS = more flags
1886 and assumed *_LDFLAGS would sum up, you should rewrite it as
1888 AM_LDFLAGS = common flags
1889 bin_PROGRAMS = a b c
1890 a_LDFLAGS = $(AM_LDFLAGS) more flags
1893 This new behavior of *_LDFLAGS is more coherent with other
1894 per-target variables, and the way *_LDFLAGS variables were
1895 considered internally.
1897 * New installation targets:
1899 - New targets mandated by GNU Coding Standards:
1904 By default they will only install Texinfo manuals.
1905 You can customize them with *-local variants:
1911 - The undocumented recursive target `uninstall-info' no longer exists.
1912 (`uninstall' is in charge of removing all possible documentation
1913 flavors, including optional formats such as dvi, ps, or info even
1914 when `no-installinfo' is used.)
1916 * Miscellaneous changes:
1918 - Automake no longer complains if input files for AC_CONFIG_FILES
1919 are specified using shell variables.
1921 - clean, distribution, or rebuild rules are normally disabled for
1922 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1923 AC_CONFIG_LINK specified using shell variables. However, if these
1924 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1925 be able to output rules anyway.
1926 (See the Automake documentation for AC_CONFIG_FILES.)
1928 - $(EXEEXT) is automatically appended to filenames of TESTS
1929 that have been declared as programs in the same Makefile.
1930 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1932 - `-Wportability' has finally been turned on by default for `gnu' and
1933 `gnits' strictness. This means, automake will complain about %-rules
1934 or $(GNU Make functions) unless you switch to `foreign' strictness or
1935 use `-Wno-portability'.
1937 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1938 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1939 $(mkdir_p) variable is still defined (to the same value as
1940 $(MKDIR_P)) but should be considered obsolete. If you are using
1941 $(mkdir_p) in some of your rules, please plan to update them to
1942 $(MKDIR_P) at some point.
1944 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1945 They still work in this release, but may be withdrawn in a future one.
1947 - Inline compilation rules for gcc3-style dependency tracking are
1950 - Automake installs a "Hello World!" example package in $(docdir).
1951 This example is used throughout the new "Autotools Introduction"
1952 chapter of the manual.
1954 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1958 * Makefile.in bloat reduction:
1960 - Inference rules are used to compile sources in subdirectories when
1961 the `subdir-objects' option is used and no per-target flags are
1962 used. This should reduce the size of some projects a lot, because
1963 Automake used to output an explicit rule for each such object in
1966 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1967 object that must be built with explicit rules. It just outputs
1968 the rules required to build the kind of object considered: either
1969 the two .o and .obj rules for usual objects, or the .lo rule for
1972 * Change to Libtool support:
1974 - Libtool tags are used with libtool versions that support them.
1975 (I.e., with Libtool 1.5 or greater.)
1977 - Automake is now able to handle setups where a libtool library is
1978 conditionally installed in different directories, as in
1981 lib_LTLIBRARIES = liba.la
1983 pkglib_LTLIBRARIES = liba.la
1985 liba_la_SOURCES = ...
1987 * Changes to aclocal:
1989 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1990 really evaluated, before it decides to include them in aclocal.m4.
1991 This solves nasty problems with conditional redefinitions of
1992 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1993 *.m4 files to be included in any project using these macros.
1994 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1995 most famous instance of this bug.)
1997 - Do not complain about missing conditionally AC_REQUIREd macros
1998 that are not actually used. In 1.8.x aclocal would correctly
1999 determine which of these macros were really needed (and include
2000 only these in the package); unfortunately it would also require
2001 all of them to be present in order to run. This created
2002 situations were aclocal would not work on a tarball distributing
2003 all the macros it uses. For instance running aclocal on a project
2004 containing only the subset of the Gettext macros in use by the
2005 project did not work, because gettext conditionally requires other
2008 * Portability improvements:
2010 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
2011 tar-pax. The new option filename-length-max=99 helps diagnosing
2012 filenames that are too long for tar-v7. (PR/414)
2014 - Variables augmented with `+=' are now automatically flattened (i.e.,
2015 trailing backslashes removed) and then wrapped around 80 columns
2016 (adding trailing backslashes). In previous versions, a long series
2022 would result in a single-line definition of VAR that could possibly
2023 exceed the maximum line length of some make implementations.
2025 Non-augmented variables are still output as they are defined in
2030 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
2031 Works the same as the old Fortran 77 implementation; just replace
2032 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
2033 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
2035 - Support for conditional _LISP.
2037 - Support for conditional -hook and -local rules (PR/428).
2039 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
2041 - Automake will not write any Makefile.ins after the first error it
2042 encounters. The previous Makefile.ins (if any) will be left in
2043 place. (Warnings will not prevent output, but remember they can
2044 be turned into errors with -Werror.)
2046 - The restriction that SUBDIRS must contain direct children is gone.
2049 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
2050 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
2052 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2054 Bugs fixed in 1.8.5:
2056 * Long-standing bugs:
2058 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
2059 so that `make distclean' and `make maintainer-clean' can work.
2061 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
2063 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
2065 - Polish diagnostic when no input file is found.
2067 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2069 Bugs fixed in 1.8.4:
2071 * Long-standing bugs:
2073 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
2074 overridden by the user.
2076 - Honor PATH_SEPARATOR in various places of the Automake package, for
2079 - Adjust dependency tracking mode detection to ICC 8.0's new output.
2082 - Fix install-sh so it can install the `mv' binary... using `mv'.
2084 - Fix tru64 dependency tracking for libtool objects.
2086 - Work around Exuberant Ctags when creating a TAGS files in a directory
2087 without files to scan but with subdirectories to include.
2089 * Bugs introduced by 1.8:
2091 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
2092 not defined in the same conditions as the _LDADD that uses it.
2094 - Do not warn when JAVAROOT is overridden, this is legitimate.
2096 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2098 Bugs fixed in 1.8.3:
2100 * Long-standing bugs:
2102 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
2103 or any of the other *dir variables contain a space.
2105 Please note that Automake does not and cannot support spaces in
2106 filenames that are involved during the build. This change affects
2107 only installation paths, so that `make install' does not bomb out
2108 in packages configured with
2109 ./configure --prefix '/c/Program Files'
2111 - Fix the depfiles output so it works with GNU sed (<4.1) even when
2112 POSIXLY_CORRECT is set.
2114 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
2115 since Autoconf 2.54, which defines LIBOBJS itself.
2117 - Fix a potential (but unlikely) race condition in parallel elisp
2118 builds. (Introduced in 1.7.3.)
2120 - Do not assume that users override _DEPENDENCIES in all conditions
2121 where Automake will try to define them.
2123 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
2124 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
2127 This fix also affects the $(mkdir_p) variable defined since
2128 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
2129 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
2131 - Secure temporary directory creation in `make distcheck'. (PR/413)
2133 - Do not generate two build rules for `parser.h' when the
2134 parser appears in two different conditionals.
2136 - Work around a Solaris 8 /bin/sh bug in the test for dependency
2137 checking. Usually ./configure will not pick this shell; so this
2138 fix only helps cases where the shell is forced to /bin/sh.
2140 * Bugs introduced by 1.8:
2142 - In some situations (hand-written `m4_include's), aclocal would
2143 call the `File::Spec->rel2abs' method, which was only introduced
2144 in Perl 5.6. This new version reestablish support Perl 5.005.
2146 It is likely that the next major Automake releases will require at
2147 least Perl 5.6. Consider upgrading your development environment
2148 if you are still using the five-year-old Perl 5.005.
2150 - Automake would sometimes fail to define rules for targets listed
2151 in variables defined in multiple conditions. For instance on
2157 it would define only the `a.$(OBJEXT): a.c' rule and omit the
2158 `b.$(OBJEXT): b.c' rule.
2160 * New sections in manual:
2162 - Third-Party Makefiles: how to interface third party Makefiles.
2163 - Upgrading: upgrading packages to newer Automake versions.
2164 - Multiple Outputs: handling tools that produce many outputs.
2166 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2170 * A (well known) portability bug slipped in the changes made to
2171 install-sh in Automake 1.8.1. The broken install-sh would refuse to
2172 install anything on Tru64.
2174 * Fix install rules for conditionally built python files. (This never
2177 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2181 * Bugs introduced by 1.8:
2183 - Fix Config.pm import error with old Perl versions (at least
2184 5.005_03). One symptom is that aclocal could not find its macro
2187 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
2188 created by `make install' are always world readable, even if the
2189 installer happens to have an overly restrictive umask (e.g. 077).
2190 This was a mistake and has been reverted. There are at least two
2191 reasons why we must not use `-m 0755':
2192 - it causes special bits like SGID to be ignored,
2193 - it may be too restrictive (some setups expect 775 directories).
2195 - Fix aclocal to honor definitions located in files which have been
2196 m4_included manually. aclocal 1.8 had been updated to check
2197 m4_included files for new requirements, but forgot that these
2198 m4_included files can also provide new definitions.
2200 Note that if you have such a setup, we recommend you get rid of
2201 it. In the past, there was a reason to m4_include files manually:
2202 aclocal used to duplicate entire M4 files into aclocal.m4, even
2203 files that were distributed. Some packages were therefore
2204 m4_including the distributed file directly, and playing some
2205 tricks to ensure aclocal would not copy that file to aclocal.m4,
2206 in order to limit the amount of duplication. Since aclocal 1.8.x
2207 will precisely output m4_includes for local M4 files, we recommend
2208 that you clean up your setup, removing all manual m4_includes and
2209 letting aclocal output them.
2211 - Output detailed menus in the Info version if the Automake manual,
2212 so that Emacs can locate the indexes.
2214 - configure.ac and configure were listed twice in DIST_COMMON (an
2215 internal variable where Automake lists configury files to
2216 distribute). This was harmless, but unaesthetic.
2218 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
2219 This was an issue only in the Automake package itself, not in
2222 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
2223 DEST:SRC. This was wrong, as some packages do
2224 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
2227 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
2228 argument. This caused two kinds of failures:
2229 - Rules installing data in a conditionally defined directory
2230 failed when that directory was undefined. In this case no
2231 argument was supplied.
2232 - `make installdirs' failed, because several directories were
2233 passed to $(mkdir_p). This was an issue only on platform
2234 were $(mkdir_p) is implemented with `install-sh -d'.
2235 $(mkdir_p) as been changed to accept 0 or more arguments, as
2238 * Long-standing bugs:
2240 - Fix an unexpected diagnostic occurring when users attempt
2241 to override some internal variables that Automake appends to.
2243 - aclocal now scans configure.ac for macro definitions (PR/319).
2245 - Fix a portability issue with OSF1/Tru64 Make. If a directory
2246 distributes files which are outside itself (this usually occurs
2247 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
2248 from a parent package), then `make distcheck' fails due to an
2249 optimization performed by OSF1/Tru64 Make in its VPATH handling.
2250 (tests/subpkg2.test failure)
2252 - Fix another portability issue with Sun and OSF1/Tru64 Make.
2253 In a VPATH-build configuration, `make install' would install
2254 nobase_ files to wrong locations.
2256 - Fix a Perl `uninitialized value' diagnostic occurring when
2257 automake complains that a Texinfo file does not have a
2258 @setfilename statement.
2260 - Erase config.status.lineno during `make distclean'. This file
2261 can be created by config.status. Automake already knew about
2262 configure.lineno, but forgot config.status.lineno.
2264 - Distribute all files, even those which are built and installed
2265 conditionally. This change affects files listed in conditionally
2266 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
2267 as well as those listed in conditionally defined dist_*_DATA,
2268 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
2270 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
2271 doesn't conform to POSIX.
2273 - Normalize help strings for configure variables and options added
2278 - Check for python2.4 in AM_PATH_PYTHON.
2280 * Spurious failures in test suite:
2282 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
2283 tests/ltconv.test: fix failures with CVS Libtool.
2284 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
2285 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
2286 fix failures with old Texinfo versions.
2288 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2294 - The NEWS file is more verbose.
2298 - Autoconf 2.58 or greater is required.
2302 - Default source file names in the absence of a _SOURCES declaration
2303 are made by removing any target extension before appending `.c', so
2304 to make the libtool module `foo.la' from `foo.c', you only need to
2307 lib_LTLIBRARIES = foo.la
2308 foo_la_LDFLAGS = -module
2310 For backward compatibility, foo_la.c will be used instead of
2311 foo.c if this file exists or is the explicit target of a rule.
2312 However -Wobsolete will warn about this deprecated naming.
2314 - AR's `cru' flags are now set in a global ARFLAGS variable instead
2315 of being hard-coded in each $(AR) invocation, so they can be
2316 substituted from configure.ac. This has been requested by people
2317 dealing with non-POSIX ar implementations.
2319 - New warning option: -Woverride. This will warn about any user
2320 target or variable definitions which override Automake
2323 - Texinfo rules back up and restore info files when makeinfo fails.
2325 - Texinfo rules now support the `html' target.
2326 Running this requires Texinfo 4.0 or greater.
2328 `html' is a new recursive target, so if your package mixes
2329 hand-crafted `Makefile.in's with Automake-generated
2330 `Makefile.in's, you should adjust the former to support (or
2331 ignore) this target so that `make html' recurses successfully. If
2332 you had a custom `html' rule in your `Makefile.am', it's better to
2333 rename it as `html-local', otherwise your rule will override
2334 Automake's new rule (you can check that by running `automake
2335 -Woverride') and that will stop the recursion to subdirectories.
2337 Last but not least, this `html' rule is declared PHONY, even when
2338 overridden. Fortunately, it appears that few packages use a
2339 non-PHONY `html' rule.
2341 - Any file which is m4_included from configure.ac will appear as a
2342 configure and Makefile.in dependency, and will be automatically
2345 - The rules for rebuilding Makefiles and Makefile.ins will now
2346 rebuild all Makefiles and all Makefile.ins at once when one of
2347 configure's dependencies has changed. This is considerably faster
2348 than previous implementations, where config.status and automake
2349 were run separately in each directory (this still happens when you
2350 change a Makefile.am locally, without touching configure.ac or
2351 friends). Doing this also solves a longstanding issue: these
2352 rebuild rules failed to work when adding new directories to the
2353 tree, forcing you to run automake manually.
2355 - For similar reasons, the rules to rebuild configure,
2356 config.status, and aclocal.m4 are now defined in all directories.
2357 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
2358 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
2359 should better define them in all directories. This is easily done
2360 using an AC_SUBST (make sure you prefix these dependencies with
2361 $(top_srcdir) since this variable will appear at different
2362 levels of the build tree).
2364 - aclocal will now use `m4_include' instead of copying local m4
2365 files into aclocal.m4. (Local m4 files are those you ship with
2366 your project, other files will be copied as usual.)
2368 Because m4_included files are automatically distributed, it means
2369 for most projects there is no point in EXTRA_DISTing the list of
2370 m4 files which are used. (You can probably get rid of
2371 m4/Makefile.am if you had one.)
2373 - aclocal will avoid touching aclocal.m4 when possible, so that
2374 Autom4te's cache isn't needlessly invalidated. This behavior can
2375 be switched off with the new `--force' option.
2377 - aclocal now uses Autoconf's --trace to detect macros which are
2378 actually used and will no longer include unused macros simply
2379 because they where mentioned. This was often the case for macros
2380 called conditionally.
2382 - New options no-dist and no-dist-gzip.
2384 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
2385 py-compile, and ylwrap, now all understand --version and --help.
2387 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
2388 links as part of the distclean target and including source files in
2391 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
2392 argument. The latter can be used to override the default behavior
2393 (which is to abort).
2395 - Automake will exit with $? = 63 on version mismatch. (So does
2396 Autoconf 2.58) missing knows this, and in this case it will
2397 emulate the tools as if they were absent. Because older versions
2398 of Automake and Autoconf did not use this exit code, this change
2399 will only be useful in projects generated with future versions of
2402 - When using AC_CONFIG_FILES with multiple input files, Automake
2403 generates the first ".in" input file for which a ".am" exists.
2404 (Former versions would try to use only the first input file.)
2406 - lisp_DATA is now allowed. If you are using the empty ELCFILES
2407 idiom to disable byte-compilation of lisp_LISP files, it is
2408 recommended that you switch to using lisp_DATA. Note that
2409 this is not strictly equivalent: lisp_DATA will install elisp
2410 files even if emacs is not installed, while *_LISP do not
2411 install anything unless emacs is found.
2413 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
2414 available. This selection is achieved through the Makefile
2415 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
2416 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
2417 `$(install_sh) -m 0755 -d'.
2421 - Because `mkdir -p' is available on most platforms, and we can use
2422 `install-sh -d' when it is not, the use of the mkinstalldirs
2423 script is being phased out. `automake --add-missing' no longer
2424 installs it, and if you remove mkinstalldirs from your package,
2425 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
2427 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
2428 gettextize and autopoint will install it when needed. Automake
2429 will continue to define the $(mkinstalldirs) and to distribute
2430 mkinstalldirs when this script is in the source tree.
2432 - AM_PROG_CC_STDC is now empty. The content of this macro was
2433 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
2434 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
2435 renaming should be safe, even if you have to support several,
2436 versions of Automake, because AC_PROG_CC defines this variable
2437 since Autoconf 2.54.)
2439 - Some users where using the undocumented ACLOCAL_M4_SOURCES
2440 variable to override the aclocal.m4 dependencies computed
2441 (inaccurately) by older versions of Automake. Because Automake
2442 now tracks configure's m4 dependencies accurately (see m4_include
2443 above), the use of ACLOCAL_M4_SOURCES should be considered
2444 obsolete and will be flagged as such when running `automake
2449 - Defining programs conditionally using Automake conditionals no
2450 longer leads to a combinatorial explosion. The following
2451 construct used to be troublesome when used with dozens of
2466 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
2468 - Due to implementation constraints, previous versions of Automake
2469 proscribed multiple conditional definitions of some variables
2479 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
2480 This restriction has been lifted, and these variables now
2481 support multiple conditional definitions as do other variables.
2483 - Cleanup the definitions of $(distdir) and $(top_distdir).
2484 $(top_distdir) now points to the root of the distribution
2485 directory created during `make dist', as it did in Automake 1.4,
2486 not to the root of the build tree as it did in intervening
2487 versions. Furthermore these two variables are now only defined in
2488 the top level Makefile, and passed to sub-directories when running
2491 - The --no-force option now correctly checks the Makefile.in's
2492 dependencies before deciding not to update it.
2494 - Do not assume that make files are called Makefile in cleaning rules.
2496 - Update .info files in the source tree, not in the build tree. This
2497 is what the GNU Coding Standard recommend. Only Automake 1.7.x
2498 used to update these files in the build tree (previous versions did
2499 it in the source tree too), and it caused several problems, varying
2500 from mere annoyance to portability issues.
2502 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
2503 when --add-missing and --force-missing are used. For backward
2504 compatibility --add-missing will continue to install COPYING (in
2505 `gnu' strictness) when none of these three files exist, but this
2506 use is deprecated: you should better choose a license yourself and
2507 install it once for all in your source tree (and in your code
2510 - Fix ylwrap so that it does not overwrite header files that haven't
2511 changed, as the inline rule already does.
2513 - User-defined rules override automake-defined rules for the same
2514 targets, even when rules do not have commands. This is not new
2515 (and was documented), however some of the automake-generated
2516 rules have escaped this principle in former Automake versions.
2517 Rules for the following targets are affected by this fix:
2519 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
2520 info, info-am, install-data-am, install-exec-am, install-info,
2521 install-info-am, install-man, installcheck-am, maintainer-clean,
2522 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
2523 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
2525 Practically it means that an attempt to supplement the dependencies
2526 of some target, as in
2528 clean: my-clean-rule
2530 will now *silently override* the automake definition of the
2531 rule for this target. Running `automake -Woverride' will diagnose
2532 all such overriding definitions.
2534 It should be noted that almost all of these targets support a *-local
2535 variant that is meant to supplement the automake-defined rule
2536 (See node `Extending' in the manual). The above rule should
2539 clean-local: my-clean-rule
2541 These *-local targets have been documented since at least
2542 Automake 1.2, so you should not fear the change if you have
2543 to support multiple automake versions.
2547 - The Automake manual is now distributed under the terms of the GNU FDL.
2549 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
2551 - core dumps are no longer removed by the cleaning rules. There are
2552 at least three reasons for this:
2553 1. These files should not be created by any build step,
2554 so their removal do not fit any of the cleaning rules.
2555 Actually, they may be precious to the developer.
2556 2. If such file is created during a build, then it's clearly a
2557 bug Automake should not hide. Not removing the file will
2558 cause `make distcheck' to complain about its presence.
2559 3. Operating systems have different naming conventions for
2560 core dump files. A core file on one system might be a
2561 completely legitimate data file on another system.
2563 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
2564 defined by Automake. This means that any definition in the
2565 environment will be used, unless overridden in the Makefile.am or
2566 on the command line. The old behavior, where these variables were
2567 defined empty in each Makefile, can be obtained by AC_SUBSTing or
2568 AC_ARG_VARing each variable from configure.ac.
2570 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
2571 documented. (The is not a new feature, these variables have
2572 been there since at least Automake 1.4.)
2574 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2576 Bugs fixed in 1.7.9:
2577 * Fix install-strip to work with nobase_ binaries.
2578 * Fix renaming of #line directives in ylwrap.
2579 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
2581 Bugs fixed in 1.7.8:
2582 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
2583 * Fix detection of Debian's install-info, broken since version 1.5.
2584 (Debian bug #213524).
2585 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
2586 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
2588 Bugs fixed in 1.7.7:
2589 * The implementation of automake's --no-force option is unreliable,
2590 so this option is ignored in this version. A real fix will appear in
2591 Automake 1.8. (Debian Bug #206299)
2592 * AM_PATH_PYTHON: really check the whole list of interpreters if no
2593 argument is given. (PR/399)
2594 * Do not warn about leading `_' in variable names, even with -Wportability.
2595 * Support user redefinitions of TEXINFO_TEX.
2596 * depcomp: support AIX Compiler version 6.
2597 * Fix missing rebuilds during `make dist' with BSD make.
2598 (Could produce tarballs containing out-of-date files.)
2599 * Resurrect multilib support.
2600 * Noteworthy manual updates:
2601 - Extending aclocal: how to write m4 macros that won't trigger warnings
2603 - A Shared Library: Rewrite and split into subsections.
2605 Bugs fixed in 1.7.6:
2606 * Fix depcomp's icc mode for ICC 7.1.
2607 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
2608 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
2609 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
2610 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
2611 * Remove Latin-1 characters from elisp-comp.
2612 * Update the manual's @dircategory to match the Free Software Directory.
2614 Bugs fixed in 1.7.5:
2615 * Update install-sh's license to remove an advertising clause.
2616 (Debian bug #191717)
2617 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2618 that caused invalid Makefile.ins to be generated.
2619 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2620 * New FAQ entry: renamed objects.
2622 Bugs fixed in 1.7.4:
2623 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2624 the Emacs implementation)
2625 * Fix output of aclocal.m4 dependencies in subdirectories.
2626 * Use `mv -f' instead of `mv' in fastdep rules.
2627 * Upgrade mdate-sh to work on OS/2.
2628 * Don't byte-compile elisp files when ELCFILES is set empty.
2629 (this documented feature was broken by 1.7.3)
2630 * Diagnose trailing backslashes on last line of Makefile.am.
2631 * Diagnose whitespace following trailing backslashes.
2632 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2633 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2635 * `make install' will build `BUILT_SOURCES' first.
2636 * Minor documentation fixes.
2638 Bugs fixed in 1.7.3:
2639 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2640 * Query distutils for `pythondir' and `pythonexecdir', instead of
2641 using an hardcoded path. This should allow builds on 64-bit
2642 distributions that usually use lib64/ instead of lib/.
2643 * AM_PATH_PYTHON will also search for python2.3.
2644 * elisp files are now built all at once instead of one by one. Besides
2645 incurring a speed-up, this is required to support interdependent elisp files.
2646 * Support for DJGPP:
2647 - `make distcheck' will now work in `_inst/' and `_build' instead
2648 of `=inst/' and `=build/'
2649 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2650 - install/uninstall `*.i[0-9][0-9]'-style info files
2651 - more changes that affect only the Automake package (not its output)
2652 * Fix some incompatibilities with upcoming perl-5.10.
2653 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2654 PACKAGE and VERSION.
2656 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2657 is troublesome with gcc and Solaris compilers. (PR/385)
2658 - makedepend mode: work with Libtool. (PR/385 too)
2660 * better support for unusual gettext setups, such as multiple po/ directories
2662 - Flag missing po/ and intl/ directories as warnings, not errors.
2663 - Disable these warnings if po/ does not exist.
2664 * Noteworthy manual updates:
2666 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2668 - Document `AM_YFLAGS = -d'. (PR/382)
2670 Bugs fixed in 1.7.2:
2671 * Fix installation and uninstallation of Info files built in subdirectories.
2672 * Do not run `./configure --with-included-gettext' during `make distcheck'
2673 if AM_GNU_GETTEXT([external]) is used.
2674 * Correctly uninstall renamed man pages.
2675 * Do not strip escaped newline in variables defined in one condition
2676 and augmented in another condition.
2677 * Fix ansi2knr rules for LIBOBJS sources.
2678 * Clean all known Texinfo index files, not only those which appear to
2679 be used, because we cannot know which indexes are used in included files.
2680 (PR/375, Debian Bug #168671)
2681 * Honor only the first @setfilename seen in a Texinfo file.
2682 * Treat "required file X not found" diagnostics as errors (exit status 1).
2683 * Don't complain that a required file is not found when it is a Makefile
2685 * Don't use single suffix inference rules when building `.info'-less
2686 Info files, for the sake of Solaris make.
2687 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2688 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2689 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2690 * Fix building of deansified files from subdirectories. (PR/370)
2691 * Add missing `fi' in the .c->.obj rules.
2692 * Improve install-sh to work even when names contain spaces or certain
2693 (but not all) shell metachars.
2694 * Fix the following spurious failures in the test suite:
2695 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2696 * Noteworthy manual updates:
2697 - Augment the section about BUILT_SOURCES.
2698 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2700 Bugs fixed in 1.7.1:
2701 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2703 * Aclocal should now recognize macro names containing parentheses, e.g.
2704 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2705 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2707 * Install Python files even if they were built. (PR/369)
2708 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2709 version might not be defined in the latter. (PR/358)
2710 * Reorder arguments passed to a couple of commands, so things works
2711 when POSIXLY_CORRECT=1.
2712 * Fix a regex that can cause Perl to segfault on large input.
2714 * Fix distribution of packages that have some sources defined conditionally,
2715 as in the `Conditional compilation using Automake conditionals' example
2717 * Fix spurious test suite failures on IRIX.
2718 * Don't report a required variable as undefined if it has been
2719 defined conditionally for the "right" conditions.
2720 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2721 `make distcheck' fails.
2722 * Fix distribution of included Makefile fragment, so we don't create
2723 spurious directories in the distribution. (PR/366)
2724 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2727 * Autoconf 2.54 is required.
2728 * `aclocal' and `automake' will no longer warn about obsolete
2729 configure macros. This is done by `autoconf -Wobsolete'.
2730 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2731 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2732 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2733 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2734 `configure.ac' for you.
2735 * Support for per-program and per-library `_CPPFLAGS'.
2736 * New `ctags' target (builds CTAGS files).
2737 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2738 (see `automake --help' or the manual for a list of them).
2739 * Honor the WARNINGS environment variable.
2740 * Omit the call to depcomp when using gcc3: call the compiler directly.
2741 * A new option, std-options, tests that programs support --help and --version
2742 when `make installcheck' is run. This is enabled by --gnits.
2743 * Texinfo rules now support the `ps' and `pdf' targets.
2744 * Info files are now created in the build directory, not the source directory.
2745 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2747 * `make distcheck' will enforce DESTDIR support by attempting
2749 * `+=' can be used in conditionals, even if the augmented variable
2750 was defined for another condition.
2751 * Makefile fragments (inserted with `include') are always distributed.
2752 * Use Autoconf's --trace interface to inspect configure.ac and get
2753 a more accurate view of it.
2754 * Add support for extending aclocal's default macro search path
2755 using a `dirlist' file within the aclocal directory.
2756 * automake --output-dir is deprecated.
2757 * The part of the distcheck target that checks whether uninstall actually
2758 removes all installed files has been moved in a separate target,
2759 distuninstallcheck, so it can be overridden easily.
2763 * Support for AM_INIT_GETTEXT([external])
2764 * Bug fixes, including:
2765 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2766 - nobase_ programs and scripts honor --program-transform correctly.
2767 - Erase configure.lineno during `make distclean'.
2768 - Erase YACC and LEX outputs during `make maintainer-clean'.
2771 * Many bug fixes, including:
2772 - Requiring the current version works.
2773 - Fix "$@" portability issues (for Zsh).
2774 - Fix output of dummy dependency files in presence of post-processed
2776 - Don't compute dependencies in background to avoid races with libtool.
2777 - Fix handling of _OBJECTS variables for targets sharing source variables.
2778 - Check dependency mode for Java when AM_PROG_GCJ is used.
2781 * automake --output-dir is deprecated
2782 * Many bug fixes, including:
2783 - Don't choke on AM_LDFLAGS definitions.
2784 - Clean libtool objects from subdirectories.
2785 - Allow configure variables with reserved suffix and unknown prefix
2786 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2787 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2790 * Autoconf 2.52 is required.
2791 * automake no longer run libtoolize.
2792 This is the job of autoreconf (from GNU Autoconf).
2793 * `dist' generates all the archive flavors, as did `dist-all'.
2794 * `dist-gzip' generates the Gzip tar file only.
2795 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2796 explosion. Makefile.in's keep a reasonable size.
2797 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2798 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2800 * `#line' of Lex and Yacc files are properly set.
2801 * EXTRA_DIST can contain generated directories.
2802 * Support for dot-less extensions in suffix rules.
2803 * The part of the distcheck target that checks whether distclean actually
2804 cleans all built files has been moved in a separate target, distcleancheck,
2805 so it can be overridden easily.
2806 * `make distcheck' will pass additional options defined in
2807 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2808 * Fixed CDPATH portability problems, in particular for MacOS X.
2809 * Fixed handling of nobase_ targets.
2810 * Fixed support of implicit rules leading to .lo objects.
2811 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2812 * Added uninstall-hook target
2813 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2814 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2815 (Note that "pkgname" is not "tarname", see the manual for details.)
2816 It is also possible to pass a list of global Automake options as
2817 first argument to this new form of AM_INIT_AUTOMAKE.
2818 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2819 to be a real assembler.
2820 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2821 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2822 * aclocal and automake are also installed with the version number
2823 appended, and some of the install directory names have changed.
2824 This lets you have multiple versions installed simultaneously.
2825 * Support for parsers and lexers in subdirectories.
2828 * Support for `configure.ac'.
2829 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2830 * `make dist-all' is much faster.
2831 * Allows '@' AC_SUBSTs in macro names.
2832 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2833 * User-side dependency tracking. Developers no longer need GNU make
2835 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2836 * Most files are correctly handled if they appear in subdirs
2837 For instance, a _DATA file can appear in a subdir
2838 * GNU tar is no longer required for `make dist'
2839 * Added support for `dist_' and `nodist_' prefixes
2840 * Added support for `nobase_' prefix
2841 * Compiled Java support
2842 * Support for per-executable and per-library compilation flags
2846 * Added support for the Fortran 77 programming language.
2847 * Re-indexed the Automake Texinfo manual.
2848 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2849 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2850 * Support for latest autoconf, including support for objext
2851 * Can now put `.' in SUBDIRS to control build order
2852 * `include' command and `+=' support for macro assignment
2853 * Dependency tracking no long susceptible to deleted header file problem
2854 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2859 * Better Cygwin32 support
2860 * Support for suffix rules with _SOURCES variables
2861 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2862 * @LEXLIB@ no longer required when lex source seen
2863 Lex support in `missing', and new lex macro. Update your missing script.
2864 * Built-in support for assembly
2865 * aclocal gives error if `AM_' macro not found
2866 * Passed YFLAGS, not YACCFLAGS, to yacc
2867 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2868 * Dependencies computed as a side effect of compilation
2869 * Preliminary support for Java
2870 * DESTDIR support at "make install" time
2871 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2875 * Better DejaGnu support
2876 * Added no-installinfo option
2877 * Added Emacs Lisp support
2878 * Added --no-force option
2879 * Included `aclocal' program
2880 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2881 * Now uses `AM_' macro names everywhere
2882 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2883 ansi2knr now works correctly on K&R sources
2884 * Better C++, yacc, lex support
2885 * Will compute _DEPENDENCIES variables automatically if not supplied
2886 * Will interpolate $(...) and ${...} when examining contents of a variable
2887 * .deps files now in build directory, not source directory; dependency
2888 handling generally rewritten
2889 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2890 * can now put config.h into a subdir
2891 * Added dist-all target
2892 * Support for install-info program (see texinfo 3.9)
2893 * Support for "yacc -d"
2894 * configure substitutions are automatically discovered and included
2895 in generated Makefile.in
2896 * Special --cygnus mode
2897 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2898 when making distribution. Some dependencies are auto-ignored.
2899 * Changed how libraries are specified in _LIBRARIES variable
2900 * Full libtool support, from Gord Matzigkeit
2901 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2902 AM_CONFIG_HEADER handles it automatically
2903 * Texinfo output files no longer need .info extension
2904 * Added `missing' support
2906 * Conditionals in Makefile.am, from Ian Taylor
2910 * distcheck target runs install and installcheck targets
2911 * Added preliminary support for DejaGnu.
2916 * More libtool fixes from Gord Matzigkeit; libtool support is still
2918 * Added support for jm_MAINTAINER_MODE
2920 * New "distcheck" target
2924 * mkinstalldirs and mdate-sh now appear in directory specified by
2926 * Removed DIST_SUBDIRS, DIST_OTHER
2927 * AC_ARG_PROGRAM only required when an actual program exists
2928 * dist-hook target now run before distribution packaged up; idea from
2929 Dieter Baron. Other hooks exist, too.
2930 * Preliminary (unfinished) support for libtool
2931 * Added short option names.
2932 * Better "dist" support when gluing together multiple packages
2936 * Documentation updates (many from François Pinard)
2937 * strictness `normal' now renamed to `foreign'
2938 * Renamed --install-missing to --add-missing
2939 * Now handles AC_CONFIG_AUX_DIR
2940 * Now handles TESTS macro
2941 * DIST_OTHER renamed to EXTRA_DIST
2942 * DIST_SUBDIRS is deprecated
2943 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2944 * Better error messages in many cases
2945 * Program names are canonicalized
2946 * Added "check" prefix; from Gord Matzigkeit
2950 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2951 * Beginnings of a test suite
2952 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2953 * Doesn't print anything when running
2954 * Beginnings of MAINT_CHARSET support
2955 * Can specify version in AUTOMAKE_OPTIONS
2956 * Most errors recognizable by Emacs' M-x next-error
2957 * Added --verbose option
2958 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2959 configure-generated names
2960 * Required macros now distributed in aclocal.m4
2962 * --strictness=gnu is default
2966 * More sophisticated configure.in scanning; now understands ALLOCA and
2967 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2968 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2969 * CONFIG_HEADER variable now obsolete
2970 * Can handle multiple Texinfo sources
2971 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2972 * HEADERS variable no longer needed; now can put .h files directly into
2973 foo_SOURCES variable.
2974 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2975 corresponding ".in" files are included in the distribution.
2978 * Added --gnu and --gnits options
2979 * More standards checking
2981 * Cleaned up 'dist' targets
2982 * Added AUTOMAKE_OPTIONS variable and several options
2983 * Now scans configure.in to get some information (preliminary)
2986 * Works with Perl 4 again
2989 * Added --install-missing option.
2990 * Pretty-prints generated macros and rules
2991 * Comments in Makefile.am are placed more intelligently in Makefile.in
2992 * Generates .PHONY target
2993 * Rule or macro in Makefile.am now overrides contents of Automake file
2994 * Substantial cleanups from François Pinard
2998 * Works with Perl 4 again.
3001 * New uniform naming scheme.
3002 * --strictness option
3004 * '.c' files corresponding to '.y' or '.l' files are automatically
3006 * Many bug fixes and cleanups
3009 * Allow objects to be conditionally included in libraries via lib_LIBADD.
3012 * Bug fixes in 'clean' code.
3013 * Now generates 'installdirs' target.
3014 * man page installation reworked.
3015 * 'make dist' no longer re-creates all Makefile.in's.
3018 * Reimplemented in Perl
3019 * Added --amdir option (for debugging)
3020 * Texinfo support cleaned up.
3021 * Automatic de-ANSI-fication cleaned up.
3022 * Cleaned up 'clean' targets.
3025 * Automatic dependency tracking
3026 * More documentation
3027 * New variables DATA and PACKAGEDATA
3028 * SCRIPTS installed using $(INSTALL_SCRIPT)
3029 * No longer uses double-colon rules
3031 * Changes in advance of internationalization
3035 Copyright (C) 1995-2018 Free Software Foundation, Inc.
3037 This program is free software; you can redistribute it and/or modify
3038 it under the terms of the GNU General Public License as published by
3039 the Free Software Foundation; either version 2, or (at your option)
3042 This program is distributed in the hope that it will be useful,
3043 but WITHOUT ANY WARRANTY; without even the implied warranty of
3044 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
3045 GNU General Public License for more details.
3047 You should have received a copy of the GNU General Public License
3048 along with this program. If not, see <https://www.gnu.org/licenses/>.