ID: 44666 User updated by: geoffrey dot hughes at otago dot ac dot nz Reported By: geoffrey dot hughes at otago dot ac dot nz Status: Bogus Bug Type: Apache2 related Operating System: Mac OS X 10.5.2 PHP Version: 5.2.5 New Comment:
phpcli returns a loaded libtidy at /opt/local/lib whereas libphp5.so returns a libtidy loaded from /usr/lib It seems you are correct but my next question is why is libphp5.so linked against that one when I've specified a path to tidy in the configure statement. Previous Comments: ------------------------------------------------------------------------ [2008-04-08 10:57:06] [EMAIL PROTECTED] And that's supposed to be *nix? pff.. Well, if you had bothered to use google you would have found that the equivalent for ldd is: otool -L Anyway, as I'm sure this is just a misconfigured system and not a PHP bug -> bogus. ------------------------------------------------------------------------ [2008-04-08 10:42:25] geoffrey dot hughes at otago dot ac dot nz No ldd in OS X 10.5 ------------------------------------------------------------------------ [2008-04-08 08:06:02] [EMAIL PROTECTED] I would guess /opt/local/lib is not in your LD_LIBRARY_PATH, hence the shared apache2 module uses whatever it finds in the path. And CLI is propably linked as static..? Try this: # ldd /path/to/cli/binary and # ldd /path/to/libphp5.so ------------------------------------------------------------------------ [2008-04-08 02:48:15] geoffrey dot hughes at otago dot ac dot nz Description: ------------ PHPCLI uses the correct libtidy version when compiled with --with- tidy=/opt/local but the apache2 module uses the leopard default libtidy whether you use --with-tidy=/opt/local or not. PHPCLI Info: libTidy Release => 22 March 2008 Apache2 phpinfo.php: libTidy Release 31 October 2006 - Apple Inc. build 13 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=44666&edit=1
