Thank you! On Thursday, October 26, 2017 at 3:29:55 PM UTC-4, Alvaro Miranda Aguilera wrote: > > Hello Eric > > Sorry for the delay there. > > A bug has been identified and plugin 5.0.1 should be released shortly. > > That will include a fix for the issue you are seeing. > > Thanks > Alvaro. > > On Thu, Oct 26, 2017 at 12:35 PM, Eric Beach <[email protected] > <javascript:>> wrote: > >> I get pretty much the same result when trying to install the Workstation >> plugin. No response from Support, as of yet. >> >> >> >> PS C:\> vagrant plugin install vagrant-vmware-workstation >> Installing the 'vagrant-vmware-workstation' plugin. This can take a few >> minutes... >> Building native extensions. This could take a while... >> >> >> Vagrant is installing the VMware plugin which requires >> Administrator access. You may be prompted for your password to >> complete setup. >> >> >> Failed to complete install: exec: "H:\\windows\\system32\\wbem\\wmic.exe" >> : file does not exist >> Bundler, the underlying system Vagrant uses to install plugins, >> reported an error. The error is shown below. These errors are usually >> caused by misconfigured plugin installations or transient network >> issues. The error from Bundler is: >> >> >> ERROR: Failed to build gem native extension. >> >> >> current directory: C:/Users/xxxx/.vagrant.d/gems/2.3.4/gems/vagrant- >> vmware-workstation-5.0.0/ext/vagrant-vmware-desktop >> C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r ./siteconf20171026- >> 146968-1oumt80.rb extconf.rb >> *** 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 >> ) >> >> >> extconf failed, exit code 1 >> >> >> Gem files will remain installed in C:/Users/xxxx/.vagrant.d/gems/2.3.4/ >> gems/vagrant-vmware-workstation-5.0.0 for inspection. >> Results logged to C:/Users/xxxx/.vagrant.d/gems/2.3.4/extensions/x64- >> mingw32/2.3.0/vagrant-vmware-workstation-5.0.0/gem_make.out >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/a4f448a7-6979-44b2-9b76-fc6fc28cf8b0%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/a4f448a7-6979-44b2-9b76-fc6fc28cf8b0%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > >
-- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/064764b9-912e-4d24-bac4-26132a06661e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
