1
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
1
Installation Instructions
2
*************************
4
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
5
2006, 2007, 2008, 2009 Free Software Foundation, Inc.
4
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
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.
12
18
The `configure' shell script attempts to guess correct values for
13
19
various system-dependent variables used during compilation. It uses
21
27
It can also use an optional file (typically called `config.cache'
22
28
and enabled with `--cache-file=config.cache' or simply `-C') that saves
23
the results of its tests to speed up reconfiguring. (Caching is
29
the results of its tests to speed up reconfiguring. Caching is
24
30
disabled by default to prevent problems with accidental use of stale
27
33
If you need to do unusual things to compile the package, please try
28
34
to figure out how `configure' could check whether to do them, and mail
32
38
may remove or edit it.
34
40
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'.
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
39
45
The simplest way to compile this package is:
41
47
1. `cd' to the directory containing the package's source code and type
42
`./configure' to configure the package for your system. If you're
43
using `csh' on an old version of System V, you might need to type
44
`sh ./configure' instead to prevent `csh' from trying to execute
48
`./configure' to configure the package for your system.
47
Running `configure' takes awhile. While running, it prints some
48
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.
50
53
2. Type `make' to compile the package.
85
91
You can compile the package for more than one kind of computer at the
86
92
same time, by placing the object files for each architecture in their
87
own directory. To do this, you must use a version of `make' that
88
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
89
94
directory where you want the object files and executables to go and run
90
95
the `configure' script. `configure' automatically checks for the
91
96
source code in the directory that `configure' is in and in `..'.
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.
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.
99
117
Installation Names
100
118
==================
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'.
120
By default, `make install' installs the package's commands under
121
`/usr/local/bin', include files under `/usr/local/include', etc. You
122
can specify an installation prefix other than `/usr/local' by giving
123
`configure' the option `--prefix=PREFIX'.
107
125
You can specify separate installation prefixes for
108
126
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.
127
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
128
PREFIX as the prefix for installing programs and libraries.
129
Documentation and other data files still use the regular prefix.
113
131
In addition, if you use an unusual directory layout you can give
114
options like `--bindir=PATH' to specify different values for particular
132
options like `--bindir=DIR' to specify different values for particular
115
133
kinds of files. Run `configure --help' for a list of the directories
116
134
you can set and what kinds of files go in them.
134
152
you can use the `configure' options `--x-includes=DIR' and
135
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 -D_XOPEN_SOURCE=500"
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"
177
On Solaris, don't put `/usr/ucb' early in your `PATH'. This
178
directory contains several dysfunctional programs; working variants of
179
these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
180
in your `PATH', put it _after_ `/usr/bin'.
182
On Haiku, software installed for all users goes in `/boot/common',
183
not `/usr/local'. It is recommended to use the following options:
185
./configure --prefix=/boot/common
137
187
Specifying the System Type
138
188
==========================
150
200
where SYSTEM can have one of these forms:
154
205
See the file `config.sub' for the possible values of each field. If
155
206
`config.sub' isn't included in this package, then this package doesn't
156
207
need to know the machine type.
158
209
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
210
use the option `--target=TYPE' to select the type of system they will
160
211
produce code for.
162
213
If you want to _use_ a cross compiler, that generates code for a
224
287
Look for the package's source code in directory DIR. Usually
225
288
`configure' can determine that directory automatically.
291
Use DIR as the installation prefix. *Note Installation Names::
292
for more details, including other options available for fine-tuning
293
the installation locations.
297
Run the configure checks, but stop before creating any output
227
300
`configure' also accepts some other, not widely useful, options. Run
228
301
`configure --help' for more details.
added
removed
INSTALL
