Moncef Belyamani

@argent-codes The reason why you're not able to compile the bigdecimal gem is not because there's something wrong with Ruby 3.1.6, but because you're trying to install a version of...

@theJohnnyBrown That's a great question. I don't know the reason why the official instructions recommend using `sudo` and using the system Ruby that comes preinstalled on macOS, but @jshier is...

I cannot reproduce this on macOS Sonoma 14.5. The `sha1` command does not exist by default on macOS Sonoma (and possibly older versions too). In my case, `ruby-install` finds these...

This seems to be the issue: ``` % bundle info rspec-core | grep Path Path: /Users/jed/.gem/ruby/3.2.0/gems/rspec-core-3.12.2 ``` It looks like you have rspec-core installed in 3.2.0, but not in 3.2.1....

Right, I'm used to `chruby`, and I have minor versions in my `~/.gem/ruby` folder. But asdf behaves differently. Out of curiosity, I switched to asdf (which my [Ruby on Mac](https://www.rubyonmac.dev/)...

I should have specified that it's probably the GEM_PATH and/or GEM_HOME env vars that are possibly being set somewhere. You can check with `env | grep GEM`. Also, are you...

@leesheppard No, that will not work because Ruby versions older than 3.1 do not support OpenSSL 3. Here's a handy [OpenSSL and Ruby Compatibility Table](https://www.rubyonmac.dev/openssl-versions-supported-by-ruby). The reason why some people...

I am unable to reproduce this issue with ruby-build 20231025 and the following combinations on macOS Sonoma on an M1 Mini: - Xcode 15.0 and CLT 15.0 on macOS 14.0...

Yes, certain projects that require the use of the Xcode app also require that `xcode-select -p` points to the Xcode app. This build failure is definitely not a 100% reproducible...

That's because Ruby 3.4.x stopped including certain gems by default. For example, `bigdecimal` used to be a default gem in Ruby 3.3.x and older, but starting with Ruby 3.4.0, it...