Bug 204916 – www-apache/mod_perl-2.0.3-r2: ithreads restriction too strict

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Martin von Gagern 2008-01-08 17:03:06 UTC]

The latest mod_perl ebuild tries to ensure that the threading capabilities of perl and apache agree. However while a threaded MPM really requires an ithread-enabled Perl installation, the reverse is not true as far as I know.
At least the Prerequisites section of the mod_perl install manual (see URL) describes the combination of a prefork MPM with an ithreads-enabled Perl. Also bug 182235 which probably was the reason for the changed test in the ebuild mentions no MPM-restrictions for ithreads-enabled Perl setups.

So I guess the ebuild is a bit pessimistic the way it is right now. It should restrict the allowed MPMs to non-threaded ones when Perl is built without ithreads, but otherwise allow any MPM unless there is a known issue with a combination.

[Comment 1 Martin von Gagern 2008-01-08 17:07:42 UTC]

Created attachment 140478 [details, diff]
Only restrict MPMs when perl is built without ithreads

[Comment 2 Jakub Moc (RETIRED) 2008-01-08 21:54:05 UTC]

*** This bug has been marked as a duplicate of bug 204736 ***

[Comment 3 Martin von Gagern 2008-01-18 18:48:27 UTC]

Reopening for lack of reply to bug 204736 comment 5. Can't reopen that one.

That bug talks a lot about error messages. This bug here is specifically for the fact that perfork and perl with ithrads are a combination marked supported by upstream, so I see no reason for the ebuild to forbid this combination.

[Comment 4 Benedikt Böhm (RETIRED) 2008-01-27 20:12:08 UTC]

fixed, thanks