Re^2: How PAR pp works?

Replies are listed 'Best First'.
Re^3: How PAR pp works? by almut (Canon) on Jun 21, 2010 at 20:15 UTC
But the problem is not the switch but is how the modules are boundled in... Well, the thing is that on some occassions, `Module::ScanDeps` fails to detect dependencies. Usually, the problem is with shared object files that XS modules have been linked against, but there are also other difficult cases like the one above you found with `Switch`. In that case, you just have to help `pp` by telling it (using the options `-M`, `-l`, `-a`) what else to include in the package (`.pm` / `.so` files, etc.) in addition to what `Module::ScanDeps` automatically figured out. In case of doubt, try to deploy the package in an environment comparable to the target environment (i.e. without Perl/modules/libs installed) until it no longer complains about missing stuff...	[reply] [d/l] [select]
Re^4: How PAR pp works? by Anonymous Monk on Jun 21, 2010 at 23:01 UTC
In case of doubt, try to deploy the package in an environment comparable to the target environment (i.e. without Perl/modules/libs installed) until it no longer complains about missing stuff... That can be as simple as starting a new console and emptying %PATH%	[reply]
Re^5: How PAR pp works? by almut (Canon) on Jun 21, 2010 at 23:34 UTC
...on Windows, maybe. On Unix, and for shared libs, there's at least also the issue of runtime linker configuration (`ldconfig`), potentially compiled-in search paths (`-rpath`), `LD_LIBRARY_PATH`, and whatever else I don't think of at the moment :)	[reply] [d/l] [select]
Re^6: How PAR pp works? by Anonymous Monk on Dec 17, 2012 at 11:23 UTC


Welcome to the Monastery
	PerlMonks