Open tribbloid opened 8 years ago
vagrant plugins are essentially Ruby gems. you can use
$ gem install vagrant-aws
to debug the issue. it's probably trying to install a gem that uses native extensions.
you can try the following
$ sudo apt-get install ruby1.9.1-dev
I'd the same issue with mac osx install with vagrant 1.8.3 I'd juste upgrade within 1.8.4 and the issue gone away https://releases.hashicorp.com/vagrant/1.8.4/
I saw the error Failed to build gem native extension
too on CentOS 7.3 and vagrant 1.8.7.
I resolved it after installing ruby-devel and gcc (yum -y install ruby-devel gcc
)
Trying to install on Ruby 1.9.3 and vagrant 1.4.3. End up with the following error message:
Gem files will remain installed in /home/ubuntu/.vagrant.d/gems/gems/nokogiri-1.6.7.2 for inspection. Results logged to /home/ubuntu/.vagrant.d/gems/gems/nokogiri-1.6.7.2/ext/nokogiri/gem_make.out from /usr/lib/ruby/1.9.1/rubygems/installer.rb:540:in'
block in build_extensions' from /usr/lib/ruby/1.9.1/rubygems/installer.rb:515:in
each' from /usr/lib/ruby/1.9.1/rubygems/installer.rb:515:inbuild_extensions' from /usr/lib/ruby/1.9.1/rubygems/installer.rb:180:in
install' from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:297:inblock in install' from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in
each' from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:ineach_with_index' from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in
install' from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:65:inblock in call' from /usr/share/vagrant/plugins/commands/plugin/gem_helper.rb:42:in
block in with_environment' from /usr/lib/ruby/1.9.1/rubygems/user_interaction.rb:40:inuse_ui' from /usr/share/vagrant/plugins/commands/plugin/gem_helper.rb:41:in
with_environment' from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:52:incall' from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in
call' from /usr/share/vagrant/plugins/commands/plugin/action/bundler_check.rb:20:incall' from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in
call' from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:incall' from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in
block in run' from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:inbusy' from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in
run' from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:17:inaction' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:27:in
execute' from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:inexecute' from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:38:in
execute' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:484:incli' from /usr/bin/vagrant:127:in
Is this a compatibility issue?