source: EcnlProtoTool/trunk/openssl-1.1.0e/NOTES.VMS@ 331

Last change on this file since 331 was 331, checked in by coas-nagasima, 6 years ago

prototoolに関連するプロジェクトをnewlibからmuslを使うよう変更・更新
ntshellをnewlibの下位の実装から、muslのsyscallの実装に変更・更新
以下のOSSをアップデート
・mruby-1.3.0
・musl-1.1.18
・onigmo-6.1.3
・tcc-0.9.27
以下のOSSを追加
・openssl-1.1.0e
・curl-7.57.0
・zlib-1.2.11
以下のmrbgemsを追加
・iij/mruby-digest
・iij/mruby-env
・iij/mruby-errno
・iij/mruby-iijson
・iij/mruby-ipaddr
・iij/mruby-mock
・iij/mruby-require
・iij/mruby-tls-openssl

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