-
Notifications
You must be signed in to change notification settings - Fork 7k
[berkeleydb] Fix build error with Visual Studio 16.7.0 #12870
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
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
I don't know why there were the linux failures; it looks like an incorrectly declared dependency, but when I try myself the problem doesn't repro. Just going to try rerun...
|
Well now it passed ¯_(ツ)_/¯ |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks for your contribution! I merged even though this was marked draft because it is blocking the infrastructure update to 16.7. |
@BillyONeal @LilyWangL Thank you, works like before. Have a great weekend. |
a104cae Update the vcpkg checkout commit ID in appveyor config. (Aaron Clauson) Pull request description: A recent appveyor vm update broke the build of the `berkeleydb` vcpkg dependency, see #19839. The temporary resolution was to switch back to the previous appveyor vm. This PR updates the pegged vcpkg commit ID to the most recent commit as of 31 Aug 2020. That commit ID has been tested against the latest appveyor vm and is able to build Bitcoin Core successfully. The vcpkg bump includes a [patch](microsoft/vcpkg#12870) to the `berkeleydb` build config which allows it to be built on the latest appveyor vm. ACKs for top commit: MarcoFalke: Concept ACK a104cae Tree-SHA512: 6d363d1615c51bb3d4b324eb96d53950648fc97fc81ffaef91ee6e92f1336776d150d89f6e859f354ee75ce66afcef07aa19ed39b725dbb3f47ba67d26e111db
Describe the pull request
Due to
berkeleydb
defining a function-like macroatomic_init
of the same name as a standard library,berkeleydb
build failed with Visual Studio 16.7.0. Adding patch to rename macroatomic_init
, this will fix this issue temporarily.No
Yes