|
|
||||||||||||||||||||||||
![]() |
![]() |
|||||||||||||||||||||||
|
|
||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||
|
|
||||||||||||||||||||||||
|
|
|
|
||||||||||||||||||||||
|
|
||||||||||||||||||||||||
|
|
|
|
||||||||||||||||||||||
|
13.6 Specifying the System Type
There may be some features
where system can have one of these forms:
See the file `config.sub' for the possible values of each field. If `config.sub' isn't included in this package, then this package doesn't need to know the host type. If you are building compiler tools for cross-compiling, you should use the `--target=type' option to select the type of system they will produce code for. If you want to use a cross compiler, that generates code for a platform different from the build platform, you should specify the host platform (i.e., that on which the generated programs will eventually be run) with `--host=type'. In this case, you should also specify the build platform with `--build=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).
|
|
||||||||||||||||||||||
|
|
||||||||||||||||||||||||
|
Marketplace: include("links-a.html"); ?> | ||||||||||||||||||||||||
| " $quotes = file("2quotes.txt"); $quote = rand(1, sizeof($quotes)); echo $quotes[$quote]; ?> " | ||||||||||||||||||||||||