vagrant-aws
vagrant-aws copied to clipboard
could not install on windows 10, Vagrant 2.2.13
I see there are many (mostly closed without resolution) issues with workarounds which don't generally work.
Should I expect vagrant plugin install vagrant-aws
to work on windows 10 and Vagrant 2.2.13? (without additional steps, if there are any, please document them)
thank you
vagrant plugin install vagrant-aws
Installing the 'vagrant-aws' plugin. This can take a few minutes...
Nokogiri is built with the packaged libraries: libxml2-2.9.10, libxslt-1.1.34, zlib-1.2.11, libiconv-1.15.
Building native extensions. This could take a while...
Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations
or transient network issues. The reported error is:
ERROR: Failed to build gem native extension.
current directory: C:/Users/amitp/.vagrant.d/gems/2.6.6/gems/ovirt-engine-sdk-4.4.0/ext/ovirtsdk4c
C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -I C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.6.0 -r ./siteconf20201117-12744-i63bon.rb extconf.rb
checking for xml2-config... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=C:/HashiCorp/Vagrant/embedded/mingw64/bin/$(RUBY_BASE_NAME)
--with-libxml2-config
--without-libxml2-config
--with-pkg-config
--without-pkg-config
extconf.rb:29:in `<main>': The "libxml2" package isn't available. (RuntimeError)
To see why this extension failed to compile, please check the mkmf.log which can be found here:
C:/Users/amitp/.vagrant.d/gems/2.6.6/extensions/x64-mingw32/2.6.0/ovirt-engine-sdk-4.4.0/mkmf.log
extconf failed, exit code 1
Gem files will remain installed in C:/Users/amitp/.vagrant.d/gems/2.6.6/gems/ovirt-engine-sdk-4.4.0 for inspection.
Results logged to C:/Users/amitp/.vagrant.d/gems/2.6.6/extensions/x64-mingw32/2.6.0/ovirt-engine-sdk-4.4.0/gem_make.out
I have the exact same issue.