1.1 --- a/gmyth-stream/client/INSTALL Wed Apr 11 18:39:39 2007 +0100
1.2 +++ b/gmyth-stream/client/INSTALL Thu Apr 19 16:02:10 2007 +0100
1.3 @@ -102,16 +102,16 @@
1.4 Installation Names
1.5 ==================
1.6
1.7 -By default, `make install' installs the package's commands under
1.8 -`/usr/local/bin', include files under `/usr/local/include', etc. You
1.9 -can specify an installation prefix other than `/usr/local' by giving
1.10 -`configure' the option `--prefix=PREFIX'.
1.11 +By default, `make install' will install the package's files in
1.12 +`/usr/local/bin', `/usr/local/man', etc. You can specify an
1.13 +installation prefix other than `/usr/local' by giving `configure' the
1.14 +option `--prefix=PREFIX'.
1.15
1.16 You can specify separate installation prefixes for
1.17 architecture-specific files and architecture-independent files. If you
1.18 -pass the option `--exec-prefix=PREFIX' to `configure', the package uses
1.19 -PREFIX as the prefix for installing programs and libraries.
1.20 -Documentation and other data files still use the regular prefix.
1.21 +give `configure' the option `--exec-prefix=PREFIX', the package will
1.22 +use PREFIX as the prefix for installing programs and libraries.
1.23 +Documentation and other data files will still use the regular prefix.
1.24
1.25 In addition, if you use an unusual directory layout you can give
1.26 options like `--bindir=DIR' to specify different values for particular
1.27 @@ -159,7 +159,7 @@
1.28 need to know the machine type.
1.29
1.30 If you are _building_ compiler tools for cross-compiling, you should
1.31 -use the option `--target=TYPE' to select the type of system they will
1.32 +use the `--target=TYPE' option to select the type of system they will
1.33 produce code for.
1.34
1.35 If you want to _use_ a cross compiler, that generates code for a