-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOLUTION: Ruby 2.6.3 compilation error on OSX 14 (Sonoma) #5408
Comments
One caveat: for some reason the
Is there any way to know if the installation is really broken? |
Curious, did you experience the same behavior with 2.6.9, 2.6.10 and 2.6.3 ? |
@mathieujobin Same thing when installing 2.6.10. |
Oh... You are trying to build ruby 2.6 with OpenSSL 3 You can't There are patches but it's best to get OpenSSL 1.1 |
Oh, I just noticed the solution was already written in the updated description. I guess you are all good then? |
Yeah, everything is fine! 👍 |
I had to use different paths to make it work on my M1 laptop:
With these variables set, it finally works. Thank you! |
Felt like I tried 100 different things today and this finally worked, was able to install 2.6.3 and 2.6.6 via rvm. M1 + Sonoma 14.3.1 (23D60) Thanks so much! |
For anyone else trying to install Ruby 2.6.x where the "x" is less than 10, the first thing I always recommend is to update your Ruby project to at least 2.6.10. There is rarely a good reason to use a Ruby version where the patch version (the 3rd digit) is less than the latest one. In the 2.6.x series, the latest one is 2.6.10. This is especially important on Apple Silicon Macs, which don't support versions older than 2.6.8 using the native arm64 architecture. Yes, there are hacks to get older Ruby versions to install on arm64, but they are dangerous hacks that can cause other issues. One safe workaround is to use Rosetta, but that defeats the purpose of buying an Apple Silicon Mac because you won't be taking advantage of the faster arm64 chip. Also, installing things with and without Rosetta can cause all kinds of issues if you're not an expert at setting up a proper Ruby dev environment. Here's a step-by-step guide I wrote that explains how and why to upgrade the Ruby version in your project. I hope it helps! Also, keep in mind that RVM is not the only version manager out there. Others include asdf, chruby, frum, and rbenv. Some are more reliable than others, so give them a try if RVM doesn't work for you. |
@monfresh Good point! Better keep patch version as recent as possible since it rarely breaks something, quite the opposite. Ps: Very good article by the way! |
Description
I went through a situation where I spent several hours understanding and resolving it. That's why I'm opening this issue as a public utility. (Solution is the last topic.)
Steps to reproduce
Expected behavior
It should compile and install for the arm64 architecture (Apple M1 Pro).
Actual behavior
For some reason that I'm not aware of, the compilation insists on using the
openssl@3
library as you can see an excerpt from themake.log
below. Giving more context, I have bothopenssl@1.1
andopenssl@3
installed through HomeBrew as a dependency on several other packages.Full
make.log
: https://gist.github.com/igordelorenzi/236abb28c9e439f1890b8804d2df081aEnvironment info
Solution
The text was updated successfully, but these errors were encountered: