search

agiledivider / vagrant-hostsupdater

MIT License
1.15k stars 129 forks source link

vagrant-hostupdater failing to install #115

Closed tom-smalls closed 8 years ago

tom-smalls commented 8 years ago

I'm not sure if this is an error with the plugin, or vagrant itself.

The vagrant-hostupdater started failing to install for us last night (in the UK) with the following error:

Bundler, the underlying system Vagrant uses to install plugins,\nreported an error. The error is shown below. These errors are usually\ncaused by misconfigured plugin installations or transient network\nissues. The error from Bundler is:\n\nAn error occurred while installing ffi (1.9.12), and Bundler cannot continue.\nMake sure that gem install ffi -v '1.9.12' succeeds before bundling.\n\nWarning: this Gemfile contains multiple primary sources. Using source more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run bundle config disable_multisource true.Gem::Ext::BuildError: ERROR: Failed to build gem native extension.\n\n /opt/vagrant/embedded/bin/ruby -r ./siteconf20160706-8962-cyjadj.rb extconf.rb\nchecking for ffi.h... no\nchecking for ffi.h in /usr/local/include,/usr/include/ffi... no\nchecking for rb_thread_blocking_region()... no\nchecking for rb_thread_call_with_gvl()... yes\nchecking for rb_thread_call_without_gvl()... yes\nchecking for ffi_prep_cif_var()... no\ncreating extconf.h\ncreating Makefile\n\nmake \"DESTDIR=\" clean\nsh: make: command not found\n\nmake \"DESTDIR=\"\nsh: make: command not found\n\nmake failed, exit code 127\n\nGem files will remain installed in /root/.vagrant.d/gems/gems/ffi-1.9.12 for inspection.\nResults logged to /root/.vagrant.d/gems/extensions/x86_64-linux/2.2.0/ffi-1.9.12/gem_make.out

This is on a Centos 7 machine. May be related to https://github.com/mitchellh/vagrant/issues/7549

tom-smalls commented 8 years ago

I noticed that FFI had new versions released over the past few days (https://rubygems.org/gems/ffi), but not sure where it sits on the dependency graph.

tom-smalls commented 8 years ago

This appears to have been a problem with FFI 1.19.2 (see https://github.com/ffi/ffi/issues/510), and a new version has been fixed to resolve the issue.