Bug #225 | MySQL 4.012 - PHP, MyODBC, Perl May Not Work with release | ||
---|---|---|---|
Submitted: | 3 Apr 2003 9:02 | Modified: | 31 May 2003 14:16 |
Reporter: | gogman | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Embedded Library ( libmysqld ) | Severity: | S1 (Critical) |
Version: | 4.0.12 | OS: | Linux (Redhat 8.0) |
Assigned to: | CPU Architecture: | Any |
[3 Apr 2003 9:02]
gogman
[4 Apr 2003 0:26]
Indrek Siitan
Thanks for the bug report. We're trying to reproduce the problem, but it would be really helpful, if you could check a few things: - locate the directory where libmysqlclient is in. There should be a symlink named libmysqlclient.so, which points to libmysqlclient.so.12. Does the symlink exist and point to .12, or does it still point to .10? - can you run "ldd" on your binary of PHP and see if it's linked against libmysqlclient.so or libmysqlclient.so.10 directly?
[4 Apr 2003 16:08]
gogman
/usr/lib/libmysqlclient.so points to /usr/lib/libmysqlclient.so.12.0.0 lpp against rpm file does not see to get any results. [it may just be me] Here is the source: http://rpmfind.net/linux/RPM/redhat/updates/8.0/i386/php-mysql-4.2.2-8.0.7.i386.html
[4 Apr 2003 16:29]
gogman
php-mysql-4.3.1-rbt.rh8.1.i386.rpm source: http://www.aucs.org/rpmcenter/details/php-4.3.1-for-apache-1.3.x/php-mysql-4.3.1-rbt.rh8.1... Requires libmysqlclient.so.10 Looks like it is direct. Not through libmysqlclient.so.
[7 Apr 2003 6:28]
Indrek Siitan
In this case it's a problem with that RPM packaging, which is dynamically linking against a direct version of the libmysqlclient library. I have however notified the package maintainer (Edwin Chan) of the problem.
[7 Apr 2003 11:20]
gogman
Thank you with regards to your response to bug id 225, MySQL 4.012 - PHP, MyODBC, Perl May Not Work with release. The use of the rpm example was to illustrate the issue with regards to the linking library. A simple search of rpms shows nearly all rpms for nearly all platforms currently are dependent on libmysqlclient.so.10 and not directed towards libmsyslqclient.so or libmysqlclient.so.12. This issues, as indicated in my initial bug report, has occurred for persons performing direct builds (the behavior is not consisent and may depend on how the party performs the linking operation). Where is seems not to occur is when someone uses the CVS to build the application (php not mysql). This is not a direct bug for mysql, but since nearly every depended piece of software (perl, php, myodbc) has the same error, mysql will be blocked from being deployed. This thus represents a very serious communication challenge for mysql, since it needs to communicate to all parties that the dependency needs to be updated. thank you
[31 May 2003 14:16]
Alexander Keremidarski
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ Since 4.0.13 we provide RPM for backward compatibility MySQL-shared-compat-4.0.13-0.i386.rpm It consist of: /usr/lib/libmysqlclient.so -> libmysqlclient.so.12.0.0 /usr/lib/libmysqlclient.so.10 -> libmysqlclient.so.10.0.0 /usr/lib/libmysqlclient.so.10.0.0 /usr/lib/libmysqlclient.so.12 -> libmysqlclient.so.12.0.0 /usr/lib/libmysqlclient.so.12.0.0 /usr/lib/libmysqlclient_r.so -> libmysqlclient_r.so.12.0.0 /usr/lib/libmysqlclient_r.so.10 -> libmysqlclient_r.so.10.0.0 /usr/lib/libmysqlclient_r.so.10.0.0 /usr/lib/libmysqlclient_r.so.12 -> libmysqlclient_r.so.12.0.0 /usr/lib/libmysqlclient_r.so.12.0.0