From: Chen Baozi <baozich@gmail.com>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Gary Lowell <gary.lowell@inktank.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Fail to build the latest ceph tree on Fedora 17
Date: Sun, 18 Nov 2012 11:55:49 +0800 [thread overview]
Message-ID: <20121118035549.GA22651@cbz-workstation> (raw)
In-Reply-To: <CAC-hyiH31rfvnzNZnWusCTXBGLsA4o2WeCDnAwMv=v8A9ELLfA@mail.gmail.com>
On Sat, Nov 17, 2012 at 01:20:51PM -0800, Yehuda Sadeh wrote:
> On Sat, Nov 17, 2012 at 3:29 AM, Chen Baozi <baozich@gmail.com> wrote:
> > Hi, everyone.
> >
> > I was tring to build the latest ceph tree on my fedora 17 box.
> > However, there is an error message when linking radosgw as following:
> >
> > CXXLD radosgw
> > /usr/bin/ld: radosgw-rgw_resolve.o: undefined reference to symbol
> > '__res_nquery@@GLIBC_2.2.5'
> > /usr/bin/ld: note: '__res_nquery@@GLIBC_2.2.5' is defined in DSO
> > /lib64/libresolv.so.2 so try adding it to the linker command line
> > /lib64/libresolv.so.2: could not read symbols: Invalid operation
> > collect2: error: ld returned 1 exit status
> > make[3]: *** [radosgw] Error 1
> > make[3]: Leaving directory `/home/cbz/src/ceph/src'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/home/cbz/src/ceph/src'
> > make[1]: *** [all] Error 2
> > make[1]: Leaving directory `/home/cbz/src/ceph/src'
> > make: *** [all-recursive] Error 1
> >
> > I've also tried build the version 0.53 which is checked out from
> > fedora's pkg repo. And it can pass the building process without this
> > error.
> >
> > Any suggestion?
>
> Linking with libresolv failed. Garry, any idea?
I've tried to add "LIBS=-lresolv" when doing "./configure". And it works.
I'm trying to fix it from the configure.ac now.
>
> Yehuda
prev parent reply other threads:[~2012-11-18 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 11:29 Fail to build the latest ceph tree on Fedora 17 Chen Baozi
2012-11-17 21:20 ` Yehuda Sadeh
2012-11-18 3:55 ` Chen Baozi [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=20121118035549.GA22651@cbz-workstation \
--to=baozich@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gary.lowell@inktank.com \
--cc=yehuda@inktank.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox