Am 18.09.2013 19:22, schrieb Roberto Spadim:
hum about static libs... a default binary version with static libs are ok to me
a binary yes a source build should *never* default to static linking
... if anyone need a more "dynamic" we could compiler a second binary version
as said the binary packages does not matter distribution ones does 98 out of 100 users get their binaries from them upstream binaries are linked statically because you never know about a major upgrade of whatever distribution which would need a rebuild while break the binary for others
static is very easier to report bugs, we just know what is running and don't need to ask users about it today when i install mariadb i use the binary package, i'm not using rpm deb or others packages... when possible i have the binary and a copy of source package with a compiled binary (to make sure i can change if something happen, or a important patch appear)
in theory yes practically not really because you depend on enough dynamic libraries linking other libraries dynamic that you can only catch specific things with static linking but never make regressions impossible in case of cross-dependencies you may even hit a bug *because* you linked whatever statically and one of the dynamic libraries doe snot work properly with it while the distribution ships a patch for this siutuation not visible for you *because* of the static linking defaulting to static/bundeled libraries only makes the life of distributions harder they work around it, the ordinary user does not compile from source and the userbase which does has enough expierience to verify the results
2013/9/18 Sergei Golubchik <serg@mariadb.org <mailto:serg@mariadb.org>>
Hi, Reindl!
On Sep 18, Reindl Harald wrote: > > > Anyway, jemalloc is bundled with the mariadb sources and is linked in > > statically: > > > > $ ldd sql/mysqld|grep jemalloc > > $ grep jemalloc sql/mysqld > > Binary file sql/mysqld matches > > oh no - please no static libraries that is a very bad style > and explicitly forbidden by most distributions and patched > around whereever upstreams insists on it > > so we really need soemthing like > > -DWITH_SSL=system \ > -DWITH_ZLIB=system \
Yes. https://mariadb.atlassian.net/browse/MDEV-5026 I'll fix it for 5.5.34 At the moment you can try a workaround
-DWITH_JEMALLOC=no -DLIBJEMALLOC=jemalloc
(or only the first one, to disable jemalloc completely)