[Bug 224185] [cmake] net/ceph and net/ceph-devel: fails to build with boost 1.66
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Dec 28 20:09:18 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224185
--- Comment #17 from Jan Beich <jbeich at FreeBSD.org> ---
Comment on attachment 188925
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188925
Help find Boost
After applying the patch Boost 1.66 is detected fine but the build is still
busted. Ceph bundles Beast library which is now part of Boost, not sure if
there're any API differences.
11.1 amd64 + net/ceph - https://ptpb.pw/tX2s
11.1 amd64 + net/ceph-devel - https://ptpb.pw/1XaE
12.0 amd64 + net/ceph - https://ptpb.pw/a4Qb
12.0 amd64 + net/ceph-devel - https://ptpb.pw/ZjKR
In file included from src/rgw/rgw_asio_frontend.cc:13:
In file included from src/rgw/../Beast/include/beast/http/read.hpp:12:
src/rgw/../Beast/include/beast/core/async_completion.hpp:73:11: error: no
matching constructor for initialization of
'boost::asio::async_result<handler_type>' (aka
'async_result<coro_handler<boost::asio::executor_binder<void (*)(),
boost::asio::executor>, unsigned long> >')
, result(handler)
^ ~~~~~~~
src/rgw/../Beast/include/beast/http/impl/async_read.ipp:584:40: note: in
instantiation of member function
'beast::async_completion<boost::asio::basic_yield_context<boost::asio::executor_binder<void
(*)(), boost::asio::executor> >, void (boost::system::error_code, unsigned
long)>::async_completion' requested here
void(error_code, std::size_t)> completion{handler};
^
src/rgw/../Beast/include/beast/http/impl/async_read.ipp:650:20: note: in
instantiation of function template specialization
'beast::http::detail::async_read_some<boost::asio::basic_stream_socket<boost::asio::ip::tcp>,
beast::basic_flat_streambuf<std::__1::allocator<char> >, true,
beast::http::message_parser<true, rgw::asio::streaming_body,
beast::http::basic_fields<std::__1::allocator<char> > >,
boost::asio::basic_yield_context<boost::asio::executor_binder<void (*)(),
boost::asio::executor> > >' requested here
return detail::async_read_some(stream, dynabuf, parser,
^
src/rgw/rgw_asio_frontend.cc:86:33: note: in instantiation of function template
specialization
'beast::http::async_read_some<boost::asio::basic_stream_socket<boost::asio::ip::tcp>,
beast::basic_flat_streambuf<std::__1::allocator<char> >, true, true,
beast::http::message_parser<true, rgw::asio::streaming_body,
beast::http::basic_fields<std::__1::allocator<char> > >,
boost::asio::basic_yield_context<boost::asio::executor_binder<void (*)(),
boost::asio::executor> > >' requested here
auto bytes = beast::http::async_read_some(socket, buffer, parser,
yield[ec]);
^
/usr/local/include/boost/asio/async_result.hpp:50:7: note: candidate
constructor (the implicit copy constructor) not viable: no known conversion
from 'handler_type' (aka 'coro_handler<boost::asio::executor_binder<void (*)(),
boost::asio::executor>, unsigned long>') to 'const
boost::asio::async_result<boost::asio::detail::coro_handler<boost::asio::executor_binder<void
(*)(), boost::asio::executor>, unsigned long>, void>' for 1st argument
class async_result
^
/usr/local/include/boost/asio/impl/spawn.hpp:316:12: note: candidate
constructor not viable: no known conversion from 'handler_type' (aka
'coro_handler<boost::asio::executor_binder<void (*)(), boost::asio::executor>,
unsigned long>') to 'typename detail::coro_async_result<executor_binder<void
(*)(), executor>, void>::completion_handler_type &' (aka
'coro_handler<boost::asio::executor_binder<void (*)(), boost::asio::executor>,
void> &') for 1st argument
explicit async_result(
^
1 error generated.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kde-freebsd
mailing list