GNU Automake Changelog
What's new in GNU Automake 1.14
Jun 22, 2013- It introduces a new feature aimed at making the implementation of non-recursive build systems more convenient and manageable (thanks to the new support for the '%reldir%' and '�non_reldir%' automake-time substitutions).
- It improves the handling of C compiles not supporting the conjunct use of the '-c' and '-o' options (unfortunately, this improvement comes with a couple of minor backward-incompatibilities). Among the other things, this means that you no longer need to explicitly call the AM_PROG_CC_C_O macro yourself in configure.ac (pre-existing invocation of this macro are of course still accepted and correctly working, for the sake of backward-compatibility).
- The 1.14 release also introduces new (non-fatal) runtime warnings to simplify the transition to Automake 2.0. You are free to ignore such warnings for now, but should address them before the transition to Automake 2.0 (whose ETA is about one year from now, maybe more, so no need to hurry yet).
New in GNU Automake 1.13.4 (Jun 15, 2013)
- This is a bug-fixing release, that remedies to a minor (and almost certainly basically harmless) regression introduced in the previous 1.13.3 micro release: When two or more user-defined suffix rules are present in a single Makefile.am, automake 1.13.3 would needlessly include definition of some make variables related to C compilation in the generated Makefile.in (this is bug#14560, reported by Ralf Corsepius). This is fixed in automake 1.13.4. Apart from few minor testsuite enhancements, the fix for the bug reported above is only relevant change between Automake 1.13.3 and Automake 1.13.4, so we omit the usual detailed excerpt from NEWS.
New in GNU Automake 1.13.1 (Jan 1, 2013)
- This is a bug-fixing release, partly remedying to the too-abrupt removal on our part of some long-obsoleted macros which were however still used "in the wild": AM_CONFIG_HEADER and (to a much lesser degree) AM_PROG_CC_STDC. Now the use of these obsolete macros elicit clear and helpful error messages, rather than obscure failures that give no hint about to the reason behind them.