Fix Clang-23 RC build - #2482
Draft
evantypanski wants to merge 5 commits into
Draft
Conversation
This was included transitively but should not be.
Thi `/` fix was only proper for MSVC. It broke when using an absolute path on Mac. I used `-isystem /Library/...` when testing Clang 23.1 RC.
We had a few pragmas, but this one couldn't actually be fixed by pragmas since the warning technically happened in a system include. Bleh.
evantypanski
force-pushed
the
topic/etyp/transitive-include-fix
branch
from
August 25, 2026 19:45
945b8b4 to
e68109d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
draft since I'm going to look at other stuff too (and so I make sure to come back to this), this isn't urgent.
Just tested Clang 23 RC3 and hit an error building Zeek:
Also changed this to fix some warnings, as well.
Note this fixes warnings in fiber/ - I did that as patches (see zeek/fiber#1). Unless they respond upstream to the other patch, I don't see much reason to not mildly maintain it ourselves.