Unfortunately I misspent six days trying various combinations of
calls to File::Basename::basename() and/or File::Basename::fileparse()
all to no avail as far as fixing the two failing test problem on
a usevmsdebug configured VMS build.  Those failures
were:

lib/ExtUtils/t/basic.................FAILED at test 22
lib/ExtUtils/t/Constant..............FAILED at test 5
Failed 2 test scripts out of 728, 99.73% okay.

I suspect that the $^X in use while running the shell command:

   mmk/macro=(__DEBUG__=1) test

Is in fact miniperl.exe.  If I ran the sequence of shell commands:

$ perl lib/ExtUtils/t/00compile.t
$ perl lib/ExtUtils/t/00setup_dummy.t
$ perl lib/ExtUtils/t/backwards.t
$ perl lib/ExtUtils/t/basic.t
$ perl lib/ExtUtils/t/bytes.t
$ perl lib/ExtUtils/t/Command.t
$ perl lib/ExtUtils/t/Constant.t

Then I could not trigger the basic.t test 22 nor the Constant.t test 5
tests to fail, but under the test configuration the foreign symbol
"perl" pointed to the full path to NDBGPERL.EXE.

Hence I left the $ndbg variable in in such a way that it would
only affect usevmsdebug VMS platforms (a small number of
perl installations).

By the way while I agree that the bug is low priority we
currently do not document in say the INSTALL file that
you cannot Configure a build of perl with the name
'miniperl' anywhere along the installation path (-Dprefix e.g.).
If you do not want to put the patch in then I'd recommend
mentioning the bug in INSTALL.

Peter Prymmer

Michael G Schwern <[EMAIL PROTECTED]> wrote on 09/11/2003 12:19:22 AM:

> On Tue, Sep 09, 2003 at 11:14:01AM -0400, [EMAIL PROTECTED] wrote:
> > I have been trying to patch MakeMaker as ships with recent
> > maint snapshots to accomodate some of Michael Schwern's
> > recent suggestions.  It has been difficult to do since one of
> > the problems that arises on VMS is test failures only seen
> > under "mmk test".  Along the way I realized that the s/miniperl/perl/
> > substitution seems as though it ought to cause trouble
> > elsewhere.  Indeed it now appears that on any platform
> > it is now not possible to install perl into a path that has
> > the substring "miniperl" along it.
>
> I'm going to go out on a limb and call this a low priority bug.
> Please post it on rt.cpan.org so it doesn't get lost.
>
> A pretty simple fix is to replace the clumsy s/miniperl/perl/ logic with
> a more accurate one using File::Basename to apply it only to the
filename.
>
>
> --
> Michael G Schwern        [EMAIL PROTECTED]
http://www.pobox.com/~schwern/
> I sit on the floor and pick my nose
>   and think of dirty things
> Of deviant dwarfs who suck their toes
>   and elves who drub their dings.
>    -- Frito Bugger, "Bored Of The Rings"

Reply via email to