Re: autoconf-2.70 released [stable]
Woohoo!! About time! :) On Tue, Dec 8, 2020 at 12:14 PM Zack Weinberg wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > We are pleased to announce stable release 2.70 of GNU Autoconf. > > This release includes eight years of development work since the > previous release, 2.69. Noteworthy changes include support for the > 2011 revisions of the C and C++ standards, support for reproducible > builds, improved support for cross-compilation, improved compatibility > with current compilers and shell utilities, more efficient generated > shell code, and many bug fixes. See below for a detailed list of > changes since the previous version, 2.69, as summarized by the NEWS > file. > > Unfortunately, we were not able to maintain perfect backward > compatibility with existing Autoconf scripts. Caution is advised when > upgrading. The list of changes, below, includes detailed explanations > and advice for all of the compatibility problems we know about. > > Please report bugs and problems with this release to the Savannah bug > tracker: > >https://savannah.gnu.org/support/?func=additem=autoconf > > Please also send general comments and feedback to . > > We would like to thank everyone who has contributed patches, reported > problems, and helped testing Autoconf in the past decade. > > - -*-*-*- > > Here are the compressed sources: > https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.gz (2.0MB) > https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.xz (1.3MB) > > Here are the GPG detached signatures[*]: > https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.gz.sig > https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.xz.sig > > Use a mirror for higher download bandwidth: > https://www.gnu.org/order/ftp.html > > [*] Use a .sig file to verify that the corresponding file (without the > .sig suffix) is intact. First, be sure to download both the .sig file > and the corresponding tarball. Then, run a command like this: > > gpg --verify autoconf-2.70.tar.gz.sig > > If that command fails because you don't have the required public key, > then run this command to import it: > > gpg --keyserver keys.gnupg.net --recv-keys 91FCC32B6769AA64 > > and rerun the 'gpg --verify' command. > > This release was bootstrapped with the following tools: > Automake 1.16.3 > > - -*-*-*- > > * Noteworthy changes in release 2.70 (2020-12-08) [stable] > > ** Backward incompatibilities: > > *** Warnings about obsolete constructs are now on by default. > > These warnings can be turned off with ‘-Wno-obsolete’. > > Many of these warnings advise maintainers to run autoupdate. > Be aware that autoupdate cannot solve all backward compatibility > problems, and cannot completely solve all of the problems it does > address. A configure script edited by autoupdate is likely to > need further manual fix-ups. > > *** Many macros have become pickier about argument quotation. > > If you get a shell syntax error from your generated configure > script, or seemingly impossible misbehavior (e.g. entire blocks of > the configure script not getting executed), check first that all > macro arguments are properly quoted. The “M4 Quotation” section of > the manual explains how to quote macro arguments properly. > > It is unfortunately not possible for autoupdate to correct > quotation errors. > > *** Many macros no longer AC_REQUIRE as many other macros as they used to. > > This can expose several classes of latent bugs. These are the ones > we know about: > >- Make sure to explicitly invoke all of the macros that set result > variables used later in the configure script, or in generated > Makefiles. > >- Autoconf macros that use AC_REQUIRE are not safe to use in shell > control-flow constructs that appear outside of macros defined by > AC_DEFUN. Use AS_IF, AS_CASE, etc. instead. (See the > “Prerequisite Macros” section of the manual for details.) > > The set of macros that use AC_REQUIRE internally may change from > release to release. The only macros that are guaranteed *not* to > use AC_REQUIRE are the macros for acting on the results of a > test: AC_DEFINE, AC_SUBST, AC_MSG_*, AC_CACHE_CHECK, etc. > >- AC_REQUIRE cannot be applied to macros that need to be used with > arguments. Instead, invoke the macro normally, with its arguments. > > *** More macros use config.sub and config.guess internally. > > As a consequence of improved support for cross compilation (see below), > more macros now use the auxiliary scripts ‘config.sub’ and > ‘config.guess’. > If you use any of the affected macros, these scripts must be available > when your configure script is run, even if you have no intention of > ever cross-compiling your program. > > autoreconf will issue an error if any auxiliary scripts are needed but > cannot be found. (It is not currently possible to make autoconf > itself issue this error.) > > ‘autoreconf
autoconf-2.70 released [stable]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 We are pleased to announce stable release 2.70 of GNU Autoconf. This release includes eight years of development work since the previous release, 2.69. Noteworthy changes include support for the 2011 revisions of the C and C++ standards, support for reproducible builds, improved support for cross-compilation, improved compatibility with current compilers and shell utilities, more efficient generated shell code, and many bug fixes. See below for a detailed list of changes since the previous version, 2.69, as summarized by the NEWS file. Unfortunately, we were not able to maintain perfect backward compatibility with existing Autoconf scripts. Caution is advised when upgrading. The list of changes, below, includes detailed explanations and advice for all of the compatibility problems we know about. Please report bugs and problems with this release to the Savannah bug tracker: https://savannah.gnu.org/support/?func=additem=autoconf Please also send general comments and feedback to . We would like to thank everyone who has contributed patches, reported problems, and helped testing Autoconf in the past decade. - -*-*-*- Here are the compressed sources: https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.gz (2.0MB) https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.xz (1.3MB) Here are the GPG detached signatures[*]: https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.gz.sig https://ftpmirror.gnu.org/autoconf/autoconf-2.70.tar.xz.sig Use a mirror for higher download bandwidth: https://www.gnu.org/order/ftp.html [*] Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this: gpg --verify autoconf-2.70.tar.gz.sig If that command fails because you don't have the required public key, then run this command to import it: gpg --keyserver keys.gnupg.net --recv-keys 91FCC32B6769AA64 and rerun the 'gpg --verify' command. This release was bootstrapped with the following tools: Automake 1.16.3 - -*-*-*- * Noteworthy changes in release 2.70 (2020-12-08) [stable] ** Backward incompatibilities: *** Warnings about obsolete constructs are now on by default. These warnings can be turned off with â-Wno-obsoleteâ. Many of these warnings advise maintainers to run autoupdate. Be aware that autoupdate cannot solve all backward compatibility problems, and cannot completely solve all of the problems it does address. A configure script edited by autoupdate is likely to need further manual fix-ups. *** Many macros have become pickier about argument quotation. If you get a shell syntax error from your generated configure script, or seemingly impossible misbehavior (e.g. entire blocks of the configure script not getting executed), check first that all macro arguments are properly quoted. The âM4 Quotationâ section of the manual explains how to quote macro arguments properly. It is unfortunately not possible for autoupdate to correct quotation errors. *** Many macros no longer AC_REQUIRE as many other macros as they used to. This can expose several classes of latent bugs. These are the ones we know about: - Make sure to explicitly invoke all of the macros that set result variables used later in the configure script, or in generated Makefiles. - Autoconf macros that use AC_REQUIRE are not safe to use in shell control-flow constructs that appear outside of macros defined by AC_DEFUN. Use AS_IF, AS_CASE, etc. instead. (See the âPrerequisite Macrosâ section of the manual for details.) The set of macros that use AC_REQUIRE internally may change from release to release. The only macros that are guaranteed *not* to use AC_REQUIRE are the macros for acting on the results of a test: AC_DEFINE, AC_SUBST, AC_MSG_*, AC_CACHE_CHECK, etc. - AC_REQUIRE cannot be applied to macros that need to be used with arguments. Instead, invoke the macro normally, with its arguments. *** More macros use config.sub and config.guess internally. As a consequence of improved support for cross compilation (see below), more macros now use the auxiliary scripts âconfig.subâ and âconfig.guessâ. If you use any of the affected macros, these scripts must be available when your configure script is run, even if you have no intention of ever cross-compiling your program. autoreconf will issue an error if any auxiliary scripts are needed but cannot be found. (It is not currently possible to make autoconf itself issue this error.) âautoreconf --installâ will add âconfig.subâ, âconfig.guessâ, and âinstall-shâ to your source tree if they are needed. If you are using Automake, scripts added to your tree by âautoreconf --installâ will automatically be included in the tarball
