+2006-08-31 Paul Eggert <eggert@cs.ucla.edu>
+
+ * NEWS: AC_FUNC_FNMATCH, AC_FUNC_FNMATCH_GNU, AC_FUNC_GETLOADVG,
+ and AC_REPLACE_FNMATCH are now obsolescent in Autoconf. New
+ programs should use their Gnulib counterparts.
+ * doc/autoconf.texi (Particular Functions): Likewise.
+ (Macro Names, testsuite Invocation): Replace uses of these
+ obsolete macros with uses of non-obsolete macros.
+
2006-08-29 Eric Blake <ebb9@byu.net>
* configure.ac (AC_INIT): Bump to 2.60b.
* Major changes in Autoconf 2.60b (??)
+** Obsolescent macros
+ The documentation now says that the following macros are obsolescent,
+ as they are superseded by Gnulib:
+
+ AC_FUNC_FNMATCH AC_FUNC_FNMATCH_GNU AC_FUNC_GETLOADVG AC_REPLACE_FNMATCH
+
+ New programs should use the Gnulib counterparts of these macros.
+ We have no current plans to remove them from Autoconf.
+
* Major changes in Autoconf 2.60a (2006-08-25)
** GNU M4 1.4.6 or later is now recommended. At least one "make check"
@code{AC_FUNC} macros, @code{AC_FUNC_FNMATCH} does not replace a
broken/missing @code{fnmatch}. This is for historical reasons.
See @code{AC_REPLACE_FNMATCH} below.
+
+This macro is obsolescent. New programs should use Gnulib's
+@code{fnmatch-posix} module. @xref{Gnulib}.
@end defmac
@defmac AC_FUNC_FNMATCH_GNU
whether @code{fnmatch} supports @acronym{GNU} extensions. Detect common
implementation bugs, for example, the bugs in the @acronym{GNU} C
Library 2.1.
+
+This macro is obsolescent. New programs should use Gnulib's
+@code{fnmatch-gnu} module. @xref{Gnulib}.
@end defmac
@defmac AC_FUNC_FORK
@code{KMEM_GROUP} to the name of the group that should own the installed
program.
@end enumerate
+
+The @code{AC_FUNC_GETLOADVG} macro is obsolescent. New programs should
+use Gnulib's @code{getloadavg} module. @xref{Gnulib}.
@end defmac
@defmac AC_FUNC_GETMNTENT
this source code is compiled as an @code{AC_LIBOBJ} replacement, and the
@file{fnmatch_.h} file is linked to @file{fnmatch.h} so that it can be
included in place of the system @code{<fnmatch.h>}.
+
+This macro is obsolescent, as it assumes the use of particular source
+files. New programs should use Gnulib's @code{fnmatch-posix} module,
+which provides this macro along with the source files. @xref{Gnulib}.
@end defmac
After the category comes the name of the particular feature being
tested. Any further words in the macro name indicate particular aspects
-of the feature. For example, @code{AC_FUNC_FNMATCH_GNU} checks whether
-the @code{fnmatch} function supports @acronym{GNU} extensions.
+of the feature. For example, @code{AC_PROG_CC_STDC} checks whether the
+C compiler supports @acronym{ISO} Standard C.
An internal macro should have a name that starts with an underscore;
Autoconf internals should therefore start with @samp{_AC_}.
@noindent
selects all tests tagged @samp{autoupdate} @emph{and} with tags
-containing @samp{FUNC} (as in @samp{AC_CHECK_FUNC}, @samp{AC_FUNC_FNMATCH},
+containing @samp{FUNC} (as in @samp{AC_CHECK_FUNC}, @samp{AC_FUNC_ALLOCA},
etc.), while
@example