Sun Apr 10 09:18:02 2016: Request 113618 was acted upon.
Transaction: Correspondence added by RSCHUPP
Queue: PAR-Packer
Subject: Strange issue with not packing libperl.dylib
Broken in: 1.030
Severity: Important
Owner: Nobody
Requestors: philk...@kime.org.uk
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=113618 >
On 2016-04-10 09:09:07, PHILKIME wrote:
> When I run otool -L on the packed binary in the cache folder:
>
> > otool -L /var/folders/g0/t3rtgwks57366nz5dvxkrv_m0000gn/T/par-
> > 7068696c6b696d65/cache-
> > 3ce6949415c8a684cec51d84d1f897600bd5b03e/biber-darwin_x86_64
> /var/folders/g0/t3rtgwks57366nz5dvxkrv_m0000gn/T/par-
> 7068696c6b696d65/cache-3ce6949415c8a684cec51d84d1f897600bd5b03e/biber-
> darwin_x86_64:
> /opt/local/lib/perl5/5.22/darwin-thread-multi-
> 2level/CORE/libperl.dylib (compatibility version 5.22.0, current
> version 5.22.1)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
> current version 1226.10.1)
> /usr/lib/libutil.dylib (compatibility version 1.0.0, current
> version 1.0.0)
>
> It's looking for libperl.dylib in the wrong place ...
That's expected: OSX always burns absolute paths to shared libraries into
executables. Can you try the following:
pp -o foo.exe -E 'say "DYLD_LIBRARY_PATH=$ENV{DYLD_LIBRARY_PATH}";'
./foo.exe
This should tell you the DYLD_LIBRARY_PATH seen by the unpacked executable
(should be the cache directory). Look in this directory: there should be an
executable foo.exe and also libperl.dylib.
Cheers, Roderich
