On Mon, Apr 13, 2009 at 3:33 PM, Memo Garcia <memo.garcia...@gmail.com> wrote: > But Steffen is also correct when he said that "it's strange that it's > failing during linking". Could that missing file be checked previously?
In theory :) But there's not enough information in Perl's Config.pm/Config_heavy.pl do to that. Note that PAR::Packer is an unusual customer here - linking to libperl isn't necessary for building any Perl modules (XS or generated by Swig etc). Only applications embedding a Perl interpreter (e.g. vim or Apache mod_perl) need to do that. PAR::Packer already tries second guessing how your perl was built/installed, but looking for libperl*.so would simply mean to re-implement your platform linker's library search algorithm. Cheers, Roderich
