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 trialnicholastillman
8,319 PointsCan't get ruby to install via rbenv, keep getting a build error
This is the error I get when trying to install ruby via rbenv:
BUILD FAILED (OS X 10.10.5 using ruby-build 20160330)
Inspect or clean up the working tree at /var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160405092042.38963 Results logged to /var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160405092042.38963.log
Last 10 log lines:
from /private/var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160405092042.38963/ruby-2.2.4/lib/rubygems/dependency_installer.rb:373:in install'
from /private/var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160405092042.38963/ruby-2.2.4/lib/rubygems.rb:558:in
install'
from ./tool/rbinstall.rb:722:in block (2 levels) in <main>'
from ./tool/rbinstall.rb:721:in
each'
from ./tool/rbinstall.rb:721:in block in <main>'
from ./tool/rbinstall.rb:757:in
call'
from ./tool/rbinstall.rb:757:in block in <main>'
from ./tool/rbinstall.rb:754:in
each'
from ./tool/rbinstall.rb:754:in `<main>'
make: *** [do-install-all] Error 1
Any suggestions?
Thanks
nicholastillman
8,319 PointsSeth,
Thanks for the feedback. I figured my issue. I uninstalled rbenv and ruby-build. I reinstalled via homebrew and noticed I was adding an extra dependency that was not needed. Thanks again for you help.
Seth Kroger
56,413 PointsSeth Kroger
56,413 PointsThose log lines are what's called a stacktrace. It shows the function that are called from the top function of a program (often called main), and what that function called, etc. when the error occurred. They can get lengthy and unfortunately what you posted from the log wasn't enough to see what the error was. You should look further up until you see a line that says "error" or "exception" or the like.