Hello Brian, therun-tests.php command will take care of any INI settings that are known to break tests.So if anyof your INI settings cause tests to failwe simply need to include them into the tests. Othewise it is important to test with your INI settings asyou want to know if your PHP installation works. Instead of knowing whether PHP in general could work.
best regards marcus Friday, December 1, 2006, 3:25:15 AM, you wrote: > I noticed the make test command may need the "-n" flag added so that > it will exclude already installed ini files. Specifically this > causes a problem when running make test on a system that already has > the same DSO installed so it tries to load it twice (once via the > installed ini and again for the test). Perhaps there's other places > where this causes problems? ... > " -n No php.ini file will be used" > diff --git a/Makefile.global b/Makefile.global > index ec86927..237c1a6 100644 > --- a/Makefile.global > +++ b/Makefile.global > @@ -74,7 +74,7 @@ test: all > TEST_PHP_EXECUTABLE=$(PHP_EXECUTABLE) \ > TEST_PHP_SRCDIR=$(top_srcdir) \ > CC="$(CC)" \ > - $(PHP_EXECUTABLE) -d 'open_basedir=' -d 'safe_mode=0' > -d > 'output_buffering=0' -d 'memory_limit=-1' $(top_srcdir)/run-tests.php > -d 'extension_dir=modules/' -d `( . $(PHP_MODULES) ; echo extension=$ > $dlname)` tests/; \ > + $(PHP_EXECUTABLE) -d 'open_basedir=' -d 'safe_mode=0' > -d > 'output_buffering=0' -d 'memory_limit=-1' $(top_srcdir)/run-tests.php > -n -d 'extension_dir=modules/' -d `( . $(PHP_MODULES) ; echo > extension=$$dlname)` tests/; \ > elif test ! -z "$(SAPI_CLI_PATH)" && test -x "$(SAPI_CLI_PATH)"; then > \ > TEST_PHP_EXECUTABLE=$(top_builddir)/$(SAPI_CLI_PATH) \ > TEST_PHP_SRCDIR=$(top_srcdir) \ > -Brian Shire > [EMAIL PROTECTED] > [EMAIL PROTECTED] > aim: int80h Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
