1 --- autoconf-2.72/doc/autoconf.texi.orig 2023-12-25 17:45:48.441111910 +0100
2 +++ autoconf-2.72/doc/autoconf.texi 2023-12-25 17:49:20.953293966 +0100
3 @@ -225,29 +225,19 @@ entitled ``GNU Free Documentation Licens
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.
45 @@ -290,7 +280,7 @@ entitled ``GNU Free Documentation Licens
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
54 @@ -311,10 +301,10 @@ The GNU Build System
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}
69 @@ -349,7 +339,7 @@ Substitutions in Makefiles
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
78 @@ -468,7 +458,7 @@ M4 Quotation
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
87 @@ -607,13 +597,13 @@ Running @command{configure} Scripts
88 * System Types:: Specifying a 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
103 @@ -638,7 +628,7 @@ Generating Test Suites with Autotest
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
112 @@ -999,7 +989,7 @@ containing @code{#define} directives (@p
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 @@ -1079,10 +1069,10 @@ Makefile.in ---' `->
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 @@ -1098,7 +1088,7 @@ you can use Autoconf template macros to
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 @@ -1397,7 +1387,7 @@ checks for system services
149 -@node autoscan Invocation
151 @section Using @command{autoscan} to Create @file{configure.ac}
152 @cindex @command{autoscan}
154 @@ -1419,7 +1409,7 @@ you need to move such macros manually.
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 @@ -1462,7 +1452,7 @@ Append @var{dir} to the include path. M
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 @@ -1471,8 +1461,7 @@ package. It prints the identifiers that
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 @@ -1494,7 +1483,7 @@ Print a summary of the command line opti
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 @@ -1596,7 +1585,7 @@ just make @var{format} as long as needed
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 @@ -1670,7 +1659,7 @@ AUTOMAKE|:::::|automake|:::::|$missing_d
204 -@node autoreconf Invocation
206 @section Using @command{autoreconf} to Update @command{configure} Scripts
207 @cindex @command{autoreconf}
209 @@ -1709,7 +1698,7 @@ infrastructure to a source package. If
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 @@ -2124,7 +2113,7 @@ this package. @command{configure} will
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 @@ -2379,7 +2368,7 @@ The special value @samp{-} might be used
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 @@ -3340,7 +3329,7 @@ AC_CONFIG_FILES([stamp-h], [echo timesta
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 @@ -3427,7 +3416,7 @@ AC_CONFIG_COMMANDS_PRE(
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 @@ -3469,7 +3458,7 @@ once. Other preprocessor lines, such as
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 @@ -3507,7 +3496,7 @@ config header template. If you are usin
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 @@ -7559,7 +7548,7 @@ abort configure and tell the installer h
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 @@ -8373,10 +8362,8 @@ information other than through the C pre
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 @@ -8547,10 +8534,8 @@ The result of the macro is cached in the
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 @@ -10331,7 +10316,7 @@ dangerous. If for instance the user run
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 @@ -10384,7 +10369,7 @@ to a warning only, but the old value is
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 @@ -11546,11 +11531,11 @@ Yet another great name from Lars J. Aas.
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 @@ -11800,7 +11785,7 @@ newlines in the @samp{separator}), while
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 @@ -11888,8 +11873,8 @@ lines are ignored. Customization is per
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 @@ -23306,7 +23291,7 @@ may use comes with Autoconf.
360 * System Types:: Specifying a 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 @@ -23315,7 +23300,7 @@ may use comes with Autoconf.
370 @c ============================================== config.status Invocation
372 -@node config.status Invocation
374 @chapter config.status Invocation
375 @cindex @command{config.status}
377 @@ -23484,7 +23469,7 @@ understanding how to move to more modern
379 * Obsolete config.status Use:: Obsolete convention for @command{config.status}
380 * acconfig Header:: Additional entries in @file{config.h.in}
381 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
382 +* autoupdate:: Automatic update of @file{configure.ac}
383 * Obsolete Macros:: Backward compatibility macros
384 * Autoconf 1:: Tips for upgrading your files
385 * Autoconf 2.13:: Some fresher tips
386 @@ -23494,7 +23479,7 @@ understanding how to move to more modern
387 @section Obsolete @file{config.status} Invocation
389 @file{config.status} now supports arguments to specify the files to
390 -instantiate; see @ref{config.status Invocation}, for more details.
391 +instantiate; see @ref{config.status}, for more details.
392 Before, environment variables had to be used.
394 @defvar CONFIG_COMMANDS
395 @@ -23525,7 +23510,7 @@ The symbolic links to establish. The de
396 @file{config.status} ignores this variable.
399 -In @ref{config.status Invocation}, using this old interface, the example
400 +In @ref{config.status}, using this old interface, the example
404 @@ -23599,7 +23584,7 @@ Using only the @code{AH_} macros, @file{
405 self-contained, and should not depend upon @file{acconfig.h} etc.
408 -@node autoupdate Invocation
410 @section Using @command{autoupdate} to Modernize @file{configure.ac}
411 @cindex @command{autoupdate}
413 @@ -24836,7 +24821,7 @@ Autoconf distribution.
415 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
416 in a particular package's source directory), you must rename it to
417 -@file{acsite.m4}. @xref{autoconf Invocation}.
418 +@file{acsite.m4}. @xref{autoconf}.
420 If you distribute @file{install.sh} with your package, rename it to
421 @file{install-sh} so @command{make} builtin rules don't inadvertently
422 @@ -24891,7 +24876,7 @@ use the old names, but the new ones are
423 the documentation for them. @xref{Obsolete Macros}, for a table showing the
424 new names for the old macros. Use the @command{autoupdate} program to
425 convert your @file{configure.ac} to using the new macro names.
426 -@xref{autoupdate Invocation}.
429 Some macros have been superseded by similar ones that do the job better,
430 but are not call-compatible. If you get warnings about calling obsolete
431 @@ -25428,7 +25413,7 @@ interactive tool testing, which is proba
433 * Using an Autotest Test Suite:: Autotest and the user
434 * Writing Testsuites:: Autotest macros
435 -* testsuite Invocation:: Running @command{testsuite} scripts
436 +* testsuite:: Running @command{testsuite} scripts
437 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
440 @@ -25490,7 +25475,7 @@ the test group, and they include:
443 @item a debugging script named @file{run} which reruns the test in
444 -@dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation
445 +@dfn{debug mode} (@pxref{testsuite}). The automatic generation
446 of debugging scripts has the purpose of easing the chase for bugs.
448 @item all the files created with @code{AT_DATA}
449 @@ -25762,7 +25747,7 @@ variables or reset them to safe values i
450 @var{shell-code} is only executed if at least one test is going to be
451 run. In particular, it will not be executed if any of the @option{--help},
452 @option{--version}, @option{--list}, or @option{--clean} options are
453 -given to @command{testsuite} (@pxref{testsuite Invocation}).
454 +given to @command{testsuite} (@pxref{testsuite}).
457 @defmac AT_PREPARE_EACH_TEST (@var{shell-code})
458 @@ -25897,8 +25882,7 @@ command substitution (@samp{`}), and bac
462 -@defmac AT_CHECK (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @
463 - @ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
464 +@defmac AT_CHECK (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @@ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
465 @defmacx AT_CHECK_UNQUOTED (@var{commands}, @dvar{status, 0}, @ovar{stdout}, @
466 @ovar{stderr}, @ovar{run-if-fail}, @ovar{run-if-pass})
468 @@ -26058,7 +26042,7 @@ individual unit tests.
472 -@node testsuite Invocation
474 @section Running @command{testsuite} Scripts
475 @cindex @command{testsuite}
477 @@ -26253,7 +26237,7 @@ Invoke @code{AC_CONFIG_TESTDIR} in your
478 An Autotest test suite is to be configured in @var{directory}. This
479 macro causes @file{@var{directory}/atconfig} to be created by
480 @command{config.status} and sets the default @code{AUTOTEST_PATH} to
481 -@var{test-path} (@pxref{testsuite Invocation}).
482 +@var{test-path} (@pxref{testsuite}).
486 @@ -26668,7 +26652,7 @@ check the GNU Build System components th
487 which can be a long process for complex @file{configure.ac}.
489 This is why all these tools, instead of running directly M4, invoke
490 -@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
491 +@command{autom4te} (@pxref{autom4te}) which, while answering to
492 a specific demand, stores additional information in
493 @file{autom4te.cache} for future runs. For instance, if you run
494 @command{autoconf}, behind the scenes, @command{autom4te} also
495 --- autoconf-2.70/doc/install.texi.orig 2020-12-01 15:47:57.000000000 +0100
496 +++ autoconf-2.70/doc/install.texi 2021-01-07 21:58:37.050901476 +0100
498 CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
501 -@node configure Invocation
503 @section @command{configure} Invocation
505 @command{configure} recognizes the following options to control how it
506 --- autoconf-2.72/doc/standards.texi.orig 2023-12-25 17:45:48.491111639 +0100
507 +++ autoconf-2.72/doc/standards.texi 2023-12-25 17:49:44.189834749 +0100
509 @set lastupdate August 17, 2021
512 -@dircategory GNU organization
513 +@dircategory GNU organization:
515 -* Standards: (standards). GNU coding standards.
516 +* Standards: (standards). GNU coding standards
519 @c @setchapternewpage odd