-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
cannot load such file -- ffi_c #648
Comments
Ah 64-bit. Yay. I'll investigate and see if I can get to the bottom of this. |
Can you give this a shot? http://stackoverflow.com/questions/7964778/no-such-file-to-load-ffi-c-loaderror FFI is a dependency of a dependency on Vagrant, so I'll let that gem author know as well. |
Also, what version of FFI is installed now? |
Looks like this issue. |
I uninstalled all ffi gems except ffi-1.0.9-x86-mingw32. Then, vagrant worked. Thus, it is the issue @jarib mentioned with the follow up of ffi/ffi#182 , which sadly have not been resolved. Finally, I can use Ruby 1.9.3 MRI with Vagrant on Win7 :) Thanks! |
Great! So dumb. Closing this issue because this is really an FFI issue and I don't think locking Vagrant to FFI 1.0.9 is a good choice. |
When using vagrant 0.9 on win 7 64bit with ruby 1.9.3 p0 MRI, the command
vagrant init
works as expected. However, invokingvagrant up
next results in this error:The text was updated successfully, but these errors were encountered: