| 1 | Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, |
1 | Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software |
| 2 | Inc. |
2 | Foundation, Inc. |
| 3 | |
3 | |
| 4 | This file is free documentation; the Free Software Foundation gives |
4 | This file is free documentation; the Free Software Foundation gives |
| 5 | unlimited permission to copy, distribute and modify it. |
5 | unlimited permission to copy, distribute and modify it. |
| 6 | |
6 | |
| 7 | Basic Installation |
7 | Basic Installation |
| … | |
… | |
| 69 | |
69 | |
| 70 | Some systems require unusual options for compilation or linking that |
70 | Some systems require unusual options for compilation or linking that |
| 71 | the `configure' script does not know about. Run `./configure --help' |
71 | the `configure' script does not know about. Run `./configure --help' |
| 72 | for details on some of the pertinent environment variables. |
72 | for details on some of the pertinent environment variables. |
| 73 | |
73 | |
| 74 | You can give `configure' initial values for variables by setting |
74 | You can give `configure' initial values for configuration parameters |
| 75 | them in the environment. You can do that on the command line like this: |
75 | by setting variables in the command line or in the environment. Here |
|
|
76 | is an example: |
| 76 | |
77 | |
| 77 | ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix |
78 | ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix |
| 78 | |
79 | |
| 79 | *Note Defining Variables::, for more details. |
80 | *Note Defining Variables::, for more details. |
| 80 | |
81 | |
| … | |
… | |
| 135 | |
136 | |
| 136 | Specifying the System Type |
137 | Specifying the System Type |
| 137 | ========================== |
138 | ========================== |
| 138 | |
139 | |
| 139 | There may be some features `configure' cannot figure out |
140 | There may be some features `configure' cannot figure out |
| 140 | automatically, but needs to determine by the type of host the package |
141 | automatically, but needs to determine by the type of machine the package |
| 141 | will run on. Usually `configure' can figure that out, but if it prints |
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 |
| 142 | a message saying it cannot guess the host type, give it the |
144 | a message saying it cannot guess the machine type, give it the |
| 143 | `--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 |
| 144 | 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: |
| 145 | |
147 | |
| 146 | CPU-COMPANY-SYSTEM |
148 | CPU-COMPANY-SYSTEM |
| 147 | |
149 | |
| … | |
… | |
| 149 | |
151 | |
| 150 | OS KERNEL-OS |
152 | OS KERNEL-OS |
| 151 | |
153 | |
| 152 | See the file `config.sub' for the possible values of each field. If |
154 | 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 |
155 | `config.sub' isn't included in this package, then this package doesn't |
| 154 | need to know the host type. |
156 | need to know the machine type. |
| 155 | |
157 | |
| 156 | If you are _building_ compiler tools for cross-compiling, you should |
158 | If you are _building_ compiler tools for cross-compiling, you should |
| 157 | use the `--target=TYPE' option to select the type of system they will |
159 | use the `--target=TYPE' option to select the type of system they will |
| 158 | produce code for. |
160 | produce code for. |
| 159 | |
161 | |
| 160 | If you want to _use_ a cross compiler, that generates code for a |
162 | 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 |
163 | platform different from the build platform, you should specify the |
| 162 | platform (i.e., that on which the generated programs will eventually be |
164 | "host" platform (i.e., that on which the generated programs will |
| 163 | run) with `--host=TYPE'. In this case, you should also specify the |
165 | eventually be run) with `--host=TYPE'. |
| 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 | |
166 | |
| 169 | Sharing Defaults |
167 | Sharing Defaults |
| 170 | ================ |
168 | ================ |
| 171 | |
169 | |
| 172 | If you want to set default values for `configure' scripts to share, |
170 | If you want to set default values for `configure' scripts to share, |
Parent Directory
| 
Revision Log
| 
Patch