On Wed, Oct 26, 2011 at 10:43 AM, Roderich Schupp
<roderich.sch...@googlemail.com> wrote:
> Obviously you must install PAR::Packer in all perlbrew managed versions
> and also use the corresponding pp.
On a more general note: If you have multiple versions of Perl installed
on a machine, you must be very careful that PAR::Packer built and installed
using Perl version A only draws on "stuff" from version A and no other.
(Actually the dependency is not visible in PAR/Packer.pm or the pp script,
but in modules PAR/StrippedPARL/{Dynamic,Static}.pm and the parl executable)
Getting things mixed up will likely result in error messages like the
one you saw.
Problems stem from installations where Config.pm is not 100% correct
i.e. contains settings that are not consistent with the actual installation.
These might go undetected if all you do is installing pure Perl or XS modules,
but when building PAR::Packer we create a custom Perl interpreter.
Also, PAR::Packer uses heuristics to gather some information about
the Perl installation that is NOT available from Config.pm - these might
get the wrong answer (i.e. report stuff from the wrong Perl installation).
To diagnose such problems, I'll need a full build log for PAR::Packer,
i.e. the output of (after unpacking the tarball)
perl Makefile.PL # or /what/ever/perl Makefile.PL
make
Also note that such a "wrong" build of PAR::Packer can never be repaired
later on by giving options to pp.
Cheers, Roderich
