NPO-Accounting/houdini
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
houdini/docs/KNOWN_ISSUES.MD

2.4 KiB
Raw Blame History

Byebug or Pry won't start - image not found readline.bundle

Error reported.

pry
# Sorry, you can't use byebug without Readline. To solve this, you need to
# rebuild Ruby with Readline support. If using Ubuntu, try `sudo apt-get
# install libreadline-dev` and then reinstall your Ruby.

What's the problem?

Ruby installation with gems, specifically the readline gem already installed on a system that had a macOS upgrade.

How to solve it?

If you use rvm to manage your ruby versions. You can use rvm to recompile ruby from source to solve the problem.

Note: You'll need to rebuild ruby as a best practice after macOS upgrades.

Steps to rebuild ruby via RVM

Make sure you've installed the latest Xcode + tools before proceeding; check App Store for updates. Be sure to accept the Xcode License before proceeding!

Update Xcode and accept the license:

  • Update Xcode to latest via App Store, be sure to update the Xcode Tools as well.
  • In a terminal window, exec this command: sudo xcodebuild -license accept

Make sure you have the readline lib installed:

  • brew --prefix readline
  • if you get Error: No available formula with the name "readline", install readline:
    • brew install readline
    • brew link --force readline You'll need to use --force to make it work.
    • vi ~/.rvm/user/db and add the following: ruby_configure_flags=--with-readline-dir=/usr/local/opt/readline

Reinstall Ruby, with a rebuild of sources:

  • rvm reinstall <your_ruby_version> This command removes the specified version's ruby binaries and libs, and rebuilds from source code on your system, with the latest macOS headers and libs.
  • rvm reinstall <your_ruby_version> --gems This command repro's the same steps as above, but it removes the gems first as well. The next time you run bundle install the gems will be downloaded and rebuilt against your latest ruby. This can help resolve other potential issues with gems after rebuilding ruby on macOS.
  • Change the specified version (2.5.1 in my case) to match your needs.
  • I ended up using the second syntax for a completely fresh start.

Gotchas: If you're in the project directory running a terminal window when finished this process, You'll had to cd .. up a level and then cd project-folder back into the project so that RVM would reactivate your gemset. Run gem install bundler and then bundle install to re-hydrate the gems for the project.