Michael G. Schwern wrote:
!Its not supposed to fix the core build.
!
!Try installing MM as a CPAN module with that patch against your installed
!ndbgperl. If that works then I know how to fix the core build properly.
I had tried to include an illustration of the inability
to build Pod2VMSHlp 1.02. Unfortunately in my previous
mail I omitted a critical MakeMaker message visible in
the C<perl Makefile.PL> output.
Here is a re-run with more text included. I started
with a [EMAIL PROTECTED] kit
configured with C<@configure "-Dusevmsdebug" "-des">,
ran C<mmk/macro=(__DEBUG__=1) install>, commented out
my earlier patch to MM_Unix::init_PERL(), added your PERL_CORE
patch to MM_VMS::find_perl(), I also added my separate
patch to File::Spec::VMS.pm::abs2rel as found in
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-08/msg01988.html
Then I unpacked Pod2VMSHlp-1_02 from CPAN and saw
the following:
$ perl Makefile.PL
Testing for presence of the Pod::Parser module...ok
Checking if your kit is complete...
Looks good
Unable to find a perl 5 (by these names:
dka200:[users.perl.581rc.perl_20898_root]ndbgperl.exe;1.exe perl.exe
perl5.exe perl5_8_1
.exe miniperl.exe, in these dirs: perl_root:[000000])
Writing Descrip.MMS for Pod2VMSHlp
In order to build, test, and install the modules and utilities run:
MMK
MMK test
MMK install
To set up foreign symbols for the utilities add:
$ pod2hlp == @PERL_ROOT:[utils]pod2hlp
$ pod2hlb == @PERL_ROOT:[utils]pod2hlb
$ pod2rno == @PERL_ROOT:[utils]pod2rno.com
to your LOGIN.COM or your PERL_SETUP.COM.
Note that the full path to ndbgperl.exe
is given, albeit with an additional .exe
tagged on. I suspect that comes from having
$thisperl (derived from $^X) put through the
$Config{exe_ext} map in MM_Unix::init_PERL.
I have no file
dka200:[users.perl.581rc.perl_20898_root]ndbgperl.exe;1.exe
I do however have a file
dka200:[users.perl.581rc.perl_20898_root]ndbgperl.exe;1
therein lies the bug. I am surprised that this
bug does not affect other .exe platforms, though perhaps
the additional perl names in the @perls array catches them.
Note for example that on Windows (not Cygwin) with
perl 5.8.0 I see this value for $^X:
C:\>perl -e "print $^X"
C:\Perl\bin\perl.exe
Note that if I appended .exe to that I'd
wind up with C:\Perl\bin\perl.exe.exe
and would not be able to build extensions there either.
I think this message contains sufficient information
to fix the problem, but I'll leave the patching to
you for now. MakeMaker with [EMAIL PROTECTED] is OK as is
on VMS as far as a "usevmsdebug" build is concerned.
Peter Prymmer
