I just tried to do an "mmk install" with 5.6.0 plus Charles Lane's patches
and mine. The first thing I noticed is that README.VMS is no longer correct
in saying that you can define PERL_ROOT and then do an install because the
install target runs PERL_SETUP.COM and overrides whatever you've defined it
to. Having to know where you are going to install at configure time seems a
bit odd to me, but I guess it's easy enough to edit PERL_SETUP.COM later as
long as we tell folks that's what they have to do. I have a vague memory
this was discussed before but can't find where at the moment.
After doing that edit myself, I get boatloads of the following errors:
cp /perl_root/lib/VMS_AXP/5_6_0/CORE/
creating new version of /perl_root/lib/VMS_AXP/5_6_0/CORE/
Couldn't copy to /perl_root/lib/VMS_AXP/5_6_0/CORE/: invalid argument
chmod 444 /perl_root/lib/VMS_AXP/5_6_0/CORE/
Couldn't chmod 444 /perl_root/lib/VMS_AXP/5_6_0/CORE/: no such file or directory
installperl: not found at installperl line 650.
Then it helpfully tells me both "Installation complete" and
"%MMK-I-ACTNOUPD, action did not update target INSTALL." I got the same
thing running with BYPASS so I know it's not a file protection issue. The
directory in question exists. My guess would be the file copy is in a
subprocess of a subprocess and has somehow lost track of the perl_root logical.
Has anyone else encountered this or tried the install target?
_______________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
