summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorAkim Demaille <akim@epita.fr>2001-08-17 12:06:44 +0000
committerAkim Demaille <akim@epita.fr>2001-08-17 12:06:44 +0000
commit40556ab827e3876e73139c89a15190c0cfe9166b (patch)
tree009bb679d82b4e40398483d62ff6d4398651e6e0 /INSTALL
parent7582d2a4f43878371686b5eb3cf0bf854ecabc96 (diff)
downloadautoconf-40556ab827e3876e73139c89a15190c0cfe9166b.tar.gz
* bin/Makefile.am, lib/Autom4te/Makefile.am, lib/autoconf/Makefile.am
* lib/autotest/Makefile.am, lib/m4sugar/Makefile.am: Add TAGS support.
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL19
1 files changed, 9 insertions, 10 deletions
diff --git a/INSTALL b/INSTALL
index d1723084..27690b44 100644
--- a/INSTALL
+++ b/INSTALL
@@ -70,7 +70,7 @@ them in the environment. You can do that on the command line like this:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
- *Note Environment Variables::, for more details.
+ *Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
@@ -84,10 +84,10 @@ the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a time
-in the source code directory. After you have installed the package for
-one architecture, use `make distclean' before reconfiguring for another
-architecture.
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
Installation Names
==================
@@ -141,8 +141,7 @@ type, such as `sun4', or a canonical name which has the form:
where SYSTEM can have one of these forms:
- OS
- KERNEL-OS
+ OS KERNEL-OS
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
@@ -172,11 +171,11 @@ default values for variables like `CC', `cache_file', and `prefix'.
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
-Environment Variables
-=====================
+Defining Variables
+==================
Variables not defined in a site shell script can be set in the
-environment passed to configure. However, some packages may run
+environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example: