Skip to content

Conversation

@pokowaka
Copy link
Contributor

This fixes an issue where g++ would be used to compile c files.

Verify compilation of a C file that uses C11 atomics, which currently
fails due to the toolchain incorrectly including C++ headers when
compiling a C file.

This test documents the existing issue where C files pick up C++
include paths, resulting in build failures. It also adds the new
target to the `arm_linux_test` build test exposing the issue.
@pokowaka
Copy link
Contributor Author

Looks like the build failures on mac are unrelated to this change, but due to infra structure issues.

@pokowaka
Copy link
Contributor Author

Note, this will fix #83

Remove the hardcoded `gcc_tool = "g++"` argument from the
`arm_none_eabi_toolchain` definition.

This explicit setting was incorrectly forcing the C compiler to use
the C++ frontend (g++) for C files, which led to compilation failures
when attempting to use C-specific features like C11 atomics.

By removing this argument, Bazel is allowed to correctly infer the
appropriate C compiler (`gcc`) for C sources and the C++ compiler
(`g++`) for C++ sources, resolving the build issue documented in the
previous test commit.

Fixes: 83
@hexdae
Copy link
Owner

hexdae commented Dec 5, 2025

Thank you for fixing the examples

@hexdae hexdae merged commit 76837cb into hexdae:master Dec 5, 2025
6 checks passed
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