VMS Installation instructions written by Richard Levitte Intro: ====== This file is divided in the following parts: Requirements - Mandatory reading. Checking the distribution - Mandatory reading. Compilation - Mandatory reading. Logical names - Mandatory reading. Test - Mandatory reading. Installation - Mandatory reading. Backward portability - Read if it's an issue. Possible bugs or quirks - A few warnings on things that may go wrong or may surprise you. TODO - Things that are to come. Requirements: ============= To build and install OpenSSL, you will need: * DEC C or some other ANSI C compiler. VAX C is *not* supported. [Note: OpenSSL has only been tested with DEC C. Compiling with a different ANSI C compiler may require some work] Checking the distribution: ========================== There have been reports of places where the distribution didn't quite get through, for example if you've copied the tree from a NFS-mounted Unix mount point. The easiest way to check if everything got through as it should is to check for one of the following files: [.CRYPTO]OPENSSLCONF.H_IN [.CRYPTO]OPENSSLCONF_H.IN They should never exist both at once, but one of them should (preferably the first variant). If you can't find any of those two, something went wrong. The best way to get a correct distribution is to download the gzipped tar file from ftp://ftp.openssl.org/source/, use GUNZIP to uncompress it and use VMSTAR to unpack the resulting tar file. GUNZIP is available in many places on the net. One of the distribution points is the WKU software archive, ftp://ftp.wku.edu/vms/fileserv/ . VMSTAR is also available in many places on the net. The recommended place to find information about it is http://www.free.lp.se/vmstar/ . Compilation: ============ I've used the very good command procedures written by Robert Byer , and just slightly modified them, making them slightly more general and easier to maintain. You can actually compile in almost any directory separately. Look for a command procedure name xxx-LIB.COM (in the library directories) or MAKExxx.COM (in the program directories) and read the comments at the top to understand how to use them. However, if you want to compile all you can get, the simplest is to use MAKEVMS.COM in the top directory. The syntax is the following: @MAKEVMS