Bug #2648: Conflict with mod_cgi when compiling with Solid -> Apache will not start

From: Date: Mon, 01 Nov 1999 11:00:32 +0000
Subject: Bug #2648: Conflict with mod_cgi when compiling with Solid -> Apache will not start
Groups: php.dev 
Request: Send a blank email to php-dev+get-12055@lists.php.net to get a copy of this message
From: gordon+php@vip.fi Operating system: Linux 2.2.5-15smp PHP version: 3.0.12 PHP Bug Type: Solid related Bug description: Conflict with mod_cgi when compiling with Solid -&gt; Apache will not start When compiling PHP with Solid RDBMS support (--with-solid) and Apache with DSO support, the Apache module order affects whether Apache starts at all or not. By default, the PHP module gets installed as the last one on the list, thus crippling Apache (1.3.9) totally, not allowing it even to start. Moving mod_php _above_ mod_cgi on the list lets Apache start up normally. The problem exists only when compiling --with-solid, so there might be some very iffy interactions between mod_php, mod_cgi and the Solid libraries. I have submitted this as a non-serious bug to the Apache development team - the problem is not that big as it can be circumvented by placing mod_php _before_ mod_cgi on the module list, but I still think it could/should be fixed. It just might be that the problem is with the Solid libraries or Apache, but it also could be a problem with PHP. Thus the multiple bug reports to various development teams. To reproduce: Compile Apache (1.3.9) with --enable-module=all --enable-shared=max --enable-rule=SHARED_CORE --enable-rule=SHARED_CHAIN; Compile PHP with --with-apxs=<path to apxs> --with-solid=<path to Solid includes/libs>; the PHP module gets installed as the last one on the module list by default - Apache will not start at this point. Move mod_php _above_ mod_cgi on the module list and Apache will start nicely.

« previous php.dev (#12055) next »