Upon emerging mod_php 4.3.11 it seems to place libphp4.so into /usr/lib/apache2-extramodules/ instead of /usr/lib/apache2/extramodules/ Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: locate libphp4.so /usr/lib/apache2-extramodules/libphp4.so Expected Results: locate libphp4.so /usr/lib/apache2/extramodules/libphp4.so One thing that MAY be causing this... I am actually installing from an overlay that I created to test that it works with apache 2.0.53. Apache will not start with -D PHP4 in the conf.d/apache file without the module being in the proper place - one other work around is to put the full path (/usr/lib/apache2-extramodules/libphp4.so) in the 70_mod_php.conf file.
/usr/lib/apache2/extramodules/ is a symlink to /usr/lib/apache2-extramodules/ here. You have broken something with your overlay. ;-) # ls -la /usr/lib/apache2 drwxr-xr-x 2 root root 400 Feb 9 01:20 build lrwxrwxrwx 1 root root 17 Feb 26 00:30 conf -> /etc/apache2/conf lrwxrwxrwx 1 root root 29 Feb 26 00:30 extramodules -> /usr/lib/apache2-extramodules lrwxrwxrwx 1 root root 8 Feb 26 00:30 lib -> /usr/lib lrwxrwxrwx 1 root root 16 Feb 26 00:30 logs -> /var/log/apache2 drwxr-xr-x 2 root root 1752 Nov 6 14:17 modules
The reason forthis overlay is the fact that mod_php-4.3.11 is blocking ~x86 versions of apache. I see no reason at the moment to do so.
I believe you need php/mod_php-4.3.11-r1 for ~x86 apache2 :-)
there is no dev-php/mod_php-4.3.11-r1 in portage :(
You should emerge sync...
Yep found it. Tnx that fixed it :)
so issue fixed? can this be closed then?
erm. I should read the whole message ;) closing then.
