Skip to content
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

An error occurred while installing nokogiri (1.6.4.1), and Bundler cannot continue. #19

Closed
intelligence opened this issue Nov 16, 2014 · 7 comments

Comments

@intelligence
Copy link

Getting this error when trying to install this. Tried to install nokogiri on my own and found errors pointing me to this http://stackoverflow.com/questions/22703393/clang-error-unknown-argument-mno-fused-madd-wunused-command-line-argumen

So got nokogiri installed, but when trying to install again it still throws me this..

@gael-ian
Copy link
Owner

Hi,

How do you try to install the plugin ? Could you please post a complete log of your installation process ?

@intelligence
Copy link
Author

Simply using vagrant plugin install vagrant-bindfs

This is what happens:
Installing the 'vagrant-bindfs' plugin. This can take a few minutes... Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is:

An error occurred while installing nokogiri (1.6.4.1), and Bundler cannot continue. Make sure that gem install nokogiri -v '1.6.4.1' succeeds before bundling.

I've updated to 10.9.5 now, still seeing this problem unfortunately..

@gael-ian
Copy link
Owner

vagrant-bindfs does not require nokogiri. Do you have any other plugin installed ?

@intelligence
Copy link
Author

Only lists -login and -share, but the problem seems connected to Vagrant itself.

@gael-ian
Copy link
Owner

Yes. I think we can close this issue.

@oflannabhra
Copy link

I'm coming across a similar issue, @intelligence . I realize this might not be vagrant-bindfs specific, but how did you resolve it?

Edit: I resolved this issue by updating vagrant, because it was an issue with vagrant that was resolved in vagrant 1.6.4

@gael-ian
Copy link
Owner

Sorry but I didn't look further into this problem as it is not related to the plugin. Maybe you can find more help in vagrant's issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants