A local copy of OpenSSL from GitHub
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

116 lines
4.1 KiB

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