Project

General

Profile

Bug #48988

asio compilation failures with boost >= 1.74

Added by Casey Bodley 5 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

from fedora build log for ceph 15.2.8: https://kojipkgs.fedoraproject.org//work/tasks/993/60470993/build.log

In file included from /builddir/build/BUILD/ceph-15.2.8/src/rgw/rgw_dmclock_async_scheduler.h:18,
                 from /builddir/build/BUILD/ceph-15.2.8/src/test/rgw/test_rgw_dmclock_scheduler.cc:18:
/builddir/build/BUILD/ceph-15.2.8/src/common/async/completion.h: In instantiation of 'void ceph::async::detail::CompletionImpl<Executor1, Handler, T, Args>::destroy_defer(std::tuple<Args ...>&&) [with Executor1 = boost::asio::io_context::basic_executor_type<std::allocator<void>, 0>; Handler = boost::asio::detail::coro_handler<boost::asio::executor_binder<void (*)(), boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > > >, crimson::dmclock::PhaseType>; T = ceph::async::AsBase<rgw::dmclock::Request>; Args = {boost::system::error_code, crimson::dmclock::PhaseType}]':
/builddir/build/BUILD/ceph-15.2.8/src/common/async/completion.h:188:8:   required from here
/builddir/build/BUILD/ceph-15.2.8/src/common/async/completion.h:194:29: error: 'boost::asio::executor_work_guard<boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > >, void>::executor_type' {aka 'class boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > >'} has no member named 'defer'; did you mean 'prefer'?
  194 |     w.second.get_executor().defer(std::move(f), alloc2);
      |     ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
      |     prefer

probably effects rgw_asio_frontend.cc as well


Related issues

Copied to rgw - Backport #49030: pacific: asio compilation failures with boost >= 1.74 Resolved
Copied to rgw - Backport #49031: octopus: asio compilation failures with boost >= 1.74 Resolved

History

#1 Updated by Casey Bodley 5 months ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 39065

#2 Updated by Casey Bodley 5 months ago

  • Backport changed from octopus to pacific, octopus

#3 Updated by Kefu Chai 5 months ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Backport Bot 5 months ago

  • Copied to Backport #49030: pacific: asio compilation failures with boost >= 1.74 added

#5 Updated by Backport Bot 5 months ago

  • Copied to Backport #49031: octopus: asio compilation failures with boost >= 1.74 added

#6 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF