diff options
author | Jim Meyering <jim@meyering.net> | 2003-08-13 06:14:50 +0000 |
---|---|---|
committer | Jim Meyering <jim@meyering.net> | 2003-08-13 06:14:50 +0000 |
commit | 4f9e9c540a53e26b4df6efe5728f142a59fff394 (patch) | |
tree | 5cf7f7ee00ccdac3263e92d2134ae59b4f1b6c00 | |
parent | 564fa6ab8846fa1803aee5e0aab37068fd70ccef (diff) | |
download | coreutils-4f9e9c540a53e26b4df6efe5728f142a59fff394.tar.xz |
new version from autoconf
-rw-r--r-- | INSTALL | 28 |
1 files changed, 13 insertions, 15 deletions
@@ -1,5 +1,5 @@ -Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, -Inc. +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software +Foundation, Inc. This file is free documentation; the Free Software Foundation gives unlimited permission to copy, distribute and modify it. @@ -71,8 +71,9 @@ Compilers and Options the `configure' script does not know about. Run `./configure --help' for details on some of the pertinent environment variables. - You can give `configure' initial values for variables by setting -them in the environment. You can do that on the command line like this: + You can give `configure' initial values for configuration parameters +by setting variables in the command line or in the environment. Here +is an example: ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix @@ -137,9 +138,10 @@ Specifying the System Type ========================== There may be some features `configure' cannot figure out -automatically, but needs to determine by the type of host the package -will run on. Usually `configure' can figure that out, but if it prints -a message saying it cannot guess the host type, give it the +automatically, but needs to determine by the type of machine the package +will run on. Usually, assuming the package is built to be run on the +_same_ architectures, `configure' can figure that out, but if it prints +a message saying it cannot guess the machine type, give it the `--build=TYPE' option. TYPE can either be a short name for the system type, such as `sun4', or a canonical name which has the form: @@ -151,20 +153,16 @@ 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. +need to know the machine 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). +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'. Sharing Defaults ================ |