On Tue, Sep 15, 2009 at 7:58 PM, Jonathan Robinson <jonarobin...@rim.com> wrote: > It would indeed appear that PAR Packer has the problems indicated by Brian. > You may be interested in my stackoverflow post here: > http://stackoverflow.com/questions/1424181/can-par-packer-generate-stand-alone-scripts > > > In particular I see two common issues: > 1. Issues with something like Log::Any::Adapter::Null required by > CHI::Driver::File > 2. Issues with compiled modules such as Scalar::Util required by > Compress::Zlib > a. Ref: > http://search.cpan.org/~gbarr/Scalar-List-Utils-1.21/lib/Scalar/Util.pm#DIAGNOSTICS
Steffen Mueller (tsee on stackoverflow.com) has already addressed issue #1 there. No need to repeat it here. > Errors produced by issue #2 above: > [Tue Sep 15 09:11:06 2009] [error] "dualvar" is not exported by the > Scalar::Util module > [Tue Sep 15 09:11:06 2009] [error] Can't continue after import errors at > /usr/lib/perl5/site_perl/5.8.5/Compress/Zlib.pm line 9 > [Tue Sep 15 09:11:06 2009] [error] BEGIN failed--compilation aborted at > /usr/lib/perl5/site_perl/5.8.5/Compress/Zlib.pm line 9. > [Tue Sep 15 09:11:06 2009] [error] Compilation failed in require at -e line > 360. Please reduce the problem to a simple example that you can post here, error messages without the code that produced them are worthless. BTW, ' "dualvar" is not exported by the Scalar::Util module' is actually produced by Exporter::Heavy. Cheers, Roderich
