Blame NOTES.VMS

Packit c4476c
Packit c4476c
 NOTES FOR THE OPENVMS PLATFORM
Packit c4476c
 ==============================
Packit c4476c
Packit c4476c
 Requirement details
Packit c4476c
 -------------------
Packit c4476c
Packit c4476c
 In addition to the requirements and instructions listed in INSTALL,
Packit c4476c
 this are required as well:
Packit c4476c
Packit c4476c
  * At least ODS-5 disk organization for source and build.
Packit c4476c
    Installation can be done on any existing disk organization.
Packit c4476c
Packit c4476c
Packit c4476c
 About ANSI C compiler
Packit c4476c
 ---------------------
Packit c4476c
Packit c4476c
 An ANSI C compiled is needed among other things.  This means that
Packit c4476c
 VAX C is not and will not be supported.
Packit c4476c
Packit c4476c
 We have only tested with DEC C (a.k.a HP VMS C / VSI C) and require
Packit c4476c
 version 7.1 or later.  Compiling with a different ANSI C compiler may
Packit c4476c
 require some work.
Packit c4476c
Packit c4476c
 Please avoid using C RTL feature logical names DECC$* when building
Packit c4476c
 and testing OpenSSL.  Most of all, they can be disruptive when
Packit c4476c
 running the tests, as they affect the Perl interpreter.
Packit c4476c
Packit c4476c
Packit c4476c
 About ODS-5 directory names and Perl
Packit c4476c
 ------------------------------------
Packit c4476c
Packit c4476c
 It seems that the perl function canonpath() in the File::Spec module
Packit c4476c
 doesn't treat file specifications where the last directory name
Packit c4476c
 contains periods very well.  Unfortunately, some versions of VMS tar
Packit c4476c
 will keep the periods in the OpenSSL source directory instead of
Packit c4476c
 converting them to underscore, thereby leaving your source in
Packit c4476c
 something like [.openssl-1^.1^.0].  This will lead to issues when
Packit c4476c
 configuring and building OpenSSL.
Packit c4476c
Packit c4476c
 We have no replacement for Perl's canonpath(), so the best workaround
Packit c4476c
 for now is to rename the OpenSSL source directory, as follows (please
Packit c4476c
 adjust for the actual source directory name you have):
Packit c4476c
Packit c4476c
    $ rename openssl-1^.1^.0.DIR openssl-1_1_0.DIR
Packit c4476c
Packit c4476c
Packit c4476c
 About MMS and DCL
Packit c4476c
 -----------------
Packit c4476c
Packit c4476c
 MMS has certain limitations when it comes to line length, and DCL has
Packit c4476c
 certain limitations when it comes to total command length.  We do
Packit c4476c
 what we can to mitigate, but there is the possibility that it's not
Packit c4476c
 enough.  Should you run into issues, a very simple solution is to set
Packit c4476c
 yourself up a few logical names for the directory trees you're going
Packit c4476c
 to use.
Packit c4476c
Packit c4476c
Packit c4476c
 About debugging
Packit c4476c
 ---------------
Packit c4476c
Packit c4476c
 If you build for debugging, the default on VMS is that image
Packit c4476c
 activation starts the debugger automatically, giving you a debug
Packit c4476c
 prompt.  Unfortunately, this disrupts all other uses, such as running
Packit c4476c
 test programs in the test framework.
Packit c4476c
Packit c4476c
 Generally speaking, if you build for debugging, only use the programs
Packit c4476c
 directly for debugging.  Do not try to use them from a script, such
Packit c4476c
 as running the test suite.
Packit c4476c
Packit c4476c
 *The following is not available on Alpha*
Packit c4476c
Packit c4476c
 As a compromise, we're turning off the flag that makes the debugger
Packit c4476c
 start automatically.  If there is a program that you need to debug,
Packit c4476c
 you need to turn that flag back on first, for example:
Packit c4476c
Packit c4476c
    $ set image /flag=call_debug [.test]evp_test.exe
Packit c4476c
Packit c4476c
 Then just run it and you will find yourself in a debugging session.
Packit c4476c
 When done, we recommend that you turn that flag back off:
Packit c4476c
Packit c4476c
    $ set image /flag=nocall_debug [.test]evp_test.exe
Packit c4476c
Packit c4476c
Packit c4476c
 Checking the distribution
Packit c4476c
 -------------------------
Packit c4476c
Packit c4476c
 There have been reports of places where the distribution didn't quite
Packit c4476c
 get through, for example if you've copied the tree from a NFS-mounted
Packit c4476c
 Unix mount point.
Packit c4476c
Packit c4476c
 The easiest way to check if everything got through as it should is to
Packit c4476c
 check for one of the following files:
Packit c4476c
Packit c4476c
   [.crypto]opensslconf^.h.in
Packit c4476c
Packit c4476c
 The best way to get a correct distribution is to download the gzipped
Packit c4476c
 tar file from ftp://ftp.openssl.org/source/, use GZIP -d to uncompress
Packit c4476c
 it and VMSTAR to unpack the resulting tar file.
Packit c4476c
Packit c4476c
 Gzip and VMSTAR are available here:
Packit c4476c
Packit c4476c
   http://antinode.info/dec/index.html#Software
Packit c4476c
Packit c4476c
 Should you need it, you can find UnZip for VMS here:
Packit c4476c
Packit c4476c
   http://www.info-zip.org/UnZip.html