mirror of
https://github.com/hl-archive-node/nanoreth.git
synced 2025-12-06 10:59:55 +00:00
144 lines
5.1 KiB
Markdown
144 lines
5.1 KiB
Markdown
# Build from Source
|
||
|
||
You can build Reth on Linux, macOS, Windows, and Windows WSL2.
|
||
|
||
> **Note**
|
||
>
|
||
> Reth does **not** work on Windows WSL1.
|
||
|
||
## Dependencies
|
||
|
||
First, **install Rust** using [rustup](https://rustup.rs/)：
|
||
|
||
```bash
|
||
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
|
||
```
|
||
|
||
The rustup installer provides an easy way to update the Rust compiler, and works on all platforms.
|
||
|
||
> **Tips**
|
||
>
|
||
> - During installation, when prompted, enter `1` for the default installation.
|
||
> - After Rust installation completes, try running `cargo version` . If it cannot
|
||
> be found, run `source $HOME/.cargo/env`. After that, running `cargo version` should return the version, for example `cargo 1.68.2`.
|
||
> - It's generally advisable to append `source $HOME/.cargo/env` to `~/.bashrc`.
|
||
|
||
With Rust installed, follow the instructions below to install dependencies relevant to your
|
||
operating system:
|
||
|
||
- **Ubuntu**: `apt-get install libclang-dev pkg-config build-essential`
|
||
- **macOS**: `brew install llvm pkg-config`
|
||
- **Windows**: `choco install llvm` or `winget install LLVM.LLVM`
|
||
|
||
These are needed to build bindings for Reth's database.
|
||
|
||
## Build Reth
|
||
|
||
With Rust and the dependencies installed, you're ready to build Reth. First, clone the repository:
|
||
|
||
```bash
|
||
git clone https://github.com/paradigmxyz/reth
|
||
cd reth
|
||
```
|
||
|
||
Then, install Reth into your `PATH` directly via:
|
||
|
||
```bash
|
||
cargo install --locked --path bin/reth --bin reth
|
||
```
|
||
|
||
The binary will now be accessible as `reth` via the command line, and exist under your default `.cargo/bin` folder.
|
||
|
||
Alternatively, you can build yourself with:
|
||
|
||
```bash
|
||
cargo build --release
|
||
```
|
||
|
||
This will place the reth binary under `./target/release/reth`, and you can copy it to your directory of preference after that.
|
||
|
||
Compilation may take around 10 minutes. Installation was successful if `reth --help` displays the [command-line documentation](../cli/cli.md).
|
||
|
||
If you run into any issues, please check the [Troubleshooting](#troubleshooting) section, or reach out to us on [Telegram](https://t.me/paradigm_reth).
|
||
|
||
## Update Reth
|
||
|
||
You can update Reth to a specific version by running the commands below.
|
||
|
||
The `reth` directory will be the location you cloned reth to during the installation process.
|
||
|
||
`${VERSION}` will be the version you wish to build in the format `vX.X.X`.
|
||
|
||
```bash
|
||
cd reth
|
||
git fetch
|
||
git checkout ${VERSION}
|
||
cargo build --release
|
||
```
|
||
|
||
## Optimizations
|
||
|
||
**Profiles**
|
||
|
||
You can customise the compiler settings used to compile Reth via
|
||
[Cargo profiles](https://doc.rust-lang.org/cargo/reference/profiles.html).
|
||
|
||
Reth includes several profiles which can be selected via the Cargo flag `--profile`.
|
||
|
||
* `release`: default for source builds, enables most optimisations while not taking too long to
|
||
compile.
|
||
* `maxperf`: default for binary releases, enables aggressive optimisations including full LTO.
|
||
Although compiling with this profile improves some benchmarks by around 20% compared to `release`,
|
||
it imposes a _significant_ cost at compile time and is only recommended if you have a fast CPU.
|
||
|
||
**Rust compiler flags**
|
||
|
||
You can also use `RUSTFLAGS="-C target-cpu=native"` to enable CPU-specific optimisations. In order to get
|
||
the highest performance out of your build:
|
||
|
||
```bash
|
||
RUSTFLAGS="-C target-cpu=native" cargo build --profile maxperf
|
||
```
|
||
|
||
**Features**
|
||
|
||
Finally, some features may improve performance on your system, most notably `jemalloc`, which replaces the default memory allocator used by reth.
|
||
|
||
You can enable features by passing them to the `--features` Cargo flag.
|
||
|
||
> **Note**
|
||
>
|
||
> The `jemalloc` feature is unstable on Windows due to jemallocator itself.
|
||
|
||
## Troubleshooting
|
||
|
||
### Command is not found
|
||
|
||
Reth will be installed to `CARGO_HOME` or `$HOME/.cargo`. This directory needs to be on your `PATH` before you can run `$ reth`.
|
||
|
||
See ["Configuring the `PATH` environment variable"](https://www.rust-lang.org/tools/install) for more information.
|
||
|
||
### Compilation error
|
||
|
||
Make sure you are running the latest version of Rust. If you have installed Rust using rustup, simply run `rustup update`.
|
||
|
||
If you can't install the latest version of Rust you can instead compile using the Minimum Supported
|
||
Rust Version (MSRV) which is listed under the `rust-version` key in Reth's
|
||
[Cargo.toml](https://github.com/paradigmxyz/reth/blob/main/Cargo.toml).
|
||
|
||
If compilation fails with `(signal: 9, SIGKILL: kill)`, this could mean your machine ran out of
|
||
memory during compilation. If you are on Docker, consider increasing the memory of the container, or use a [pre-built
|
||
binary](../installation/binaries.md).
|
||
|
||
If compilation fails with `error: linking with cc failed: exit code: 1`, try running `cargo clean`.
|
||
|
||
_(Thanks to Sigma Prime for this section from [their Lighthouse book](https://lighthouse-book.sigmaprime.io/installation.html)!)_
|
||
|
||
### Bus error (WSL2)
|
||
|
||
In WSL 2 on Windows, the default virtual disk size is set to 1TB.
|
||
|
||
You must increase the allocated disk size for your WSL2 instance before syncing reth.
|
||
|
||
You can follow the instructions here: [how to expand the size of your WSL2 virtual hard disk.](https://learn.microsoft.com/en-us/windows/wsl/disk-space#how-to-expand-the-size-of-your-wsl-2-virtual-hard-disk)
|