This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Latest node template fails to build #14335
Labels
I3-bug
The node fails to follow expected behavior.
Comments
github-actions
bot
added
the
J2-unconfirmed
Issue might be valid, but it’s not yet known.
label
Jun 9, 2023
Some similar reports seem to be made here: #12791 |
In case this failure is related to #13580:
|
Version::extract("cargo 1.69.0-nightly").unwrap(); // panicked at 'called |
Since the checking code accepts any nightly a workaround is to: export RUSTC_BOOTSTRAP=1 |
bkchr
added
I3-bug
The node fails to follow expected behavior.
and removed
J2-unconfirmed
Issue might be valid, but it’s not yet known.
labels
Jun 11, 2023
I got the same error, but the root cause may be different.
I know the error. It only occurs on macOS with Xcode bundled LLVM, and the WASM target has C binding crates. Changing to the Homebrew LLVM will solve the problem. It's just annoying. The problem introduced to node-template from #14452 |
@jasl yes this is not related and is caused by the pr you linked. |
bkchr
added a commit
that referenced
this issue
Jul 2, 2023
Apparently there are installations where the `hash` and `date` is optional. Closes: #14335
paritytech-processbot bot
pushed a commit
that referenced
this issue
Jul 3, 2023
* wasm-builder: Make `hash` and `date` optional Apparently there are installations where the `hash` and `date` is optional. Closes: #14335 * ".git/.scripts/commands/fmt/fmt.sh" --------- Co-authored-by: command-bot <>
nathanwhit
pushed a commit
to nathanwhit/substrate
that referenced
this issue
Jul 19, 2023
* wasm-builder: Make `hash` and `date` optional Apparently there are installations where the `hash` and `date` is optional. Closes: paritytech#14335 * ".git/.scripts/commands/fmt/fmt.sh" --------- Co-authored-by: command-bot <>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
Compiling the current main tip (commit 87b1b4728e29f68c6b2bafde7f3d0f4c8af9b302) of the node template results in this error:
Steps to reproduce
substrate-node-template> git checkout 87b1b4728e29f68c6b2bafde7f3d0f4c8af9b302
substrate-node-template> cargo c
The text was updated successfully, but these errors were encountered: