You're right. It's the same issue as MDEV-16183.
The thing is, there are, basically, two ways to install MariaDB — RPM/DEB packages, where we know that the run-time configuration won't be much different from the build configuration, and we can install files in /etc. And binary tarballs, that are just unpacked anywhere on the filesystem.
In the first case we we don't link TokuDB with jemalloc, but preload it with LD_PRELOAD. This needs some changes in files in /etc. In the second case we link with jemalloc statically and our build host uses old jemalloc.
Gentoo should be more like the first case, but it builds using the bintar way. I'll see what we can do here...
Sergei, thank you very much!
Just for now, we'll temporarily mask jemalloc 5+ versions.
grknight, so far as I cannot see a good fix that will work for Gentoo and won't make bintar builds worse for everyone else (normally people build tokudb just in case, and use mysqld_safe or systemd).
But I see you do this for tcmalloc:
if use tcmalloc; then
|
echo "TARGET_LINK_LIBRARIES(mysqld tcmalloc)" >> "${S}/sql/CMakeLists.txt"
|
fi
|
You can do the same for jemalloc and it should solve the issue for Gentoo.
jan.reges, another option that you could is to LD_PRELOAD jemalloc. This will work with jemalloc 5 too. I think that if you set LD_PRELOAD in a /etc/conf.d/ file, it'll affect mysqld just fine.
Hi Sergei,
I reported your solution to Gentoo ticket system: https://bugs.gentoo.org/673470
Thank you for your time. Merry Christmas and a Happy New Year 