From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: ceph-devel@vger.kernel.org
Subject: Re: Build fails on Fedora 14 on linking librados-config
Date: Fri, 09 Dec 2011 16:17:47 +0100 [thread overview]
Message-ID: <1494963.dggp1jPvU4@pc10> (raw)
In-Reply-To: <220547841.g14m0M3JMV@pc10>
Am Mittwoch, 7. Dezember 2011, 16:19:24 schrieben Sie:
> Hi,
>
> When building ceph 0.39 on Fedora 14, the build process fails with the
> following messages:
>
> CXXLD librados-config
> /usr/bin/ld: ./.libs/libglobal.a(libcommon_la-HeartbeatMap.o): undefined
> reference to symbol 'pthread_rwlock_wrlock@@GLIBC_2.2.5'
> /usr/bin/ld: note: 'pthread_rwlock_wrlock@@GLIBC_2.2.5' is defined in DSO
> /lib64/libpthread.so.0 so try adding it to the linker command line
> /lib64/libpthread.so.0: could not read symbols: Invalid operation
> collect2: ld returned 1 exit status
> make[3]: *** [librados-config] Error 1
I filed a bug under http://tracker.newdream.net/issues/1797
It turns out compiling works if you call configure with
LIBS="-lpthread" ./configure
Guido
prev parent reply other threads:[~2011-12-09 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:19 Build fails on Fedora 14 on linking librados-config Guido Winkelmann
2011-12-09 15:17 ` Guido Winkelmann [this message]
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=1494963.dggp1jPvU4@pc10 \
--to=guido-ceph@thisisnotatest.de \
--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.