After installing fresh mariadb, I'm having troubles using some software compiled with the mysql support.

For ex. mysql2 ruby gem: Incorrect MySQL client library version! This gem was compiled for 5.5.23-MariaDB but the client library is 5.1.61

Quick investigation took me into this conclusions: mariadb-client-5.5 introduces new libmariadbclient18, but depends on libdbd-mysql-perl which depends on libmysqlclient16.

So after install we have 2 libraries: libmysqlclient.so.16(from original mysql) and libmysqlclient.so.18(from mariadb).

And default libmysqlclient.so is symlinked to libmysqlclient.so.16

Can this be solved in some way?

Answer Answered by knielsen in this comment.

It is expected behaviour to have both libmysqlclient.so.16 and libmysqlclient.18.

The symlink to libmysqlclient.so.16 is a bug, it should be libmysqlclient.so.18. It will be fixed in the next 5.5 release, thanks for pointing this out!

https://mariadb.atlassian.net/browse/MDEV-257

Comments

Comments loading...