wbrawner/openssl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
openssl/NOTES.VMS

63 lines
1.9 KiB
Text
Raw Normal View History

Change the INSTALL documentation for unified builds Because of the unified scheme, building on different platforms is very similar. We currently have Unix and OpenVMS on the unified scheme, which means that a separate INSTALL.VMS is no longer needed. Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-07 23:04:27 +00:00
NOTES FOR THE OPENVMS PLATFORM
==============================
Requirement details
-------------------
VMS: compensate for command line length limits with a logical name Sometimes, you might end up with a rather long compile line due to excessively long /INCLUDE directories. Compensate for it by making a temporary logical name with them and using said logical name as /INCLUDE argument. A note was added to NOTES.VMS regarding these limitations. Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-03-23 18:27:08 +00:00
In addition to the requirements and instructions listed in INSTALL,
this are required as well:
Change the INSTALL documentation for unified builds Because of the unified scheme, building on different platforms is very similar. We currently have Unix and OpenVMS on the unified scheme, which means that a separate INSTALL.VMS is no longer needed. Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-07 23:04:27 +00:00
* At least ODS-5 disk organization for source and build.
Installation can be done on any existing disk organization.
About ANSI C compiler
---------------------
VMS: add a note about DECC$* logical names These logical names are used to make the C RTL change certain behaviors, sometimes to make it act more like Unix. While they can make life easier in some cases, they can be disruptive as well. When building and testing OpenSSL, the latter is the case, so we ask people to avoid using them. Reviewed-by: Tim Hudson <tjh@openssl.org>
2016-03-25 07:27:35 +00:00
An ANSI C compiled is needed among other things. This means that
VAX C is not and will not be supported.
Change the INSTALL documentation for unified builds Because of the unified scheme, building on different platforms is very similar. We currently have Unix and OpenVMS on the unified scheme, which means that a separate INSTALL.VMS is no longer needed. Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-07 23:04:27 +00:00
VMS: add a note about DECC$* logical names These logical names are used to make the C RTL change certain behaviors, sometimes to make it act more like Unix. While they can make life easier in some cases, they can be disruptive as well. When building and testing OpenSSL, the latter is the case, so we ask people to avoid using them. Reviewed-by: Tim Hudson <tjh@openssl.org>
2016-03-25 07:27:35 +00:00
We have only tested with DEC C (a.k.a HP VMS C / VSI C), compiling
with a different ANSI C compiler may require some work.
Please avoid using C RTL feature logical names DECC$* when building
and testing OpenSSL. Most of all, they can be disruptive when
running the tests, as they affect the Perl interpreter.
Change the INSTALL documentation for unified builds Because of the unified scheme, building on different platforms is very similar. We currently have Unix and OpenVMS on the unified scheme, which means that a separate INSTALL.VMS is no longer needed. Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-07 23:04:27 +00:00
VMS: compensate for command line length limits with a logical name Sometimes, you might end up with a rather long compile line due to excessively long /INCLUDE directories. Compensate for it by making a temporary logical name with them and using said logical name as /INCLUDE argument. A note was added to NOTES.VMS regarding these limitations. Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-03-23 18:27:08 +00:00
About MMS and DCL
-----------------
MMS has certain limitations when it comes to line length, and DCL has
certain limitations when it comes to total command length. We do
what we can to mitigate, but there is the possibility that it's not
enough. Should you run into issues, a very simple solution is to set
yourself up a few logical names for the directory trees you're going
to use.
Change the INSTALL documentation for unified builds Because of the unified scheme, building on different platforms is very similar. We currently have Unix and OpenVMS on the unified scheme, which means that a separate INSTALL.VMS is no longer needed. Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-07 23:04:27 +00:00
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
The best way to get a correct distribution is to download the gzipped
tar file from ftp://ftp.openssl.org/source/, use GZIP -d to uncompress
it and VMSTAR to unpack the resulting tar file.
Gzip and VMSTAR are available here:
http://antinode.info/dec/index.html#Software
Should you need it, you can find UnZip for VMS here:
http://www.info-zip.org/UnZip.html
Reference in a new issue Copy permalink