Documented support of OURDEFS to pass compile flags to configure.

[mmh] / INSTALL

diff --git a/INSTALL b/INSTALL
index d93ff2c..e6a7e17 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -31,8 +31,8 @@ need an ANSI C compiler such as gcc.
    This will check the configuration of your OS, as well as the various
    Makefiles.
 
-   The configure script accepts various options.  The options of 
-   most interest are listed in a section below.  To see the list 
+   The configure script accepts various options.  The options of
+   most interest are listed in a section below.  To see the list
    of all available options, you can run:
 
        ./configure --help
@@ -50,24 +50,11 @@ need an ANSI C compiler such as gcc.
    that directory to see if you need to merge changes.
 
 4) Edit the file `mhn.defaults' (installed in the mmh `etc' directory).
+
    This file contains the default profile entries for the mmh commands
-   mhlist/mhstore/mhshow and is created by the script `mhn.defaults.sh'.
-   This script will search a generic path (essentially your $PATH) for
-   programs to handle various content types (for example, xv to display
-   images).  You can re-run this script and give it a more tailored
-   path.  You may want to re-run this script later if you install new
-   programs to display content.  An example of this is:
-
-       % cd support/general
-       % ./mhn.defaults.sh /usr/local/bin:/usr/ucb > mhn.defaults
-
-   and then move `mhn.defaults' into the mmh `etc' directory.
-
-   The `mhn.defaults.sh' script only searches for a simple set of programs.
-   If you have specialized programs to handle various types, you will need
-   to edit the `mhn.defaults' file manually.  The syntax of this file is
-   described in section 9.4 of the book "MH & xmh: Email for Users and
-   Programmers", 3rd edition, by Jerry Peek, on the Internet at
+   mhlist/mhstore/mhshow.  The syntax of this file is described in section
+   9.4 of the book "MH & xmh: Email for Users and Programmers", 3rd edition,
+   by Jerry Peek, on the Internet at
    <http://www.ics.uci.edu/~mh/book/mh/confmhn.htm>.
 
 5) Add the bindir to your PATH variable.
@@ -86,13 +73,17 @@ 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),
- 
+
 you can do that on the command line like this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
- 
+
 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
+
 ----------------------------------------
 Building mmh on additional architectures
 ----------------------------------------
@@ -101,7 +92,7 @@ This should restore the mmh source distribution back to its original
 state.  You can then configure mmh as above on other architectures in
 which you wish to build mmh.  Or alternatively, you can use a different
 build directory for each architecture.
- 
+
 ---------------------------------
 Using a different build directory
 ---------------------------------
@@ -112,7 +103,7 @@ architecture at the same time.  To do this, you must use a version of
 the directory where you want the object files and executables to go and
 run the "configure" script.  "configure" automatically checks for the
 source code in the directory that "configure" is in.  For example,
- 
+
     cd /usr/local/solaris/mmh
     /usr/local/src/mmh-1.0/configure
     make