1 diff -Nur autoconf-2.58.orig/doc/autoconf.texi autoconf-2.58/doc/autoconf.texi
2 --- autoconf-2.58.orig/doc/autoconf.texi 2003-11-05 19:26:28.000000000 +0100
3 +++ autoconf-2.58/doc/autoconf.texi 2003-11-05 19:29:40.054405552 +0100
8 -@dircategory Software development
9 +@dircategory Programming tools:
11 -* Autoconf: (autoconf). Create source code configuration scripts.
14 -@dircategory Individual utilities
16 -* autoscan: (autoconf)autoscan Invocation.
17 - Semi-automatic @file{configure.ac} writing
18 -* ifnames: (autoconf)ifnames Invocation. Listing conditionals in source.
19 -* autoconf: (autoconf)autoconf Invocation.
20 - How to create configuration scripts
21 -* autoreconf: (autoconf)autoreconf Invocation.
22 - Remaking multiple @command{configure} scripts
23 -* autoheader: (autoconf)autoheader Invocation.
24 - How to create configuration templates
25 -* autom4te: (autoconf)autom4te Invocation.
26 - The Autoconf executables backbone
27 -* configure: (autoconf)configure Invocation. Configuring a package.
28 -* autoupdate: (autoconf)autoupdate Invocation.
29 - Automatic update of @file{configure.ac}
30 -* config.status: (autoconf)config.status Invocation. Recreating configurations.
31 -* testsuite: (autoconf)testsuite Invocation. Running an Autotest test suite.
32 +* Autoconf: (autoconf). Create source code configuration scripts
33 +* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac} writing
34 +* ifnames: (autoconf)ifnames. Listing conditionals in source
35 +* autoconf: (autoconf)autoconf. How to create configuration scripts
36 +* autoreconf: (autoconf)autoreconf. Remaking multiple @command{configure} scripts
37 +* autoheader: (autoconf)autoheader. How to create configuration templates
38 +* autom4te: (autoconf)autom4te. The Autoconf executables backbone
39 +* configure: (autoconf)configure. Configuring a package.
40 +* autoupdate: (autoconf)autoupdate. Automatic update of @file{configure.ac}
41 +* config.status: (autoconf)config.status. Recreating configurations
42 +* testsuite: (autoconf)testsuite. Running an Autotest test suite
47 * Manual Configuration:: Selecting features that can't be guessed
48 * Site Configuration:: Local defaults for @command{configure}
49 * Running configure Scripts:: How to use the Autoconf output
50 -* config.status Invocation:: Recreating a configuration
51 +* config.status:: Recreating a configuration
52 * Obsolete Constructs:: Kept for backward compatibility
53 * Using Autotest:: Creating portable test suites
54 * FAQ:: Frequent Autoconf Questions, with answers
56 Making @command{configure} Scripts
58 * Writing configure.ac:: What to put in an Autoconf input file
59 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
60 -* ifnames Invocation:: Listing the conditionals in source code
61 -* autoconf Invocation:: How to create configuration scripts
62 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
63 +* autoscan:: Semi-automatic @file{configure.ac} writing
64 +* ifnames:: Listing the conditionals in source code
65 +* autoconf:: How to create configuration scripts
66 +* autoreconf:: Remaking multiple @command{configure} scripts
68 Writing @file{configure.ac}
71 Configuration Header Files
73 * Header Templates:: Input for the configuration headers
74 -* autoheader Invocation:: How to create configuration templates
75 +* autoheader:: How to create configuration templates
76 * Autoheader Macros:: How to specify CPP templates
81 Using @command{autom4te}
83 -* autom4te Invocation:: A @acronym{GNU} M4 wrapper
84 +* autom4te:: A @acronym{GNU} M4 wrapper
85 * Customizing autom4te:: Customizing the Autoconf package
87 Programming in M4sugar
89 * System Type:: Specifying the system type
90 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
91 * Defining Variables:: Specifying the compiler etc.
92 -* configure Invocation:: Changing how @command{configure} runs
93 +* configure:: Changing how @command{configure} runs
97 * Obsolete config.status Use:: Different calling convention
98 * acconfig.h:: Additional entries in @file{config.h.in}
99 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
100 +* autoupdate:: Automatic update of @file{configure.ac}
101 * Obsolete Macros:: Backward compatibility macros
102 * Autoconf 1:: Tips for upgrading your files
103 * Autoconf 2.13:: Some fresher tips
106 * Using an Autotest Test Suite:: Autotest and the user
107 * Writing testsuite.at:: Autotest macros
108 -* testsuite Invocation:: Running @command{testsuite} scripts
109 +* testsuite:: Running @command{testsuite} scripts
110 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
112 Using an Autotest Test Suite
116 a shell script called @file{config.status} that, when run, will recreate
117 -the files listed above (@pxref{config.status Invocation});
118 +the files listed above (@pxref{config.status});
121 an optional shell script normally called @file{config.cache}
122 @@ -903,10 +893,10 @@
125 * Writing configure.ac:: What to put in an Autoconf input file
126 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
127 -* ifnames Invocation:: Listing the conditionals in source code
128 -* autoconf Invocation:: How to create configuration scripts
129 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
130 +* autoscan:: Semi-automatic @file{configure.ac} writing
131 +* ifnames:: Listing the conditionals in source code
132 +* autoconf:: How to create configuration scripts
133 +* autoreconf:: Remaking multiple @command{configure} scripts
136 @node Writing configure.ac
138 or specialized features, @file{configure.ac} might need to contain some
139 hand-crafted shell commands; see @ref{Portable Shell}. The
140 @command{autoscan} program can give you a good start in writing
141 -@file{configure.ac} (@pxref{autoscan Invocation}, for more information).
142 +@file{configure.ac} (@pxref{autoscan}, for more information).
144 Previous versions of Autoconf promoted the name @file{configure.in},
145 which is somewhat ambiguous (the tool needed to process this file is not
146 @@ -1150,7 +1140,7 @@
150 -@node autoscan Invocation
152 @section Using @command{autoscan} to Create @file{configure.ac}
153 @cindex @command{autoscan}
155 @@ -1172,7 +1162,7 @@
156 use a configuration header file, you must add a call to
157 @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might
158 also have to change or add some @code{#if} directives to your program in
159 -order to make it work with Autoconf (@pxref{ifnames Invocation}, for
160 +order to make it work with Autoconf (@pxref{ifnames}, for
161 information about a program that can help with that job).
163 When using @command{autoscan} to maintain a @file{configure.ac}, simply
164 @@ -1211,7 +1201,7 @@
165 Prepend @var{dir} to the include path. Multiple invocations accumulate.
168 -@node ifnames Invocation
170 @section Using @command{ifnames} to List Conditionals
171 @cindex @command{ifnames}
173 @@ -1220,8 +1210,7 @@
174 preprocessor conditionals. If a package has already been set up to have
175 some portability, @command{ifnames} can thus help you figure out what its
176 @command{configure} needs to check for. It may help fill in some gaps in a
177 -@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan
179 +@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan}).
181 @command{ifnames} scans all of the C source files named on the command line
182 (or the standard input, if none are given) and writes to the standard
183 @@ -1243,7 +1232,7 @@
184 Print the version number of Autoconf and exit.
187 -@node autoconf Invocation
189 @section Using @command{autoconf} to Create @command{configure}
190 @cindex @command{autoconf}
192 @@ -1337,8 +1326,7 @@
193 @cindex Macro invocation stack
194 Because @command{autoconf} uses @command{autom4te} behind the scenes, it
195 displays a back trace for errors, but not for warnings; if you want
196 -them, just pass @option{-W error}. @xref{autom4te Invocation}, for some
198 +them, just pass @option{-W error}. @xref{autom4te}, for some examples.
200 @item --trace=@var{macro}[:@var{format}]
201 @itemx -t @var{macro}[:@var{format}]
202 @@ -1350,7 +1338,7 @@
204 The @var{format} is a regular string, with newlines if desired, and
205 several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
206 -@ref{autom4te Invocation}, for details on the @var{format}.
207 +@ref{autom4te}, for details on the @var{format}.
209 @item --initialization
211 @@ -1424,7 +1412,7 @@
215 -@node autoreconf Invocation
217 @section Using @command{autoreconf} to Update @command{configure} Scripts
218 @cindex @command{autoreconf}
220 @@ -1709,8 +1697,8 @@
221 source directory; @command{configure} checks for this file's existence to
222 make sure that the directory that it is told contains the source code in
223 fact does. Occasionally people accidentally specify the wrong directory
224 -with @option{--srcdir}; this is a safety check. @xref{configure
225 -Invocation}, for more information.
226 +with @option{--srcdir}; this is a safety check. @xref{configure},
227 +for more information.
231 @@ -1898,7 +1886,7 @@
232 when used in @var{output}, or the standard input when used in the
233 @var{inputs}. You most probably don't need to use this in
234 @file{configure.ac}, but it is convenient when using the command line
235 -interface of @file{./config.status}, see @ref{config.status Invocation},
236 +interface of @file{./config.status}, see @ref{config.status},
239 The @var{inputs} may be absolute or relative filenames. In the latter
240 @@ -2521,7 +2509,7 @@
241 @file{config.h} is considered up to date. @xref{Output}, for more
242 information about @code{AC_OUTPUT}.
244 -@xref{config.status Invocation}, for more examples of handling
245 +@xref{config.status}, for more examples of handling
246 configuration-related dependencies.
248 @node Configuration Headers
249 @@ -2583,7 +2571,7 @@
252 * Header Templates:: Input for the configuration headers
253 -* autoheader Invocation:: How to create configuration templates
254 +* autoheader:: How to create configuration templates
255 * Autoheader Macros:: How to specify CPP templates
258 @@ -2637,10 +2625,10 @@
259 comments in preprocessor macros has never been a good idea.
261 Since it is a tedious task to keep a template header up to date, you may
262 -use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
263 +use @command{autoheader} to generate it, see @ref{autoheader}.
266 -@node autoheader Invocation
268 @subsection Using @command{autoheader} to Create @file{config.h.in}
269 @cindex @command{autoheader}
271 @@ -6948,7 +6936,7 @@
272 files will depend upon @command{bizarre-cc} being the C compiler. If
273 for some reason the user runs @command{./configure} again, or if it is
274 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
275 -and @pxref{config.status Invocation}), then the configuration can be
276 +and @pxref{config.status}), then the configuration can be
277 inconsistent, composed of results depending upon two different
280 @@ -7000,7 +6988,7 @@
283 @var{variable} is kept during automatic reconfiguration
284 -(@pxref{config.status Invocation}) as if it had been passed as a command
285 +(@pxref{config.status}) as if it had been passed as a command
286 line argument, including when no cache is used:
289 @@ -7871,11 +7859,11 @@
290 It supports M4 extensions designed for use in tools like Autoconf.
293 -* autom4te Invocation:: A @acronym{GNU} M4 wrapper
294 +* autom4te:: A @acronym{GNU} M4 wrapper
295 * Customizing autom4te:: Customizing the Autoconf package
298 -@node autom4te Invocation
300 @subsection Invoking @command{autom4te}
302 The command line arguments are modeled after M4's:
303 @@ -8158,7 +8146,7 @@
307 -@xref{autoconf Invocation}, for examples of trace uses.
308 +@xref{autoconf}, for examples of trace uses.
310 @item --preselect=@var{macro}
311 @itemx -p @var{macro}
312 @@ -8232,8 +8220,8 @@
313 wrapped in between a @samp{begin-language: "@var{language}"},
314 @samp{end-language: "@var{language}"} pair.
316 -Customizing a language stands for appending options (@pxref{autom4te
317 -Invocation}) to the current definition of the language. Options, and
318 +Customizing a language stands for appending options (@pxref{autom4te})
319 +to the current definition of the language. Options, and
320 more generally arguments, are introduced by @samp{args:
321 @var{arguments}}. You may use the traditional shell syntax to quote the
323 @@ -8662,7 +8650,7 @@
325 When the user runs @samp{autoconf -W error}, warnings from
326 @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
327 -@ref{autoconf Invocation}.
330 @node Dependencies Between Macros
331 @section Dependencies Between Macros
332 @@ -12729,7 +12717,7 @@
333 * System Type:: Specifying the system type
334 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
335 * Defining Variables:: Specifying the compiler etc.
336 -* configure Invocation:: Changing how @command{configure} runs
337 +* configure:: Changing how @command{configure} runs
341 @@ -12738,7 +12726,7 @@
343 @c ============================================== Recreating a Configuration
345 -@node config.status Invocation
347 @chapter Recreating a Configuration
348 @cindex @command{config.status}
350 @@ -12878,7 +12866,7 @@
352 * Obsolete config.status Use:: Different calling convention
353 * acconfig.h:: Additional entries in @file{config.h.in}
354 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
355 +* autoupdate:: Automatic update of @file{configure.ac}
356 * Obsolete Macros:: Backward compatibility macros
357 * Autoconf 1:: Tips for upgrading your files
358 * Autoconf 2.13:: Some fresher tips
359 @@ -12888,7 +12876,7 @@
360 @section Obsolete @file{config.status} Invocation
362 @file{config.status} now supports arguments to specify the files to
363 -instantiate; see @ref{config.status Invocation}, for more details.
364 +instantiate; see @ref{config.status}, for more details.
365 Before, environment variables had to be used.
367 @defvar CONFIG_COMMANDS
368 @@ -12919,7 +12907,7 @@
369 @file{config.status} ignores this variable.
372 -In @ref{config.status Invocation}, using this old interface, the example
373 +In @ref{config.status}, using this old interface, the example
377 @@ -12993,7 +12981,7 @@
378 self-contained, and should not depend upon @file{acconfig.h} etc.
381 -@node autoupdate Invocation
383 @section Using @command{autoupdate} to Modernize @file{configure.ac}
384 @cindex @command{autoupdate}
386 @@ -13929,7 +13917,7 @@
388 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
389 in a particular package's source directory), you must rename it to
390 -@file{acsite.m4}. @xref{autoconf Invocation}.
391 +@file{acsite.m4}. @xref{autoconf}.
393 If you distribute @file{install.sh} with your package, rename it to
394 @file{install-sh} so @code{make} builtin rules won't inadvertently
395 @@ -13984,7 +13972,7 @@
396 the documentation for them. @xref{Obsolete Macros}, for a table showing the
397 new names for the old macros. Use the @command{autoupdate} program to
398 convert your @file{configure.ac} to using the new macro names.
399 -@xref{autoupdate Invocation}.
402 Some macros have been superseded by similar ones that do the job better,
403 but are not call-compatible. If you get warnings about calling obsolete
404 @@ -14549,7 +14537,7 @@
406 * Using an Autotest Test Suite:: Autotest and the user
407 * Writing testsuite.at:: Autotest macros
408 -* testsuite Invocation:: Running @command{testsuite} scripts
409 +* testsuite:: Running @command{testsuite} scripts
410 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
413 @@ -14611,7 +14599,7 @@
416 @item a debugging script named @file{run} which reruns the test in
417 -@dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation
418 +@dfn{debug mode} (@pxref{testsuite}). The automatic generation
419 of debugging scripts has the purpose of easing the chase for bugs.
421 @item all the files created with @code{AT_DATA}
422 @@ -14833,7 +14821,7 @@
426 -@node testsuite Invocation
428 @section Running @command{testsuite} Scripts
429 @cindex @command{testsuite}
431 @@ -14976,7 +14964,7 @@
432 An Autotest test suite is to be configured in @var{directory}. This
433 macro requires the instantiation of @file{@var{directory}/atconfig} from
434 @file{@var{directory}/atconfig.in}, and sets the default
435 -@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite Invocation}).
436 +@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite}).
440 @@ -15306,7 +15294,7 @@
441 which can be a very long process for complex @file{configure.ac}.
443 This is why all these tools, instead of running directly M4, invoke
444 -@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
445 +@command{autom4te} (@pxref{autom4te}) which, while answering to
446 a specific demand, stores additional information in
447 @file{autom4te.cache} for future runs. For instance, if you run
448 @command{autoconf}, behind the scenes, @command{autom4te} will also
449 diff -Nur autoconf-2.58.orig/doc/install.texi autoconf-2.58/doc/install.texi
450 --- autoconf-2.58.orig/doc/install.texi 2002-08-27 10:28:06.000000000 +0200
451 +++ autoconf-2.58/doc/install.texi 2003-11-05 19:26:39.414866936 +0100
453 overridden in the site shell script).
456 -@node configure Invocation
458 @section @command{configure} Invocation
460 @command{configure} recognizes the following options to control how it
461 diff -Nur autoconf-2.58.orig/doc/standards.texi autoconf-2.58/doc/standards.texi
462 --- autoconf-2.58.orig/doc/standards.texi 2003-09-15 03:33:44.000000000 +0200
463 +++ autoconf-2.58/doc/standards.texi 2003-11-05 19:26:39.427864960 +0100
465 @set lastupdate April 29, 2003
468 -@dircategory GNU organization
469 +@dircategory Miscellaneous:
471 -* Standards: (standards). GNU coding standards.
472 +* Standards: (standards). GNU coding standards
475 @c @setchapternewpage odd