-
Notifications
You must be signed in to change notification settings - Fork 975
Closed
Labels
in diagnosticissue under diagnosticissue under diagnostic
Description
Issue and Steps to Reproduce
When building 23.05.2 from source for my arm64 board, I encountered the following error during build:
ld plugins/sql
cargo build --quiet --bin cln-grpc
error: failed to run custom build command for `cln-grpc v0.1.2 (/sdcard/opt/lightning/cln-grpc)`
Caused by:
process didn't exit successfully: `/sdcard/opt/lightning/target/debug/build/cln-grpc-815443097e528e12/build-script-build` (exit status: 101)
--- stdout
cargo:rerun-if-changed=proto/node.proto
cargo:rerun-if-changed=proto
--- stderr
thread 'main' panicked at 'Could not find `protoc` installation and this build crate cannot proceed without
this knowledge. If `protoc` is installed and this crate had trouble finding
it, you can set the `PROTOC` environment variable with the specific path to your
installed `protoc` binary.If you're on debian, try `apt-get install protobuf-compiler` or download it from https://github.com/protocolbuffers/protobuf/releases
For more information: https://docs.rs/prost-build/#sourcing-protoc
', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/prost-build-0.11.5/src/lib.rs:1295:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: ambiguous glob re-exports
--> cln-rpc/src/model.rs:12:9
|
12 | pub use requests::*;
| ^^^^^^^^^^^ the name `DelinvoiceStatus` in the type namespace is first re-exported here
13 | pub use responses::*;
| ------------ but the name `DelinvoiceStatus` in the type namespace is also re-exported here
|
= note: `#[warn(ambiguous_glob_reexports)]` on by default
make: *** [plugins/Makefile:241: target/debug/cln-grpc] Error 101
rm external/aarch64-openwrt-linux-musl/libwally-core-build/src/secp256k1/libsecp256k1.la
I am building off the specific tag to ensure a proper release build. Unfortunately, my understanding of Rust related builds is still very new, so I might be missing something here.
Here are the Rust related versions:
# rustc --version
rustc 1.70.0 (90c541806 2023-05-31)
# cargo --version
cargo 1.70.0 (ec8a8a0ca 2023-04-25)
The target device is Linux, aarch64, musl (stable-aarch64-unknown-linux-musl).
Any idea what I might be doing wrong here?
getinfo output
None, since I don't have a compiled build.
Thank you and kind regards,
Ingwie!
PS: Before sending this, I decided to rustup update and see if anything changed, but that didn't happen. The same error still on 1.71.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
in diagnosticissue under diagnosticissue under diagnostic