Sat May 29 12:55:19 2010: Request 57948 was acted upon.
Transaction: Correspondence added by RSCHUPP
       Queue: PAR-Packer
     Subject: Bug report: pp-generated executable and a missing dependency 
libgcc_s_sjlj-1.dll
   Broken in: (no value)
    Severity: (no value)
       Owner: RSCHUPP
  Requestors: [email protected]
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=57948 >


On Sat May 29 09:03:30 2010, [email protected] wrote:
> perl5xx.dll depends on libgcc_s_sjlj-1.dll, so libgcc_s_sjlj-1.dll
> needs
> to be packed with, and extracted with perl5xx.dll before any Perl code
> is run at all.

Indeed, the problem is that the custom Perl interpreter 
"included" in every packed executable is linked dynamically
against perl5xx.dll. If you do
 
   pp -o foo.exe ....

and run foo.exe at least once you'll find the corresponding
cache area

  TMP\par-USER\cache-SHA1CHECKSUM

contains a file called foo.exe, too. That's the custom Perl
interpreter (it's always the same file). Now, if we linked
this executable dynamically, you'll also find a copy of perl5xx.dll
in this directory. But for Strawberry that's not enough, it needs
libgcc_s*.dll there, too.

So I see two possible options:
- stick with a dynamically linked custom Perl and
  modify (conditionally for Strawberry only) the whole 
  load_me_* shebang in myldr and add a load_me_3 file that
  would contain libgcc_s_*.dll (which would get extracted 
  alongside par.exe and perl512.dll)
- link the custom Perl statically, then the whole second
  bootstrap phase is omitted and the problem goes away

I definitely don't want to touch the load_me stuff with a
ten-foot pole, so I experimented with the latter option.
However, even after tweaking myldr/Makefile by hand I
couldn't produce a par.exe there that was NOT dynamically
linked against perl512.dll.

@Mark: Do you know why even

g++ main.o my_par_pl.o  -Wl,-Bstatic -Lc:\strawberry\perl\lib\CORE
-lperl512 -o par.exe

generates par.exe with a reference to perl512.dll? 

Cheers, Roderich






Reply via email to