Skip to content

Compilation errors #13

@Daanvdplas

Description

@Daanvdplas

Running into an Error when installing ink-node
OS
Ubuntu 24
Command
cargo install ink-node
Error
error: failed to run custom build command for litep2p v0.9.5

Caused by:
process didn't exit successfully: /tmp/cargo-installUPzGqE/release/build/litep2p-03d8dc271d7b74a2/build-script-build (exit status: 101)
--- stderr

thread 'main' panicked at /home/user/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/litep2p-0.9.5/build.rs:20:10:
called Result::unwrap() on an Err value: Custom { kind: NotFound, error: "Could not find protoc. If protoc is installed, try setting the PROTOC environment variable to the path of the protoc binary. To install it on Debian, run apt-get install protobuf-compiler. It is also available at https://github.com/protocolbuffers/protobuf/releases For more information: https://docs.rs/prost-build/#sourcing-protoc" }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile ink-node v0.43.2, intermediate artifacts can be found at /tmp/cargo-installUPzGqE.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.

After fixing the above by installing protobuf this person got another error:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions