---- autoconf-2.52/doc/autoconf.texi.orig Tue Jul 17 18:34:55 2001
-+++ autoconf-2.52/doc/autoconf.texi Wed Jul 18 21:44:32 2001
-@@ -27,25 +27,20 @@
- @end ifnothtml
+diff -Nur autoconf-2.58.orig/doc/autoconf.texi autoconf-2.58/doc/autoconf.texi
+--- autoconf-2.58.orig/doc/autoconf.texi 2003-11-05 19:26:28.000000000 +0100
++++ autoconf-2.58/doc/autoconf.texi 2003-11-05 19:29:40.054405552 +0100
+@@ -208,29 +208,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
+-* ifnames: (autoconf)ifnames Invocation. Listing conditionals in source.
-* autoconf: (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
-@@ -146,7 +141,7 @@
+ @titlepage
+@@ -270,7 +260,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
-@@ -168,10 +163,10 @@
- Making @code{configure} Scripts
+ * Using Autotest:: Creating portable test suites
+ * FAQ:: Frequent Autoconf Questions, with answers
+@@ -290,10 +280,10 @@
+ Making @command{configure} Scripts
* Writing configure.ac:: 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}
-@@ -203,7 +198,7 @@
+@@ -326,7 +316,7 @@
Configuration Header Files
* Header Templates:: Input for the configuration headers
* Autoheader Macros:: How to specify CPP templates
Existing Tests
-@@ -369,13 +364,13 @@
+@@ -437,7 +427,7 @@
+
+ Using @command{autom4te}
+
+-* autom4te Invocation:: A @acronym{GNU} M4 wrapper
++* autom4te:: A @acronym{GNU} M4 wrapper
+ * Customizing autom4te:: Customizing the Autoconf package
+
+ Programming in M4sugar
+@@ -505,13 +495,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 Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
-@@ -680,7 +675,7 @@
+@@ -536,7 +526,7 @@
+
+ * Using an Autotest Test Suite:: Autotest and the user
+ * Writing testsuite.at:: Autotest macros
+-* testsuite Invocation:: Running @command{testsuite} scripts
++* testsuite:: Running @command{testsuite} scripts
+ * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
+
+ Using an Autotest Test Suite
+@@ -843,7 +833,7 @@
@item
a shell script called @file{config.status} that, when run, will recreate
@item
an optional shell script normally called @file{config.cache}
-@@ -740,13 +735,13 @@
+@@ -903,10 +893,10 @@
@menu
* Writing configure.ac:: 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
-@@ -759,7 +754,7 @@
+ @node Writing configure.ac
+@@ -922,7 +912,7 @@
or specialized features, @file{configure.ac} might need to contain some
hand-crafted shell commands; see @ref{Portable Shell}. The
- @code{autoscan} program can give you a good start in writing
+ @command{autoscan} program can give you a good start in writing
-@file{configure.ac} (@pxref{autoscan Invocation}, for more information).
+@file{configure.ac} (@pxref{autoscan}, for more information).
Previous versions of Autoconf promoted the name @file{configure.in},
- which is somewhat ambiguous (the tool needed to produce this file is not
-@@ -987,7 +982,7 @@
+ which is somewhat ambiguous (the tool needed to process this file is not
+@@ -1150,7 +1140,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}
-@@ -1009,7 +1004,7 @@
+@@ -1172,7 +1162,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
information about a program that can help with that job).
When using @command{autoscan} to maintain a @file{configure.ac}, simply
-@@ -1051,7 +1046,7 @@
- plays with different versions of Autoconf simultaneously.
+@@ -1211,7 +1201,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}
-@@ -1060,8 +1055,7 @@
+@@ -1220,8 +1210,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
-@@ -1083,7 +1077,7 @@
+@@ -1243,7 +1232,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}
-
-@@ -1346,7 +1340,7 @@
+-@node autoconf Invocation
++@node autoconf
+ @section Using @command{autoconf} to Create @command{configure}
+ @cindex @command{autoconf}
+
+@@ -1337,8 +1326,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}]
+@@ -1350,7 +1338,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
+@@ -1424,7 +1412,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}
+-@node autoreconf Invocation
++@node autoreconf
+ @section Using @command{autoreconf} to Update @command{configure} Scripts
+ @cindex @command{autoreconf}
-@@ -1568,8 +1562,8 @@
- source directory; @code{configure} checks for this file's existence to
+@@ -1709,8 +1697,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
-@@ -1755,7 +1749,7 @@
+@@ -1898,7 +1886,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
for more details.
The @var{inputs} may be absolute or relative filenames. In the latter
-@@ -2223,7 +2217,7 @@
+@@ -2521,7 +2509,7 @@
@file{config.h} is considered up to date. @xref{Output}, for more
information about @code{AC_OUTPUT}.
+@xref{config.status}, for more examples of handling
configuration-related dependencies.
- @node Configuration Headers, Configuration Commands, Makefile Substitutions, Setup
-@@ -2284,11 +2278,11 @@
+ @node Configuration Headers
+@@ -2583,7 +2571,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}
-@@ -2335,10 +2329,10 @@
- @samp{#undef} is strongly discouraged.
+@@ -2637,10 +2625,10 @@
+ comments in preprocessor macros has never been a good idea.
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}.
--@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}
-@@ -2443,7 +2437,7 @@
+-@node autoheader Invocation
++@node autoheader
+ @subsection Using @command{autoheader} to Create @file{config.h.in}
+ @cindex @command{autoheader}
-
-
--@node Autoheader Macros, , autoheader Invocation, Configuration Headers
-+@node Autoheader Macros, , autoheader, Configuration Headers
- @subsection Autoheader Macros
-
- @code{autoheader} scans @file{configure.ac} and figures out which C
-@@ -5621,7 +5615,7 @@
+@@ -6948,7 +6936,7 @@
files will depend upon @command{bizarre-cc} being the C compiler. If
- for some reason the user runs @command{/configure} again, or if it is
+ 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.
-@@ -5665,7 +5659,7 @@
+@@ -7000,7 +6988,7 @@
@item
@var{variable} is kept during automatic reconfiguration
line argument, including when no cache is used:
@example
-@@ -6670,7 +6664,7 @@
+@@ -7871,11 +7859,11 @@
+ It supports M4 extensions designed for use in tools like Autoconf.
+
+ @menu
+-* autom4te Invocation:: A @acronym{GNU} M4 wrapper
++* autom4te:: A @acronym{GNU} M4 wrapper
+ * Customizing autom4te:: Customizing the Autoconf package
+ @end menu
+
+-@node autom4te Invocation
++@node autom4te
+ @subsection Invoking @command{autom4te}
+
+ The command line arguments are modeled after M4's:
+@@ -8158,7 +8146,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}
+@@ -8232,8 +8220,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}.
+@@ -8662,7 +8650,7 @@
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}.
- @node Dependencies Between Macros, Obsoleting Macros, Reporting Messages, Writing Autoconf Macros
+ @node Dependencies Between Macros
@section Dependencies Between Macros
-@@ -9445,7 +9439,7 @@
-
- @c ============================================== Running configure Scripts.
-
--@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}
-
-@@ -9463,7 +9457,7 @@
+@@ -12729,7 +12717,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
+ * 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
- @include install.texi
-@@ -9471,7 +9465,7 @@
+ @set autoconf
+@@ -12738,7 +12726,7 @@
@c ============================================== Recreating a Configuration
--@node config.status Invocation, Obsolete Constructs, Running configure scripts, Top
-+@node config.status, Obsolete Constructs, Running configure scripts, Top
+-@node config.status Invocation
++@node config.status
@chapter Recreating a Configuration
- @cindex @code{config.status}
-
-@@ -9590,7 +9584,7 @@
-
- @c =================================================== Obsolete Constructs
+ @cindex @command{config.status}
--@node Obsolete Constructs, Questions, config.status Invocation, Top
-+@node Obsolete Constructs, Questions, config.status, Top
- @chapter Obsolete Constructs
-
- Autoconf changes, and throughout the years some constructs are obsoleted.
-@@ -9604,7 +9598,7 @@
+@@ -12878,7 +12866,7 @@
@menu
* Obsolete config.status Use:: Different calling convention
* acconfig.h:: Additional entries in @file{config.h.in}
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
-@@ -9614,7 +9608,7 @@
+@@ -12888,7 +12876,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
-@@ -9645,7 +9639,7 @@
+@@ -12919,7 +12907,7 @@
@file{config.status} ignores this variable.
@end defvar
would be:
@example
-@@ -9668,7 +9662,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}
-@@ -9719,7 +9713,7 @@
+@@ -12993,7 +12981,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}
-
-@@ -9777,7 +9771,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
-@@ -10572,7 +10566,7 @@
+@@ -13929,7 +13917,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
If you distribute @file{install.sh} with your package, rename it to
@file{install-sh} so @code{make} builtin rules won't inadvertently
-@@ -10627,7 +10621,7 @@
+@@ -13984,7 +13972,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
+@@ -14549,7 +14537,7 @@
+ @menu
+ * Using an Autotest Test Suite:: Autotest and the user
+ * Writing testsuite.at:: Autotest macros
+-* testsuite Invocation:: Running @command{testsuite} scripts
++* testsuite:: Running @command{testsuite} scripts
+ * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
+ @end menu
+
+@@ -14611,7 +14599,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}
+@@ -14833,7 +14821,7 @@
+ @end defmac
+
+
+-@node testsuite Invocation
++@node testsuite
+ @section Running @command{testsuite} Scripts
+ @cindex @command{testsuite}
+
+@@ -14976,7 +14964,7 @@
+ An Autotest test suite is to be configured in @var{directory}. This
+ macro requires the instantiation of @file{@var{directory}/atconfig} from
+ @file{@var{directory}/atconfig.in}, and sets the default
+-@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite Invocation}).
++@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite}).
+ @end defmac
+
+ @item
+@@ -15306,7 +15294,7 @@
+ which can be a very 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} will also
+diff -Nur autoconf-2.58.orig/doc/install.texi autoconf-2.58/doc/install.texi
+--- autoconf-2.58.orig/doc/install.texi 2002-08-27 10:28:06.000000000 +0200
++++ autoconf-2.58/doc/install.texi 2003-11-05 19:26:39.414866936 +0100
+@@ -225,7 +225,7 @@
+ overridden in the site shell script).
+
+
+-@node configure Invocation
++@node configure
+ @section @command{configure} Invocation
+
+ @command{configure} recognizes the following options to control how it
+diff -Nur autoconf-2.58.orig/doc/standards.texi autoconf-2.58/doc/standards.texi
+--- autoconf-2.58.orig/doc/standards.texi 2003-09-15 03:33:44.000000000 +0200
++++ autoconf-2.58/doc/standards.texi 2003-11-05 19:26:39.427864960 +0100
+@@ -6,9 +6,9 @@
+ @set lastupdate April 29, 2003
+ @c %**end of header
+
+-@dircategory GNU organization
++@dircategory Miscellaneous:
+ @direntry
+-* Standards: (standards). GNU coding standards.
++* Standards: (standards). GNU coding standards
+ @end direntry
+
+ @c @setchapternewpage odd
projects / packages / autoconf.git / blobdiff