wdm
wdm copied to clipboard
WDM fails to install with no useable error message
Hello,
I am trying to install wdm
so that I can get started with jekyll (jekyll requires wdm
for watching files). However, the installation keeps failing with some (not very helpful) error messages.
Relevant version information:
Windows 10 Home 64-bit (version 1511)
> ruby -v
ruby 2.3.0p0 (2015-12-25 revision 53290) [x64-mingw32] # (installed via chocolatey)
> gem -v
2.5.1
# Ruby Devkit installed via:
> choco.exe install ruby2.devkit
# NOTE: chocolatey failed to automatically install, so I had to go to C:\tools\DevKit2 and
# complete installation myself.
Installation & logs
> gem install wdm -v '0.1.1'
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
ERROR: Error installing wdm:
ERROR: Failed to build gem native extension.
current directory: C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/wdm-0.1.1/ext/wdm
C:/tools/ruby23/bin/ruby.exe -r ./siteconf20160621-18176-1cmz67l.rb extconf.rb
checking for main() in -lkernel32... yes
checking for windows.h... yes
checking for ruby.h... yes
checking for HAVE_RUBY_ENCODING_H... yes
checking for rb_thread_call_without_gvl()... yes
creating Makefile
To see why this extension failed to compile, please check the mkmf.log which can be found here:
C:/tools/ruby23/lib/ruby/gems/2.3.0/extensions/x64-mingw32/2.3.0/wdm-0.1.1/mkmf.log
current directory: C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/wdm-0.1.1/ext/wdm
make "DESTDIR=" clean
current directory: C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/wdm-0.1.1/ext/wdm
make "DESTDIR="
make failed, exit code 1
Gem files will remain installed in C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/wdm-0.1.1 for inspection.
Results logged to C:/tools/ruby23/lib/ruby/gems/2.3.0/extensions/x64-mingw32/2.3.0/wdm-0.1.1/gem_make.out
I've attached mkmf.log
and gem_make.out
to this gist so that it doesn't make this issue painful to read :grin:
To me, the error messages are not entirely helpful. If possible, could someone take a look at this for me?
Thanks!
Was there ever a resolution for this? I'm running into the same issue.
I wasn't able to find a resolution, and none of the contributors ever replied :disappointed: