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.
Created attachment 140478 [details, diff] Only restrict MPMs when perl is built without ithreads
*** This bug has been marked as a duplicate of bug 204736 ***
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.
fixed, thanks
