Ok, once the management decides that we can update to MySQL 5.1, I will 
try to provide a webrev for review

- sriram

Jeff Trawick wrote:
> Sriram Natarajan wrote:
>> Hi
>> I was wondering, if any one has any concerns if PHP depends on MySQL 
>> 5.1 client libraries for OpenSolaris 2009.06. What this means is AMP 
>> meta cluster will need to replace MySQL 5.0 with MySQL 5.1 package ? 
>> If no one has any concerns, I will send out the suggested diff and 
>> hope to make it into build 111. Any thoughts , concerns ?
>>
> Another issue, potentially worse:
>
> The apr-util DBD library links with libmysqlclient_r but the PHP MySQL 
> extensions link with libmysqlclient. A bit of web research suggests 
> that this specific combination (apr-util DBD + PHP + both MySQL client 
> builds) is to be avoided (multiply-defined symbols, behavior dependent 
> on load order, etc.).
>
> I'll file a CR for that shortly.
>
> --/--
>
> /usr/mysql library references in b109
>
> Full Nevada b109 install; /usr and /opt checked via ldd
>
> libmysqlclient:
>
> /usr/php/5.2/modules/pdo_mysql.so 
> (/usr/mysql/5.0/lib/mysql/libmysqlclient.so.15)
> /usr/php/5.2/modules/mysql.so 
> (/usr/mysql/5.0/lib/mysql/libmysqlclient.so.15)
> /usr/php/5.2/modules/mysqli.so 
> (/usr/mysql/5.0/lib/mysql/libmysqlclient.so.15)
> /usr/lighttpd/1.4/lib/mod_mysql_vhost.so 
> (/usr/mysql/5.0/lib/mysql/libmysqlclient.so.15)
>
> libmysqlclient_r:
>
> /usr/lib/python2.4/vendor-packages/_mysql.so 
> (/usr/mysql/lib/mysql/libmysqlclient_r.so.15)
> /usr/apr-util/1.3/lib/apr-util-1/apr_dbd_mysql-1.so 
> (/usr/mysql/5.0/lib/mysql/libmysqlclient_r.so.15)
> /usr/apr-util/1.3/lib/amd64/apr-util-1/apr_dbd_mysql-1.so 
> (/usr/mysql/5.0/lib/amd64/mysql/libmysqlclient_r.so.15)
>
> libndbclient:
>
> none
>
> --/--
>
> I don't see any fewer/additional ones from the package dependencies, 
> so that's good.
>
> _______________________________________________
>
>
> webstack-discuss mailing list
> webstack-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/webstack-discuss

Reply via email to