]>
Commit | Line | Data |
---|---|---|
7c08ed99 AF |
1 | --- autoconf-2.54/doc/autoconf.texi.wiget Fri Oct 18 10:53:27 2002 |
2 | +++ autoconf-2.54/doc/autoconf.texi Fri Oct 18 11:01:49 2002 | |
2fcb7ba1 JB |
3 | @@ -94,33 +94,19 @@ |
4 | ||
5 | ||
6 | ||
7 | -@dircategory GNU programming tools | |
8 | +@dircategory Programming tools: | |
9 | @direntry | |
10 | -* Autoconf: (autoconf). Create source code configuration scripts | |
11 | -@end direntry | |
12 | - | |
13 | -@dircategory Individual utilities | |
14 | -@direntry | |
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)Invoking autom4te. | |
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 | |
46 | @end direntry | |
47 | ||
48 | @titlepage | |
49 | @@ -160,7 +146,7 @@ | |
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 | |
58 | @@ -180,10 +166,10 @@ | |
59 | Making @command{configure} Scripts | |
60 | ||
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 | |
70 | ||
71 | Writing @file{configure.ac} | |
72 | ||
73 | @@ -216,7 +202,7 @@ | |
74 | Configuration Header Files | |
75 | ||
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 | |
80 | ||
81 | Existing Tests | |
7c08ed99 AF |
82 | @@ -311,7 +297,7 @@ |
83 | Programming in M4 | |
84 | ||
85 | * M4 Quotation:: Protecting macros from unwanted expansion | |
86 | -* Invoking autom4te:: The Autoconf executables backbone | |
87 | +* autom4te:: The Autoconf executables backbone | |
88 | * Programming in M4sugar:: Convenient pure M4 macros | |
89 | * Programming in M4sh:: Common shell constructs | |
90 | ||
2fcb7ba1 JB |
91 | @@ -388,13 +374,13 @@ |
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 | |
97 | ||
98 | Obsolete Constructs | |
99 | ||
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 | |
107 | @@ -418,7 +404,7 @@ | |
108 | ||
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} | |
114 | ||
115 | Using an Autotest Test Suite | |
116 | @@ -729,7 +715,7 @@ | |
117 | ||
118 | @item | |
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}); | |
122 | ||
123 | @item | |
124 | an optional shell script normally called @file{config.cache} | |
125 | @@ -789,10 +775,10 @@ | |
126 | ||
127 | @menu | |
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 | |
137 | @end menu | |
138 | ||
139 | @node Writing configure.ac | |
140 | @@ -808,7 +794,7 @@ | |
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). | |
146 | ||
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 | @@ -1036,7 +1022,7 @@ | |
150 | @end display | |
151 | ||
152 | ||
153 | -@node autoscan Invocation | |
154 | +@node autoscan | |
155 | @section Using @command{autoscan} to Create @file{configure.ac} | |
156 | @cindex @command{autoscan} | |
157 | ||
158 | @@ -1058,7 +1044,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). | |
165 | ||
166 | When using @command{autoscan} to maintain a @file{configure.ac}, simply | |
167 | @@ -1097,7 +1083,7 @@ | |
168 | Prepend @var{dir} to the include path. Multiple invocations accumulate. | |
169 | @end table | |
170 | ||
171 | -@node ifnames Invocation | |
172 | +@node ifnames | |
173 | @section Using @command{ifnames} to List Conditionals | |
174 | @cindex @command{ifnames} | |
175 | ||
176 | @@ -1106,8 +1092,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 | |
181 | -Invocation}). | |
182 | +@file{configure.ac} generated by @command{autoscan} (@pxref{autoscan}). | |
183 | ||
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 | @@ -1129,7 +1114,7 @@ | |
187 | Print the version number of Autoconf and exit. | |
188 | @end table | |
189 | ||
190 | -@node autoconf Invocation | |
191 | +@node autoconf | |
192 | @section Using @command{autoconf} to Create @command{configure} | |
193 | @cindex @command{autoconf} | |
194 | ||
195 | @@ -1389,7 +1374,7 @@ | |
196 | @end group | |
197 | @end example | |
198 | ||
199 | -@node autoreconf Invocation | |
200 | +@node autoreconf | |
201 | @section Using @command{autoreconf} to Update @command{configure} Scripts | |
202 | @cindex @command{autoreconf} | |
203 | ||
204 | @@ -1623,8 +1608,8 @@ | |
205 | source directory; @command{configure} checks for this file's existence to | |
206 | make sure that the directory that it is told contains the source code in | |
207 | fact does. Occasionally people accidentally specify the wrong directory | |
208 | -with @option{--srcdir}; this is a safety check. @xref{configure | |
209 | -Invocation}, for more information. | |
210 | +with @option{--srcdir}; this is a safety check. @xref{configure}, | |
211 | +for more information. | |
212 | @end defmac | |
213 | ||
214 | ||
215 | @@ -1790,7 +1775,7 @@ | |
216 | when used in @var{output}, or the standard input when used in the | |
217 | @var{inputs}. You most probably don't need to use this in | |
218 | @file{configure.ac}, but it is convenient when using the command line | |
219 | -interface of @file{./config.status}, see @ref{config.status Invocation}, | |
220 | +interface of @file{./config.status}, see @ref{config.status}, | |
221 | for more details. | |
222 | ||
223 | The @var{inputs} may be absolute or relative filenames. In the latter | |
224 | @@ -2387,7 +2372,7 @@ | |
225 | @file{config.h} is considered up to date. @xref{Output}, for more | |
226 | information about @code{AC_OUTPUT}. | |
227 | ||
228 | -@xref{config.status Invocation}, for more examples of handling | |
229 | +@xref{config.status}, for more examples of handling | |
230 | configuration-related dependencies. | |
231 | ||
232 | @node Configuration Headers | |
233 | @@ -2448,7 +2433,7 @@ | |
234 | ||
235 | @menu | |
236 | * Header Templates:: Input for the configuration headers | |
237 | -* autoheader Invocation:: How to create configuration templates | |
238 | +* autoheader:: How to create configuration templates | |
239 | * Autoheader Macros:: How to specify CPP templates | |
240 | @end menu | |
241 | ||
242 | @@ -2499,10 +2484,10 @@ | |
243 | @samp{#undef} is strongly discouraged. | |
244 | ||
245 | Since it is a tedious task to keep a template header up to date, you may | |
246 | -use @command{autoheader} to generate it, see @ref{autoheader Invocation}. | |
247 | +use @command{autoheader} to generate it, see @ref{autoheader}. | |
248 | ||
249 | ||
250 | -@node autoheader Invocation | |
251 | +@node autoheader | |
252 | @subsection Using @command{autoheader} to Create @file{config.h.in} | |
253 | @cindex @command{autoheader} | |
254 | ||
255 | @@ -6215,7 +6200,7 @@ | |
256 | files will depend upon @command{bizarre-cc} being the C compiler. If | |
257 | for some reason the user runs @command{./configure} again, or if it is | |
258 | run via @samp{./config.status --recheck}, (@xref{Automatic Remaking}, | |
259 | -and @pxref{config.status Invocation}), then the configuration can be | |
260 | +and @pxref{config.status}), then the configuration can be | |
261 | inconsistent, composed of results depending upon two different | |
262 | compilers. | |
263 | ||
264 | @@ -6267,7 +6252,7 @@ | |
265 | ||
266 | @item | |
267 | @var{variable} is kept during automatic reconfiguration | |
268 | -(@pxref{config.status Invocation}) as if it had been passed as a command | |
269 | +(@pxref{config.status}) as if it had been passed as a command | |
270 | line argument, including when no cache is used: | |
271 | ||
272 | @example | |
7c08ed99 AF |
273 | @@ -6608,7 +6593,7 @@ |
274 | ||
275 | @menu | |
276 | * M4 Quotation:: Protecting macros from unwanted expansion | |
277 | -* Invoking autom4te:: The Autoconf executables backbone | |
278 | +* autom4te:: The Autoconf executables backbone | |
279 | * Programming in M4sugar:: Convenient pure M4 macros | |
280 | * Programming in M4sh:: Common shell Constructs | |
281 | @end menu | |
282 | @@ -7111,7 +7096,7 @@ | |
283 | unexpanded macros. The @command{autoconf} program checks for this problem | |
284 | by doing @samp{grep AC_ configure}. | |
285 | ||
286 | -@node Invoking autom4te | |
287 | +@node autom4te | |
288 | @section Invoking @command{autom4te} | |
289 | ||
290 | The Autoconf suite, including M4sugar, M4sh, and Autotest, in addition to | |
2fcb7ba1 JB |
291 | @@ -7394,7 +7379,7 @@ |
292 | not. | |
293 | @end table | |
294 | ||
295 | -@xref{autoconf Invocation}, for examples of trace uses. | |
296 | +@xref{autoconf}, for examples of trace uses. | |
297 | ||
298 | @item --preselect=@var{macro} | |
299 | @itemx -p @var{macro} | |
300 | @@ -7845,7 +7830,7 @@ | |
301 | ||
302 | When the user runs @samp{autoconf -W error}, warnings from | |
303 | @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see | |
304 | -@ref{autoconf Invocation}. | |
305 | +@ref{autoconf}. | |
306 | ||
307 | @node Dependencies Between Macros | |
308 | @section Dependencies Between Macros | |
309 | @@ -11642,7 +11627,7 @@ | |
310 | * System Type:: Specifying the system type | |
311 | * Sharing Defaults:: Setting site-wide defaults for @command{configure} | |
312 | * Defining Variables:: Specifying the compiler etc. | |
313 | -* configure Invocation:: Changing how @command{configure} runs | |
314 | +* configure:: Changing how @command{configure} runs | |
315 | @end menu | |
316 | ||
317 | @set autoconf | |
318 | @@ -11651,7 +11636,7 @@ | |
319 | ||
320 | @c ============================================== Recreating a Configuration | |
321 | ||
322 | -@node config.status Invocation | |
323 | +@node config.status | |
324 | @chapter Recreating a Configuration | |
325 | @cindex @command{config.status} | |
326 | ||
327 | @@ -11785,7 +11770,7 @@ | |
328 | @menu | |
329 | * Obsolete config.status Use:: Different calling convention | |
330 | * acconfig.h:: Additional entries in @file{config.h.in} | |
331 | -* autoupdate Invocation:: Automatic update of @file{configure.ac} | |
332 | +* autoupdate:: Automatic update of @file{configure.ac} | |
333 | * Obsolete Macros:: Backward compatibility macros | |
334 | * Autoconf 1:: Tips for upgrading your files | |
335 | * Autoconf 2.13:: Some fresher tips | |
336 | @@ -11795,7 +11780,7 @@ | |
337 | @section Obsolete @file{config.status} Invocation | |
338 | ||
339 | @file{config.status} now supports arguments to specify the files to | |
340 | -instantiate; see @ref{config.status Invocation}, for more details. | |
341 | +instantiate; see @ref{config.status}, for more details. | |
342 | Before, environment variables had to be used. | |
343 | ||
344 | @defvar CONFIG_COMMANDS | |
345 | @@ -11826,7 +11811,7 @@ | |
346 | @file{config.status} ignores this variable. | |
347 | @end defvar | |
348 | ||
349 | -In @ref{config.status Invocation}, using this old interface, the example | |
350 | +In @ref{config.status}, using this old interface, the example | |
351 | would be: | |
352 | ||
353 | @example | |
354 | @@ -11900,7 +11885,7 @@ | |
355 | self-contained, and should not depend upon @file{acconfig.h} etc. | |
356 | ||
357 | ||
358 | -@node autoupdate Invocation | |
359 | +@node autoupdate | |
360 | @section Using @command{autoupdate} to Modernize @file{configure.ac} | |
361 | @cindex @command{autoupdate} | |
362 | ||
363 | @@ -12750,7 +12735,7 @@ | |
364 | ||
365 | If you have an @file{aclocal.m4} installed with Autoconf (as opposed to | |
366 | in a particular package's source directory), you must rename it to | |
367 | -@file{acsite.m4}. @xref{autoconf Invocation}. | |
368 | +@file{acsite.m4}. @xref{autoconf}. | |
369 | ||
370 | If you distribute @file{install.sh} with your package, rename it to | |
371 | @file{install-sh} so @code{make} builtin rules won't inadvertently | |
372 | @@ -12805,7 +12790,7 @@ | |
373 | the documentation for them. @xref{Obsolete Macros}, for a table showing the | |
374 | new names for the old macros. Use the @command{autoupdate} program to | |
375 | convert your @file{configure.ac} to using the new macro names. | |
376 | -@xref{autoupdate Invocation}. | |
377 | +@xref{autoupdate}. | |
378 | ||
379 | Some macros have been superseded by similar ones that do the job better, | |
380 | but are not call-compatible. If you get warnings about calling obsolete | |
381 | @@ -13302,7 +13287,7 @@ | |
382 | @menu | |
383 | * Using an Autotest Test Suite:: Autotest and the user | |
384 | * Writing testsuite.at:: Autotest macros | |
385 | -* testsuite Invocation:: Running @command{testsuite} scripts | |
386 | +* testsuite:: Running @command{testsuite} scripts | |
387 | * Making testsuite Scripts:: Using autom4te to create @command{testsuite} | |
388 | @end menu | |
389 | ||
390 | @@ -13564,7 +13549,7 @@ | |
391 | @end defmac | |
392 | ||
393 | ||
394 | -@node testsuite Invocation | |
395 | +@node testsuite | |
396 | @section Running @command{testsuite} Scripts | |
397 | @cindex @command{testsuite} | |
398 | ||
399 | @@ -13706,7 +13691,7 @@ | |
400 | An Autotest test suite is to be configured in @var{directory}. This | |
401 | macro requires the instantiation of @file{@var{directory}/atconfig} from | |
402 | @file{@var{directory}/atconfig.in}, and sets the default | |
403 | -@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite Invocation}). | |
404 | +@code{AUTOTEST_PATH} to @var{test-path} (@pxref{testsuite}). | |
405 | @end defmac | |
406 | ||
407 | @item | |
7c08ed99 AF |
408 | --- autoconf-2.54/doc/install.texi.wiget Tue Aug 27 10:28:06 2002 |
409 | +++ autoconf-2.54/doc/install.texi Fri Oct 18 10:53:29 2002 | |
2fcb7ba1 JB |
410 | @@ -225,7 +225,7 @@ |
411 | overridden in the site shell script). | |
412 | ||
413 | ||
414 | -@node configure Invocation | |
415 | +@node configure | |
416 | @section @command{configure} Invocation | |
417 | ||
418 | @command{configure} recognizes the following options to control how it | |
7c08ed99 AF |
419 | --- autoconf-2.54/doc/standards.texi.wiget Wed Apr 10 10:13:19 2002 |
420 | +++ autoconf-2.54/doc/standards.texi Fri Oct 18 10:53:29 2002 | |
421 | @@ -8,9 +8,10 @@ | |
422 | ||
423 | @ifinfo | |
424 | @format | |
425 | -START-INFO-DIR-ENTRY | |
426 | -* Standards: (standards). GNU coding standards. | |
427 | -END-INFO-DIR-ENTRY | |
428 | +@dircategory Miscellaneous: | |
429 | +@direntry | |
430 | +* Standards: (standards). GNU coding standards. | |
431 | +@end direntry | |
432 | @end format | |
433 | @end ifinfo | |
434 |