I removed the inclusion of Glib.dll, Pango.dll, Gtk2.dll, Cairo.dll
I renamed these in _Glib.dll … in the site/lib/auto/Glib folders
And the script call  with perl still works (to my surprise)


The exe crash with
Can't locate loadable object for module Glib in @INC (@INC contains: 
C:\Users\rappazf\AppData\Local\Temp\par-72617070617a66\cache-03c9735aed48f3559d2bea43563ae9be2919152f\inc\lib
 
C:\Users\rappazf\AppData\Local\Temp\par-72617070617a66\cache-03c9735aed48f3559d2bea43563ae9be2919152f\inc
 CODE(0x31c09e4) CODE(0x31c0bdc)) at C:/strawberry/perl/site/lib/PAR/Heavy.pm 
line 99.

F.

From: Roderich Schupp <roderich.sch...@gmail.com>
Sent: 08 February 2019 09:23
To: RAPPAZ Francois <francois.rap...@unifr.ch>
Cc: par@perl.org; Shawn Laffan <shawnlaf...@gmail.com>
Subject: Re: use Glib -> crash


On Fri, Feb 8, 2019, 09:06 RAPPAZ Francois 
<francois.rap...@unifr.ch<mailto:francois.rap...@unifr.ch> wrote:
Adding Glib.xs.dll to my list does not change the problem: same error
Shawn was correct that they should not be added with --lib. Also they should be 
automatically detected, if not that's a bug.
Using pp_autolink.pl<http://pp_autolink.pl> without any other file added 
manualy gives the error
Can't load 
'C:\Users\rappazf\AppData\Local\Temp\par-72617070617a66\cache-c3a6620d3518bb97ef20a314815e03e1745a9234\778ce824.xs.dll'
 for module Pango: load_file:The specified module could not be found at 
C:/strawberry/perl/lib/DynaLoader.pm line 193.
  at C:/strawberry/perl/site/lib/PAR/Heavy.pm line 123.

Does Pango.xs.dll directly link to Glib.xs.dl?
Comparing the output gavec by pp_autolink and the list I used before, I see that
libgcc_s_sjlj-1.dll

That is always included as part of bootstrapping parl, hence superfluous.

Strangely (for me !) the dll, Glib, Gtk2, Pango, Cairo are present in auto/Glib 
etc despite they are not listed by pp_autolink

As above, they should be included automatically.
I also see that in lib/auto/ the folder Gtk2, Glib and Pango are not renamed in 
_Gtk2, _Glib, _Pango
Huh?

Cheers, Roderich

Reply via email to