frum: can't find OpenSSL

I’ve updated my installation guide Install Ruby with Frum for Ruby 3.1. I’m advising to install OpenSSL using Homebrew before installing frum. However, after installing OpenSSL, frum, and Ruby 3.1, when I try to install the rails gem, I get:

$ gem install rails
ERROR:  While executing gem ... (Gem::Exception)
    OpenSSL is not available. Install OpenSSL and rebuild Ruby (preferred) or use non-HTTPS sources

Looking at closed issues, it looks like frum version 0.1.2 fixes any issues with OpenSSL. What am I overlooking? Do I need to install ruby with the option --with-openssl-dir=<ssl_dir>? Or do I need to add openssl to my PATH?

Let me know and I’ll update my guide.

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 1
Comments: 17 (4 by maintainers)

Most upvoted comments

I was able to get past the openssl issue by reinstalling ruby. Using frum,

frum uninstall 3.1.0
frum install 3.1.0 --with-openssl-dir=`brew --prefix openssl`

151henry151 on Jan 11, 2022

@fsegouin Ruby versions less than 3.1 don’t support OpenSSL3. If you want to use OpenSSL 3, then you need to use Ruby 3.1 or higher. If you need to install 2.7.5, then you have to use OpenSSL 1.1

monfresh on Aug 29, 2023

maOS Monterey Version 12.0.1 Mac Mini 2020 Apple M1 8GB memory frum 0.1.2

which -a brew
/opt/homebrew/bin/brew

FYI, Homebrew installs to a different directory on M1 than Intel.

DanielKehoe on Jan 15, 2022

Does everyone in this issue use M1 mac? I want to know your environment…

@TaKO8Ki in reference to your question, here are my device specs

MacBook Pro (16-inch, 2021) Apple M1 Max Memory 32GB macOS Monterrey 12.0.1 Frum 0.1.2

shanebarringer on Jan 13, 2022

0.1.2 compiles everything without issue for me (pre 0.1.2, I did have openssl issues as without @1.1 in the prefix, it was targeting @3 on my machine by default).

One thing to mention is that if memory serves me correctly when the M1 was released, a lot of early adopters had to use arch -arm64 to install Homebrew.

That changed some months after, but I wonder if having to use arch -amd64 is now an unfortunate consequence of that initial install.

MacBook Air (M1, 2020) Apple M1 Memory 16GB macOS Monterey 12.0.1 From 0.1.2

error: No such file or directory (os error 2)

I noticed a similar error if there’s a default alias symlink left.

adam12 on Jan 13, 2022

I ran into a similar error while trying to bring up a rails app. Prefixing arch -arm64 to my requests seems to have fixed the issue.

arch -arm64 gem install bundler

Hope this helps!

shanebarringer on Jan 7, 2022