"Fossies" - the Fresh Open Source Software Archive

Member "automake-1.16.3/NEWS" (19 Nov 2020, 131068 Bytes) of package /linux/misc/automake-1.16.3.tar.xz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "NEWS": 1.16.2_vs_1.16.3.

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