Fixed progress indicator.

[mmh] / INSTALL

diff --git a/INSTALL b/INSTALL
index b1dca8c..3cefafc 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -135,17 +135,14 @@ Compiler options, or using a different compiler
 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 giving
 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 giving

-"configure" initial values for these in its environment.  Using a
-Bourne-compatible shell, such as sh, ksh, zsh, or bash, you can do
-that on the command line like this:
-    CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+"configure" initial values for these on its command line or in its
+environment.  For example,

 
 

-Or on systems that have the "env" program, you can do it like this:
-    env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+    ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix

 
 

-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 wish to add options that are only used at compile time instead of
+link time, you can use the CPPFLAGS variable:
+   ./configure CPPFLAGS='-Wextra -Wno-sign-compare'

 
 If you want to add to both compile and link flags at build time
 without putting them in the configuration, you can use an otherwise
 
 If you want to add to both compile and link flags at build time
 without putting them in the configuration, you can use an otherwise

@@ -157,8 +154,8 @@ have to repeat it if you re-run "make".  One example would be if you
 build the test suite as a separate step:
     make test AM_CFLAGS=--coverage
 
 build the test suite as a separate step:
     make test AM_CFLAGS=--coverage
 

-Though note that the Makefile test target depends on the default
-target, so both be can built in one step with "make test".
+Note that the Makefile test target depends on the default target, so
+both be can built in one step with "make test".

 
 ----------------------------------------
 Building nmh on additional architectures
 
 ----------------------------------------
 Building nmh on additional architectures

@@ -181,7 +178,7 @@ run the "configure" script.  "configure" automatically checks for the
 source code in the directory that "configure" is in.  For example,
 
     cd /usr/local/solaris/nmh
 source code in the directory that "configure" is in.  For example,
 
     cd /usr/local/solaris/nmh

-    /usr/local/src/nmh-1.0/configure
+    /usr/local/src/nmh-1.5/configure

     make
 
 ---------------------
     make
 
 ---------------------