1 --- autoconf-2.60/doc/autoconf.texi.orig 2006-06-27 23:03:21.858011250 +0200
2 +++ autoconf-2.60/doc/autoconf.texi 2006-06-27 23:04:06.268786750 +0200
7 -@dircategory Software development
8 +@dircategory Programming tools:
10 -* Autoconf: (autoconf). Create source code configuration scripts.
13 -@dircategory Individual utilities
15 -* autoscan: (autoconf)autoscan Invocation.
16 - Semi-automatic @file{configure.ac} writing
17 -* ifnames: (autoconf)ifnames Invocation. Listing conditionals in source.
18 -* autoconf: (autoconf)autoconf Invocation.
19 - How to create configuration scripts
20 -* autoreconf: (autoconf)autoreconf Invocation.
21 - Remaking multiple @command{configure} scripts
22 -* autoheader: (autoconf)autoheader Invocation.
23 - How to create configuration templates
24 -* autom4te: (autoconf)autom4te Invocation.
25 - The Autoconf executables backbone
26 -* configure: (autoconf)configure Invocation. Configuring a package.
27 -* autoupdate: (autoconf)autoupdate Invocation.
28 - Automatic update of @file{configure.ac}
29 -* config.status: (autoconf)config.status Invocation. Recreating configurations.
30 -* testsuite: (autoconf)testsuite Invocation. Running an Autotest test suite.
31 +* Autoconf: (autoconf). Create source code configuration scripts
32 +* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac} writing
33 +* ifnames: (autoconf)ifnames. Listing conditionals in source
34 +* autoconf: (autoconf)autoconf. How to create configuration scripts
35 +* autoreconf: (autoconf)autoreconf. Remaking multiple @command{configure} scripts
36 +* autoheader: (autoconf)autoheader. How to create configuration templates
37 +* autom4te: (autoconf)autom4te. The Autoconf executables backbone
38 +* configure: (autoconf)configure. Configuring a package
39 +* autoupdate: (autoconf)autoupdate. Automatic update of @file{configure.ac}
40 +* config.status: (autoconf)config.status. Recreating configurations
41 +* testsuite: (autoconf)testsuite. Running an Autotest test suite
46 * Manual Configuration:: Selecting features that can't be guessed
47 * Site Configuration:: Local defaults for @command{configure}
48 * Running configure Scripts:: How to use the Autoconf output
49 -* config.status Invocation:: Recreating a configuration
50 +* config.status:: Recreating a configuration
51 * Obsolete Constructs:: Kept for backward compatibility
52 * Using Autotest:: Creating portable test suites
53 * FAQ:: Frequent Autoconf Questions, with answers
55 Making @command{configure} Scripts
57 * Writing configure.ac:: What to put in an Autoconf input file
58 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
59 -* ifnames Invocation:: Listing the conditionals in source code
60 -* autoconf Invocation:: How to create configuration scripts
61 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
62 +* autoscan:: Semi-automatic @file{configure.ac} writing
63 +* ifnames:: Listing the conditionals in source code
64 +* autoconf:: How to create configuration scripts
65 +* autoreconf:: Remaking multiple @command{configure} scripts
67 Writing @file{configure.ac}
70 Configuration Header Files
72 * Header Templates:: Input for the configuration headers
73 -* autoheader Invocation:: How to create configuration templates
74 +* autoheader:: How to create configuration templates
75 * Autoheader Macros:: How to specify CPP templates
80 Using @command{autom4te}
82 -* autom4te Invocation:: A @acronym{GNU} M4 wrapper
83 +* autom4te:: A @acronym{GNU} M4 wrapper
84 * Customizing autom4te:: Customizing the Autoconf package
86 Programming in M4sugar
88 * System Type:: Specifying the system type
89 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
90 * Defining Variables:: Specifying the compiler etc.
91 -* configure Invocation:: Changing how @command{configure} runs
92 +* configure:: Changing how @command{configure} runs
96 * Obsolete config.status Use:: Different calling convention
97 * acconfig.h:: Additional entries in @file{config.h.in}
98 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
99 +* autoupdate:: Automatic update of @file{configure.ac}
100 * Obsolete Macros:: Backward compatibility macros
101 * Autoconf 1:: Tips for upgrading your files
102 * Autoconf 2.13:: Some fresher tips
105 * Using an Autotest Test Suite:: Autotest and the user
106 * Writing testsuite.at:: Autotest macros
107 -* testsuite Invocation:: Running @command{testsuite} scripts
108 +* testsuite:: Running @command{testsuite} scripts
109 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
111 Using an Autotest Test Suite
115 a shell script called @file{config.status} that, when run, recreates
116 -the files listed above (@pxref{config.status Invocation});
117 +the files listed above (@pxref{config.status});
120 an optional shell script normally called @file{config.cache}
121 @@ -971,10 +961,10 @@
124 * Writing configure.ac:: What to put in an Autoconf input file
125 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
126 -* ifnames Invocation:: Listing the conditionals in source code
127 -* autoconf Invocation:: How to create configuration scripts
128 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
129 +* autoscan:: Semi-automatic @file{configure.ac} writing
130 +* ifnames:: Listing the conditionals in source code
131 +* autoconf:: How to create configuration scripts
132 +* autoreconf:: Remaking multiple @command{configure} scripts
135 @node Writing configure.ac
137 or specialized features, @file{configure.ac} might need to contain some
138 hand-crafted shell commands; see @ref{Portable Shell}. The
139 @command{autoscan} program can give you a good start in writing
140 -@file{configure.ac} (@pxref{autoscan Invocation}, for more information).
141 +@file{configure.ac} (@pxref{autoscan}, for more information).
143 Previous versions of Autoconf promoted the name @file{configure.in},
144 which is somewhat ambiguous (the tool needed to process this file is not
145 @@ -1244,7 +1234,7 @@
149 -@node autoscan Invocation
151 @section Using @command{autoscan} to Create @file{configure.ac}
152 @cindex @command{autoscan}
154 @@ -1266,7 +1256,7 @@
155 use a configuration header file, you must add a call to
156 @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might
157 also have to change or add some @code{#if} directives to your program in
158 -order to make it work with Autoconf (@pxref{ifnames Invocation}, for
159 +order to make it work with Autoconf (@pxref{ifnames}, for
160 information about a program that can help with that job).
162 When using @command{autoscan} to maintain a @file{configure.ac}, simply
163 @@ -1305,7 +1295,7 @@
164 Prepend @var{dir} to the include path. Multiple invocations accumulate.
167 -@node ifnames Invocation
169 @section Using @command{ifnames} to List Conditionals
170 @cindex @command{ifnames}
172 @@ -1314,8 +1304,7 @@
173 preprocessor conditionals. If a package has already been set up to have
174 some portability, @command{ifnames} can thus help you figure out what its
175 @command{configure} needs to check for. It may help fill in some gaps in a
176 -@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan
178 +@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan}).
180 @command{ifnames} scans all of the C source files named on the command line
181 (or the standard input, if none are given) and writes to the standard
182 @@ -1337,7 +1326,7 @@
183 Print the version number of Autoconf and exit.
186 -@node autoconf Invocation
188 @section Using @command{autoconf} to Create @command{configure}
189 @cindex @command{autoconf}
191 @@ -1431,8 +1420,7 @@
192 @cindex Macro invocation stack
193 Because @command{autoconf} uses @command{autom4te} behind the scenes, it
194 displays a back trace for errors, but not for warnings; if you want
195 -them, just pass @option{-W error}. @xref{autom4te Invocation}, for some
197 +them, just pass @option{-W error}. @xref{autom4te}, for some examples.
199 @item --trace=@var{macro}[:@var{format}]
200 @itemx -t @var{macro}[:@var{format}]
201 @@ -1444,7 +1432,7 @@
203 The @var{format} is a regular string, with newlines if desired, and
204 several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
205 -@ref{autom4te Invocation}, for details on the @var{format}.
206 +@ref{autom4te}, for details on the @var{format}.
208 @item --initialization
210 @@ -1518,7 +1506,7 @@
214 -@node autoreconf Invocation
216 @section Using @command{autoreconf} to Update @command{configure} Scripts
217 @cindex @command{autoreconf}
219 @@ -1831,8 +1819,8 @@
220 source directory; @command{configure} checks for this file's existence to
221 make sure that the directory that it is told contains the source code in
222 fact does. Occasionally people accidentally specify the wrong directory
223 -with @option{--srcdir}; this is a safety check. @xref{configure
224 -Invocation}, for more information.
225 +with @option{--srcdir}; this is a safety check. @xref{configure},
226 +for more information.
230 @@ -2037,7 +2025,7 @@
231 when used in @var{output}, or the standard input when used in the
232 @var{inputs}. You most probably don't need to use this in
233 @file{configure.ac}, but it is convenient when using the command line
234 -interface of @file{./config.status}, see @ref{config.status Invocation},
235 +interface of @file{./config.status}, see @ref{config.status},
238 The @var{inputs} may be absolute or relative file names. In the latter
239 @@ -2857,7 +2845,7 @@
240 so @file{config.status} ensures that @file{config.h} is considered up to
241 date. @xref{Output}, for more information about @code{AC_OUTPUT}.
243 -@xref{config.status Invocation}, for more examples of handling
244 +@xref{config.status}, for more examples of handling
245 configuration-related dependencies.
247 @node Configuration Headers
248 @@ -2941,7 +2929,7 @@
251 * Header Templates:: Input for the configuration headers
252 -* autoheader Invocation:: How to create configuration templates
253 +* autoheader:: How to create configuration templates
254 * Autoheader Macros:: How to specify CPP templates
257 @@ -2996,10 +2984,10 @@
258 comments in preprocessor macros has never been a good idea.
260 Since it is a tedious task to keep a template header up to date, you may
261 -use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
262 +use @command{autoheader} to generate it, see @ref{autoheader}.
265 -@node autoheader Invocation
267 @subsection Using @command{autoheader} to Create @file{config.h.in}
268 @cindex @command{autoheader}
270 @@ -8289,7 +8277,7 @@
271 files depend upon @command{bizarre-cc} being the C compiler. If
272 for some reason the user runs @command{./configure} again, or if it is
273 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
274 -and @pxref{config.status Invocation}), then the configuration can be
275 +and @pxref{config.status}), then the configuration can be
276 inconsistent, composed of results depending upon two different
279 @@ -8341,7 +8329,7 @@
282 @var{variable} is kept during automatic reconfiguration
283 -(@pxref{config.status Invocation}) as if it had been passed as a command
284 +(@pxref{config.status}) as if it had been passed as a command
285 line argument, including when no cache is used:
288 @@ -9258,11 +9246,11 @@
289 It supports M4 extensions designed for use in tools like Autoconf.
292 -* autom4te Invocation:: A @acronym{GNU} M4 wrapper
293 +* autom4te:: A @acronym{GNU} M4 wrapper
294 * Customizing autom4te:: Customizing the Autoconf package
297 -@node autom4te Invocation
299 @subsection Invoking @command{autom4te}
301 The command line arguments are modeled after M4's:
302 @@ -9520,7 +9508,7 @@
306 -@xref{autoconf Invocation}, for examples of trace uses.
307 +@xref{autoconf}, for examples of trace uses.
309 @item --preselect=@var{macro}
310 @itemx -p @var{macro}
311 @@ -9608,8 +9596,8 @@
312 wrapped in between a @samp{begin-language: "@var{language}"},
313 @samp{end-language: "@var{language}"} pair.
315 -Customizing a language stands for appending options (@pxref{autom4te
316 -Invocation}) to the current definition of the language. Options, and
317 +Customizing a language stands for appending options (@pxref{autom4te})
318 +to the current definition of the language. Options, and
319 more generally arguments, are introduced by @samp{args:
320 @var{arguments}}. You may use the traditional shell syntax to quote the
322 @@ -10305,7 +10293,7 @@
324 When the user runs @samp{autoconf -W error}, warnings from
325 @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
326 -@ref{autoconf Invocation}.
329 @node Dependencies Between Macros
330 @section Dependencies Between Macros
331 @@ -15688,7 +15676,7 @@
332 * System Type:: Specifying the system type
333 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
334 * Defining Variables:: Specifying the compiler etc.
335 -* configure Invocation:: Changing how @command{configure} runs
336 +* configure:: Changing how @command{configure} runs
340 @@ -15697,7 +15685,7 @@
342 @c ============================================== Recreating a Configuration
344 -@node config.status Invocation
346 @chapter Recreating a Configuration
347 @cindex @command{config.status}
349 @@ -15842,7 +15830,7 @@
351 * Obsolete config.status Use:: Different calling convention
352 * acconfig.h:: Additional entries in @file{config.h.in}
353 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
354 +* autoupdate:: Automatic update of @file{configure.ac}
355 * Obsolete Macros:: Backward compatibility macros
356 * Autoconf 1:: Tips for upgrading your files
357 * Autoconf 2.13:: Some fresher tips
358 @@ -15852,7 +15840,7 @@
359 @section Obsolete @file{config.status} Invocation
361 @file{config.status} now supports arguments to specify the files to
362 -instantiate; see @ref{config.status Invocation}, for more details.
363 +instantiate; see @ref{config.status}, for more details.
364 Before, environment variables had to be used.
366 @defvar CONFIG_COMMANDS
367 @@ -15883,7 +15871,7 @@
368 @file{config.status} ignores this variable.
371 -In @ref{config.status Invocation}, using this old interface, the example
372 +In @ref{config.status}, using this old interface, the example
376 @@ -15957,7 +15945,7 @@
377 self-contained, and should not depend upon @file{acconfig.h} etc.
380 -@node autoupdate Invocation
382 @section Using @command{autoupdate} to Modernize @file{configure.ac}
383 @cindex @command{autoupdate}
385 @@ -16944,7 +16932,7 @@
387 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
388 in a particular package's source directory), you must rename it to
389 -@file{acsite.m4}. @xref{autoconf Invocation}.
390 +@file{acsite.m4}. @xref{autoconf}.
392 If you distribute @file{install.sh} with your package, rename it to
393 @file{install-sh} so @code{make} builtin rules don't inadvertently
394 @@ -16999,7 +16987,7 @@
395 the documentation for them. @xref{Obsolete Macros}, for a table showing the
396 new names for the old macros. Use the @command{autoupdate} program to
397 convert your @file{configure.ac} to using the new macro names.
398 -@xref{autoupdate Invocation}.
401 Some macros have been superseded by similar ones that do the job better,
402 but are not call-compatible. If you get warnings about calling obsolete
403 @@ -17535,7 +17523,7 @@
405 * Using an Autotest Test Suite:: Autotest and the user
406 * Writing testsuite.at:: Autotest macros
407 -* testsuite Invocation:: Running @command{testsuite} scripts
408 +* testsuite:: Running @command{testsuite} scripts
409 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
412 @@ -17597,7 +17585,7 @@
415 @item a debugging script named @file{run} which reruns the test in
416 -@dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation
417 +@dfn{debug mode} (@pxref{testsuite}). The automatic generation
418 of debugging scripts has the purpose of easing the chase for bugs.
420 @item all the files created with @code{AT_DATA}
421 @@ -17836,7 +17824,7 @@
425 -@node testsuite Invocation
427 @section Running @command{testsuite} Scripts
428 @cindex @command{testsuite}
430 @@ -17996,7 +17984,7 @@
431 An Autotest test suite is to be configured in @var{directory}. This
432 macro requires the instantiation of @file{@var{directory}/atconfig} from
433 @file{@var{directory}/atconfig.in}, and sets the default
434 -@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite Invocation}).
435 +@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite}).
439 @@ -18346,7 +18334,7 @@
440 which can be a long process for complex @file{configure.ac}.
442 This is why all these tools, instead of running directly M4, invoke
443 -@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
444 +@command{autom4te} (@pxref{autom4te}) which, while answering to
445 a specific demand, stores additional information in
446 @file{autom4te.cache} for future runs. For instance, if you run
447 @command{autoconf}, behind the scenes, @command{autom4te} also
448 diff -Nur autoconf-2.58.orig/doc/install.texi autoconf-2.58/doc/install.texi
449 --- autoconf-2.58.orig/doc/install.texi 2002-08-27 10:28:06.000000000 +0200
450 +++ autoconf-2.58/doc/install.texi 2003-11-05 19:26:39.414866936 +0100
452 overridden in the site shell script).
455 -@node configure Invocation
457 @section @command{configure} Invocation
459 @command{configure} recognizes the following options to control how it
460 diff -Nur autoconf-2.58.orig/doc/standards.texi autoconf-2.58/doc/standards.texi
461 --- autoconf-2.58.orig/doc/standards.texi 2003-09-15 03:33:44.000000000 +0200
462 +++ autoconf-2.58/doc/standards.texi 2003-11-05 19:26:39.427864960 +0100
464 @set lastupdate April 29, 2003
467 -@dircategory GNU organization
468 +@dircategory Miscellaneous:
470 -* Standards: (standards). GNU coding standards.
471 +* Standards: (standards). GNU coding standards
474 @c @setchapternewpage odd