Error: hyperkit: no bottle available! #330
Description
While installing hyperkit on mac using brew I am getting this error.
Error: hyperkit: no bottle available!
You can try to install from source with:
brew install --build-from-source hyperkit
Please note building from source is unsupported. You will encounter build
failures with some formulae. If you experience any issues please create pull
requests instead of asking for help on Homebrew's GitHub, Twitter or any other
official channels
So I ran brew install --build-from-source hyperkit and got this error,
==> Downloading https://github.com/Homebrew/homebrew-core/files/6405545/tinycorelinux_8.x.tar.gz
Already downloaded: /Users/satyaki.das/Library/Caches/Homebrew/downloads/840a6f58d851f8ac4dbfee434980e81b172cdb88593b1f5bfacf1fb074f981c5--tinycorelinux_8.x.tar.gz
==> Downloading https://github.com/moby/hyperkit/archive/v0.20200908.tar.gz
Already downloaded: /Users/satyaki.das/Library/Caches/Homebrew/downloads/c64ec9afae5c38df6a44b8ebcc74aeb71804de95b750c81c5c8a4124b4861857--hyperkit-0.20200908.tar.gz
==> opam init --disable-sandboxing --no-setup
==> opam config exec -- opam install -y uri.3.1.0 qcow.0.11.0 conduit.2.1.0 lwt.5.3.0 qcow-tool.0.11.0 mirage
==> opam config exec -- make GIT_VERSION=0.20200908
Last 15 lines from /Users/satyaki.das/Library/Logs/Homebrew/hyperkit/03.opam:
hv_vcpu_enable_native_msr(((hv_vcpuid_t) vcpuid), MSR_CSTAR, 1);
^
src/lib/vmm/intel/vmx_msr.c:215:30: error: use of undeclared identifier 'hv_vcpuid_t'
hv_vcpu_enable_native_msr(((hv_vcpuid_t) vcpuid), MSR_STAR, 1);
^
src/lib/vmm/intel/vmx_msr.c:216:30: error: use of undeclared identifier 'hv_vcpuid_t'
hv_vcpu_enable_native_msr(((hv_vcpuid_t) vcpuid), MSR_SF_MASK, 1);
^
src/lib/vmm/intel/vmx_msr.c:217:30: error: use of undeclared identifier 'hv_vcpuid_t'
hv_vcpu_enable_native_msr(((hv_vcpuid_t) vcpuid), MSR_KGSBASE, 1);
^
20 errors generated.
11 errors generated.
make: *** [build/lib/vmm/intel/vmx.o] Error 1
make: *** [build/lib/vmm/intel/vmx_msr.o] Error 1
READ THIS: https://docs.brew.sh/Troubleshooting
Any idea on why this is happening and how to solve this?