generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

unified build scheme: rewrite INSTALL.VMS

Browse Source 
There is more to be added, but this will at least tell people how to try.

Reviewed-by: Rich Salz <rsalz@openssl.org>
This commit is contained in:
Richard Levitte 2016-01-30 07:15:59 +01:00
parent 0f53f939a1
commit f578075a93
2 changed files with 62 additions and 280 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

324
INSTALL.VMS
View File

@ -1,302 +1,66 @@
VMS Installation instructions
written by Richard Levitte
<richard@levitte.org>
INSTALLATION ON THE VMS PLATFORM
--------------------------------
Intro: Intro
====== -----
This file is divided in the following parts: This file is divided in the following parts:
Requirements - Mandatory reading. Requirements - Mandatory reading.
Checking the distribution - Mandatory reading. Cheking the distribution - Mandatory reading.
Compilation - Mandatory reading. Quick start
Logical names - Mandatory reading. Test <TO BE ADDED>
Test - Mandatory reading. Installation <TO BE ADDED>
Installation - Mandatory reading. Backward portability <TO BE ADDED>
Backward portability - Read if it's an issue. Possible bugs and quirks <TO BE ADDED>
Possible bugs or quirks - A few warnings on things that
may go wrong or may surprise you.
TODO - Things that are to come.
Requirements: Requirements
============= ------------
To build and install OpenSSL, you will need: To build and install OpenSSL, you will need:
* Perl 5 with core modules. If you don't want to build it yourself, * Perl 5 with core modules (please read README.PERL)
we suggest you look here: http://sourceforge.net/projects/vmsperlkit/files/ * The perl module Text::Template (please read README.PERL)
* DEC C or some other ANSI C compiler. VAX C is *not* supported. * DEC C or some other ANSI C compiler. VAX C is *not* supported.
[Note: OpenSSL has only been tested with DEC C. Compiling with [Note: OpenSSL has only been tested with DEC C. Compiling with
a different ANSI C compiler may require some work] a different ANSI C compiler may require some work]
Checking the distribution: Checking the distribution
========================== -------------------------
There have been reports of places where the distribution didn't quite get There have been reports of places where the distribution didn't quite
through, for example if you've copied the tree from a NFS-mounted Unix get through, for example if you've copied the tree from a NFS-mounted
mount point. Unix mount point.
The easiest way to check if everything got through as it should is to check The easiest way to check if everything got through as it should is to
for one of the following files: check for one of the following files:
[.CRYPTO]OPENSSLCONF.H_IN [.crypto]opensslconf^.h.in
[.CRYPTO]OPENSSLCONF_H.IN
They should never exist both at once, but one of them should (preferably The best way to get a correct distribution is to download the gzipped
the first variant). If you can't find any of those two, something went tar file from ftp://ftp.openssl.org/source/, use GUNZIP to uncompress
wrong. it and use VMSTAR to unpack the resulting tar file.
The best way to get a correct distribution is to download the gzipped tar GUNZIP is available {FIXME: where is it available?}
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 VMSTAR is available {FIXME: where is it available?}
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/ .
Quick start
-----------
Compilation: If you want to just get on with it, do this:
============
I've used the very good command procedures written by Robert Byer $ @config
<byer@mail.all-net.net>, and just slightly modified them, making $ mms
them slightly more general and easier to maintain. $ mms test
$ mmm install
You can actually compile in almost any directory separately. Look This will buidl and install OpenSSL in the default location, which is
for a command procedure name xxx-LIB.COM (in the library directories) SYS$COMMON:[OPENSSL-'VERSION']. If you want it to be anywhere else,
or MAKExxx.COM (in the program directories) and read the comments at run config.com like this:
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 <option> <bits> <debug-p> [<compiler>] $ @config --prefix=PROGRAM:[OPENSSL]
<option> must be one of the following:
ALL Just build "everything".
CONFIG Just build the "[.CRYPTO]OPENSSLCONF.H" file.
BUILDINF Just build the "[.INCLUDE]BUILDINF.H" file.
SOFTLINKS Just copies some files, to simulate Unix soft links.
BUILDALL Same as ALL, except CONFIG, BUILDINF and SOFTLINKS aren't done.
RSAREF Just build the "[.xxx.EXE.RSAREF]LIBRSAGLUE.OLB" library.
CRYPTO Just build the "[.xxx.EXE.CRYPTO]LIBCRYPTO.OLB" library.
SSL Just build the "[.xxx.EXE.SSL]LIBSSL.OLB" library.
TEST Just build the "[.xxx.EXE.TEST]" test programs for OpenSSL.
APPS Just build the "[.xxx.EXE.APPS]" application programs for OpenSSL.
<bits> must be one of the following:
"" compile using default pointer size
32 compile using 32 bit pointer size
64 compile using 64 bit pointer size
<debug-p> must be one of the following:
DEBUG compile with debugging info (will not optimize)
NODEBUG compile without debugging info (will optimize)
<compiler> must be one of the following:
DECC For DEC C.
GNUC For GNU C.
You will find the crypto library in [.xxx.EXE.CRYPTO] (where xxx is VAX,
ALPHA or IA64), called SSL_LIBCRYPTO32.OLB or SSL_LIBCRYPTO.OLB depending
on how it was built. You will find the SSL library in [.xxx.EXE.SSL],
named SSL_LIBSSL32.OLB or SSL_LIBSSL.OLB, and you will find a bunch of
useful programs in [.xxx.EXE.APPS]. However, these shouldn't be used
right off unless it's just to test them. For production use, make sure
you install first, see Installation below.
Note 1: Some programs in this package require a TCP/IP library.
Note 2: if you want to compile the crypto library only, please make sure
you have at least done a @MAKEVMS CONFIG, a @MAKEVMS BUILDINF and
a @MAKEVMS SOFTLINKS. A lot of things will break if you don't.
Logical names:
==============
There are a few things that can't currently be given through the command
line. Instead, logical names are used.
Currently, the logical names supported are:
OPENSSL_NO_ASM with value YES, the assembler parts of OpenSSL will
not be used. Instead, plain C implementations are
used. This is good to try if something doesn't work.
OPENSSL_NO_'alg' with value YES, the corresponding crypto algorithm,
protocol or other routine will not be implemented if
disabling it is supported. Supported algorithms to
do this with are: AES, BF, CAMELLIA, CAST, CMS, COMP,
DES, DGRAM, DH, DSA, EC, EC2M, ECDH, ECDSA, ENGINE,
ERR, GOST, HEARTBEATS, HMAC, IDEA, MD2, MD4,
MD5, OCB, OCSP, PSK, RC2, RC4, RC5, RMD160, RSA, SCTP,
SEED, SOCK, SRP, SRTP, WHIRLPOOL. So, for
example, having the logical name OPENSSL_NO_RSA with
the value YES means that the LIBCRYPTO.OLB library
will not contain an RSA implementation.
OPENSSL_EXPERIMENTAL_'alg'
with value YES, the corresponding experimental
algorithm is enabled. Note that is also requires
the application using this to define the C macro
OPENSSL_EXPERIMENTAL_'alg'. Supported algorithms
to do this with are: JPAKE, STORE.
Test:
=====
Testing is very simple, just do the following:
@[.TEST]TESTS
If a test fails, try with defining the logical name OPENSSL_NO_ASM (yes,
it's an ugly hack!) and rebuild. Please send a bug report to
<openssl-bugs@openssl.org>, including the output of "openssl version -a"
and of the failed test.
Installation:
=============
Installation is easy, just do the following:
@INSTALL <root> <bits>
<root> is the directory in which everything will be installed,
subdirectories, libraries, header files, programs and startup command
procedures.
<bits> works the same way as for MAKEVMS.COM
N.B.: INSTALL.COM builds a new directory structure, different from
the directory tree where you have now build OpenSSL.
In the [.VMS] subdirectory of the installation, you will find the
following command procedures:
OPENSSL_STARTUP.COM
defines all needed logical names. Takes one argument that
tells it in what logical name table to insert the logical
names. If you insert if it SYS$MANAGER:SYSTARTUP_VMS.COM, the
call should look like this:
@openssldev:[openssldir.VMS]OPENSSL_STARTUP "/SYSTEM"
OPENSSL_UTILS.COM
sets up the symbols to the applications. Should be called
from for example SYS$MANAGER:SYLOGIN.COM
OPENSSL_UNDO.COM
deassigns the logical names created with OPENSSL_STARTUP.COM.
The logical names that are set up are the following:
SSLROOT a dotted concealed logical name pointing at the
root directory.
SSLCERTS Initially an empty directory, this is the default
location for certificate files.
SSLPRIVATE Initially an empty directory, this is the default
location for private key files.
SSLEXE Contains the openssl binary and a few other utility
programs.
SSLINCLUDE Contains the header files needed if you want to
compile programs with libcrypto or libssl.
SSLLIB Contains the OpenSSL library files themselves:
- SSL_LIBCRYPTO32.OLB and SSL_LIBSSL32.OLB or
- SSL_LIBCRYPTO.OLB and SSL_LIBSSL.OLB
OPENSSL Same as SSLINCLUDE. This is because the standard
way to include OpenSSL header files from version
0.9.3 and on is:
#include <openssl/header.h>
For more info on this issue, see the INSTALL. file
(the NOTE in section 4 of "Installation in Detail").
You don't need to "deleting old header files"!!!
Backward portability:
=====================
One great problem when you build a library is making sure it will work
on as many versions of VMS as possible. Especially, code compiled on
OpenVMS version 7.x and above tend to be unusable in version 6.x or
lower, because some C library routines have changed names internally
(the C programmer won't usually see it, because the old name is
maintained through C macros). One obvious solution is to make sure
you have a development machine with an old enough version of OpenVMS.
However, if you are stuck with a bunch of Alphas running OpenVMS version
7.1, you seem to be out of luck. Fortunately, the DEC C header files
are cluttered with conditionals that make some declarations and definitions
dependent on the OpenVMS version or the C library version, *and* you
can use those macros to simulate older OpenVMS or C library versions,
by defining the macros _VMS_V6_SOURCE, __VMS_VER and __CTRL_VER with
correct values. In the compilation scripts, I've provided the possibility
for the user to influence the creation of such macros, through a bunch of
symbols, all having names starting with USER_. Here's the list of them:
USER_CCFLAGS - Used to give additional qualifiers to the
compiler. It can't be used to define macros
since the scripts will do such things as well.
To do such things, use USER_CCDEFS.
USER_CCDEFS - Used to define macros on the command line. The
value of this symbol will be inserted inside a
/DEFINE=(...).
USER_CCDISABLEWARNINGS - Used to disable some warnings. The value is
inserted inside a /DISABLE=WARNING=(...).
So, to maintain backward compatibility with older VMS versions, do the
following before you start compiling:
$ USER_CCDEFS := _VMS_V6_SOURCE=1,__VMS_VER=60000000,__CRTL_VER=60000000
$ USER_CCDISABLEWARNINGS := PREOPTW
The USER_CCDISABLEWARNINGS is there because otherwise, DEC C will complain
that those macros have been changed.
Note: Currently, this is only useful for library compilation. The
programs will still be linked with the current version of the
C library shareable image, and will thus complain if they are
faced with an older version of the same C library shareable image.
This will probably be fixed in a future revision of OpenSSL.
Possible bugs or quirks:
========================
I'm not perfectly sure all the programs will use the SSLCERTS:
directory by default, it may very well be that you have to give them
extra arguments. Please experiment.
TODO:
=====
There are a few things that need to be worked out in the VMS version of
OpenSSL, still:
- Description files. ("Makefile's" :-))
- Script code to link an already compiled build tree.
- A VMSINSTALlable version (way in the future, unless someone else hacks).
- shareable images (DLL for you Windows folks).
There may be other things that I have missed and that may be desirable.
Please send mail to <openssl-users@openssl.org> or to me directly if you
have any ideas.
--
Richard Levitte <richard@levitte.org>
2000-02-27, 2011-03-18

18
README.PERL
View File

@ -37,6 +37,15 @@
package that we know of is ActiveState Perl, available from package that we know of is ActiveState Perl, available from
http://www.activestate.com/ActivePerl. http://www.activestate.com/ActivePerl.
Notes on Perl on VMS
--------------------
You will need to install Perl separately. One way to do so is to
download the source from http://perl.org/, unpacking it, reading
README.vms and follow instructions. Another way is to download a
.PCSI file from http://sourceforge.net/projects/vmsperlkit/files/
and install it using the POLYCENTER install tool.
Notes on Perl modules we use Notes on Perl modules we use
---------------------------- ----------------------------
@ -97,3 +106,12 @@
seen the tests succeed!): seen the tests succeed!):
$ cpan -f -i Text::Template $ cpan -f -i Text::Template
Note: on VMS, you must quote any argument that contains upper case
characters, so the lines above would be:
$ cpan -i "Text::Template"
and:
$ cpan -f -i "Text::Template"