(Sending to the PAR list, as I neglected to include it in my initial
response).
If you can work out which packages the function calls come from then you
can check the packed executable to see if it contains them. If they are
not included then they have been missed in the module scan process.
Hi Claudio,
as a Windows user, I can't help with your Apple problem, but...
> By the way, why is the application trying to call something in
> "Users/we/perl5/perlbrew" which is a path in the machine where I
> compiled the application?
this is likely a problem of the Perl distribution you are
On Sat, Jun 15, 2019 at 11:49 AM Oliver Betz wrote:
> On Fri, Jun 14, 2019 at 8:40 PM welle ozean via par wrote:
>
By the way, why is the application trying to call something in
> "Users/we/perl5/perlbrew" which is a path in the machine where I
> compiled the application?
>
>
> this is likely a
Thanks Roderich,
That shows how much I have used Tcl (i.e. never).
Claudio - The missing DLLs are likely to be the cause. You can use ldd on
the DLLs loaded by perl in a rinse-and-repeat process to identify the set.
You might also be able to adapt the code or the approach in pp_autolink to
run
