Description:
------------
In the README.TESTING file, it indicates:

"[Which php.ini is used]
-----------------------
 "make test" uses the same php.ini file as it would once installed.
The tests have been written to be independent of that php.ini file,
so if you find a test that is affected by a setting, please report
this, so we can address the issue."

However, I have PHP-5.0.4 installed on the same system that I am testing PHP-5.2.6.  The /etc/php.ini file for PHP-5.0.4 contains the statement:

extension_dir = "/usr/lib/php/modules"

When I execute run-tests.php, it reads /etc/php.ini and loads the modules from the old directory, rather than /usr/lib/20060613.

I found that I could create a new php.ini file in sapi/cli/ and it will be used by run-tests.php.  However, the README.TESTING file does not indicate that this step is needed.

Also, sapi/cli/php determines which modules to load based on the INI files in /etc/php.d.  Since different modules are shared, I get errors that modules have been loaded twice.

I tried using the syntax in the README.TESTING file:

TEST_PHP_EXECUTABLE=sapi/cli/php \
sapi/cli/php [-c /path/to/php.ini] run-tests.php [ext/foo/tests/GLOB]

I tried creating a new directory /etc-5.2.6 for my php.ini file and php.d directory.

However, this command did not work:

TEST_PHP_EXECUTABLE=sapi/cli/php \
sapi/cli/php -c /etc-5.2.6 run-tests.php /path/to/tests/

It ignored the "-c /etc-5.2.6" part entirely.  This parameter works for the compiled php executable, not for the test scripts that are run by run-tests.php.

I found that I had to configure php with --with-config-file-path=/etc-5.2.6 and --with-config-file-scan-dir=/etc-5.2.6/php.d.  I placed the new php.ini in directory /etc-5.2.6 and placed the INI files in this new directory /etc-5.2.6/php.d.

Jim











Reproduce code:
---------------
NA

Expected result:
----------------
NA

Actual result:
--------------
NA