|
|
|
@ -2,15 +2,15 @@ Installation Instructions
|
|
|
|
|
*************************
|
|
|
|
|
|
|
|
|
|
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
|
|
|
|
|
2006, 2007 Free Software Foundation, Inc.
|
|
|
|
|
2006, 2007, 2008, 2009 Free Software Foundation, Inc.
|
|
|
|
|
|
|
|
|
|
This file is free documentation; the Free Software Foundation gives
|
|
|
|
|
This file is free documentation; the Free Software Foundation gives
|
|
|
|
|
unlimited permission to copy, distribute and modify it.
|
|
|
|
|
|
|
|
|
|
Basic Installation
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
Briefly, the shell commands `./configure; make; make install' should
|
|
|
|
|
Briefly, the shell commands `./configure; make; make install' should
|
|
|
|
|
configure, build, and install this package. The following
|
|
|
|
|
more-detailed instructions are generic; see the `README' file for
|
|
|
|
|
instructions specific to this package.
|
|
|
|
@ -73,9 +73,9 @@ The simplest way to compile this package is:
|
|
|
|
|
Compilers and Options
|
|
|
|
|
=====================
|
|
|
|
|
|
|
|
|
|
Some systems require unusual options for compilation or linking that the
|
|
|
|
|
`configure' script does not know about. Run `./configure --help' for
|
|
|
|
|
details on some of the pertinent environment variables.
|
|
|
|
|
Some systems require unusual options for compilation or linking that
|
|
|
|
|
the `configure' script does not know about. Run `./configure --help'
|
|
|
|
|
for details on some of the pertinent environment variables.
|
|
|
|
|
|
|
|
|
|
You can give `configure' initial values for configuration parameters
|
|
|
|
|
by setting variables in the command line or in the environment. Here
|
|
|
|
@ -88,7 +88,7 @@ is an example:
|
|
|
|
|
Compiling For Multiple Architectures
|
|
|
|
|
====================================
|
|
|
|
|
|
|
|
|
|
You can compile the package for more than one kind of computer at the
|
|
|
|
|
You can compile the package for more than one kind of computer at the
|
|
|
|
|
same time, by placing the object files for each architecture in their
|
|
|
|
|
own directory. To do this, you can use GNU `make'. `cd' to the
|
|
|
|
|
directory where you want the object files and executables to go and run
|
|
|
|
@ -100,10 +100,24 @@ architecture at a time in the source code directory. After you have
|
|
|
|
|
installed the package for one architecture, use `make distclean' before
|
|
|
|
|
reconfiguring for another architecture.
|
|
|
|
|
|
|
|
|
|
On MacOS X 10.5 and later systems, you can create libraries and
|
|
|
|
|
executables that work on multiple system types--known as "fat" or
|
|
|
|
|
"universal" binaries--by specifying multiple `-arch' options to the
|
|
|
|
|
compiler but only a single `-arch' option to the preprocessor. Like
|
|
|
|
|
this:
|
|
|
|
|
|
|
|
|
|
./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
|
|
|
|
|
CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
|
|
|
|
|
CPP="gcc -E" CXXCPP="g++ -E"
|
|
|
|
|
|
|
|
|
|
This is not guaranteed to produce working output in all cases, you
|
|
|
|
|
may have to build one architecture at a time and combine the results
|
|
|
|
|
using the `lipo' tool if you have problems.
|
|
|
|
|
|
|
|
|
|
Installation Names
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
By default, `make install' installs the package's commands under
|
|
|
|
|
By default, `make install' installs the package's commands under
|
|
|
|
|
`/usr/local/bin', include files under `/usr/local/include', etc. You
|
|
|
|
|
can specify an installation prefix other than `/usr/local' by giving
|
|
|
|
|
`configure' the option `--prefix=PREFIX'.
|
|
|
|
@ -126,7 +140,7 @@ option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
|
|
|
|
Optional Features
|
|
|
|
|
=================
|
|
|
|
|
|
|
|
|
|
Some packages pay attention to `--enable-FEATURE' options to
|
|
|
|
|
Some packages pay attention to `--enable-FEATURE' options to
|
|
|
|
|
`configure', where FEATURE indicates an optional part of the package.
|
|
|
|
|
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
|
|
|
|
|
is something like `gnu-as' or `x' (for the X Window System). The
|
|
|
|
@ -138,14 +152,46 @@ find the X include and library files automatically, but if it doesn't,
|
|
|
|
|
you can use the `configure' options `--x-includes=DIR' and
|
|
|
|
|
`--x-libraries=DIR' to specify their locations.
|
|
|
|
|
|
|
|
|
|
Particular systems
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
On HP-UX, the default C compiler is not ANSI C compatible. If GNU
|
|
|
|
|
CC is not installed, it is recommended to use the following options in
|
|
|
|
|
order to use an ANSI C compiler:
|
|
|
|
|
|
|
|
|
|
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
|
|
|
|
|
|
|
|
|
|
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
|
|
|
|
|
|
|
|
|
|
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
|
|
|
|
|
parse its `<wchar.h>' header file. The option `-nodtk' can be used as
|
|
|
|
|
a workaround. If GNU CC is not installed, it is therefore recommended
|
|
|
|
|
to try
|
|
|
|
|
|
|
|
|
|
./configure CC="cc"
|
|
|
|
|
|
|
|
|
|
and if that doesn't work, try
|
|
|
|
|
|
|
|
|
|
./configure CC="cc -nodtk"
|
|
|
|
|
|
|
|
|
|
On Solaris, don't put `/usr/ucb' early in your `PATH'. This
|
|
|
|
|
directory contains several dysfunctional programs; working variants of
|
|
|
|
|
these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
|
|
|
|
|
in your `PATH', put it _after_ `/usr/bin'.
|
|
|
|
|
|
|
|
|
|
On Haiku, software installed for all users goes in `/boot/common',
|
|
|
|
|
not `/usr/local'. It is recommended to use the following options:
|
|
|
|
|
|
|
|
|
|
./configure --prefix=/boot/common
|
|
|
|
|
|
|
|
|
|
Specifying the System Type
|
|
|
|
|
==========================
|
|
|
|
|
|
|
|
|
|
There may be some features `configure' cannot figure out automatically,
|
|
|
|
|
but needs to determine by the type of machine the package will run on.
|
|
|
|
|
Usually, assuming the package is built to be run on the _same_
|
|
|
|
|
architectures, `configure' can figure that out, but if it prints a
|
|
|
|
|
message saying it cannot guess the machine type, give it the
|
|
|
|
|
There may be some features `configure' cannot figure out
|
|
|
|
|
automatically, but needs to determine by the type of machine the package
|
|
|
|
|
will run on. Usually, assuming the package is built to be run on the
|
|
|
|
|
_same_ architectures, `configure' can figure that out, but if it prints
|
|
|
|
|
a message saying it cannot guess the machine type, give it the
|
|
|
|
|
`--build=TYPE' option. TYPE can either be a short name for the system
|
|
|
|
|
type, such as `sun4', or a canonical name which has the form:
|
|
|
|
|
|
|
|
|
@ -153,7 +199,8 @@ type, such as `sun4', or a canonical name which has the form:
|
|
|
|
|
|
|
|
|
|
where SYSTEM can have one of these forms:
|
|
|
|
|
|
|
|
|
|
OS KERNEL-OS
|
|
|
|
|
OS
|
|
|
|
|
KERNEL-OS
|
|
|
|
|
|
|
|
|
|
See the file `config.sub' for the possible values of each field. If
|
|
|
|
|
`config.sub' isn't included in this package, then this package doesn't
|
|
|
|
@ -171,9 +218,9 @@ eventually be run) with `--host=TYPE'.
|
|
|
|
|
Sharing Defaults
|
|
|
|
|
================
|
|
|
|
|
|
|
|
|
|
If you want to set default values for `configure' scripts to share, you
|
|
|
|
|
can create a site shell script called `config.site' that gives default
|
|
|
|
|
values for variables like `CC', `cache_file', and `prefix'.
|
|
|
|
|
If you want to set default values for `configure' scripts to share,
|
|
|
|
|
you can create a site shell script called `config.site' that gives
|
|
|
|
|
default values for variables like `CC', `cache_file', and `prefix'.
|
|
|
|
|
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
|
|
|
|
`PREFIX/etc/config.site' if it exists. Or, you can set the
|
|
|
|
|
`CONFIG_SITE' environment variable to the location of the site script.
|
|
|
|
@ -182,7 +229,7 @@ A warning: not all `configure' scripts look for a site script.
|
|
|
|
|
Defining Variables
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
Variables not defined in a site shell script can be set in the
|
|
|
|
|
Variables not defined in a site shell script can be set in the
|
|
|
|
|
environment passed to `configure'. However, some packages may run
|
|
|
|
|
configure again during the build, and the customized values of these
|
|
|
|
|
variables may be lost. In order to avoid this problem, you should set
|
|
|
|
@ -201,11 +248,19 @@ an Autoconf bug. Until the bug is fixed you can use this workaround:
|
|
|
|
|
`configure' Invocation
|
|
|
|
|
======================
|
|
|
|
|
|
|
|
|
|
`configure' recognizes the following options to control how it operates.
|
|
|
|
|
`configure' recognizes the following options to control how it
|
|
|
|
|
operates.
|
|
|
|
|
|
|
|
|
|
`--help'
|
|
|
|
|
`-h'
|
|
|
|
|
Print a summary of the options to `configure', and exit.
|
|
|
|
|
Print a summary of all of the options to `configure', and exit.
|
|
|
|
|
|
|
|
|
|
`--help=short'
|
|
|
|
|
`--help=recursive'
|
|
|
|
|
Print a summary of the options unique to this package's
|
|
|
|
|
`configure', and exit. The `short' variant lists options used
|
|
|
|
|
only in the top level, while the `recursive' variant lists options
|
|
|
|
|
also present in any nested packages.
|
|
|
|
|
|
|
|
|
|
`--version'
|
|
|
|
|
`-V'
|
|
|
|
@ -232,6 +287,16 @@ an Autoconf bug. Until the bug is fixed you can use this workaround:
|
|
|
|
|
Look for the package's source code in directory DIR. Usually
|
|
|
|
|
`configure' can determine that directory automatically.
|
|
|
|
|
|
|
|
|
|
`--prefix=DIR'
|
|
|
|
|
Use DIR as the installation prefix. *Note Installation Names::
|
|
|
|
|
for more details, including other options available for fine-tuning
|
|
|
|
|
the installation locations.
|
|
|
|
|
|
|
|
|
|
`--no-create'
|
|
|
|
|
`-n'
|
|
|
|
|
Run the configure checks, but stop before creating any output
|
|
|
|
|
files.
|
|
|
|
|
|
|
|
|
|
`configure' also accepts some other, not widely useful, options. Run
|
|
|
|
|
`configure --help' for more details.
|
|
|
|
|
|
|
|
|
|