Well, it seems like I wasn't totally wrong with my assumption...
With a statically linked mod_unixd mod_fcgid is working! The error message is gone and a few some small tests showed that mod_fcgid is doing what it shall do. Strange thing about it is that it is a problem to stop httpd now. The only possible way is a kill -9. Something I wouldn't regard as everything is working fine. The changes in the compilation of Apache 2.4.1 was to add the following lines to the configure configuration: --enable-unixd --enable-mods-static='unixd' all other modules are compiled with a --enable-mods-shared=all I hope this information helps all of you, who are looking for a solution for this problem! I'll gonna go on looking for one, as well. Ciao Richard ----- Ursprüngliche Nachricht ----- Von: Richard Westebbe Gesendet: 22.03.12 10:20 Uhr An: users@httpd.apache.org Betreff: Re: [users@httpd] mod_fcgid 2.3.6 causes Apache 2.4.1 not to start with undefined symbol: ap_unixd_setup_child message Hi William, thank you that you've already answered the question of Tianyin! @Tianyin: Hi, thank you for your time and interest! I'm trying to solve the problem too, at the moment. The appears to me, that the problem is caused by the fact, that mod_unixd is new in 2.4.1. I compiled 2.4.1 with mod_unixd as an DSO, what might be the reason for the problem. Though mod_fcgid is including mod_unixd.h in fcgid_pm_unix.c in line 35: #if MODULE_MAGIC_NUMBER_MAJOR >= 20090209 #include "mod_unixd.h" #endif As I wasn't sure, whether the MODULE_MAGIC_NUMBER_MAJOR condition works, or not. So I forced the inclusion of mod_unixd.h by deleting the condition. The result was the same. The function still isn't defined. I guess I'll give it a try with an statically linked mod_unixd in the httpd executable. Maybe this might help. I'll report the result at this mailing list. Ciao Richard
