-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Do not propagate host RUSTFLAGS when checking for WASM toolchain #9926
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good find! But we should also remove the normal RUSTFLAGS
, because that will otherwise be picked up.
bot merge |
Waiting for commit status. |
Bot will approve on the behalf of @bkchr, since they are a team lead, in an attempt to reach the minimum approval count |
Merge failed: Could not recover from: |
bot merge |
Trying merge. |
bot merge |
Trying merge. |
* master: (125 commits) Update multiple dependencies (#9936) Speed up timestamp generation when logging (#9933) First word should be Substrate not Polkadot (#9935) Improved file not found error message (#9931) don't read events in elections anymore. (#9898) Remove incorrect sanity check (#9924) Require crypto scheme for `insert-key` (#9909) chore: refresh of the substrate_builder image (#9808) Introduce block authorship soft deadline (#9663) Rework Transaction Priority calculation (#9834) Do not propagate host RUSTFLAGS when checking for WASM toolchain (#9926) Small quoting comment fix (#9927) add clippy to CI (#9694) Ensure BeforeBestBlockBy voting rule accounts for base (#9920) rm `.maintain` lock (#9919) Downstream `node-template` pull (#9915) Implement core::fmt::Debug for BoundedVec (#9914) Quickly skip invalid transactions during block authorship. (#9789) Add SS58 prefix for Automata (#9805) Clean up sc-peerset (#9806) ...
I stumble upon a similar issue, but it seems like in my case |
I usually export
RUSTFLAGS
with an alternative linker (mold) to speed up the compilation for development builds; unfortunately the check for the WASM toolchain fails when you do this as it then tries to use this linker forwasm32-unknown-unknown
which obviously doesn't work. This PR fixes this issue by simply clearing RUSTFLAGS beforehand.