Hi, Reindl! On Jul 13, Reindl Harald wrote:
i am missing something (probably simple like symbol versioning however done with some hack) or is it really not possible by providing symlinks to avoid "libmysqlclient.so.18 => not found" and all clients linked against 10.1.x failing?
I'm not quite sure. I used to think that symlinks don't solve the issue, and one needs the correct SONAME value inside the dynamic library. And I created MDEV-9294. But many people were asking for and complaining about symlinks, and nobody said that they didn't help. So I thought that may be I misunderstood the documentation and symlinks are enough. Now it looks like we might still need to imlement MDEV-9294 after all...
attached my current rpm-spec - the server itself works fine and i really want to avoid building a "server-only" package for the whole lifetime of Fedora25/26 as well as not wait for Fedora 27 to get 10.2.x
[root@testserver:/usr/lib64/mysql]$ ls insgesamt 308K lrwxrwxrwx 1 root root 13 2017-07-13 13:15 libmysqlclient.so.18.0.0 -> libmariadb.so lrwxrwxrwx 1 root root 13 2017-07-13 13:15 libmysqlclient.so.18 -> libmariadb.so -rwxr-xr-x 1 root root 305K 2017-07-13 13:15 libmariadb.so.3 lrwxrwxrwx 1 root root 15 2017-07-13 13:15 libmariadb.so -> libmariadb.so.3 lrwxrwxrwx 1 root root 17 2017-07-13 13:15 libmysqlclient_r.so -> libmysqlclient.so lrwxrwxrwx 1 root root 13 2017-07-13 13:15 libmysqlclient.so -> libmariadb.so
[root@testserver:/usr/lib64/mysql]$ ldd /usr/sbin/dbmail-imapd ... libmysqlclient.so.18 => not found
Regards, Sergei Chief Architect MariaDB and security@mariadb.org