Skip to content

fix(ci): scope -Wno-error=maybe-uninitialized to gcc only in build workflow - #72

Merged
volschin merged 1 commit into
mainfrom
claude/fix-build-workflow-UuxSK
Mar 28, 2026
Merged

fix(ci): scope -Wno-error=maybe-uninitialized to gcc only in build workflow#72
volschin merged 1 commit into
mainfrom
claude/fix-build-workflow-UuxSK

Conversation

@volschin

Copy link
Copy Markdown
Collaborator

Clang does not recognise -Wmaybe-uninitialized and rejects
-Wno-error=maybe-uninitialized as an unknown warning option, which
becomes a hard error under -Werror. The suppression is only needed for
GCC 14 false positives in aes.c; clang builds aes.c cleanly without it.

Switch the build matrix from a simple cc list to matrix.include entries
so each compiler can carry its own extra_cflags.

https://claude.ai/code/session_012GUFo63miXVwTirEo4ApxZ

…rkflow

Clang does not recognise -Wmaybe-uninitialized and rejects
-Wno-error=maybe-uninitialized as an unknown warning option, which
becomes a hard error under -Werror.  The suppression is only needed for
GCC 14 false positives in aes.c; clang builds aes.c cleanly without it.

Switch the build matrix from a simple cc list to matrix.include entries
so each compiler can carry its own extra_cflags.

https://claude.ai/code/session_012GUFo63miXVwTirEo4ApxZ
@volschin
volschin merged commit a10cf4c into main Mar 28, 2026
8 checks passed
@volschin
volschin deleted the claude/fix-build-workflow-UuxSK branch March 28, 2026 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants