+++ /dev/null
-diff -Nur autoconf-2.53.orig/doc/autoconf.texi autoconf-2.53/doc/autoconf.texi
---- autoconf-2.53.orig/doc/autoconf.texi Fri Mar 8 13:57:41 2002
-+++ autoconf-2.53/doc/autoconf.texi Sat Mar 16 12:31:46 2002
-@@ -32,27 +32,16 @@
- @end ifnothtml
-
-
--@dircategory GNU admin
-+@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.
-- How to create configuration scripts
--* autoreconf: (autoconf)autoreconf Invocation.
-- Remaking multiple @command{configure} scripts
--* configure: (autoconf)configure Invocation.
-- Configuring a package
--* config.status: (autoconf)config.status Invocation.
-- Recreating a configuration
--* 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
-+* autoconf: (autoconf)autoconf. How to create configuration scripts
-+* autoreconf: (autoconf)autoreconf. Remaking multiple @command{configure} scripts
-+* configure: (autoconf)configure. Configuring a package
-+* config.status: (autoconf)config.status. Recreating a configuration
-+* testsuite: (autoconf)testsuite. Running an Autotest test suite
- @end direntry
-
- @ifinfo
-@@ -162,7 +151,7 @@
- * Manual Configuration:: Selecting features that can't be guessed
- * 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
- * Using Autotest:: Creating portable test suites
- * Questions:: Questions about Autoconf, with answers
-@@ -182,10 +171,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 @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 @command{configure} scripts
-
- Writing @file{configure.ac}
-
-@@ -218,7 +207,7 @@
- Configuration Header Files
-
- * Header Templates:: Input for the configuration headers
--* autoheader Invocation:: How to create configuration templates
-+* autoheader:: How to create configuration templates
- * Autoheader Macros:: How to specify CPP templates
-
- Existing Tests
-@@ -389,13 +378,13 @@
- * 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
-
- Obsolete Constructs
-
- * Obsolete config.status Use:: Different calling convention
- * acconfig.h:: 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
-@@ -419,7 +408,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
-@@ -729,7 +718,7 @@
-
- @item
- a shell script called @file{config.status} that, when run, will recreate
--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}
-@@ -789,10 +778,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 @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 @command{configure} scripts
- @end menu
-
- @node Writing configure.ac
-@@ -808,7 +797,7 @@
- or specialized features, @file{configure.ac} might need to contain some
- hand-crafted shell commands; see @ref{Portable Shell}. The
- @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
-@@ -1036,7 +1025,7 @@
- @end display
-
-
--@node autoscan Invocation
-+@node autoscan
- @section Using @command{autoscan} to Create @file{configure.ac}
- @cindex @command{autoscan}
-
-@@ -1058,7 +1047,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).
-
- When using @command{autoscan} to maintain a @file{configure.ac}, simply
-@@ -1094,7 +1083,7 @@
- accumulate. Directories are browsed from last to first.
- @end table
-
--@node ifnames Invocation
-+@node ifnames
- @section Using @command{ifnames} to List Conditionals
- @cindex @command{ifnames}
-
-@@ -1103,8 +1092,7 @@
- preprocessor conditionals. If a package has already been set up to have
- 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 @command{autoscan} (@pxref{autoscan}).
-
- @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
-@@ -1126,7 +1114,7 @@
- Print the version number of Autoconf and exit.
- @end table
-
--@node autoconf Invocation
-+@node autoconf
- @section Using @command{autoconf} to Create @command{configure}
- @cindex @command{autoconf}
-
-@@ -1383,7 +1371,7 @@
- @end group
- @end example
-
--@node autoreconf Invocation
-+@node autoreconf
- @section Using @command{autoreconf} to Update @command{configure} Scripts
- @cindex @command{autoreconf}
-
-@@ -1611,8 +1599,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
--Invocation}, for more information.
-+with @option{--srcdir}; this is a safety check. @xref{configure},
-+for more information.
- @end defmac
-
-
-@@ -1778,7 +1766,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 Invocation},
-+interface of @file{./config.status}, see @ref{config.status},
- for more details.
-
- The @var{inputs} may be absolute or relative filenames. In the latter
-@@ -2350,7 +2338,7 @@
- @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
-@@ -2411,7 +2399,7 @@
-
- @menu
- * Header Templates:: Input for the configuration headers
--* autoheader Invocation:: How to create configuration templates
-+* autoheader:: How to create configuration templates
- * Autoheader Macros:: How to specify CPP templates
- @end menu
-
-@@ -2462,10 +2450,10 @@
- @samp{#undef} is strongly discouraged.
-
- Since it is a tedious task to keep a template header up to date, you may
--use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
-+use @command{autoheader} to generate it, see @ref{autoheader}.
-
-
--@node autoheader Invocation
-+@node autoheader
- @subsection Using @command{autoheader} to Create @file{config.h.in}
- @cindex @command{autoheader}
-
-@@ -5991,7 +5979,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
- 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.
-
-@@ -6035,7 +6023,7 @@
-
- @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:
-
- @example
-@@ -7162,7 +7150,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}
-@@ -7575,7 +7563,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
- @section Dependencies Between Macros
-@@ -10555,7 +10543,7 @@
- * 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
-
- @set autoconf
-@@ -10564,7 +10552,7 @@
-
- @c ============================================== Recreating a Configuration
-
--@node config.status Invocation
-+@node config.status
- @chapter Recreating a Configuration
- @cindex @command{config.status}
-
-@@ -10698,7 +10686,7 @@
- @menu
- * Obsolete config.status Use:: Different calling convention
- * acconfig.h:: 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
-@@ -10708,7 +10696,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.
- Before, environment variables had to be used.
-
- @defvar CONFIG_COMMANDS
-@@ -10739,7 +10727,7 @@
- @file{config.status} ignores this variable.
- @end defvar
-
--In @ref{config.status Invocation}, using this old interface, the example
-+In @ref{config.status}, using this old interface, the example
- would be:
-
- @example
-@@ -10813,7 +10801,7 @@
- self-contained, and should not depend upon @file{acconfig.h} etc.
-
-
--@node autoupdate Invocation
-+@node autoupdate
- @section Using @command{autoupdate} to Modernize @file{configure.ac}
- @cindex @command{autoupdate}
-
-@@ -11660,7 +11648,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 Invocation}.
-+@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
-@@ -11715,7 +11703,7 @@
- the documentation for them. @xref{Obsolete Macros}, for a table showing the
- 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
-@@ -12214,7 +12202,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
-
-@@ -12476,7 +12464,7 @@
- @end defmac
-
-
--@node testsuite Invocation
-+@node testsuite
- @section Running @command{testsuite} Scripts
- @cindex @command{testsuite}
-
-diff -Nur autoconf-2.53.orig/doc/install.texi autoconf-2.53/doc/install.texi
---- autoconf-2.53.orig/doc/install.texi Mon Mar 4 16:11:11 2002
-+++ autoconf-2.53/doc/install.texi Sat Mar 16 12:32:45 2002
-@@ -224,7 +224,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.53.orig/doc/standards.texi autoconf-2.53/doc/standards.texi
---- autoconf-2.53.orig/doc/standards.texi Fri Nov 2 17:29:03 2001
-+++ autoconf-2.53/doc/standards.texi Sat Mar 16 12:34:09 2002
-@@ -8,9 +8,10 @@
-
- @ifinfo
- @format
--START-INFO-DIR-ENTRY
--* Standards: (standards). GNU coding standards.
--END-INFO-DIR-ENTRY
-+@dircategory Miscellaneous:
-+@direntry
-+* Standards: (standards). GNU coding standards.
-+@end direntry
- @end format
- @end ifinfo
-
projects / packages / autoconf.git / commitdiff