search

cloudflare / pingora

A library for building fast, reliable and evolvable network services.
Apache License 2.0
20.3k stars 1.1k forks source link

error: failed to run custom build command for `boring-sys v4.5.0` #157

Closed ash-927 closed 3 months ago

ash-927 commented 3 months ago

When I cloned the pingora source and built in a clean Ubuntu container, I get "error: failed to run custom build command for boring-sys v4.5.0". I already did "apt install cmake" and "apt install build-essential". Is there any toolchain I am missing? Has anyone faced this issue?

error: failed to run custom build command for boring-sys v4.5.0 Caused by: process didn't exit successfully: /code/proxy/pingora/target/debug/build/boring-sys-150dab0054b09689/build-script-main (exit status: 101) --- stdout cargo:rerun-if-env-changed=BORING_BSSL_PATH_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BORING_BSSL_PATH_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_BORING_BSSL_PATH cargo:rerun-if-env-changed=BORING_BSSL_PATH cargo:rerun-if-env-changed=BORING_BSSL_INCLUDE_PATH_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BORING_BSSL_INCLUDE_PATH_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_BORING_BSSL_INCLUDE_PATH cargo:rerun-if-env-changed=BORING_BSSL_INCLUDE_PATH cargo:rerun-if-env-changed=BORING_BSSL_SOURCE_PATH_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BORING_BSSL_SOURCE_PATH_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_BORING_BSSL_SOURCE_PATH cargo:rerun-if-env-changed=BORING_BSSL_SOURCE_PATH cargo:rerun-if-env-changed=BORING_BSSL_PRECOMPILED_BCM_O_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BORING_BSSL_PRECOMPILED_BCM_O_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_BORING_BSSL_PRECOMPILED_BCM_O cargo:rerun-if-env-changed=BORING_BSSL_PRECOMPILED_BCM_O cargo:rerun-if-env-changed=BORING_BSSL_ASSUME_PATCHED_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BORING_BSSL_ASSUME_PATCHED_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_BORING_BSSL_ASSUME_PATCHED cargo:rerun-if-env-changed=BORING_BSSL_ASSUME_PATCHED cargo:rerun-if-env-changed=BORING_BSSL_SYSROOT_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BORING_BSSL_SYSROOT_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_BORING_BSSL_SYSROOT cargo:rerun-if-env-changed=BORING_BSSL_SYSROOT cargo:rerun-if-env-changed=BORING_BSSL_COMPILER_EXTERNAL_TOOLCHAIN_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BORING_BSSL_COMPILER_EXTERNAL_TOOLCHAIN_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_BORING_BSSL_COMPILER_EXTERNAL_TOOLCHAIN cargo:rerun-if-env-changed=BORING_BSSL_COMPILER_EXTERNAL_TOOLCHAIN cargo:rerun-if-env-changed=DEBUG_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=DEBUG_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_DEBUG cargo:rerun-if-env-changed=DEBUG cargo:rerun-if-env-changed=OPT_LEVEL_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=OPT_LEVEL_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_OPT_LEVEL cargo:rerun-if-env-changed=OPT_LEVEL cargo:rerun-if-env-changed=ANDROID_NDK_HOME_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=ANDROID_NDK_HOME_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_ANDROID_NDK_HOME cargo:rerun-if-env-changed=ANDROID_NDK_HOME cargo:rerun-if-env-changed=CMAKE_TOOLCHAIN_FILE_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=CMAKE_TOOLCHAIN_FILE_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_CMAKE_TOOLCHAIN_FILE cargo:rerun-if-env-changed=CMAKE_TOOLCHAIN_FILE

--- stderr

thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/boring-sys-4.5.0/build/main.rs:569:44: called Result::unwrap() on an Err value: Custom { kind: Other, error: "cd \"/code/proxy/pingora/target/debug/build/boring-sys-ab6b41fbee140dc6/out/boringssl\" && \"git\" \"init\" exited with status: 127" } note: run with RUST_BACKTRACE=1 environment variable to display a backtrace warning: build failed, waiting for other jobs to finish...

cxw620 commented 3 months ago

Have git installed? linux exit code 127 means command not found

ash-927 commented 3 months ago

Have git installed? linux exit code 127 means command not found

Oh! thank you so much For anyone else trying to build on a clean system, install curl, build-essential, cmake, git, clang