1 --- autoconf-2.70/doc/autoconf.texi.orig 2021-01-07 21:55:44.435169949 +0100
2 +++ autoconf-2.70/doc/autoconf.texi 2021-01-07 21:57:55.634459181 +0100
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 GNU M4 wrapper
83 +* autom4te:: A 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 @@ -1080,10 +1070,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 @@ -1099,7 +1089,7 @@
137 or specialized features, @file{configure.ac} might need to contain some
138 hand-crafted shell commands; see @ref{Portable Shell, , Portable Shell
139 Programming}. The @command{autoscan} program can give you a good start
140 -in writing @file{configure.ac} (@pxref{autoscan Invocation}, for more
141 +in writing @file{configure.ac} (@pxref{autoscan} Invocation, for more
144 @cindex @file{configure.in}
145 @@ -1398,7 +1388,7 @@
149 -@node autoscan Invocation
151 @section Using @command{autoscan} to Create @file{configure.ac}
152 @cindex @command{autoscan}
154 @@ -1420,7 +1410,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 @@ -1463,7 +1453,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 @@ -1472,8 +1462,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 @@ -1495,7 +1484,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 @@ -1597,7 +1586,7 @@
193 The @var{format} is a regular string, with newlines if desired, and
194 several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
195 -@ref{autom4te Invocation}, for details on the @var{format}.
196 +@ref{autom4te}, for details on the @var{format}.
198 @item --initialization
200 @@ -1671,7 +1660,7 @@
204 -@node autoreconf Invocation
206 @section Using @command{autoreconf} to Update @command{configure} Scripts
207 @cindex @command{autoreconf}
209 @@ -1710,7 +1699,7 @@
210 your @file{configure.ac} should invoke @code{AM_GNU_GETTEXT} and
211 one of @code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})} or
212 @code{AM_GNU_GETTEXT_REQUIRE_VERSION(@var{min-gettext-version})}.
213 -@xref{autopoint Invocation, , Invoking the @code{autopoint} Program,
214 +@xref{autopoint, , Invoking the @code{autopoint} Program,
215 gettext, GNU @code{gettext} utilities}, for further details.
218 @@ -2125,7 +2114,7 @@
220 Use of this macro is strongly recommended. It protects against people
221 accidentally specifying the wrong directory with @option{--srcdir}.
222 -@xref{configure Invocation}, for more information.
223 +@xref{configure}, for more information.
226 Packages that use @command{aclocal} to generate @file{aclocal.m4}
227 @@ -2380,7 +2369,7 @@
228 when used in @var{output}, or the standard input when used in the
229 @var{inputs}. You most probably don't need to use this in
230 @file{configure.ac}, but it is convenient when using the command line
231 -interface of @file{./config.status}, see @ref{config.status Invocation},
232 +interface of @file{./config.status}, see @ref{config.status},
235 The @var{inputs} may be absolute or relative file names. In the latter
236 @@ -3341,7 +3330,7 @@
237 so @file{config.status} ensures that @file{config.h} is considered up to
238 date. @xref{Output}, for more information about @code{AC_OUTPUT}.
240 -@xref{config.status Invocation}, for more examples of handling
241 +@xref{config.status}, for more examples of handling
242 configuration-related dependencies.
244 @node Configuration Headers
245 @@ -3428,7 +3417,7 @@
248 * Header Templates:: Input for the configuration headers
249 -* autoheader Invocation:: How to create configuration templates
250 +* autoheader:: How to create configuration templates
251 * Autoheader Macros:: How to specify CPP templates
254 @@ -3470,7 +3459,7 @@
257 Since it is a tedious task to keep a template header up to date, you may
258 -use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
259 +use @command{autoheader} to generate it, see @ref{autoheader}.
261 During the instantiation of the header, each @samp{#undef} line in the
262 template file for each symbol defined by @samp{AC_DEFINE} is changed to an
263 @@ -3508,7 +3497,7 @@
264 probably use @samp{AH_BOTTOM} to append the @samp{#include} directive.
267 -@node autoheader Invocation
269 @subsection Using @command{autoheader} to Create @file{config.h.in}
270 @cindex @command{autoheader}
272 @@ -7630,7 +7619,7 @@
273 And finally, the default for @var{action-if-universal} is to ensure that
274 @samp{WORDS_BIGENDIAN} is defined if and only if a universal build is
275 detected and the current code is big-endian; this default works only if
276 -@command{autoheader} is used (@pxref{autoheader Invocation}).
277 +@command{autoheader} is used (@pxref{autoheader}).
279 If you use this macro without specifying @var{action-if-universal}, you
280 should also use @code{AC_CONFIG_HEADERS}; otherwise
281 @@ -8460,10 +8449,8 @@
282 to call Fortran routines from some language other than C/C++.
285 -@defmac AC_FC_SRCEXT (@var{ext}, @ovar{action-if-success}, @
286 - @dvar{action-if-failure, AC_MSG_FAILURE})
287 -@defmacx AC_FC_PP_SRCEXT (@var{ext}, @ovar{action-if-success}, @
288 - @dvar{action-if-failure, AC_MSG_FAILURE})
289 +@defmac AC_FC_SRCEXT (@var{ext}, @ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
290 +@defmacx AC_FC_PP_SRCEXT (@var{ext}, @ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
292 @acindex{FC_PP_SRCEXT}
293 @caindex fc_srcext_@var{ext}
294 @@ -8634,10 +8621,8 @@
298 -@defmac AC_F77_IMPLICIT_NONE (@ovar{action-if-success}, @
299 - @dvar{action-if-failure, AC_MSG_FAILURE})
300 -@defmacx AC_FC_IMPLICIT_NONE (@ovar{action-if-success}, @
301 - @dvar{action-if-failure, AC_MSG_FAILURE})
302 +@defmac AC_F77_IMPLICIT_NONE (@ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
303 +@defmacx AC_FC_IMPLICIT_NONE (@ovar{action-if-success}, @@dvar{action-if-failure, AC_MSG_FAILURE})
304 @acindex{F77_IMPLICIT_NONE}
305 @acindex{FC_IMPLICIT_NONE}
306 @caindex f77_implicit_none
307 @@ -10266,7 +10251,7 @@
308 files depend upon @command{bizarre-cc} being the C compiler. If
309 for some reason the user runs @command{./configure} again, or if it is
310 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
311 -and @pxref{config.status Invocation}), then the configuration can be
312 +and @pxref{config.status}), then the configuration can be
313 inconsistent, composed of results depending upon two different
316 @@ -10319,7 +10304,7 @@
319 @var{variable} is kept during automatic reconfiguration
320 -(@pxref{config.status Invocation}) as if it had been passed as a command
321 +(@pxref{config.status}) as if it had been passed as a command
322 line argument, including when no cache is used:
325 @@ -11480,11 +11465,11 @@
326 It supports M4 extensions designed for use in tools like Autoconf.
329 -* autom4te Invocation:: A GNU M4 wrapper
330 +* autom4te:: A GNU M4 wrapper
331 * Customizing autom4te:: Customizing the Autoconf package
334 -@node autom4te Invocation
336 @subsection Invoking @command{autom4te}
338 The command line arguments are modeled after M4's:
339 @@ -11734,7 +11719,7 @@
343 -@xref{autoconf Invocation}, for examples of trace uses.
344 +@xref{autoconf}, for examples of trace uses.
346 @item --preselect=@var{macro}
347 @itemx -p @var{macro}
348 @@ -11822,8 +11807,8 @@
349 wrapped in between a @samp{begin-language: "@var{language}"},
350 @samp{end-language: "@var{language}"} pair.
352 -Customizing a language stands for appending options (@pxref{autom4te
353 -Invocation}) to the current definition of the language. Options, and
354 +Customizing a language stands for appending options (@pxref{autom4te})
355 +to the current definition of the language. Options, and
356 more generally arguments, are introduced by @samp{args:
357 @var{arguments}}. You may use the traditional shell syntax to quote the
359 @@ -23211,16 +23196,16 @@
360 * System Type:: Specifying the system type
361 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
362 * Defining Variables:: Specifying the compiler etc.
363 -* configure Invocation:: Changing how @command{configure} runs
364 +* configure:: Changing how @command{configure} runs
368 @include install.texi
371 -@c ============================================== config.status Invocation
372 +@c ============================================== config.status
374 -@node config.status Invocation
376 @chapter config.status Invocation
377 @cindex @command{config.status}
379 @@ -23389,7 +23374,7 @@
381 * Obsolete config.status Use:: Obsolete convention for @command{config.status}
382 * acconfig Header:: Additional entries in @file{config.h.in}
383 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
384 +* autoupdate:: Automatic update of @file{configure.ac}
385 * Obsolete Macros:: Backward compatibility macros
386 * Autoconf 1:: Tips for upgrading your files
387 * Autoconf 2.13:: Some fresher tips
388 @@ -23399,7 +23384,7 @@
389 @section Obsolete @file{config.status} Invocation
391 @file{config.status} now supports arguments to specify the files to
392 -instantiate; see @ref{config.status Invocation}, for more details.
393 +instantiate; see @ref{config.status}, for more details.
394 Before, environment variables had to be used.
396 @defvar CONFIG_COMMANDS
397 @@ -23430,7 +23415,7 @@
398 @file{config.status} ignores this variable.
401 -In @ref{config.status Invocation}, using this old interface, the example
402 +In @ref{config.status}, using this old interface, the example
406 @@ -23504,7 +23489,7 @@
407 self-contained, and should not depend upon @file{acconfig.h} etc.
410 -@node autoupdate Invocation
412 @section Using @command{autoupdate} to Modernize @file{configure.ac}
413 @cindex @command{autoupdate}
415 @@ -24741,7 +24726,7 @@
417 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
418 in a particular package's source directory), you must rename it to
419 -@file{acsite.m4}. @xref{autoconf Invocation}.
420 +@file{acsite.m4}. @xref{autoconf}.
422 If you distribute @file{install.sh} with your package, rename it to
423 @file{install-sh} so @command{make} builtin rules don't inadvertently
424 @@ -24796,7 +24781,7 @@
425 the documentation for them. @xref{Obsolete Macros}, for a table showing the
426 new names for the old macros. Use the @command{autoupdate} program to
427 convert your @file{configure.ac} to using the new macro names.
428 -@xref{autoupdate Invocation}.
431 Some macros have been superseded by similar ones that do the job better,
432 but are not call-compatible. If you get warnings about calling obsolete
433 @@ -25333,7 +25318,7 @@
435 * Using an Autotest Test Suite:: Autotest and the user
436 * Writing Testsuites:: Autotest macros
437 -* testsuite Invocation:: Running @command{testsuite} scripts
438 +* testsuite:: Running @command{testsuite} scripts
439 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
442 @@ -25395,7 +25380,7 @@
445 @item a debugging script named @file{run} which reruns the test in
446 -@dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation
447 +@dfn{debug mode} (@pxref{testsuite}). The automatic generation
448 of debugging scripts has the purpose of easing the chase for bugs.
450 @item all the files created with @code{AT_DATA}
451 @@ -25667,7 +25652,7 @@
452 @var{shell-code} is only executed if at least one test is going to be
453 run. In particular, it will not be executed if any of the @option{--help},
454 @option{--version}, @option{--list}, or @option{--clean} options are
455 -given to @command{testsuite} (@pxref{testsuite Invocation}).
456 +given to @command{testsuite} (@pxref{testsuite}).
459 @defmac AT_PREPARE_EACH_TEST (@var{shell-code})
460 @@ -25802,8 +25787,7 @@
464 -@defmac AT_CHECK (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @
465 - @ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
466 +@defmac AT_CHECK (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @@ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
467 @defmacx AT_CHECK_UNQUOTED (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @
468 @ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
470 @@ -25963,7 +25947,7 @@
474 -@node testsuite Invocation
476 @section Running @command{testsuite} Scripts
477 @cindex @command{testsuite}
479 @@ -26158,7 +26142,7 @@
480 An Autotest test suite is to be configured in @var{directory}. This
481 macro causes @file{@var{directory}/atconfig} to be created by
482 @command{config.status} and sets the default @code{AUTOTEST_PATH} to
483 -@var{test-path} (@pxref{testsuite Invocation}).
484 +@var{test-path} (@pxref{testsuite}).
488 @@ -26572,7 +26556,7 @@
489 which can be a long process for complex @file{configure.ac}.
491 This is why all these tools, instead of running directly M4, invoke
492 -@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
493 +@command{autom4te} (@pxref{autom4te}) which, while answering to
494 a specific demand, stores additional information in
495 @file{autom4te.cache} for future runs. For instance, if you run
496 @command{autoconf}, behind the scenes, @command{autom4te} also
497 --- autoconf-2.70/doc/install.texi.orig 2020-12-01 15:47:57.000000000 +0100
498 +++ autoconf-2.70/doc/install.texi 2021-01-07 21:58:37.050901476 +0100
500 CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
503 -@node configure Invocation
505 @section @command{configure} Invocation
507 @command{configure} recognizes the following options to control how it
508 --- autoconf-2.70/doc/standards.texi.orig 2020-12-02 16:26:23.000000000 +0100
509 +++ autoconf-2.70/doc/standards.texi 2021-01-09 21:01:18.586724643 +0100
511 @set lastupdate June 12, 2020
514 -@dircategory GNU organization
515 +@dircategory GNU organization:
517 -* Standards: (standards). GNU coding standards.
518 +* Standards: (standards). GNU coding standards
521 @c @setchapternewpage odd