These are generic installation instructions.
The configure
shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the
package. It may also create one or more `.h' files containing
system-dependent definitions. Finally, it creates a shell script
`config.status' that you can run in the future to recreate the
current configuration, a file `config.cache' that saves the results
of its tests to speed up reconfiguring, and a file `config.log'
containing compiler output (useful mainly for debugging
configure
).
If you need to do unusual things to compile the package, please try to
figure out how configure
could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they
can be considered for the next release. If at some point
`config.cache' contains results you don't want to keep, you may
remove or edit it.
The file `configure.in' is used to create `configure' by a
program called autoconf
. You only need `configure.in' if
you want to change it or regenerate `configure' using a newer
version of autoconf
.
The simplest way to compile this package is:
cd
to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using csh
on an old version of System V, you might need to type
`sh ./configure' instead to prevent csh
from trying to
execute configure
itself.
Running configure
takes awhile. While running, it prints some
messages telling which features it is checking for.
configure
created (so you can compile the package for a different
kind of computer), type `make distclean'.
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'.
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.
In addition, if you use an unusual directory layout you can give options like `--bindir=path' 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.
If the package supports it, you can cause programs to be installed with
an extra prefix or suffix on their names by giving configure
the
option `--program-prefix=PREFIX' or
`--program-suffix=SUFFIX'.
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 `README' should mention any
`--enable-' and `--with-' options that the package recognizes.
For packages that use the X Window System, configure
can usually
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.
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.
configure
recognizes the following options to control how it
operates.
--cache-file=file
configure
.
--help
configure
, and exit.
--quiet
--silent
-q
--srcdir=dir
configure
can determine that directory automatically.
--version
configure
script, and exit.
configure
also accepts some other, not widely useful, options.
Go to the first, previous, next, last section, table of contents.