-----Original Message----- From: maria-developers- bounces+wlad=montyprogram.com@lists.launchpad.net [mailto:maria- developers-bounces+wlad=montyprogram.com@lists.launchpad.net] On Behalf Of Michael Widenius Sent: Mittwoch, 30. November 2011 20:09 To: Sergei Golubchik Cc: Kristian Nielsen; maria-developers@lists.launchpad.net Subject: Re: [Maria-developers] MariaDB 5.5 binary tarball packages and libaio
Hi!
"Sergei" == Sergei Golubchik <serg@askmonty.org> writes:
Sergei> Hi, Kristian! Sergei> On Nov 25, Kristian Nielsen wrote:
One option could be statically linking libaio. Now in general, static linking is a can of worms with many pitfalls, however for just libaio it might work (libaio.so is statically linked on my Debian Wheezy). However, I am not sure if this is safe in general, nor do I know how to make cmake link just libaio statically?
Sergei> We can take the position that for correct integration of mariadb into OS Sergei> (and in particular, using OS dynamic libraries), one needs to use native Sergei> OS packages of mariadb - deb, rpm, whatever. And for tarballs all bets Sergei> are off.
However it would be good that with tarballs we do as much static linking as possible as this makes it more likely that the binary will work.
I pushed a workaround (or a hack dependent on point of view) that builds mysqld without shared libaio dependency, on Linuxes that provide static libaio (not all Linuxes have it, for example there is no static libaio on OpenSUSE). However, users of shared embedded library will still have shared libaio dependency, and users of static embedded library will need to link with either static or shared aio themselves to satisfy all dependencies . mysql_config has -laio in the link flags for embedded
Regards, Monty
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp