-
Notifications
You must be signed in to change notification settings - Fork 62
Windows install fails due to JSON gem dependency. #60
Comments
After further research, this doesn't appear to be a salty-vagrant problem and may not even be an issue with Vagrant itself. (If someone could clarify, that would be great.) However, I was able to resolve this issue: Poking around in some old issues in the Vagrant project led me to this Stackoverflow answer. I then downloaded
|
While I seem to have solved the JSON problem, unfortunately I'm still having an issue with salty-vagrant on Windows 7. The relevant output when I run
Any ideas? |
Well, for one salty-vagrant is not yet released for the latest vagrant. You will need to run <1.1. Sorry about that! Release should be out very shortly! |
Well, I guess that would explain it. :-) Confirmed that using Vagrant 1.0.7 doesn't result in these problems. Thank you for the quick suggestion. Closing. |
The original problem that I raised is still an issue on the latest release (using the new plugin system). The good news, however, is that the workaround I discovered also still works. Is the root issue solvable here or is something that needs to raised with the Vagrant project? |
Has this issue been resolved? |
Not noticing that this had been merged into vagrant core, I tried to install it as a plugin and still got this error. But since it's now in vagrant 1.3, this wasn't needed, so close this and maybe add a banner to the readme stating that it's no longer necessary to install this as a plugin? |
I'm not much of a Ruby guy, but it looks like there's a dependency on a JSON gem somewhere. This particular gem includes C extension that needs to be compiled, which causes the build to bomb on Windows:
Is there any way "json_pure" can be used to eliminate the need for the C extension?
The text was updated successfully, but these errors were encountered: