-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
libprotobuf v4.23.0 #156
libprotobuf v4.23.0 #156
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
So this fails with:
Though we're using abseil 20230125.2 and not 20230125.3 like protobuf, the difference is only one commit, and we've backported that one. So while we've got abseil in the error log, I doubt that it has something to do with the unvendoring. |
Very unusually, linux-64 builds are the only ones that are failing, while everything else passes. So it must be related to the test targets (which we're not building on linux-aarch&ppc), and it's specific to GCC (i.e. doesn't appear with Clang & MSVC). Any insights you might have on this would be much appreciated @coryan! :) |
I think you are running into the problems fixed by protocolbuffers/protobuf@ae7ec4e. It only affects GCC because only GCC defaults to C++17 at the moment (that is a guess). That patch will be part of 23.1: |
That looks bang on, thanks a lot!
I switched to C++17 globally in #144 already, but as the commit message mentions it seems a GCC issue |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
Based on #155, will be rebased once that's in.Closes #157