1+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2This file contains the typical GNU installation descriptions. 3The gl-117 specific installation instructions are covert (briefly) 4in the file README. 5+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 6 7Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software 8Foundation, Inc. 9 10 This file is free documentation; the Free Software Foundation gives 11unlimited permission to copy, distribute and modify it. 12 13Basic Installation 14================== 15 16 These are generic installation instructions. 17 18 The `configure' shell script attempts to guess correct values for 19various system-dependent variables used during compilation. It uses 20those values to create a `Makefile' in each directory of the package. 21It may also create one or more `.h' files containing system-dependent 22definitions. Finally, it creates a shell script `config.status' that 23you can run in the future to recreate the current configuration, and a 24file `config.log' containing compiler output (useful mainly for 25debugging `configure'). 26 27 It can also use an optional file (typically called `config.cache' 28and enabled with `--cache-file=config.cache' or simply `-C') that saves 29the results of its tests to speed up reconfiguring. (Caching is 30disabled by default to prevent problems with accidental use of stale 31cache files.) 32 33 If you need to do unusual things to compile the package, please try 34to figure out how `configure' could check whether to do them, and mail 35diffs or instructions to the address given in the `README' so they can 36be considered for the next release. If you are using the cache, and at 37some point `config.cache' contains results you don't want to keep, you 38may remove or edit it. 39 40 The file `configure.ac' (or `configure.in') is used to create 41`configure' by a program called `autoconf'. You only need 42`configure.ac' if you want to change it or regenerate `configure' using 43a newer version of `autoconf'. 44 45The simplest way to compile this package is: 46 47 1. `cd' to the directory containing the package's source code and type 48 `./configure' to configure the package for your system. If you're 49 using `csh' on an old version of System V, you might need to type 50 `sh ./configure' instead to prevent `csh' from trying to execute 51 `configure' itself. 52 53 Running `configure' takes awhile. While running, it prints some 54 messages telling which features it is checking for. 55 56 2. Type `make' to compile the package. 57 58 3. Optionally, type `make check' to run any self-tests that come with 59 the package. 60 61 4. Type `make install' to install the programs and any data files and 62 documentation. 63 64 5. You can remove the program binaries and object files from the 65 source code directory by typing `make clean'. To also remove the 66 files that `configure' created (so you can compile the package for 67 a different kind of computer), type `make distclean'. There is 68 also a `make maintainer-clean' target, but that is intended mainly 69 for the package's developers. If you use it, you may have to get 70 all sorts of other programs in order to regenerate files that came 71 with the distribution. 72 73Compilers and Options 74===================== 75 76 Some systems require unusual options for compilation or linking that 77the `configure' script does not know about. Run `./configure --help' 78for details on some of the pertinent environment variables. 79 80 You can give `configure' initial values for configuration parameters 81by setting variables in the command line or in the environment. Here 82is an example: 83 84 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix 85 86 *Note Defining Variables::, for more details. 87 88Compiling For Multiple Architectures 89==================================== 90 91 You can compile the package for more than one kind of computer at the 92same time, by placing the object files for each architecture in their 93own directory. To do this, you must use a version of `make' that 94supports the `VPATH' variable, such as GNU `make'. `cd' to the 95directory where you want the object files and executables to go and run 96the `configure' script. `configure' automatically checks for the 97source code in the directory that `configure' is in and in `..'. 98 99 If you have to use a `make' that does not support the `VPATH' 100variable, you have to compile the package for one architecture at a 101time in the source code directory. After you have installed the 102package for one architecture, use `make distclean' before reconfiguring 103for another architecture. 104 105Installation Names 106================== 107 108 By default, `make install' will install the package's files in 109`/usr/local/bin', `/usr/local/man', etc. You can specify an 110installation prefix other than `/usr/local' by giving `configure' the 111option `--prefix=PATH'. 112 113 You can specify separate installation prefixes for 114architecture-specific files and architecture-independent files. If you 115give `configure' the option `--exec-prefix=PATH', the package will use 116PATH as the prefix for installing programs and libraries. 117Documentation and other data files will still use the regular prefix. 118 119 In addition, if you use an unusual directory layout you can give 120options like `--bindir=PATH' to specify different values for particular 121kinds of files. Run `configure --help' for a list of the directories 122you can set and what kinds of files go in them. 123 124 If the package supports it, you can cause programs to be installed 125with an extra prefix or suffix on their names by giving `configure' the 126option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 127 128Optional Features 129================= 130 131 Some packages pay attention to `--enable-FEATURE' options to 132`configure', where FEATURE indicates an optional part of the package. 133They may also pay attention to `--with-PACKAGE' options, where PACKAGE 134is something like `gnu-as' or `x' (for the X Window System). The 135`README' should mention any `--enable-' and `--with-' options that the 136package recognizes. 137 138 For packages that use the X Window System, `configure' can usually 139find the X include and library files automatically, but if it doesn't, 140you can use the `configure' options `--x-includes=DIR' and 141`--x-libraries=DIR' to specify their locations. 142 143Specifying the System Type 144========================== 145 146 There may be some features `configure' cannot figure out 147automatically, but needs to determine by the type of machine the package 148will run on. Usually, assuming the package is built to be run on the 149_same_ architectures, `configure' can figure that out, but if it prints 150a message saying it cannot guess the machine type, give it the 151`--build=TYPE' option. TYPE can either be a short name for the system 152type, such as `sun4', or a canonical name which has the form: 153 154 CPU-COMPANY-SYSTEM 155 156where SYSTEM can have one of these forms: 157 158 OS KERNEL-OS 159 160 See the file `config.sub' for the possible values of each field. If 161`config.sub' isn't included in this package, then this package doesn't 162need to know the machine type. 163 164 If you are _building_ compiler tools for cross-compiling, you should 165use the `--target=TYPE' option to select the type of system they will 166produce code for. 167 168 If you want to _use_ a cross compiler, that generates code for a 169platform different from the build platform, you should specify the 170"host" platform (i.e., that on which the generated programs will 171eventually be run) with `--host=TYPE'. 172 173Sharing Defaults 174================ 175 176 If you want to set default values for `configure' scripts to share, 177you can create a site shell script called `config.site' that gives 178default values for variables like `CC', `cache_file', and `prefix'. 179`configure' looks for `PREFIX/share/config.site' if it exists, then 180`PREFIX/etc/config.site' if it exists. Or, you can set the 181`CONFIG_SITE' environment variable to the location of the site script. 182A warning: not all `configure' scripts look for a site script. 183 184Defining Variables 185================== 186 187 Variables not defined in a site shell script can be set in the 188environment passed to `configure'. However, some packages may run 189configure again during the build, and the customized values of these 190variables may be lost. In order to avoid this problem, you should set 191them in the `configure' command line, using `VAR=value'. For example: 192 193 ./configure CC=/usr/local2/bin/gcc 194 195will cause the specified gcc to be used as the C compiler (unless it is 196overridden in the site shell script). 197 198`configure' Invocation 199====================== 200 201 `configure' recognizes the following options to control how it 202operates. 203 204`--help' 205`-h' 206 Print a summary of the options to `configure', and exit. 207 208`--version' 209`-V' 210 Print the version of Autoconf used to generate the `configure' 211 script, and exit. 212 213`--cache-file=FILE' 214 Enable the cache: use and save the results of the tests in FILE, 215 traditionally `config.cache'. FILE defaults to `/dev/null' to 216 disable caching. 217 218`--config-cache' 219`-C' 220 Alias for `--cache-file=config.cache'. 221 222`--quiet' 223`--silent' 224`-q' 225 Do not print messages saying which checks are being made. To 226 suppress all normal output, redirect it to `/dev/null' (any error 227 messages will still be shown). 228 229`--srcdir=DIR' 230 Look for the package's source code in directory DIR. Usually 231 `configure' can determine that directory automatically. 232 233`configure' also accepts some other, not widely useful, options. Run 234`configure --help' for more details. 235 236