I am running on a PPC, with up-to-date portage. I have apache 1.3 and uw-imap installed: $ emerge -s apache Latest version available: 1.3.27-r3 Latest version installed: 1.3.27-r3 $ emerge -s uw-imap Latest version available: 2002d Latest version installed: 2002d $ grep USE /etc/make.conf USE="X gnome gtk kde alsa arts dvd cups gphoto2 mpeg samba sox spell v4l xmms xvid xml imap" When I emerge mod_php, everything builds correctly. $ ls -l /etc/apache/extramodules/libphp4.so -rwxr-xr-x 1 root root 3034448 Jul 8 14:30 libphp4.so I execute the configure step and add the -D PHP4 to the apache start script. I then start apache with a tail -f on the error log and get: Cannot load /etc/apache/extramodules/libphp4.so into server: /etc/apache/extramodules/libphp4.so: R_PPC_REL24 relocation at 0x0d9c5660 for symbol 'encoding' out of range and apache does not start. I then decide to try without imap, so I edit USE flags accordingly and re-emerge mod_php. $ ls -l /etc/apache/extramodules/libphp4.so -rwxr-xr-x 1 root root 1884952 Jul 8 15:18 libphp4.so Wow, much smaller. With this version, apache starts with no error, and starts PHP nicely. Of course there is no imap support, which is a bummer. Questions: Why when I compile with imap does mod_php appear to statically link c-client? Is this right? And if it is statically linked, why does it throw an error when loading and complain that the 'encoding' symbol is out of range (presuming it's external, right)? Hold on... $ qpkg -l uw-imap net-mail/uw-imap-2002d * ... /usr/lib /usr/lib/c-client.a /usr/lib/libc-client.a -> /usr/lib/c-client.a ... Ah okay, looks like uw-imap does not have any kind of c-client.so... it just has a c-client.a. So that explains the static linking. But I still don't get the error. It doesn't make sense that the imap-enabled libphp4.so would fail in this way when it is loaded by apache.
$ emerge -s binutils Latest version available: 2.14.90.0.2 Latest version installed: 2.14.90.0.2
that bug is a duplicate of #21870 is an upstream problem and is fixed in php5 *** This bug has been marked as a duplicate of 21870 ***
