X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=INSTALL;h=8f3b7d3fffe8b4033133893783e5b02d9db2e40f;hp=32e6d42e602a2f5076da05548dc8ddaed486221d;hb=32d4f9daaa70519be3072479232ff7be0500d009;hpb=ec31c208d8618994f39ec21aa14d6cf4b7fdae66 diff --git a/INSTALL b/INSTALL index 32e6d42..8f3b7d3 100644 --- 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 @@ -52,10 +52,10 @@ need an ANSI C compiler such as gcc. 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. The syntax of this file is described in section + mhlist/mhstore/show. 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 - . + . 5) Add the bindir to your PATH variable. @@ -71,15 +71,17 @@ 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), - -you can do that on the command line like this: - CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure - +or giving "configure" initial values for these in its command line or in +its environment. For example: + + ./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: + ./configure OURDEFS='-Wextra -Wno-sign-compare' + ---------------------------------------- Building mmh on additional architectures ---------------------------------------- @@ -88,7 +90,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 --------------------------------- @@ -99,7 +101,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 @@ -129,16 +131,12 @@ Options for configure --enable-debug Enable debugging support. ---enable-mhe (DEFAULT) - Add support for the Emacs front-end `mhe'. - --with-locking=LOCKTYPE (DEFAULT is dot) - Specify the locking mechanism when attempting to "inc" or - "msgchk" a local mail spool. Valid options are "dot", - "fcntl", "flock", and "lockf". Of the four, dot-locking - requires no special kernel or filesystem support, and simply - creates a file called "FILE.lock" to indicate that "FILE" is - locked. + Specify the locking mechanism when attempting to "inc" + a local mail spool. Valid options are "dot", "fcntl", "flock", + and "lockf". Of the four, dot-locking requires no special kernel + or filesystem support, and simply creates a file called + "FILE.lock" to indicate that "FILE" is locked. In order to be effective, you should contact the site administrator to find out what locking mechanisms other