We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I don't know if this is the right place, but I'm trying to build bettercap inside a Docker and it balks at this:
/go/pkg/mod/github.com/chifflier/nfqueue-go@v0.0.0-20170228160439-61ca646babef/nfqueue/nfqueue.go:187:29: could not determine kind of name for C.u_int16_t /go/pkg/mod/github.com/chifflier/nfqueue-go@v0.0.0-20170228160439-61ca646babef/nfqueue/nfqueue.go:269:35: could not determine kind of name for C.u_int32_t /go/pkg/mod/github.com/chifflier/nfqueue-go@v0.0.0-20170228160439-61ca646babef/nfqueue/nfqueue.go:257:27: could not determine kind of name for C.u_int8_t
My host OS runs go 1.18.5 and builds fine, but the Docker has 1.19.2 and I guess has the issue?
The text was updated successfully, but these errors were encountered:
I have a similar issue; see pentoo/pentoo-overlay#1545 and bettercap/bettercap#1070
Sorry, something went wrong.
No branches or pull requests
I don't know if this is the right place, but I'm trying to build bettercap inside a Docker and it balks at this:
github.com/chifflier/nfqueue-go/nfqueue
/go/pkg/mod/github.com/chifflier/nfqueue-go@v0.0.0-20170228160439-61ca646babef/nfqueue/nfqueue.go:187:29: could not determine kind of name for C.u_int16_t
/go/pkg/mod/github.com/chifflier/nfqueue-go@v0.0.0-20170228160439-61ca646babef/nfqueue/nfqueue.go:269:35: could not determine kind of name for C.u_int32_t
/go/pkg/mod/github.com/chifflier/nfqueue-go@v0.0.0-20170228160439-61ca646babef/nfqueue/nfqueue.go:257:27: could not determine kind of name for C.u_int8_t
My host OS runs go 1.18.5 and builds fine, but the Docker has 1.19.2 and I guess has the issue?
The text was updated successfully, but these errors were encountered: