-diff -Nur autoconf-2.50.orig/doc/autoconf.texi autoconf-2.50/doc/autoconf.texi
---- autoconf-2.50.orig/doc/autoconf.texi Fri Jun 15 14:57:50 2001
-+++ autoconf-2.50/doc/autoconf.texi Fri Jun 15 15:21:46 2001
-@@ -27,25 +27,20 @@
- @end ifnothtml
+--- autoconf-2.69/doc/autoconf.texi.orig 2013-10-15 07:44:41.594844773 +0200
++++ autoconf-2.69/doc/autoconf.texi 2013-10-15 07:45:45.782179984 +0200
+@@ -217,29 +217,19 @@
--@dircategory GNU admin
-+@dircategory Programming tools:
- @direntry
--* Autoconf: (autoconf). Create source code configuration scripts
-+* Autoconf: (autoconf). Create source code configuration scripts
- @end direntry
- @dircategory Individual utilities
+-@dircategory Software development
++@dircategory Programming tools:
@direntry
+-* Autoconf: (autoconf). Create source code configuration scripts.
+-@end direntry
+-
+-@dircategory Individual utilities
+-@direntry
-* autoscan: (autoconf)autoscan Invocation.
- Semi-automatic @file{configure.ac} writing
--* ifnames: (autoconf)ifnames Invocation.
-- Listing the conditionals in source code
--* autoconf: (autoconf)autoconf Invocation.
+-* ifnames: (autoconf)ifnames Invocation. Listing conditionals in source.
+-* autoconf-invocation: (autoconf)autoconf Invocation.
- How to create configuration scripts
-* autoreconf: (autoconf)autoreconf Invocation.
-- Remaking multiple @code{configure} scripts
--* configure: (autoconf)configure Invocation.
-- Configuring a package
--* config.status: (autoconf)config.status Invocation.
-- Recreating a configuration
+- Remaking multiple @command{configure} scripts
+-* autoheader: (autoconf)autoheader Invocation.
+- How to create configuration templates
+-* autom4te: (autoconf)autom4te Invocation.
+- The Autoconf executables backbone
+-* configure: (autoconf)configure Invocation. Configuring a package.
+-* autoupdate: (autoconf)autoupdate Invocation.
+- Automatic update of @file{configure.ac}
+-* config.status: (autoconf)config.status Invocation. Recreating configurations.
+-* testsuite: (autoconf)testsuite Invocation. Running an Autotest test suite.
++* Autoconf: (autoconf). Create source code configuration scripts
+* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac} writing
-+* ifnames: (autoconf)ifnames. Listing the conditionals in source code
++* ifnames: (autoconf)ifnames. Listing conditionals in source
+* autoconf: (autoconf)autoconf. How to create configuration scripts
-+* autoreconf: (autoconf)autoreconf. Remaking multiple @code{configure} scripts
++* autoreconf: (autoconf)autoreconf. Remaking multiple @command{configure} scripts
++* autoheader: (autoconf)autoheader. How to create configuration templates
++* autom4te: (autoconf)autom4te. The Autoconf executables backbone
+* configure: (autoconf)configure. Configuring a package
-+* config.status: (autoconf)config.status.
-+ Recreating a configuration
++* autoupdate: (autoconf)autoupdate. Automatic update of @file{configure.ac}
++* config.status: (autoconf)config.status. Recreating configurations.
++* testsuite: (autoconf)testsuite. Running an Autotest test suite.
@end direntry
- @ifinfo
-@@ -142,7 +137,7 @@
+ @titlepage
+@@ -282,7 +272,7 @@
* Manual Configuration:: Selecting features that can't be guessed
- * Site Configuration:: Local defaults for @code{configure}
- * Running configure scripts:: How to use the Autoconf output
+ * Site Configuration:: Local defaults for @command{configure}
+ * Running configure Scripts:: How to use the Autoconf output
-* config.status Invocation:: Recreating a configuration
+* config.status:: Recreating a configuration
* Obsolete Constructs:: Kept for backward compatibility
- * Questions:: Questions about Autoconf, with answers
- * History:: History of Autoconf
-@@ -164,10 +159,10 @@
- Making @code{configure} Scripts
+ * Using Autotest:: Creating portable test suites
+ * FAQ:: Frequent Autoconf Questions, with answers
+@@ -303,10 +293,10 @@
+ Making @command{configure} Scripts
- * Writing configure.ac:: What to put in an Autoconf input file
+ * Writing Autoconf Input:: What to put in an Autoconf input file
-* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
-* ifnames Invocation:: Listing the conditionals in source code
-* autoconf Invocation:: How to create configuration scripts
--* autoreconf Invocation:: Remaking multiple @code{configure} scripts
+-* autoreconf Invocation:: Remaking multiple @command{configure} scripts
+* autoscan:: Semi-automatic @file{configure.ac} writing
+* ifnames:: Listing the conditionals in source code
+* autoconf:: How to create configuration scripts
-+* autoreconf:: Remaking multiple @code{configure} scripts
++* autoreconf:: Remaking multiple @command{configure} scripts
Writing @file{configure.ac}
-@@ -199,7 +194,7 @@
+@@ -341,7 +331,7 @@
Configuration Header Files
* Header Templates:: Input for the configuration headers
* Autoheader Macros:: How to specify CPP templates
Existing Tests
-@@ -348,13 +343,13 @@
+@@ -460,7 +450,7 @@
+
+ Using @command{autom4te}
+
+-* autom4te Invocation:: A GNU M4 wrapper
++* autom4te:: A GNU M4 wrapper
+ * Customizing autom4te:: Customizing the Autoconf package
+
+ Programming in M4sugar
+@@ -601,13 +591,13 @@
* System Type:: Specifying the system type
- * Sharing Defaults:: Setting site-wide defaults for @code{configure}
- * Environment Variables:: Defining environment variables.
--* configure Invocation:: Changing how @code{configure} runs
-+* configure:: Changing how @code{configure} runs
+ * Sharing Defaults:: Setting site-wide defaults for @command{configure}
+ * Defining Variables:: Specifying the compiler etc.
+-* configure Invocation:: Changing how @command{configure} runs
++* configure:: Changing how @command{configure} runs
Obsolete Constructs
- * Obsolete config.status Use:: Different calling convention
- * acconfig.h:: Additional entries in @file{config.h.in}
+ * Obsolete config.status Use:: Obsolete convention for @command{config.status}
+ * acconfig Header:: Additional entries in @file{config.h.in}
-* autoupdate Invocation:: Automatic update of @file{configure.ac}
+* autoupdate:: Automatic update of @file{configure.ac}
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
+ * Autoconf 2.13:: Some fresher tips
+@@ -632,7 +622,7 @@
+
+ * Using an Autotest Test Suite:: Autotest and the user
+ * Writing Testsuites:: Autotest macros
+-* testsuite Invocation:: Running @command{testsuite} scripts
++* testsuite:: Running @command{testsuite} scripts
+ * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
-@@ -652,7 +647,7 @@
+ Using an Autotest Test Suite
+@@ -992,7 +982,7 @@
@item
- a shell script called @file{config.status} that, when run, will recreate
+ a shell script called @file{config.status} that, when run, recreates
-the files listed above (@pxref{config.status Invocation});
+the files listed above (@pxref{config.status});
@item
an optional shell script normally called @file{config.cache}
-@@ -712,13 +707,13 @@
+@@ -1073,10 +1063,10 @@
@menu
- * Writing configure.ac:: What to put in an Autoconf input file
+ * Writing Autoconf Input:: What to put in an Autoconf input file
-* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
-* ifnames Invocation:: Listing the conditionals in source code
-* autoconf Invocation:: How to create configuration scripts
--* autoreconf Invocation:: Remaking multiple @code{configure} scripts
+-* autoreconf Invocation:: Remaking multiple @command{configure} scripts
+* autoscan:: Semi-automatic @file{configure.ac} writing
+* ifnames:: Listing the conditionals in source code
+* autoconf:: How to create configuration scripts
-+* autoreconf:: Remaking multiple @code{configure} scripts
++* autoreconf:: Remaking multiple @command{configure} scripts
@end menu
--@node Writing configure.ac, autoscan Invocation, Making configure Scripts, Making configure Scripts
-+@node Writing configure.ac, autoscan, Making configure Scripts, Making configure Scripts
- @section Writing @file{configure.ac}
-
- To produce a @code{configure} script for a software package, create a
-@@ -730,7 +725,7 @@
- @ref{Writing Tests}, for information about them. For especially tricky
+ @node Writing Autoconf Input
+@@ -1092,7 +1082,7 @@
or specialized features, @file{configure.ac} might need to contain some
- hand-crafted shell commands. The @code{autoscan} program can give you a
--good start in writing @file{configure.ac} (@pxref{autoscan Invocation},
-+good start in writing @file{configure.ac} (@pxref{autoscan},
- for more information).
+ hand-crafted shell commands; see @ref{Portable Shell, , Portable Shell
+ Programming}. The @command{autoscan} program can give you a good start
+-in writing @file{configure.ac} (@pxref{autoscan Invocation}, for more
++in writing @file{configure.ac} (@pxref{autoscan} Invocation, for more
+ information).
Previous versions of Autoconf promoted the name @file{configure.in},
-@@ -959,7 +954,7 @@
+@@ -1380,7 +1370,7 @@
@end display
--@node autoscan Invocation, ifnames Invocation, Writing configure.ac, Making configure Scripts
-+@node autoscan, ifnames, Writing configure.ac, Making configure Scripts
- @section Using @code{autoscan} to Create @file{configure.ac}
- @cindex @code{autoscan}
+-@node autoscan Invocation
++@node autoscan
+ @section Using @command{autoscan} to Create @file{configure.ac}
+ @cindex @command{autoscan}
-@@ -979,7 +974,7 @@
- configuration header file, you must add a call to
- @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might also
- have to change or add some @code{#if} directives to your program in
+@@ -1402,7 +1392,7 @@
+ use a configuration header file, you must add a call to
+ @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might
+ also have to change or add some @code{#if} directives to your program in
-order to make it work with Autoconf (@pxref{ifnames Invocation}, for
+order to make it work with Autoconf (@pxref{ifnames}, for
information about a program that can help with that job).
- @code{autoscan} uses several data files (installed along with Autoconf)
-@@ -1017,7 +1012,7 @@
- plays with different versions of Autoconf simultaneously.
+ When using @command{autoscan} to maintain a @file{configure.ac}, simply
+@@ -1445,7 +1435,7 @@
+ Prepend @var{dir} to the include path. Multiple invocations accumulate.
@end table
--@node ifnames Invocation, autoconf Invocation, autoscan Invocation, Making configure Scripts
-+@node ifnames, autoconf, autoscan, Making configure Scripts
- @section Using @code{ifnames} to List Conditionals
- @cindex @code{ifnames}
+-@node ifnames Invocation
++@node ifnames
+ @section Using @command{ifnames} to List Conditionals
+ @cindex @command{ifnames}
-@@ -1026,8 +1021,7 @@
+@@ -1454,8 +1444,7 @@
preprocessor conditionals. If a package has already been set up to have
- some portability, @code{ifnames} can thus help you figure out what its
- @code{configure} needs to check for. It may help fill in some gaps in a
--@file{configure.ac} generated by @code{autoscan} (@pxref{autoscan
+ some portability, @command{ifnames} can thus help you figure out what its
+ @command{configure} needs to check for. It may help fill in some gaps in a
+-@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan
-Invocation}).
-+@file{configure.ac} generated by @code{autoscan} (@pxref{autoscan}).
++@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan}).
- @code{ifnames} scans all of the C source files named on the command line
+ @command{ifnames} scans all of the C source files named on the command line
(or the standard input, if none are given) and writes to the standard
-@@ -1049,7 +1043,7 @@
+@@ -1477,7 +1466,7 @@
Print the version number of Autoconf and exit.
@end table
--@node autoconf Invocation, autoreconf Invocation, ifnames Invocation, Making configure Scripts
-+@node autoconf, autoreconf, ifnames, Making configure Scripts
- @section Using @code{autoconf} to Create @code{configure}
- @cindex @code{autoconf}
-
-@@ -1311,7 +1305,7 @@
+-@node autoconf Invocation
++@node autoconf
+ @section Using @command{autoconf} to Create @command{configure}
+ @cindex @command{autoconf}
+
+@@ -1571,8 +1560,7 @@
+ @cindex Macro invocation stack
+ Because @command{autoconf} uses @command{autom4te} behind the scenes, it
+ displays a back trace for errors, but not for warnings; if you want
+-them, just pass @option{-W error}. @xref{autom4te Invocation}, for some
+-examples.
++them, just pass @option{-W error}. @xref{autom4te}, for some examples.
+
+ @item --trace=@var{macro}[:@var{format}]
+ @itemx -t @var{macro}[:@var{format}]
+@@ -1584,7 +1572,7 @@
+
+ The @var{format} is a regular string, with newlines if desired, and
+ several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
+-@ref{autom4te Invocation}, for details on the @var{format}.
++@ref{autom4te}, for details on the @var{format}.
+
+ @item --initialization
+ @itemx -i
+@@ -1658,7 +1646,7 @@
@end group
@end example
--@node autoreconf Invocation, , autoconf Invocation, Making configure Scripts
-+@node autoreconf, , autoconf, Making configure Scripts
- @section Using @code{autoreconf} to Update @code{configure} Scripts
- @cindex @code{autoreconf}
-
-@@ -1533,8 +1527,8 @@
- source directory; @code{configure} checks for this file's existence to
+-@node autoreconf Invocation
++@node autoreconf
+ @section Using @command{autoreconf} to Update @command{configure} Scripts
+ @cindex @command{autoreconf}
+
+@@ -1695,8 +1683,8 @@
+ Gettext supplies the @command{autopoint} command to add translation
+ infrastructure to a source package. If you use @command{autopoint},
+ your @file{configure.ac} should invoke both @code{AM_GNU_GETTEXT} and
+-@code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})}. @xref{autopoint
+-Invocation, , Invoking the @code{autopoint} Program, gettext,
++@code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})}.
++@xref{autopoint, , Invoking the @code{autopoint} Program, gettext,
+ GNU @code{gettext} utilities}, for further details.
+
+ @noindent
+@@ -2032,8 +2020,8 @@
+ source directory; @command{configure} checks for this file's existence to
make sure that the directory that it is told contains the source code in
fact does. Occasionally people accidentally specify the wrong directory
-with @option{--srcdir}; this is a safety check. @xref{configure
@end defmac
-@@ -1719,7 +1713,7 @@
+@@ -2247,7 +2235,7 @@
when used in @var{output}, or the standard input when used in the
@var{inputs}. You most probably don't need to use this in
@file{configure.ac}, but it is convenient when using the command line
+interface of @file{./config.status}, see @ref{config.status},
for more details.
- The @var{inputs} may be absolute or relative filenames. In the latter
-@@ -2185,7 +2179,7 @@
- @file{config.h} is considered up to date. @xref{Output}, for more
- information about @code{AC_OUTPUT}.
+ The @var{inputs} may be absolute or relative file names. In the latter
+@@ -3182,7 +3170,7 @@
+ so @file{config.status} ensures that @file{config.h} is considered up to
+ date. @xref{Output}, for more information about @code{AC_OUTPUT}.
-@xref{config.status Invocation}, for more examples of handling
+@xref{config.status}, for more examples of handling
configuration-related dependencies.
- @node Configuration Headers, Configuration Commands, Makefile Substitutions, Setup
-@@ -2246,11 +2240,11 @@
+ @node Configuration Headers
+@@ -3262,7 +3250,7 @@
@menu
* Header Templates:: Input for the configuration headers
* Autoheader Macros:: How to specify CPP templates
@end menu
--@node Header Templates, autoheader Invocation, Configuration Headers, Configuration Headers
-+@node Header Templates, autoheader, Configuration Headers, Configuration Headers
- @subsection Configuration Header Templates
- @cindex Configuration Header Template
- @cindex @file{config.h.in}
-@@ -2297,10 +2291,10 @@
- @samp{#undef} is strongly discouraged.
+@@ -3304,7 +3292,7 @@
+ generated header.
Since it is a tedious task to keep a template header up to date, you may
--use @code{autoheader} to generate it, see @ref{autoheader Invocation}.
-+use @code{autoheader} to generate it, see @ref{autoheader}.
+-use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
++use @command{autoheader} to generate it, see @ref{autoheader}.
+
+ During the instantiation of the header, each @samp{#undef} line in the
+ template file for each symbol defined by @samp{AC_DEFINE} is changed to an
+@@ -3342,7 +3330,7 @@
+ probably use @samp{AH_BOTTOM} to append the @samp{#include} directive.
+
+
+-@node autoheader Invocation
++@node autoheader
+ @subsection Using @command{autoheader} to Create @file{config.h.in}
+ @cindex @command{autoheader}
+
+@@ -7424,7 +7412,7 @@
+ And finally, the default for @var{action-if-universal} is to ensure that
+ @samp{WORDS_BIGENDIAN} is defined if and only if a universal build is
+ detected and the current code is big-endian; this default works only if
+-@command{autoheader} is used (@pxref{autoheader Invocation}).
++@command{autoheader} is used (@pxref{autoheader}).
+
+ If you use this macro without specifying @var{action-if-universal}, you
+ should also use @code{AC_CONFIG_HEADERS}; otherwise
+@@ -8013,10 +8001,8 @@
+ @code{ac_cv_f77_libs} or @code{ac_cv_fc_libs}, respectively.
+ @end defmac
+-@defmac AC_F77_DUMMY_MAIN (@ovar{action-if-found}, @dvar{action-if-not-found, @
+- AC_MSG_FAILURE})
+-@defmacx AC_FC_DUMMY_MAIN (@ovar{action-if-found}, @dvar{action-if-not-found, @
+- AC_MSG_FAILURE})
++@defmac AC_F77_DUMMY_MAIN (@ovar{action-if-found}, @dvar{action-if-not-found, @AC_MSG_FAILURE})
++@defmacx AC_FC_DUMMY_MAIN (@ovar{action-if-found}, @dvar{action-if-not-found, @AC_MSG_FAILURE})
+ @acindex{F77_DUMMY_MAIN}
+ @cvindex F77_DUMMY_MAIN
+ @acindex{FC_DUMMY_MAIN}
+@@ -8201,10 +8187,8 @@
+ to call Fortran routines from some language other than C/C++.
+ @end defmac
--@node autoheader Invocation, Autoheader Macros, Header Templates, Configuration Headers
-+@node autoheader, Autoheader Macros, Header Templates, Configuration Headers
- @subsection Using @code{autoheader} to Create @file{config.h.in}
- @cindex @code{autoheader}
+-@defmac AC_FC_SRCEXT (@var{ext}, @ovar{action-if-success}, @
+- @dvar{action-if-failure, AC_MSG_FAILURE})
+-@defmacx AC_FC_PP_SRCEXT (@var{ext}, @ovar{action-if-success}, @
+- @dvar{action-if-failure, AC_MSG_FAILURE})
++@defmac AC_FC_SRCEXT (@var{ext}, @ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
++@defmacx AC_FC_PP_SRCEXT (@var{ext}, @ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
+ @acindex{FC_SRCEXT}
+ @acindex{FC_PP_SRCEXT}
+ @caindex fc_srcext_@var{ext}
+@@ -8267,8 +8251,7 @@
+ @code{ac_cv_fc_pp_srcext_@var{ext}} variables, respectively.
+ @end defmac
-@@ -2405,7 +2399,7 @@
+-@defmac AC_FC_PP_DEFINE (@ovar{action-if-success}, @dvar{action-if-failure, @
+- AC_MSG_FAILURE})
++@defmac AC_FC_PP_DEFINE (@ovar{action-if-success}, @dvar{action-if-failure, @AC_MSG_FAILURE})
+ @acindex{FC_PP_DEFINE}
+ @caindex fc_pp_define
+@@ -8286,8 +8269,7 @@
+ variable.
+ @end defmac
+-@defmac AC_FC_FREEFORM (@ovar{action-if-success}, @dvar{action-if-failure, @
+- AC_MSG_FAILURE})
++@defmac AC_FC_FREEFORM (@ovar{action-if-success}, @dvar{action-if-failure, @AC_MSG_FAILURE})
+ @acindex{FC_FREEFORM}
+ @caindex fc_freeform
--@node Autoheader Macros, , autoheader Invocation, Configuration Headers
-+@node Autoheader Macros, , autoheader, Configuration Headers
- @subsection Autoheader Macros
+@@ -8313,8 +8295,7 @@
+ the @code{ac_cv_fc_freeform} variable.
+ @end defmac
- @code{autoheader} scans @file{configure.ac} and figures out which C
-@@ -7854,7 +7848,7 @@
+-@defmac AC_FC_FIXEDFORM (@ovar{action-if-success}, @dvar{action-if-failure, @
+- AC_MSG_FAILURE})
++@defmac AC_FC_FIXEDFORM (@ovar{action-if-success}, @dvar{action-if-failure, @AC_MSG_FAILURE})
+ @acindex{FC_FIXEDFORM}
+ @caindex fc_fixedform
- When the user runs @samp{autoconf -W error}, warnings from
- @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
--@ref{autoconf Invocation}.
-+@ref{autoconf}.
+@@ -8375,10 +8356,8 @@
+ variable.
+ @end defmac
- @node Dependencies Between Macros, Obsoleting Macros, Reporting Messages, Writing Macros
- @section Dependencies Between Macros
-@@ -8892,7 +8886,7 @@
+-@defmac AC_F77_IMPLICIT_NONE (@ovar{action-if-success}, @
+- @dvar{action-if-failure, AC_MSG_FAILURE})
+-@defmacx AC_FC_IMPLICIT_NONE (@ovar{action-if-success}, @
+- @dvar{action-if-failure, AC_MSG_FAILURE})
++@defmac AC_F77_IMPLICIT_NONE (@ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
++@defmacx AC_FC_IMPLICIT_NONE (@ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
+ @acindex{F77_IMPLICIT_NONE}
+ @acindex{FC_IMPLICIT_NONE}
+ @caindex f77_implicit_none
+@@ -9914,7 +9893,7 @@
+ files depend upon @command{bizarre-cc} being the C compiler. If
+ for some reason the user runs @command{./configure} again, or if it is
+ run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
+-and @pxref{config.status Invocation}), then the configuration can be
++and @pxref{config.status}), then the configuration can be
+ inconsistent, composed of results depending upon two different
+ compilers.
+
+@@ -9967,7 +9946,7 @@
- @c ============================================== Running configure Scripts.
+ @item
+ @var{variable} is kept during automatic reconfiguration
+-(@pxref{config.status Invocation}) as if it had been passed as a command
++(@pxref{config.status}) as if it had been passed as a command
+ line argument, including when no cache is used:
--@node Running configure scripts, config.status Invocation, Site Configuration, Top
-+@node Running configure scripts, config.status, Site Configuration, Top
- @chapter Running @code{configure} Scripts
- @cindex @code{configure}
+ @example
+@@ -11113,11 +11092,11 @@
+ It supports M4 extensions designed for use in tools like Autoconf.
-@@ -8910,7 +8904,7 @@
- * System Type:: Specifying the system type
- * Sharing Defaults:: Setting site-wide defaults for @code{configure}
- * Environment Variables:: Defining environment variables.
--* configure Invocation:: Changing how @code{configure} runs
-+* configure:: Changing how @code{configure} runs
+ @menu
+-* autom4te Invocation:: A GNU M4 wrapper
++* autom4te:: A GNU M4 wrapper
+ * Customizing autom4te:: Customizing the Autoconf package
@end menu
- @include install.texi
-@@ -8918,7 +8912,7 @@
+-@node autom4te Invocation
++@node autom4te
+ @subsection Invoking @command{autom4te}
+
+ The command line arguments are modeled after M4's:
+@@ -11376,7 +11355,7 @@
+ not.
+ @end table
+
+-@xref{autoconf Invocation}, for examples of trace uses.
++@xref{autoconf}, for examples of trace uses.
+
+ @item --preselect=@var{macro}
+ @itemx -p @var{macro}
+@@ -11464,8 +11443,8 @@
+ wrapped in between a @samp{begin-language: "@var{language}"},
+ @samp{end-language: "@var{language}"} pair.
+
+-Customizing a language stands for appending options (@pxref{autom4te
+-Invocation}) to the current definition of the language. Options, and
++Customizing a language stands for appending options (@pxref{autom4te})
++to the current definition of the language. Options, and
+ more generally arguments, are introduced by @samp{args:
+ @var{arguments}}. You may use the traditional shell syntax to quote the
+ @var{arguments}.
+@@ -13793,8 +13772,7 @@
+ undefined if expansion of an indirect variable does not result in a
+ literal variable name.
+
+-@defmac AS_LITERAL_IF (@var{expression}, @ovar{if-literal}, @ovar{if-not}, @
+- @dvar{if-simple-ref, @var{if-not}})
++@defmac AS_LITERAL_IF (@var{expression}, @ovar{if-literal}, @ovar{if-not}, @@dvar{if-simple-ref, @var{if-not}})
+ @defmacx AS_LITERAL_WORD_IF (@var{expression}, @ovar{if-literal}, @
+ @ovar{if-not}, @dvar{if-simple-ref, @var{if-not}})
+ @asindex{LITERAL_IF}
+@@ -14446,7 +14424,7 @@
+
+ When the user runs @samp{autoconf -W error}, warnings from
+ @code{m4_warn} (including those issued through @code{AC_DIAGNOSE} and
+-@code{AC_WARNING}) are reported as errors, see @ref{autoconf Invocation}.
++@code{AC_WARNING}) are reported as errors, see @ref{autoconf}.
- @c ============================================== Recreating a Configuration
+ @node Dependencies Between Macros
+ @section Dependencies Between Macros
+@@ -22640,16 +22618,16 @@
+ * System Type:: Specifying the system type
+ * Sharing Defaults:: Setting site-wide defaults for @command{configure}
+ * Defining Variables:: Specifying the compiler etc.
+-* configure Invocation:: Changing how @command{configure} runs
++* configure:: Changing how @command{configure} runs
+ @end menu
--@node config.status Invocation, Obsolete Constructs, Running configure scripts, Top
-+@node config.status, Obsolete Constructs, Running configure scripts, Top
- @chapter Recreating a Configuration
- @cindex @code{config.status}
+ @set autoconf
+ @include install.texi
-@@ -9037,7 +9031,7 @@
- @c =================================================== Obsolete Constructs
+-@c ============================================== config.status Invocation
++@c ============================================== config.status
--@node Obsolete Constructs, Questions, config.status Invocation, Top
-+@node Obsolete Constructs, Questions, config.status, Top
- @chapter Obsolete Constructs
+-@node config.status Invocation
++@node config.status
+ @chapter config.status Invocation
+ @cindex @command{config.status}
- Autoconf changes, and throughout the years some constructs are obsoleted.
-@@ -9051,7 +9045,7 @@
+@@ -22818,7 +22796,7 @@
@menu
- * Obsolete config.status Use:: Different calling convention
- * acconfig.h:: Additional entries in @file{config.h.in}
+ * Obsolete config.status Use:: Obsolete convention for @command{config.status}
+ * acconfig Header:: Additional entries in @file{config.h.in}
-* autoupdate Invocation:: Automatic update of @file{configure.ac}
+* autoupdate:: Automatic update of @file{configure.ac}
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
- @end menu
-@@ -9060,7 +9054,7 @@
+ * Autoconf 2.13:: Some fresher tips
+@@ -22828,7 +22806,7 @@
@section Obsolete @file{config.status} Invocation
@file{config.status} now supports arguments to specify the files to
--instantiate, see @ref{config.status Invocation}, for more details.
-+instantiate, see @ref{config.status}, for more details.
+-instantiate; see @ref{config.status Invocation}, for more details.
++instantiate; see @ref{config.status}, for more details.
Before, environment variables had to be used.
@defvar CONFIG_COMMANDS
-@@ -9091,7 +9085,7 @@
+@@ -22859,7 +22837,7 @@
@file{config.status} ignores this variable.
@end defvar
would be:
@example
-@@ -9114,7 +9108,7 @@
- for @code{CONFIG_COMMANDS} etc.)
-
-
--@node acconfig.h, autoupdate Invocation, Obsolete config.status Use, Obsolete Constructs
-+@node acconfig.h, autoupdate, Obsolete config.status Use, Obsolete Constructs
- @section @file{acconfig.h}
-
- @cindex @file{acconfig.h}
-@@ -9165,7 +9159,7 @@
+@@ -22933,7 +22911,7 @@
self-contained, and should not depend upon @file{acconfig.h} etc.
--@node autoupdate Invocation, Obsolete Macros, acconfig.h, Obsolete Constructs
-+@node autoupdate, Obsolete Macros, acconfig.h, Obsolete Constructs
- @section Using @code{autoupdate} to Modernize @file{configure.ac}
- @cindex @code{autoupdate}
-
-@@ -9223,7 +9217,7 @@
- instead of in the current directory.
- @end table
-
--@node Obsolete Macros, Autoconf 1, autoupdate Invocation, Obsolete Constructs
-+@node Obsolete Macros, Autoconf 1, autoupdate, Obsolete Constructs
- @section Obsolete Macros
+-@node autoupdate Invocation
++@node autoupdate
+ @section Using @command{autoupdate} to Modernize @file{configure.ac}
+ @cindex @command{autoupdate}
- Several macros are obsoleted in Autoconf, for various reasons (typically
-@@ -9987,7 +9981,7 @@
+@@ -24111,7 +24089,7 @@
If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
in a particular package's source directory), you must rename it to
+@file{acsite.m4}. @xref{autoconf}.
If you distribute @file{install.sh} with your package, rename it to
- @file{install-sh} so @code{make} builtin rules won't inadvertently
-@@ -10042,7 +10036,7 @@
+ @file{install-sh} so @command{make} builtin rules don't inadvertently
+@@ -24166,7 +24144,7 @@
the documentation for them. @xref{Obsolete Macros}, for a table showing the
- new names for the old macros. Use the @code{autoupdate} program to
+ new names for the old macros. Use the @command{autoupdate} program to
convert your @file{configure.ac} to using the new macro names.
-@xref{autoupdate Invocation}.
+@xref{autoupdate}.
Some macros have been superseded by similar ones that do the job better,
but are not call-compatible. If you get warnings about calling obsolete
-diff -Nur autoconf-2.50.orig/doc/install.texi autoconf-2.50/doc/install.texi
---- autoconf-2.50.orig/doc/install.texi Mon Mar 19 15:28:42 2001
-+++ autoconf-2.50/doc/install.texi Fri Jun 15 15:26:39 2001
-@@ -215,8 +215,8 @@
- overridden in the site shell script).
+@@ -24703,7 +24681,7 @@
+ @menu
+ * Using an Autotest Test Suite:: Autotest and the user
+ * Writing Testsuites:: Autotest macros
+-* testsuite Invocation:: Running @command{testsuite} scripts
++* testsuite:: Running @command{testsuite} scripts
+ * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
+ @end menu
+
+@@ -24765,7 +24743,7 @@
+ @itemize @bullet
+ @item a debugging script named @file{run} which reruns the test in
+-@dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation
++@dfn{debug mode} (@pxref{testsuite}). The automatic generation
+ of debugging scripts has the purpose of easing the chase for bugs.
+
+ @item all the files created with @code{AT_DATA}
+@@ -25125,8 +25103,7 @@
+ be a single shell word that expands into a single file name.
+ @end defmac
+
+-@defmac AT_CHECK (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @
+- @ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
++@defmac AT_CHECK (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @@ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
+ @defmacx AT_CHECK_UNQUOTED (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @
+ @ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
+ @atindex{CHECK}
+@@ -25270,7 +25247,7 @@
+ @end defmac
+
+
+-@node testsuite Invocation
++@node testsuite
+ @section Running @command{testsuite} Scripts
+ @cindex @command{testsuite}
+
+@@ -25465,7 +25442,7 @@
+ An Autotest test suite is to be configured in @var{directory}. This
+ macro causes @file{@var{directory}/atconfig} to be created by
+ @command{config.status} and sets the default @code{AUTOTEST_PATH} to
+-@var{test-path} (@pxref{testsuite Invocation}).
++@var{test-path} (@pxref{testsuite}).
+ @end defmac
+
+ @item
+@@ -25858,7 +25835,7 @@
+ which can be a long process for complex @file{configure.ac}.
+
+ This is why all these tools, instead of running directly M4, invoke
+-@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
++@command{autom4te} (@pxref{autom4te}) which, while answering to
+ a specific demand, stores additional information in
+ @file{autom4te.cache} for future runs. For instance, if you run
+ @command{autoconf}, behind the scenes, @command{autom4te} also
+--- autoconf-2.62/doc/install.texi.orig 2007-12-08 14:58:52.000000000 +0100
++++ autoconf-2.62/doc/install.texi 2008-04-16 20:34:45.697178391 +0200
+@@ -239,7 +239,7 @@
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
+ @end example
-@node configure Invocation
--@section @code{configure} Invocation
+@node configure
-+@section @code{configure}
+ @section @command{configure} Invocation
+
+ @command{configure} recognizes the following options to control how it
+--- autoconf-2.62/doc/standards.texi.orig 2008-04-04 15:16:45.000000000 +0200
++++ autoconf-2.62/doc/standards.texi 2008-04-16 20:39:27.317224488 +0200
+@@ -6,9 +6,9 @@
+ @set lastupdate February 23, 2008
+ @c %**end of header
+
+-@dircategory GNU organization
++@dircategory Miscellaneous:
+ @direntry
+-* Standards: (standards). GNU coding standards.
++* Standards: (standards). GNU coding standards
+ @end direntry
- @code{configure} recognizes the following options to control how it
- operates.
+ @c @setchapternewpage odd
projects / packages / autoconf.git / blobdiff