From: Akim Demaille Date: Mon, 20 Dec 1999 13:33:27 +0000 (+0000) Subject: Updated. X-Git-Tag: autoconf-2.50~1310 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=80c299377a3d4ac37427eb0d5b62c649a9fbb77f;p=thirdparty%2Fautoconf.git Updated. --- diff --git a/NEWS b/NEWS index c6d6b2705..d39329d42 100644 --- a/NEWS +++ b/NEWS @@ -1,50 +1,51 @@ -* Major changes in release 2.14.1 -*- outline -*- - -** Use of Automake -All the standard GNU Makefile targets are supported. - -* config.status - - much faster on most architectures - - has a useful --help - - concurrent executions - It is safe to use `make -j' with config.status. - - files to links (AC_LINK_FILES) can be specified via CONFIG_LINKS. - - human interface improved - It is possible to invoke - ./config.status foobar - instead of the former form (still valid) - CONFIG_HEADERS= CONFIG_LINKS= CONFIG_FILES=foobar:foo.in:bar.in \ - ./config.status - The same holds for configuration headers and links. -* New macros - - AC_CHECK_DECL and AC_CHECK_DECLS - To check whether a symbol is declared. - - AC_HELP_STRING - To format an Autoconf macro's help string so that it looks pretty - when the user executes `configure --help'. - - AC_ARG_VAR - Document and ask for the registration of an envvar. - - AC_CONFIG_LINKS - Replaces the now obsolete AC_LINK_FILES. - - AC_PROG_CC_STDC - Checks if the compiler supports ISO C, included when needs special - options. - -* Environment variables are kept when reconfiguring. - The previous scheme to set envvar before running configure was - ENV=VAL ./configure - what prevented configure from remembering the environment in which - it was run, therefore --recheck was run in an inconsistent environment. - Now, one runs - ./configure ENV=VAR - and the --recheck works correctly. Variable declared with AC_ARG_VAR - are also preserved. -* Support for automatically determining a Fortran 77 compilers - name-mangling scheme. New CPP macros F77_FUNC and F77_FUNC_ are - provided to wrap C/C++ identifiers, thus making it easier and more - transparent for C/C++ to call Fortran 77 routines, and Fortran 77 to - call C/C++ routines. See the Texinfo documentation for details. -* Many fixesd to bugs reported to the Autoconf GNATS database. +* Major changes in release 2.15 -*- outline -*- + +** config.status +- much faster on most architectures +- has a useful --help +- concurrent executions +It is safe to use `make -j' with config.status. +- files to links (AC_LINK_FILES) can be specified via CONFIG_LINKS. +- commands to run can be specified via CONFIG_COMMANDS. +- human interface improved +It is possible to invoke + ./config.status foobar +instead of the former form (still valid) + CONFIG_COMMANDS= CONFIG_HEADERS= CONFIG_LINKS= \ + CONFIG_FILES=foobar:foo.in:bar.in \ + ./config.status +The same holds for configuration headers and links. + +** New macros +- AC_CHECK_DECL and AC_CHECK_DECLS +To check whether a symbol is declared. +- AC_HELP_STRING +To format an Autoconf macro's help string so that it looks pretty when +the user executes `configure --help'. +- AC_ARG_VAR +Document and ask for the registration of an envvar. +- AC_CONFIG_LINKS +Replaces the now obsolete AC_LINK_FILES. +- AC_CONFIG_COMMANDS +To add new actions to config.status. Should be used instead of +AC_OUTPUT_COMMANDS. + +** Environment variables are kept when reconfiguring. +The previous scheme to set envvar before running configure was + ENV=VAL ./configure +what prevented configure from remembering the environment in which +it was run, therefore --recheck was run in an inconsistent environment. +Now, one runs + ./configure ENV=VAR +and the --recheck works correctly. Variables declared with AC_ARG_VAR +are also preserved. + +** Fortran 77 compilers +Support for automatically determining a Fortran 77 compilers +name-mangling scheme. New CPP macros F77_FUNC and F77_FUNC_ are +provided to wrap C/C++ identifiers, thus making it easier and more +transparent for C/C++ to call Fortran 77 routines, and Fortran 77 to +call C/C++ routines. See the Texinfo documentation for details. Major changes in release 2.14: There was no release of GNU Autoconf 2.14. diff --git a/TODO b/TODO index c72708038..b5ef67e87 100644 --- a/TODO +++ b/TODO @@ -19,7 +19,7 @@ reader catches that properly, we should not care. If no info reader can handle this, we should change the affected node names. Bug triggered by looking for `CONFIG_FILES' in the index. -** autoconf.texi: Document AC_CONFIG_FILES. +** autoconf.texi: Document AC_CONFIG_FILES and AC_CONFIG_COMMANDS. I didn't do it, because I don't know where to do that. I would like to have all the AC_CONFIG_ together, but it is not currently the case. An architecture for the docs needs to be decided. @@ -36,10 +36,7 @@ AC_CHECK_MEMBER/AC_CHECK_MEMBERS is a proposal, see the code. ** AC_CHECK_HEADER should not template config.h entries. Its entry in autoheader.m4 should be removed. -** Allow tags for AC_OUTPUT_COMMANDS -so that we can run ./config.status name-of-the command. - -** Generalize the association of a commands to an output file. +** Generalize the association of commands to an output file. See AC_CONFIG_FILES: it is possible to associate a command which is run when the file is creating. This should be extended to all the other AC_CONFIG entities. But then there is a question: should the