1 --- autoconf-2.63/doc/autoconf.texi.orig 2008-09-10 17:43:06.324991499 +0200
2 +++ autoconf-2.63/doc/autoconf.texi 2008-09-10 17:43:06.468990661 +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-invocation: (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 Autoconf Input:: 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:: Obsolete convention for @command{config.status}
97 * acconfig Header:: 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 Testsuites:: 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 @@ -1008,10 +998,10 @@
124 * Writing Autoconf Input:: 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 Autoconf Input
136 @@ -1027,7 +1017,7 @@
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 @@ -1283,7 +1273,7 @@
149 -@node autoscan Invocation
151 @section Using @command{autoscan} to Create @file{configure.ac}
152 @cindex @command{autoscan}
154 @@ -1305,7 +1295,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 @@ -1348,7 +1338,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 @@ -1357,8 +1347,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 @@ -1380,7 +1369,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 @@ -1474,8 +1463,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 @@ -1487,7 +1475,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 @@ -1561,7 +1549,7 @@
214 -@node autoreconf Invocation
216 @section Using @command{autoreconf} to Update @command{configure} Scripts
217 @cindex @command{autoreconf}
219 @@ -1598,8 +1586,8 @@
220 Gettext supplies the @command{autopoint} command to add translation
221 infrastructure to a source package. If you use @command{autopoint},
222 your @file{configure.ac} should invoke both @code{AM_GNU_GETTEXT} and
223 -@code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})}. @xref{autopoint
224 -Invocation, , Invoking the @code{autopoint} Program, gettext,
225 +@code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})}.
226 +@xref{autopoint, , Invoking the @code{autopoint} Program, gettext,
227 @acronym{GNU} @code{gettext} utilities}, for further details.
230 @@ -1914,8 +1902,8 @@
231 source directory; @command{configure} checks for this file's existence to
232 make sure that the directory that it is told contains the source code in
233 fact does. Occasionally people accidentally specify the wrong directory
234 -with @option{--srcdir}; this is a safety check. @xref{configure
235 -Invocation}, for more information.
236 +with @option{--srcdir}; this is a safety check. @xref{configure},
237 +for more information.
241 @@ -2128,7 +2116,7 @@
242 when used in @var{output}, or the standard input when used in the
243 @var{inputs}. You most probably don't need to use this in
244 @file{configure.ac}, but it is convenient when using the command line
245 -interface of @file{./config.status}, see @ref{config.status Invocation},
246 +interface of @file{./config.status}, see @ref{config.status},
249 The @var{inputs} may be absolute or relative file names. In the latter
250 @@ -2991,7 +2979,7 @@
251 so @file{config.status} ensures that @file{config.h} is considered up to
252 date. @xref{Output}, for more information about @code{AC_OUTPUT}.
254 -@xref{config.status Invocation}, for more examples of handling
255 +@xref{config.status}, for more examples of handling
256 configuration-related dependencies.
258 @node Configuration Headers
259 @@ -3071,7 +3059,7 @@
262 * Header Templates:: Input for the configuration headers
263 -* autoheader Invocation:: How to create configuration templates
264 +* autoheader:: How to create configuration templates
265 * Autoheader Macros:: How to specify CPP templates
268 @@ -3113,7 +3101,7 @@
271 Since it is a tedious task to keep a template header up to date, you may
272 -use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
273 +use @command{autoheader} to generate it, see @ref{autoheader}.
275 During the instantiation of the header, each @samp{#undef} line in the
276 template file for each symbol defined by @samp{AC_DEFINE} is changed to an
277 @@ -3151,7 +3139,7 @@
278 probably use @samp{AH_BOTTOM} to append the @samp{#include} directive.
281 -@node autoheader Invocation
283 @subsection Using @command{autoheader} to Create @file{config.h.in}
284 @cindex @command{autoheader}
286 @@ -6801,7 +6789,7 @@
287 And finally, the default for @var{action-if-universal} is to ensure that
288 @samp{WORDS_BIGENDIAN} is defined if and only if a universal build is
289 detected and the current code is big-endian; this default works only if
290 -@command{autoheader} is used (@pxref{autoheader Invocation}).
291 +@command{autoheader} is used (@pxref{autoheader}).
293 If you use this macro without specifying @var{action-if-universal}, you
294 should also use @code{AC_CONFIG_HEADERS}; otherwise
295 @@ -8794,7 +8782,7 @@
296 files depend upon @command{bizarre-cc} being the C compiler. If
297 for some reason the user runs @command{./configure} again, or if it is
298 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
299 -and @pxref{config.status Invocation}), then the configuration can be
300 +and @pxref{config.status}), then the configuration can be
301 inconsistent, composed of results depending upon two different
304 @@ -8847,7 +8835,7 @@
307 @var{variable} is kept during automatic reconfiguration
308 -(@pxref{config.status Invocation}) as if it had been passed as a command
309 +(@pxref{config.status}) as if it had been passed as a command
310 line argument, including when no cache is used:
313 @@ -9856,11 +9844,11 @@
314 It supports M4 extensions designed for use in tools like Autoconf.
317 -* autom4te Invocation:: A @acronym{GNU} M4 wrapper
318 +* autom4te:: A @acronym{GNU} M4 wrapper
319 * Customizing autom4te:: Customizing the Autoconf package
322 -@node autom4te Invocation
324 @subsection Invoking @command{autom4te}
326 The command line arguments are modeled after M4's:
327 @@ -10118,7 +10106,7 @@
331 -@xref{autoconf Invocation}, for examples of trace uses.
332 +@xref{autoconf}, for examples of trace uses.
334 @item --preselect=@var{macro}
335 @itemx -p @var{macro}
336 @@ -10206,8 +10194,8 @@
337 wrapped in between a @samp{begin-language: "@var{language}"},
338 @samp{end-language: "@var{language}"} pair.
340 -Customizing a language stands for appending options (@pxref{autom4te
341 -Invocation}) to the current definition of the language. Options, and
342 +Customizing a language stands for appending options (@pxref{autom4te})
343 +to the current definition of the language. Options, and
344 more generally arguments, are introduced by @samp{args:
345 @var{arguments}}. You may use the traditional shell syntax to quote the
347 @@ -12175,7 +12163,7 @@
349 When the user runs @samp{autoconf -W error}, warnings from
350 @code{m4_warn} (including those issued through @code{AC_DIAGNOSE} and
351 -@code{AC_WARNING}) are reported as errors, see @ref{autoconf Invocation}.
352 +@code{AC_WARNING}) are reported as errors, see @ref{autoconf}.
354 @node Dependencies Between Macros
355 @section Dependencies Between Macros
356 @@ -18580,16 +18568,16 @@
357 * System Type:: Specifying the system type
358 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
359 * Defining Variables:: Specifying the compiler etc.
360 -* configure Invocation:: Changing how @command{configure} runs
361 +* configure:: Changing how @command{configure} runs
365 @include install.texi
368 -@c ============================================== config.status Invocation
369 +@c ============================================== config.status
371 -@node config.status Invocation
373 @chapter config.status Invocation
374 @cindex @command{config.status}
376 @@ -18735,7 +18723,7 @@
378 * Obsolete config.status Use:: Obsolete convention for @command{config.status}
379 * acconfig Header:: Additional entries in @file{config.h.in}
380 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
381 +* autoupdate:: Automatic update of @file{configure.ac}
382 * Obsolete Macros:: Backward compatibility macros
383 * Autoconf 1:: Tips for upgrading your files
384 * Autoconf 2.13:: Some fresher tips
385 @@ -18745,7 +18733,7 @@
386 @section Obsolete @file{config.status} Invocation
388 @file{config.status} now supports arguments to specify the files to
389 -instantiate; see @ref{config.status Invocation}, for more details.
390 +instantiate; see @ref{config.status}, for more details.
391 Before, environment variables had to be used.
393 @defvar CONFIG_COMMANDS
394 @@ -18776,7 +18764,7 @@
395 @file{config.status} ignores this variable.
398 -In @ref{config.status Invocation}, using this old interface, the example
399 +In @ref{config.status}, using this old interface, the example
403 @@ -18850,7 +18838,7 @@
404 self-contained, and should not depend upon @file{acconfig.h} etc.
407 -@node autoupdate Invocation
409 @section Using @command{autoupdate} to Modernize @file{configure.ac}
410 @cindex @command{autoupdate}
412 @@ -20028,7 +20016,7 @@
414 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
415 in a particular package's source directory), you must rename it to
416 -@file{acsite.m4}. @xref{autoconf Invocation}.
417 +@file{acsite.m4}. @xref{autoconf}.
419 If you distribute @file{install.sh} with your package, rename it to
420 @file{install-sh} so @command{make} builtin rules don't inadvertently
421 @@ -20083,7 +20071,7 @@
422 the documentation for them. @xref{Obsolete Macros}, for a table showing the
423 new names for the old macros. Use the @command{autoupdate} program to
424 convert your @file{configure.ac} to using the new macro names.
425 -@xref{autoupdate Invocation}.
428 Some macros have been superseded by similar ones that do the job better,
429 but are not call-compatible. If you get warnings about calling obsolete
430 @@ -20619,7 +20607,7 @@
432 * Using an Autotest Test Suite:: Autotest and the user
433 * Writing Testsuites:: Autotest macros
434 -* testsuite Invocation:: Running @command{testsuite} scripts
435 +* testsuite:: Running @command{testsuite} scripts
436 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
439 @@ -20681,7 +20669,7 @@
442 @item a debugging script named @file{run} which reruns the test in
443 -@dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation
444 +@dfn{debug mode} (@pxref{testsuite}). The automatic generation
445 of debugging scripts has the purpose of easing the chase for bugs.
447 @item all the files created with @code{AT_DATA}
448 @@ -20943,7 +20931,7 @@
452 -@node testsuite Invocation
454 @section Running @command{testsuite} Scripts
455 @cindex @command{testsuite}
457 @@ -21115,7 +21103,7 @@
458 An Autotest test suite is to be configured in @var{directory}. This
459 macro requires the instantiation of @file{@var{directory}/atconfig} from
460 @file{@var{directory}/atconfig.in}, and sets the default
461 -@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite Invocation}).
462 +@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite}).
466 @@ -21469,7 +21457,7 @@
467 which can be a long process for complex @file{configure.ac}.
469 This is why all these tools, instead of running directly M4, invoke
470 -@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
471 +@command{autom4te} (@pxref{autom4te}) which, while answering to
472 a specific demand, stores additional information in
473 @file{autom4te.cache} for future runs. For instance, if you run
474 @command{autoconf}, behind the scenes, @command{autom4te} also
475 --- autoconf-2.62/doc/install.texi.orig 2007-12-08 14:58:52.000000000 +0100
476 +++ autoconf-2.62/doc/install.texi 2008-04-16 20:34:45.697178391 +0200
478 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
481 -@node configure Invocation
483 @section @command{configure} Invocation
485 @command{configure} recognizes the following options to control how it
486 --- autoconf-2.62/doc/standards.texi.orig 2008-04-04 15:16:45.000000000 +0200
487 +++ autoconf-2.62/doc/standards.texi 2008-04-16 20:39:27.317224488 +0200
489 @set lastupdate February 23, 2008
492 -@dircategory GNU organization
493 +@dircategory Miscellaneous:
495 -* Standards: (standards). GNU coding standards.
496 +* Standards: (standards). GNU coding standards
499 @c @setchapternewpage odd