On Sun, Sep 13, 2009 at 09:49:03AM -0500, Craig A. Berry wrote:

> What's happening with these is that the build mostly succeeds but
> fails building perldoc:
> 
> MCR Sys$Disk:[]miniperl.exe "-I[-.lib]" "-I[-.ext.Cwd]" [.UTILS]PERLDOC.PL
> Perl lib version (5.10.0) doesn't match executable version (v5.11.0)
> at /perl_root/lib/Config.pm line 50.
> Compilation failed in require at [.utils]perldoc.pl line 9.
> BEGIN failed--compilation aborted at [.utils]perldoc.pl line 9.

That's from the expansion of

        $(MINIPERL_UP) $(MMS$SOURCE)

?


If so, until recently, that was

        $(MINIPERL) -"I[-.lib]" $(MMS$SOURCE)

with MINIPERL = MCR $(MINIPERL_EXE) "-I[.lib]"

So, which directory does it run in?
Was I overly aggressive in

http://perl5.git.perl.org/perl.git/blobdiff/961b49424657d49b2fbc2121bae68b67175886d8..052792984b8f177f8f314261429d93930437fc49:/vms/descrip_mms.template

in that quite a lot of the scripts being run as

        MCR $(MINIPERL_EXE) "-I[.lib]" -"I[-.lib]" $(MMS$SOURCE)

really didn't need -"I[-.lib]" as they were run from the top level, rather
one down? Were a lot of the -"I[-.lib]" defensive-cargo cult? Or do some of
the scripts change directory, so ./lib *and* ../lib are needed?

> Then Test::Smoke detects the presence of miniperl and runs minitest,
> so we get test results even though it reports a make failure.  The
> nonxs extensions do get built successfully (three times) but all post

Odd.

> the following nastygram
> 
>         Making Archive::Extract (all)
> 
> Creating Makefile.PL in ext/Archive-Extract for Archive::Extract
> 
> Running Makefile.PL in ext/Archive-Extract
> alma$dkb200:[smoke.test-smoke.blead]miniperl.exe;1 "Makefile.PL"
> "INST_LIB=[--.lib]" "INST_ARCHLIB=[--.lib]" "PERL_CORE=1"
> 
> You cannot build extensions below the perl source tree after executing
> a 'make clean' in the perl source tree.
> 
> To rebuild extensions distributed with the perl source you should
> simply Configure (to include those extensions) and then build perl as
> normal. After installing perl the source tree can be deleted. It is
> not needed for building extensions by running 'perl Makefile.PL'
> usually without extra arguments.
> 
> It is recommended that you unpack and build additional extensions away
> from the perl source tree.

I don't see that on Unix. I'm not sure why it's happening, and why it would be
just for one module.

Nicholas Clark

Reply via email to