2014-04-23 11:05 GMT+03:00 Kristian Nielsen <kniel...@knielsen-hq.org>: > on demand by libmariadbclient. So to install both 32-bit and 64-bit client > library on amd64, we will need to put the client plugins under an > architecture-specific name. Like /usr/lib32/mysql/plugin/dialog.so or > whatever. Then 32-bit and 64-bit applications, running on the same 64-bit > system, can each load the correct plugin into their library.
Jacub: was your intention to say that these plugins should be installed at paths like? /usr/lib/x86_64-linux-gnu/mariadb/plugin/dialog.so /usr/lib/i386-linux-gnu/mariadb/plugin/dialog.so The paths /usr/lib32|64 are deprecated, right? If I've understood the situation correctly, we now have in the cmake build options the line "-DINSTALL_LIBDIR=lib/$(DEB_HOST_MULTIARCH)" and all that is needed is a patch for the upstream sources to install dialog.so and password.so into LIBDIR/mariadb/ (+ respective change in the mariadb-server-5.5.install file). https://wiki.debian.org/Multiarch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
