From: Stefan Priebe <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: trying to compile with-jemalloc but ceph-osd is still linked to libtcmalloc
Date: Fri, 03 Jul 2015 11:15:11 +0200 [thread overview]
Message-ID: <5596529F.8060709@profihost.ag> (raw)
Hi,
i'm trying to compile current hammer with-jemalloc.
configure .. --without-tcmalloc --with-jemalloc
but resulting ceph-osd is still linked against tcmalloc:
ldd /usr/bin/ceph-osd
linux-vdso.so.1 => (0x00007fffbf3b9000)
libjemalloc.so.1 => /usr/lib/x86_64-linux-gnu/libjemalloc.so.1
(0x00007fc44bc25000)
libaio.so.1 => /lib/x86_64-linux-gnu/libaio.so.1
(0x00007fc44ba23000)
libleveldb.so.1 => /usr/lib/x86_64-linux-gnu/libleveldb.so.1
(0x00007fc44b7d2000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007fc44b5b6000)
libcrypto++.so.9 => /usr/lib/libcrypto++.so.9 (0x00007fc44aea8000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1
(0x00007fc44aca2000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc44aa9e000)
libboost_thread.so.1.49.0 => /usr/lib/libboost_thread.so.1.49.0
(0x00007fc44aa81000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fc44a878000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007fc44a571000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc44a2ef000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007fc44a0d8000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc449d4d000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc44be65000)
libsnappy.so.1 => /usr/lib/libsnappy.so.1 (0x00007fc449b47000)
libtcmalloc.so.4 => /usr/lib/libtcmalloc.so.4 (0x00007fc4498d4000)
libunwind.so.7 => /usr/lib/libunwind.so.7 (0x00007fc4496bb000)
Stefan
next reply other threads:[~2015-07-03 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 9:15 Stefan Priebe [this message]
2015-07-07 7:56 ` trying to compile with-jemalloc but ceph-osd is still linked to libtcmalloc Shishir Gowda
2015-07-07 9:17 ` Stefan Priebe - Profihost AG
2015-07-07 10:55 ` Shishir Gowda
2015-07-07 12:46 ` Stefan Priebe - Profihost AG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5596529F.8060709@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.