On Tue, Aug 19, 2003 at 09:50:12PM -0400, [EMAIL PROTECTED] wrote:
> --- perl_20760/lib/ExtUtils/MM_Unix.pm 2003-08-18 12:48:39.000000000 -0400
> +++ perl/lib/ExtUtils/MM_Unix.pm 2003-08-19 21:33:42.000000000 -0400
> @@ -2327,6 +2327,15 @@
> $thisperl = $self->abs2rel($thisperl) if $self->{PERL_CORE};
>
> my @perls = ($thisperl);
> + my $ndbg = '';
> + if ( $Is_VMS ) {
> + if ( defined( $Config{usevmsdebug} ) ) {
> + if ( $Config{usevmsdebug} eq 'define' ) {
> + push @perls, map { "$_$Config{exe_ext}" } ('ndbgperl');
> + $ndbg = 'ndbg';
> + }
> + }
> + }
<snip>
> I would be very remiss in posting this if I did not
> also mention to the pumpking that last week Michael
> expressed a desire not to include such a patch into
> MakeMaker when I was discussing it on the vmsperl
> mailing list. His comments are in the archive at:
>
> http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/2003-08/msg00072.html
I missed your response to this. My answer is: because there's no need for
it to be. During the build process we control the name of the perl
executable. Once perl has been installed, we get the name of the perl
executable from $^X. Actually, during the build process we should be getting
the name of the perl executable from $^X. Is $^X not getting set
properly? Is lib/File/Spec/t/rel2abs2rel.t working? That relies on $^X.
If so then there's a deeper problem with the init_PERL/find_perl logic.
Or is this all to work around the dubious "find miniperl" logic?
# Define 'FULLPERL' to be a non-miniperl (used in test: target)
($self->{FULLPERL} = $self->{PERL}) =~ s/miniperl/perl/i
unless $self->{FULLPERL};
Your final note about my prefering three historical copies of perl.exe
seems... odd. There's some misunderstanding going on here.
I didn't know that there were actually *three* different Perl
executables. I thought there were only 2. Debugging and not debugging.
That's why I figured it made sense to alias ndbperl.exe to perl.exe.
Since perl.exe is the normal, fast as possible executable -- why can't
we use it during the core testing? Where is it? Did it get built? If not,
why not?
Even if a normal, non-debugging perl.exe doesn't get built you can still
alias ndbperl.exe to perl.exe during the build/test process and then
simply not install it.
But ndbgperl.exe should work alone without perl.exe.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
Milk may build strong bones, but adhesives are cement for the mind.
http://www.goats.com/archive/990103.html
