Install RyuSim with the installer script, pin a version, or download a release tarball yourself.
curl -fsSL https://ryusim.com/install.sh | bash
The script installs the newest release. From the builds of that release, it takes the one for the highest glibc that is not newer than yours. It installs into ~/.ryusim for a regular user, or into /opt/ryusim when run as root.
RyuSim needs Clang, Ninja or CMake, and the zlib development files to build simulations. Getting Started has the package commands for each distribution, the PATH setup, and the cocotb install.
curl -fsSL https://ryusim.com/install.sh | bash -s -- --version 2.1.16
Each release is built and tested on these distributions. Builds are for x86_64 only.
| Distribution | Version | glibc |
|---|---|---|
| Ubuntu | 24.04 LTS | 2.39 |
| Ubuntu | 22.04 LTS | 2.35 |
| Debian | 13 (Trixie) | 2.41 |
| Debian | 12 (Bookworm) | 2.36 |
| Fedora | 42 | 2.41 |
| Fedora | 40 | 2.39 |
| Rocky Linux | 10 | 2.39 |
| Rocky Linux | 9 | 2.34 |
Release tarballs target glibc 2.34, 2.35, 2.36, 2.39 and 2.41. The installer also runs on other distributions with glibc 2.34 or newer; RyuSim is not tested on them. On an older glibc it stops and lists the glibc each build requires.
On Windows, install Ubuntu 24.04 under WSL2 and run the installer inside it.
Every release tarball is listed at ryusim.com/releases. Each 2.x tarball has a SHA-256 checksum file beside it, with the same name plus .sha256; some 1.x releases up to 1.7.21 have none. The installer checks the tarball against that file when the file exists and sha256sum is installed. Otherwise it prints a NOTE: line saying it skipped the check, and installs anyway. Tarball names follow this pattern:
ryusim-{VERSION}-linux-{ARCH}-glibc{X.Y}.tar.gz
To install by hand, pick the build with the newest glibc that is not newer than yours (ldd --version prints yours on its first line). Download it and its checksum, check it, and unpack it. This example takes release 2.1.16 built for glibc 2.39, which runs on hosts with glibc 2.39 or newer. The && chain stops if the checksum does not match:
curl -fsSLO https://downloads.ryusim.com/releases/v2.1.16/ryusim-2.1.16-linux-x86_64-glibc2.39.tar.gz
curl -fsSLO https://downloads.ryusim.com/releases/v2.1.16/ryusim-2.1.16-linux-x86_64-glibc2.39.tar.gz.sha256
sha256sum -c ryusim-2.1.16-linux-x86_64-glibc2.39.tar.gz.sha256 &&
tar -xzf ryusim-2.1.16-linux-x86_64-glibc2.39.tar.gz &&
export PATH="$PWD/ryusim-2.1.16-linux-x86_64-glibc2.39/bin:$PATH"
sha256sum -c prints the file name followed by OK. The unpacked directory holds bin/, lib/ and include/, and ryusim runs from it where it is.