-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation failure with 1.83 #70
Comments
To fix, you'd need to patch boost.function and boost.signals2 from development, or wait for boost 1.84, or compile against a version of the c++ standard which is not c++20 |
@fmhess thanks, could you point me to the commits that purport to fix this? I can try them locally, since boost 1.84 is still some time away |
@fmhess ping. Could you please have a look, which commits are needed for fix? Thank you! |
Ping |
Unfortunately, the code still fails with boost 1.84 😢 |
I can confirm, that appliying those patches against boost-1.83 (haven't tested boost-1.84), makes it compiling again. |
Bug: boostorg/signals2#70 Bug: https://bugs.gentoo.org/912309 Signed-off-by: David Seifert <soap@gentoo.org>
We're seeing one specific failure of Boost.Signals2 in our Gentoo package tree: Bug 912309
This code used to compile fine under Boost 1.82. The offending line is:
here
stanzaChannel_->onPresenceReceived
is of typeboost::signals2::signal<void (std::shared_ptr<Message>)>
and theonPresenceReceived
argument on the right-hand side is of typeboost::signals2::signal<void (std::shared_ptr<Message>)>
too. The error boils down to an ambiguous overloadDo you have any ideas or guidance that could help us fix this locally? Upstream seems mostly gone, and this is the last bug for us in Boost 1.83. Paging in @pdimov who recommended I file a bug here.
The text was updated successfully, but these errors were encountered: