FS#45392 - [mod_perl] 2.0.8-5 missing symbol modperl_handler_name if compiled with gcc-5.1
Attached to Project:
Community Packages
Opened by Christoph Bayer (chrbayer) - Friday, 19 June 2015, 20:08 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 19 July 2015, 17:34 GMT
Opened by Christoph Bayer (chrbayer) - Friday, 19 June 2015, 20:08 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 19 July 2015, 17:34 GMT
|
Details
Description: mod_perl does not seem to provide symbol
modperl_handler_name if compiled with gcc-5.1,
for a patch see https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-apache/mod_perl/files/mod_perl-2.0.4-inline.patch?view=markup I have not tested the patch, but this is exactly the problem I observed Additional info: * package version(s) 2.0.8-5 * config and/or log files etc. Jun 19 20:36:14 beta.local systemd[1]: Starting Apache Web Server... Jun 19 20:36:14 beta.local apachectl[1480]: httpd: Syntax error on line 179 of /etc/httpd/conf/httpd.conf: Cannot load modules/mod_perl.so into server: /etc/httpd/modules/mod_perl.so: undefined symbol: modperl_handler_name Jun 19 20:36:14 beta.local systemd[1]: httpd.service: Control process exited, code=exited status=1 Jun 19 20:36:14 beta.local systemd[1]: Failed to start Apache Web Server. Jun 19 20:36:14 beta.local systemd[1]: httpd.service: Unit entered failed state. Jun 19 20:36:14 beta.local systemd[1]: httpd.service: Failed with result 'exit-code'. Steps to reproduce: Just configure apache to include mod_perl and try to start httpd |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Sunday, 19 July 2015, 17:34 GMT
Reason for closing: Won't fix
Additional comments about closing: mod_perl was dropped from the repo due to incompatibility with Perl 5.22.
Sunday, 19 July 2015, 17:34 GMT
Reason for closing: Won't fix
Additional comments about closing: mod_perl was dropped from the repo due to incompatibility with Perl 5.22.
#0 0x00007f0717ddec9e in modperl_env_init () from /etc/httpd/modules/mod_perl.so
There is an upcoming mod_perl release 2.0.9 that (after two and half years of waiting) officially declares apache 2.4 support http://mail-archives.apache.org/mod_mbox/perl-modperl/201505.mbox/%3CCADED%3DK60WOOBnrPH7aSia%3DydHd0EdDmu3e6ocAL4bG-MPLg60Q%40mail.gmail.com%3E
It also mentions that there is a crash with perl 5.22 https://rt.cpan.org/Public/Bug/Display.html?ShowHeaders=1;id=101962 and it looks the same as I see. Upstream promised to add perl 5.22 support in its mod_perl 2.0.10 release.
So for now no mod_perl with 5.22, unfortunately. I encourage to ping upstream on getting a fix for the problem.
I suggest to drop mod_perl to AUR to unblock perl5.22 rebuild. Those who wants to use mod_perl have to stick with perl5.20.
Also, Perl 5.22 has just been moved out of [testing]. People who use mod_perl won't be able to upgrade and instead receive the following error:
:: mod_perl: requires perl<5.21'
This seems to be the best we can do to avoid breakage without holding back the Perl 5.22 update any longer.
[1] https://lists.archlinux.org/pipermail/arch-commits/2015-June/284067.html
Perl 5.22 was moved out of [testing] 6 hours ago so mod_perl wasn't blocking anything. All this does is result in broken systems once existing mod_perl installations get upgraded to Perl 5.22.
Feel free to close this again, but state the correct reason and not invalid information.
- Existing mod_perl installations would conflict with Perl 5.22 thus preventing silent breakage upon upgrade.
- mod_perl would not be installable on new systems with Perl 5.22; this behavior is acceptable and would have been resolved with the release of mod_perl 2.0.10.
The situation we have now is that nothing will prevent systems with mod_perl from upgrading to Perl 5.22.