--- autoconf-2.60/doc/autoconf.texi.orig 2006-06-27 23:03:21.858011250 +0200 +++ autoconf-2.60/doc/autoconf.texi 2006-06-27 23:04:06.268786750 +0200 @@ -203,29 +203,19 @@ -@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 conditionals in source. -* 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)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 conditionals in source +* 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 configurations +* testsuite: (autoconf)testsuite. Running an Autotest test suite @end direntry @titlepage @@ -267,7 +257,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 @@ -288,10 +278,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} @@ -325,7 +315,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 @@ -441,7 +431,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 @@ -548,13 +538,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 @@ -579,7 +569,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 @@ -911,7 +901,7 @@ @item a shell script called @file{config.status} that, when run, recreates -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} @@ -971,10 +961,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 @@ -990,7 +980,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 @@ -1244,7 +1234,7 @@ @end display -@node autoscan Invocation +@node autoscan @section Using @command{autoscan} to Create @file{configure.ac} @cindex @command{autoscan} @@ -1266,7 +1256,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 @@ -1305,7 +1295,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} @@ -1314,8 +1304,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 @@ -1337,7 +1326,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} @@ -1431,8 +1420,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}] @@ -1444,7 +1432,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 @@ -1518,7 +1506,7 @@ @end group @end example -@node autoreconf Invocation +@node autoreconf @section Using @command{autoreconf} to Update @command{configure} Scripts @cindex @command{autoreconf} @@ -1831,8 +1819,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 @@ -2037,7 +2025,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 file names. In the latter @@ -2857,7 +2845,7 @@ so @file{config.status} ensures that @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 @@ -2941,7 +2929,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 @@ -2996,10 +2984,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 @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} @@ -8289,7 +8277,7 @@ files 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. @@ -8341,7 +8329,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 @@ -9258,11 +9246,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: @@ -9520,7 +9508,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} @@ -9608,8 +9596,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}. @@ -10305,7 +10293,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 @@ -15688,7 +15676,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 @@ -15697,7 +15685,7 @@ @c ============================================== Recreating a Configuration -@node config.status Invocation +@node config.status @chapter Recreating a Configuration @cindex @command{config.status} @@ -15842,7 +15830,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 @@ -15852,7 +15840,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 @@ -15883,7 +15871,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 @@ -15957,7 +15945,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} @@ -16944,7 +16932,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 don't inadvertently @@ -16999,7 +16987,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 @@ -17535,7 +17523,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 @@ -17597,7 +17585,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} @@ -17836,7 +17824,7 @@ @end defmac -@node testsuite Invocation +@node testsuite @section Running @command{testsuite} Scripts @cindex @command{testsuite} @@ -17996,7 +17984,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 @@ -18346,7 +18334,7 @@ which can be a 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} 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