On Fri, Feb 28, 2014 at 09:44:21PM -0600, Craig A. Berry wrote: > Hmm. It ran a lot faster because the build failed. The first sign > of trouble was this: > > Making Carp (all) > %DCL-W-IVVERB, unrecognized command verb - check validity and spelling > \GIT\ > WARNING - make_ext.pl is building Carp using EU::MM, as it found file > 'lib.DIR' at make_ext.pl line 476. I think I can see what two things I need to fix here are. Got the first done (it's 'lib.DIR', not 'lib' etc). Second is harmless, but probably that the git check should skip on VMS for now. > which happened for several other modules as well. Then things really > went south with: > > Running Makefile.PL in dist/PathTools > MDA0:[CRAIG.smoke.][fake-pm_to_blib]MINIPERL.EXE;2 "-I../../lib" > "Makefile.PL" "INST_LIB=[--.lib]" "INST_ARCHLIB=[--.lib]" > "PERL_CORE=1" > Can't locate ExtUtils/MakeMaker.pm in @INC (you may need to install > the ExtUtils::MakeMaker module) (@INC contains: .) at Makefile.PL line > 5. > BEGIN failed--compilation aborted at Makefile.PL line 5. > %SYSTEM-F-ABORT, abort > %SYSTEM-F-ABORT, abort > 1024 from dist/PathTools's Makefile.PL at make_ext.pl line 499. > Warning: No Makefile! > %MMK-F-NOOPNDSC, could not open description file descrip.mms > %MMK-F-NOOPNDSC, could not open description file descrip.mms > -RMS-E-FNF, file not found > -RMS-E-FNF, file not found That doesn't make sense. Effectively what happens is if the code figures that it has to use Makefile.PL (and therefore mmk), then it drops down into the existing code. So everything should still build (which it did for me on HP's system) The above looks like 'perl' is being used to run Makefile.PL, not 'miniperl'. miniperl is using lib/buildcustomize.pl to set up @INC to include all the toolchain modules. perl isn't (so it won't work) But it doesn't make sense to me why make_ext.pl *seems* to be running `perl -I../../lib Makefile.PL` instead of `miniperl -I../../lib Makefile.PL` Nicholas ClarkThread Previous | Thread Next