----- Original Message -----
From: "Dean Hamstead" <d...@fragfest.com.au>
To: "Sisyphus" <sisyph...@optusnet.com.au>
Cc: "David Oswald" <daosw...@gmail.com>; <inline@perl.org>
Sent: Thursday, January 19, 2012 6:31 PM
Subject: Re: Smoke test failure: Inline::CPP: Still dealing with "Can't
locate Parse::RecDescent, and M18 errors.
I'm not certain which of my tester machines created this. I have a rhel5,
rhel6, dragonflybsd and FreeBSD running- though clearly this is Linux.
rhel6 has perl 5.10 (tragically) but that kernel version in rhel5...
Hi Dean,
I've just worked out how to get to 0.33_004 FAIL reports and I'm now looking
at one of yours:
http://www.cpantesters.org/cpan/report/901971e6-4170-11e1-b516-a5fe68b631f7
(perl-5.14.2, freebsd).
I'm wondering if $ENV{PERL5LIB} somehow gets messed with when the
Inline::CPP test suite is run.
It would be interesting to see the output of the same build if the first of
the test scripts (t/01basic.t) was modified to begin with:
BEGIN {warn "\$ENV{PERL5LIB}: $ENV{PERL5LIB}\n";};
I don't know how easy (or otherwise) it is for you to give that a try.
At least we'd then know if PERL5LIB is still set correctly or not at that
point .... where we'd go from there, I'm not sure :-)
Do you have similar types of FAIL reports with any other modules ? Or is it
just with Inline::CPP ?
Cheers,
Rob
