prysmaticlabs / bazel-go-ethereum Goto Github PK

Running ./catalyst.sh on raspberry pi
Seems to be complaining about chi. Not sure how to fix

DEBUG: /home/ethereum/.cache/bazel/_bazel_ethereum/175a49d1d117ca9f3586f99c1144c5d6/external/bazel_gazelle/internal/go_repository.bzl:189:18: com_github_rs_cors: gazelle: finding module path for import github.com/pressly/chi: go: downloading github.com/pressly/chi v1.5.4
go get: github.com/pressly/[email protected] updating to
github.com/pressly/[email protected]: parsing go.mod:
module declares its path as: github.com/go-chi/chi
but was required as: github.com/pressly/chi
INFO: Analyzed target //cmd/geth:geth (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /home/ethereum/bazel-go-ethereum/rpc/BUILD.bazel:3:11: GoCompilePkg rpc/go_default_library.a failed: (Exit 1): builder failed: error executing command bazel-out/host/bin/external/go_sdk/builder compilepkg -sdk external/go_sdk -installsuffix linux_arm64 -src rpc/client.go -src rpc/constants_unix.go -src rpc/constants_unix_nocgo.go -src rpc/doc.go -src ... (remaining 73 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox builder failed: error executing command bazel-out/host/bin/external/go_sdk/builder compilepkg -sdk external/go_sdk -installsuffix linux_arm64 -src rpc/client.go -src rpc/constants_unix.go -src rpc/constants_unix_nocgo.go -src rpc/doc.go -src ... (remaining 73 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
/usr/bin/ld.gold: error: cannot find -lm -latomic
collect2: error: ld returned 1 exit status
compilepkg: error running subcommand /usr/bin/gcc: exit status 1
Target //cmd/geth:geth failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 1.926s, Critical Path: 1.10s
INFO: 4 processes: 4 internal.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

bazel-go-ethereum should attempt to load bazel dependencies, if they are not already present.

This would be a "maybe" type rule where the downstream client would load this library and call

load("@com_github_ethereum_go_ethereum//:deps.bzl", "go_ethereum_repositories")

go_ethereum_repositories()

The go_ethereum_repositories rule will load any repository necessary to build go-ethereum which is not already installed. What we are seeing is that there are mixed versions of the same library in our downstream client which leads to wasted/redundant work.

Vendor/github.com/karalabe/hid is disabled because the cgo deps were not building properly.

This means the USB support is not enabled.