You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: resolve Rust hermiticity issue with rules_cc fork (Issue #163)
## Solution
Use fork with auto_detect parameter to disable system C++ toolchain detection.
## Changes
1. Added git_override to use avrabe/rules_cc fork with fix
- Commit: 7215331f9e53f80070dc01c4a95a0f9c53ea477b
- Branch: feature/optional-cc-toolchain-auto-detect
2. Configured cc_configure with auto_detect = False
- Prevents /usr/local/wasi-sdk from being detected
- Generates empty toolchain instead of system paths
## Test Results
✅ Build successful (605 processes)
✅ Hermiticity test PASSED (401 actions analyzed, 0 issues)
✅ No system paths in generated toolchain config
✅ No /usr/local/wasi-sdk references
## Before vs After
Before:
- 86 hermiticity issues
- Hardcoded system WASI SDK linker paths
- 43 suspicious tool references
After:
- 0 hermiticity issues
- All tools from Bazel cache
- Empty toolchain config (no system detection)
## Upstream
This uses the fork temporarily until PR is accepted upstream:
- Fork: https://github.com/avrabe/rules_cc
- RFC: avrabe/rules_cc#1
- Verified: #163Closes#163
0 commit comments