Skip to content
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 compile Starport on FreeBSD #2042

Closed
moonshine-cc opened this issue Jan 31, 2022 · 2 comments
Closed

Unable to compile Starport on FreeBSD #2042

moonshine-cc opened this issue Jan 31, 2022 · 2 comments
Labels

Comments

@moonshine-cc
Copy link

I have tried to compile Starport v0.19.3 on FreeBSD 13.0-RELEASE-p6, but it aborts with the following error:

$ go version
go version go1.17.5 freebsd/amd64

$ gmake build
Building Starport...
# github.com/tendermint/starport/starport/pkg/nodetime/data
starport/pkg/nodetime/data/data.go:5:9: undefined: binaryCompressed
# github.com/tendermint/starport/starport/pkg/protoc-gen-dart/data
starport/pkg/protoc-gen-dart/data/data.go:5:9: undefined: binary
# github.com/tendermint/starport/starport/pkg/protoc/data
starport/pkg/protoc/data/data.go:19:9: undefined: binary
# github.com/docker/docker/pkg/system
../../go/pkg/mod/github.com/docker/[email protected]+incompatible/pkg/system/mknod.go:12:19: cannot use dev (type int) as type uint64 in argument to unix.Mknod
gmake: *** [Makefile:22: build] Error 2

There is no docker on FreeBSD and I don't understand, why it is necessary for compiling the binary.
Can docker support be disabled?

No idea about the other errors.

P.S. I'm not a programmer or developer, just a user. I was able to compile the daemons (written in golang) of various blockchain project that use the Cosmos-SDK, but now I have stumbled across the first one that uses Starport for building.

@4coffeeihadbreakfast
Copy link

it looks like this is a known issue within a dependency used by this project https://github.com/fsouza/go-dockerclient//issues/878 moby/moby#42849 hopefully it will be addressed in a timely manner.

@aljo242
Copy link
Contributor

aljo242 commented Oct 28, 2022

It looks like the issue has been fixed here! Please let us know if the issue persists by opening a new one

@aljo242 aljo242 closed this as completed Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants