I think you lost me somewhere ....
The module still gets compiled as myext.so PHP_SHLIB_SUFFIX does not affect that at all (perhaps you're saying it's supposed to but did not?)
The PHP_SHLIB_SUFFIX affects the autoconf macro PHP_SETUP_OPENSSL() specifically on MacOSX (it may very well affect others too), because it is searching for libcrypto.so and libssl.so INSTEAD OF libcrypto.dylib and libssl.dylib this is WRONG, as libssl.so and libcrypto.so do NOT exist on MacOSX.
So no, we DO NOT want PHP_SHLIB_SUFFIX to be .so on MacOSX, as it causes detection to fail. If you look at my patch, the correct logic was already in place, I just changed $host_alias to $host_os because $host_alias was not being set, so the check did nothing.
-Brad
Andrei Zmievski wrote:
On Tue, 04 Jan 2005, Brad House wrote:
Just tried to phpize an extension, and it appears as though there is a problem on MacOSX. PHP_SHLIB_SUFFIX defaults to .so because a check is run on $host_alias, which is set to "".
Just to make sure: we do want PHP_SHLIB_SUFFIX to be set to .so on Mac OS X. Since we are not linking against the extensions, the .dylib does not apply.
- Andrei
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
