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

cannot load such file -- ffi_c #648

Closed
simonharrer opened this issue Jan 18, 2012 · 6 comments
Closed

cannot load such file -- ffi_c #648

simonharrer opened this issue Jan 18, 2012 · 6 comments

Comments

@simonharrer
Copy link

When using vagrant 0.9 on win 7 64bit with ruby 1.9.3 p0 MRI, the command vagrant init works as expected. However, invoking vagrant up next results in this error:

c:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:59:in `require': cannot load such file -- ffi_c (LoadError)
    from c:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:59:in `rescue in require'
    from c:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:35:in `require'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/ffi-1.0.11-x86-mingw32/lib/ffi.rb:11:in `rescue in <top (required)>'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/ffi-1.0.11-x86-mingw32/lib/ffi.rb:2:in `<top (required)>'
    from c:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
    from c:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/childprocess-0.3.0/lib/childprocess/windows.rb:1:in `<top (required)>'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/childprocess-0.3.0/lib/childprocess.rb:23:in `new'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/util/subprocess.rb:36:in `execute'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/util/subprocess.rb:20:in `execute'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox_base.rb:279:in `block in raw'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/util/busy.rb:19:in `busy'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox_base.rb:278:in `raw'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox_base.rb:254:in `execute'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox.rb:117:in `read_version'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox.rb:36:in `initialize'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/vm.rb:129:in `new'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/vm.rb:129:in `reload!'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/vm.rb:35:in `initialize'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:426:in `new'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:426:in `block in load_vms!'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:425:in `each'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:425:in `load_vms!'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:114:in `vms'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:147:in `multivm?'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:122:in `vms_ordered'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/command/base.rb:88:in `with_target_vms'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/command/up.rb:39:in `execute'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/cli.rb:38:in `execute'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/lib/vagrant/environment.rb:156:in `cli'
    from c:/Ruby193/lib/ruby/gems/1.9.1/gems/vagrant-0.9.0/bin/vagrant:43:in `<top (required)>'
    from c:/Ruby193/bin/vagrant:19:in `load'
    from c:/Ruby193/bin/vagrant:19:in `<main>'
@mitchellh
Copy link
Contributor

Ah 64-bit. Yay. I'll investigate and see if I can get to the bottom of this.

@mitchellh
Copy link
Contributor

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.

@mitchellh
Copy link
Contributor

Also, what version of FFI is installed now?

@jarib
Copy link

jarib commented Jan 19, 2012

Looks like this issue.

@simonharrer
Copy link
Author

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!

@mitchellh
Copy link
Contributor

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.

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

No branches or pull requests

3 participants