~x86 postfix-2.0.3 mysql-4.0.11a ( i don't need mysql. I wasn't aware that 4.x version was installed) After an emerge world (on ~x86 accepted system), when trying to start postfix, i get the error below. bash-2.05b# postfix restart postfix: error while loading shared libraries: libmysqlclient.so.10: cannot open shared object file: No such file or directory bash-2.05b# ldd /usr/sbin/postfix libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002b000) libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000) libmysqlclient.so.10 => not found libm.so.6 => /lib/libm.so.6 (0x4011f000) libz.so.1 => /usr/lib/libz.so.1 (0x40141000) libpam.so.0 => /lib/libpam.so.0 (0x40150000) libpcre.so.0 => /usr/lib/libpcre.so.0 (0x40158000) libdl.so.2 => /lib/libdl.so.2 (0x40162000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x40165000) libdb-3.2.so => /usr/lib/libdb-3.2.so (0x40192000) libnsl.so.1 => /lib/libnsl.so.1 (0x40230000) libresolv.so.2 => /lib/libresolv.so.2 (0x40245000) libc.so.6 => /lib/libc.so.6 (0x40258000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) bash-2.05b# cd /usr/lib bash-2.05b# ls -l libmysqlclient* lrwxrwxrwx 1 root root 24 Mar 5 18:42 libmysqlclient.so -> libmysqlclient.so.12.0.0 lrwxrwxrwx 1 root root 24 Mar 5 18:42 libmysqlclient.so.12 -> libmysqlclient.so.12.0.0 -rwxr-xr-x 1 root root 291475 Mar 5 18:42 libmysqlclient.so.12.0.0 lrwxrwxrwx 1 root root 26 Mar 5 18:42 libmysqlclient_r.so -> libmysqlclient_r.so.12.0.0 lrwxrwxrwx 1 root root 26 Mar 5 18:42 libmysqlclient_r.so.12 -> libmysqlclient_r.so.12.0.0 -rwxr-xr-x 1 root root 301570 Mar 5 18:42 libmysqlclient_r.so.12.0.0 bash-2.05b# Creating a symlink to libmysqlclient.so works fine. Keep up the good work ! Oktay Reproducible: Always Steps to Reproduce: 1. emerge postfix-2.0.3 and mysql-4.0.11a 2. try to restart postfix Actual Results: error message in details Expected Results: start I know this is an easy fix. I will even accept that it might be peculiar to my system somehow.. Anyway just wanted to bring it up since mysql 4.x and postfix on a system is not the most common combination.
Same problem here, same cause. Have just emerged the new postfix-2.0.6 and all is well. However, it does mean that the mysql upgrade managed to break postfix; suspect this isn't going to be a big problem since most people will also get the postfix upgrade... Phil
if you re-emerge postfix after mysql does the problem of the bad linking go away?
Not MySQL, but emerging the latest postfix (postfix-2.0.6) fixes the problem since it's linked against the correct mysql library. (see below) bash-2.05b# ldd /usr/sbin/postfix libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005c000) libmysqlclient.so.12 => /usr/lib/libmysqlclient.so.12 (0x40121000) libm.so.6 => /lib/libm.so.6 (0x40161000) libz.so.1 => /usr/lib/libz.so.1 (0x40183000) libpam.so.0 => /lib/libpam.so.0 (0x40191000) libpcre.so.0 => /usr/lib/libpcre.so.0 (0x4019a000) libdl.so.2 => /lib/libdl.so.2 (0x401a4000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x401a7000) libdb-3.2.so => /usr/lib/libdb-3.2.so (0x401d4000) libnsl.so.1 => /lib/libnsl.so.1 (0x40272000) libresolv.so.2 => /lib/libresolv.so.2 (0x40287000) libc.so.6 => /lib/libc.so.6 (0x4029a000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) Thank you for your help. As far as I am concerned this is not an issue anymore.
2.0.9 will be unmasked soon, thus addressing this bug. closing.
