develooper Front page | perl.vmsperl | Postings from December 2001

Re: [PATCH lib/ExtUtils/] miniperl found before perl?

Thread Previous | Thread Next
Michael G Schwern
December 16, 2001 23:45
Re: [PATCH lib/ExtUtils/] miniperl found before perl?
Message ID:
On Mon, Dec 17, 2001 at 12:24:07AM -0600, Craig A. Berry wrote:
> >    1) Why is MakeMaker looking for miniperl?
> Hmm.  There is no miniperl installed with 5.005_03 (or later) in any
> installation I've looked at, nor have I found any version of Perl on
> VMS that defines miniperl as a symbol (it's always invoked directly
> during the core build).  Do you see something from the command C<SHOW

$ show symbol miniperl
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
$ show symbol perl
  PERL == "$PERL_ROOT:[000000]PERL.EXE"
$ show symbol perl_root
%DCL-W-UNDSYM, undefined symbol - check validity and spelling

which is odd because I know its set.

$ perl -v

This is perl, v5.7.2 built for VMS_AXP
(with 1 registered patch, see perl -V for more detail)

Copyright 1987-2001, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using `man perl' or `perldoc perl'.  If you have access to the
Internet, point your browser at, the Perl Home Page.

$ perl
Test::Harness likes to have Devel::CoreStack, but doesn't require it.
Checking if your kit is complete...
Looks good
Writing Descrip.MMS for Test::Harness
$ mmk test
miniperl "-Iperl_root:[lib]" "-MExtUtils::Install" -e "pm_to_blib({split(' ',<STDIN>)},'[]','')" <.MM_tmp
Perl 5.006001 required--this is only version 5.00503, stopped at /perl_root/lib/ExtUtils/ line 3.
BEGIN failed--compilation aborted at /perl_root/lib/ExtUtils/ line 3.
BEGIN failed--compilation aborted.
%MMK-F-ERRUPD, error status %X0000002C occurred when updating target PM_TO_BLIB.TS

> Perhaps your PERL_ROOT logical name points to a 5.005_03 build
> directory (or possibly such a directory is in your path).  But that
> should only happen if you were running Makefile.PL with 5.005_03.
> Were you?

No, I was running it with bleadperl where PERL_ROOT points to the
bleadperl build directory.  I do have a 5.005_03 lying around
somewhere, though.  My environment is a little screwy, that might be
the problem.

> I have successfully built and installed the extension against a
> bleadperl build directory tree, and though there were a number of
> test failures, I had no trouble getting it to build and install, 

You guys have to get out of the habit of treating test failures as
normal, at least when I'm around.  What were those failures?

> >I think the answer to #1 is "because it needs it when building the
> >core".  That can be made more elegant by only looking for miniperl if
> >PERL_CORE is set.  I can fix it in ExtUtils::MM_Unix (patch below),
> I don't have any objections to this patch.  Did it do you any good?

Haven't applied it on VMS yet, their server's been twitchy lately.


Michael G. Schwern   <>
Perl Quality Assurance	    <>	       Kwalitee Is Job One
humble abode cries
there is not enough paste here
restock erotica please
	-- imploded

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About