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