Cannot build on darwin_amd64

[kubernetes]

Cannot build on darwin_amd64

[ialidzhikov]

Workarounded by running local container with

docker run --rm -v ${GOPATH}/src:/go/src -it golang:1.13.4 bash

and setting up everything here.

[mikedanese]

This is probably because we are building with boringcrypto and haven't added a release for darwin.

cloud-provider-gcp/WORKSPACE

Lines 45 to 51 in ef10a68

	go_download_sdk(
	name = "go_sdk",
	sdks = {
	"linux_amd64": ("go1.13.1b4.linux-amd64.tar.gz", "70be1bae05feb67d0560f39767e80707343d96554c5a611fbb93b04ce5913693"),
	},
	urls = ["https://storage.googleapis.com/go-boringcrypto/{}"],
	)

[awly]

Looks like https://storage.googleapis.com/go-boringcrypto/ doesn't provide darwin releases at all.

Interestingly, this works for me (on a linux host):

 bazel build --platforms=@io_bazel_rules_go//go/toolchain:darwin_amd64 //cmd/gcp-controller-manager/...

It's also odd that your error message says: invalid registered toolchain '@go_sdk//:go_android_amd64': no such package '@go_sdk//': unsupported platform darwin_amd64 - where did go_androind_amd64 come from?

[ialidzhikov]

I can confirm that removing

cloud-provider-gcp/WORKSPACE

Lines 45 to 51 in ef10a68

	go_download_sdk(
	name = "go_sdk",
	sdks = {
	"linux_amd64": ("go1.13.1b4.linux-amd64.tar.gz", "70be1bae05feb67d0560f39767e80707343d96554c5a611fbb93b04ce5913693"),
	},
	urls = ["https://storage.googleapis.com/go-boringcrypto/{}"],
	)

allows building on darwin_amd64.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.