安装Ruby 2.5.0遇__rvm_make -j 1错误，卸载重装rvm未果求助

Hey there, I’ve dealt with this exact frustration on High Sierra before—let’s work through targeted fixes to get Ruby 2.5.0 installed smoothly.

1. Refresh Xcode Command Line Tools First #

Mac’s core compilation tools often cause these make errors. Let’s make sure they’re up to snuff:

• Run this to install or update the tools (follow the on-screen prompts if needed):

  xcode-select --install
  

• If you already have them installed, reset the path to fix potential conflicts:

  xcode-select --reset
  

2. Fix OpenSSL Dependencies (The Most Common Culprit) #

Ruby 2.5.x relies heavily on OpenSSL, and High Sierra’s default setup can clash with Homebrew’s version:

• First, update Homebrew and reinstall OpenSSL to ensure a clean copy:

  brew update
  brew reinstall openssl
  

• Install Ruby 2.5.0 while explicitly pointing to Homebrew’s OpenSSL path:

  rvm install 2.5.0 --with-openssl-dir=$(brew --prefix openssl)
  

3. Deep Clean RVM Residues (Beyond rvm implode) #

Sometimes rvm implode leaves hidden files that mess up reinstalls. Let’s wipe every trace:

• Uninstall RVM completely:

  rvm implode
  rm -rf ~/.rvm ~/.rvmrc /etc/rvmrc
  

• Restart your terminal to clear any lingering environment variables.
• Reinstall the stable RVM version:

  \curl -sSL https://get.rvm.io | bash -s stable
  

• Before installing Ruby, run this to check for missing system requirements and install them:

  rvm requirements
  

4. Adjust Compilation Core Count #

The -j 1 flag limits make to a single core, which can trigger timeouts or errors on some systems. Try matching your CPU core count (e.g., -j4 for 4 cores):

rvm install 2.5.0 --make "-j4"

5. Switch to Homebrew’s GCC Instead of Default Clang #

High Sierra’s built-in Clang compiler has compatibility quirks with older Ruby versions. Let’s use GCC instead:

• Install GCC via Homebrew:

  brew install gcc
  

• Install Ruby using your new GCC (replace gcc-8 with the version you installed—check with brew info gcc):

  rvm install 2.5.0 --cc=gcc-8
  

If none of these resolve the issue, sharing the full make.log output would help pinpoint the exact compilation failure!

内容的提问来源于stack exchange，提问作者Andreia