renatofilho@909: Installation Instructions renatofilho@909: ************************* renatofilho@909: renatofilho@909: Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free renatofilho@909: Software Foundation, Inc. renatofilho@909: renatofilho@909: This file is free documentation; the Free Software Foundation gives renatofilho@909: unlimited permission to copy, distribute and modify it. renatofilho@909: renatofilho@909: Basic Installation renatofilho@909: ================== renatofilho@909: renatofilho@909: These are generic installation instructions. renatofilho@909: renatofilho@909: The `configure' shell script attempts to guess correct values for renatofilho@909: various system-dependent variables used during compilation. It uses renatofilho@909: those values to create a `Makefile' in each directory of the package. renatofilho@909: It may also create one or more `.h' files containing system-dependent renatofilho@909: definitions. Finally, it creates a shell script `config.status' that renatofilho@909: you can run in the future to recreate the current configuration, and a renatofilho@909: file `config.log' containing compiler output (useful mainly for renatofilho@909: debugging `configure'). renatofilho@909: renatofilho@909: It can also use an optional file (typically called `config.cache' renatofilho@909: and enabled with `--cache-file=config.cache' or simply `-C') that saves renatofilho@909: the results of its tests to speed up reconfiguring. (Caching is renatofilho@909: disabled by default to prevent problems with accidental use of stale renatofilho@909: cache files.) renatofilho@909: renatofilho@909: If you need to do unusual things to compile the package, please try renatofilho@909: to figure out how `configure' could check whether to do them, and mail renatofilho@909: diffs or instructions to the address given in the `README' so they can renatofilho@909: be considered for the next release. If you are using the cache, and at renatofilho@909: some point `config.cache' contains results you don't want to keep, you renatofilho@909: may remove or edit it. renatofilho@909: renatofilho@909: The file `configure.ac' (or `configure.in') is used to create renatofilho@909: `configure' by a program called `autoconf'. You only need renatofilho@909: `configure.ac' if you want to change it or regenerate `configure' using renatofilho@909: a newer version of `autoconf'. renatofilho@909: renatofilho@909: The simplest way to compile this package is: renatofilho@909: renatofilho@909: 1. `cd' to the directory containing the package's source code and type renatofilho@909: `./configure' to configure the package for your system. If you're renatofilho@909: using `csh' on an old version of System V, you might need to type renatofilho@909: `sh ./configure' instead to prevent `csh' from trying to execute renatofilho@909: `configure' itself. renatofilho@909: renatofilho@909: Running `configure' takes awhile. While running, it prints some renatofilho@909: messages telling which features it is checking for. renatofilho@909: renatofilho@909: 2. Type `make' to compile the package. renatofilho@909: renatofilho@909: 3. Optionally, type `make check' to run any self-tests that come with renatofilho@909: the package. renatofilho@909: renatofilho@909: 4. Type `make install' to install the programs and any data files and renatofilho@909: documentation. renatofilho@909: renatofilho@909: 5. You can remove the program binaries and object files from the renatofilho@909: source code directory by typing `make clean'. To also remove the renatofilho@909: files that `configure' created (so you can compile the package for renatofilho@909: a different kind of computer), type `make distclean'. There is renatofilho@909: also a `make maintainer-clean' target, but that is intended mainly renatofilho@909: for the package's developers. If you use it, you may have to get renatofilho@909: all sorts of other programs in order to regenerate files that came renatofilho@909: with the distribution. renatofilho@909: renatofilho@909: Compilers and Options renatofilho@909: ===================== renatofilho@909: renatofilho@909: Some systems require unusual options for compilation or linking that the renatofilho@909: `configure' script does not know about. Run `./configure --help' for renatofilho@909: details on some of the pertinent environment variables. renatofilho@909: renatofilho@909: You can give `configure' initial values for configuration parameters renatofilho@909: by setting variables in the command line or in the environment. Here renatofilho@909: is an example: renatofilho@909: renatofilho@909: ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix renatofilho@909: renatofilho@909: *Note Defining Variables::, for more details. renatofilho@909: renatofilho@909: Compiling For Multiple Architectures renatofilho@909: ==================================== renatofilho@909: renatofilho@909: You can compile the package for more than one kind of computer at the renatofilho@909: same time, by placing the object files for each architecture in their renatofilho@909: own directory. To do this, you must use a version of `make' that renatofilho@909: supports the `VPATH' variable, such as GNU `make'. `cd' to the renatofilho@909: directory where you want the object files and executables to go and run renatofilho@909: the `configure' script. `configure' automatically checks for the renatofilho@909: source code in the directory that `configure' is in and in `..'. renatofilho@909: renatofilho@909: If you have to use a `make' that does not support the `VPATH' renatofilho@909: variable, you have to compile the package for one architecture at a renatofilho@909: time in the source code directory. After you have installed the renatofilho@909: package for one architecture, use `make distclean' before reconfiguring renatofilho@909: for another architecture. renatofilho@909: renatofilho@909: Installation Names renatofilho@909: ================== renatofilho@909: renatofilho@909: By default, `make install' installs the package's commands under renatofilho@909: `/usr/local/bin', include files under `/usr/local/include', etc. You renatofilho@909: can specify an installation prefix other than `/usr/local' by giving renatofilho@909: `configure' the option `--prefix=PREFIX'. renatofilho@909: renatofilho@909: You can specify separate installation prefixes for renatofilho@909: architecture-specific files and architecture-independent files. If you renatofilho@909: pass the option `--exec-prefix=PREFIX' to `configure', the package uses renatofilho@909: PREFIX as the prefix for installing programs and libraries. renatofilho@909: Documentation and other data files still use the regular prefix. renatofilho@909: renatofilho@909: In addition, if you use an unusual directory layout you can give renatofilho@909: options like `--bindir=DIR' to specify different values for particular renatofilho@909: kinds of files. Run `configure --help' for a list of the directories renatofilho@909: you can set and what kinds of files go in them. renatofilho@909: renatofilho@909: If the package supports it, you can cause programs to be installed renatofilho@909: with an extra prefix or suffix on their names by giving `configure' the renatofilho@909: option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. renatofilho@909: renatofilho@909: Optional Features renatofilho@909: ================= renatofilho@909: renatofilho@909: Some packages pay attention to `--enable-FEATURE' options to renatofilho@909: `configure', where FEATURE indicates an optional part of the package. renatofilho@909: They may also pay attention to `--with-PACKAGE' options, where PACKAGE renatofilho@909: is something like `gnu-as' or `x' (for the X Window System). The renatofilho@909: `README' should mention any `--enable-' and `--with-' options that the renatofilho@909: package recognizes. renatofilho@909: renatofilho@909: For packages that use the X Window System, `configure' can usually renatofilho@909: find the X include and library files automatically, but if it doesn't, renatofilho@909: you can use the `configure' options `--x-includes=DIR' and renatofilho@909: `--x-libraries=DIR' to specify their locations. renatofilho@909: renatofilho@909: Specifying the System Type renatofilho@909: ========================== renatofilho@909: renatofilho@909: There may be some features `configure' cannot figure out automatically, renatofilho@909: but needs to determine by the type of machine the package will run on. renatofilho@909: Usually, assuming the package is built to be run on the _same_ renatofilho@909: architectures, `configure' can figure that out, but if it prints a renatofilho@909: message saying it cannot guess the machine type, give it the renatofilho@909: `--build=TYPE' option. TYPE can either be a short name for the system renatofilho@909: type, such as `sun4', or a canonical name which has the form: renatofilho@909: renatofilho@909: CPU-COMPANY-SYSTEM renatofilho@909: renatofilho@909: where SYSTEM can have one of these forms: renatofilho@909: renatofilho@909: OS KERNEL-OS renatofilho@909: renatofilho@909: See the file `config.sub' for the possible values of each field. If renatofilho@909: `config.sub' isn't included in this package, then this package doesn't renatofilho@909: need to know the machine type. renatofilho@909: renatofilho@909: If you are _building_ compiler tools for cross-compiling, you should renatofilho@909: use the option `--target=TYPE' to select the type of system they will renatofilho@909: produce code for. renatofilho@909: renatofilho@909: If you want to _use_ a cross compiler, that generates code for a renatofilho@909: platform different from the build platform, you should specify the renatofilho@909: "host" platform (i.e., that on which the generated programs will renatofilho@909: eventually be run) with `--host=TYPE'. renatofilho@909: renatofilho@909: Sharing Defaults renatofilho@909: ================ renatofilho@909: renatofilho@909: If you want to set default values for `configure' scripts to share, you renatofilho@909: can create a site shell script called `config.site' that gives default renatofilho@909: values for variables like `CC', `cache_file', and `prefix'. renatofilho@909: `configure' looks for `PREFIX/share/config.site' if it exists, then renatofilho@909: `PREFIX/etc/config.site' if it exists. Or, you can set the renatofilho@909: `CONFIG_SITE' environment variable to the location of the site script. renatofilho@909: A warning: not all `configure' scripts look for a site script. renatofilho@909: renatofilho@909: Defining Variables renatofilho@909: ================== renatofilho@909: renatofilho@909: Variables not defined in a site shell script can be set in the renatofilho@909: environment passed to `configure'. However, some packages may run renatofilho@909: configure again during the build, and the customized values of these renatofilho@909: variables may be lost. In order to avoid this problem, you should set renatofilho@909: them in the `configure' command line, using `VAR=value'. For example: renatofilho@909: renatofilho@909: ./configure CC=/usr/local2/bin/gcc renatofilho@909: renatofilho@909: causes the specified `gcc' to be used as the C compiler (unless it is renatofilho@909: overridden in the site shell script). Here is a another example: renatofilho@909: renatofilho@909: /bin/bash ./configure CONFIG_SHELL=/bin/bash renatofilho@909: renatofilho@909: Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent renatofilho@909: configuration-related scripts to be executed by `/bin/bash'. renatofilho@909: renatofilho@909: `configure' Invocation renatofilho@909: ====================== renatofilho@909: renatofilho@909: `configure' recognizes the following options to control how it operates. renatofilho@909: renatofilho@909: `--help' renatofilho@909: `-h' renatofilho@909: Print a summary of the options to `configure', and exit. renatofilho@909: renatofilho@909: `--version' renatofilho@909: `-V' renatofilho@909: Print the version of Autoconf used to generate the `configure' renatofilho@909: script, and exit. renatofilho@909: renatofilho@909: `--cache-file=FILE' renatofilho@909: Enable the cache: use and save the results of the tests in FILE, renatofilho@909: traditionally `config.cache'. FILE defaults to `/dev/null' to renatofilho@909: disable caching. renatofilho@909: renatofilho@909: `--config-cache' renatofilho@909: `-C' renatofilho@909: Alias for `--cache-file=config.cache'. renatofilho@909: renatofilho@909: `--quiet' renatofilho@909: `--silent' renatofilho@909: `-q' renatofilho@909: Do not print messages saying which checks are being made. To renatofilho@909: suppress all normal output, redirect it to `/dev/null' (any error renatofilho@909: messages will still be shown). renatofilho@909: renatofilho@909: `--srcdir=DIR' renatofilho@909: Look for the package's source code in directory DIR. Usually renatofilho@909: `configure' can determine that directory automatically. renatofilho@909: renatofilho@909: `configure' also accepts some other, not widely useful, options. Run renatofilho@909: `configure --help' for more details. renatofilho@909: