-
Notifications
You must be signed in to change notification settings - Fork 923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to install at go 1.18 #816
Comments
it seems that something wrong with your environment. Can you try the command in other computer? |
I get the same thing from 2 different machines (go 1.17.8 for both)
|
go install github.com/beego/bee/v2@latest golang.org/x/sys/unix../../go/pkg/mod/golang.org/x/[email protected]/unix/syscall_darwin.1_13.go:29:3: //go:linkname must refer to declared function or variable |
Since Go 1.16 Knowing that didn't get me much farther though. Other tries failed as well: go install github.com/beego/bee/[email protected]
go: github.com/beego/bee/[email protected]: github.com/beego/[email protected]: invalid version: module contains a go.mod file, so module path must match major version ("github.com/beego/bee/v2") go install github.com/beego/bee/[email protected]
go: github.com/beego/bee/[email protected]: github.com/beego/[email protected]: invalid version: module contains a go.mod file, so module path must match major version ("github.com/beego/bee/v2") Strangely the version of beego in go.mod actually seems to be correct for 2.0.1 and 2.0.0 - but for 2.0.2 the version is wrongfully referring require (
github.com/beego/beego/v2 v2.0.1 I tried using Go 1.17.9 and 1.18.1 - no luck 🤷♂️ |
I realised there are some unmerged changes in develop: e3d0b64 These fix the issue for me. For anyone who can't wait, you can install the develop version of bee like this: |
--- I do it by this way, The problem is solved , I don't know if there are any other effects. |
mac 12.2.1
go 1.18 darwin/amd64
i tried to follow the docs, but on go 1.18 i cant use go get outside the module
and this happened.
The text was updated successfully, but these errors were encountered: