Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#16392 - [mod_perl] DynaLoader not working

Attached to Project: Arch Linux
Opened by Georg Grabler (STiAT) - Tuesday, 29 September 2009, 15:56 GMT
Last edited by Francois Charette (Firmicus) - Thursday, 01 October 2009, 15:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Kevin Piche (kpiche)
Pierre Schmitz (Pierre)
Francois Charette (Firmicus)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I lately updated from [testing], and don't know why, but I had problems bringing up my perl / mod_perl webservices.

Additional info:
* apache-2.2.13-3
* apr-util-1.3.9-3
* perl-5.10.1-2

[Tue Sep 29 17:43:44 2009] [error] DynaLoader object version 1.08 does not match $DynaLoader::VERSION 1.10 at /usr/lib/perl5/core_perl/ line 18.\n
Compilation failed in require at /usr/lib/perl5/vendor_perl/Apache2/ line 21.\nBEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/Apa
che2/ line 21.\nCompilation failed in require at /usr/lib/perl5/vendor_perl/Apache2/ line 24.\nBEGIN failed--compilation aborted at /us
r/lib/perl5/vendor_perl/Apache2/ line 24.\nCompilation failed in require at /usr/share/perl5/vendor_perl/ line 190.\nCompilation failed in r
equire at (eval 3) line 3.\n

The log complains about DynaLoader which comes with the perl package doesn't have the right object version (5.10.0 to 5.10.1 dynaloader was upgraded from 1.08 to 1.10). It looks as if the binary didn't come with the distribution - or at least not properly.

Strange is, I can do a perl -e "use CGI;" properly. If I add CGI to the httpd.conf (PerlModule CGI) it throws this error.

** Steps to reproduce
Update to testing, and load CGI in the apache conf as a requirement trough mod_perl.
This task depends upon

Closed by  Francois Charette (Firmicus)
Thursday, 01 October 2009, 15:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  perl and mod_perl in testing are now compatible.
Comment by Georg Grabler (STiAT) - Tuesday, 29 September 2009, 15:57 GMT
In between, the mod_perl version on the server was mod_perl-2.0.4-5.
Comment by Francois Charette (Firmicus) - Wednesday, 30 September 2009, 08:15 GMT
Huh? Pierre, why did you put perl 5.10.1 in testing? It's not ready yet, see  FS#10971 

mod_perl in extra is built for perl 5.10.0, so it's no wonder you have problems...

We thus need to add a rebuild of mod_perl in testing, and probably some other perl packages.

@Georg: In the meanwhile, revert to perl 5.10.0 in extra, please
Comment by Georg Grabler (STiAT) - Wednesday, 30 September 2009, 08:54 GMT
I already downgraded, just thought I'll let you know before somebody pushes it to extra...
Comment by Pierre Schmitz (Pierre) - Wednesday, 30 September 2009, 10:33 GMT
@Firmicus: Why do did you commit it into trunk then? We needed to rebuild perl for the db so name bump and we allways buiud from trunk. So,we have to revert all chagnes and rebuild perl 5.10.0? Note that this will move to extra very soon.
Comment by Allan McRae (Allan) - Wednesday, 30 September 2009, 10:38 GMT
And this commit message on trunk is very confusing if we were not supposed to use it:
"change db ver in depends, in preparation of db-4.8 rebuild"
And that came after the version bump...
Comment by Francois Charette (Firmicus) - Wednesday, 30 September 2009, 11:05 GMT
You're right. I should have informed you on the dev ML in the first place. Sorry for being rude ;)

Don't revert it to 5.10.0. The current build is perfectly OK.
It's just that perl now includes the file /usr/lib/ which is probably useless at this stage (see, but it does not hurt either.

So I am going to rebuild mod_perl with perl 5.10.1 and release it in testing, so as not to delay the move to extra.