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 thatVAX C is not and will not be supported.We have only tested with DEC C (aka HP VMS C / VSI C) and requireversion 7.1 or later. Compiling with a different ANSI C compiler mayrequire some work.Please avoid using C RTL feature logical names DECC$* when buildingand testing OpenSSL. Most of all, they can be disruptive whenrunning the tests, as they affect the Perl interpreter.About ODS-5 directory names and Perl------------------------------------It seems that the perl function canonpath() in the File::Spec moduledoesn't treat file specifications where the last directory namecontains periods very well. Unfortunately, some versions of VMS tarwill keep the periods in the OpenSSL source directory instead ofconverting them to underscore, thereby leaving your source insomething like [.openssl-1^.1^.0]. This will lead to issues whenconfiguring and building OpenSSL.We have no replacement for Perl's canonpath(), so the best workaroundfor now is to rename the OpenSSL source directory, as follows (pleaseadjust for the actual source directory name you have):$ rename openssl-1^.1^.0.DIR openssl-1_1_0.DIRAbout MMS and DCL-----------------MMS has certain limitations when it comes to line length, and DCL hascertain limitations when it comes to total command length. We dowhat we can to mitigate, but there is the possibility that it's notenough. Should you run into issues, a very simple solution is to setyourself up a few logical names for the directory trees you're goingto use.About debugging---------------If you build for debugging, the default on VMS is that imageactivation starts the debugger automatically, giving you a debugprompt. Unfortunately, this disrupts all other uses, such as runningtest programs in the test framework.Generally speaking, if you build for debugging, only use the programsdirectly for debugging. Do not try to use them from a script, suchas running the test suite.*The following is not available on Alpha*As a compromise, we're turning off the flag that makes the debuggerstart automatically. If there is a program that you need to debug,you need to turn that flag back on first, for example:$ set image /flag=call_debug [.test]evp_test.exeThen just run it and you will find yourself in a debugging session.When done, we recommend that you turn that flag back off:$ set image /flag=nocall_debug [.test]evp_test.exeChecking the distribution-------------------------There have been reports of places where the distribution didn't quiteget through, for example if you've copied the tree from a NFS-mountedUnix mount point.The easiest way to check if everything got through as it should is tocheck that this file exists:[.include.openssl]opensslconf^.h.inThe best way to get a correct distribution is to download the gzippedtar file from ftp://ftp.openssl.org/source/, use GZIP -d to uncompressit and VMSTAR to unpack the resulting tar file.Gzip and VMSTAR are available here:http://antinode.info/dec/index.html#SoftwareShould you need it, you can find UnZip for VMS here:http://www.info-zip.org/UnZip.htmlHow the value of 'arch' is determined-------------------------------------'arch' is mentioned in INSTALL. It's value is determined like this:arch = f$edit( f$getsyi( "arch_name"), "upcase")
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。