X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=NEWS;h=546d78ccde21d3ba0c1fae8790e886a17d768c7f;hb=b4eefc79759fcb2c5941a65759d242488af8ed1a;hp=4e8683353d7e32e3218ac9e96834b717e7148fbb;hpb=d114599bd66589794c6b78130bbc0db4ac91c334;p=platform%2Fupstream%2Fautomake.git diff --git a/NEWS b/NEWS index 4e86833..546d78c 100644 --- a/NEWS +++ b/NEWS @@ -1,23 +1,264 @@ +* WARNING: New versioning scheme for Automake. + + - Starting with this version onward, Automake will use an update and + more rational versioning scheme, one that will allow users to know + which kind of changes can be expected from a new version, based on + its version number. + + + Micro versions (e.g., 1.13.3, 2.0.1, 3.2.8) will introduce only + documentation updates and bug and regression fixes; they will + not introduce new features, nor any backward-incompatibility (any + such incompatibility would be considered a bug, to be fixed with + a further micro release). + + + Minor versions (e.g., 1.14, 2.1) can introduce new backward + compatible features; the only backward-incompatibilities allowed + in such a release are new *non-fatal* deprecations and warnings, + and possibly fixes for old or non-trivial bugs (or even inefficient + behaviours) that could unfortunately have been seen, and used, by + some developers as "corner case features". Possible disruptions + caused by this kind of fixes should hopefully be quite rare. + + + Major versions (now expected to be released every 18 or 24 months, + and not more often) can introduce new big features (possibly with + rough edges and not-fully-stabilized APIs), removal of deprecated + features, backward-incompatible changes of behaviour, and possibly + major refactorings (that, while ideally transparent to the user, + could introduce new bugs). Incompatibilities should however not + be introduced gratuitously and abruptly; a proper deprecation path + should be duly implemented in the preceding minor releases. + + - According to this new scheme, the next major version of Automake + (the one that has until now been labelled as '1.14') will actually + become "Automake 2.0". Automake 1.14 will be the next minor version, + which will introduce new features, deprecations and bug fixes, but + no real backward incompatibility. + + - See discussion about automake bug#13578 for more details and + background: + +* WARNING: Future backward-incompatibilities! + + - Makefile recipes generated by Automake 2.0 will expect to use an + 'rm' program that doesn't complain when called without any non-option + argument if the '-f' option is given (so that commands like "rm -f" + and "rm -rf" will act as a no-op, instead of raising usage errors). + Accordingly, AM_INIT_AUTOMAKE will expand new shell code checking + that the default 'rm' program in PATH satisfies this requirement, and + aborting the configure process if this is not the case. This behavior + of 'rm' is very widespread in the wild, and it will be required in the + next POSIX version: + + + - Automake 2.0 will require Autoconf 2.70 or later (which is still + unreleased at the moment of writing, but is planned to be released + before Automake 2.0 is). + + - Automake 2.0 will drop support for the long-deprecated 'configure.in' + name for the Autoconf input file. You are advised to start using the + recommended name 'configure.ac' instead, ASAP. + + - The ACLOCAL_AMFLAGS special make variable will be fully deprecated + in Automake 2.0 (where it will raise warnings in the "obsolete" + category). You are advised to start relying on the new Automake + support for AC_CONFIG_MACRO_DIRS instead (which was introduced in + Automake 1.13). + + - Automake 2.0 will remove support for automatic dependency tracking + with the SGI C/C++ compilers on IRIX. The SGI depmode has been + reported broken "in the wild" already, and we don't think investing + time in debugging and fixing is worthwhile, especially considering + that SGI has last updated those compilers in 2006, and is expected + to retire support for them in December 2013: + + + - Future versions of Automake might remove support for MS-DOS and + Windows 95/98/ME (support for them was offered by relying on the + DJGPP project). Note however that both Cygwin and MSYS/MinGW on + modern Windows versions will continue to be fully supported. + + - Automake-provided scripts and makefile recipes might (finally!) + start assuming a POSIX shell in Automake 2.0. + + - Starting from Automake 2.0, third-party m4 files located in the + system-wide aclocal directory, as well as in any directory listed + in the ACLOCAL_PATH environment variable, will take precedence + over "built-in" Automake macros. For example (assuming Automake + is installed in the /usr/local hierarchy), a definition of the + AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4' + should take precedence over the same-named automake-provided macro + (defined in '/usr/local/share/aclocal-2.0/vala.m4'). + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +New in 1.13.3: + +* Documentation fixes: + + - The documentation no longer mistakenly reports that the obsolete + 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going + to be removed in Automake 2.0. + +* Bugs fixed: + + - Byte-compilation of Emacs lisp files could fail spuriously on Solaris, + when /bin/ksh or /usr/xpg4/bin/sh were used as shell. + + - The same user-defined suffix being transformed into different + Automake-known suffixes in different Makefiles could confuse automake + and make it generate inconsistent Makefiles (automake bug#14441). + For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule, and + 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake would + have mistakenly put into 'Makefile.in' rules to compile *.c files + into object files, and into 'sub/Makefile.in' rules to compile *.cc + files into object files --- rather than the other way around. + This is now fixed. + +* Testsuite work: + + - The test cases no longer have the executable bit set. This should + make it clear that they are not meant to be run directly; as + explained in t/README, they can only be run through the custom + 'runtest' script, or by a "make check" invocation. + + - The testsuite has seen the introduction of a new helper function + 'run_make', and several related changes. These serve a two-fold + purpose: + + 1. Removing brittleness due to the use of "make -e" in test cases. + + 2. Seamlessly allowing the use of parallel make ("make -j...") in + the test cases, even where redirection of make output is involved + (see automake bug#11413 for a description of the subtle issues in + this area). + + - Few spurious failures have been fixed (they hit especially MinGW/MSYS). + See automake bugs #14493, #14494, #14495, #14498, #14499, #14500 and + #14501. + + - Some other minor miscellaneous changes and fixlets. + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +New in 1.13.2: + +* Obsolescent features: + + - Use of suffix-less info files (that can be specified through the + '@setfilename' macro in Texinfo input files) is discouraged, and + its use will raise warnings in the 'obsolete' category. + + - Use of Texinfo input files with '.txi' or '.texinfo' extensions + is discouraged, and its use will raise warnings in the 'obsolete' + category. You are advised to simply use the '.texi' extension + instead. + +* Documentation fixes: + + - The long-deprecated but still supported two-arguments invocation form + of AM_INIT_AUTOMAKE is documented once again. This seems the sanest + thing to do, given that support for such usage might need to remain + in place for an unspecified amount of time in order to cater to people + who want to define the version number for their package dynamically at + configure runtime (unfortunately, Autoconf does not yet support this + scenario, so we cannot delegate the work to it). + + - The serial testsuite harness is no longer reported as "deprecated", + but as "discouraged". We have no plan to remove it, nor to make its + use cause runtime warnings. + + - The parallel testsuite is no longer reported as "experimental"; it + is well tested, and should be stable now. + + - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and + 'dist-tarZ' options are obsolescent, and their use is deprecated + in the documentation. + + - Other minor miscellaneous fixes and improvements; in particular, + some improvements in cross-references. + +* Bugs fixed: + + - When the 'ustar' option is used, the generated configure script no + longer risks hanging during the tests for the availability of the + 'pax' utility, even if the user running configure has a UID or GID + that requires more than 21 bits to be represented. + See automake bug#8343 and bug#13588. + + - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once + again, as they did in Automake 1.12.x (albeit printing runtime + warnings in the 'obsolete' category). Removing them has turned + out to be a very bad idea, because it complicated distro packing + enormously. Making them issue fatal warnings, as we did in + Automake 1.13, has turned out to be a similarly very bad idea, + for exactly the same reason. + + - aclocal will no longer error out if the first local m4 directory + (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or + 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report + a warning in the 'unsupported' category. This is done to support + some pre-existing real-world usages. See automake bug#13514. + + - aclocal will no longer consider directories for extra m4 files more + than once, even if they are specified multiple times. This ensures + packages that specify both + + AC_CONFIG_MACRO_DIR([m4]) in configure.ac + ACLOCAL_AMFLAGS = -I m4 in Makefile.am + + will work correctly, even when the 'm4' directory contains no + package-specific files, but is used only to install third-party + m4 files (as can happen with e.g., "libtoolize --install"). + See automake bug#13514. + + - Analysis of make flags in Automake-generated rules has been made more + robust, and more future-proof. For example, in presence of make that + (like '-I') take an argument, the characters in said argument will no + longer be spuriously considered as a set of additional make options. + In particular, automake-generated rules will no longer spuriously + believe to be running in dry mode ("make -n") if run with an invocation + like "make -I noob"; nor will they believe to be running in keep-going + mode ("make -k") if run with an invocation like "make -I kool" + (automake bug#12554). + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +New in 1.13.1: + +* Bugs fixed: + + - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now + causes a clear and helpful error message, instead of obscure ones + (issue introduced in Automake 1.13). + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + New in 1.13: +* Bugs fixed: + + - ylwrap renames properly header guards in generated header files + (*.h), instead of leaving Y_TAB_H. + + - ylwrap now also converts header guards in implementation files + (*.c). Because ylwrap failed to rename properly #include in the + implementation files, current versions of Bison (e.g., 2.7) + duplicate the generated header file in the implementation file. + The header guard then protects the implementation file from + duplicate definitions from the header file. + * Version requirements: - - Autoconf 2.65 or greater is required. + - Autoconf 2.65 or greater is now required. - The rules to build PDF and DVI output from Texinfo input now - requires Texinfo 4.9 or later. + require Texinfo 4.9 or later. + +* Obsolete features: - Support for the "Cygnus-style" trees (once enabled by the 'cygnus' option) has been removed. See discussion about automake bug#11034 - for more background. - - - The automake-provided '@mkdir_p@' configure substitution and - AM_PROG_MKDIR m4 macro have been removed. They had been obsolete - since automake 1.10, and actively deprecated since Automake 1.12.1. - However, to maintain a degree of backward-compatibility, the make - variable '$(mkdir_p)' is still defined (now simple as an alias to - '$(MKDIR_P)'). It will probably be removed in future major versions - of Automake (probably 1.14). + for more background: . - The deprecated aclocal option '--acdir' has been removed. You should use the options '--automake-acdir' and '--system-acdir' @@ -39,8 +280,6 @@ New in 1.13: - All the "old alias" macros in 'm4/obsolete.m4' have been removed. -* Obsolescent features: - - Use of the long-deprecated two- and three-arguments invocation forms of the AM_INIT_AUTOMAKE is no longer documented. It's still supported though (albeit with a warning in the 'obsolete' category), to cater @@ -100,6 +339,9 @@ New in 1.13: * Texinfo Support: + - The rules to build PDF and DVI files from Texinfo input now require + Texinfo 4.9 or later. + - The rules to build PDF and DVI files from Texinfo input now use the '--build-dir' option, to keep the auxiliary files used by texi2dvi and texi2pdf around without cluttering the build directory, and to @@ -110,8 +352,8 @@ New in 1.13: - The 'missing' script no longer tries to update the timestamp of out-of-date files that require a maintainer-specific tool to be remade, in case the user lacks such a tool (or has a too-old version - of it). It just give a useful warning, and in some cases also a tip - about how to obtain such a tool. + of it). It just gives a useful warning, and in some cases also a + tip about how to obtain such a tool. - The missing script has thus become useless as a (poor) way to work around the sketched-timestamps issues that can happen for projects @@ -138,79 +380,76 @@ New in 1.13: * Improvements to aclocal and related rebuilds rules: - - The Autoconf-provided macro AC_CONFIG_MACRO_DIR is now traced by - aclocal, and can be used to declare the local m4 include directory. - Formerly, one had to specify it with an explicit '-I' option to the - 'aclocal' invocation. + - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS + are now traced by aclocal, and can be used to declare the local m4 + include directories. Formerly, one had to specify it with an explicit + '-I' option to the 'aclocal' invocation. - The special make variable ACLOCAL_AMFLAGS is deprecated; future Automake versions will warn about its use, and later version will remove support for it altogether. +* The depcomp script: + + - Dropped support for libtool 1.4. + + - Various internal refactorings. They should cause no visible change, + but the chance for regression is there anyway, so please report any + unexpected or suspicious behaviour. + + - Support for pre-8.0 versions of the Intel C Compiler has been dropped. + This should cause no problem, since icc 8.0 has been released in + December 2003 -- almost nine years ago. + + - Support for tcc (the Tiny C Compiler) has been improved, and is now + handled through a dedicated 'tcc' mode. + +* The ylwrap script: + + - ylwrap generates header guards with a single '_' for series of non + alphabetic characters, instead of several. This is what Bison >= + 2.5.1 does. + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -New in 1.12.5: +Bugs fixed in 1.12.6: -* WARNING: Future backward-incompatibilities! +* Python-related bugs: - - Future versions of Automake will likely drop support for the - long-deprecated 'configure.in' name for the Autoconf input file. - You are advised to use the recommended name 'configure.ac' instead. + - The default installation location for python modules has been improved + for Python 3 on Debian and Ubuntu systems, changing from: - - Support for the "Cygnus-style" trees (as enabled by the 'cygnus' - option) will be removed in the next major Automake release (1.13). + ${prefix}/lib/python3/dist-packages - - The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will - be removed in Automake 1.13. The $(mkdir_p) make variable and the - @mkdir_p@ substitution will still remain available (as aliases of - $(MKDIR_P)) for the moment, for better backward compatibility. + to - - Autoconf 2.65 or later will be required by the next major Automake - version (1.13). Until now, Automake has required Autoconf version - 2.62 or later. + ${prefix}/lib/python3.x/site-packages - - Starting from the next major Automake version (1.13), the rules - to build pdf, ps and dvi output from Texinfo input will use the - '--build-dir' option by default. Since such an option was only - introduced in Texinfo 4.9, this means that Makefiles generated by - future Automake versions will require at least that version of - Texinfo. + This change should ensure modules installed using the default ${prefix} + "/usr/local" are found by default by system python 3.x installations. + See automake bug#10227. - - Starting from the next major Automake version (1.13), the parallel - testsuite harness (previously only enabled by the 'parallel-tests' - option) will become the default one; the older serial testsuite - harness will still be available through the use of the 'serial-tests' - option. + - Python byte-compilation supports the new layout mandated by PEP-3147, + with its __pycache__ directory (automake bug#8847). - - The following long-obsolete m4 macros will be removed in the - next major Automake version (1.13): +* Build system issues: - AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002 - fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC - fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC - AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002 - ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR - jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE - ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT - gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL - fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part - of the now-removed automatic de-ANSI-fication - support of Automake) + - The maintainer rebuild rules for Makefiles and aclocal.m4 in + Automake's own build system works correctly again (bug introduced + in Automake 1.12.5). - - All the "old alias" macros in 'm4/obsolete.m4' will be removed in - the next major Automake version (1.13). +* Testsuite issues: - - The '--acdir' option of aclocal is deprecated, and will probably - be removed in the next major Automake release (1.13). You should - use the options '--automake-acdir' and '--system-acdir' instead - (which have been introduced in Automake 1.11.2). + - The Vala-related tests has been changed to adjust to the removal of + the 'posix' profile in the valac compiler. See automake bug#12934 + a.k.a. bug#12522. - - The 'missing' script will no longer try to update the timestamp - of out-of-date files that require a maintainer-specific tool to be - remade, in case the user lacks such a tool (or has a too-old version - of it). In fact, starting from Automake 1.13, all it'll do will be - giving more useful warnings than a bare "command not found" from a - make recipe would. + - Some spurious testsuite failures related to older tools and systems + have been fixed. + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +New in 1.12.5: * Vala support: @@ -236,6 +475,12 @@ New in 1.12.5: the error possibly going unnoticed or triggering harder-to-diagnose fallout failures in later steps. +* Miscellaneous changes: + + - automake and aclocal no longer honours the 'perllibdir' environment + variable. That had always been intended only as an hack required in + the testsuite, not meant for any use beyond that. + Bugs fixed in 1.12.5: * Long-standing bugs: @@ -1398,8 +1643,8 @@ New in 1.9: tar-pax. The new option filename-length-max=99 helps diagnosing filenames that are too long for tar-v7. (PR/414) - - Variables aumented with `+=' are now automatically flattened (i.e., - trailing backslashes removed) and then wrapped around 80 colummns + - Variables augmented with `+=' are now automatically flattened (i.e., + trailing backslashes removed) and then wrapped around 80 columns (adding trailing backslashes). In previous versions, a long series of VAR += value1 @@ -2419,7 +2664,7 @@ New in 0.20: ----- -Copyright (C) 1995-2012 Free Software Foundation, Inc. +Copyright (C) 1995-2013 Free Software Foundation, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by