-
Notifications
You must be signed in to change notification settings - Fork 173
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
make需要到github上下载依赖包 #47
Comments
成了死循环了 |
可否在release中传一个编译好的二进制包啊 |
配置了代理,但还是 make -C local VERSION=v0.5.0-beta.1 CC=gcc CXX=g++ AR=ar
make[1]: 进入目录“/root/code/graftcp/local”
go build -ldflags "-s -w -X main.version=v0.5.0-beta.1" ./cmd/graftcp-local
go: github.com/jedisct1/dlog@v0.0.0-20210101122416-354ffe815216: Get "https://proxy.golang.org/github.com/jedisct1/dlog/@v/v0.0.0-20210101122416-354ffe815216.mod": dial tcp 142.251.42.241:443: connect: connection refused
go: downloading github.com/jedisct1/dlog v0.0.0-20210101122416-354ffe815216
go: downloading github.com/kardianos/service v1.2.0
go: downloading golang.org/x/net v0.0.0-20210614182718-04defd469f4e
go: github.com/jedisct1/dlog@v0.0.0-20210101122416-354ffe815216: Get "https://proxy.golang.org/github.com/jedisct1/dlog/@v/v0.0.0-20210101122416-354ffe815216.mod": dial tcp 142.251.42.241:443: connect: connection refused
make[1]: *** [Makefile:28:graftcp-local] 错误 1
make[1]: 离开目录“/root/code/graftcp/local”
make: *** [Makefile:71:local/graftcp-local] 错误 2 |
试了下, 这个mod是可以正常访问的 [master1 root ~/code/graftcp]# curl https://proxy.golang.org/github.com/jedisct1/dlog/@v/v0.0.0-20210101122416-354ffe815216.mod
module github.com/jedisct1/dlog
go 1.15
require (
github.com/hashicorp/go-syslog v1.0.0
golang.org/x/sys v0.0.0-20201231184435-2d18734c6014 |
现在 release 只打包了 deb 和 arch 的包。这里要自己编译的话可以把 GOPROXY 设置成内地比较方便访问的 https://goproxy.cn 。也可以切换到 v0.3.1 之前的 vendor 方式的版本。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
系统版本声明: Rocky Linu8.4(Centos8.4)
大佬,这是个死循环啊.我是因为无法正常拉去强外包才来安装graftcp,现在安装graftcp又要从墙外拉取依赖包......
The text was updated successfully, but these errors were encountered: