------------------------------------
Hello all,
I've recently installed the latest OpenPKG Apache RPM in an existing OpenPKG hierarchy, compiled with '--define "with_mod_php yes"' and '--define "with_mod_php_pear yes"', among other flags (as I would like Apache PHP support).
The problem I am having is that throughout the PHP tarball within the Apache RPM there are references to a '@php_dir@' variable, which as far as I understand should be replaced with 'OPENPKG_ROOT/lib/php', as that is where all the PHP/PEAR-related scripts are stored. However after installing the newly-created binary RPM I find that all the '@php_dir@' variables have been replaced by what looks to be a bogus path, namely 'OPENPKG_ROOT/RPM/TMP/apache-1.3.29-rootOPENPKG_ROOT/lib/php' (OPENPKG_ROOT in this particular case is /kolab). This results in PHP being unable to locate required include files, and the 'OPENPKG_ROOT/bin/pear' utility script does not work as it cannot find the PEAR.php file that it requires. Unfortunately there are countless other PHP-related files in the distribution that also utilise this path, meaning that they too are broken.
In order to solve this I've attempted placing a '%php_dir' variable in the relevant rpmmacros file within the openpkg hierarchy, tried hacking around with the Apache .spec file, as well as defining a 'PHP_PEAR_INSTALL_DIR' environment variable (I was grep'ing through the PHP files to find references to 'php_dir', which lead me to this), but none of these methods have proven successful. I do not have that much experience with RPM either, so I am not sure whether these would even be related to the problem.
Does anyone perhaps have experience with something similar to this, or even know of any other relevant files that I could edit to define this variable? I am at a loss at what to do, and would be grateful for any help possible.
Regards, Stuart Bing� ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
