Re: [PHP] Extensions Directory (PEAR/PECL)
Robert Samuel White wrote: When I ran the command: pecl install zip-1.3.1 It intalled the zip.so file to: /usr/local/lib/php/extensions/no-debug-non-zts-20050922/zip.so Extensions are compiled with a given Zend/PHP API. The zip extension you installed was compiled against the API dated 2005-09-22. I complained/questioned this default behavior of 'pecl install' myself and asked why pecl didn't use the 'extension dir' value I already had set in the PHP.ini file. The response was that the php.ini file is not the authoritative definition for the extension directory because there could in theory be many php.ini files all over the system not to mention the defaults which might be used if no php.ini file exists at all. The only way I could get zip support working was to put it here: /usr/local/php/ext Which is where my extensions directory is located. I've checked, and the extensions directory is set correctly in the php.ini file. Does anyone know where/how it would come up with this other path? I've seen several people complain about this problem, but it doesn't seem anyone wants to change it. If you want your life to continue without tons of stress, just go with the flow, don't try to customize your installation, and just accept the defaults. Yeah, I didn't like that answer either. In summary: Change your php.ini file to match the 'no-debug-non-zts-20050922' default directory and your problems will go away. Dante -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Extensions Directory (PEAR/PECL)
[SNIP] When I ran the command: pecl install zip-1.3.1 It intalled the zip.so file to: /usr/local/lib/php/extensions/no-debug-non-zts-20050922/zip.so Extensions are compiled with a given Zend/PHP API. The zip extension you installed was compiled against the API dated 2005-09-22. I complained/questioned this default behavior of 'pecl install' myself and asked why pecl didn't use the 'extension dir' value I already had set in the PHP.ini file. The response was that the php.ini file is not the authoritative definition for the extension directory because there could in theory be many php.ini files all over the system not to mention the defaults which might be used if no php.ini file exists at all. The only way I could get zip support working was to put it here: /usr/local/php/ext Which is where my extensions directory is located. I've checked, and the extensions directory is set correctly in the php.ini file. Does anyone know where/how it would come up with this other path? I've seen several people complain about this problem, but it doesn't seem anyone wants to change it. If you want your life to continue without tons of stress, just go with the flow, don't try to customize your installation, and just accept the defaults. Yeah, I didn't like that answer either. In summary: Change your php.ini file to match the 'no-debug-non-zts-20050922' default directory and your problems will go away. Dante [/SNIP] Thanks. At least I know it's not something that can be changed. I'll just move them to the appropriate place after it installs them. That seems to be working just fine. I just wanted to make sure I wasn't missing some configuration directive that could point these to where I really want them... I did notice the 20050922 in my phpinfo() page under PHP Extension. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Extensions Directory (PEAR/PECL)
On Fri, May 19, 2006 12:43 pm, D. Dante Lorenso wrote: Robert Samuel White wrote: When I ran the command: pecl install zip-1.3.1 It intalled the zip.so file to: /usr/local/lib/php/extensions/no-debug-non-zts-20050922/zip.so In summary: Change your php.ini file to match the 'no-debug-non-zts-20050922' default directory and your problems will go away. Or, if you are CERTAIN that the version, debug, and zts settings for the two compilations are the same, just copy the .so file into your extensions directory. PHP is trying to keep you from shooting yourself in the foot by compiling an extension for one version, and dumping it will-he nill-he into some incompatible extensions directory. For those users with multiple installs of PHP, this is crucial, as you might imagine. -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
