| 1 | Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, |
|
|
| 2 | Inc. |
|
|
| 3 | |
|
|
| 4 | This file is free documentation; the Free Software Foundation gives |
|
|
| 5 | unlimited permission to copy, distribute and modify it. |
|
|
| 6 | |
|
|
| 7 | Basic Installation |
1 | Basic Installation |
| 8 | ================== |
2 | ================== |
| 9 | |
3 | |
| 10 | These are generic installation instructions. |
4 | These are generic installation instructions. |
| 11 | |
5 | |
| 12 | The `configure' shell script attempts to guess correct values for |
6 | The `configure' shell script attempts to guess correct values for |
| 13 | various system-dependent variables used during compilation. It uses |
7 | various system-dependent variables used during compilation. It uses |
| 14 | those values to create a `Makefile' in each directory of the package. |
8 | those values to create a `Makefile' in each directory of the package. |
| 15 | It may also create one or more `.h' files containing system-dependent |
9 | It may also create one or more `.h' files containing system-dependent |
| 16 | definitions. Finally, it creates a shell script `config.status' that |
10 | definitions. Finally, it creates a shell script `config.status' that |
| 17 | you can run in the future to recreate the current configuration, and a |
11 | you can run in the future to recreate the current configuration, a file |
| 18 | file `config.log' containing compiler output (useful mainly for |
12 | `config.cache' that saves the results of its tests to speed up |
| 19 | debugging `configure'). |
13 | reconfiguring, and a file `config.log' containing compiler output |
| 20 | |
14 | (useful mainly for debugging `configure'). |
| 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.) |
|
|
| 26 | |
15 | |
| 27 | If you need to do unusual things to compile the package, please try |
16 | If you need to do unusual things to compile the package, please try |
| 28 | to figure out how `configure' could check whether to do them, and mail |
17 | to figure out how `configure' could check whether to do them, and mail |
| 29 | diffs or instructions to the address given in the `README' so they can |
18 | diffs or instructions to the address given in the `README' so they can |
| 30 | be considered for the next release. If you are using the cache, and at |
19 | be considered for the next release. If at some point `config.cache' |
| 31 | some point `config.cache' contains results you don't want to keep, you |
20 | contains results you don't want to keep, you may remove or edit it. |
| 32 | may remove or edit it. |
|
|
| 33 | |
21 | |
| 34 | The file `configure.ac' (or `configure.in') is used to create |
22 | The file `configure.in' is used to create `configure' by a program |
| 35 | `configure' by a program called `autoconf'. You only need |
23 | called `autoconf'. You only need `configure.in' if you want to change |
| 36 | `configure.ac' if you want to change it or regenerate `configure' using |
24 | it or regenerate `configure' using a newer version of `autoconf'. |
| 37 | a newer version of `autoconf'. |
|
|
| 38 | |
25 | |
| 39 | The simplest way to compile this package is: |
26 | The simplest way to compile this package is: |
| 40 | |
27 | |
| 41 | 1. `cd' to the directory containing the package's source code and type |
28 | 1. `cd' to the directory containing the package's source code and type |
| 42 | `./configure' to configure the package for your system. If you're |
29 | `./configure' to configure the package for your system. If you're |
| … | |
… | |
| 66 | |
53 | |
| 67 | Compilers and Options |
54 | Compilers and Options |
| 68 | ===================== |
55 | ===================== |
| 69 | |
56 | |
| 70 | Some systems require unusual options for compilation or linking that |
57 | Some systems require unusual options for compilation or linking that |
| 71 | the `configure' script does not know about. Run `./configure --help' |
58 | the `configure' script does not know about. You can give `configure' |
| 72 | for details on some of the pertinent environment variables. |
59 | initial values for variables by setting them in the environment. Using |
|
|
60 | a Bourne-compatible shell, you can do that on the command line like |
|
|
61 | this: |
|
|
62 | CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure |
| 73 | |
63 | |
| 74 | You can give `configure' initial values for variables by setting |
64 | Or on systems that have the `env' program, you can do it like this: |
| 75 | them in the environment. You can do that on the command line like this: |
65 | env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure |
| 76 | |
|
|
| 77 | ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix |
|
|
| 78 | |
|
|
| 79 | *Note Defining Variables::, for more details. |
|
|
| 80 | |
66 | |
| 81 | Compiling For Multiple Architectures |
67 | Compiling For Multiple Architectures |
| 82 | ==================================== |
68 | ==================================== |
| 83 | |
69 | |
| 84 | You can compile the package for more than one kind of computer at the |
70 | You can compile the package for more than one kind of computer at the |
| … | |
… | |
| 87 | supports the `VPATH' variable, such as GNU `make'. `cd' to the |
73 | supports the `VPATH' variable, such as GNU `make'. `cd' to the |
| 88 | directory where you want the object files and executables to go and run |
74 | directory where you want the object files and executables to go and run |
| 89 | the `configure' script. `configure' automatically checks for the |
75 | the `configure' script. `configure' automatically checks for the |
| 90 | source code in the directory that `configure' is in and in `..'. |
76 | source code in the directory that `configure' is in and in `..'. |
| 91 | |
77 | |
| 92 | If you have to use a `make' that does not support the `VPATH' |
78 | If you have to use a `make' that does not supports the `VPATH' |
| 93 | variable, you have to compile the package for one architecture at a |
79 | variable, you have to compile the package for one architecture at a time |
| 94 | time in the source code directory. After you have installed the |
80 | in the source code directory. After you have installed the package for |
| 95 | package for one architecture, use `make distclean' before reconfiguring |
81 | one architecture, use `make distclean' before reconfiguring for another |
| 96 | for another architecture. |
82 | architecture. |
| 97 | |
83 | |
| 98 | Installation Names |
84 | Installation Names |
| 99 | ================== |
85 | ================== |
| 100 | |
86 | |
| 101 | By default, `make install' will install the package's files in |
87 | By default, `make install' will install the package's files in |
| … | |
… | |
| 134 | `--x-libraries=DIR' to specify their locations. |
120 | `--x-libraries=DIR' to specify their locations. |
| 135 | |
121 | |
| 136 | Specifying the System Type |
122 | Specifying the System Type |
| 137 | ========================== |
123 | ========================== |
| 138 | |
124 | |
| 139 | There may be some features `configure' cannot figure out |
125 | There may be some features `configure' can not figure out |
| 140 | automatically, but needs to determine by the type of host the package |
126 | automatically, but needs to determine by the type of host the package |
| 141 | will run on. Usually `configure' can figure that out, but if it prints |
127 | will run on. Usually `configure' can figure that out, but if it prints |
| 142 | a message saying it cannot guess the host type, give it the |
128 | a message saying it can not guess the host type, give it the |
| 143 | `--build=TYPE' option. TYPE can either be a short name for the system |
129 | `--host=TYPE' option. TYPE can either be a short name for the system |
| 144 | type, such as `sun4', or a canonical name which has the form: |
130 | type, such as `sun4', or a canonical name with three fields: |
| 145 | |
|
|
| 146 | CPU-COMPANY-SYSTEM |
131 | CPU-COMPANY-SYSTEM |
| 147 | |
132 | |
| 148 | where SYSTEM can have one of these forms: |
|
|
| 149 | |
|
|
| 150 | OS KERNEL-OS |
|
|
| 151 | |
|
|
| 152 | See the file `config.sub' for the possible values of each field. If |
133 | See the file `config.sub' for the possible values of each field. If |
| 153 | `config.sub' isn't included in this package, then this package doesn't |
134 | `config.sub' isn't included in this package, then this package doesn't |
| 154 | need to know the host type. |
135 | need to know the host type. |
| 155 | |
136 | |
| 156 | If you are _building_ compiler tools for cross-compiling, you should |
137 | If you are building compiler tools for cross-compiling, you can also |
| 157 | use the `--target=TYPE' option to select the type of system they will |
138 | use the `--target=TYPE' option to select the type of system they will |
| 158 | produce code for. |
139 | produce code for and the `--build=TYPE' option to select the type of |
| 159 | |
140 | system on which you are compiling the package. |
| 160 | If you want to _use_ a cross compiler, that generates code for a |
|
|
| 161 | platform different from the build platform, you should specify the host |
|
|
| 162 | platform (i.e., that on which the generated programs will eventually be |
|
|
| 163 | run) with `--host=TYPE'. In this case, you should also specify the |
|
|
| 164 | build platform with `--build=TYPE', because, in this case, it may not |
|
|
| 165 | be possible to guess the build platform (it sometimes involves |
|
|
| 166 | compiling and running simple test programs, and this can't be done if |
|
|
| 167 | the compiler is a cross compiler). |
|
|
| 168 | |
141 | |
| 169 | Sharing Defaults |
142 | Sharing Defaults |
| 170 | ================ |
143 | ================ |
| 171 | |
144 | |
| 172 | If you want to set default values for `configure' scripts to share, |
145 | If you want to set default values for `configure' scripts to share, |
| … | |
… | |
| 175 | `configure' looks for `PREFIX/share/config.site' if it exists, then |
148 | `configure' looks for `PREFIX/share/config.site' if it exists, then |
| 176 | `PREFIX/etc/config.site' if it exists. Or, you can set the |
149 | `PREFIX/etc/config.site' if it exists. Or, you can set the |
| 177 | `CONFIG_SITE' environment variable to the location of the site script. |
150 | `CONFIG_SITE' environment variable to the location of the site script. |
| 178 | A warning: not all `configure' scripts look for a site script. |
151 | A warning: not all `configure' scripts look for a site script. |
| 179 | |
152 | |
| 180 | Defining Variables |
153 | Operation Controls |
| 181 | ================== |
154 | ================== |
| 182 | |
|
|
| 183 | Variables not defined in a site shell script can be set in the |
|
|
| 184 | environment passed to `configure'. However, some packages may run |
|
|
| 185 | configure again during the build, and the customized values of these |
|
|
| 186 | variables may be lost. In order to avoid this problem, you should set |
|
|
| 187 | them in the `configure' command line, using `VAR=value'. For example: |
|
|
| 188 | |
|
|
| 189 | ./configure CC=/usr/local2/bin/gcc |
|
|
| 190 | |
|
|
| 191 | will cause the specified gcc to be used as the C compiler (unless it is |
|
|
| 192 | overridden in the site shell script). |
|
|
| 193 | |
|
|
| 194 | `configure' Invocation |
|
|
| 195 | ====================== |
|
|
| 196 | |
155 | |
| 197 | `configure' recognizes the following options to control how it |
156 | `configure' recognizes the following options to control how it |
| 198 | operates. |
157 | operates. |
| 199 | |
158 | |
|
|
159 | `--cache-file=FILE' |
|
|
160 | Use and save the results of the tests in FILE instead of |
|
|
161 | `./config.cache'. Set FILE to `/dev/null' to disable caching, for |
|
|
162 | debugging `configure'. |
|
|
163 | |
| 200 | `--help' |
164 | `--help' |
| 201 | `-h' |
|
|
| 202 | Print a summary of the options to `configure', and exit. |
165 | Print a summary of the options to `configure', and exit. |
| 203 | |
|
|
| 204 | `--version' |
|
|
| 205 | `-V' |
|
|
| 206 | Print the version of Autoconf used to generate the `configure' |
|
|
| 207 | script, and exit. |
|
|
| 208 | |
|
|
| 209 | `--cache-file=FILE' |
|
|
| 210 | Enable the cache: use and save the results of the tests in FILE, |
|
|
| 211 | traditionally `config.cache'. FILE defaults to `/dev/null' to |
|
|
| 212 | disable caching. |
|
|
| 213 | |
|
|
| 214 | `--config-cache' |
|
|
| 215 | `-C' |
|
|
| 216 | Alias for `--cache-file=config.cache'. |
|
|
| 217 | |
166 | |
| 218 | `--quiet' |
167 | `--quiet' |
| 219 | `--silent' |
168 | `--silent' |
| 220 | `-q' |
169 | `-q' |
| 221 | Do not print messages saying which checks are being made. To |
170 | Do not print messages saying which checks are being made. To |
| … | |
… | |
| 224 | |
173 | |
| 225 | `--srcdir=DIR' |
174 | `--srcdir=DIR' |
| 226 | Look for the package's source code in directory DIR. Usually |
175 | Look for the package's source code in directory DIR. Usually |
| 227 | `configure' can determine that directory automatically. |
176 | `configure' can determine that directory automatically. |
| 228 | |
177 | |
| 229 | `configure' also accepts some other, not widely useful, options. Run |
178 | `--version' |
| 230 | `configure --help' for more details. |
179 | Print the version of Autoconf used to generate the `configure' |
|
|
180 | script, and exit. |
| 231 | |
181 | |
|
|
182 | `configure' also accepts some other, not widely useful, options. |
Parent Directory
| 
Revision Log
| 
Patch