On Tue, Sep 02, 2003 at 01:26:45PM -0400, [EMAIL PROTECTED] wrote:
> Checking if your kit is complete...
> Looks good
> Unable to find a perl 5 (by these names:
> dga200:[users.perl.581rc.perl_20898_root]ndbgperl.exe;4.exe perl.exe
> perl5.exe perl5_8_1
> .exe miniperl.exe, in these dirs: perl_root:[000000])
> Writing Descrip.MMS for Pod2VMSHlp
> <snip>
Oh, I got it backwards.
--- MM_Unix.pm 2 Sep 2003 20:50:02 -0000 1.186
+++ MM_Unix.pm 2 Sep 2003 20:50:29 -0000
@@ -2324,7 +2324,7 @@
my $thisperl = $self->canonpath($^X);
$thisperl .= $Config{exe_ext} unless
# VMS might have a file version # at the end
- $Is_VMS ? $thisperl =~ m/(;\d+)?$Config{exe_ext}$/i
+ $Is_VMS ? $thisperl =~ m/$Config{exe_ext}(;\d+)?$/i
: $thisperl =~ m/$Config{exe_ext}$/i;
# We need a relative path to perl when in the core.
> Note also that it appears to be trying to look for
> the file $1$dga3004:[fds0.perl.581rc.perl_20898_root]ndbgperl.exe;4.exe
> within the directory perl_root:[000000]
> or, in other words, I think that MM_VMS::find_perl()
> is looking for the invalid file specification:
> perl_root:[000000]dka200:[users.perl.581rc.perl_20898_root]ndbgperl.exe;4.exe
I think its smart enough not to do that using file_name_is_absolute().
> But as shipped [EMAIL PROTECTED] can already
> test and build CPAN extensions hence the
> point of trying to use basename() may be moot.
It can only handle it when Perl is installed as "perl" or "ndbgperl" but
not any other name. Also, the CPAN version will not have the hack in the
core version. There's a real bug to be fixed here.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
Please Captain, not in front of the Klingons.
