|
|
|
@ -102,16 +102,16 @@ for another architecture. |
|
|
|
|
Installation Names |
|
|
|
|
================== |
|
|
|
|
|
|
|
|
|
By default, `make install' will install the package's files in |
|
|
|
|
`/usr/local/bin', `/usr/local/man', etc. You can specify an |
|
|
|
|
installation prefix other than `/usr/local' by giving `configure' the |
|
|
|
|
option `--prefix=PREFIX'. |
|
|
|
|
By default, `make install' installs the package's commands under |
|
|
|
|
`/usr/local/bin', include files under `/usr/local/include', etc. You |
|
|
|
|
can specify an installation prefix other than `/usr/local' by giving |
|
|
|
|
`configure' the option `--prefix=PREFIX'. |
|
|
|
|
|
|
|
|
|
You can specify separate installation prefixes for |
|
|
|
|
architecture-specific files and architecture-independent files. If you |
|
|
|
|
give `configure' the option `--exec-prefix=PREFIX', the package will |
|
|
|
|
use PREFIX as the prefix for installing programs and libraries. |
|
|
|
|
Documentation and other data files will still use the regular prefix. |
|
|
|
|
pass the option `--exec-prefix=PREFIX' to `configure', the package uses |
|
|
|
|
PREFIX as the prefix for installing programs and libraries. |
|
|
|
|
Documentation and other data files still use the regular prefix. |
|
|
|
|
|
|
|
|
|
In addition, if you use an unusual directory layout you can give |
|
|
|
|
options like `--bindir=DIR' to specify different values for particular |
|
|
|
@ -159,7 +159,7 @@ where SYSTEM can have one of these forms: |
|
|
|
|
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 |
|
|
|
|
use the option `--target=TYPE' to select the type of system they will |
|
|
|
|
produce code for. |
|
|
|
|
|
|
|
|
|
If you want to _use_ a cross compiler, that generates code for a |
|
|
|
|