[MDEV-6793] Install TokuDB from Generic Binaries Created: 2014-09-26 Updated: 2014-10-10 Resolved: 2014-10-10 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - TokuDB |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Minor |
| Reporter: | Nicolas Payart | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Description |
|
I used to install MariaDB from Generic Binaries on a Debian Wheezy 64bits: mariadb-10.0.13-linux-x86_64.tar.gz (from downloads.mariadb.org) I would like to use TokuDB as Storage Engine. However, TokuDB is available in "glibc_214" generic linux package as well as .deb packages, but it is NOT available in "non glibc_214 generic linux package"... I can't use "mariadb-10.0.13-linux-glibc_214-x86_64.tar.gz" because Debian Wheezy glibc is 2.13:
Is there a reason why TokuDB is not available in standard 64bits version of Generic Binaries? Especially since I can enable TokuDB by copying ha_tokudb.so from a debian wheezy apt install to the ./lib/plugin folder of my generic binaries, and all seems to work (I hope so anyway...)
|
| Comments |
| Comment by Sergei Golubchik [ 2014-10-10 ] |
|
we build two versions of "generic linux" binaries — "new" ones (glibc 2.14+) and "old" ones (gcc 2.5). That "old" one is built on CentOS 5, gcc 4.1.2, binutils 2.17, etc. everything's pretty old, this toolchain cannot build TokuDB. Introducing yet another set of generic linux binaries with glibc 2.13 would be undesirable, the practice shows that even two generic linux binary tarballs is confusing, ideally there should be only one. |