summaryrefslogtreecommitdiff
path: root/app/xdriinfo/INSTALL
diff options
context:
space:
mode:
authorMatthieu Herrb <matthieu@cvs.openbsd.org>2006-11-27 13:10:20 +0000
committerMatthieu Herrb <matthieu@cvs.openbsd.org>2006-11-27 13:10:20 +0000
commit19714142badb3cad63f6dcdd759496ef0ede38a6 (patch)
treed66ae97e2d3f1abe8b6128a5611ebfc177444c39 /app/xdriinfo/INSTALL
parent60b4ed1cedbbb3082308d32a222324fb6e774cbc (diff)
regenerate with OpenBSD autotools
Diffstat (limited to 'app/xdriinfo/INSTALL')
-rw-r--r--app/xdriinfo/INSTALL16
1 files changed, 8 insertions, 8 deletions
diff --git a/app/xdriinfo/INSTALL b/app/xdriinfo/INSTALL
index 56b077d6a..23e5f25d0 100644
--- a/app/xdriinfo/INSTALL
+++ b/app/xdriinfo/INSTALL
@@ -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