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