- According to this new scheme, the next major version of Automake
(the one that had previously been labelled as "1.14") will actually
- become "Automake 2.0". Automake 1.14 is *this* release (which is
- a minor one). It introduces new features, deprecations and bug
- fixes, but no serious backward incompatibility. A partial exception
- is given by the behavioural changes in the AM_PROG_CC_C_O macro
- (described in details below) but such changes can also be seen as a
- fix for the old suboptimal and somewhat confusing behaviour.
+ become "Automake 2.0". Automake 1.14 has already been released as
+ the last minor release, and the present one is a bug-fixing release
+ following up on that one.
- See discussion about automake bug#13578 for more details and
background: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+New in 1.14.1:
+
+* Bugs fixed:
+
+ - The user is no longer allowed to override the --srcdir nor the --prefix
+ configure options used by "make distcheck" (bug#14991).
+
+ - Fixed a gross inefficiency in the recipes for installing byte-compiled
+ python files, that was causing an O(N^2) performance on the number N of
+ files, instead of the expected O(N) performance. Note that this bug
+ was only relevant when the number of python files was high (which is
+ unusual in practice).
+
+ - Automake try to offer a more reproducible output for warning messages,
+ in the face of the newly-introduced randomization for hash keys order
+ in Perl 5.18.
+
+ - The 'test-driver' script now actually error out with a clear error
+ message on the most common invalid usages.
+
+ - Several spurious failures/hangs in the testsuite (bugs #14706, #14707,
+ #14760, #14911, #15181, #15237).
+
+* Documentation fixes:
+
+ - Fixed typos in the 'fix-timestamp.sh' example script that made it
+ nonsensical.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
New in 1.14:
* C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
macro behind the scenes.
2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
- and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name
- in only dynamically computed *at configure runtime* from the
- content of the '$CC' variable.
+ and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
+ dynamically computed only at configure runtime (really!) from
+ the content of the '$CC' variable.
3. It no longer automatically AC_DEFINE the C preprocessor
symbol 'NO_MINUS_C_MINUS_O'.