|
|
1 | Installation Instructions |
|
|
2 | ************************* |
|
|
3 | |
| 1 | Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software |
4 | Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free |
| 2 | Foundation, Inc. |
5 | Software Foundation, Inc. |
| 3 | |
6 | |
| 4 | This file is free documentation; the Free Software Foundation gives |
7 | This file is free documentation; the Free Software Foundation gives |
| 5 | unlimited permission to copy, distribute and modify it. |
8 | unlimited permission to copy, distribute and modify it. |
| 6 | |
9 | |
| 7 | Basic Installation |
10 | Basic Installation |
| 8 | ================== |
11 | ================== |
| 9 | |
12 | |
| 10 | These are generic installation instructions. |
13 | These are generic installation instructions. |
| 11 | |
14 | |
| 12 | The `configure' shell script attempts to guess correct values for |
15 | The `configure' shell script attempts to guess correct values for |
| 13 | various system-dependent variables used during compilation. It uses |
16 | various system-dependent variables used during compilation. It uses |
| 14 | those values to create a `Makefile' in each directory of the package. |
17 | 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 |
18 | It may also create one or more `.h' files containing system-dependent |
| … | |
… | |
| 65 | with the distribution. |
68 | with the distribution. |
| 66 | |
69 | |
| 67 | Compilers and Options |
70 | Compilers and Options |
| 68 | ===================== |
71 | ===================== |
| 69 | |
72 | |
| 70 | Some systems require unusual options for compilation or linking that |
73 | Some systems require unusual options for compilation or linking that the |
| 71 | the `configure' script does not know about. Run `./configure --help' |
74 | `configure' script does not know about. Run `./configure --help' for |
| 72 | for details on some of the pertinent environment variables. |
75 | details on some of the pertinent environment variables. |
| 73 | |
76 | |
| 74 | You can give `configure' initial values for configuration parameters |
77 | You can give `configure' initial values for configuration parameters |
| 75 | by setting variables in the command line or in the environment. Here |
78 | by setting variables in the command line or in the environment. Here |
| 76 | is an example: |
79 | is an example: |
| 77 | |
80 | |
| … | |
… | |
| 80 | *Note Defining Variables::, for more details. |
83 | *Note Defining Variables::, for more details. |
| 81 | |
84 | |
| 82 | Compiling For Multiple Architectures |
85 | Compiling For Multiple Architectures |
| 83 | ==================================== |
86 | ==================================== |
| 84 | |
87 | |
| 85 | You can compile the package for more than one kind of computer at the |
88 | You can compile the package for more than one kind of computer at the |
| 86 | same time, by placing the object files for each architecture in their |
89 | same time, by placing the object files for each architecture in their |
| 87 | own directory. To do this, you must use a version of `make' that |
90 | own directory. To do this, you must use a version of `make' that |
| 88 | supports the `VPATH' variable, such as GNU `make'. `cd' to the |
91 | supports the `VPATH' variable, such as GNU `make'. `cd' to the |
| 89 | directory where you want the object files and executables to go and run |
92 | directory where you want the object files and executables to go and run |
| 90 | the `configure' script. `configure' automatically checks for the |
93 | the `configure' script. `configure' automatically checks for the |
| … | |
… | |
| 97 | for another architecture. |
100 | for another architecture. |
| 98 | |
101 | |
| 99 | Installation Names |
102 | Installation Names |
| 100 | ================== |
103 | ================== |
| 101 | |
104 | |
| 102 | By default, `make install' will install the package's files in |
105 | By default, `make install' will install the package's files in |
| 103 | `/usr/local/bin', `/usr/local/man', etc. You can specify an |
106 | `/usr/local/bin', `/usr/local/man', etc. You can specify an |
| 104 | installation prefix other than `/usr/local' by giving `configure' the |
107 | installation prefix other than `/usr/local' by giving `configure' the |
| 105 | option `--prefix=PATH'. |
108 | option `--prefix=PREFIX'. |
| 106 | |
109 | |
| 107 | You can specify separate installation prefixes for |
110 | You can specify separate installation prefixes for |
| 108 | architecture-specific files and architecture-independent files. If you |
111 | architecture-specific files and architecture-independent files. If you |
| 109 | give `configure' the option `--exec-prefix=PATH', the package will use |
112 | give `configure' the option `--exec-prefix=PREFIX', the package will |
| 110 | PATH as the prefix for installing programs and libraries. |
113 | use PREFIX as the prefix for installing programs and libraries. |
| 111 | Documentation and other data files will still use the regular prefix. |
114 | Documentation and other data files will still use the regular prefix. |
| 112 | |
115 | |
| 113 | In addition, if you use an unusual directory layout you can give |
116 | In addition, if you use an unusual directory layout you can give |
| 114 | options like `--bindir=PATH' to specify different values for particular |
117 | options like `--bindir=DIR' to specify different values for particular |
| 115 | kinds of files. Run `configure --help' for a list of the directories |
118 | kinds of files. Run `configure --help' for a list of the directories |
| 116 | you can set and what kinds of files go in them. |
119 | you can set and what kinds of files go in them. |
| 117 | |
120 | |
| 118 | If the package supports it, you can cause programs to be installed |
121 | If the package supports it, you can cause programs to be installed |
| 119 | with an extra prefix or suffix on their names by giving `configure' the |
122 | with an extra prefix or suffix on their names by giving `configure' the |
| 120 | option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. |
123 | option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. |
| 121 | |
124 | |
| 122 | Optional Features |
125 | Optional Features |
| 123 | ================= |
126 | ================= |
| 124 | |
127 | |
| 125 | Some packages pay attention to `--enable-FEATURE' options to |
128 | Some packages pay attention to `--enable-FEATURE' options to |
| 126 | `configure', where FEATURE indicates an optional part of the package. |
129 | `configure', where FEATURE indicates an optional part of the package. |
| 127 | They may also pay attention to `--with-PACKAGE' options, where PACKAGE |
130 | They may also pay attention to `--with-PACKAGE' options, where PACKAGE |
| 128 | is something like `gnu-as' or `x' (for the X Window System). The |
131 | is something like `gnu-as' or `x' (for the X Window System). The |
| 129 | `README' should mention any `--enable-' and `--with-' options that the |
132 | `README' should mention any `--enable-' and `--with-' options that the |
| 130 | package recognizes. |
133 | package recognizes. |
| … | |
… | |
| 135 | `--x-libraries=DIR' to specify their locations. |
138 | `--x-libraries=DIR' to specify their locations. |
| 136 | |
139 | |
| 137 | Specifying the System Type |
140 | Specifying the System Type |
| 138 | ========================== |
141 | ========================== |
| 139 | |
142 | |
| 140 | There may be some features `configure' cannot figure out |
143 | There may be some features `configure' cannot figure out automatically, |
| 141 | automatically, but needs to determine by the type of machine the package |
144 | but needs to determine by the type of machine the package will run on. |
| 142 | will run on. Usually, assuming the package is built to be run on the |
145 | Usually, assuming the package is built to be run on the _same_ |
| 143 | _same_ architectures, `configure' can figure that out, but if it prints |
146 | architectures, `configure' can figure that out, but if it prints a |
| 144 | a message saying it cannot guess the machine type, give it the |
147 | 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 |
148 | `--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: |
149 | type, such as `sun4', or a canonical name which has the form: |
| 147 | |
150 | |
| 148 | CPU-COMPANY-SYSTEM |
151 | CPU-COMPANY-SYSTEM |
| 149 | |
152 | |
| … | |
… | |
| 165 | eventually be run) with `--host=TYPE'. |
168 | eventually be run) with `--host=TYPE'. |
| 166 | |
169 | |
| 167 | Sharing Defaults |
170 | Sharing Defaults |
| 168 | ================ |
171 | ================ |
| 169 | |
172 | |
| 170 | If you want to set default values for `configure' scripts to share, |
173 | If you want to set default values for `configure' scripts to share, you |
| 171 | you can create a site shell script called `config.site' that gives |
174 | can create a site shell script called `config.site' that gives default |
| 172 | default values for variables like `CC', `cache_file', and `prefix'. |
175 | values for variables like `CC', `cache_file', and `prefix'. |
| 173 | `configure' looks for `PREFIX/share/config.site' if it exists, then |
176 | `configure' looks for `PREFIX/share/config.site' if it exists, then |
| 174 | `PREFIX/etc/config.site' if it exists. Or, you can set the |
177 | `PREFIX/etc/config.site' if it exists. Or, you can set the |
| 175 | `CONFIG_SITE' environment variable to the location of the site script. |
178 | `CONFIG_SITE' environment variable to the location of the site script. |
| 176 | A warning: not all `configure' scripts look for a site script. |
179 | A warning: not all `configure' scripts look for a site script. |
| 177 | |
180 | |
| 178 | Defining Variables |
181 | Defining Variables |
| 179 | ================== |
182 | ================== |
| 180 | |
183 | |
| 181 | Variables not defined in a site shell script can be set in the |
184 | Variables not defined in a site shell script can be set in the |
| 182 | environment passed to `configure'. However, some packages may run |
185 | environment passed to `configure'. However, some packages may run |
| 183 | configure again during the build, and the customized values of these |
186 | 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 |
187 | 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: |
188 | them in the `configure' command line, using `VAR=value'. For example: |
| 186 | |
189 | |
| … | |
… | |
| 190 | overridden in the site shell script). |
193 | overridden in the site shell script). |
| 191 | |
194 | |
| 192 | `configure' Invocation |
195 | `configure' Invocation |
| 193 | ====================== |
196 | ====================== |
| 194 | |
197 | |
| 195 | `configure' recognizes the following options to control how it |
198 | `configure' recognizes the following options to control how it operates. |
| 196 | operates. |
|
|
| 197 | |
199 | |
| 198 | `--help' |
200 | `--help' |
| 199 | `-h' |
201 | `-h' |
| 200 | Print a summary of the options to `configure', and exit. |
202 | Print a summary of the options to `configure', and exit. |
| 201 | |
203 | |
Parent Directory
| 
Revision Log
| 
Patch