Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update troubleshoot-rust-issues.md #2145

Merged
merged 4 commits into from
Aug 28, 2024
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions content/md/en/docs/install/troubleshoot-rust-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,11 +114,11 @@ WASM_BUILD_TOOLCHAIN=nightly-<yyyy-MM-dd> cargo build --release
```

This command builds the _runtime_ using the specified nightly toolchain.
The rest of project is compiled using the _default_ toolchain, that is, the latest version of the `stable` toolchain that you have installed.
The rest of the project is compiled using the _default_ toolchain, that is, the latest version of the `stable` toolchain that you have installed.

### Downgrade the nightly toolchain

If your computer is configured to use the latest Rust `nightly` toolchain and you want to downgrade to a specific nightly version,you must first uninstall the latest `nightly` toolchain.
If your computer is configured to use the latest Rust `nightly` toolchain and you want to downgrade to a specific nightly version, you must first uninstall the latest `nightly` toolchain.
For example, you can remove the latest `nightly` toolchain, then use a specific version of the `nightly` toolchain by running commands similar to the following:

```sh
Expand All @@ -129,17 +129,17 @@ rustup target add wasm32-unknown-unknown --toolchain nightly-<yyyy-MM-dd>

## Ensure PATH is set correctly

If after installing Rust the commands don't seem to work, showing errors such as `command not found: rustup`, make sure it your PATH is configured correctly.
If after installing Rust the commands don't seem to work, showing errors such as `command not found: rustup`, make sure that your PATH is configured correctly.

Currently, the `rustup` installer installs by default to the bash profile (on mac). If you are using another shell, make sure to add this line to your profile (e.g. `.zshrc`):
Currently, the `rustup` installer installs by default to the bash profile (on Mac). If you are using another shell, make sure to add this line to your profile (e.g. `.zshrc`):

```bash
source "$HOME/.cargo/env"
```

## Installing cmake or protobuf for M1 macOS users
## Installing cmake or protobuf for M-series macOS users
shawntabrizi marked this conversation as resolved.
Show resolved Hide resolved

Currently, there are issues compiling the Substrate node when using the packages that are pre-installed on macOS computers with the M1 chip.
Currently, there are issues when compiling the Substrate node while using the packages that are pre-installed on macOS computers with the M-series chip.

```sh
error: failed to run custom build command for prost-build v0.10.4
Expand Down