Mem-management: use proper define for constant

[exim.git] / src / README

diff --git a/src/README b/src/README
index d14e87cd17b8978e8b733baff5eb31d0bcf32be3..768eabbe820ee451fe0c5b9598446c9aae6ed9c8 100644 (file)
--- a/src/README
+++ b/src/README
@@ -1,9 +1,8 @@
-$Cambridge: exim/src/README,v 1.2 2005/01/04 10:00:42 ph10 Exp $
-

 THE EXIM MAIL TRANSFER AGENT VERSION 4
 --------------------------------------
 
 THE EXIM MAIL TRANSFER AGENT VERSION 4
 --------------------------------------
 

-Copyright (c) 1995 - 2005 University of Cambridge.
+Copyright (c) 1995 - 2018 University of Cambridge.
+SPDX-License-Identifier: GPL-2.0-or-later

 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",
 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",


@@ -11,12 +10,12 @@ published by UIT Cambridge in May 2003. This is the official guide for Exim 4.
 The current edition covers release 4.10 and a few later extensions.
 
 The O'Reilly book about Exim ("Exim The Mail Transfer Agent" by Philip Hazel)
 The current edition covers release 4.10 and a few later extensions.
 
 The O'Reilly book about Exim ("Exim The Mail Transfer Agent" by Philip Hazel)

-covers Exim 3, which is now deprecated. Exim 4 has a large number of changes
+covers Exim 3, which is now obsolete. Exim 4 has a large number of changes

 from Exim 3, though the basic structure and philosophy remains the same. The
 older book may be helpful for the background, but a lot of the detail has
 changed, so it is likely to be confusing to newcomers.
 
 from Exim 3, though the basic structure and philosophy remains the same. The
 older book may be helpful for the background, but a lot of the detail has
 changed, so it is likely to be confusing to newcomers.
 

-There is a web site at http://www.exim.org; this contains details of the
+There is a website at https://www.exim.org; this contains details of the

 mailing list exim-users@exim.org.
 
 A copy of the Exim FAQ should be available from the same source that you used
 mailing list exim-users@exim.org.
 
 A copy of the Exim FAQ should be available from the same source that you used


@@ -49,7 +48,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:
 
 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
   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 +79,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.
 
   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
 . 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


@@ -146,6 +151,7 @@ system and architecture types respectively, the files used are:
   Local/Makefile-<ostype>
   Local/Makefile-<archtype>
   Local/Makefile-<ostype>-<archtype>
   Local/Makefile-<ostype>
   Local/Makefile-<archtype>
   Local/Makefile-<ostype>-<archtype>

+  Local/Makefile-<buildname>

   OS/Makefile-Base
 
 Of the Local/* files, only Local/Makefile is required to exist; the rest are
   OS/Makefile-Base
 
 Of the Local/* files, only Local/Makefile is required to exist; the rest are


@@ -327,7 +333,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
 
 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 *******
 
 
 ******* IMPORTANT FOR ULTRIX USERS *******


@@ -342,4 +348,4 @@ GNU/Hurd doesn't (at the time of writing, June 1999) have the ioctls for
 finding out the IP addresses of the local interfaces. You therefore have to set
 local_interfaces yourself. Otherwise it will treat only 127.0.0.1 as local.
 
 finding out the IP addresses of the local interfaces. You therefore have to set
 local_interfaces yourself. Otherwise it will treat only 127.0.0.1 as local.
 

-Philip Hazel <ph10@cus.cam.ac.uk>
+Philip Hazel