Blame INSTALL

Packit 70b277
Basic Installation
Packit 70b277
==================
Packit 70b277
Packit 70b277
   These are generic installation instructions.
Packit 70b277
Packit 70b277
   The `configure' shell script attempts to guess correct values for
Packit 70b277
various system-dependent variables used during compilation.  It uses
Packit 70b277
those values to create a `Makefile' in each directory of the package.
Packit 70b277
It may also create one or more `.h' files containing system-dependent
Packit 70b277
definitions.  Finally, it creates a shell script `config.status' that
Packit 70b277
you can run in the future to recreate the current configuration, a file
Packit 70b277
`config.cache' that saves the results of its tests to speed up
Packit 70b277
reconfiguring, and a file `config.log' containing compiler output
Packit 70b277
(useful mainly for debugging `configure').
Packit 70b277
Packit 70b277
   If you need to do unusual things to compile the package, please try
Packit 70b277
to figure out how `configure' could check whether to do them, and mail
Packit 70b277
diffs or instructions to the address given in the `README' so they can
Packit 70b277
be considered for the next release.  If at some point `config.cache'
Packit 70b277
contains results you don't want to keep, you may remove or edit it.
Packit 70b277
Packit 70b277
   The file `configure.in' is used to create `configure' by a program
Packit 70b277
called `autoconf'.  You only need `configure.in' if you want to change
Packit 70b277
it or regenerate `configure' using a newer version of `autoconf'.
Packit 70b277
Packit 70b277
The simplest way to compile this package is:
Packit 70b277
Packit 70b277
  1. `cd' to the directory containing the package's source code and type
Packit 70b277
     `./configure' to configure the package for your system.  If you're
Packit 70b277
     using `csh' on an old version of System V, you might need to type
Packit 70b277
     `sh ./configure' instead to prevent `csh' from trying to execute
Packit 70b277
     `configure' itself.
Packit 70b277
Packit 70b277
     Running `configure' takes a while.  While running, it prints some
Packit 70b277
     messages telling which features it is checking for.
Packit 70b277
Packit 70b277
  2. Type `make' to compile the package.
Packit 70b277
Packit 70b277
  3. Optionally, type `make check' to run any self-tests that come with
Packit 70b277
     the package.
Packit 70b277
Packit 70b277
  4. Type `make install' to install the programs and any data files and
Packit 70b277
     documentation.
Packit 70b277
Packit 70b277
  5. You can remove the program binaries and object files from the
Packit 70b277
     source code directory by typing `make clean'.  To also remove the
Packit 70b277
     files that `configure' created (so you can compile the package for
Packit 70b277
     a different kind of computer), type `make distclean'.  There is
Packit 70b277
     also a `make maintainer-clean' target, but that is intended mainly
Packit 70b277
     for the package's developers.  If you use it, you may have to get
Packit 70b277
     all sorts of other programs in order to regenerate files that came
Packit 70b277
     with the distribution.
Packit 70b277
Packit 70b277
Compilers and Options
Packit 70b277
=====================
Packit 70b277
Packit 70b277
   Some systems require unusual options for compilation or linking that
Packit 70b277
the `configure' script does not know about.  You can give `configure'
Packit 70b277
initial values for variables by setting them in the environment.  Using
Packit 70b277
a Bourne-compatible shell, you can do that on the command line like
Packit 70b277
this:
Packit 70b277
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Packit 70b277
Packit 70b277
Or on systems that have the `env' program, you can do it like this:
Packit 70b277
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Packit 70b277
Packit 70b277
Compiling For Multiple Architectures
Packit 70b277
====================================
Packit 70b277
Packit 70b277
   You can compile the package for more than one kind of computer at the
Packit 70b277
same time, by placing the object files for each architecture in their
Packit 70b277
own directory.  To do this, you must use a version of `make' that
Packit 70b277
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
Packit 70b277
directory where you want the object files and executables to go and run
Packit 70b277
the `configure' script.  `configure' automatically checks for the
Packit 70b277
source code in the directory that `configure' is in and in `..'.
Packit 70b277
Packit 70b277
   If you have to use a `make' that does not supports the `VPATH'
Packit 70b277
variable, you have to compile the package for one architecture at a time
Packit 70b277
in the source code directory.  After you have installed the package for
Packit 70b277
one architecture, use `make distclean' before reconfiguring for another
Packit 70b277
architecture.
Packit 70b277
Packit 70b277
Installation Names
Packit 70b277
==================
Packit 70b277
Packit 70b277
   By default, `make install' will install the package's files in
Packit 70b277
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
Packit 70b277
installation prefix other than `/usr/local' by giving `configure' the
Packit 70b277
option `--prefix=PATH'.
Packit 70b277
Packit 70b277
   You can specify separate installation prefixes for
Packit 70b277
architecture-specific files and architecture-independent files.  If you
Packit 70b277
give `configure' the option `--exec-prefix=PATH', the package will use
Packit 70b277
PATH as the prefix for installing programs and libraries.
Packit 70b277
Documentation and other data files will still use the regular prefix.
Packit 70b277
Packit 70b277
   If the package supports it, you can cause programs to be installed
Packit 70b277
with an extra prefix or suffix on their names by giving `configure' the
Packit 70b277
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Packit 70b277
Packit 70b277
Optional Features
Packit 70b277
=================
Packit 70b277
Packit 70b277
   Some packages pay attention to `--enable-FEATURE' options to
Packit 70b277
`configure', where FEATURE indicates an optional part of the package.
Packit 70b277
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
Packit 70b277
is something like `gnu-as' or `x' (for the X Window System).  The
Packit 70b277
`README' should mention any `--enable-' and `--with-' options that the
Packit 70b277
package recognizes.
Packit 70b277
Packit 70b277
   For packages that use the X Window System, `configure' can usually
Packit 70b277
find the X include and library files automatically, but if it doesn't,
Packit 70b277
you can use the `configure' options `--x-includes=DIR' and
Packit 70b277
`--x-libraries=DIR' to specify their locations.
Packit 70b277
Packit 70b277
Specifying the System Type
Packit 70b277
==========================
Packit 70b277
Packit 70b277
   There may be some features `configure' can not figure out
Packit 70b277
automatically, but needs to determine by the type of host the package
Packit 70b277
will run on.  Usually `configure' can figure that out, but if it prints
Packit 70b277
a message saying it can not guess the host type, give it the
Packit 70b277
`--host=TYPE' option.  TYPE can either be a short name for the system
Packit 70b277
type, such as `sun4', or a canonical name with three fields:
Packit 70b277
     CPU-COMPANY-SYSTEM
Packit 70b277
Packit 70b277
See the file `config.sub' for the possible values of each field.  If
Packit 70b277
`config.sub' isn't included in this package, then this package doesn't
Packit 70b277
need to know the host type.
Packit 70b277
Packit 70b277
   If you are building compiler tools for cross-compiling, you can also
Packit 70b277
use the `--target=TYPE' option to select the type of system they will
Packit 70b277
produce code for and the `--build=TYPE' option to select the type of
Packit 70b277
system on which you are compiling the package.
Packit 70b277
Packit 70b277
Sharing Defaults
Packit 70b277
================
Packit 70b277
Packit 70b277
   If you want to set default values for `configure' scripts to share,
Packit 70b277
you can create a site shell script called `config.site' that gives
Packit 70b277
default values for variables like `CC', `cache_file', and `prefix'.
Packit 70b277
`configure' looks for `PREFIX/share/config.site' if it exists, then
Packit 70b277
`PREFIX/etc/config.site' if it exists.  Or, you can set the
Packit 70b277
`CONFIG_SITE' environment variable to the location of the site script.
Packit 70b277
A warning: not all `configure' scripts look for a site script.
Packit 70b277
Packit 70b277
Operation Controls
Packit 70b277
==================
Packit 70b277
Packit 70b277
   `configure' recognizes the following options to control how it
Packit 70b277
operates.
Packit 70b277
Packit 70b277
`--cache-file=FILE'
Packit 70b277
     Use and save the results of the tests in FILE instead of
Packit 70b277
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
Packit 70b277
     debugging `configure'.
Packit 70b277
Packit 70b277
`--help'
Packit 70b277
     Print a summary of the options to `configure', and exit.
Packit 70b277
Packit 70b277
`--quiet'
Packit 70b277
`--silent'
Packit 70b277
`-q'
Packit 70b277
     Do not print messages saying which checks are being made.
Packit 70b277
Packit 70b277
`--srcdir=DIR'
Packit 70b277
     Look for the package's source code in directory DIR.  Usually
Packit 70b277
     `configure' can determine that directory automatically.
Packit 70b277
Packit 70b277
`--version'
Packit 70b277
     Print the version of Autoconf used to generate the `configure'
Packit 70b277
     script, and exit.
Packit 70b277
Packit 70b277
`configure' also accepts some other, not widely useful, options.
Packit 70b277