Re: pp cannot find a file

2006-10-25 Thread rahed
[EMAIL PROTECTED] (Roderich Schupp) writes: It's not a bug, it's a feature :) When you call your pp'ed executable bar.exe, it will look for a script called bar or bar.pl in the zip when you execute bar.exe. The reason is that this way you can pack several related scripts into one

Re: bugs somewhere, not sure where: Perl? PAR? Image::Info::JPEG? All3?

2006-10-25 Thread Roderich Schupp
On 10/25/06, Steffen Mueller [EMAIL PROTECTED] wrote: open ( $fh, , \$data ) or die can't open string fh: $!; [...] That's the culprit! I explained this in detail in https://rt.cpan.org/Public/Bug/Display.html?id=11108 I concur that Module::ScanDeps can't statically detect whether a given

Re: bugs somewhere, not sure where: Perl? PAR? Image::Info::JPEG? All3?

2006-10-25 Thread Steffen Mueller
Roderich Schupp schrieb: [...] On the other hand, Glenn tried packing with pp -M PerlIO ... which is failry reasonable when seeing Can't locate PerlIO.pm errors. But that didn't work either, because it doesn't pick up PerlIO::scalar. One could add something like 'PerlIO.pm' = sub {

Re: bugs somewhere, not sure where: Perl? PAR? Image::Info::JPEG? All3?

2006-10-25 Thread Roderich Schupp
On 10/25/06, Steffen Mueller [EMAIL PROTECTED] wrote: At first, I thought modules passed to pp via -M just weren't scanned at all, but they are! (pp -M Math::Symbolic -e 'print Hello\n;' packages Parse::RecDescent alright.) Yeah, modules are scanned either way, but the %Preload magic of M::SD