Summary: | www-apache/mod_perl-2.0.3-r2 doesn't install for mpm-prefork enabled apache | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Timo Gurr (RETIRED) <tgurr> |
Component: | [OLD] Server | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | Martin.vGagern |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Timo Gurr (RETIRED)
![]() Wondering whether you've read the message at all... no, you can't mix non-threaded and threaded things at will. Perhaps I was not clear enough, my point was to mention that the description of the error message could perhaps be improved by adding something like: * The module you are trying to install (mod_perl) * will only work with one of the following MPMs: * event worker * You do not currently have any of these MPMs installed. * Please re-install apache with the correct mpm-* USE flag set. * _OR_ * re-install libperl and perl with proper "ithreads" USE flag if * you don't want to change your current apache mpm. Since the current error message in that case * The module you are trying to install (mod_perl) * will only work with one of the following MPMs: * event worker implies that it ONLY works with event and worker at all. Yeah, perhaps you don't understand that is a *generic* apache-module eclass message. And telling users to use an appropriate apache MPM for threaded/non-threaded stuff is a *lot* more sensible than telling them to re-emerge every single perl application they have installed. *** Bug 204916 has been marked as a duplicate of this bug. *** (In reply to comment #1) > no, you can't mix non-threaded and threaded things at will. Maybe not at will, but I still claim that non-threaded apache and threaded perl should be a valid combination, according to upstream documentation. So I suggest you either reopen one of these bugs, this one here or bug 204916, or you point us to a description of an actual problem that arises from using perfork and ithreads-enabled Perl. In the latter case, probably an upstream bug should be filed in order to get the documentation corrected or the issue resolved. |