1 --- autoconf-2.52/doc/autoconf.texi.orig Tue Jul 17 18:34:55 2001
2 +++ autoconf-2.52/doc/autoconf.texi Wed Jul 18 23:56:19 2001
5 @dircategory Individual utilities
7 -* autoscan: (autoconf)autoscan Invocation.
8 - Semi-automatic @file{configure.ac} writing
9 -* ifnames: (autoconf)ifnames Invocation.
10 - Listing the conditionals in source code
11 -* autoconf: (autoconf)autoconf Invocation.
12 - How to create configuration scripts
13 -* autoreconf: (autoconf)autoreconf Invocation.
14 - Remaking multiple @code{configure} scripts
15 -* configure: (autoconf)configure Invocation.
16 - Configuring a package
17 -* config.status: (autoconf)config.status Invocation.
18 - Recreating a configuration
19 +* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac}
21 +* ifnames: (autoconf)ifnames. Listing the conditionals in source code
22 +* autoconf: (autoconf)autoconf. How to create configuration scripts
23 +* autoreconf: (autoconf)autoreconf. Remaking multiple @code{configure}
25 +* configure: (autoconf)configure. Configuring a package
26 +* config.status: (autoconf)config.status.
27 + Recreating a configuration
32 * Manual Configuration:: Selecting features that can't be guessed
33 * Site Configuration:: Local defaults for @code{configure}
34 * Running configure scripts:: How to use the Autoconf output
35 -* config.status Invocation:: Recreating a configuration
36 +* config.status:: Recreating a configuration
37 * Obsolete Constructs:: Kept for backward compatibility
38 * Questions:: Questions about Autoconf, with answers
39 * History:: History of Autoconf
41 Making @code{configure} Scripts
43 * Writing configure.ac:: What to put in an Autoconf input file
44 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
45 -* ifnames Invocation:: Listing the conditionals in source code
46 -* autoconf Invocation:: How to create configuration scripts
47 -* autoreconf Invocation:: Remaking multiple @code{configure} scripts
48 +* autoscan:: Semi-automatic @file{configure.ac} writing
49 +* ifnames:: Listing the conditionals in source code
50 +* autoconf:: How to create configuration scripts
51 +* autoreconf:: Remaking multiple @code{configure} scripts
53 Writing @file{configure.ac}
56 * System Type:: Specifying the system type
57 * Sharing Defaults:: Setting site-wide defaults for @code{configure}
58 * Environment Variables:: Defining environment variables.
59 -* configure Invocation:: Changing how @code{configure} runs
60 +* configure:: Changing how @code{configure} runs
67 a shell script called @file{config.status} that, when run, will recreate
68 -the files listed above (@pxref{config.status Invocation});
69 +the files listed above (@pxref{config.status});
72 an optional shell script normally called @file{config.cache}
76 * Writing configure.ac:: What to put in an Autoconf input file
77 -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing
78 -* ifnames Invocation:: Listing the conditionals in source code
79 -* autoconf Invocation:: How to create configuration scripts
80 -* autoreconf Invocation:: Remaking multiple @code{configure} scripts
81 +* autoscan:: Semi-automatic @file{configure.ac} writing
82 +* ifnames:: Listing the conditionals in source code
83 +* autoconf:: How to create configuration scripts
84 +* autoreconf:: Remaking multiple @code{configure} scripts
87 -@node Writing configure.ac, autoscan Invocation, Making configure Scripts, Making configure Scripts
88 +@node Writing configure.ac, autoscan, Making configure Scripts, Making configure Scripts
89 @section Writing @file{configure.ac}
91 To produce a @code{configure} script for a software package, create a
93 or specialized features, @file{configure.ac} might need to contain some
94 hand-crafted shell commands; see @ref{Portable Shell}. The
95 @code{autoscan} program can give you a good start in writing
96 -@file{configure.ac} (@pxref{autoscan Invocation}, for more information).
97 +@file{configure.ac} (@pxref{autoscan}, for more information).
99 Previous versions of Autoconf promoted the name @file{configure.in},
100 which is somewhat ambiguous (the tool needed to produce this file is not
105 -@node autoscan Invocation, ifnames Invocation, Writing configure.ac, Making configure Scripts
106 +@node autoscan, ifnames, Writing configure.ac, Making configure Scripts
107 @section Using @code{autoscan} to Create @file{configure.ac}
108 @cindex @code{autoscan}
110 @@ -1009,7 +1006,7 @@
111 use a configuration header file, you must add a call to
112 @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might
113 also have to change or add some @code{#if} directives to your program in
114 -order to make it work with Autoconf (@pxref{ifnames Invocation}, for
115 +order to make it work with Autoconf (@pxref{ifnames}, for
116 information about a program that can help with that job).
118 When using @command{autoscan} to maintain a @file{configure.ac}, simply
119 @@ -1051,7 +1048,7 @@
120 plays with different versions of Autoconf simultaneously.
123 -@node ifnames Invocation, autoconf Invocation, autoscan Invocation, Making configure Scripts
124 +@node ifnames, autoconf, autoscan, Making configure Scripts
125 @section Using @code{ifnames} to List Conditionals
126 @cindex @code{ifnames}
128 @@ -1060,8 +1057,7 @@
129 preprocessor conditionals. If a package has already been set up to have
130 some portability, @code{ifnames} can thus help you figure out what its
131 @code{configure} needs to check for. It may help fill in some gaps in a
132 -@file{configure.ac} generated by @code{autoscan} (@pxref{autoscan
134 +@file{configure.ac} generated by @code{autoscan} (@pxref{autoscan}).
136 @code{ifnames} scans all of the C source files named on the command line
137 (or the standard input, if none are given) and writes to the standard
138 @@ -1083,7 +1079,7 @@
139 Print the version number of Autoconf and exit.
142 -@node autoconf Invocation, autoreconf Invocation, ifnames Invocation, Making configure Scripts
143 +@node autoconf, autoreconf, ifnames, Making configure Scripts
144 @section Using @code{autoconf} to Create @code{configure}
145 @cindex @code{autoconf}
147 @@ -1346,7 +1342,7 @@
151 -@node autoreconf Invocation, , autoconf Invocation, Making configure Scripts
152 +@node autoreconf, , autoconf, Making configure Scripts
153 @section Using @code{autoreconf} to Update @code{configure} Scripts
154 @cindex @code{autoreconf}
156 @@ -1568,8 +1564,8 @@
157 source directory; @code{configure} checks for this file's existence to
158 make sure that the directory that it is told contains the source code in
159 fact does. Occasionally people accidentally specify the wrong directory
160 -with @option{--srcdir}; this is a safety check. @xref{configure
161 -Invocation}, for more information.
162 +with @option{--srcdir}; this is a safety check. @xref{configure},
163 +for more information.
167 @@ -1755,7 +1751,7 @@
168 when used in @var{output}, or the standard input when used in the
169 @var{inputs}. You most probably don't need to use this in
170 @file{configure.ac}, but it is convenient when using the command line
171 -interface of @file{./config.status}, see @ref{config.status Invocation},
172 +interface of @file{./config.status}, see @ref{config.status},
175 The @var{inputs} may be absolute or relative filenames. In the latter
176 @@ -2223,7 +2219,7 @@
177 @file{config.h} is considered up to date. @xref{Output}, for more
178 information about @code{AC_OUTPUT}.
180 -@xref{config.status Invocation}, for more examples of handling
181 +@xref{config.status}, for more examples of handling
182 configuration-related dependencies.
184 @node Configuration Headers, Configuration Commands, Makefile Substitutions, Setup
185 @@ -5621,7 +5617,7 @@
186 files will depend upon @command{bizarre-cc} being the C compiler. If
187 for some reason the user runs @command{/configure} again, or if it is
188 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
189 -and @pxref{config.status Invocation}), then the configuration can be
190 +and @pxref{config.status}), then the configuration can be
191 inconsistent, composed of results depending upon two different
194 @@ -5665,7 +5661,7 @@
197 @var{variable} is kept during automatic reconfiguration
198 -(@pxref{config.status Invocation}) as if it had been passed as a command
199 +(@pxref{config.status}) as if it had been passed as a command
200 line argument, including when no cache is used:
203 @@ -6670,7 +6666,7 @@
205 When the user runs @samp{autoconf -W error}, warnings from
206 @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
207 -@ref{autoconf Invocation}.
210 @node Dependencies Between Macros, Obsoleting Macros, Reporting Messages, Writing Autoconf Macros
211 @section Dependencies Between Macros
212 @@ -9445,7 +9441,7 @@
214 @c ============================================== Running configure Scripts.
216 -@node Running configure scripts, config.status Invocation, Site Configuration, Top
217 +@node Running configure scripts, config.status, Site Configuration, Top
218 @chapter Running @code{configure} Scripts
219 @cindex @code{configure}
221 @@ -9463,7 +9459,7 @@
222 * System Type:: Specifying the system type
223 * Sharing Defaults:: Setting site-wide defaults for @code{configure}
224 * Environment Variables:: Defining environment variables.
225 -* configure Invocation:: Changing how @code{configure} runs
226 +* configure:: Changing how @code{configure} runs
229 @include install.texi
230 @@ -9471,7 +9467,7 @@
232 @c ============================================== Recreating a Configuration
234 -@node config.status Invocation, Obsolete Constructs, Running configure scripts, Top
235 +@node config.status, Obsolete Constructs, Running configure scripts, Top
236 @chapter Recreating a Configuration
237 @cindex @code{config.status}
239 @@ -9590,7 +9586,7 @@
241 @c =================================================== Obsolete Constructs
243 -@node Obsolete Constructs, Questions, config.status Invocation, Top
244 +@node Obsolete Constructs, Questions, config.status, Top
245 @chapter Obsolete Constructs
247 Autoconf changes, and throughout the years some constructs are obsoleted.
248 @@ -9614,7 +9610,7 @@
249 @section Obsolete @file{config.status} Invocation
251 @file{config.status} now supports arguments to specify the files to
252 -instantiate, see @ref{config.status Invocation}, for more details.
253 +instantiate, see @ref{config.status}, for more details.
254 Before, environment variables had to be used.
256 @defvar CONFIG_COMMANDS
257 @@ -9645,7 +9641,7 @@
258 @file{config.status} ignores this variable.
261 -In @ref{config.status Invocation}, using this old interface, the example
262 +In @ref{config.status}, using this old interface, the example
266 @@ -10572,7 +10568,7 @@
268 If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
269 in a particular package's source directory), you must rename it to
270 -@file{acsite.m4}. @xref{autoconf Invocation}.
271 +@file{acsite.m4}. @xref{autoconf}.
273 If you distribute @file{install.sh} with your package, rename it to
274 @file{install-sh} so @code{make} builtin rules won't inadvertently
275 --- autoconf-2.52/doc/install.texi.orig Tue Jul 17 18:34:55 2001
276 +++ autoconf-2.52/doc/install.texi Wed Jul 18 23:53:41 2001
278 overridden in the site shell script).
281 -@node configure Invocation
282 -@section @code{configure} Invocation
284 +@section @code{configure}
286 @code{configure} recognizes the following options to control how it