Skip to content
This repository has been archived by the owner on Oct 19, 2021. It is now read-only.

Bazel fails when running catalyst.sh #18

Open
handelaar2 opened this issue Apr 30, 2021 · 0 comments
Open

Bazel fails when running catalyst.sh #18

handelaar2 opened this issue Apr 30, 2021 · 0 comments

Comments

@handelaar2
Copy link

handelaar2 commented Apr 30, 2021

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant