-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 with XCode 11.3 #12905
Labels
Comments
This was referenced Jan 26, 2021
arunkumar9t2
pushed a commit
to arunkumar9t2/bazel
that referenced
this issue
Feb 9, 2021
This reverts commit 0cb8757. This flag isn't supported by Xcode 11.2, which is the newest available version for macOS 10.14 bazelbuild#12354 (comment) Fixes bazelbuild#12905 Closes bazelbuild#12882. PiperOrigin-RevId: 355126529
Found this problem too |
FYI to workaround this now you can pass |
Thank you, it works as usual now |
philwo
pushed a commit
that referenced
this issue
Mar 15, 2021
This reverts commit 0cb8757. This flag isn't supported by Xcode 11.2, which is the newest available version for macOS 10.14 #12354 (comment) Fixes #12905 Closes #12882. PiperOrigin-RevId: 355126529
philwo
pushed a commit
that referenced
this issue
Mar 15, 2021
This reverts commit 0cb8757. This flag isn't supported by Xcode 11.2, which is the newest available version for macOS 10.14 #12354 (comment) Fixes #12905 Closes #12882. PiperOrigin-RevId: 355126529
haberman
added a commit
to haberman/upb
that referenced
this issue
Apr 16, 2021
This works around: bazelbuild/bazel#12905
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This line here:
bazel/tools/osx/crosstool/cc_toolchain_config.bzl
Line 5369 in 8959dff
introduced in this commit:
0cb8757
causes Bazel 4.0.0 to not work with XCode 11.3 because it does not support the
-fdebug-compilation-dir
flag:clang --version
Apple clang version 11.0.0 (clang-1100.0.33.16)
clang: error: unknown argument: '-fdebug-compilation-dir'
That version of XCode is still in pretty common use.
The text was updated successfully, but these errors were encountered: