1 --- autoconf-2.57/doc/autoconf.texi.wiget Wed Dec 4 17:25:14 2002
2 +++ autoconf-2.57/doc/autoconf.texi Wed Dec 4 17:25:14 2002
7 -@dircategory GNU programming tools
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.
18 - Listing the conditionals in source code
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.
28 - Configuring a package
29 -* autoupdate: (autoconf)autoupdate Invocation.
30 - Automatic update of @file{configure.ac}
31 -* config.status: (autoconf)config.status Invocation.
32 - Recreating a configuration
33 -* testsuite: (autoconf)testsuite Invocation.
34 - Running an Autotest test suite
35 +* Autoconf: (autoconf). Create source code configuration scripts
36 +* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac} writing
37 +* ifnames: (autoconf)ifnames. Listing the conditionals in source code
38 +* autoconf: (autoconf)autoconf. How to create configuration scripts
39 +* autoreconf: (autoconf)autoreconf. Remaking multiple @command{configure} scripts
40 +* autoheader: (autoconf)autoheader. How to create configuration templates
41 +* autom4te: (autoconf)autom4te. The Autoconf executables backbone
42 +* configure: (autoconf)configure. Configuring a package
43 +* autoupdate: (autoconf)autoupdate. Automatic update of @file{configure.ac}
44 +* config.status: (autoconf)config.status. Recreating a configuration
45 +* testsuite: (autoconf)testsuite. Running an Autotest test suite
50 * Manual Configuration:: Selecting features that can't be guessed
51 * Site Configuration:: Local defaults for @command{configure}
52 * Running configure Scripts:: How to use the Autoconf output
53 -* config.status Invocation:: Recreating a configuration
54 +* config.status:: Recreating a configuration
55 * Obsolete Constructs:: Kept for backward compatibility
56 * Using Autotest:: Creating portable test suites
57 * FAQ:: Frequent Autoconf Questions, with answers
59 Making @command{configure} Scripts
61 * Writing configure.ac:: What to put in an Autoconf input file
62 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
63 -* ifnames Invocation:: Listing the conditionals in source code
64 -* autoconf Invocation:: How to create configuration scripts
65 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
66 +* autoscan:: Semi-automatic @file{configure.ac} writing
67 +* ifnames:: Listing the conditionals in source code
68 +* autoconf:: How to create configuration scripts
69 +* autoreconf:: Remaking multiple @command{configure} scripts
71 Writing @file{configure.ac}
74 Configuration Header Files
76 * Header Templates:: Input for the configuration headers
77 -* autoheader Invocation:: How to create configuration templates
78 +* autoheader:: How to create configuration templates
79 * Autoheader Macros:: How to specify CPP templates
84 Using @command{autom4te}
86 -* autom4te Invocation:: A @acronym{GNU} M4 wrapper
87 +* autom4te:: A @acronym{GNU} M4 wrapper
88 * Customizing autom4te:: Customizing the Autoconf package
90 Programming in M4sugar
92 * System Type:: Specifying the system type
93 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
94 * Defining Variables:: Specifying the compiler etc.
95 -* configure Invocation:: Changing how @command{configure} runs
96 +* configure:: Changing how @command{configure} runs
100 * Obsolete config.status Use:: Different calling convention
101 * acconfig.h:: Additional entries in @file{config.h.in}
102 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
103 +* autoupdate:: Automatic update of @file{configure.ac}
104 * Obsolete Macros:: Backward compatibility macros
105 * Autoconf 1:: Tips for upgrading your files
106 * Autoconf 2.13:: Some fresher tips
109 * Using an Autotest Test Suite:: Autotest and the user
110 * Writing testsuite.at:: Autotest macros
111 -* testsuite Invocation:: Running @command{testsuite} scripts
112 +* testsuite:: Running @command{testsuite} scripts
113 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
115 Using an Autotest Test Suite
119 a shell script called @file{config.status} that, when run, will recreate
120 -the files listed above (@pxref{config.status Invocation});
121 +the files listed above (@pxref{config.status});
124 an optional shell script normally called @file{config.cache}
125 @@ -800,10 +786,10 @@
128 * Writing configure.ac:: What to put in an Autoconf input file
129 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
130 -* ifnames Invocation:: Listing the conditionals in source code
131 -* autoconf Invocation:: How to create configuration scripts
132 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
133 +* autoscan:: Semi-automatic @file{configure.ac} writing
134 +* ifnames:: Listing the conditionals in source code
135 +* autoconf:: How to create configuration scripts
136 +* autoreconf:: Remaking multiple @command{configure} scripts
139 @node Writing configure.ac
141 or specialized features, @file{configure.ac} might need to contain some
142 hand-crafted shell commands; see @ref{Portable Shell}. The
143 @command{autoscan} program can give you a good start in writing
144 -@file{configure.ac} (@pxref{autoscan Invocation}, for more information).
145 +@file{configure.ac} (@pxref{autoscan}, for more information).
147 Previous versions of Autoconf promoted the name @file{configure.in},
148 which is somewhat ambiguous (the tool needed to process this file is not
149 @@ -1047,7 +1033,7 @@
153 -@node autoscan Invocation
155 @section Using @command{autoscan} to Create @file{configure.ac}
156 @cindex @command{autoscan}
158 @@ -1069,7 +1055,7 @@
159 use a configuration header file, you must add a call to
160 @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might
161 also have to change or add some @code{#if} directives to your program in
162 -order to make it work with Autoconf (@pxref{ifnames Invocation}, for
163 +order to make it work with Autoconf (@pxref{ifnames}, for
164 information about a program that can help with that job).
166 When using @command{autoscan} to maintain a @file{configure.ac}, simply
167 @@ -1108,7 +1094,7 @@
168 Prepend @var{dir} to the include path. Multiple invocations accumulate.
171 -@node ifnames Invocation
173 @section Using @command{ifnames} to List Conditionals
174 @cindex @command{ifnames}
176 @@ -1117,8 +1103,7 @@
177 preprocessor conditionals. If a package has already been set up to have
178 some portability, @command{ifnames} can thus help you figure out what its
179 @command{configure} needs to check for. It may help fill in some gaps in a
180 -@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan
182 +@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan}).
184 @command{ifnames} scans all of the C source files named on the command line
185 (or the standard input, if none are given) and writes to the standard
186 @@ -1140,7 +1125,7 @@
187 Print the version number of Autoconf and exit.
190 -@node autoconf Invocation
192 @section Using @command{autoconf} to Create @command{configure}
193 @cindex @command{autoconf}
195 @@ -1234,8 +1219,7 @@
196 @cindex Macro invocation stack
197 Because @command{autoconf} uses @command{autom4te} behind the scenes, it
198 displays a back trace for errors, but not for warnings; if you want
199 -them, just pass @option{-W error}. @xref{autom4te Invocation}, for some
201 +them, just pass @option{-W error}. @xref{autom4te}, for some examples.
203 @item --trace=@var{macro}[:@var{format}]
204 @itemx -t @var{macro}[:@var{format}]
205 @@ -1247,7 +1231,7 @@
207 The @var{format} is a regular string, with newlines if desired, and
208 several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
209 -@ref{autom4te Invocation}, for details on the @var{format}.
210 +@ref{autom4te}, for details on the @var{format}.
212 @item --initialization
214 @@ -1321,7 +1305,7 @@
218 -@node autoreconf Invocation
220 @section Using @command{autoreconf} to Update @command{configure} Scripts
221 @cindex @command{autoreconf}
223 @@ -1606,8 +1590,8 @@
224 source directory; @command{configure} checks for this file's existence to
225 make sure that the directory that it is told contains the source code in
226 fact does. Occasionally people accidentally specify the wrong directory
227 -with @option{--srcdir}; this is a safety check. @xref{configure
228 -Invocation}, for more information.
229 +with @option{--srcdir}; this is a safety check. @xref{configure},
230 +for more information.
234 @@ -1774,7 +1758,7 @@
235 when used in @var{output}, or the standard input when used in the
236 @var{inputs}. You most probably don't need to use this in
237 @file{configure.ac}, but it is convenient when using the command line
238 -interface of @file{./config.status}, see @ref{config.status Invocation},
239 +interface of @file{./config.status}, see @ref{config.status},
242 The @var{inputs} may be absolute or relative filenames. In the latter
243 @@ -2388,7 +2372,7 @@
244 @file{config.h} is considered up to date. @xref{Output}, for more
245 information about @code{AC_OUTPUT}.
247 -@xref{config.status Invocation}, for more examples of handling
248 +@xref{config.status}, for more examples of handling
249 configuration-related dependencies.
251 @node Configuration Headers
252 @@ -2450,7 +2434,7 @@
255 * Header Templates:: Input for the configuration headers
256 -* autoheader Invocation:: How to create configuration templates
257 +* autoheader:: How to create configuration templates
258 * Autoheader Macros:: How to specify CPP templates
261 @@ -2504,10 +2488,10 @@
262 comments in preprocessor macros has never been a good idea.
264 Since it is a tedious task to keep a template header up to date, you may
265 -use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
266 +use @command{autoheader} to generate it, see @ref{autoheader}.
269 -@node autoheader Invocation
271 @subsection Using @command{autoheader} to Create @file{config.h.in}
272 @cindex @command{autoheader}
274 @@ -6447,7 +6431,7 @@
275 files will depend upon @command{bizarre-cc} being the C compiler. If
276 for some reason the user runs @command{./configure} again, or if it is
277 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
278 -and @pxref{config.status Invocation}), then the configuration can be
279 +and @pxref{config.status}), then the configuration can be
280 inconsistent, composed of results depending upon two different
283 @@ -6499,7 +6483,7 @@
286 @var{variable} is kept during automatic reconfiguration
287 -(@pxref{config.status Invocation}) as if it had been passed as a command
288 +(@pxref{config.status}) as if it had been passed as a command
289 line argument, including when no cache is used:
292 @@ -7370,11 +7354,11 @@
296 -* autom4te Invocation:: A @acronym{GNU} M4 wrapper
297 +* autom4te:: A @acronym{GNU} M4 wrapper
298 * Customizing autom4te:: Customizing the Autoconf package
301 -@node autom4te Invocation
303 @subsection Invoking @command{autom4te}
305 The command line arguments are modeled after M4's:
306 @@ -7657,7 +7641,7 @@
310 -@xref{autoconf Invocation}, for examples of trace uses.
311 +@xref{autoconf}, for examples of trace uses.
313 @item --preselect=@var{macro}
314 @itemx -p @var{macro}
315 @@ -7727,8 +7711,8 @@
316 wrapped in between a @samp{begin-language: "@var{language}"},
317 @samp{end-language: "@var{language}"} pair.
319 -Customizing a language stands for appending options (@pxref{autom4te
320 -Invocation}) to the current definition of the language. Options, and
321 +Customizing a language stands for appending options (@pxref{autom4te})
322 +to the current definition of the language. Options, and
323 more generally arguments, are introduced by @samp{args:
324 @var{arguments}}. You may use the traditional shell syntax to quote the
326 @@ -8141,7 +8125,7 @@
328 When the user runs @samp{autoconf -W error}, warnings from
329 @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
330 -@ref{autoconf Invocation}.
333 @node Dependencies Between Macros
334 @section Dependencies Between Macros
335 @@ -12054,7 +12038,7 @@
336 * System Type:: Specifying the system type
337 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
338 * Defining Variables:: Specifying the compiler etc.
339 -* configure Invocation:: Changing how @command{configure} runs
340 +* configure:: Changing how @command{configure} runs
344 @@ -12063,7 +12047,7 @@
346 @c ============================================== Recreating a Configuration
348 -@node config.status Invocation
350 @chapter Recreating a Configuration
351 @cindex @command{config.status}
353 @@ -12203,7 +12187,7 @@
355 * Obsolete config.status Use:: Different calling convention
356 * acconfig.h:: Additional entries in @file{config.h.in}
357 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
358 +* autoupdate:: Automatic update of @file{configure.ac}
359 * Obsolete Macros:: Backward compatibility macros
360 * Autoconf 1:: Tips for upgrading your files
361 * Autoconf 2.13:: Some fresher tips
362 @@ -12213,7 +12197,7 @@
363 @section Obsolete @file{config.status} Invocation
365 @file{config.status} now supports arguments to specify the files to
366 -instantiate; see @ref{config.status Invocation}, for more details.
367 +instantiate; see @ref{config.status}, for more details.
368 Before, environment variables had to be used.
370 @defvar CONFIG_COMMANDS
371 @@ -12244,7 +12228,7 @@
372 @file{config.status} ignores this variable.
375 -In @ref{config.status Invocation}, using this old interface, the example
376 +In @ref{config.status}, using this old interface, the example
380 @@ -12318,7 +12302,7 @@
381 self-contained, and should not depend upon @file{acconfig.h} etc.
384 -@node autoupdate Invocation
386 @section Using @command{autoupdate} to Modernize @file{configure.ac}
387 @cindex @command{autoupdate}
389 @@ -13243,7 +13227,7 @@
391 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
392 in a particular package's source directory), you must rename it to
393 -@file{acsite.m4}. @xref{autoconf Invocation}.
394 +@file{acsite.m4}. @xref{autoconf}.
396 If you distribute @file{install.sh} with your package, rename it to
397 @file{install-sh} so @code{make} builtin rules won't inadvertently
398 @@ -13298,7 +13282,7 @@
399 the documentation for them. @xref{Obsolete Macros}, for a table showing the
400 new names for the old macros. Use the @command{autoupdate} program to
401 convert your @file{configure.ac} to using the new macro names.
402 -@xref{autoupdate Invocation}.
405 Some macros have been superseded by similar ones that do the job better,
406 but are not call-compatible. If you get warnings about calling obsolete
407 @@ -13863,7 +13847,7 @@
409 * Using an Autotest Test Suite:: Autotest and the user
410 * Writing testsuite.at:: Autotest macros
411 -* testsuite Invocation:: Running @command{testsuite} scripts
412 +* testsuite:: Running @command{testsuite} scripts
413 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
416 @@ -14125,7 +14109,7 @@
420 -@node testsuite Invocation
422 @section Running @command{testsuite} Scripts
423 @cindex @command{testsuite}
425 @@ -14267,7 +14251,7 @@
426 An Autotest test suite is to be configured in @var{directory}. This
427 macro requires the instantiation of @file{@var{directory}/atconfig} from
428 @file{@var{directory}/atconfig.in}, and sets the default
429 -@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite Invocation}).
430 +@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite}).
434 @@ -14596,7 +14580,7 @@
435 which can be a very long process for complex @file{configure.ac}.
437 This is why all these tools, instead of running directly M4, invoke
438 -@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
439 +@command{autom4te} (@pxref{autom4te}) which, while answering to
440 a specific demand, stores additional information in
441 @file{autom4te.cache} for future runs. For instance, if you run
442 @command{autoconf}, behind the scenes, @command{autom4te} will also
443 --- autoconf-2.57/doc/install.texi.wiget Mon Jul 29 10:20:52 2002
444 +++ autoconf-2.57/doc/install.texi Wed Dec 4 17:25:14 2002
446 overridden in the site shell script).
449 -@node configure Invocation
451 @section @command{configure} Invocation
453 @command{configure} recognizes the following options to control how it
454 --- autoconf-2.57/doc/standards.texi.wiget Sat Nov 23 06:08:33 2002
455 +++ autoconf-2.57/doc/standards.texi Wed Dec 4 17:26:51 2002
457 @set lastupdate November 23, 2002
460 -@dircategory GNU organization
461 +@dircategory Miscellaneous:
463 * Standards: (standards). GNU coding standards.