1 diff -Nur autoconf-2.53.orig/doc/autoconf.texi autoconf-2.53/doc/autoconf.texi
2 --- autoconf-2.53.orig/doc/autoconf.texi Fri Mar 8 13:57:41 2002
3 +++ autoconf-2.53/doc/autoconf.texi Sat Mar 16 12:31:46 2002
8 -@dircategory GNU admin
9 +@dircategory Programming tools:
11 -* Autoconf: (autoconf). Create source code configuration scripts
14 -@dircategory Individual utilities
16 -* autoscan: (autoconf)autoscan Invocation.
17 - Semi-automatic @file{configure.ac} writing
18 -* ifnames: (autoconf)ifnames Invocation.
19 - Listing the conditionals in source code
20 -* autoconf: (autoconf)autoconf Invocation.
21 - How to create configuration scripts
22 -* autoreconf: (autoconf)autoreconf Invocation.
23 - Remaking multiple @command{configure} scripts
24 -* configure: (autoconf)configure Invocation.
25 - Configuring a package
26 -* config.status: (autoconf)config.status Invocation.
27 - Recreating a configuration
28 -* testsuite: (autoconf)testsuite Invocation.
29 - Running an Autotest test suite
30 +* Autoconf: (autoconf). Create source code configuration scripts
31 +* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac} writing
32 +* ifnames: (autoconf)ifnames. Listing the conditionals in source code
33 +* autoconf: (autoconf)autoconf. How to create configuration scripts
34 +* autoreconf: (autoconf)autoreconf. Remaking multiple @command{configure} scripts
35 +* configure: (autoconf)configure. Configuring a package
36 +* config.status: (autoconf)config.status. Recreating a configuration
37 +* testsuite: (autoconf)testsuite. Running an Autotest test suite
42 * Manual Configuration:: Selecting features that can't be guessed
43 * Site Configuration:: Local defaults for @command{configure}
44 * Running configure scripts:: How to use the Autoconf output
45 -* config.status Invocation:: Recreating a configuration
46 +* config.status:: Recreating a configuration
47 * Obsolete Constructs:: Kept for backward compatibility
48 * Using Autotest:: Creating portable test suites
49 * Questions:: Questions about Autoconf, with answers
51 Making @command{configure} Scripts
53 * Writing configure.ac:: What to put in an Autoconf input file
54 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
55 -* ifnames Invocation:: Listing the conditionals in source code
56 -* autoconf Invocation:: How to create configuration scripts
57 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
58 +* autoscan:: Semi-automatic @file{configure.ac} writing
59 +* ifnames:: Listing the conditionals in source code
60 +* autoconf:: How to create configuration scripts
61 +* autoreconf:: Remaking multiple @command{configure} scripts
63 Writing @file{configure.ac}
66 Configuration Header Files
68 * Header Templates:: Input for the configuration headers
69 -* autoheader Invocation:: How to create configuration templates
70 +* autoheader:: How to create configuration templates
71 * Autoheader Macros:: How to specify CPP templates
75 * System Type:: Specifying the system type
76 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
77 * Defining Variables:: Specifying the compiler etc.
78 -* configure Invocation:: Changing how @command{configure} runs
79 +* configure:: Changing how @command{configure} runs
83 * Obsolete config.status Use:: Different calling convention
84 * acconfig.h:: Additional entries in @file{config.h.in}
85 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
86 +* autoupdate:: Automatic update of @file{configure.ac}
87 * Obsolete Macros:: Backward compatibility macros
88 * Autoconf 1:: Tips for upgrading your files
89 * Autoconf 2.13:: Some fresher tips
92 * Using an Autotest Test Suite:: Autotest and the user
93 * Writing testsuite.at:: Autotest macros
94 -* testsuite Invocation:: Running @command{testsuite} scripts
95 +* testsuite:: Running @command{testsuite} scripts
96 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
98 Using an Autotest Test Suite
102 a shell script called @file{config.status} that, when run, will recreate
103 -the files listed above (@pxref{config.status Invocation});
104 +the files listed above (@pxref{config.status});
107 an optional shell script normally called @file{config.cache}
108 @@ -789,10 +778,10 @@
111 * Writing configure.ac:: What to put in an Autoconf input file
112 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
113 -* ifnames Invocation:: Listing the conditionals in source code
114 -* autoconf Invocation:: How to create configuration scripts
115 -* autoreconf Invocation:: Remaking multiple @command{configure} scripts
116 +* autoscan:: Semi-automatic @file{configure.ac} writing
117 +* ifnames:: Listing the conditionals in source code
118 +* autoconf:: How to create configuration scripts
119 +* autoreconf:: Remaking multiple @command{configure} scripts
122 @node Writing configure.ac
124 or specialized features, @file{configure.ac} might need to contain some
125 hand-crafted shell commands; see @ref{Portable Shell}. The
126 @command{autoscan} program can give you a good start in writing
127 -@file{configure.ac} (@pxref{autoscan Invocation}, for more information).
128 +@file{configure.ac} (@pxref{autoscan}, for more information).
130 Previous versions of Autoconf promoted the name @file{configure.in},
131 which is somewhat ambiguous (the tool needed to produce this file is not
132 @@ -1036,7 +1025,7 @@
136 -@node autoscan Invocation
138 @section Using @command{autoscan} to Create @file{configure.ac}
139 @cindex @command{autoscan}
141 @@ -1058,7 +1047,7 @@
142 use a configuration header file, you must add a call to
143 @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might
144 also have to change or add some @code{#if} directives to your program in
145 -order to make it work with Autoconf (@pxref{ifnames Invocation}, for
146 +order to make it work with Autoconf (@pxref{ifnames}, for
147 information about a program that can help with that job).
149 When using @command{autoscan} to maintain a @file{configure.ac}, simply
150 @@ -1094,7 +1083,7 @@
151 accumulate. Directories are browsed from last to first.
154 -@node ifnames Invocation
156 @section Using @command{ifnames} to List Conditionals
157 @cindex @command{ifnames}
159 @@ -1103,8 +1092,7 @@
160 preprocessor conditionals. If a package has already been set up to have
161 some portability, @command{ifnames} can thus help you figure out what its
162 @command{configure} needs to check for. It may help fill in some gaps in a
163 -@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan
165 +@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan}).
167 @command{ifnames} scans all of the C source files named on the command line
168 (or the standard input, if none are given) and writes to the standard
169 @@ -1126,7 +1114,7 @@
170 Print the version number of Autoconf and exit.
173 -@node autoconf Invocation
175 @section Using @command{autoconf} to Create @command{configure}
176 @cindex @command{autoconf}
178 @@ -1383,7 +1371,7 @@
182 -@node autoreconf Invocation
184 @section Using @command{autoreconf} to Update @command{configure} Scripts
185 @cindex @command{autoreconf}
187 @@ -1611,8 +1599,8 @@
188 source directory; @command{configure} checks for this file's existence to
189 make sure that the directory that it is told contains the source code in
190 fact does. Occasionally people accidentally specify the wrong directory
191 -with @option{--srcdir}; this is a safety check. @xref{configure
192 -Invocation}, for more information.
193 +with @option{--srcdir}; this is a safety check. @xref{configure},
194 +for more information.
198 @@ -1778,7 +1766,7 @@
199 when used in @var{output}, or the standard input when used in the
200 @var{inputs}. You most probably don't need to use this in
201 @file{configure.ac}, but it is convenient when using the command line
202 -interface of @file{./config.status}, see @ref{config.status Invocation},
203 +interface of @file{./config.status}, see @ref{config.status},
206 The @var{inputs} may be absolute or relative filenames. In the latter
207 @@ -2350,7 +2338,7 @@
208 @file{config.h} is considered up to date. @xref{Output}, for more
209 information about @code{AC_OUTPUT}.
211 -@xref{config.status Invocation}, for more examples of handling
212 +@xref{config.status}, for more examples of handling
213 configuration-related dependencies.
215 @node Configuration Headers
216 @@ -2411,7 +2399,7 @@
219 * Header Templates:: Input for the configuration headers
220 -* autoheader Invocation:: How to create configuration templates
221 +* autoheader:: How to create configuration templates
222 * Autoheader Macros:: How to specify CPP templates
225 @@ -2462,10 +2450,10 @@
226 @samp{#undef} is strongly discouraged.
228 Since it is a tedious task to keep a template header up to date, you may
229 -use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
230 +use @command{autoheader} to generate it, see @ref{autoheader}.
233 -@node autoheader Invocation
235 @subsection Using @command{autoheader} to Create @file{config.h.in}
236 @cindex @command{autoheader}
238 @@ -5991,7 +5979,7 @@
239 files will depend upon @command{bizarre-cc} being the C compiler. If
240 for some reason the user runs @command{/configure} again, or if it is
241 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
242 -and @pxref{config.status Invocation}), then the configuration can be
243 +and @pxref{config.status}), then the configuration can be
244 inconsistent, composed of results depending upon two different
247 @@ -6035,7 +6023,7 @@
250 @var{variable} is kept during automatic reconfiguration
251 -(@pxref{config.status Invocation}) as if it had been passed as a command
252 +(@pxref{config.status}) as if it had been passed as a command
253 line argument, including when no cache is used:
256 @@ -7162,7 +7150,7 @@
260 -@xref{autoconf Invocation}, for examples of trace uses.
261 +@xref{autoconf}, for examples of trace uses.
263 @item --preselect=@var{macro}
264 @itemx -p @var{macro}
265 @@ -7575,7 +7563,7 @@
267 When the user runs @samp{autoconf -W error}, warnings from
268 @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
269 -@ref{autoconf Invocation}.
272 @node Dependencies Between Macros
273 @section Dependencies Between Macros
274 @@ -10555,7 +10543,7 @@
275 * System Type:: Specifying the system type
276 * Sharing Defaults:: Setting site-wide defaults for @command{configure}
277 * Defining Variables:: Specifying the compiler etc.
278 -* configure Invocation:: Changing how @command{configure} runs
279 +* configure:: Changing how @command{configure} runs
283 @@ -10564,7 +10552,7 @@
285 @c ============================================== Recreating a Configuration
287 -@node config.status Invocation
289 @chapter Recreating a Configuration
290 @cindex @command{config.status}
292 @@ -10698,7 +10686,7 @@
294 * Obsolete config.status Use:: Different calling convention
295 * acconfig.h:: Additional entries in @file{config.h.in}
296 -* autoupdate Invocation:: Automatic update of @file{configure.ac}
297 +* autoupdate:: Automatic update of @file{configure.ac}
298 * Obsolete Macros:: Backward compatibility macros
299 * Autoconf 1:: Tips for upgrading your files
300 * Autoconf 2.13:: Some fresher tips
301 @@ -10708,7 +10696,7 @@
302 @section Obsolete @file{config.status} Invocation
304 @file{config.status} now supports arguments to specify the files to
305 -instantiate, see @ref{config.status Invocation}, for more details.
306 +instantiate, see @ref{config.status}, for more details.
307 Before, environment variables had to be used.
309 @defvar CONFIG_COMMANDS
310 @@ -10739,7 +10727,7 @@
311 @file{config.status} ignores this variable.
314 -In @ref{config.status Invocation}, using this old interface, the example
315 +In @ref{config.status}, using this old interface, the example
319 @@ -10813,7 +10801,7 @@
320 self-contained, and should not depend upon @file{acconfig.h} etc.
323 -@node autoupdate Invocation
325 @section Using @command{autoupdate} to Modernize @file{configure.ac}
326 @cindex @command{autoupdate}
328 @@ -11660,7 +11648,7 @@
330 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
331 in a particular package's source directory), you must rename it to
332 -@file{acsite.m4}. @xref{autoconf Invocation}.
333 +@file{acsite.m4}. @xref{autoconf}.
335 If you distribute @file{install.sh} with your package, rename it to
336 @file{install-sh} so @code{make} builtin rules won't inadvertently
337 @@ -11715,7 +11703,7 @@
338 the documentation for them. @xref{Obsolete Macros}, for a table showing the
339 new names for the old macros. Use the @command{autoupdate} program to
340 convert your @file{configure.ac} to using the new macro names.
341 -@xref{autoupdate Invocation}.
344 Some macros have been superseded by similar ones that do the job better,
345 but are not call-compatible. If you get warnings about calling obsolete
346 @@ -12214,7 +12202,7 @@
348 * Using an Autotest Test Suite:: Autotest and the user
349 * Writing testsuite.at:: Autotest macros
350 -* testsuite Invocation:: Running @command{testsuite} scripts
351 +* testsuite:: Running @command{testsuite} scripts
352 * Making testsuite Scripts:: Using autom4te to create @command{testsuite}
355 @@ -12476,7 +12464,7 @@
359 -@node testsuite Invocation
361 @section Running @command{testsuite} Scripts
362 @cindex @command{testsuite}
364 diff -Nur autoconf-2.53.orig/doc/install.texi autoconf-2.53/doc/install.texi
365 --- autoconf-2.53.orig/doc/install.texi Mon Mar 4 16:11:11 2002
366 +++ autoconf-2.53/doc/install.texi Sat Mar 16 12:32:45 2002
368 overridden in the site shell script).
371 -@node configure Invocation
373 @section @command{configure} Invocation
375 @command{configure} recognizes the following options to control how it
376 diff -Nur autoconf-2.53.orig/doc/standards.texi autoconf-2.53/doc/standards.texi
377 --- autoconf-2.53.orig/doc/standards.texi Fri Nov 2 17:29:03 2001
378 +++ autoconf-2.53/doc/standards.texi Sat Mar 16 12:34:09 2002
383 -START-INFO-DIR-ENTRY
384 -* Standards: (standards). GNU coding standards.
386 +@dircategory Miscellaneous:
388 +* Standards: (standards). GNU coding standards.