-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazel 4.0.0 does not work on MacOS #1902
Comments
We can see the old clang could cause this though: bazelbuild/bazel#12905 |
The path to Xcode was
Then it was upgraded as expected.
But still I am facing the original issue... |
Probably, the reason why it still fails even though clang is updated is wrapped_clang is made of the old one. I assumed it from the skimming the log:
The clang under this directory (/Applications/Xcode.app/Contents/Developer) is old one (v11.0.0). So I'm guessing Bazel still refers the old one. |
This reverts commit 3b9d3e6. **What this PR does / why we need it**: From #1901 #1902 can take a little bit long time. So to workaround we can revert it. **Which issue(s) this PR fixes**: Fixes # **Does this PR introduce a user-facing change?**: <!-- If no, just write "NONE" in the release-note block below. --> ```release-note NONE ``` This PR was merged by Kapetanios.
/assign @nakabonne |
**What this PR does / why we need it**: Finally I won the game. **Which issue(s) this PR fixes**: Fixes #1902 **Does this PR introduce a user-facing change?**: <!-- If no, just write "NONE" in the release-note block below. --> ```release-note NONE ``` This PR was merged by Kapetanios.
What would you like to be added:
After bumping Bazel to 4.0.0,
make build
failed leaving this clang log:error: unknown argument: '-fdebug-compilation-dir'
Entire log is here:
I tried with bazelisk installed not only
go get
butbrew
. But both were the same.clang version:
Why is this needed:
The text was updated successfully, but these errors were encountered: