maria-developers team mailing list archive
Mailing list archive
Re: Installing jemalloc on build VMs
On Thu, 25 Apr 2013 18:29:32 +0200, Kristian Nielsen
Daniel Bartholomew <dbart@xxxxxxxxxxx> writes:
I'm getting ready to install jemalloc on the buildslaves for
https://mariadb.atlassian.net/browse/TODO-459 , and wanted to know
there was a preferred way to do it. Since we want to use a specific
version of jemalloc (3.1.0), I figured I would build from source on
of the build machines.
Has this been thought through properly with respect to packaging? My
it has not.
For .debs, which are what I know about, it is generally expected that
rebuild from `apt-get source mariadb-server`. This requires proper
dependencies. It doesn't work to install random stuff on random
It does not appear that jemalloc 3.1 is available on most .deb
support. Wheezy seems to have 3.0.0.
It is said that tokutek "requires" jemalloc - maybe it would be
better to fix
tokutek to work with standard libraries?
The proper way to produce .debs with custom jemalloc requires
custom packages for libjemalloc and including them in our repos.
I don't see any reason why MariaDB package couldn't bring it's own
Not everything has to be dynamically linked.
IIRC there were several such things happening with MySQL packages where
was known the distro didn't come with a suitable version of a library
some reason readline comes to mind, but don't quote me on that).