FS#9450 - zim error with perl in testing
Attached to Project:
Arch Linux
Opened by Giorgio Lando (patroclo7) - Saturday, 02 February 2008, 21:14 GMT
Last edited by Kevin Piche (kpiche) - Thursday, 24 April 2008, 02:42 GMT
Opened by Giorgio Lando (patroclo7) - Saturday, 02 February 2008, 21:14 GMT
Last edited by Kevin Piche (kpiche) - Thursday, 24 April 2008, 02:42 GMT
|
Details
Description:
Zim does not start with per in testing. It fails with the following error: /usr/bin/perl: symbol lookup error: /usr/lib/perl5/site_perl/current/i686-linux-thread-multi/auto/Glib/Glib.so: undefined symbol: Perl_Tstack_sp_ptr Additional info: * package version(s): zim-0.23-1, perl 5.10.0-2 Steps to reproduce: upgrade to the latest perl in testing, launch zim |
This task depends upon
Closed by Kevin Piche (kpiche)
Thursday, 24 April 2008, 02:42 GMT
Reason for closing: Fixed
Additional comments about closing: Released version 0.24
Thursday, 24 April 2008, 02:42 GMT
Reason for closing: Fixed
Additional comments about closing: Released version 0.24
BTW, here zim seg faults on x86_64. It starts fine on i686.
Creating custom builder _build/lib/My/Builder.pm in _build/lib/My
Checking whether your kit is complete...
Looks good
perl: symbol lookup error: /usr/lib/perl5/site_perl/current/i686-linux-thread-multi/auto/Cairo/Cairo.so: undefined symbol: Perl_Tstack_sp_ptr
Can't open perl script "Build": No such file or directory
Can't open perl script "Build": No such file or directory
After that the compilation is interrupted.
Now, that error is away, but zim segfaults. I attach the output of 'strace zim' (it seems that it looks for things in a wrong path)
For me, that did the trick on x86_64.
Perhaps this leads to the conclusion that this is an upstream bug with zim and 5.10.0 perl?
Sorry for the empty attachment, I will reattach the strace as soon as I reach home this evening or sooner.
I also had to rebuild perl-gtk2-spell and perl-gtk2-trayicon against the new perl or it would hang before opening the notebook. after that zim doesn't report any errors, and after a few minutes of testing it seems to be working fine.
using: arch=i686, not testing.