Fix header guard definition in system_fs026.h which breaks builds with gcc 15+#440
Merged
fpoussin merged 1 commit intoChibiOS:chibios-21.11.xfrom Apr 8, 2026
Merged
Conversation
Contributor
Author
|
I don't think the error is related to my PR change as other PRs are failing the same way. |
Member
|
Thank you! |
Contributor
Author
|
Hi @fpoussin , any expected date to have this updated on QMK? |
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
2 participants
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.
This pull request corrects a preprocessor macro definition in the
system_fs026.hheader file to ensure the correct include guard is used.__SYSTEM_ES32F0283_H__to__SYSTEM_FS026_H__insystem_fs026.hto prevent potential issues with recursive inclusion or incorrect header protection.The
-Werror=header-guarddiagnostic (which promotes the mismatched #ifndef/#define guard to a hard error) was introduced/tightened in GCC 15. On GCC 14 the mismatch is silently ignored, on GCC 15 it becomes a build-breaking error.