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