Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

wasm builder fails when running with a specific toolchain #3492

Closed
jbg opened this issue Aug 27, 2019 · 2 comments · Fixed by #5021
Closed

wasm builder fails when running with a specific toolchain #3492

jbg opened this issue Aug 27, 2019 · 2 comments · Fixed by #5021
Assignees

Comments

@jbg
Copy link

jbg commented Aug 27, 2019

rustup target add wasm32-unknown-unknown --toolchain nightly-2019-08-22
cargo +nightly-2019-08-22 build

fails with

error: failed to run custom build command for `polkadot-runtime v0.6.0 (polkadot/runtime)`

Caused by:
  process didn't exit successfully: `polkadot/target/debug/build/polkadot-runtime-8e31e940c712ba37/build-script-build` (exit code: 1)
--- stderr
   Compiling wasm-build-runner-impl v1.0.0 (polkadot/target/debug/build/polkadot-runtime-eec245fcb90ce820/out/wasm_build_runner)
    Finished dev [unoptimized + debuginfo] target(s) in 0.90s
     Running `polkadot/target/debug/build/polkadot-runtime-eec245fcb90ce820/out/wasm_build_runner/target/debug/wasm-build-runner-impl`
Rust WASM toolchain not installed, please install it!

because https://github.com/paritytech/substrate/blob/master/core/utils/wasm-builder/src/lib.rs#L154 hardcodes rustup run nightly cargo rather than using the CARGO environment variable to find cargo from the toolchain that’s in use.

@bkchr bkchr self-assigned this Aug 27, 2019
@bkchr
Copy link
Member

bkchr commented Aug 27, 2019

I had used CARGO in the beginning, but it would break for some use cases. Looks like I need to think again about it.

@emkman
Copy link

emkman commented Feb 19, 2020

I am unable to install the latest subkey because of this issue on OS X

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants