Chris@39: Installation Instructions Chris@39: ************************* Chris@39: Chris@39: Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, Chris@39: 2006, 2007, 2008, 2009 Free Software Foundation, Inc. Chris@39: Chris@39: Copying and distribution of this file, with or without modification, Chris@39: are permitted in any medium without royalty provided the copyright Chris@39: notice and this notice are preserved. This file is offered as-is, Chris@39: without warranty of any kind. Chris@39: Chris@39: Basic Installation Chris@39: ================== Chris@39: Chris@39: Briefly, the shell commands `./configure; make; make install' should Chris@39: configure, build, and install this package. The following Chris@39: more-detailed instructions are generic; see the `README' file for Chris@39: instructions specific to this package. Some packages provide this Chris@39: `INSTALL' file but do not implement all of the features documented Chris@39: below. The lack of an optional feature in a given package is not Chris@39: necessarily a bug. More recommendations for GNU packages can be found Chris@39: in *note Makefile Conventions: (standards)Makefile Conventions. Chris@39: Chris@39: The `configure' shell script attempts to guess correct values for Chris@39: various system-dependent variables used during compilation. It uses Chris@39: those values to create a `Makefile' in each directory of the package. Chris@39: It may also create one or more `.h' files containing system-dependent Chris@39: definitions. Finally, it creates a shell script `config.status' that Chris@39: you can run in the future to recreate the current configuration, and a Chris@39: file `config.log' containing compiler output (useful mainly for Chris@39: debugging `configure'). Chris@39: Chris@39: It can also use an optional file (typically called `config.cache' Chris@39: and enabled with `--cache-file=config.cache' or simply `-C') that saves Chris@39: the results of its tests to speed up reconfiguring. Caching is Chris@39: disabled by default to prevent problems with accidental use of stale Chris@39: cache files. Chris@39: Chris@39: If you need to do unusual things to compile the package, please try Chris@39: to figure out how `configure' could check whether to do them, and mail Chris@39: diffs or instructions to the address given in the `README' so they can Chris@39: be considered for the next release. If you are using the cache, and at Chris@39: some point `config.cache' contains results you don't want to keep, you Chris@39: may remove or edit it. Chris@39: Chris@39: The file `configure.ac' (or `configure.in') is used to create Chris@39: `configure' by a program called `autoconf'. You need `configure.ac' if Chris@39: you want to change it or regenerate `configure' using a newer version Chris@39: of `autoconf'. Chris@39: Chris@39: The simplest way to compile this package is: Chris@39: Chris@39: 1. `cd' to the directory containing the package's source code and type Chris@39: `./configure' to configure the package for your system. Chris@39: Chris@39: Running `configure' might take a while. While running, it prints Chris@39: some messages telling which features it is checking for. Chris@39: Chris@39: 2. Type `make' to compile the package. Chris@39: Chris@39: 3. Optionally, type `make check' to run any self-tests that come with Chris@39: the package, generally using the just-built uninstalled binaries. Chris@39: Chris@39: 4. Type `make install' to install the programs and any data files and Chris@39: documentation. When installing into a prefix owned by root, it is Chris@39: recommended that the package be configured and built as a regular Chris@39: user, and only the `make install' phase executed with root Chris@39: privileges. Chris@39: Chris@39: 5. Optionally, type `make installcheck' to repeat any self-tests, but Chris@39: this time using the binaries in their final installed location. Chris@39: This target does not install anything. Running this target as a Chris@39: regular user, particularly if the prior `make install' required Chris@39: root privileges, verifies that the installation completed Chris@39: correctly. Chris@39: Chris@39: 6. You can remove the program binaries and object files from the Chris@39: source code directory by typing `make clean'. To also remove the Chris@39: files that `configure' created (so you can compile the package for Chris@39: a different kind of computer), type `make distclean'. There is Chris@39: also a `make maintainer-clean' target, but that is intended mainly Chris@39: for the package's developers. If you use it, you may have to get Chris@39: all sorts of other programs in order to regenerate files that came Chris@39: with the distribution. Chris@39: Chris@39: 7. Often, you can also type `make uninstall' to remove the installed Chris@39: files again. In practice, not all packages have tested that Chris@39: uninstallation works correctly, even though it is required by the Chris@39: GNU Coding Standards. Chris@39: Chris@39: 8. Some packages, particularly those that use Automake, provide `make Chris@39: distcheck', which can by used by developers to test that all other Chris@39: targets like `make install' and `make uninstall' work correctly. Chris@39: This target is generally not run by end users. Chris@39: Chris@39: Compilers and Options Chris@39: ===================== Chris@39: Chris@39: Some systems require unusual options for compilation or linking that Chris@39: the `configure' script does not know about. Run `./configure --help' Chris@39: for details on some of the pertinent environment variables. Chris@39: Chris@39: You can give `configure' initial values for configuration parameters Chris@39: by setting variables in the command line or in the environment. Here Chris@39: is an example: Chris@39: Chris@39: ./configure CC=c99 CFLAGS=-g LIBS=-lposix Chris@39: Chris@39: *Note Defining Variables::, for more details. Chris@39: Chris@39: Compiling For Multiple Architectures Chris@39: ==================================== Chris@39: Chris@39: You can compile the package for more than one kind of computer at the Chris@39: same time, by placing the object files for each architecture in their Chris@39: own directory. To do this, you can use GNU `make'. `cd' to the Chris@39: directory where you want the object files and executables to go and run Chris@39: the `configure' script. `configure' automatically checks for the Chris@39: source code in the directory that `configure' is in and in `..'. This Chris@39: is known as a "VPATH" build. Chris@39: Chris@39: With a non-GNU `make', it is safer to compile the package for one Chris@39: architecture at a time in the source code directory. After you have Chris@39: installed the package for one architecture, use `make distclean' before Chris@39: reconfiguring for another architecture. Chris@39: Chris@39: On MacOS X 10.5 and later systems, you can create libraries and Chris@39: executables that work on multiple system types--known as "fat" or Chris@39: "universal" binaries--by specifying multiple `-arch' options to the Chris@39: compiler but only a single `-arch' option to the preprocessor. Like Chris@39: this: Chris@39: Chris@39: ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ Chris@39: CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ Chris@39: CPP="gcc -E" CXXCPP="g++ -E" Chris@39: Chris@39: This is not guaranteed to produce working output in all cases, you Chris@39: may have to build one architecture at a time and combine the results Chris@39: using the `lipo' tool if you have problems. Chris@39: Chris@39: Installation Names Chris@39: ================== Chris@39: Chris@39: By default, `make install' installs the package's commands under Chris@39: `/usr/local/bin', include files under `/usr/local/include', etc. You Chris@39: can specify an installation prefix other than `/usr/local' by giving Chris@39: `configure' the option `--prefix=PREFIX', where PREFIX must be an Chris@39: absolute file name. Chris@39: Chris@39: You can specify separate installation prefixes for Chris@39: architecture-specific files and architecture-independent files. If you Chris@39: pass the option `--exec-prefix=PREFIX' to `configure', the package uses Chris@39: PREFIX as the prefix for installing programs and libraries. Chris@39: Documentation and other data files still use the regular prefix. Chris@39: Chris@39: In addition, if you use an unusual directory layout you can give Chris@39: options like `--bindir=DIR' to specify different values for particular Chris@39: kinds of files. Run `configure --help' for a list of the directories Chris@39: you can set and what kinds of files go in them. In general, the Chris@39: default for these options is expressed in terms of `${prefix}', so that Chris@39: specifying just `--prefix' will affect all of the other directory Chris@39: specifications that were not explicitly provided. Chris@39: Chris@39: The most portable way to affect installation locations is to pass the Chris@39: correct locations to `configure'; however, many packages provide one or Chris@39: both of the following shortcuts of passing variable assignments to the Chris@39: `make install' command line to change installation locations without Chris@39: having to reconfigure or recompile. Chris@39: Chris@39: The first method involves providing an override variable for each Chris@39: affected directory. For example, `make install Chris@39: prefix=/alternate/directory' will choose an alternate location for all Chris@39: directory configuration variables that were expressed in terms of Chris@39: `${prefix}'. Any directories that were specified during `configure', Chris@39: but not in terms of `${prefix}', must each be overridden at install Chris@39: time for the entire installation to be relocated. The approach of Chris@39: makefile variable overrides for each directory variable is required by Chris@39: the GNU Coding Standards, and ideally causes no recompilation. Chris@39: However, some platforms have known limitations with the semantics of Chris@39: shared libraries that end up requiring recompilation when using this Chris@39: method, particularly noticeable in packages that use GNU Libtool. Chris@39: Chris@39: The second method involves providing the `DESTDIR' variable. For Chris@39: example, `make install DESTDIR=/alternate/directory' will prepend Chris@39: `/alternate/directory' before all installation names. The approach of Chris@39: `DESTDIR' overrides is not required by the GNU Coding Standards, and Chris@39: does not work on platforms that have drive letters. On the other hand, Chris@39: it does better at avoiding recompilation issues, and works well even Chris@39: when some directory options were not specified in terms of `${prefix}' Chris@39: at `configure' time. Chris@39: Chris@39: Optional Features Chris@39: ================= Chris@39: Chris@39: If the package supports it, you can cause programs to be installed Chris@39: with an extra prefix or suffix on their names by giving `configure' the Chris@39: option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. Chris@39: Chris@39: Some packages pay attention to `--enable-FEATURE' options to Chris@39: `configure', where FEATURE indicates an optional part of the package. Chris@39: They may also pay attention to `--with-PACKAGE' options, where PACKAGE Chris@39: is something like `gnu-as' or `x' (for the X Window System). The Chris@39: `README' should mention any `--enable-' and `--with-' options that the Chris@39: package recognizes. Chris@39: Chris@39: For packages that use the X Window System, `configure' can usually Chris@39: find the X include and library files automatically, but if it doesn't, Chris@39: you can use the `configure' options `--x-includes=DIR' and Chris@39: `--x-libraries=DIR' to specify their locations. Chris@39: Chris@39: Some packages offer the ability to configure how verbose the Chris@39: execution of `make' will be. For these packages, running `./configure Chris@39: --enable-silent-rules' sets the default to minimal output, which can be Chris@39: overridden with `make V=1'; while running `./configure Chris@39: --disable-silent-rules' sets the default to verbose, which can be Chris@39: overridden with `make V=0'. Chris@39: Chris@39: Particular systems Chris@39: ================== Chris@39: Chris@39: On HP-UX, the default C compiler is not ANSI C compatible. If GNU Chris@39: CC is not installed, it is recommended to use the following options in Chris@39: order to use an ANSI C compiler: Chris@39: Chris@39: ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" Chris@39: Chris@39: and if that doesn't work, install pre-built binaries of GCC for HP-UX. Chris@39: Chris@39: On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot Chris@39: parse its `' header file. The option `-nodtk' can be used as Chris@39: a workaround. If GNU CC is not installed, it is therefore recommended Chris@39: to try Chris@39: Chris@39: ./configure CC="cc" Chris@39: Chris@39: and if that doesn't work, try Chris@39: Chris@39: ./configure CC="cc -nodtk" Chris@39: Chris@39: On Solaris, don't put `/usr/ucb' early in your `PATH'. This Chris@39: directory contains several dysfunctional programs; working variants of Chris@39: these programs are available in `/usr/bin'. So, if you need `/usr/ucb' Chris@39: in your `PATH', put it _after_ `/usr/bin'. Chris@39: Chris@39: On Haiku, software installed for all users goes in `/boot/common', Chris@39: not `/usr/local'. It is recommended to use the following options: Chris@39: Chris@39: ./configure --prefix=/boot/common Chris@39: Chris@39: Specifying the System Type Chris@39: ========================== Chris@39: Chris@39: There may be some features `configure' cannot figure out Chris@39: automatically, but needs to determine by the type of machine the package Chris@39: will run on. Usually, assuming the package is built to be run on the Chris@39: _same_ architectures, `configure' can figure that out, but if it prints Chris@39: a message saying it cannot guess the machine type, give it the Chris@39: `--build=TYPE' option. TYPE can either be a short name for the system Chris@39: type, such as `sun4', or a canonical name which has the form: Chris@39: Chris@39: CPU-COMPANY-SYSTEM Chris@39: Chris@39: where SYSTEM can have one of these forms: Chris@39: Chris@39: OS Chris@39: KERNEL-OS Chris@39: Chris@39: See the file `config.sub' for the possible values of each field. If Chris@39: `config.sub' isn't included in this package, then this package doesn't Chris@39: need to know the machine type. Chris@39: Chris@39: If you are _building_ compiler tools for cross-compiling, you should Chris@39: use the option `--target=TYPE' to select the type of system they will Chris@39: produce code for. Chris@39: Chris@39: If you want to _use_ a cross compiler, that generates code for a Chris@39: platform different from the build platform, you should specify the Chris@39: "host" platform (i.e., that on which the generated programs will Chris@39: eventually be run) with `--host=TYPE'. Chris@39: Chris@39: Sharing Defaults Chris@39: ================ Chris@39: Chris@39: If you want to set default values for `configure' scripts to share, Chris@39: you can create a site shell script called `config.site' that gives Chris@39: default values for variables like `CC', `cache_file', and `prefix'. Chris@39: `configure' looks for `PREFIX/share/config.site' if it exists, then Chris@39: `PREFIX/etc/config.site' if it exists. Or, you can set the Chris@39: `CONFIG_SITE' environment variable to the location of the site script. Chris@39: A warning: not all `configure' scripts look for a site script. Chris@39: Chris@39: Defining Variables Chris@39: ================== Chris@39: Chris@39: Variables not defined in a site shell script can be set in the Chris@39: environment passed to `configure'. However, some packages may run Chris@39: configure again during the build, and the customized values of these Chris@39: variables may be lost. In order to avoid this problem, you should set Chris@39: them in the `configure' command line, using `VAR=value'. For example: Chris@39: Chris@39: ./configure CC=/usr/local2/bin/gcc Chris@39: Chris@39: causes the specified `gcc' to be used as the C compiler (unless it is Chris@39: overridden in the site shell script). Chris@39: Chris@39: Unfortunately, this technique does not work for `CONFIG_SHELL' due to Chris@39: an Autoconf bug. Until the bug is fixed you can use this workaround: Chris@39: Chris@39: CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash Chris@39: Chris@39: `configure' Invocation Chris@39: ====================== Chris@39: Chris@39: `configure' recognizes the following options to control how it Chris@39: operates. Chris@39: Chris@39: `--help' Chris@39: `-h' Chris@39: Print a summary of all of the options to `configure', and exit. Chris@39: Chris@39: `--help=short' Chris@39: `--help=recursive' Chris@39: Print a summary of the options unique to this package's Chris@39: `configure', and exit. The `short' variant lists options used Chris@39: only in the top level, while the `recursive' variant lists options Chris@39: also present in any nested packages. Chris@39: Chris@39: `--version' Chris@39: `-V' Chris@39: Print the version of Autoconf used to generate the `configure' Chris@39: script, and exit. Chris@39: Chris@39: `--cache-file=FILE' Chris@39: Enable the cache: use and save the results of the tests in FILE, Chris@39: traditionally `config.cache'. FILE defaults to `/dev/null' to Chris@39: disable caching. Chris@39: Chris@39: `--config-cache' Chris@39: `-C' Chris@39: Alias for `--cache-file=config.cache'. Chris@39: Chris@39: `--quiet' Chris@39: `--silent' Chris@39: `-q' Chris@39: Do not print messages saying which checks are being made. To Chris@39: suppress all normal output, redirect it to `/dev/null' (any error Chris@39: messages will still be shown). Chris@39: Chris@39: `--srcdir=DIR' Chris@39: Look for the package's source code in directory DIR. Usually Chris@39: `configure' can determine that directory automatically. Chris@39: Chris@39: `--prefix=DIR' Chris@39: Use DIR as the installation prefix. *note Installation Names:: Chris@39: for more details, including other options available for fine-tuning Chris@39: the installation locations. Chris@39: Chris@39: `--no-create' Chris@39: `-n' Chris@39: Run the configure checks, but stop before creating any output Chris@39: files. Chris@39: Chris@39: `configure' also accepts some other, not widely useful, options. Run Chris@39: `configure --help' for more details. Chris@39: