"Sisyphus" <[email protected]> writes:
> Hi guys,
>
> I don't regard this as "high priority", and neither should you.
>
> I got this failure report recently:
>
> Inline-0.45:
> - i686-linux-thread-multi / 5.10.0:
> - FAIL http://nntp.x.perl.org/group/perl.cpan.testers/3166579
> - FAIL http://nntp.x.perl.org/group/perl.cpan.testers/3166624
>
> I sent off an email to the tester, but haven't heard back. Admittedly,
> I sent that email only a little over 2 days ago. Perhaps I should've
> waited a bit longer before bothering you people, but it's something
> that has me puzzled ... and I'm a little impatient to reach some sort
> of understanding about it :-)
>
> The thing that particularly puzzles me is the notion that the failure
> would be fixed if ExtUtils::F77 were to be specified as a prerequisite
> (see the "MISSING PREREQUISITES" section of the failure report). But
> then, the *entire* report makes no sense to me.
>
> Can anyone shed any light on this ?
>
> Intuitively, I feel that there's something broken in the tester's set
> up ... and I've no problem with that if that is, in fact, the case.
> But if the failure is indicative of some inadequacy in Inline-0.45,
> then it's a different matter.
For me it also looks like a broken perl installation. The test failure
messages come from diagnostics.pm complaining that it cannot find
perldiag.pod to feed itself from. Maybe perldiag.pod is really
missing, or the test user does not have sufficient permissions to read
it.
Regards,
Slaven
--
Slaven Rezic - slaven <at> rezic <dot> de
tkruler - Perl/Tk program for measuring screen distances
http://ptktools.sourceforge.net/#tkruler
