Another thing to add to this, pear does not appear to compile with
the apache build.
I have this in my /etc/portage/package.use: dev-lang/php apache2
sockets mysql mysqli cli xml xsl pcre pdo-external session sqlite
curl gd iconv jpeg pcntl pear png posix soap snmp ssl zlib bzip2
bcmath ctype calendar curlwrappers gdbm exif dbm unicode
According to this url: http://gentoo-wiki.com/HOWTO_PHP_5_with_PEAR
all that pear needs in order to compile are the following USE flags:
cli pcre xml zlib. Maybe I'm a little out of it, but if you use the
ebuild command does it use /etc/portage/package.use or is that only
for emerge?
On Sep 26, 2006, at 3:31 PM, nate wrote:
I'm not sure if this is the proper list, if it is not I apologize
and if someone could tell me which I should use it would be
appreciated.
I'm having a few issues, and I'm not exactly sure where these are
exactly.
First off I built a custom apache-2.0.58 ebuild from the one in the
portage tree. It seems to have compiled just fine, and reads all
of our previous apache configs, it even loads up php just fine and
dandy. The reason for this custom build was we needed a specific
layout that we have created, which was used during the compiling of
apache.
Next onto php. Since our application relies heavily on php for the
back end we have several patches that we have created, as well as
needing very specific things done in the ./configure portion of
compiling. The patches applied just fine, I looked for the lines
that were changed in the source code while it was compiling and
they did change. The ./configure that I put inside /usr/portage/
eclass/depend.apache also ran with no problems.
My php.ini location was specified in two locations, first with --
with-config-file-path=/etc/apache as well as modifying
PHP_INI_DIR="/etc/apache/" in /usr/portage/eclass/php5_1-
sapi.eclass, though a php -i still shows the default location for
the gentoo build at /etc/php/apache2-php5/php.ini. I know it's
silly to require our php.ini to be in /etc/apache, but currently
that's where a *lot* of code looks for that file, symbolic links
cause issues so the file must reside there.
Finally libphp5.so does not seem to compile *at all.* This is
troublesome considering I am compiling with the apache support
enabled. Without that I won't be able to use php scripts through
apache, any idea why that doesn't exist?
--
[email protected] mailing list
--
[email protected] mailing list
