1
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
4
This file is free documentation; the Free Software Foundation gives
5
unlimited permission to copy, distribute and modify it.
8
14
those values to create a `Makefile' in each directory of the package.
9
15
It may also create one or more `.h' files containing system-dependent
10
16
definitions. Finally, it creates a shell script `config.status' that
11
you can run in the future to recreate the current configuration, a file
12
`config.cache' that saves the results of its tests to speed up
13
reconfiguring, and a file `config.log' containing compiler output
14
(useful mainly for debugging `configure').
17
you can run in the future to recreate the current configuration, and a
18
file `config.log' containing compiler output (useful mainly for
19
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
16
27
If you need to do unusual things to compile the package, please try
17
28
to figure out how `configure' could check whether to do them, and mail
18
29
diffs or instructions to the address given in the `README' so they can
19
be considered for the next release. If at some point `config.cache'
20
contains results you don't want to keep, you may remove or edit it.
30
be considered for the next release. If you are using the cache, and at
31
some point `config.cache' contains results you don't want to keep, you
32
may remove or edit it.
22
The file `configure.in' is used to create `configure' by a program
23
called `autoconf'. You only need `configure.in' if you want to change
24
it or regenerate `configure' using a newer version of `autoconf'.
34
The file `configure.ac' (or `configure.in') is used to create
35
`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'.
26
39
The simplest way to compile this package is:
55
68
=====================
57
70
Some systems require unusual options for compilation or linking that
58
the `configure' script does not know about. You can give `configure'
59
initial values for variables by setting them in the environment. Using
60
a Bourne-compatible shell, you can do that on the command line like
62
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
64
Or on systems that have the `env' program, you can do it like this:
65
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
71
the `configure' script does not know about. Run `./configure --help'
72
for details on some of the pertinent environment variables.
74
You can give `configure' initial values for configuration parameters
75
by setting variables in the command line or in the environment. Here
78
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
80
*Note Defining Variables::, for more details.
67
82
Compiling For Multiple Architectures
68
83
====================================
75
90
the `configure' script. `configure' automatically checks for the
76
91
source code in the directory that `configure' is in and in `..'.
78
If you have to use a `make' that does not supports the `VPATH'
79
variable, you have to compile the package for one architecture at a time
80
in the source code directory. After you have installed the package for
81
one architecture, use `make distclean' before reconfiguring for another
93
If you have to use a `make' that does not support the `VPATH'
94
variable, you have to compile the package for one architecture at a
95
time in the source code directory. After you have installed the
96
package for one architecture, use `make distclean' before reconfiguring
97
for another architecture.
85
100
==================
122
137
Specifying the System Type
123
138
==========================
125
There may be some features `configure' can not figure out
126
automatically, but needs to determine by the type of host the package
127
will run on. Usually `configure' can figure that out, but if it prints
128
a message saying it can not guess the host type, give it the
129
`--host=TYPE' option. TYPE can either be a short name for the system
130
type, such as `sun4', or a canonical name with three fields:
140
There may be some features `configure' cannot figure out
141
automatically, but needs to determine by the type of machine the package
142
will run on. Usually, assuming the package is built to be run on the
143
_same_ architectures, `configure' can figure that out, but if it prints
144
a message saying it cannot guess the machine type, give it the
145
`--build=TYPE' option. TYPE can either be a short name for the system
146
type, such as `sun4', or a canonical name which has the form:
131
148
CPU-COMPANY-SYSTEM
133
See the file `config.sub' for the possible values of each field. If
150
where SYSTEM can have one of these forms:
154
See the file `config.sub' for the possible values of each field. If
134
155
`config.sub' isn't included in this package, then this package doesn't
135
need to know the host type.
156
need to know the machine type.
137
If you are building compiler tools for cross-compiling, you can also
158
If you are _building_ compiler tools for cross-compiling, you should
138
159
use the `--target=TYPE' option to select the type of system they will
139
produce code for and the `--build=TYPE' option to select the type of
140
system on which you are compiling the package.
162
If you want to _use_ a cross compiler, that generates code for a
163
platform different from the build platform, you should specify the
164
"host" platform (i.e., that on which the generated programs will
165
eventually be run) with `--host=TYPE'.
150
175
`CONFIG_SITE' environment variable to the location of the site script.
151
176
A warning: not all `configure' scripts look for a site script.
154
179
==================
181
Variables not defined in a site shell script can be set in the
182
environment passed to `configure'. However, some packages may run
183
configure again during the build, and the customized values of these
184
variables may be lost. In order to avoid this problem, you should set
185
them in the `configure' command line, using `VAR=value'. For example:
187
./configure CC=/usr/local2/bin/gcc
189
will cause the specified gcc to be used as the C compiler (unless it is
190
overridden in the site shell script).
192
`configure' Invocation
193
======================
156
195
`configure' recognizes the following options to control how it
160
Use and save the results of the tests in FILE instead of
161
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
162
debugging `configure'.
165
200
Print a summary of the options to `configure', and exit.
204
Print the version of Autoconf used to generate the `configure'
208
Enable the cache: use and save the results of the tests in FILE,
209
traditionally `config.cache'. FILE defaults to `/dev/null' to
214
Alias for `--cache-file=config.cache'.
175
224
Look for the package's source code in directory DIR. Usually
176
225
`configure' can determine that directory automatically.
179
Print the version of Autoconf used to generate the `configure'
227
`configure' also accepts some other, not widely useful, options. Run
228
`configure --help' for more details.
182
`configure' also accepts some other, not widely useful, options.
added
removed
INSTALL
