-
Notifications
You must be signed in to change notification settings - Fork 385
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
Gazelle fails on macOS when using apple_support
and go version 1.22+
#1793
Comments
Also, running with |
See bazel-contrib/bazel-gazelle#1793 for details.
See github/codeql@b0758fd for a workaround based on using the 1.21.9 go toolchain just for gazelle on macOS. |
I've been running into this for weeks now as well. I'm in a codebase where we must include apple_support in order to drive rules_apple, but also have some custom Gazelle functionality to support other kinds of programs. We are stuck on Go 1.21 until this is corrected, workarounds notwithstanding. The only research I've managed to do with my limited knowledge of |
Which version of Xcode are you on? I think I saw similar error messages on Slack and this was resolved by just updating to the latest version. |
I am on the latest stable release, Xcode 15.3. Using Which Slack messages are you referring to? I am here via this. |
Seems like this may be an upstream problem: uber/hermetic_cc_toolchain#171 |
This caused by the and this Slack thread: https://bazelbuild.slack.com/archives/CDBP88Z0D/p1715173028271439 |
Discovered yesterday while experimenting with Go 1.22.5 that this does not occur for me anymore. Xcode 15.4, apple_support 1.15.1, rules_go 0.48.1 and latest gazelle. Not sure it will make a difference for y'all, but maybe something upstream changed that's working for me? |
When defining this minimal
MODULE.bazel
:and creating the usual
BUILD.bazel
:then when I
bazel run //:gazelle
I getCommenting out either the
apple_support
dependency or using a lower go version works ok.If it helps, I'm running this on an M1 macOS, with bazel version 7.1.1. Funnily enough,
bazel build @gazelle//cmd/gazelle
builds ok, so it seems this is only happening when building it[for tool]
.The text was updated successfully, but these errors were encountered: