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