#19730 [Opn->Fbk]: PHP --with-mysql reports the wrong client API version
| From: | sniper@php.net | Date: | Sat, 12 Oct 2002 15:23:46 +0000 |
| Subject: | #19730 [Opn->Fbk]: PHP --with-mysql reports the wrong client API version | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-22236@lists.php.net to get a copy of this message | ||
ID: 19730
Updated by: sniper@php.net
Reported By: shane@sell.com
-Status: Open
+Status: Feedback
-Bug Type: Apache related
+Bug Type: MySQL related
Operating System: debian linux potato
PHP Version: 4.2.3
New Comment:
Please try using this CVS snapshot:
http://snaps.php.net/php4-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-latest.zip
Even as I'm pretty sure this is some problem in your system or an user
error..
Previous Comments:
------------------------------------------------------------------------
[2002-10-04 19:21:39] shane@sell.com
yes, it does. Both the binary build and the apache module were built on
October 2, 2002, and they both show the correct build date.
------------------------------------------------------------------------
[2002-10-04 18:29:07] sniper@php.net
Can you check what the build-date is in the phpinfo output where the
incorrect mysql version is shown?
(2nd line, iirc)
Does it match the date you build it?
------------------------------------------------------------------------
[2002-10-04 13:08:36] shane@sell.com
Additionally, as I stated earlier, the PHP binary and the PHP Apache
modules are being compiled on the same server, with the same configure
options (except --with-apache).
Nothing on the server was changed between building the binary and the
module. They both used clean source trees (freshly untarred, even). The
binary reports the correct version, the module does not. The module
also does not report the version of the included MySQL libs, instead it
reports a version of MySQL that has never been installed on the server.
------------------------------------------------------------------------
[2002-10-03 20:01:10] shane@sell.com
with regards to the beta string, I have known about the development
life cycle, and the alpha, beta, gamma, and release phases of
development for many years. MySQL 4 is doing wonderfully in production,
and we put each release through rigorous testing in house before
implementing it. You should try it out sometime.
With regards to the version string, there are no files on the
filesystem that match 3.23.35.
Have you tried to build it yet using the build method I sent? If so,
what were the results?
------------------------------------------------------------------------
[2002-10-03 19:27:21] sniper@php.net
I hope you're aware that the 'beta' text in that version for mysql
really means that it's not ready for production..
Anyway, the api version shown in phpinfo() output comes from
mysql function called 'mysql_get_client_info()' and that is provided by
the mysql client libs and in the bundled mysql lib sources it's like
this:
mysql_get_client_info(void)
{
return (char*) MYSQL_SERVER_VERSION;
}
Try grepping your whole system for that incorrect version and you'll
find where it's defined..
------------------------------------------------------------------------
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/19730
--
Edit this bug report at http://bugs.php.net/?id=19730&edit=1