-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Mavericks, cannot install gems because libyaml is missing? #2689
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
Comments
can you please show me:
|
@mpapis, here is the output of rvm reinstall 2.1.1 --debug: https://gist.github.com/pzula/9477008 |
hmm, nothing obvious, now run: find /Users/pzula/.rvm/{gems,rubies}/ruby-2.1.1 -name psych.bundle |
btw. was this ruby initially upgraded from older version or installed? |
I initially have everything working before upgrading to Mavericks. After the upgrade, nothing worked, so I uninstalled & reinstalled. Output of find:
|
ah it complains that otool -L /Users/pzula/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/x86_64-darwin13.0/psych.bundle
find /usr/local -name libyaml*.dylib
yaml_name=$( pkg-config --list-all | awk '/^yaml[- ]/{print $1}' )
echo $yaml_name
pkg-config $yaml_name --variable=prefix I'm getting a feeling it's another time when you need to link packages in homebrew event they are keg only |
@mpapis, here is that output: https://gist.github.com/pzula/9484355 |
you should be able to fix the problem with: brew link libyaml but then it makes
also check Homebrew/legacy-homebrew#26367 |
Makefile: https://gist.github.com/pzula/9484560 |
It looks like somehow ruby/homebrew links to wrong libyaml library, please open a bug for ruby here: https://bugs.ruby-lang.org/projects/ruby-trunk/issues/new
you can mention this ticket and the homebrew one Homebrew/legacy-homebrew#26367 as it might take some time to get answer there try this to get temporary fix: brew link libyaml |
brew unlink libyaml && brew link libyaml |
I gave this problem some thinking and this bug can not be detected before you install ruby, this means we can not fix it on the autolibs level, so the only thing I can easily add is an warning, but still, I would prefer MRI take on the problem, please link me to the issue when it gets created |
This worked for me but I also needed to;
|
I have the same problem. Would somebody plz help me? My system |
@thanh8604 no it does not look like the same problem, you need to read the log, it points to a problem in your file |
phew! @tomjoro yeah it works, you just saved my day :) 👍 |
Ive already fix that "end" problem. I think my ruby don't have enough gem or spec. Do y'all have any idea? I've been struggling with this for a month and still stuck. Cant get it run. |
@thanh8604 can you please file a new issue with your problem and gist the current output on your system so we can help |
This is what i get. Thank you for ur answer. |
This is what i get. Plz help me On Thu, May 22, 2014 at 5:58 PM, Rys Sommefeldt notifications@github.comwrote:
|
@thanh8604 it's not RVM problem, please read the error again, it shows you that |
closing as the problem does not repeat that often (any more) and I already forgot the idea about warning, if you hit tis problem again please let me know |
I got the installing gem fails with permission error when trying to do After installing brew unlink libyaml && brew link libyaml After that, I now have a ruby gem setup with
As well as |
Why the fuck is everyone using rmv? Is everyone that lazy and cant navigate a Linux terminal? |
I've tried using RVM since I've upgraded to OSX Mavericks, and I've come across the same issue more than once while trying to install gems.
When using Ruby 2.1.1 as my installation, and running
gem install minitest
, I received the following error:Having read the error message, I thought perhaps I somehow have autolibs turned off, so I went ahead and removed RVM from the system, and reinstalled using the following command:
However, even after reinstalling RVM, I am unable to install gems due to the libyaml error. Am I doing something incorrectly? Do I have to install libyaml separately?
The text was updated successfully, but these errors were encountered: