Centos 5.5 64bit correct way to resolve libmysqlclient.so conflict /usr/lib64/ vs /usr/lib64/mysql ?

Trying to compile PHP 5.3.2 on CentOS 5.5 64bit with Percona 5.1.47 rel11.1 64bit when i try either

./configure --with-apxs2=/usr/sbin/apxs --with-mysql --with-mysqli=/usr/bin/mysql_config --with-libdir=lib64


./configure --with-apxs2=/usr/sbin/apxs --with-mysql --with-mysqli=/usr/bin/mysql_config


./configure --with-apxs2=/usr/sbin/apxs --with-mysql/usr --with-mysqli=/usr/bin/mysql_config --with-libdir=lib64

during make command i get

-lxml2 -lz -lm -lcrypt -o libphp5.lagcc: /usr/lib64/mysql/libmysqlclient.so: No such file or directorymake: *** [libphp5.la] Error 1

libmysql* files only exist in /usr/lib64 but php is looking for /usr/lib64/mysql directory as /usr/lib is empty.

ls -lah /usr/lib64/ | grep libmysqllrwxrwxrwx 1 root root 26 Jul 10 01:22 libmysqlclient_r.so -> libmysqlclient_r.so.16.0.0lrwxrwxrwx 1 root root 26 Jul 10 01:22 libmysqlclient_r.so.16 -> libmysqlclient_r.so.16.0.0-rwxr-xr-x 1 root root 4.9M Jun 25 20:21 libmysqlclient_r.so.16.0.0lrwxrwxrwx 1 root root 24 Jul 10 01:22 libmysqlclient.so -> libmysqlclient.so.16.0.0lrwxrwxrwx 1 root root 24 Jul 10 01:22 libmysqlclient.so.16 -> libmysqlclient.so.16.0.0-rwxr-xr-x 1 root root 4.9M Jun 25 20:19 libmysqlclient.so.16.0.0ls -lah /usr/lib/ | grep libmysql

I found this method http://default.io/2009/11/working-around-the-percona-mysql-r pm-dependancy-conflict-on-rhelcentos-5/ but not sure if it’s best way to do it ? Or a symlink ?? Got the exact symlink link I have to run ?

what’s best ?



Kindly check in your system the mysql is 64 bit install or 32 bit.

rpm -qa | grep -i mysql

This problem usually comes when you have install mysql 32 bit.

I think you are trying to intall php.

symlink can be work. But it will create the problem further.

Can you give me the mysql installation procedure how you did that.

-Vaneet Gupta

I dont use percona build, but I found on Centos 64 bit I had to add the following to php configure…

–libdir=/usr/lib64 --with-libdir=lib64

Might be worth trying the --libdir param, which you are missing at the moment.