2
2
*************************
4
4
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
5
2006, 2007 Free Software Foundation, Inc.
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
Briefly, the shell commands `./configure; make; make install' should
13
Briefly, the shell commands `./configure; make; make install' should
14
14
configure, build, and install this package. The following
15
15
more-detailed instructions are generic; see the `README' file for
16
16
instructions specific to this package.
73
73
Compilers and Options
74
74
=====================
76
Some systems require unusual options for compilation or linking that the
77
`configure' script does not know about. Run `./configure --help' for
78
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.
80
80
You can give `configure' initial values for configuration parameters
81
81
by setting variables in the command line or in the environment. Here
88
88
Compiling For Multiple Architectures
89
89
====================================
91
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
92
92
same time, by placing the object files for each architecture in their
93
93
own directory. To do this, you can use GNU `make'. `cd' to the
94
94
directory where you want the object files and executables to go and run
100
100
installed the package for one architecture, use `make distclean' before
101
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.
103
117
Installation Names
104
118
==================
106
By default, `make install' installs the package's commands under
120
By default, `make install' installs the package's commands under
107
121
`/usr/local/bin', include files under `/usr/local/include', etc. You
108
122
can specify an installation prefix other than `/usr/local' by giving
109
123
`configure' the option `--prefix=PREFIX'.
126
140
Optional Features
127
141
=================
129
Some packages pay attention to `--enable-FEATURE' options to
143
Some packages pay attention to `--enable-FEATURE' options to
130
144
`configure', where FEATURE indicates an optional part of the package.
131
145
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
132
146
is something like `gnu-as' or `x' (for the X Window System). The
138
152
you can use the `configure' options `--x-includes=DIR' and
139
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"
141
177
Specifying the System Type
142
178
==========================
144
There may be some features `configure' cannot figure out automatically,
145
but needs to determine by the type of machine the package will run on.
146
Usually, assuming the package is built to be run on the _same_
147
architectures, `configure' can figure that out, but if it prints a
148
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
149
185
`--build=TYPE' option. TYPE can either be a short name for the system
150
186
type, such as `sun4', or a canonical name which has the form:
174
If you want to set default values for `configure' scripts to share, you
175
can create a site shell script called `config.site' that gives default
176
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'.
177
213
`configure' looks for `PREFIX/share/config.site' if it exists, then
178
214
`PREFIX/etc/config.site' if it exists. Or, you can set the
179
215
`CONFIG_SITE' environment variable to the location of the site script.
182
218
Defining Variables
183
219
==================
185
Variables not defined in a site shell script can be set in the
221
Variables not defined in a site shell script can be set in the
186
222
environment passed to `configure'. However, some packages may run
187
223
configure again during the build, and the customized values of these
188
224
variables may be lost. In order to avoid this problem, you should set
201
237
`configure' Invocation
202
238
======================
204
`configure' recognizes the following options to control how it operates.
240
`configure' recognizes the following options to control how it
208
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.
232
276
Look for the package's source code in directory DIR. Usually
233
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
235
289
`configure' also accepts some other, not widely useful, options. Run
236
290
`configure --help' for more details.
added
removed
INSTALL
