--- autoconf-2.54/doc/autoconf.texi.wiget Fri Oct 18 10:53:27 2002 +++ autoconf-2.54/doc/autoconf.texi Fri Oct 18 11:01:49 2002 @@ -94,33 +94,19 @@ -@dircategory GNU programming tools +@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 -* autoheader: (autoconf)autoheader Invocation. - How to create configuration templates -* autom4te: (autoconf)Invoking autom4te. - 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 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 +* autoheader: (autoconf)autoheader. How to create configuration templates +* autom4te: (autoconf)autom4te. The Autoconf executables backbone +* configure: (autoconf)configure. Configuring a package +* autoupdate: (autoconf)autoupdate. Automatic update of @file{configure.ac} +* config.status: (autoconf)config.status. Recreating a configuration +* testsuite: (autoconf)testsuite. Running an Autotest test suite @end direntry @titlepage @@ -160,7 +146,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 * FAQ:: Frequent Autoconf Questions, with answers @@ -180,10 +166,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} @@ -216,7 +202,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 @@ -311,7 +297,7 @@ Programming in M4 * M4 Quotation:: Protecting macros from unwanted expansion -* Invoking autom4te:: The Autoconf executables backbone +* autom4te:: The Autoconf executables backbone * Programming in M4sugar:: Convenient pure M4 macros * Programming in M4sh:: Common shell constructs @@ -388,13 +374,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 @@ -418,7 +404,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 +715,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 +775,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 +794,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 process this file is not @@ -1036,7 +1022,7 @@ @end display -@node autoscan Invocation +@node autoscan @section Using @command{autoscan} to Create @file{configure.ac} @cindex @command{autoscan} @@ -1058,7 +1044,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 @@ -1097,7 +1083,7 @@ Prepend @var{dir} to the include path. Multiple invocations accumulate. @end table -@node ifnames Invocation +@node ifnames @section Using @command{ifnames} to List Conditionals @cindex @command{ifnames} @@ -1106,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 @@ -1129,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} @@ -1389,7 +1374,7 @@ @end group @end example -@node autoreconf Invocation +@node autoreconf @section Using @command{autoreconf} to Update @command{configure} Scripts @cindex @command{autoreconf} @@ -1623,8 +1608,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 @@ -1790,7 +1775,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 @@ -2387,7 +2372,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 @@ -2448,7 +2433,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 @@ -2499,10 +2484,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} @@ -6215,7 +6200,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. @@ -6267,7 +6252,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 @@ -6608,7 +6593,7 @@ @menu * M4 Quotation:: Protecting macros from unwanted expansion -* Invoking autom4te:: The Autoconf executables backbone +* autom4te:: The Autoconf executables backbone * Programming in M4sugar:: Convenient pure M4 macros * Programming in M4sh:: Common shell Constructs @end menu @@ -7111,7 +7096,7 @@ unexpanded macros. The @command{autoconf} program checks for this problem by doing @samp{grep AC_ configure}. -@node Invoking autom4te +@node autom4te @section Invoking @command{autom4te} The Autoconf suite, including M4sugar, M4sh, and Autotest, in addition to @@ -7394,7 +7379,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} @@ -7845,7 +7830,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 @@ -11642,7 +11627,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 @@ -11651,7 +11636,7 @@ @c ============================================== Recreating a Configuration -@node config.status Invocation +@node config.status @chapter Recreating a Configuration @cindex @command{config.status} @@ -11785,7 +11770,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 @@ -11795,7 +11780,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 @@ -11826,7 +11811,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 @@ -11900,7 +11885,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} @@ -12750,7 +12735,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 @@ -12805,7 +12790,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 @@ -13302,7 +13287,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 @@ -13564,7 +13549,7 @@ @end defmac -@node testsuite Invocation +@node testsuite @section Running @command{testsuite} Scripts @cindex @command{testsuite} @@ -13706,7 +13691,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 --- autoconf-2.54/doc/install.texi.wiget Tue Aug 27 10:28:06 2002 +++ autoconf-2.54/doc/install.texi Fri Oct 18 10:53:29 2002 @@ -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 --- autoconf-2.54/doc/standards.texi.wiget Wed Apr 10 10:13:19 2002 +++ autoconf-2.54/doc/standards.texi Fri Oct 18 10:53:29 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