From: "Jim Schutt" <jaschut@sandia.gov>
To: Tommi Virtanen <tommi.virtanen@dreamhost.com>
Cc: Simon Tian <aixt2006@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: compile error for ceph-0.28.*.tar.gz
Date: Tue, 31 May 2011 11:52:35 -0600 [thread overview]
Message-ID: <4DE52AE3.9020900@sandia.gov> (raw)
In-Reply-To: <20110531172458.GA12733@dreamer>
Tommi Virtanen wrote:
> On Tue, May 31, 2011 at 02:23:10PM +0800, Simon Tian wrote:
>> hi folks,
>>
>> When I make ceph after ./configure, error comes both in 0.28.1
>> and 0.28.2 like bellow:
>>
>> ./include/encoding.h:294: error: no matching function for call to
>> ?.ecode(PG::Log::Entry&, ceph::buffer::list::iterator&)?
>> ./include/encoding.h:42: note: candidates are: void decode(__u8&,
>> ceph::buffer::list::iterator&)
>> ... ...
>>
>> ./include/encoding.h:406: error: no matching function for call to
>> ?.ncode(const PG::Missing::item&, ceph::buffer::list&)?
>> ./include/encoding.h:42: note: candidates are: void encode(const
>> __u8&, ceph::bufferlist&)
>> ... ...
>>
>>
>> I just download them from http://ceph.newdream.net/download/ceph-0.28.*.tar.gz
>
> I just built ceph-0.28.2 from the tarball, with ./configure && make,
> and had no problems.
>
> What operating system and version are you trying to build it on?
>
> Does the output really say "?.ecode" and "?.ncode"? Those seem really
> odd. Can this machine successfully compile bigger projects, e.g. the
> Linux kernel? That's a good general test of hardware reliability..
>
FWIW, I believe I saw such errors on RHEL 5 due to it having
boost v1.33.1, while Ceph needs v1.34 or newer to get statechart.
-- Jim
next prev parent reply other threads:[~2011-05-31 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 6:23 compile error for ceph-0.28.*.tar.gz Simon Tian
2011-05-31 17:24 ` Tommi Virtanen
2011-05-31 17:52 ` Jim Schutt [this message]
2011-05-31 18:48 ` Tommi Virtanen
2011-06-01 9:46 ` Simon Tian
2011-06-01 15:42 ` Tommi Virtanen
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=4DE52AE3.9020900@sandia.gov \
--to=jaschut@sandia.gov \
--cc=aixt2006@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=tommi.virtanen@dreamhost.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 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.