Experience installing on Alpha VMS 8.3
[email protected] ("Miller, Edward S." via vmsperl) Mon, 15 Feb 2021 23:07:52 +0000
| Newsgroups | perl.vmsperl |
|---|---|
| Message-ID | <BY5PR07MB6982D211C811E74FA729E03EFF889@BY5PR07MB6982.namprd07.prod.outlook.com> |
--_000_BY5PR07MB6982D211C811E74FA729E03EFF889BY5PR07MB6982namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We have recently installed PERL v5.32.1 on our Alpha VMS 8.3 system using t=
he distribution from PERL.ORG.
The README.VMS suggests that:
"Regardless of how confident you are, make a bug report to the VMSPerl m=
ailing list."
This is not really a complete bug report, but more a summary of my experien=
ce doing the install
and an attempt to find out whether anyone is really interested in a more sp=
ecific 'bug report'.
As far as we can tell, the install for us was successful. Our user who rep=
orted that his code would not
work with our old perl version (5.004_04) reports that it now works with th=
e newly installed v5.32.1.
I have one change to the readme.vms I would strongly suggest: state unequi=
vocally that the install procedures should
be done using an ODS-5 disk, and that you are (very likely?) wasting your t=
ime attempting it on an ODS-2 disk.
(In our case the first MMK operation failed eventually--in two different wa=
ys, with two different MMK versions--
using an ODS-2 disk.)
The step @configure "-des" was apparently successful (assuming the many "=
NOT found" messages are benign).
The first "MMK" step had several "%CC-I" compiler messages, the most suspic=
ious of which was
neg =3D PL_statcache.st_ino < 0;
..................^
%CC-I-QUESTCOMPARE, In this statement, the unsigned expression "PL_stat=
cache.st_ino" is being compared with a relational
operator to a constant whose value is not greater than zero. This migh=
t not be what you intended.
at line number 2949 in file DISK$ORACLE5:[PERL.perl-5^.32^.1]pp_sys.c;1
The step "MMK test" completed and summarized its results with
"Failed 58 tests out of 2350, 97.53% okay."
I ran the procedure to get details of some of these failures using
$ @[.vms]test .EXE "" -"v" (filespec)
However I was successful in getting the proper syntax for (filespec) onl=
y for those that were originally
reported as FAILED with a file specification that started with "t/", not=
the others.
The step "MMK install" was apparently successful (assuming the many "Can't =
cd to (cpan/IO-Compress/) xxx.tmp: no such file or directory"
messages are benign).
A thanks to all of those who contributed to making PERL functional on VMS s=
ystems.
-- Ed Miller SLAC NAL.
--_000_BY5PR07MB6982D211C811E74FA729E03EFF889BY5PR07MB6982namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
We have recently installed PERL v5.32.1 on our Alpha VMS 8.3 system using t=
he distribution from PERL.ORG.
<div>The README.VMS suggests that:</div>
<div> "Regardless of how confident you are, make a bug rep=
ort to the VMSPerl mailing list."</div>
<div><br>
</div>
<div>This is not really a complete bug report, but more a summary of my exp=
erience doing the install</div>
<div>and an attempt to find out whether anyone is really interested in a mo=
re specific 'bug report'.</div>
<div><br>
</div>
<div>As far as we can tell, the install for us was successful. Our us=
er who reported that his code would not</div>
<div>work with our old perl version (5.004_04) reports that it now works wi=
th the newly installed v5.32.1.</div>
<div><br>
</div>
<div>I have one change to the readme.vms I would strongly suggest: st=
ate unequivocally that the install procedures should</div>
<div>be done using an ODS-5 disk, and that you are (very likely?) wasting y=
our time attempting it on an ODS-2 disk.</div>
<div>(In our case the first MMK operation failed eventually--in two differe=
nt ways, with two different MMK versions--</div>
<div>using an ODS-2 disk.)</div>
<div><br>
</div>
<div>The step @configure "-des" was apparently successful =
(assuming the many "NOT found" messages are benign).</div>
<div><br>
</div>
<div>The first "MMK" step had several "%CC-I" compiler =
messages, the most suspicious of which was</div>
<div><br>
</div>
<div> neg =3D PL_sta=
tcache.st_ino < 0;</div>
<div> ..................^</div>
<div> %CC-I-QUESTCOMPARE, In this statement, the unsigned expr=
ession "PL_statcache.st_ino" is being compared with a relational<=
/div>
<div> operator to a constant whose value is not greater than z=
ero. This might not be what you intended.</div>
<div> at line number 2949 in file DISK$ORACLE5:[PERL.perl-5^.3=
2^.1]pp_sys.c;1</div>
<div><br>
</div>
<div>The step "MMK test" completed and summarized its results wit=
h</div>
<div> "Failed 58 tests out of 2350, 97.53% okay."</di=
v>
<div><br>
</div>
<div> I ran the procedure to get details of some of these failu=
res using</div>
<div> $ @[.vms]test .EXE "" -"v&qu=
ot; (filespec)</div>
<div> However I was successful in getting the proper syntax for=
(filespec) only for those that were originally</div>
<div> reported as FAILED with a file specification that started=
with "t/", not the others.</div>
<div><br>
</div>
<div>The step "MMK install" was apparently successful (assuming t=
he many "Can't cd to (cpan/IO-Compress/) xxx.tmp: no such =
file or directory"</div>
<div>messages are benign).</div>
<div><br>
</div>
<div>A thanks to all of those who contributed to making PERL functional on =
VMS systems.</div>
<div><br>
</div>
<div> -- Ed Miller SLAC NAL.</div>
<br>
</div>
</body>
</html>
--_000_BY5PR07MB6982D211C811E74FA729E03EFF889BY5PR07MB6982namp_--