exiwhat: use RM_COMMAND

[users/heiko/exim.git] / src / README

diff --git a/src/README b/src/README
index cdf3792f9ebe3cd9db6c5c0ea4caabfc98a40651..652cee6efe9f219ec887082a09bdc824dee9b58a 100644 (file)
--- a/src/README
+++ b/src/README
@@ -1,9 +1,7 @@
-$Cambridge: exim/src/README,v 1.3 2005/08/30 10:07:58 ph10 Exp $
-
 THE EXIM MAIL TRANSFER AGENT VERSION 4
 --------------------------------------
 
-Copyright (c) 1995 - 2005 University of Cambridge.
+Copyright (c) 1995 - 2012 University of Cambridge.
 See the file NOTICE for conditions of use and distribution.
 
 There is a book about Exim by Philip Hazel called "The Exim SMTP Mail Server",
@@ -49,7 +47,7 @@ Please see the documentation files for full instructions on how to build,
 install, and run Exim. For straightforward installations on operating systems
 to which Exim has already been ported, the building process is as follows:
 
-. Ensure that the top-level Exim directory (e.g. exim-4.40) is the current
+. Ensure that the top-level Exim directory (e.g. exim-4.80) is the current
   directory (containing the files and directories listed above).
 
 . Edit the file called src/EDITME and put the result in a new file called
@@ -80,6 +78,12 @@ to which Exim has already been ported, the building process is as follows:
   comments in exim_monitor/EDITME about the values set therein, but in this
   case everything can be defaulted if you wish.
 
+. If your system is not POSIX compliant by default, then you might experience
+  fewer problems if you help point the build tools to the POSIX variants. For
+  instance, on Solaris:
+
+  PATH=/usr/xpg4/bin:$PATH make SHELL=/usr/xpg4/bin/sh
+
 . Type "make". This will determine what your machine's architecture and
   operating system are, and create a build directory from those names (e.g.
   "build-SunOS5-sparc"). Symbolic links are created from the build directory
@@ -327,7 +331,7 @@ also need to add a new alias definition: "alias utf8 utf-8".
 
 2. For some strange reason make will fail at building "exim_dbmbuild" when
    called the first time. However simply calling make a second time will solve
-   the problem. Alternatively, run "make makfile" and then "make".
+   the problem. Alternatively, run "make makefile" and then "make".
 
 
 ******* IMPORTANT FOR ULTRIX USERS *******