[Moving to ceph-devel] On Mon, 5 Aug 2013, huangjun wrote: > hi,all > i compiled ceph 0.61.3 on centos 5.9,the "sh autogen.sh" and > "./configure " is ok, but when i "make", an error occurs, the err log: > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h: > In function ?int rados::cls::lock::lock(librados::IoCtx*, const > std::string&, const std::string&, ClsLockType, const std::string&, const > std::string&, const std::string&, const utime_t&, uint8_t)?: > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h:83: > error: ?class __gnu_cxx::lock? is not a function, > cls/lock/cls_lock_client.cc:59: error: conflict with ?int > rados::cls::lock::lock(librados::IoCtx*, const std::string&, const > std::string&, ClsLockType, const std::string&, const std::string&, const > std::string&, const utime_t&, uint8_t)? > cls/lock/cls_lock_client.cc:62: error: in call to ?lock? > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h: > In member function ?void > rados::cls::lock::Lock::lock_shared(librados::ObjectWriteOperation*)?: > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h:83: > error: ?class __gnu_cxx::lock? is not a function, > cls/lock/cls_lock_client.cc:59: error: conflict with ?int > rados::cls::lock::lock(librados::IoCtx*, const std::string&, const > std::string&, ClsLockType, const std::string&, const std::string&, const > std::string&, const utime_t&, uint8_t)? > cls/lock/cls_lock_client.cc:181: error: in call to ?lock? > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h: > In member function ?int > rados::cls::lock::Lock::lock_shared(librados::IoCtx*, const std::string&)?: > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h:83: > error: ?class __gnu_cxx::lock? is not a function, > cls/lock/cls_lock_client.cc:59: error: conflict with ?int > rados::cls::lock::lock(librados::IoCtx*, const std::string&, const > std::string&, ClsLockType, const std::string&, const std::string&, const > std::string&, const utime_t&, uint8_t)? > cls/lock/cls_lock_client.cc:187: error: in call to ?lock? > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h: > In member function ?void > rados::cls::lock::Lock::lock_exclusive(librados::ObjectWriteOperation*)?: > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h:83: > error: ?class __gnu_cxx::lock? is not a function, > cls/lock/cls_lock_client.cc:59: error: conflict with ?int > rados::cls::lock::lock(librados::IoCtx*, const std::string&, const > std::string&, ClsLockType, const std::string&, const std::string&, const > std::string&, const utime_t&, uint8_t)? > cls/lock/cls_lock_client.cc:193: error: in call to ?lock? > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h: > In member function ?int > rados::cls::lock::Lock::lock_exclusive(librados::IoCtx*, const > std::string&)?: > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/concurrence.h:83: > error: ?class __gnu_cxx::lock? is not a function, > cls/lock/cls_lock_client.cc:59: error: conflict with ?int > rados::cls::lock::lock(librados::IoCtx*, const std::string&, const > std::string&, ClsLockType, const std::string&, const std::string&, const > std::string&, const utime_t&, uint8_t)? > cls/lock/cls_lock_client.cc:199: error: in call to ?lock? > make[3]: *** [cls_lock_client.o] Error 1 > > the gcc version is 4.1.2, does this make a difference? I suspect so. Mark Nelson successfully built on RHEL5 a while back but needed to use a newer gcc. > what should i do if i want to use ceph-fuse client on centos 5.9? must > compile the ceph? or just compile the ceph-fuse code? Right.. you only need the ceph-fuse code. 'make ceph-fuse' may do the trick. Otherwise, you'll need to just strip out the osd stuff from Makefile.am. Either way, let us know how it goes, as others would benefit from this as well! Thanks- sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
