Date: Thu, 17 Feb 2005 16:09:45 -0600
From: "Craig A. Berry" <[EMAIL PROTECTED]>
Subject: Re: failed tests after 5.8.6 build
In-reply-to: <[EMAIL PROTECTED]>
To: Dave Greenwood <[EMAIL PROTECTED]>
Cc: vmsperl@perl.org
> At 4:25 PM -0500 2/17/05, Dave Greenwood wrote:
> >VMS 7.3-1 axp, MMK V3.9-9, MultiNet V5.0
> >
> >I'm able to build Perl 5.8.6, but I get 3 failures when running the test
> >procedure ("MMK TEST"):
> >
> >lib/ExtUtils/t/basic......................FAILED at test 2
> >lib/ExtUtils/t/prereq_print...............FAILED at test 2
>
> Those two have been corrected in more recent versions of PathTools
> (they are not a problem with MakeMaker itself). I would go ahead and
> install and then upgrade PathTools:
I plan to add several additional CPAN modules. Is there an advantage to
building them into perl as opposed to adding or upgrading them later? I'm
thinking of the question in @CONFIGURE about which modules to build into
perl. If there is an advantage, how do I answer the question? Do I
need to re-enter all the default modules plus my additional modules? Or
do I just enter the additional modules?
> >lib/Net/Ping/t/510_ping_udp...............FAILED at test 2
>
> Dunno about this one. The test output you posted is less than
> helpful. There are so many things having to do with which network
> stack you have, what ECOs, how it's configured, and so on that it's
> hard to say what's going on without just debugging it. Running it
> outside of the test harness using the Perl debugger might turn up
> something.
This turned out to be a configuration issue. I had the updecho service
disabled. Once I re-enabled the service the test ran fine.
Dave
--------------
Dave Greenwood Email: [EMAIL PROTECTED]
Oak Ridge National Lab %STD-W-DISCLAIMER, I only speak for myself
