Subspace node build failed on Ubuntu 18.04.6 aarch64

keens312 · March 26, 2024, 10:14pm

Issue Report

Subspace node build failed: cargo build --profile production --bin subspace-node

Environment

Operating System:
Ubuntu 18.04.6 aarch64
Pulsar/Advanced CLI/Docker:
CLI

Problem

cargo build --profile production --bin subspace-node
Compiling subspace-runtime v0.1.0 (/root/keen/subspace/subspace/crates/subspace-runtime)
Compiling evm-domain-runtime v0.1.0 (/root/keen/subspace/subspace/domains/runtime/evm)
Compiling frame-benchmarking-cli v4.0.0-dev (GitHub - subspace/polkadot-sdk: The Parity Polkadot Blockchain SDK)
error: failed to run custom build command for evm-domain-runtime v0.1.0 (/root/keen/subspace/subspace/domains/runtime/evm)

Caused by:
process didn’t exit successfully: /root/keen/subspace/subspace/target/production/build/evm-domain-runtime-bc16d397733710ce/build-script-build (exit status: 101)
— stdout
Information that should be included in a bug report.
Executing build command: env -u CARGO_ENCODED_RUSTFLAGS CARGO_TARGET_DIR=“/root/keen/subspace/subspace/target/production/wbuild/evm-domain-runtime/target” RUSTFLAGS=“-C target-cpu=mvp -C target-feature=-sign-ext -C link-arg=–export-table -Clink-arg=–export=__heap_base -C link-arg=–import-memory " SKIP_WASM_BUILD=”" “/root/.rustup/toolchains/nightly-2024-02-29-aarch64-unknown-linux-gnu/bin/cargo” “rustc” “–target=wasm32-unknown-unknown” “–manifest-path=/root/keen/subspace/subspace/target/production/wbuild/evm-domain-runtime/Cargo.toml” “–color=always” “–profile” “production” “-Z” “build-std”
Using rustc version: rustc 1.78.0-nightly (c475e2303 2024-02-28)

— stderr
warning: Patch frame-benchmarking v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-block-builder v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-client-api v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-client-db v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-consensus v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-consensus-aura v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-consensus-slots v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-network v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-network-common v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-network-sync v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-rpc v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-service v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-telemetry v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-transaction-pool v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-transaction-pool-api v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-utils v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-blockchain v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-consensus v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-consensus-aura v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-consensus-slots v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-crypto-ec-utils v0.4.1 (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-database v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-keystore v0.27.0 (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch substrate-prometheus-endpoint v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Check that the patched package version and available features are compatible
with the dependency requirements. If the patch has a different version from
what is locked in the Cargo.lock file, run cargo update to use the new
version. This may also occur with an optional dependency that is not enabled.
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Compiling sp-application-crypto v23.0.0 (GitHub - subspace/polkadot-sdk: The Parity Polkadot Blockchain SDK)
Compiling blst v0.3.11 (GitHub - subspace/blst: Multilingual BLS12-381 signature library)
The following warnings were emitted during compilation:

warning: blst@0.3.11: error: unable to create target: ‘No available targets are compatible with this triple.’
warning: blst@0.3.11: 1 error generated.

error: failed to run custom build command for blst v0.3.11 (https://github.com/subspace/blst?rev=ab042e18cb3b62e131423380513964e4b2c7b445#ab042e18)

Caused by:
process didn’t exit successfully: /root/keen/subspace/subspace/target/production/wbuild/evm-domain-runtime/target/production/build/blst-bfa1031f7f12c0ff/build-script-build (exit status: 1)
— stdout
cargo:rerun-if-env-changed=BLST_TEST_NO_STD
Using blst source directory /root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1
cargo:rerun-if-changed=/root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1/src
TARGET = Some(“wasm32-unknown-unknown”)
HOST = Some(“aarch64-unknown-linux-gnu”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some(“false”)
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
running: “clang” “-O2” “-ffunction-sections” “-fdata-sections” “-fPIC” “–target=wasm32-unknown-unknown” “-mcpu=mvp” “-ffreestanding” “-D__BLST_NO_ASM__” “-DSCRATCH_LIMIT=(45 * 1024)” “-o” “/root/keen/subspace/subspace/target/production/wbuild/evm-domain-runtime/target/wasm32-unknown-unknown/production/build/blst-db1f471f0d9c73c3/out/f8dc1dcaee63b0e1-server.o” “-c” “/root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1/src/server.c”
cargo:warning=error: unable to create target: ‘No available targets are compatible with this triple.’

cargo:warning=1 error generated.

exit status: 1

--- stderr


error occurred: Command "clang" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "--target=wasm32-unknown-unknown" "-mcpu=mvp" "-ffreestanding" "-D__BLST_NO_ASM__" "-DSCRATCH_LIMIT=(45 * 1024)" "-o" "/root/keen/subspace/subspace/target/production/wbuild/evm-domain-runtime/target/wasm32-unknown-unknown/production/build/blst-db1f471f0d9c73c3/out/f8dc1dcaee63b0e1-server.o" "-c" "/root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1/src/server.c" with args "clang" did not execute successfully (status code exit status: 1).

warning: build failed, waiting for other jobs to finish…
thread ‘main’ panicked at /root/.cargo/git/checkouts/polkadot-sdk-3e27f0ebe1cdca51/d6b5009/substrate/utils/wasm-builder/src/wasm_project.rs:823:37:
Copying the bloaty file to the project dir.: Os { code: 2, kind: NotFound, message: “No such file or directory” }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish…
error: failed to run custom build command for subspace-runtime v0.1.0 (/root/keen/subspace/subspace/crates/subspace-runtime)

Caused by:
process didn’t exit successfully: /root/keen/subspace/subspace/target/production/build/subspace-runtime-c70ece81022efbf5/build-script-build (exit status: 101)
— stdout
Information that should be included in a bug report.
Executing build command: env -u CARGO_ENCODED_RUSTFLAGS CARGO_TARGET_DIR=“/root/keen/subspace/subspace/target/production/wbuild/subspace-runtime/target” RUSTFLAGS=“-C target-cpu=mvp -C target-feature=-sign-ext -C link-arg=–export-table -Clink-arg=–export=__heap_base -C link-arg=–import-memory " SKIP_WASM_BUILD=”" “/root/.rustup/toolchains/nightly-2024-02-29-aarch64-unknown-linux-gnu/bin/cargo” “rustc” “–target=wasm32-unknown-unknown” “–manifest-path=/root/keen/subspace/subspace/target/production/wbuild/subspace-runtime/Cargo.toml” “–color=always” “–profile” “production” “-Z” “build-std”
Using rustc version: rustc 1.78.0-nightly (c475e2303 2024-02-28)

— stderr
Blocking waiting for file lock on package cache
warning: Patch frame-benchmarking v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-block-builder v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-client-api v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-client-db v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-consensus v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-consensus-aura v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-consensus-slots v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-network v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-network-common v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-network-sync v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-rpc v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-service v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-telemetry v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-transaction-pool v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-transaction-pool-api v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sc-utils v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-blockchain v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-consensus v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-consensus-aura v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-crypto-ec-utils v0.4.1 (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-database v4.0.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch sp-keystore v0.27.0 (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Patch substrate-prometheus-endpoint v0.10.0-dev (https://github.com/subspace/polkadot-sdk?rev=d6b500960579d73c43fc4ef550b703acfa61c4c8#d6b50096) was not used in the crate graph.
Check that the patched package version and available features are compatible
with the dependency requirements. If the patch has a different version from
what is locked in the Cargo.lock file, run cargo update to use the new
version. This may also occur with an optional dependency that is not enabled.
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Compiling sp-application-crypto v23.0.0 (GitHub - subspace/polkadot-sdk: The Parity Polkadot Blockchain SDK)
Compiling blst v0.3.11 (GitHub - subspace/blst: Multilingual BLS12-381 signature library)
Compiling lock_api v0.4.11
Compiling blake3 v1.5.0
Compiling libc v0.2.152
Compiling scopeguard v1.2.0
Compiling digest v0.9.0
Compiling libsecp256k1-core v0.3.0
Compiling ahash v0.8.10
Compiling spin v0.9.8
Compiling zerocopy v0.7.32
Compiling thiserror v1.0.56
The following warnings were emitted during compilation:

warning: blst@0.3.11: error: unable to create target: ‘No available targets are compatible with this triple.’
warning: blst@0.3.11: 1 error generated.

error: failed to run custom build command for blst v0.3.11 (https://github.com/subspace/blst?rev=ab042e18cb3b62e131423380513964e4b2c7b445#ab042e18)

Caused by:
process didn’t exit successfully: /root/keen/subspace/subspace/target/production/wbuild/subspace-runtime/target/production/build/blst-bfa1031f7f12c0ff/build-script-build (exit status: 1)
— stdout
cargo:rerun-if-env-changed=BLST_TEST_NO_STD
Using blst source directory /root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1
cargo:rerun-if-changed=/root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1/src
TARGET = Some(“wasm32-unknown-unknown”)
HOST = Some(“aarch64-unknown-linux-gnu”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some(“false”)
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
CC_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
CC_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
CFLAGS_wasm32-unknown-unknown = None
cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
CFLAGS_wasm32_unknown_unknown = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = Some(“-mcpu=mvp”)
running: “clang” “-O2” “-ffunction-sections” “-fdata-sections” “-fPIC” “–target=wasm32-unknown-unknown” “-mcpu=mvp” “-ffreestanding” “-D__BLST_NO_ASM__” “-DSCRATCH_LIMIT=(45 * 1024)” “-o” “/root/keen/subspace/subspace/target/production/wbuild/subspace-runtime/target/wasm32-unknown-unknown/production/build/blst-db1f471f0d9c73c3/out/f8dc1dcaee63b0e1-server.o” “-c” “/root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1/src/server.c”
cargo:warning=error: unable to create target: ‘No available targets are compatible with this triple.’

cargo:warning=1 error generated.

exit status: 1

--- stderr


error occurred: Command "clang" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "--target=wasm32-unknown-unknown" "-mcpu=mvp" "-ffreestanding" "-D__BLST_NO_ASM__" "-DSCRATCH_LIMIT=(45 * 1024)" "-o" "/root/keen/subspace/subspace/target/production/wbuild/subspace-runtime/target/wasm32-unknown-unknown/production/build/blst-db1f471f0d9c73c3/out/f8dc1dcaee63b0e1-server.o" "-c" "/root/.cargo/git/checkouts/blst-648c6f016e725b96/ab042e1/src/server.c" with args "clang" did not execute successfully (status code exit status: 1).

warning: build failed, waiting for other jobs to finish…
thread ‘main’ panicked at /root/.cargo/git/checkouts/polkadot-sdk-3e27f0ebe1cdca51/d6b5009/substrate/utils/wasm-builder/src/wasm_project.rs:823:37:
Copying the bloaty file to the project dir.: Os { code: 2, kind: NotFound, message: “No such file or directory” }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

[Paste any errors or relevant logs here]

nazar-pc · March 26, 2024, 10:32pm

Is this a duplicate of Subspace source cannot build on arm64? Also please use [details] and code blocks like, see Subspace source cannot build on arm64 for example of how I edited your message.

nazar-pc · March 26, 2024, 10:33pm

Also Ubuntu 18.04 is too old and unsupported, you should upgrade to 22.04 instead as 18.04 may have too old packages in stock repositories. So whatever build issues you have there - you’re on your own.

Topic		Replies	Views
Subspace source cannot build on arm64 Support	1	100	March 24, 2024
Subspace node build failed Support	5	131	April 4, 2024
Farm on aarch64 reports error and quit Support	1	70	March 25, 2024
An error occurred while running the node Support	1	331	December 6, 2023
Subspace Node (version gemini-3h) cannot run on ARM64 Support	6	180	October 1, 2024

Subspace node build failed on Ubuntu 18.04.6 aarch64

Issue Report

Environment

Problem

Related topics