bazel-contrib / bazel-contrib/rules_foreign_cc
BootstrapGNUMake fails with hermetic_cc_toolchain (Zig) after #1470
- Dominant language
- Starlark
- Stars
- 737
- Forks
- 270
- PR merge metrics
- No merged PRs in 30d
Description
Since #1470 (442e205), -isystem flags are embedded directly into the CC variable. With hermetic_cc_toolchain, these flags contain sandbox-absolute paths into the Bazel execution root. When ./configure tests the compiler from make.build_tmpdir/, those paths are inaccessible in the subprocess → "C compiler cannot create executables".
Workaround:
build --strategy=BootstrapGNUMake=local
build --strategy=BootstrapPkgConfig=local
Contributor guide
Research direction
Start by tracing BootstrapGNUMake and the hermetic_cc_toolchain handling around the CC variable, then reproduce the ./configure failure from make.build_tmpdir/. Compare behavior with the local-strategy workaround; done means the hermetic toolchain can run the compiler configuration without inaccessible sandbox-absolute paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- zig
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100