Craig Berry wrote in response to me:
!No, PERL_CORE needs to be defined for many tests that run in the core. In
particular, packages that lead a !double life on CPAN and in the core need
to know which context they're in when running tests.
In the descrip.mms that I have PERL_CORE only appears in
the macro CORECLFAGS that is used only with the $(CC)
command. It does not appear related to any "mmk test"
target. It is not currently defined in [.vms]test.com.
How is it supposed to get into the "mmk test" environment?
In attempting to test outside of "mmk test" I found
complete failure without having a logical name PERL_CORE
defined to be "1".
You went on to add:
!Does it hang at this point, or just fail? There are two things I spot
right off that will prevent this test !from running as you are attempting.
One is that you are not, apparently, running from the [.t] directory. !The
!other is you did not (I'm guessing) first run
t/lib/ExtUtils/t/00setup_dummy.t. If not, a bunch of !things the
!MakeMaker tests need will not be present. It all gets cleaned up by
running !lib/ExtUtils/t/zz_cleanup_dummy.t.
00setup_dummy.t did run as a search of my "mmk test" log
file shows:
lib/Exporter.........................ok
lib/ExtUtils/t/00compile.............ok
lib/ExtUtils/t/00setup_dummy.........ok
lib/ExtUtils/t/backwards.............ok
The problem is a hang not a test failure.
I think that the problem is that File::Find is so broken
on VMS and that lib/ExtUtils/t/basic.t uses File::Find::find()
to find files in a test make directory.
If I can fix File::Find I might be able to let
lib/ExtUtils/t/basic.t continue to rely on it.
Otherwise a possible thing to do would be
add opendir(), readdir(), and closedir() calls
to basic.t.
Peter Prymmer
