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