[Bug 251271] net-p2p/openethereum: fails to build with clang10
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Nov 20 14:36:03 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251271
Bug ID: 251271
Summary: net-p2p/openethereum: fails to build with clang10
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ale at FreeBSD.org
Reporter: mikael at FreeBSD.org
Assignee: ale at FreeBSD.org
Flags: maintainer-feedback?(ale at FreeBSD.org)
In file included from
/wrkdirs/usr/ports/net-p2p/openethereum/work/openethereum-3.1.0/cargo-crates/parity-rocksdb-sys-0.5.6/rocksdb/utilities/backupable/backupable_db.cc:16:
/wrkdirs/usr/ports/net-p2p/openethereum/work/openethereum-3.1.0/cargo-crates/parity-rocksdb-sys-0.5.6/rocksdb/util/channel.h:35:33:
error: no matching constructor for initialization of
'std::lock_guard<std::mutex>'
std::lock_guard<std::mutex> lk(lock_);
^ ~~~~~
/usr/include/c++/v1/__mutex_base:90:14: note: candidate constructor not
viable: 1st argument ('const std::mutex') would lose const qualifier
explicit lock_guard(mutex_type& __m)
_LIBCPP_THREAD_SAFETY_ANNOTATION(acquire_capability(__m))
^
/usr/include/c++/v1/__mutex_base:100:5: note: candidate constructor not
viable: no known conversion from 'const std::mutex' to 'const
std::__1::lock_guard<std::__1::mutex>' for 1st argument
lock_guard(lock_guard const&) _LIBCPP_EQUAL_DELETE;
^
/usr/include/c++/v1/__mutex_base:94:5: note: candidate constructor not
viable: requires 2 arguments, but 1 was provided
lock_guard(mutex_type& __m, adopt_lock_t)
_LIBCPP_THREAD_SAFETY_ANNOTATION(requires_capability(__m))
^
1 error generated.
probably fixed with:
https://github.com/cockroachdb/rocksdb/pull/79
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list