make install: Error: GOBIN is not set

[tttoad]

Bug Report

What did you do?

Execution make install

What did you expect to see?

Compile the executable binary.

What did you see instead? Under which circumstances?

Error: GOBIN is not set
make: *** [install] Error 1

Environment

Operator type:

Kubernetes cluster type:

go version go1.23.4 darwin/arm64

Possible Solution

Remove code:

	@if [ -z "$(GOBIN)" ]; then \
		echo "Error: GOBIN is not set"; \
		exit 1; \
	fi

Check GOBIN is not invalid. This is empty by default. go installl installs the program in path $GOPATH/bin by default.

#6627 I think the author of this issue did not add $GOPATH/bin to the $PATH, leading him to believe that it was not installed.

Additional context

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/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-sigs/prow repository.