Changeset 153 in kBuild for branches/GNU/src/gmake/INSTALL
- Timestamp:
- Sep 8, 2004 2:43:30 AM (20 years ago)
- File:
-
- 1 edited
-
branches/GNU/src/gmake/INSTALL (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
-
branches/GNU/src/gmake/INSTALL
r54 r153 1 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software 2 Foundation, Inc. 3 4 This file is free documentation; the Free Software Foundation gives 5 unlimited permission to copy, distribute and modify it. 6 1 7 Basic Installation 2 8 ================== 9 10 These are generic installation instructions. 3 11 4 12 The `configure' shell script attempts to guess correct values for … … 7 15 It may also create one or more `.h' files containing system-dependent 8 16 definitions. Finally, it creates a shell script `config.status' that 9 you can run in the future to recreate the current configuration, a file 10 `config.cache' that saves the results of its tests to speed up 11 reconfiguring, and a file `config.log' containing compiler output 12 (useful mainly for debugging `configure'). 17 you can run in the future to recreate the current configuration, and a 18 file `config.log' containing compiler output (useful mainly for 19 debugging `configure'). 20 21 It can also use an optional file (typically called `config.cache' 22 and enabled with `--cache-file=config.cache' or simply `-C') that saves 23 the results of its tests to speed up reconfiguring. (Caching is 24 disabled by default to prevent problems with accidental use of stale 25 cache files.) 13 26 14 27 If you need to do unusual things to compile the package, please try 15 28 to figure out how `configure' could check whether to do them, and mail 16 29 diffs or instructions to the address given in the `README' so they can 17 be considered for the next release. If at some point `config.cache' 18 contains results you don't want to keep, you may remove or edit it. 19 20 The file `configure.in' is used to create `configure' by a program 21 called `autoconf'. You only need `configure.in' if you want to change 22 it or regenerate `configure' using a newer version of `autoconf'. 30 be considered for the next release. If you are using the cache, and at 31 some point `config.cache' contains results you don't want to keep, you 32 may remove or edit it. 33 34 The file `configure.ac' (or `configure.in') is used to create 35 `configure' by a program called `autoconf'. You only need 36 `configure.ac' if you want to change it or regenerate `configure' using 37 a newer version of `autoconf'. 23 38 24 39 The simplest way to compile this package is: … … 35 50 2. Type `make' to compile the package. 36 51 37 If you're building GNU make on a system which does not already have 38 a `make', you can use the build.sh shell script to compile. Run 39 `sh ./build.sh'. This should compile the program in the current 40 directory. Then you will have a Make program that you can use for 41 `make install', or whatever else. 42 43 3. Optionally, type `./make check' to run any self-tests that come with 52 3. Optionally, type `make check' to run any self-tests that come with 44 53 the package. 45 54 … … 60 69 61 70 Some systems require unusual options for compilation or linking that 62 the `configure' script does not know about. You can give `configure' 63 initial values for variables by setting them in the environment. Using 64 a Bourne-compatible shell, you can do that on the command line like 65 this: 66 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure 67 68 Or on systems that have the `env' program, you can do it like this: 69 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure 71 the `configure' script does not know about. Run `./configure --help' 72 for details on some of the pertinent environment variables. 73 74 You can give `configure' initial values for configuration parameters 75 by setting variables in the command line or in the environment. Here 76 is an example: 77 78 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix 79 80 *Note Defining Variables::, for more details. 70 81 71 82 Compiling For Multiple Architectures … … 80 91 source code in the directory that `configure' is in and in `..'. 81 92 82 If you have to use a `make' that does not support sthe `VPATH'83 variable, you have to compile the package for one architecture at a time84 in the source code directory. After you have installed the package for 85 one architecture, use `make distclean' before reconfiguring for another 86 architecture.93 If you have to use a `make' that does not support the `VPATH' 94 variable, you have to compile the package for one architecture at a 95 time in the source code directory. After you have installed the 96 package for one architecture, use `make distclean' before reconfiguring 97 for another architecture. 87 98 88 99 Installation Names … … 127 138 ========================== 128 139 129 There may be some features `configure' can not figure out 130 automatically, but needs to determine by the type of host the package 131 will run on. Usually `configure' can figure that out, but if it prints 132 a message saying it can not guess the host type, give it the 133 `--host=TYPE' option. TYPE can either be a short name for the system 134 type, such as `sun4', or a canonical name with three fields: 140 There may be some features `configure' cannot figure out 141 automatically, but needs to determine by the type of machine the package 142 will run on. Usually, assuming the package is built to be run on the 143 _same_ architectures, `configure' can figure that out, but if it prints 144 a message saying it cannot guess the machine type, give it the 145 `--build=TYPE' option. TYPE can either be a short name for the system 146 type, such as `sun4', or a canonical name which has the form: 147 135 148 CPU-COMPANY-SYSTEM 136 149 137 See the file `config.sub' for the possible values of each field. If 150 where SYSTEM can have one of these forms: 151 152 OS KERNEL-OS 153 154 See the file `config.sub' for the possible values of each field. If 138 155 `config.sub' isn't included in this package, then this package doesn't 139 need to know the hosttype.140 141 If you are building compiler tools for cross-compiling, you can also156 need to know the machine type. 157 158 If you are _building_ compiler tools for cross-compiling, you should 142 159 use the `--target=TYPE' option to select the type of system they will 143 produce code for and the `--build=TYPE' option to select the type of 144 system on which you are compiling the package. 160 produce code for. 161 162 If you want to _use_ a cross compiler, that generates code for a 163 platform different from the build platform, you should specify the 164 "host" platform (i.e., that on which the generated programs will 165 eventually be run) with `--host=TYPE'. 145 166 146 167 Sharing Defaults … … 155 176 A warning: not all `configure' scripts look for a site script. 156 177 157 Operation Controls178 Defining Variables 158 179 ================== 180 181 Variables not defined in a site shell script can be set in the 182 environment passed to `configure'. However, some packages may run 183 configure again during the build, and the customized values of these 184 variables may be lost. In order to avoid this problem, you should set 185 them in the `configure' command line, using `VAR=value'. For example: 186 187 ./configure CC=/usr/local2/bin/gcc 188 189 will cause the specified gcc to be used as the C compiler (unless it is 190 overridden in the site shell script). 191 192 `configure' Invocation 193 ====================== 159 194 160 195 `configure' recognizes the following options to control how it 161 196 operates. 162 197 198 `--help' 199 `-h' 200 Print a summary of the options to `configure', and exit. 201 202 `--version' 203 `-V' 204 Print the version of Autoconf used to generate the `configure' 205 script, and exit. 206 163 207 `--cache-file=FILE' 164 Use and save the results of the tests in FILE instead of 165 `./config.cache'. Set FILE to `/dev/null' to disable caching, for 166 debugging `configure'. 167 168 `--help' 169 Print a summary of the options to `configure', and exit. 208 Enable the cache: use and save the results of the tests in FILE, 209 traditionally `config.cache'. FILE defaults to `/dev/null' to 210 disable caching. 211 212 `--config-cache' 213 `-C' 214 Alias for `--cache-file=config.cache'. 170 215 171 216 `--quiet' … … 180 225 `configure' can determine that directory automatically. 181 226 182 `--version' 183 Print the version of Autoconf used to generate the `configure' 184 script, and exit. 185 186 `configure' also accepts some other, not widely useful, options. 187 227 `configure' also accepts some other, not widely useful, options. Run 228 `configure --help' for more details. 229
Note:
See TracChangeset
for help on using the changeset viewer.
