Show assignment of configure variables using VAR=VALUE instead of in the env.

Pulled in from nmh. Thanks to David Levine.

diff --git a/INSTALL b/INSTALL
index b8f0409b69c4a5f7311e022ccd69c88317ea1ef5..78e1390b1109900f2db72d575672034263d446f2 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -71,18 +71,16 @@ By default, configure will use the "gcc" compiler if found.  You can use a
 different compiler, or add unusual options for compiling or linking that
 the "configure" script does not know about, by either editing the user
 configuration section of the top level Makefile (after running configure)
-or giving "configure" initial values for these variables by setting them
-in the environment.  Using a Bourne-compatible shell (such as sh,ksh,zsh),
+or giving "configure" initial values for these in its command line or in
+its environment. For example:
 
-you can do that on the command line like this:
-    CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+    ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
 
 Or on systems that have the "env" program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
 
-If you want to add to, not replace, compile flags, you can use
-OURDEFS with env or like this:
-    OURDEFS='-Wextra -Wno-sign-compare' ./configure
+If you want to add to, not replace, compile flags, you can use OURDEFS:
+    ./configure OURDEFS='-Wextra -Wno-sign-compare'
 
 ----------------------------------------
 Building mmh on additional architectures