I am having an issue with vagrant where I have build the extension like the
vagrant output suggested, however, when I attempt to run 'vagrant up'
vagrant behaves like I have not built the extension. Does anyone know
where I might be going wrong?
------------------
e:\sandbox\vagrant_esdk>chef gem pristine dep-selector-libgecode --version
1.0.2
Restoring gems to pristine condition...
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
Restored dep-selector-libgecode-1.0.2
e:\sandbox\vagrant_esdk>chef gem pristine dep_selector --version 1.0.3
Restoring gems to pristine condition...
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
Restored dep_selector-1.0.3
e:\sandbox\vagrant_esdk>chef gem pristine nio4r --version 1.2.0
Restoring gems to pristine condition...
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
Restored nio4r-1.2.0
e:\sandbox\vagrant_esdk>chef gem pristine json --version 1.8.3
Restoring gems to pristine condition...
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
Restored json-1.8.3
e:\sandbox\vagrant_esdk>chef gem pristine wdm --version 0.1.1
ERROR: While executing gem ... (Gem::Exception)
Failed to find gems ["wdm"] = 0.1.1
e:\sandbox\vagrant_esdk>chef gem install wdm
Fetching: wdm-0.1.1.gem (100%)
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
Successfully installed wdm-0.1.1
Parsing documentation for wdm-0.1.1
Installing ri documentation for wdm-0.1.1
Done installing documentation for wdm after 0 seconds
1 gem installed
e:\sandbox\vagrant_esdk>chef gem pristine wdm --version 0.1.1
Restoring gems to pristine condition...
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
Restored wdm-0.1.1
e:\sandbox\vagrant_esdk>vagrant up
Bringing machine 'esdk_sync' up with 'virtualbox' provider...
The following berks command failed to execute:
c:\users\kaleb.albee\appdata\local\chefdk\gem\ruby\2.1.0\bin/berks.BAT
--version --format json
The stdout and stderr are shown below:
stdout:
stderr: Ignoring dep-selector-libgecode-1.0.2 because its extensions
are not built. Try: gem pristine dep-selector-libgecode --version 1.0.2
Ignoring dep_selector-1.0.3 because its extensions are not built. Try: gem
pristine dep_selector --version 1.0.3
Ignoring nio4r-1.2.0 because its extensions are not built. Try: gem
pristine nio4r --version 1.2.0
Ignoring json-1.8.3 because its extensions are not built. Try: gem
pristine json --version 1.8.3
Ignoring wdm-0.1.1 because its extensions are not built. Try: gem pristine
wdm --version 0.1.1
C:/Users/kaleb.albee/.vagrant.d/gems/gems/httpclient-2.6.0.1/lib/httpclient/webagent-cookie.rb:458:
warning: already initialized constant HTTPClient::CookieManager
C:/Users/kaleb.albee/.vagrant.d/gems/gems/httpclient-2.6.0.1/lib/httpclient/cookie.rb:8:
warning: previous definition of CookieManager was here
C:/HashiCorp/Vagrant/embedded/gems/gems/ffi-1.9.10-x86-mingw32/lib/ffi/library.rb:133:in
`block in ffi_lib': Could not open library
'C:\Users\kaleb.albee\.vagrant.d\gems\gems\dep_selector-1.0.3\lib\dep_gecode.so':
The specified module cou
(LoadError)d.
--
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/3f16563b-12e8-43c2-b53c-29613a4f6280%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
