3 |
|
|
4 |
@ifclear autoconf |
@ifclear autoconf |
5 |
|
|
6 |
Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, |
Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software |
7 |
Inc. |
Foundation, Inc. |
8 |
|
|
9 |
This file is free documentation; the Free Software Foundation gives |
This file is free documentation; the Free Software Foundation gives |
10 |
unlimited permission to copy, distribute and modify it. |
unlimited permission to copy, distribute and modify it. |
160 |
@section Specifying the System Type |
@section Specifying the System Type |
161 |
|
|
162 |
There may be some features @command{configure} cannot figure out |
There may be some features @command{configure} cannot figure out |
163 |
automatically, but needs to determine by the type of host the package |
automatically, but needs to determine by the type of machine the package |
164 |
will run on. Usually @command{configure} can figure that out, but if it |
will run on. Usually, assuming the package is built to be run on the |
165 |
prints a message saying it cannot guess the host type, give it the |
@emph{same} architectures, @command{configure} can figure that out, but |
166 |
@option{--build=@var{type}} option. @var{type} can either be a short |
if it prints a message saying it cannot guess the machine type, give it |
167 |
name for the system type, such as @samp{sun4}, or a canonical name which |
the @option{--build=@var{type}} option. @var{type} can either be a |
168 |
has the form: |
short name for the system type, such as @samp{sun4}, or a canonical name |
169 |
|
which has the form: |
170 |
|
|
171 |
@example |
@example |
172 |
@var{cpu}-@var{company}-@var{system} |
@var{cpu}-@var{company}-@var{system} |
181 |
|
|
182 |
See the file @file{config.sub} for the possible values of each field. |
See the file @file{config.sub} for the possible values of each field. |
183 |
If @file{config.sub} isn't included in this package, then this package |
If @file{config.sub} isn't included in this package, then this package |
184 |
doesn't need to know the host type. |
doesn't need to know the machine type. |
185 |
|
|
186 |
If you are @emph{building} compiler tools for cross-compiling, you |
If you are @emph{building} compiler tools for cross-compiling, you |
187 |
should use the @option{--target=@var{type}} option to select the type of |
should use the @option{--target=@var{type}} option to select the type of |
188 |
system they will produce code for. |
system they will produce code for. |
189 |
|
|
190 |
If you want to @emph{use} a cross compiler, that generates code for a |
If you want to @emph{use} a cross compiler, that generates code for a |
191 |
platform different from the build platform, you should specify the host |
platform different from the build platform, you should specify the |
192 |
platform (i.e., that on which the generated programs will eventually be |
@dfn{host} platform (i.e., that on which the generated programs will |
193 |
run) with @option{--host=@var{type}}. In this case, you should also |
eventually be run) with @option{--host=@var{type}}. |
|
specify the build platform with @option{--build=@var{type}}, because, in |
|
|
this case, it may not be possible to guess the build platform (it |
|
|
sometimes involves compiling and running simple test programs, and this |
|
|
can't be done if the compiler is a cross compiler). |
|
194 |
|
|
195 |
@node Sharing Defaults |
@node Sharing Defaults |
196 |
@section Sharing Defaults |
@section Sharing Defaults |