Edit report at http://bugs.php.net/bug.php?id=8295&edit=1
ID: 8295 Updated by: j...@php.net Reported by: bjoern at baer dot main dot de Summary: Allow using absolute path in extension= directive -Status: Open +Status: Bogus Type: Feature/Change Request Package: PHP options/info functions PHP Version: * Block user comment: N Private report: N New Comment: This is same as what is described in more recent bug #41310 Previous Comments: ------------------------------------------------------------------------ [2001-04-16 06:30:44] jmo...@php.net This is the correct behaviour. WIll change to feature/change request. -James ------------------------------------------------------------------------ [2001-01-03 10:28:07] bjoern at baer dot main dot de Works with extension_dir now, but the extension directive should care about an absolute path. ------------------------------------------------------------------------ [2001-01-03 10:17:25] s...@php.net Did you try using extension_dir directive? ------------------------------------------------------------------------ [2000-12-24 12:22:20] bjoern at baer dot main dot de Has it been fixed already now in CVS? (Can't test it at the moment) ------------------------------------------------------------------------ [2000-12-16 12:18:42] bjoern at baer dot main dot de Hi, we had our extension fastsearch.so in /etc/httpd and in /usr/local/lib/php.ini the following directive: extension=/etc/httpd/fastsearch.so PHP failed in loading this extension because it searched in: /usr/local/lib/php/extensions/no-debug-zts-BUILDDATE//etc/httpd/fastsearch.so As a workaround, I made a symlink, but I wonder why PHP doesn't accept extensions having in another path than /usr/local/lib/php/extension/... ? TIA, Björn. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=8295&edit=1
