-
Notifications
You must be signed in to change notification settings - Fork 32
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 build error: missing ziphash #32
Comments
Hi @onethirdzero . I am facing the same issue but I am not sure what is the workaround you carried out. Can you describe what you did for the workaround |
Hey @sharath-sri-chellappa, here's the exact diff of what I did: $ g --no-pager diff
diff --git a/Makefile b/Makefile
index 49e108e..ad5c928 100644
--- a/Makefile
+++ b/Makefile
@@ -46,7 +46,7 @@ endef
all: format build
.PHONY: build
-build: check-git deps $(PROMU)
+build: check-git $(PROMU)
@echo ">> building binaries $(GOBIN)"
@$(PROMU) build --prefix $(PREFIX) Then: $ make build
>> building binaries /home/foo/go/bin
> thanosbench
## Success! |
Oh Thank you. However I find the following issues now - |
That looks like a Go tooling issue. Which version of Go are you using?
It also looks like you're trying to run |
This workaround did not work in my case. See the ugly workaround I used. |
I have the same error when converting the module to go workspace. It seams the go workspace is not mature enough. My guess is that it requires the tool to be compiled with go workspace in order to use it with other go workspace projects. Findings: umee-network/umee#1056 |
Hi, I'm having trouble building from source. I'm using Go
1.15.6
.I've tried clearing the module cache (
~/go/pkg/mod/cache
) and doinggo mod download && make build
. No dice. I get the same errors.The only related discussion I could find on ziphashes was this Stack Overflow question, which seems to suggest that something happened in these dependencies that's causing the ziphash not to be created. Or maybe it's a bug in the Go tooling.
I'm currently working around this by removing the
deps
dependency in thebuild
target. That allows the build to succeed.The text was updated successfully, but these errors were encountered: