|
|
|
@@ -1,13 +1,16 @@
|
|
|
|
|
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
|
|
|
|
|
Foundation, Inc.
|
|
|
|
|
Installation Instructions
|
|
|
|
|
*************************
|
|
|
|
|
|
|
|
|
|
This file is free documentation; the Free Software Foundation gives
|
|
|
|
|
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
|
|
|
|
|
Software Foundation, Inc.
|
|
|
|
|
|
|
|
|
|
This file is free documentation; the Free Software Foundation gives
|
|
|
|
|
unlimited permission to copy, distribute and modify it.
|
|
|
|
|
|
|
|
|
|
Basic Installation
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
These are generic installation instructions.
|
|
|
|
|
These are generic installation instructions.
|
|
|
|
|
|
|
|
|
|
The `configure' shell script attempts to guess correct values for
|
|
|
|
|
various system-dependent variables used during compilation. It uses
|
|
|
|
@@ -67,9 +70,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
|
|
|
|
@@ -82,7 +85,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 must use a version of `make' that
|
|
|
|
|
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
|
|
|
@@ -99,19 +102,19 @@ for another architecture.
|
|
|
|
|
Installation Names
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
By default, `make install' will install the package's files in
|
|
|
|
|
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
|
|
|
|
installation prefix other than `/usr/local' by giving `configure' the
|
|
|
|
|
option `--prefix=PATH'.
|
|
|
|
|
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'.
|
|
|
|
|
|
|
|
|
|
You can specify separate installation prefixes for
|
|
|
|
|
architecture-specific files and architecture-independent files. If you
|
|
|
|
|
give `configure' the option `--exec-prefix=PATH', the package will use
|
|
|
|
|
PATH as the prefix for installing programs and libraries.
|
|
|
|
|
Documentation and other data files will still use the regular prefix.
|
|
|
|
|
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
|
|
|
|
|
PREFIX as the prefix for installing programs and libraries.
|
|
|
|
|
Documentation and other data files still use the regular prefix.
|
|
|
|
|
|
|
|
|
|
In addition, if you use an unusual directory layout you can give
|
|
|
|
|
options like `--bindir=PATH' to specify different values for particular
|
|
|
|
|
options like `--bindir=DIR' to specify different values for particular
|
|
|
|
|
kinds of files. Run `configure --help' for a list of the directories
|
|
|
|
|
you can set and what kinds of files go in them.
|
|
|
|
|
|
|
|
|
@@ -122,7 +125,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
|
|
|
|
@@ -137,11 +140,11 @@ you can use the `configure' options `--x-includes=DIR' and
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
@@ -156,7 +159,7 @@ where SYSTEM can have one of these forms:
|
|
|
|
|
need to know the machine type.
|
|
|
|
|
|
|
|
|
|
If you are _building_ compiler tools for cross-compiling, you should
|
|
|
|
|
use the `--target=TYPE' option to select the type of system they will
|
|
|
|
|
use the option `--target=TYPE' to select the type of system they will
|
|
|
|
|
produce code for.
|
|
|
|
|
|
|
|
|
|
If you want to _use_ a cross compiler, that generates code for a
|
|
|
|
@@ -167,9 +170,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.
|
|
|
|
@@ -178,7 +181,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
|
|
|
|
@@ -186,14 +189,18 @@ them in the `configure' command line, using `VAR=value'. For example:
|
|
|
|
|
|
|
|
|
|
./configure CC=/usr/local2/bin/gcc
|
|
|
|
|
|
|
|
|
|
will cause the specified gcc to be used as the C compiler (unless it is
|
|
|
|
|
overridden in the site shell script).
|
|
|
|
|
causes the specified `gcc' to be used as the C compiler (unless it is
|
|
|
|
|
overridden in the site shell script). Here is a another example:
|
|
|
|
|
|
|
|
|
|
/bin/bash ./configure CONFIG_SHELL=/bin/bash
|
|
|
|
|
|
|
|
|
|
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
|
|
|
|
|
configuration-related scripts to be executed by `/bin/bash'.
|
|
|
|
|
|
|
|
|
|
`configure' Invocation
|
|
|
|
|
======================
|
|
|
|
|
|
|
|
|
|
`configure' recognizes the following options to control how it
|
|
|
|
|
operates.
|
|
|
|
|
`configure' recognizes the following options to control how it operates.
|
|
|
|
|
|
|
|
|
|
`--help'
|
|
|
|
|
`-h'
|
|
|
|
|
Thomas Ries