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>
		
			
				
	
	
		
			59 lines
		
	
	
		
			1.7 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			59 lines
		
	
	
		
			1.7 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
 | 
						|
 NOTES FOR THE OPENVMS PLATFORM
 | 
						|
 ==============================
 | 
						|
 | 
						|
 Requirement details
 | 
						|
 -------------------
 | 
						|
 | 
						|
 In addition to the requirements and instructions listed in INSTALL,
 | 
						|
 this are required as well:
 | 
						|
 | 
						|
  * At least ODS-5 disk organization for source and build.
 | 
						|
    Installation can be done on any existing disk organization.
 | 
						|
 | 
						|
 | 
						|
 About ANSI C compiler
 | 
						|
 ---------------------
 | 
						|
 | 
						|
 An ANSI C compiled is needed among other things.  This means that VAX C
 | 
						|
 is not and will not be supported.
 | 
						|
 | 
						|
 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.
 | 
						|
 | 
						|
 | 
						|
 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.
 | 
						|
 | 
						|
 | 
						|
 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
 |