Upgrade chrome's OpenSSL to same version Android ships with.

openssl/INSTALL.VMS

                         VMS Installation instructions
                         written by Richard Levitte
                         <richard@levitte.org>
 
 
 Intro:
 ======
 
 This file is divided in the following parts:
 
@@ skipping 53 matching lines @@
 <byer@mail.all-net.net>, 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 <option> <rsaref-p> <debug-p> [<compiler>]
+  @MAKEVMS <option> <bits> <debug-p> [<compiler>]
 
 <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.
       SSL_TASK  Just build the "[.xxx.EXE.SSL]SSL_TASK.EXE" program.
       TEST      Just build the "[.xxx.EXE.TEST]" test programs for OpenSSL.
       APPS      Just build the "[.xxx.EXE.APPS]" application programs for OpenSSL.
 
-<rsaref-p> must be one of the following:
+<bits> must be one of the following:
 
-      RSAREF    compile using the RSAREF Library
-      NORSAREF  compile without using RSAREF
-
-Note 0: The RSAREF library IS NO LONGER NEEDED.  The RSA patent
-        expires September 20, 2000, and RSA Security chose to make
-        the algorithm public domain two weeks before that.
-
-Note 1: If you still want to use RSAREF, the library is NOT INCLUDED
-        and you have to download it.  RSA Security doesn't carry it
-        any more, but there are a number of places where you can find
-        it.  You have to get the ".tar-Z" file as the ".zip" file
-        doesn't have the directory structure stored.  You have to
-        extract the file into the [.RSAREF] directory as that is where
-        the scripts will look for the files.
-
-Note 2: I have never done this, so I've no idea if it works or not.
+      ""        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], called LIBCRYPTO.OLB,
-where xxx is VAX or AXP.  You will find the SSL library in [.xxx.EXE.SSL],
-named 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.
+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:
 ==============
@@ skipping 27 matching lines @@
 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>
+  @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.
-  SSLMISC       Various scripts.
   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 (LIBCRYPTO.OLB
-                and LIBSSL.OLB) themselves.
+  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"!!!
@@ skipping 63 matching lines @@
 - 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
+2000-02-27, 2011-03-18