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
Boost 1.61 hides fcontext #4270
Comments
We've worked around this in our build by doing the following hack:
|
ph1's hack does not work for me on osx with brew boost 1.61.0:
|
Yeah - I double checked my config log here. It works enough to find boost using this (which I believe I was having troubles with before), but the actual context ends up linking to system v ucontexts instead because nothing actually works. Looks like this part was fixed in #4052 |
Ah! |
duplicate of #4053 ? |
ok, if that is duplicate, then this needs to be reopened. It is more than simply namespace changes. |
I've noticed 😿 |
The root problem of the include hack mentioned by @phonedph1 is a wrong boost version check, I created a pull request (#4446) to fix the include (the fcontext incompatibility itself is still there) |
@anthraxx the boost version header also needs to be included before the check. Also my hack was because the configure script wasn't picking it up properly - this part is indeed fixed now. |
@phonedph1 good spot, for me it was already defined but technically you are correct: adjusted the pull request (#4446). |
Build fails on Alpine Linux (musl libc) too with the boost 1.61.0 release notes says that "fcontext_t: no longer part of public API" so I don't know what the way forward is.
|
Fixes for this issues are merged in master (#4499) and in the re/rec-4.0.x branch (#4511). The upcoming 4.0.4 release will contains these fixes. @ncopa please try the master branch or the current pre-release tarball: https://downloads.powerdns.com/autobuilt/recursor/dist/pdns-recursor-4.0.3-8-g9e7120f.tar.bz2 |
indeed. I manually applied the changes to |
Which means Recursor cannot use Boost Context on 1.61 and up.
The text was updated successfully, but these errors were encountered: