When I use pp to create an executable under Win98, the executable tries to
pick up any modules included in the PERL5OPT environment variable (in my
case, PERL5OPT=-MWild; Wild.pm is a simply wildcard expander) but then
dies with a complaint that it can't find the module, even if I explicitly
added it to the executable with pp's -M option. Everything runs OK if I
unset PERL5OPT. This is under ActivePerl 5.6.1 (build 629).
I'm *guessing* that the bundled interpreter is trying to load Wild.pm
*before* it's unpacked the archive, and therefore isn't finding it. It
seems to me that a standalone executable really shouldn't be looking at
Perl-specific environment variables at all during runtime. Is there a way
around this? (it's only a minor nuisance at my end, but it does mean that
if I distribute an executable, it might fail if one of the recipients has
perl installed and has PERL5OPT set).
