Disable CGo

[fmeum]

---

Changes are visible to end-users: yes/no

• Searched for relevant documentation and updated as needed: yes/no
• Breaking change (forces users to change their own code or config): yes/no
• Suggested release notes appear below: yes/no

Test plan

• Covered by existing test cases
• New test cases added
• Manual testing; please provide instructions so we can reproduce:

[alexeagle]

I see, thanks!

Is there any consequence for compiling the stdlib without cgo support? Is it possible to change it in rules_go instead to be "pure" so it doesn't attempt to use a cc toolchain?

(makes me wonder if --host_platform be renamed --exec_platform to match how the cfg attribute on rule declaration is changing...)

[fmeum]

Is there any consequence for compiling the stdlib without cgo support? Is it possible to change it in rules_go instead to be "pure" so it doesn't attempt to use a cc toolchain?

The non-Bazel Go toolchain also uses CGo on Linux if available and we wouldn't want to deviate from that. The differences are minor, but do affect subtle things like DNS resolution.

(makes me wonder if --host_platform be renamed --exec_platform to match how the cfg attribute on rule declaration is changing...)

I think it's named appropriately in this case as it really is the platform of the machine running bazel. Everything else should go into --extra_execution_platforms.

[alexeagle]

Nice thanks for answering :)