--- 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
-
-
--@dircategory GNU admin
-+@dircategory Programming tools:
- @direntry
--* Autoconf: (autoconf). Create source code configuration scripts
-+* Autoconf: (autoconf). Create source code configuration scripts
- @end direntry
++++ autoconf-2.52/doc/autoconf.texi Wed Jul 18 23:56:19 2001
+@@ -34,18 +34,15 @@
@dircategory Individual utilities
@direntry
- Configuring a package
-* config.status: (autoconf)config.status Invocation.
- Recreating a configuration
-+* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac} writing
++* 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 @code{configure} scripts
++* autoreconf: (autoconf)autoreconf. Remaking multiple @code{configure}
++ scripts
+* configure: (autoconf)configure. Configuring a package
+* config.status: (autoconf)config.status.
+ Recreating a configuration
@end direntry
@ifinfo
-@@ -146,7 +141,7 @@
+@@ -146,7 +143,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
-* config.status Invocation:: Recreating a configuration
-+* config.status:: 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 @@
+@@ -168,10 +165,10 @@
Making @code{configure} Scripts
* Writing configure.ac:: What to put in an Autoconf input file
-* ifnames Invocation:: Listing the conditionals in source code
-* autoconf Invocation:: How to create configuration scripts
-* autoreconf Invocation:: Remaking multiple @code{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
++* 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
Writing @file{configure.ac}
-@@ -203,7 +198,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
-@@ -369,13 +364,13 @@
+@@ -369,7 +366,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
++* configure:: Changing how @code{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
-@@ -680,7 +675,7 @@
+@@ -680,7 +677,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 @@
+@@ -740,13 +737,13 @@
@menu
* Writing configure.ac:: What to put in an Autoconf input file
-* ifnames Invocation:: Listing the conditionals in source code
-* autoconf Invocation:: How to create configuration scripts
-* autoreconf Invocation:: Remaking multiple @code{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
++* 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
@end menu
-@node Writing configure.ac, autoscan Invocation, 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 @@
+@@ -759,7 +756,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
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 @@
+@@ -987,7 +984,7 @@
@end display
@section Using @code{autoscan} to Create @file{configure.ac}
@cindex @code{autoscan}
-@@ -1009,7 +1004,7 @@
+@@ -1009,7 +1006,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 @@
+@@ -1051,7 +1048,7 @@
plays with different versions of Autoconf simultaneously.
@end table
@section Using @code{ifnames} to List Conditionals
@cindex @code{ifnames}
-@@ -1060,8 +1055,7 @@
+@@ -1060,8 +1057,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
@code{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 @@
+@@ -1083,7 +1079,7 @@
Print the version number of Autoconf and exit.
@end table
@section Using @code{autoconf} to Create @code{configure}
@cindex @code{autoconf}
-@@ -1346,7 +1340,7 @@
+@@ -1346,7 +1342,7 @@
@end group
@end example
@section Using @code{autoreconf} to Update @code{configure} Scripts
@cindex @code{autoreconf}
-@@ -1568,8 +1562,8 @@
+@@ -1568,8 +1564,8 @@
source directory; @code{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
@end defmac
-@@ -1755,7 +1749,7 @@
+@@ -1755,7 +1751,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 @@
+@@ -2223,7 +2219,7 @@
@file{config.h} is considered up to date. @xref{Output}, for more
information about @code{AC_OUTPUT}.
configuration-related dependencies.
@node Configuration Headers, Configuration Commands, Makefile Substitutions, Setup
-@@ -2284,11 +2278,11 @@
-
- @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
-
--@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.
-
- 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}.
-
-
--@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 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 @@
+@@ -5621,7 +5617,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},
inconsistent, composed of results depending upon two different
compilers.
-@@ -5665,7 +5659,7 @@
+@@ -5665,7 +5661,7 @@
@item
@var{variable} is kept during automatic reconfiguration
line argument, including when no cache is used:
@example
-@@ -6670,7 +6664,7 @@
+@@ -6670,7 +6666,7 @@
When the user runs @samp{autoconf -W error}, warnings from
@code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
@node Dependencies Between Macros, Obsoleting Macros, Reporting Messages, Writing Autoconf Macros
@section Dependencies Between Macros
-@@ -9445,7 +9439,7 @@
+@@ -9445,7 +9441,7 @@
@c ============================================== Running configure Scripts.
@chapter Running @code{configure} Scripts
@cindex @code{configure}
-@@ -9463,7 +9457,7 @@
+@@ -9463,7 +9459,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
++* configure:: Changing how @code{configure} runs
@end menu
@include install.texi
-@@ -9471,7 +9465,7 @@
+@@ -9471,7 +9467,7 @@
@c ============================================== Recreating a Configuration
@chapter Recreating a Configuration
@cindex @code{config.status}
-@@ -9590,7 +9584,7 @@
+@@ -9590,7 +9586,7 @@
@c =================================================== Obsolete Constructs
@chapter Obsolete Constructs
Autoconf changes, and throughout the years some constructs are obsoleted.
-@@ -9604,7 +9598,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
-@@ -9614,7 +9608,7 @@
+@@ -9614,7 +9610,7 @@
@section Obsolete @file{config.status} Invocation
@file{config.status} now supports arguments to specify the files to
Before, environment variables had to be used.
@defvar CONFIG_COMMANDS
-@@ -9645,7 +9639,7 @@
+@@ -9645,7 +9641,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 @@
- 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
-
- Several macros are obsoleted in Autoconf, for various reasons (typically
-@@ -10572,7 +10566,7 @@
+@@ -10572,7 +10568,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 @@
- the documentation for them. @xref{Obsolete Macros}, for a table showing the
- new names for the old macros. Use the @code{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
+--- autoconf-2.52/doc/install.texi.orig Tue Jul 17 18:34:55 2001
++++ autoconf-2.52/doc/install.texi Wed Jul 18 23:53:41 2001
+@@ -215,8 +215,8 @@
+ overridden in the site shell script).
+
+
+-@node configure Invocation
+-@section @code{configure} Invocation
++@node configure
++@section @code{configure}
+
+ @code{configure} recognizes the following options to control how it
+ operates.
projects / packages / autoconf.git / commitdiff