All of
 help / color / mirror / Atom feed
From: Christian Brunner <>
To: Sage Weil <>
Subject: Re: [PATCH 0/4] fixes and additions for the rpm spec file
Date: Fri, 24 Sep 2010 20:50:04 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

2010/7/9 Sage Weil <>:
> There's one other pitfall I ran into with the debs... by default symbols
> are stripped from all binaries, but the shared object needs
> to _not_ be stripped, or else the class loading doesn't work.  I have no
> idea where/when/if this is done during the rpmbuild.  The version in the
> built package should look like so:
> $ nm .libs/
> 000000000000797d T __cls_init
> 000000000020ce50 D __cls_name
> 000000000020ce7c B __cls_name__rbd
> 000000000020ce78 B __cls_ver__1_1
> 000000000020ce48 D __cls_ver_maj
> 000000000020ce4c D __cls_ver_min

After setting up a new build system I ran into this, too. I've now
looked at this a bit closer and was able to find a workaround. A patch
for the spec file is attached.


--- |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/ b/
index c92ff9d..ab91f7b 100644
--- a/
+++ b/
@@ -75,6 +75,11 @@ mkdir -p $RPM_BUILD_ROOT%{_localstatedir}/lib/ceph/tmp/
 mkdir -p $RPM_BUILD_ROOT%{_localstatedir}/log/ceph/
 mkdir -p $RPM_BUILD_ROOT%{_localstatedir}/log/ceph/stat

+# To avoid that is being striped by
+# we pretend that the debug symbols have already been extracted
+mkdir -p $RPM_BUILD_ROOT/usr/lib/debug/%{_libdir}/rados-classes/
+touch $RPM_BUILD_ROOT/usr/lib/debug/%{_libdir}/rados-classes/

To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to
More majordomo info at

  reply	other threads:[~2010-09-24 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09  9:11 [PATCH 0/4] fixes and additions for the rpm spec file Christian Brunner
2010-07-09 16:41 ` Sage Weil
2010-09-24 18:50   ` Christian Brunner [this message]
2010-09-24 21:04     ` Christian Brunner

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.