Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby Installing a Ruby Development Environment Installing a Ruby Development Environment Installing Ruby on Mac

Trying to install latest Ruby (version 2.3.0 on Mac OS X using rbenv as shown in tutorial)

Error message in terminal said : "definition not found: 2.3.0" see all available versions with 'rbenv install --list' If the version you need is missing, try upgrading ruby - build

then shows a file path /plugins/ruby-build && git pull && cd

I am a complete noob with terminal commands and git/pull commands etc. How do I properly install latest version of Ruby 2.3.0 using this rbenv ? *Note: I did not install using home brew, I followed tutorial basically identically however I am installing latest version of Ruby.

2 Answers

Hi Paul,

It looks like you might want to install/upgrade ruby-build (different from ruby) via homebrew. This is something rbenv needs to run correctly. See this this bug report on Github.

Do you have homebrew installed?

Best, Cena

Hey Cena, thanks for the response, it looks like I successfully installed ruby to latest version (without home-brew, used rbenv), and the terminal properly shows this after restarting my computer and terminal. I used command ruby -v and shows current updated version. Everything's good so far.

Yeah, so the error you ran into means that ruby-build was out of date. It's what provides the build definitions for the various Ruby versions for rbenv. How you update it depends a bit on how you installed it. But should you see this again in the future, just check the ruby-build docs on upgrading.