ID: 22787 Updated by: [EMAIL PROTECTED] Reported By: gregory dot fennell at am dot sony dot com Status: Bogus Bug Type: MySQL related Operating System: RedHat v8.0 PHP Version: 4.3.1 New Comment:
Try latest mnogosearch and latest php. And dont forget to recompile mnogosearch and php after mysql upgrades. Previous Comments: ------------------------------------------------------------------------ [2003-08-26 11:01:17] serge at skycomp dot ca This issue seems to be related to mnogosearch PHP module and MySQL 4.x. If I remove the --with-mnogosearch it will compile fine. Not sure where to go from here as I need --with-mnogosearch ------------------------------------------------------------------------ [2003-04-08 14:06:28] azza at sbcglobal dot net Thank you for your response. I am assuming nothing. What I have asserted is that use of a direct or symlink to libmysqlclient.so.10 is causing a problem. This ownership of this issue balances between (1) mysql, (2) rpm packagers, and (3) php. My objective was not to assert blame, but to identify a significant issue. The fact is that the environment has changed with the new production release of mysql 4.0.12, which is causing a problem (bug) since php-mysql is dependent on libmysqlclient.so.10 versus libmysqlclient.so (which has a link to the current version). ------------------------------------------------------------------------ [2003-04-07 17:58:46] [EMAIL PROTECTED] Come on..if you can't get it to work, don't automatically assume that it's a bug in PHP. (which this REALLY IS NOT!) ------------------------------------------------------------------------ [2003-04-07 07:05:22] gregory dot fennell at am dot sony dot com OK, I will try this one more time. As several postings have confirmed, this is an issue. Can someone please work on a fix so that we can move forward with using the newest production releases of PHP? It seems that two postings from "azza at sbcglobal dot net" didn't get posted or were removed so I am reposting them. Posting #2: I am unclear why this has been set to bogus vs open. (1) A significant number of other parties are having this issue. (2) The failure to reproduce the error does not mean the error does not exist. (3) The installation process for php and mysql is quite varied, thus unlesss one tests all major installation scenarios no conclusion may be drawn. (4) As shown in my previous post - several rpms show a requirement of libmysqlclient.so.10. The correction is to use libmysqlclient.so which has a symlink to the current version, which is libmysqlclient.so.12. Thus, a) the bug is not bogus, b) the correction may be simple and c) failure to correct the error may have significant negative consequences. Posting #1: Same Issue: I agree that working together is the means for resolving this issue. (1) php-mysql-4.3.1-rbt.rh8.1.i386.rpm shows requirement of libmysqlclient.so.10 http://www.aucs.org/rpmcenter/details/php-4.3.1-for-apache-1.3.x/php-mysql-4.3.1-rbt.rh8.1.i386.rpm.html (2) php-mysql-4.2.2-8.0.7 RPM for i386 shows requirement of libmysqlclient.so.10 http://rpmfind.net/linux/RPM/redhat/updates/8.0/i386/php-mysql-4.2.2-8.0.7.i386.html What should be in the code is a reference to libmysqlclient.so which is a symlink to the current version - libmysqlclient.so.12. This may be a major issue if it crashes a large number of sites. Take a look at how libmyssqlclient.so is configured on your system. ------------------------------------------------------------------------ [2003-04-04 10:57:34] [EMAIL PROTECTED] Did you uninstall the old mysql 3.23 version before installing that new one? Are you sure it's not just a conflict between old and new version of mysql? And I say again: This is NOT any bug in PHP. Please ask further support questions on e.g. [EMAIL PROTECTED] ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/22787 -- Edit this bug report at http://bugs.php.net/?id=22787&edit=1
