Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Makefile: Set ARCH in GOPATH not set mode #1225

Merged
merged 1 commit into from
Feb 12, 2019

Conversation

teawater
Copy link
Member

In GOPATH not set mode got:
make: go: Command not found
Makefile:38: arch/-options.mk: No such file or directory
make: go: Command not found
Makefile:237: *** "ERROR: No hypervisors known for architecture (looked for: firecracker qemu)". Stop.

The root cause is GOPATH not set mode is not set ARCH.
Set it to fix the issue.

Fixes: #1224

Signed-off-by: Hui Zhu [email protected]

In GOPATH not set mode got:
make: go: Command not found
Makefile:38: arch/-options.mk: No such file or directory
make: go: Command not found
Makefile:237: *** "ERROR: No hypervisors known for architecture  (looked for: firecracker qemu)".  Stop.

The root cause is GOPATH not set mode is not set ARCH.
Set it to fix the issue.

Fixes: kata-containers#1224

Signed-off-by: Hui Zhu <[email protected]>
@teawater
Copy link
Member Author

/test

@grahamwhaley
Copy link
Contributor

Is this related to the recently merged #1168 ?
/cc @jodh-intel

@jodh-intel
Copy link
Contributor

Looks like it might be. But I'm confused - the following wftm:

$ (unset GOPATH; make)

@teawater
Copy link
Member Author

@jodh-intel GOPATH not set mode is for "sudo make install"

@teawater
Copy link
Member Author

jenkins-ci-ARM-ubuntu-18-04 fail relate with #1202.
jenkins-ci-ubuntu-16-04-firecracker fail relate with #1221.
So I think these 2 fails do not relate with this pr.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GOPATH not set mode is not set ARCH
6 participants