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