2
0

NOTES.VMS 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. NOTES FOR THE OPENVMS PLATFORM
  2. ==============================
  3. Requirement details
  4. -------------------
  5. In addition to the requirements and instructions listed in INSTALL,
  6. this are required as well:
  7. * At least ODS-5 disk organization for source and build.
  8. Installation can be done on any existing disk organization.
  9. About ANSI C compiler
  10. ---------------------
  11. An ANSI C compiled is needed among other things. This means that
  12. VAX C is not and will not be supported.
  13. We have only tested with DEC C (a.k.a HP VMS C / VSI C) and require
  14. version 7.1 or later. Compiling with a different ANSI C compiler may
  15. require some work.
  16. Please avoid using C RTL feature logical names DECC$* when building
  17. and testing OpenSSL. Most of all, they can be disruptive when
  18. running the tests, as they affect the Perl interpreter.
  19. About ODS-5 directory names and Perl
  20. ------------------------------------
  21. It seems that the perl function canonpath() in the File::Spec module
  22. doesn't treat file specifications where the last directory name
  23. contains periods very well. Unfortunately, some versions of VMS tar
  24. will keep the periods in the OpenSSL source directory instead of
  25. converting them to underscore, thereby leaving your source in
  26. something like [.openssl-1^.1^.0]. This will lead to issues when
  27. configuring and building OpenSSL.
  28. We have no replacement for Perl's canonpath(), so the best workaround
  29. for now is to rename the OpenSSL source directory, as follows (please
  30. adjust for the actual source directory name you have):
  31. $ rename openssl-1^.1^.0.DIR openssl-1_1_0.DIR
  32. About MMS and DCL
  33. -----------------
  34. MMS has certain limitations when it comes to line length, and DCL has
  35. certain limitations when it comes to total command length. We do
  36. what we can to mitigate, but there is the possibility that it's not
  37. enough. Should you run into issues, a very simple solution is to set
  38. yourself up a few logical names for the directory trees you're going
  39. to use.
  40. About debugging
  41. ---------------
  42. If you build for debugging, the default on VMS is that image
  43. activation starts the debugger automatically, giving you a debug
  44. prompt. Unfortunately, this disrupts all other uses, such as running
  45. test programs in the test framework.
  46. Generally speaking, if you build for debugging, only use the programs
  47. directly for debugging. Do not try to use them from a script, such
  48. as running the test suite.
  49. *The following is not available on Alpha*
  50. As a compromise, we're turning off the flag that makes the debugger
  51. start automatically. If there is a program that you need to debug,
  52. you need to turn that flag back on first, for example:
  53. $ set image /flag=call_debug [.test]evp_test.exe
  54. Then just run it and you will find yourself in a debugging session.
  55. When done, we recommend that you turn that flag back off:
  56. $ set image /flag=nocall_debug [.test]evp_test.exe
  57. Checking the distribution
  58. -------------------------
  59. There have been reports of places where the distribution didn't quite
  60. get through, for example if you've copied the tree from a NFS-mounted
  61. Unix mount point.
  62. The easiest way to check if everything got through as it should is to
  63. check for one of the following files:
  64. [.crypto]opensslconf^.h.in
  65. The best way to get a correct distribution is to download the gzipped
  66. tar file from ftp://ftp.openssl.org/source/, use GZIP -d to uncompress
  67. it and VMSTAR to unpack the resulting tar file.
  68. Gzip and VMSTAR are available here:
  69. http://antinode.info/dec/index.html#Software
  70. Should you need it, you can find UnZip for VMS here:
  71. http://www.info-zip.org/UnZip.html