1
1
Installation Instructions
2
2
*************************
4
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
5
Software Foundation, Inc.
4
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
5
2006, 2007, 2008 Free Software Foundation, Inc.
7
This file is free documentation; the Free Software Foundation gives
7
This file is free documentation; the Free Software Foundation gives
8
8
unlimited permission to copy, distribute and modify it.
13
These are generic installation instructions.
13
Briefly, the shell commands `./configure; make; make install' should
14
configure, build, and install this package. The following
15
more-detailed instructions are generic; see the `README' file for
16
instructions specific to this package.
15
18
The `configure' shell script attempts to guess correct values for
16
19
various system-dependent variables used during compilation. It uses
24
27
It can also use an optional file (typically called `config.cache'
25
28
and enabled with `--cache-file=config.cache' or simply `-C') that saves
26
the results of its tests to speed up reconfiguring. (Caching is
29
the results of its tests to speed up reconfiguring. Caching is
27
30
disabled by default to prevent problems with accidental use of stale
30
33
If you need to do unusual things to compile the package, please try
31
34
to figure out how `configure' could check whether to do them, and mail
35
38
may remove or edit it.
37
40
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'.
41
`configure' by a program called `autoconf'. You need `configure.ac' if
42
you want to change it or regenerate `configure' using a newer version
42
45
The simplest way to compile this package is:
44
47
1. `cd' to the directory containing the package's source code and type
45
`./configure' to configure the package for your system. If you're
46
using `csh' on an old version of System V, you might need to type
47
`sh ./configure' instead to prevent `csh' from trying to execute
48
`./configure' to configure the package for your system.
50
Running `configure' takes awhile. While running, it prints some
51
messages telling which features it is checking for.
50
Running `configure' might take a while. While running, it prints
51
some messages telling which features it is checking for.
53
53
2. Type `make' to compile the package.
67
67
all sorts of other programs in order to regenerate files that came
68
68
with the distribution.
70
6. Often, you can also type `make uninstall' to remove the installed
70
73
Compilers and Options
71
74
=====================
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.
76
Some systems require unusual options for compilation or linking that
77
the `configure' script does not know about. Run `./configure --help'
78
for details on some of the pertinent environment variables.
77
80
You can give `configure' initial values for configuration parameters
78
81
by setting variables in the command line or in the environment. Here
81
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
84
./configure CC=c99 CFLAGS=-g LIBS=-lposix
83
86
*Note Defining Variables::, for more details.
85
88
Compiling For Multiple Architectures
86
89
====================================
88
You can compile the package for more than one kind of computer at the
91
You can compile the package for more than one kind of computer at the
89
92
same time, by placing the object files for each architecture in their
90
own directory. To do this, you must use a version of `make' that
91
supports the `VPATH' variable, such as GNU `make'. `cd' to the
93
own directory. To do this, you can use GNU `make'. `cd' to the
92
94
directory where you want the object files and executables to go and run
93
95
the `configure' script. `configure' automatically checks for the
94
96
source code in the directory that `configure' is in and in `..'.
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.
98
With a non-GNU `make', it is safer to compile the package for one
99
architecture at a time in the source code directory. After you have
100
installed the package for one architecture, use `make distclean' before
101
reconfiguring for another architecture.
103
On MacOS X 10.5 and later systems, you can create libraries and
104
executables that work on multiple system types--known as "fat" or
105
"universal" binaries--by specifying multiple `-arch' options to the
106
compiler but only a single `-arch' option to the preprocessor. Like
109
./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
110
CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
111
CPP="gcc -E" CXXCPP="g++ -E"
113
This is not guaranteed to produce working output in all cases, you
114
may have to build one architecture at a time and combine the results
115
using the `lipo' tool if you have problems.
102
117
Installation Names
103
118
==================
105
By default, `make install' installs the package's commands under
120
By default, `make install' installs the package's commands under
106
121
`/usr/local/bin', include files under `/usr/local/include', etc. You
107
122
can specify an installation prefix other than `/usr/local' by giving
108
123
`configure' the option `--prefix=PREFIX'.
137
152
you can use the `configure' options `--x-includes=DIR' and
138
153
`--x-libraries=DIR' to specify their locations.
158
On HP-UX, the default C compiler is not ANSI C compatible. If GNU
159
CC is not installed, it is recommended to use the following options in
160
order to use an ANSI C compiler:
162
./configure CC="cc -Ae"
164
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
166
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
167
parse its `<wchar.h>' header file. The option `-nodtk' can be used as
168
a workaround. If GNU CC is not installed, it is therefore recommended
173
and if that doesn't work, try
175
./configure CC="cc -nodtk"
140
177
Specifying the System Type
141
178
==========================
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
180
There may be some features `configure' cannot figure out
181
automatically, but needs to determine by the type of machine the package
182
will run on. Usually, assuming the package is built to be run on the
183
_same_ architectures, `configure' can figure that out, but if it prints
184
a message saying it cannot guess the machine type, give it the
148
185
`--build=TYPE' option. TYPE can either be a short name for the system
149
186
type, such as `sun4', or a canonical name which has the form:
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'.
210
If you want to set default values for `configure' scripts to share,
211
you can create a site shell script called `config.site' that gives
212
default values for variables like `CC', `cache_file', and `prefix'.
176
213
`configure' looks for `PREFIX/share/config.site' if it exists, then
177
214
`PREFIX/etc/config.site' if it exists. Or, you can set the
178
215
`CONFIG_SITE' environment variable to the location of the site script.
190
227
./configure CC=/usr/local2/bin/gcc
192
229
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'.
230
overridden in the site shell script).
232
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
233
an Autoconf bug. Until the bug is fixed you can use this workaround:
235
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
200
237
`configure' Invocation
201
238
======================
203
`configure' recognizes the following options to control how it operates.
240
`configure' recognizes the following options to control how it
207
Print a summary of the options to `configure', and exit.
245
Print a summary of all of the options to `configure', and exit.
249
Print a summary of the options unique to this package's
250
`configure', and exit. The `short' variant lists options used
251
only in the top level, while the `recursive' variant lists options
252
also present in any nested packages.
231
276
Look for the package's source code in directory DIR. Usually
232
277
`configure' can determine that directory automatically.
280
Use DIR as the installation prefix. *Note Installation Names::
281
for more details, including other options available for fine-tuning
282
the installation locations.
286
Run the configure checks, but stop before creating any output
234
289
`configure' also accepts some other, not widely useful, options. Run
235
290
`configure --help' for more details.