BuildSmart wrote:
The only differences I could find was that openssl was enabled in the
working builds but not enabled in the failing build.
[...]
I went a step further and manually added the ssl libraries (-lssl
-lcrypto) to the Makefile (both as bundled and shared) and all worked well.
This cannot be considered a bug (or maybe it is), perhaps an additional
check could/should be performed to see if mysql is built with SSL
support and if so check whether openssl is enabled and add the ssl
libraries to the sapi build or to MYSQL_SHARED_LDADD if it's not or to
auto-enable openssl?
yes, ext/mysql is not too clever about this and simply relies
on ext/openssl being enabled at the same time.
Adding an extra test can't rely on mysql_config though as AFAIR
it is not using mysql_config at all.
If you want to check whether you'd need to add a compile/link
test with a small example program that tries to e.g. use
http://dev.mysql.com/doc/refman/4.1/en/mysql-ssl-set.html
I'm not sure though whether this function is only available
with ssl-enabled MySQL builds or whether it is always there
and just returning error codes, i think it is the later so
you'd have to create a functionality test, not just a simple
"does it compile and link without errors" one.
As this is not a change to the actual functionality of ext/mysql
i think a working patch would be accepted even though the
extension is deprecated by now. OTOH i don't really think it
is worth the effort anymore though ...
--
Hartmut Holzgraefe, Principal Support Engineer
.
Discover new MySQL Monitoring & Advisory features at:
http://www.mysql.com/products/enterprise/whats_new.html
Hauptsitz: MySQL GmbH, Dachauer Str.37, 80335 München
Geschäftsführer: Kaj Arnö - HRB München 162140
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
