Gazelle fails on macOS when using `apple_support` and go version 1.22+ about bazel-gazelle

[redsun82]

Also, running with --@rules_go//go/config:pure is a workaround, but it's not ideal as I have the feeling it then runs quite slower.

[redsun82]

See github/codeql@b0758fd for a workaround based on using the 1.21.9 go toolchain just for gazelle on macOS.

[aaronsky]

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 rules_go and the Go linker is that the output from --subcommands between Go 1.21 and 1.22 is identical. As far as I know, there is more behavior within the builder wrapper that occurs before or as part of the linker being invoked, so this is probably not very illuminating.

[fmeum]

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.

[aaronsky]

I am on the latest stable release, Xcode 15.3. Using --xcode_version_config to aid in discovery.

Which Slack messages are you referring to? I am here via this.

[ewhauser]

Seems like this may be an upstream problem: uber/hermetic_cc_toolchain#171