1 |
|
Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, |
2 |
|
Inc. |
3 |
|
|
4 |
|
This file is free documentation; the Free Software Foundation gives |
5 |
|
unlimited permission to copy, distribute and modify it. |
6 |
|
|
7 |
Basic Installation |
Basic Installation |
8 |
================== |
================== |
9 |
|
|
14 |
those values to create a `Makefile' in each directory of the package. |
those values to create a `Makefile' in each directory of the package. |
15 |
It may also create one or more `.h' files containing system-dependent |
It may also create one or more `.h' files containing system-dependent |
16 |
definitions. Finally, it creates a shell script `config.status' that |
definitions. Finally, it creates a shell script `config.status' that |
17 |
you can run in the future to recreate the current configuration, a file |
you can run in the future to recreate the current configuration, and a |
18 |
`config.cache' that saves the results of its tests to speed up |
file `config.log' containing compiler output (useful mainly for |
19 |
reconfiguring, and a file `config.log' containing compiler output |
debugging `configure'). |
20 |
(useful mainly for debugging `configure'). |
|
21 |
|
It can also use an optional file (typically called `config.cache' |
22 |
|
and enabled with `--cache-file=config.cache' or simply `-C') that saves |
23 |
|
the results of its tests to speed up reconfiguring. (Caching is |
24 |
|
disabled by default to prevent problems with accidental use of stale |
25 |
|
cache files.) |
26 |
|
|
27 |
If you need to do unusual things to compile the package, please try |
If you need to do unusual things to compile the package, please try |
28 |
to figure out how `configure' could check whether to do them, and mail |
to figure out how `configure' could check whether to do them, and mail |
29 |
diffs or instructions to the address given in the `README' so they can |
diffs or instructions to the address given in the `README' so they can |
30 |
be considered for the next release. If at some point `config.cache' |
be considered for the next release. If you are using the cache, and at |
31 |
contains results you don't want to keep, you may remove or edit it. |
some point `config.cache' contains results you don't want to keep, you |
32 |
|
may remove or edit it. |
33 |
The file `configure.in' is used to create `configure' by a program |
|
34 |
called `autoconf'. You only need `configure.in' if you want to change |
The file `configure.ac' (or `configure.in') is used to create |
35 |
it or regenerate `configure' using a newer version of `autoconf'. |
`configure' by a program called `autoconf'. You only need |
36 |
|
`configure.ac' if you want to change it or regenerate `configure' using |
37 |
|
a newer version of `autoconf'. |
38 |
|
|
39 |
The simplest way to compile this package is: |
The simplest way to compile this package is: |
40 |
|
|
68 |
===================== |
===================== |
69 |
|
|
70 |
Some systems require unusual options for compilation or linking that |
Some systems require unusual options for compilation or linking that |
71 |
the `configure' script does not know about. You can give `configure' |
the `configure' script does not know about. Run `./configure --help' |
72 |
initial values for variables by setting them in the environment. Using |
for details on some of the pertinent environment variables. |
|
a Bourne-compatible shell, you can do that on the command line like |
|
|
this: |
|
|
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure |
|
73 |
|
|
74 |
Or on systems that have the `env' program, you can do it like this: |
You can give `configure' initial values for variables by setting |
75 |
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure |
them in the environment. You can do that on the command line like this: |
76 |
|
|
77 |
|
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix |
78 |
|
|
79 |
|
*Note Defining Variables::, for more details. |
80 |
|
|
81 |
Compiling For Multiple Architectures |
Compiling For Multiple Architectures |
82 |
==================================== |
==================================== |
89 |
the `configure' script. `configure' automatically checks for the |
the `configure' script. `configure' automatically checks for the |
90 |
source code in the directory that `configure' is in and in `..'. |
source code in the directory that `configure' is in and in `..'. |
91 |
|
|
92 |
If you have to use a `make' that does not supports the `VPATH' |
If you have to use a `make' that does not support the `VPATH' |
93 |
variable, you have to compile the package for one architecture at a time |
variable, you have to compile the package for one architecture at a |
94 |
in the source code directory. After you have installed the package for |
time in the source code directory. After you have installed the |
95 |
one architecture, use `make distclean' before reconfiguring for another |
package for one architecture, use `make distclean' before reconfiguring |
96 |
architecture. |
for another architecture. |
97 |
|
|
98 |
Installation Names |
Installation Names |
99 |
================== |
================== |
136 |
Specifying the System Type |
Specifying the System Type |
137 |
========================== |
========================== |
138 |
|
|
139 |
There may be some features `configure' can not figure out |
There may be some features `configure' cannot figure out |
140 |
automatically, but needs to determine by the type of host the package |
automatically, but needs to determine by the type of host the package |
141 |
will run on. Usually `configure' can figure that out, but if it prints |
will run on. Usually `configure' can figure that out, but if it prints |
142 |
a message saying it can not guess the host type, give it the |
a message saying it cannot guess the host type, give it the |
143 |
`--host=TYPE' option. TYPE can either be a short name for the system |
`--build=TYPE' option. TYPE can either be a short name for the system |
144 |
type, such as `sun4', or a canonical name with three fields: |
type, such as `sun4', or a canonical name which has the form: |
145 |
|
|
146 |
CPU-COMPANY-SYSTEM |
CPU-COMPANY-SYSTEM |
147 |
|
|
148 |
See the file `config.sub' for the possible values of each field. If |
where SYSTEM can have one of these forms: |
149 |
|
|
150 |
|
OS KERNEL-OS |
151 |
|
|
152 |
|
See the file `config.sub' for the possible values of each field. If |
153 |
`config.sub' isn't included in this package, then this package doesn't |
`config.sub' isn't included in this package, then this package doesn't |
154 |
need to know the host type. |
need to know the host type. |
155 |
|
|
156 |
If you are building compiler tools for cross-compiling, you can also |
If you are _building_ compiler tools for cross-compiling, you should |
157 |
use the `--target=TYPE' option to select the type of system they will |
use the `--target=TYPE' option to select the type of system they will |
158 |
produce code for and the `--build=TYPE' option to select the type of |
produce code for. |
159 |
system on which you are compiling the package. |
|
160 |
|
If you want to _use_ a cross compiler, that generates code for a |
161 |
|
platform different from the build platform, you should specify the host |
162 |
|
platform (i.e., that on which the generated programs will eventually be |
163 |
|
run) with `--host=TYPE'. In this case, you should also specify the |
164 |
|
build platform with `--build=TYPE', because, in this case, it may not |
165 |
|
be possible to guess the build platform (it sometimes involves |
166 |
|
compiling and running simple test programs, and this can't be done if |
167 |
|
the compiler is a cross compiler). |
168 |
|
|
169 |
Sharing Defaults |
Sharing Defaults |
170 |
================ |
================ |
177 |
`CONFIG_SITE' environment variable to the location of the site script. |
`CONFIG_SITE' environment variable to the location of the site script. |
178 |
A warning: not all `configure' scripts look for a site script. |
A warning: not all `configure' scripts look for a site script. |
179 |
|
|
180 |
Operation Controls |
Defining Variables |
181 |
================== |
================== |
182 |
|
|
183 |
|
Variables not defined in a site shell script can be set in the |
184 |
|
environment passed to `configure'. However, some packages may run |
185 |
|
configure again during the build, and the customized values of these |
186 |
|
variables may be lost. In order to avoid this problem, you should set |
187 |
|
them in the `configure' command line, using `VAR=value'. For example: |
188 |
|
|
189 |
|
./configure CC=/usr/local2/bin/gcc |
190 |
|
|
191 |
|
will cause the specified gcc to be used as the C compiler (unless it is |
192 |
|
overridden in the site shell script). |
193 |
|
|
194 |
|
`configure' Invocation |
195 |
|
====================== |
196 |
|
|
197 |
`configure' recognizes the following options to control how it |
`configure' recognizes the following options to control how it |
198 |
operates. |
operates. |
199 |
|
|
|
`--cache-file=FILE' |
|
|
Use and save the results of the tests in FILE instead of |
|
|
`./config.cache'. Set FILE to `/dev/null' to disable caching, for |
|
|
debugging `configure'. |
|
|
|
|
200 |
`--help' |
`--help' |
201 |
|
`-h' |
202 |
Print a summary of the options to `configure', and exit. |
Print a summary of the options to `configure', and exit. |
203 |
|
|
204 |
|
`--version' |
205 |
|
`-V' |
206 |
|
Print the version of Autoconf used to generate the `configure' |
207 |
|
script, and exit. |
208 |
|
|
209 |
|
`--cache-file=FILE' |
210 |
|
Enable the cache: use and save the results of the tests in FILE, |
211 |
|
traditionally `config.cache'. FILE defaults to `/dev/null' to |
212 |
|
disable caching. |
213 |
|
|
214 |
|
`--config-cache' |
215 |
|
`-C' |
216 |
|
Alias for `--cache-file=config.cache'. |
217 |
|
|
218 |
`--quiet' |
`--quiet' |
219 |
`--silent' |
`--silent' |
220 |
`-q' |
`-q' |
226 |
Look for the package's source code in directory DIR. Usually |
Look for the package's source code in directory DIR. Usually |
227 |
`configure' can determine that directory automatically. |
`configure' can determine that directory automatically. |
228 |
|
|
229 |
`--version' |
`configure' also accepts some other, not widely useful, options. Run |
230 |
Print the version of Autoconf used to generate the `configure' |
`configure --help' for more details. |
|
script, and exit. |
|
231 |
|
|
|
`configure' also accepts some other, not widely useful, options. |
|