I've been playing with a test version of PerlPortable. It's a portable version of Perl that's based on Strawberry Perl. [cf. http://portableapps.com/node/12595]
I've mostly been installing various modules to ensure that everything works as it should. I've had good luck with both pure Perl and XS modules but PAR::Packer (0.978) is failing. I have the same problem in the cpan shell and in a manual install. Curiously (and perhaps coincidentally) it's failing at the same point as in bug #33256: right after calling static.exe. [cf. http://rt.cpan.org/Public/Bug/Display.html?id=33256] PerlPortable contains a custom version of Config.pm that replaces the hardcoded paths with ones calculated from $^X. According to everything I've been able to find and every test I've run $^X is always a fully qualified path on Windows. Somehow Config.pm is seeing it as "perl.exe" while building pp. This custom Config.pm then die()s because it can't do its job. I'd like to get pp to install and I'm sure I could if I temporarily hacked up Config.pm, but my real concern is to understand what's happening. There might be a larger issue here that PerlPortable needs to account for. Can anyone shed any light on how perl might be invoked during the pp build process that would cause $^X to be just "perl.exe" ? Thanks, -mjc
