Mon May 10 05:15:10 2010: Request 57272 was acted upon.
Transaction: Correspondence added by RSCHUPP
Queue: PAR-Packer
Subject: Error building on Strawberry 5.12.0.1 32-bit (can't find
script/parl.exe)
Broken in: (no value)
Severity: Important
Owner: RSCHUPP
Requestors: [email protected]
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=57272 >
On Sat May 08 15:00:13 2010, CSJEWELL wrote:
> The earlier problem must have been a blip (sorry for the aggressive
> reporting), but it was a blip hiding a test issue:
...
> The problem is that gcc 4.x-compiled versions of Perl on Win32,
> including 5.12+ and greater versions of Strawberry Perl, have to use a
> gcc exception-handling DLL. Even the otherwise-static
> lib\core\libperl512.a has code that uses this dll, if I'm not mistaken.
Is that DLL needed for _every_ gcc compiled executable?
Note that a pp-packed executable is actually a stub with
a PAR archive tacked on. The stub itself is an executable built
by PAR::Packer. It contains another executable which is
a special purpose Perl interpreter; this executable is extracted
by the stub (along with some DLLs and core Perl modules) into
a temporary directory and then run.
If the sub itself needs the DLL that means you can't
execute the stub on a machine that hasn't the DLL installed
(and there's no workaround, sorry). OTOH, if the stub runs fine
and it's just the extracted Perl interpreter that needs the DLL
then adding the DLL to the pp command line will
do the trick. I'd prefer to do that automatically, if someone
can tell me how to find out whether the Perl running the pp script
is actually a Strawberry Perl.
Cheers, Roderich