ID:               47832
 Updated by:       johan...@php.net
 Reported By:      r dot borschel at gmx dot net
-Status:           Open
+Status:           Bogus
 Bug Type:         PDO related
 Operating System: OS X 10.5.6
 PHP Version:      5.3CVS-2009-03-29 (snap)
 Assigned To:      mysql
 New Comment:

You might try setting the DYLD_LIBRARY_PATH environment variable to
have the path to mysql first when starting PHP.

What happens is that PHP asks the system's dynamic loader to load
libmysqlclient, the dynamic loader has a list of directories to choose
from and looks for one after another for that file and loads it. See the
dyld(1) and elated manpages for details on that.

Setting to bogus as this is more an issue from the system than PHP.


Previous Comments:
------------------------------------------------------------------------

[2009-03-30 15:55:35] r dot borschel at gmx dot net

That's interesting. Here is the output:

$ otool -L sapi/cli/php | grep mysql
        /sw/lib/mysql/libmysqlclient.15.dylib (compatibility version 16.0.0,
current version 16.0.0)

So the libmysql getting loaded is from Fink (/sw is the root directory
of Fink). Clearly this is not what I wanted. Here is my complete
configure listing:

'./configure' \
'--prefix=/usr/local/php-5.3' \
'--with-apxs2=/usr/local/apache2.2.9/bin/apxs' \
'--enable-exif' \
'--with-gd' \
'--with-jpeg-dir=/sw' \
'--with-png-dir=/sw' \
'--enable-mbstring' \
'--with-mcrypt=/sw' \
'--with-mhash=/sw' \
'--with-iconv' \
'--with-mysql=/usr/local/mysql-5.1.32-osx10.5-x86' \
'--with-pdo-mysql=/usr/local/mysql-5.1.32-osx10.5-x86' \
'--with-pdo-pgsql=/usr/local/pgsql' \
'--with-pgsql=/usr/local/pgsql/' \
'--with-curl=/sw' \
'--with-zlib-dir=/sw' \
'--enable-soap' \
'--enable-sqlite-utf8' \
'--enable-zip' \

As you can see I'm using Fink libraries for some of the dependencies
but clearly not for mysql. It seems, however, that the Fink libmysql is
chosen anyway for whatever reason (/sw paths are prepended to the $PATH
so maybe that has something to do with it)

It's good to see that this issue is rather caused by a "version mess"
on my side even though the resulting behavior is a bit scary because it
does not indicate any errors, just garbled results.

Thanks for helping me resolve this issue. As far as I am concerned this
does not seem like a PHP-related issue and I guess unpredictable
behavior is supposed to be expected when using incompatible versions.

Feel free to close this issue if you think it does not deserve any
further attention.

------------------------------------------------------------------------

[2009-03-30 14:35:49] johan...@php.net

don't have a mac at hand, if ldd doesn't work try "otool -L" ("which is
part of the developer tools")

------------------------------------------------------------------------

[2009-03-30 14:27:23] johan...@php.net

hm, interesting mixup, can you try doing

ldd sapi/cli/php | grep mysql

to see which libmysql is being loaded?

------------------------------------------------------------------------

[2009-03-30 12:35:27] r dot borschel at gmx dot net

$ sapi/cli/php --ri pdo_mysql

pdo_mysql

PDO Driver for MySQL => enabled
Client API version => 5.0.38

Thats a bit strange, isnt it? My configure looks like this:

'./configure' \
...
'--with-mysql=/usr/local/mysql-5.1.32-osx10.5-x86' \
'--with-pdo-mysql=/usr/local/mysql-5.1.32-osx10.5-x86' \
...
 
That version mismatch may be the problem? Am I doing something
obviously wrong?

Thanks for your help.

------------------------------------------------------------------------

[2009-03-30 11:44:41] johan...@php.net

Which MySQL server and client library versions are you using? - I
tested using 5.1.31 worked for me:

$ sapi/cli/php --ri pdo_mysql

pdo_mysql

PDO Driver for MySQL => enabled
Client API version => 5.1.31

$ sapi/cli/php bug47832.php
array(4) {
  ["c0__id"]=>
  string(1) "1"
  ["c0__status"]=>
  string(9) "developer"
  ["c0__username"]=>
  string(6) "romanb"
  ["c0__name"]=>
  string(5) "Roman"
}


------------------------------------------------------------------------

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/47832

-- 
Edit this bug report at http://bugs.php.net/?id=47832&edit=1

Reply via email to