1
Installation Instructions
2
*************************
4
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
5
Software Foundation, Inc.
7
This file is free documentation; the Free Software Foundation gives
8
unlimited permission to copy, distribute and modify it.
4
These are generic installation instructions.
13
These are generic installation instructions.
6
15
The `configure' shell script attempts to guess correct values for
7
16
various system-dependent variables used during compilation. It uses
8
17
those values to create a `Makefile' in each directory of the package.
9
18
It may also create one or more `.h' files containing system-dependent
10
19
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').
20
you can run in the future to recreate the current configuration, and a
21
file `config.log' containing compiler output (useful mainly for
22
debugging `configure').
24
It can also use an optional file (typically called `config.cache'
25
and enabled with `--cache-file=config.cache' or simply `-C') that saves
26
the results of its tests to speed up reconfiguring. (Caching is
27
disabled by default to prevent problems with accidental use of stale
16
30
If you need to do unusual things to compile the package, please try
17
31
to figure out how `configure' could check whether to do them, and mail
18
32
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.
33
be considered for the next release. If you are using the cache, and at
34
some point `config.cache' contains results you don't want to keep, you
35
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'.
37
The file `configure.ac' (or `configure.in') is used to create
38
`configure' by a program called `autoconf'. You only need
39
`configure.ac' if you want to change it or regenerate `configure' using
40
a newer version of `autoconf'.
26
42
The simplest way to compile this package is:
54
70
Compilers and Options
55
71
=====================
57
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
73
Some systems require unusual options for compilation or linking that the
74
`configure' script does not know about. Run `./configure --help' for
75
details on some of the pertinent environment variables.
77
You can give `configure' initial values for configuration parameters
78
by setting variables in the command line or in the environment. Here
81
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
83
*Note Defining Variables::, for more details.
67
85
Compiling For Multiple Architectures
68
86
====================================
70
You can compile the package for more than one kind of computer at the
88
You can compile the package for more than one kind of computer at the
71
89
same time, by placing the object files for each architecture in their
72
90
own directory. To do this, you must use a version of `make' that
73
91
supports the `VPATH' variable, such as GNU `make'. `cd' to the
75
93
the `configure' script. `configure' automatically checks for the
76
94
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
96
If you have to use a `make' that does not support the `VPATH'
97
variable, you have to compile the package for one architecture at a
98
time in the source code directory. After you have installed the
99
package for one architecture, use `make distclean' before reconfiguring
100
for another architecture.
84
102
Installation Names
85
103
==================
87
By default, `make install' will install the package's files in
88
`/usr/local/bin', `/usr/local/man', etc. You can specify an
89
installation prefix other than `/usr/local' by giving `configure' the
90
option `--prefix=PATH'.
105
By default, `make install' installs the package's commands under
106
`/usr/local/bin', include files under `/usr/local/include', etc. You
107
can specify an installation prefix other than `/usr/local' by giving
108
`configure' the option `--prefix=PREFIX'.
92
110
You can specify separate installation prefixes for
93
111
architecture-specific files and architecture-independent files. If you
94
give `configure' the option `--exec-prefix=PATH', the package will use
95
PATH as the prefix for installing programs and libraries.
96
Documentation and other data files will still use the regular prefix.
112
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
113
PREFIX as the prefix for installing programs and libraries.
114
Documentation and other data files still use the regular prefix.
98
116
In addition, if you use an unusual directory layout you can give
99
options like `--bindir=PATH' to specify different values for particular
117
options like `--bindir=DIR' to specify different values for particular
100
118
kinds of files. Run `configure --help' for a list of the directories
101
119
you can set and what kinds of files go in them.
122
140
Specifying the System Type
123
141
==========================
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:
143
There may be some features `configure' cannot figure out automatically,
144
but needs to determine by the type of machine the package will run on.
145
Usually, assuming the package is built to be run on the _same_
146
architectures, `configure' can figure that out, but if it prints a
147
message saying it cannot guess the machine type, give it the
148
`--build=TYPE' option. TYPE can either be a short name for the system
149
type, such as `sun4', or a canonical name which has the form:
131
151
CPU-COMPANY-SYSTEM
133
See the file `config.sub' for the possible values of each field. If
153
where SYSTEM can have one of these forms:
157
See the file `config.sub' for the possible values of each field. If
134
158
`config.sub' isn't included in this package, then this package doesn't
135
need to know the host type.
137
If you are building compiler tools for cross-compiling, you can also
138
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.
159
need to know the machine type.
161
If you are _building_ compiler tools for cross-compiling, you should
162
use the option `--target=TYPE' to select the type of system they will
165
If you want to _use_ a cross compiler, that generates code for a
166
platform different from the build platform, you should specify the
167
"host" platform (i.e., that on which the generated programs will
168
eventually be run) with `--host=TYPE'.
145
If you want to set default values for `configure' scripts to share,
146
you can create a site shell script called `config.site' that gives
147
default values for variables like `CC', `cache_file', and `prefix'.
173
If you want to set default values for `configure' scripts to share, you
174
can create a site shell script called `config.site' that gives default
175
values for variables like `CC', `cache_file', and `prefix'.
148
176
`configure' looks for `PREFIX/share/config.site' if it exists, then
149
177
`PREFIX/etc/config.site' if it exists. Or, you can set the
150
178
`CONFIG_SITE' environment variable to the location of the site script.
151
179
A warning: not all `configure' scripts look for a site script.
154
182
==================
156
`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'.
184
Variables not defined in a site shell script can be set in the
185
environment passed to `configure'. However, some packages may run
186
configure again during the build, and the customized values of these
187
variables may be lost. In order to avoid this problem, you should set
188
them in the `configure' command line, using `VAR=value'. For example:
190
./configure CC=/usr/local2/bin/gcc
192
causes the specified `gcc' to be used as the C compiler (unless it is
193
overridden in the site shell script). Here is a another example:
195
/bin/bash ./configure CONFIG_SHELL=/bin/bash
197
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
198
configuration-related scripts to be executed by `/bin/bash'.
200
`configure' Invocation
201
======================
203
`configure' recognizes the following options to control how it operates.
165
207
Print a summary of the options to `configure', and exit.
211
Print the version of Autoconf used to generate the `configure'
215
Enable the cache: use and save the results of the tests in FILE,
216
traditionally `config.cache'. FILE defaults to `/dev/null' to
221
Alias for `--cache-file=config.cache'.
added
removed
INSTALL
