Sun Apr 10 11:10:40 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 10:28:20, PHILKIME wrote: > Very odd, the user who reported this still has the issue with that > version I mentioned - just verified five mins ago. I wonder if it is > the same for you? Me too. But looking into the cache directory I see only a file called "biber" there, no libperl.dylib. If I look at the real biber (i.e. the packed exeutable), it should consist of the following parts, concatenated in order: [1] an executable (myldr/boot) which is really small except for some large byte arrays consisting of myldr/par and libperl.dylib (not compressed) [2] several core perl modules each starting with the string "FILE" (also uncompressed) [3] a zip containing the bulk of your application [4] a small trailer with some meta data, e.g. the basename of the cache directory and the position where part [2] starts Examining biber's [4] shows that [2] starts around 90k. That's way too small to contain libperl.dylib. So something went wrong, apparently already with your build of PAR::Packer as part [1] is generated when PAR::Packer is build. In fact, [1] is the contents of PAR::StrippedPARL::Static (uuendoded) and not influenced by any packing you do. Err... except when you packed with "pp -d", then you would get PAR::StrippedPARL::Dynamic instead which lacks libperl.dylib ... Cheers, Roderich