Carl Friedberg wrote:
!Peter, would you mind explicitly listing those four patches? I'm just
catching up for another round of !testing... thanks,
!
!Carl
No I do not mind, in fact I'll CC the list on this
since it is tough to keep track of this stuff on a platform
that does not support rsync :-).
First you'll need to grab 5.8.1-RC2 and then apply the
following four patches....
Craig Berry's fix to configpm (perl will not build on VMS
without this):
http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/2003-07/msg00016.html
Next you'll need Craig's fix up for File::Find which helps
MakeMaker build the extensions in the [.ext...] directory
tree:
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-07/msg01282.html
Next you'll want to apply Michael Schwern's latest
update to ExtUtils::MakeMaker (bring it up to 6.10_08):
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-07/msg01285.html
Next you might want to apply my patch for temp files
used by a couple of Encode extension tests (this one is
optional and has not been officially put into perl
AFAIK. You would likely only see the tests fail if you
had a logical name like F0 or F1, etc. pointing to an
unreadable directory):
http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/2003-07/msg00044.html
I have yet to work out any fix for the Net::Ping
test failures I see. They should only be noticed under
Multinet (not TCPIP services, a.k.a. UCX). I see two test
failures when perl is built with Compaq C S6.5-002 on
top of Multinet V4.4 Rev A-X.
There is also a test failure if you start your build from
a rooted logical directory location (as recommended in
README.vms). You won't see this one fail if you start with
something like:
$ set def dka300:[perl-5_8_1-rc2]
the failure is:
lib/File/Spec/t/rel2abs2rel..........FAILED at test 4
I hope that helps.
Peter Prymmer
