1
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
4
This file is free documentation; the Free Software Foundation gives
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
5
8
unlimited permission to copy, distribute and modify it.
10
These are generic installation instructions.
13
These are generic installation instructions.
12
15
The `configure' shell script attempts to guess correct values for
13
16
various system-dependent variables used during compilation. It uses
67
70
Compilers and Options
68
71
=====================
70
Some systems require unusual options for compilation or linking that
71
the `configure' script does not know about. Run `./configure --help'
72
for details on some of the pertinent environment variables.
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.
74
77
You can give `configure' initial values for configuration parameters
75
78
by setting variables in the command line or in the environment. Here
82
85
Compiling For Multiple Architectures
83
86
====================================
85
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
86
89
same time, by placing the object files for each architecture in their
87
90
own directory. To do this, you must use a version of `make' that
88
91
supports the `VPATH' variable, such as GNU `make'. `cd' to the
99
102
Installation Names
100
103
==================
102
By default, `make install' will install the package's files in
103
`/usr/local/bin', `/usr/local/man', etc. You can specify an
104
installation prefix other than `/usr/local' by giving `configure' the
105
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'.
107
110
You can specify separate installation prefixes for
108
111
architecture-specific files and architecture-independent files. If you
109
give `configure' the option `--exec-prefix=PATH', the package will use
110
PATH as the prefix for installing programs and libraries.
111
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.
113
116
In addition, if you use an unusual directory layout you can give
114
options like `--bindir=PATH' to specify different values for particular
117
options like `--bindir=DIR' to specify different values for particular
115
118
kinds of files. Run `configure --help' for a list of the directories
116
119
you can set and what kinds of files go in them.
122
125
Optional Features
123
126
=================
125
Some packages pay attention to `--enable-FEATURE' options to
128
Some packages pay attention to `--enable-FEATURE' options to
126
129
`configure', where FEATURE indicates an optional part of the package.
127
130
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
128
131
is something like `gnu-as' or `x' (for the X Window System). The
137
140
Specifying the System Type
138
141
==========================
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
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
145
148
`--build=TYPE' option. TYPE can either be a short name for the system
146
149
type, such as `sun4', or a canonical name which has the form:
156
159
need to know the machine type.
158
161
If you are _building_ compiler tools for cross-compiling, you should
159
use the `--target=TYPE' option to select the type of system they will
162
use the option `--target=TYPE' to select the type of system they will
160
163
produce code for.
162
165
If you want to _use_ a cross compiler, that generates code for a
170
If you want to set default values for `configure' scripts to share,
171
you can create a site shell script called `config.site' that gives
172
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'.
173
176
`configure' looks for `PREFIX/share/config.site' if it exists, then
174
177
`PREFIX/etc/config.site' if it exists. Or, you can set the
175
178
`CONFIG_SITE' environment variable to the location of the site script.
178
181
Defining Variables
179
182
==================
181
Variables not defined in a site shell script can be set in the
184
Variables not defined in a site shell script can be set in the
182
185
environment passed to `configure'. However, some packages may run
183
186
configure again during the build, and the customized values of these
184
187
variables may be lost. In order to avoid this problem, you should set
187
190
./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
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'.
192
200
`configure' Invocation
193
201
======================
195
`configure' recognizes the following options to control how it
203
`configure' recognizes the following options to control how it operates.
added
removed
INSTALL
