ID: 19730
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Apache related
Operating System: debian linux potato
PHP Version: 4.2.3
New Comment:
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?
Previous Comments:
------------------------------------------------------------------------
[2002-10-04 13:08:36] [EMAIL PROTECTED]
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] [EMAIL PROTECTED]
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] [EMAIL PROTECTED]
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..
------------------------------------------------------------------------
[2002-10-03 09:26:40] [EMAIL PROTECTED]
Apologies, I copy and pasted the wrong build script. As you can see
from my first post to this bug, I did use a prefix of "/usr/local" when
configuring php.
Since the shipped version of the mysql libs are 3.23.39 (not 3.23.35),
it is obvious that the binary is built against other libs.
Additionally, the box has never had a version of MySQL installed on it
lower than 3.23.37, so the 3.23.35 version string has to be in error.
Additionally, there are no other copies of the mysql libs and includes
other than the 4.0.4 set. I verified this over lunch one day when I
left one of our boxen doing a recursive grep of /usr looking for old
versions.
Have you attempted to reproduce this? It should be exceedingly easy for
anyone to prove.
------------------------------------------------------------------------
[2002-10-03 07:17:18] [EMAIL PROTECTED]
If you use '--with-mysql' with php configure, it will use the bundled
mysql client libs which are of version 3.23.39
in 4.2.3.
You must use the prefix with which you installed the mysql
to get the correct libs and headers.
Also, make sure you don't have some older mysql libs in your system's
default libpath..
------------------------------------------------------------------------
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
