[MDEV-5731] Ship TokuDB engine for binary tarball with GLIBC <2.14 Created: 2014-02-25 Updated: 2015-01-19 Resolved: 2014-05-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | 5.5.38 |
| Type: | Task | Priority: | Major |
| Reporter: | Jean Weisbuch | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | buildbot, tokudb | ||
| Issue Links: |
|
||||||||||||
| Sprint: | serg-test-sprint-1 | ||||||||||||
| Description |
|
Tokutek makes binary tarballs that can run on older GLIBC (at least on 2.11) while the official MariaDB ones doesnt (except for the GLIBC2.14+ ones). |
| Comments |
| Comment by Sergei Golubchik [ 2014-05-29 ] |
|
We build pre-GLIBC-2.14 binaries on CentOS5 with glibc-2.5-42. It's not 2.11, it's way too old. The same technique I used on CentOS 6 kind of worked here, but optiimized (-O3) binaries were crashing inside glibc on shutdown (and then crashing again inside glibc when unwinding the stack for crash report). |