rbenv/ruby-build

ruby-build

ruby-build is a command-line tool that simplifies installation of any Ruby version from source on Unix-like systems.

It is available as a plugin for rbenv as the rbenv install command, or as a standalone program as the ruby-build command.

Installation

Homebrew package manager

brew install ruby-build

Upgrade with:

brew upgrade ruby-build

Clone as rbenv plugin using git

git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build

Upgrade with:

git -C "$(rbenv root)"/plugins/ruby-build pull

Install manually as a standalone program

First, download a tarball from https://github.com/rbenv/ruby-build/releases/latest. Then:

tar -xzf ruby-build-*.tar.gz
PREFIX=/usr/local ./ruby-build-*/install.sh

Usage

Basic Usage

# As a standalone program
$ ruby-build --list                        # lists latest stable releases for each Ruby
$ ruby-build --definitions                 # lists all definitions, including outdated ones
$ ruby-build 3.4.9 ~/.rubies/ruby-3.4.9    # installs Ruby 3.4.9
$ ruby-build -d ruby-3.4.9 ~/.rubies       # alternate form for the previous example
$ ruby-build -d ruby-3.4 ~/.rubies         # installs latest Ruby 3.4.x

# As an rbenv plugin
$ rbenv install 3.4.9  # installs Ruby 3.4.9 to ~/.rbenv/versions/3.4.9
$ rbenv install 3      # installs latest Ruby 3.x

[!WARNING] ruby-build mostly does not verify that system dependencies are present before downloading and attempting to compile Ruby from source. Please ensure that all requisite libraries such as build tools and development headers are already present on your system.

Basically, what ruby-build does when installing a Ruby version is this:

• Downloads an official tarball of Ruby source code;
• Extracts the archive into a temporary directory on your system;
• Executes ./configure --prefix=/path/to/destination in the source code;
• Runs make install to compile Ruby;
• Verifies that the installed Ruby is functional.

Depending on the context, ruby-build does a little bit more than the above: for example, it will try to link Ruby to the appropriate OpenSSL version, even if that means downloading and compiling OpenSSL itself; it will discover and link to Homebrew-installed instances of some libraries like libyaml and readline, etc.

Ruby versions

When listing "latest" Ruby versions, such as in ruby-build --list output, ruby-build only knows of Ruby versions that are bundled with this project. That means that when a new Ruby version comes out, ruby-build will not know about it immediately— you will have to upgrade ruby-build before you can use it to install the new Ruby version. This is because ruby-build bundles definition files for each individual Ruby version.

If it's important to you that your installer tool always consults remote resources to download the list of latest Ruby versions (without having to upgrade the tool itself), check out ruby-install as an alternative to ruby-build.

Ruby implementations

ruby-build ships with definitions for the following Ruby implementations, denoted by version prefixes in the ruby-build --list output:

• CRuby: listed in ruby-build as unprefixed version numbers in the X.Y.Z format. This is the main Ruby implementation that most people use and is also historically known as "MRI". ruby-build allows adding the ruby- prefix to CRuby version numbers for compatibility with other version managers.

• jruby: JRuby is a high-performance Ruby implementation with real threading built on top of the Java virtual machine (JVM).

• mruby: mruby is a lightweight, embeddable Ruby implementation for microcontrollers.

• picoruby: PicoRuby is an alternative mruby implementation for one-chip microcontrollers.

• truffleruby: The Native standalone distribution of TruffleRuby, an implementation of Ruby on top of GraalVM's Truffle framework.

• truffleruby+graalvm: The JVM standalone distribution of TruffleRuby.

Advanced Usage

Custom Build Definitions

To install a version of Ruby that is not available in ruby-build, you can specify the path to a custom build definition file in place of a Ruby version number.

# As a standalone program
$ ruby-build -d /path/to/3.4-custom /opt/rubies  # installs to /opt/rubies/3.4-custom

# As an rbenv plugin
$ rbenv install /path/to/3.4-custom              # installs to $(rbenv root)/versions/3.4-custom

You can also provide a directory of custom build definition files. The path(s) will be searched along with ruby-build's bundled share/ruby-build/ directory. (Perhaps a collection of 3rd-party build definitions published as a git repo, or an organization's custom build definitions distributed in-house.)

# As a standalone program
$ RUBY_BUILD_DEFINITIONS=/path/to/custom/defs ruby-build --definitions              # lists all available versions of Ruby, including custom defs
$ RUBY_BUILD_DEFINITIONS=/path/to/custom/defs ruby-build -d 3.5-custom /opt/rubies  # installs to /opt/rubies/3.5-custom

# As an rbenv plugin
$ RUBY_BUILD_DEFINITIONS=/path/to/custom/defs rbenv install --list                  # lists all available versions of Ruby, including custom defs
$ RUBY_BUILD_DEFINITIONS=/path/to/custom/defs rbenv install 3.5-custom              # installs to $(rbenv root)/versions/3.5-custom

Check out default build definitions as examples on how to write definition files.

Custom Build Configuration

The build process may be configured through the following environment variables:

Applying Patches

Both rbenv install and ruby-build commands support the -p/--patch flag to apply a patch to the Ruby source code before building. Patches are read from standard input:

# applying a single patch
$ rbenv install --patch 1.9.3-p429 < /path/to/ruby.patch

# applying a patch from HTTP
$ rbenv install --patch 1.9.3-p429 < <(curl -sSL http://git.io/ruby.patch)

# applying multiple patches
$ cat fix1.patch fix2.patch | rbenv install --patch 1.9.3-p429

Checksum Verification

All Ruby definition files bundled with ruby-build include checksums for packages, meaning that all externally downloaded packages are automatically checked for integrity after fetching.

See the next section for more information on how to author checksums.

Package Mirrors

You may specify a custom mirror by setting RUBY_BUILD_MIRROR_URL. When set, ruby-build will first attempt to download packages from the mirror before falling back to the original URL.

# example:
export RUBY_BUILD_MIRROR_URL="https://my-mirror.example.com"
install_package "ruby-2.6.5" "https://ruby-lang.org/ruby-2.6.5.tgz#<SHA2>"
# Will first try: https://my-mirror.example.com/<SHA2>

ruby-build will first try to fetch this package from $RUBY_BUILD_MIRROR_URL/<SHA2> (note: this is the complete URL), where <SHA2> is the checksum for the file. It will fall back to downloading the package from the original location if:

• the package was not found on the mirror;
• the mirror is down;
• the download is corrupt, i.e. the file's checksum doesn't match;
• no tool is available to calculate the checksum; or
• RUBY_BUILD_SKIP_MIRROR is enabled.

If a mirror site doesn't conform to the above URL format, you can specify the complete URL by setting RUBY_BUILD_MIRROR_PACKAGE_URL. It behaves the same as RUBY_BUILD_MIRROR_URL except being a complete URL.

Keeping the build directory after installation

Both ruby-build and rbenv install accept the -k or --keep flag, which tells ruby-build to keep the downloaded source after installation. This can be useful if you need to use gdb and memprof with Ruby.

Source code will be kept in a parallel directory tree ~/.rbenv/sources when using --keep with the rbenv install command. You should specify the location of the source code with the RUBY_BUILD_BUILD_PATH environment variable when using --keep with ruby-build.

Getting Help

Please see the ruby-build wiki for solutions to common problems.

If you can't find an answer on the wiki, open an issue on the issue tracker. Be sure to include the full build log for build failures.