 README file for MX Source Kit 
 February 2008   E The MX sources are divided up into subdirectories.  Each subdirectory ? contains a DESCRIP.MMS file for building the components in that 
 subdirectory.    To build MX, you will need:   D    * MMK (the makefiles are MMK-specific and will not work with MMS)    * the BLISS-32 compiler    * the C compiler 9    * DEC Document if you want to build the document files   B To build a full distribution kit, you need to be able to build allE the binaries for Alpha and IA-64 systems.  I have removed the kitting E for VAX systems, although the source code still contains VAX support.   I The makefiles are set up for "build-out" -- that is, most files generated F by the build are placed a directory tree under separate logical deviceE names (for which I use rooted logical names).  The top of the tree is C assumed to be [MX] by default, but you can define the symbol MX_TOP ? to have it be a different name.   The logical device names are:    MG_SRC:         source tree  MG_BIN_AXP:     Alpha binaries MG_BIN_I64:     IA64 binaries 1 MG_BIN:         binaries for current architecture   ; MG_ETC_AXP:     Alpha-specific generated files (non-binary) : MG_ETC_I64:     IA64-specific generated files (non-binary)8 MG_ETC:         generated files for current architecture  2 MG_KIT:         Installation kit working directory  / MG_CMS:         CMS library tree (not required)   A Here is a brief description of the contents of the subdirectories  in the source tree:   * [.ALIAS]       source for MXALIAS utility.E [.COMMON]      common include files and libraries used throughout MX. : [.DOC]         DEC DOCUMENT sources for the documentation.> [.EXAMPLES]    various example files included with the MX kit.7 [.FLQ]         file queuing library used throughout MX. & [.KIT]         installation kit files.$ [.LOCAL]       local delivery agent.; [.MAILSHR]     VMS MAIL "foreign" mail transport interface. " [.MCP]         MX Control Program.. [.MLF]         mailing list/file server agent.! [.MLFAKE]      source for MLFAKE. ! [.NETLIB]      source for NETLIB. ) [.ROUTER]      source for message router. ; [.SITE]        source for "SITE" entry and delivery agents. C [.SMTP]        source for SMTP server and agent (TCP/IP and DECnet)   B If you have used older versions of MX, you may note that the Jnet,B SMTP-over-X.25, ListServ, and UUCP interfaces are missing.  I haveC excluded thes from the kit because I don't know whether or not they E work any more. I have also removed all code relating to license keys, 1 as MX is now distributed as open source software.    To build MX binaries:   :    1. Set up the logical names mentioned above.  You don't9       need the MG_CMS: logical name unless you've put the $       MX sources into CMS libraries.7    2. Set default to the top-level source directory and        use MMK to build.   < To build the installation kit, you need to make the binaries= for both Alpha and IA64 architectures first.  Once everything : else is built, use "MMK KIT" at the top-level directory to$ build the complete installation kit.   Versioning:   A For the open-source distribution, I have bumped the major version ? of MX from 5 to 6.  Users of the commercial V5.x version of MX, > or the older V4.x freeware version, cannot upgrade directly toA the open-source version.  I did this because there was no way for / me to verify that upgrades would work properly.      ------ COPYRIGHT NOTICE  $ Copyright (c) 2008, Matthew Madison.   All rights reserved.  B Redistribution and use in source and binary forms, with or withoutB modification, are permitted provided that the following conditions are met:  :     * Redistributions of source code must retain the aboveA       copyright notice, this list of conditions and the following        disclaimer. =     * Redistributions in binary form must reproduce the above A       copyright notice, this list of conditions and the following E       disclaimer in the documentation and/or other materials provided        with the distribution.B     * Neither the name of the copyright owner nor the names of anyC       other contributors may be used to endorse or promote products ?       derived from this software without specific prior written        permission.   C THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS A "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT E LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR D A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTE OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, @ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTE LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, E DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY C THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT E (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE D OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.  