Peter Prymmer <[EMAIL PROTECTED]> wrote:
|
| miniperl, but we seem to have introduced an XS file dependency unique
| to VMS now since the perl build now fails with:
|
| MCR Sys$Disk:[]miniperl.exe "-I[.lib]" [.EXT.DYNALOADER]DYNALOADER_PM.PL
| %RENAME-I-RENAMED, DKB100:[PERL]DYNALOADER.PM;1 renamed to
| DKB100:[PERL.EXT.DYNALOADER]DYNALOADER.PM;1
| Copy/Log/NoConfirm [.ext.dynaloader]dynaloader.pm [.lib]DynaLoader.pm
| %COPY-S-COPIED, DKB100:[PERL.EXT.DYNALOADER]DYNALOADER.PM;1 copied to
| DKB100:[PERL.LIB]DYNALOADER.PM;1 (54 blocks)
| Can't locate VMS/Filespec.pm in @INC (@INC contains: lib/VMS_AXP lib
I'd bet that someone put in a C<require VMS::Filespec> into File::Spec::VMS.
In order to avoid such bootstrap problems, all of the VMS::Filespec routines
are available in VMS perl without including [.VMS]Filespec.pm; one just needs
to use the fully qualified names.
Regards,
Charles Bailey <[EMAIL PROTECTED]>
