--- autoconf.texi.~1.739.~ 2003-05-24 08:26:59.000000000 +1000 +++ autoconf.texi 2003-05-24 08:27:15.000000000 +1000 @@ -221,7 +221,7 @@ * 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. +* config.status: (autoconf)config status Invocation. Recreating configurations. * testsuite: (autoconf)testsuite Invocation. Running an Autotest test suite. @end direntry @@ -262,7 +262,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 Invocation:: Recreating a configuration * Obsolete Constructs:: Kept for backward compatibility * Using Autotest:: Creating portable test suites * FAQ:: Frequent Autoconf Questions, with answers @@ -281,7 +281,7 @@ Making @command{configure} Scripts -* Writing configure.ac:: What to put in an Autoconf input file +* Writing configure:: 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 @@ -291,7 +291,7 @@ * Shell Script Compiler:: Autoconf as solution of a problem * Autoconf Language:: Programming in Autoconf -* configure.ac Layout:: Standard organization of @file{configure.ac} +* configure Layout:: Standard organization of @file{configure.ac} Initialization and Output Files @@ -500,12 +500,12 @@ Obsolete Constructs -* Obsolete config.status Use:: Different calling convention -* acconfig.h:: Additional entries in @file{config.h.in} +* Obsolete config status Use:: Different calling convention +* acconfig header:: Additional entries in @file{config.h.in} * autoupdate Invocation:: Automatic update of @file{configure.ac} * Obsolete Macros:: Backward compatibility macros * Autoconf 1:: Tips for upgrading your files -* Autoconf 2.13:: Some fresher tips +* Autoconf 213:: Some fresher tips Upgrading From Version 1 @@ -526,7 +526,7 @@ Generating Test Suites with Autotest * Using an Autotest Test Suite:: Autotest and the user -* Writing testsuite.at:: Autotest macros +* Writing testsuite:: Autotest macros * testsuite Invocation:: Running @command{testsuite} scripts * Making testsuite Scripts:: Using autom4te to create @command{testsuite} @@ -542,7 +542,7 @@ * Bootstrapping:: Autoconf and @acronym{GNU} M4 require each other? * Why Not Imake:: Why @acronym{GNU} uses @command{configure} instead of Imake * Defining Directories:: Passing @code{datadir} to program -* autom4te.cache:: What is it? Can I remove it? +* autom4te cache:: What is it? Can I remove it? * Present But Cannot Be Compiled:: Compiler and Preprocessor Disagree History of Autoconf @@ -834,7 +834,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 Invocation}); @item an optional shell script normally called @file{config.cache} @@ -893,14 +893,14 @@ @end example @menu -* Writing configure.ac:: What to put in an Autoconf input file +* Writing configure:: 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 @end menu address@hidden Writing configure.ac address@hidden Writing configure @section Writing @file{configure.ac} To produce a @command{configure} script for a software package, create a @@ -925,7 +925,7 @@ @menu * Shell Script Compiler:: Autoconf as solution of a problem * Autoconf Language:: Programming in Autoconf -* configure.ac Layout:: Standard organization of @file{configure.ac} +* configure Layout:: Standard organization of @file{configure.ac} @end menu @node Shell Script Compiler @@ -1104,7 +1104,7 @@ # Process this file with autoconf to produce a configure script. @end example address@hidden configure.ac Layout address@hidden configure Layout @subsection Standard @file{configure.ac} Layout The order in which @file{configure.ac} calls the Autoconf macros is not @@ -1868,7 +1868,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 Invocation}, for more details. The @var{inputs} may be absolute or relative filenames. In the latter @@ -2482,7 +2482,7 @@ @file{config.h} is considered up to date. @xref{Output}, for more information about @code{AC_OUTPUT}. address@hidden Invocation}, for more examples of handling address@hidden status Invocation}, for more examples of handling configuration-related dependencies. @node Configuration Headers @@ -6612,7 +6612,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 Invocation}), then the configuration can be inconsistent, composed of results depending upon two different compilers. @@ -6664,7 +6664,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 Invocation}) as if it had been passed as a command line argument, including when no cache is used: @example @@ -12268,7 +12268,7 @@ @c ============================================== Recreating a Configuration address@hidden config.status Invocation address@hidden config status Invocation @chapter Recreating a Configuration @cindex @command{config.status} @@ -12388,7 +12388,7 @@ @end example The calling convention of @file{config.status} has changed; see address@hidden config.status Use}, for details. address@hidden config status Use}, for details. @c =================================================== Obsolete Constructs @@ -12406,19 +12406,19 @@ understanding how to move to more modern constructs. @menu -* Obsolete config.status Use:: Different calling convention -* acconfig.h:: Additional entries in @file{config.h.in} +* Obsolete config status Use:: Different calling convention +* acconfig header:: Additional entries in @file{config.h.in} * autoupdate Invocation:: Automatic update of @file{configure.ac} * Obsolete Macros:: Backward compatibility macros * Autoconf 1:: Tips for upgrading your files -* Autoconf 2.13:: Some fresher tips +* Autoconf 213:: Some fresher tips @end menu address@hidden Obsolete config.status Use address@hidden Obsolete config status Use @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 Invocation}, for more details. Before, environment variables had to be used. @defvar CONFIG_COMMANDS @@ -12449,7 +12449,7 @@ @file{config.status} ignores this variable. @end defvar -In @ref{config.status Invocation}, using this old interface, the example +In @ref{config status Invocation}, using this old interface, the example would be: @example @@ -12472,7 +12472,7 @@ for @code{CONFIG_COMMANDS} etc.) address@hidden acconfig.h address@hidden acconfig header @section @file{acconfig.h} @cindex @file{acconfig.h} @@ -13619,7 +13619,7 @@ encapsulate them into macros that you can share. address@hidden Autoconf 2.13 address@hidden Autoconf 213 @section Upgrading From Version 2.13 The introduction of the previous section (@pxref{Autoconf 1}) perfectly @@ -14082,7 +14082,7 @@ @menu * Using an Autotest Test Suite:: Autotest and the user -* Writing testsuite.at:: Autotest macros +* Writing testsuite:: Autotest macros * testsuite Invocation:: Running @command{testsuite} scripts * Making testsuite Scripts:: Using autom4te to create @command{testsuite} @end menu @@ -14240,7 +14240,7 @@ @item tested programs The absolute path and answers to @option{--version} of the tested -programs (see @ref{Writing testsuite.at}, @code{AT_TESTED}). +programs (see @ref{Writing testsuite}, @code{AT_TESTED}). @item configuration log The contents of @file{config.log}, as created by @command{configure}, @@ -14249,7 +14249,7 @@ @end table address@hidden Writing testsuite.at address@hidden Writing testsuite @section Writing @file{testsuite.at} The @file{testsuite.at} is a Bourne shell script making use of special @@ -14557,7 +14557,7 @@ * Bootstrapping:: Autoconf and @acronym{GNU} M4 require each other? * Why Not Imake:: Why @acronym{GNU} uses @command{configure} instead of Imake * Defining Directories:: Passing @code{datadir} to program -* autom4te.cache:: What is it? Can I remove it? +* autom4te cache:: What is it? Can I remove it? * Present But Cannot Be Compiled:: Compiler and Preprocessor Disagree @end menu @@ -14803,7 +14803,7 @@ @end itemize address@hidden autom4te.cache address@hidden autom4te cache @section What is @file{autom4te.cache}? @display