near / nearcore

Reference client for NEAR Protocol
https://near.org
GNU General Public License v3.0
2.32k stars 621 forks source link

makefile build failed with error 101 #4538

Closed kleinpetr closed 3 years ago

kleinpetr commented 3 years ago

Describe the bug When I am trying to make a build in LXC container I've got this error

To Reproduce

  1. create lxc container with Ubuntu 18.04
  2. pull repository and install dependencies like clang, etc
  3. jump into dir and make release

Expected behavior make a build

Screenshots image

Version (please complete the following information):

Additional context

root@near:~/nearcore# make release
cargo +stable build -p neard --release
   Compiling neard v1.19.2 (/root/nearcore/neard)
error: could not compile `neard`

Caused by:
  process didn't exit successfully: `rustc --crate-name near --edition=2018 neard/src/../src/main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C opt-level=3 -C lto -C codegen-units=1 -C overflow-checks=on -C metadata=985b624ab28deb00 -C extra-filename=-985b624ab28deb00 --out-dir /root/nearcore/target/release/deps -L dependency=/root/nearcore/target/release/deps --extern actix=/root/nearcore/target/release/deps/libactix-e03ee30e2a4b8ab0.rlib --extern actix_rt=/root/nearcore/target/release/deps/libactix_rt-d535098e646bc15b.rlib --extern actix_web=/root/nearcore/target/release/deps/libactix_web-7a9e2006adb6caf1.rlib --extern borsh=/root/nearcore/target/release/deps/libborsh-0f3b6df3f7178d62.rlib --extern byteorder=/root/nearcore/target/release/deps/libbyteorder-4d3b9774dbe1cb54.rlib --extern chrono=/root/nearcore/target/release/deps/libchrono-ad97001b47ad7a3c.rlib --extern clap=/root/nearcore/target/release/deps/libclap-a184c8117c5676d8.rlib --extern dirs=/root/nearcore/target/release/deps/libdirs-3ecdf0836320ebad.rlib --extern easy_ext=/root/nearcore/target/release/deps/libeasy_ext-f8f17bf17dc0a59e.so --extern futures=/root/nearcore/target/release/deps/libfutures-ea67768c56439650.rlib --extern git_version=/root/nearcore/target/release/deps/libgit_version-d78b990cf45a18b5.rlib --extern jemallocator=/root/nearcore/target/release/deps/libjemallocator-23e8aee5935ddcdd.rlib --extern lazy_static_include=/root/nearcore/target/release/deps/liblazy_static_include-35413747c31737b8.rlib --extern near_chain=/root/nearcore/target/release/deps/libnear_chain-4f04170c95edcb1f.rlib --extern near_chain_configs=/root/nearcore/target/release/deps/libnear_chain_configs-2d5901718e0060e6.rlib --extern near_chunks=/root/nearcore/target/release/deps/libnear_chunks-f2f04c2654245425.rlib --extern near_client=/root/nearcore/target/release/deps/libnear_client-cb41c4da63e26860.rlib --extern near_crypto=/root/nearcore/target/release/deps/libnear_crypto-fc29bbc0e77a2e9a.rlib --extern near_epoch_manager=/root/nearcore/target/release/deps/libnear_epoch_manager-73dce1a7e3f6b57e.rlib --extern near_jsonrpc=/root/nearcore/target/release/deps/libnear_jsonrpc-9fc43cfd9e2db27e.rlib --extern near_network=/root/nearcore/target/release/deps/libnear_network-b80a534914efb3b3.rlib --extern near_performance_metrics=/root/nearcore/target/release/deps/libnear_performance_metrics-6f1efff37cd25dd7.rlib --extern near_pool=/root/nearcore/target/release/deps/libnear_pool-0d9df544b855b6e0.rlib --extern near_primitives=/root/nearcore/target/release/deps/libnear_primitives-015bc43d902705f6.rlib --extern near_rust_allocator_proxy=/root/nearcore/target/release/deps/libnear_rust_allocator_proxy-7de019bb24c3fa05.rlib --extern near_store=/root/nearcore/target/release/deps/libnear_store-d22a597dc004df65.rlib --extern near_telemetry=/root/nearcore/target/release/deps/libnear_telemetry-511679555389b664.rlib --extern neard=/root/nearcore/target/release/deps/libneard-34338131f787f5e4.rlib --extern node_runtime=/root/nearcore/target/release/deps/libnode_runtime-2179328bcf7a284b.rlib --extern num_rational=/root/nearcore/target/release/deps/libnum_rational-6fa49bb7023f18e4.rlib --extern openssl_probe=/root/nearcore/target/release/deps/libopenssl_probe-d696eb45a59626b9.rlib --extern rand=/root/nearcore/target/release/deps/librand-cfc27367bf50c40d.rlib --extern serde=/root/nearcore/target/release/deps/libserde-b3d2088af8d7f23a.rlib --extern serde_json=/root/nearcore/target/release/deps/libserde_json-434bdf4506a179d8.rlib --extern thiserror=/root/nearcore/target/release/deps/libthiserror-f0f95db6cb1c79f0.rlib --extern tracing=/root/nearcore/target/release/deps/libtracing-f64250be4ce3ca83.rlib --extern tracing_subscriber=/root/nearcore/target/release/deps/libtracing_subscriber-6952e89985b79b0b.rlib -D warnings -L native=/root/nearcore/target/release/build/openssl-sys-2fdeebf0efed49dd/out/openssl-build/install/lib -L native=/root/nearcore/target/release/build/brotli-sys-a9544767d243eac9/out -L native=/root/nearcore/target/release/build/jemalloc-sys-c924c918f3fc2e5b/out/build/lib -L native=/root/nearcore/target/release/build/parity-secp256k1-0ed3e497acfbe40d/out -L native=/root/nearcore/target/release/build/librocksdb-sys-a5fbe6a28b1e235c/out -L native=/root/nearcore/target/release/build/librocksdb-sys-a5fbe6a28b1e235c/out -L native=/root/nearcore/target/release/build/librocksdb-sys-a5fbe6a28b1e235c/out -L native=/root/nearcore/target/release/build/librocksdb-sys-a5fbe6a28b1e235c/out -L native=/root/nearcore/target/release/build/librocksdb-sys-a5fbe6a28b1e235c/out -L native=/root/nearcore/target/release/build/librocksdb-sys-a5fbe6a28b1e235c/out -L native=/root/nearcore/target/release/build/wasmer-vm-b55ba1a5cdafba91/out -L native=/root/nearcore/target/release/build/wasmer-runtime-core-near-e23fb02b6b42dc07/out -L native=/root/nearcore/target/release/build/blake3-7d19f171d8d55035/out -L native=/root/nearcore/target/release/build/blake3-7d19f171d8d55035/out -L native=/root/nearcore/target/release/build/wasmtime-runtime-99d22305e4ba50d5/out -L native=/root/nearcore/target/release/build/psm-91fd652fc3a45a41/out` (signal: 9, SIGKILL: kill)
warning: build failed, waiting for other jobs to finish...
error: build failed
bowenwang1996 commented 3 years ago

@kleinpetr this looks like it ran out of memory. Does it work if you try cargo build -j 2 -p neard?

mina86 commented 3 years ago

cargo build -j2 -p neard will build a debug binary so CARGO_BUILD_JOBS=1 make release might be better test. I do agree that it looks like lack of memory.

janewang commented 3 years ago
Screen Shot 2021-07-20 at 10 42 02 AM

Thanks for looking into this @bowenwang1996 @mina86. @kleinpetr confirmed it is related to internet connectivity to the container. Closing this issue.