-
I tried to build ebpf with bpf2go on both the x86 and arm platforms but failed with arm because of the missing ebpf import path
with error:
At first, I thought there was something to do with currentModule() in output.go but I think the module is not used to generate the ebpf path. Since it works fine on x86, I'm not so sure if is there a problem with bpf2go or with my environment. |
Beta Was this translation helpful? Give feedback.
Answered by
lmb
Jan 9, 2024
Replies: 1 comment 4 replies
-
Do you have the most recent version? This might be another bazel bug. Lines 88 to 90 in 394be60 |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd argue that this is a non-standard way of building a package. Why not do
go build -o bpf2go_arm64_debug ./cmd/bpf2go
?