CEPH filesystem development
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>,
	Sage Weil <sage@newdream.net>
Subject: Clang complains about mismatiching types.
Date: Sat, 18 Feb 2017 23:52:48 +0100	[thread overview]
Message-ID: <5ad4a660-692c-130e-7dcd-89fd1565c19a@digiware.nl> (raw)

I "fixed" the the bluestore inclusion, but hten still run into this type
mismatch in Clang.

--WjW

In file included from
/home/jenkins/workspace/ceph-master/src/osd/OSDMapMapping.cc:4:
In file included from
/home/jenkins/workspace/ceph-master/src/osd/OSDMapMapping.h:9:
/usr/include/c++/v1/map:820:5: error: static_assert failed
"Allocator::value_type must be same type as value_type"
    static_assert((is_same<typename allocator_type::value_type,
value_type>::value),
    ^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/jenkins/workspace/ceph-master/src/osd/OSDMapMapping.h:242:49:
note: in instantiation of template class 'std::__1::map<int,
OSDMapMapping::PoolMapping, std::__1::less<int>,
mempool::pool_allocator<mempool::pool_index_t::mempool_osdmap_mapping,
std::__1::pair<int, OSDMapMapping::PoolMapping> > >' requested here
  mempool::osdmap_mapping::map<int,PoolMapping> pools;
                                                ^
1 error generated.
gmake[2]: *** [src/CMakeFiles/common-objs.dir/build.make:1992:
src/CMakeFiles/common-objs.dir/osd/OSDMapMapping.cc.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
Scanning dependencies of target rbd_test_mock
[ 21%] Building CXX object src/librbd/CMakeFiles/rbd_api.dir/librbd.cc.o
[ 22%] Building CXX object
src/test/librbd/CMakeFiles/rbd_test.dir/test_fixture.cc.o
[ 22%] Linking

                 reply	other threads:[~2017-02-20  0:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5ad4a660-692c-130e-7dcd-89fd1565c19a@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /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