On Sun, Jul 12, 2009 at 8:40 PM, Chris Marshall <[email protected]> wrote:
> Any suggestions for how to work around the problem?
>
See my other email.
The initial problem I was trying to resolve was
> failure of podselect to compile since Devel::Autoflush
> was not available. Unsetting PERL5OPT on the podselect
> line was a hack to resolve the problem but I couldn't
> think of a better way to do it. Apparently, there is
> no way to override PERL5OPT usage....
>
There was an unfortunate period of time when Devel::Autoflush in PERL5OPT
caused a lot of problems. Recent smokers now only use Devel::Autoflush
during Makefile.PL/Build.PL and go out of their way to make sure it's found,
even if someone invokes a different perl than the one running tests.
However, if you want to clear out PERL5OPT, you can just put "local
$ENV{PERL5OPT};" before your system calls. That will be more portable than
trying to unset it on the command line.
> Have other modules/module authors had this problem with
> podselect and other perl scripts being called from the
> shell within make?
>
Possibly, but if they complained, it never made it to cpan-testers-discuss
whre we could suggest an answer. :-) (Thank you Bob, for fowarding Chris'
question)
-- David
