Multiple target patterns on Windows 10

[a1ee9b]

I encountered an error while installing this plugin on Windows 10 using the vagrant (1.9.1) native ruby (2.2.5p319 (2016-04-26 revision 54774) [i386-mingw32]). The plugin has never been installed before.

On the Windows version:

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      14393  0

ERROR: Failed to build gem native extension.

    "C:/Program Files (x86)/Vagrant/embedded/bin/ruby.exe" -r ./siteconf20161228-6168-1elpv5f.rb extconf.rb
checking for main() in -lssleay32... no
checking for main() in -lssleay32... no
checking for main() in -lssleay32... no
checking for main() in -lssleay32... no
checking for rb_trap_immediate in ruby.h,rubysig.h... no
checking for rb_thread_blocking_region()... no
checking for ruby/thread.h... yes
checking for rb_thread_call_without_gvl() in ruby/thread.h... yes
checking for inotify_init() in sys/inotify.h... no
checking for __NR_inotify_init in sys/syscall.h... no
checking for writev() in sys/uio.h... no
checking for rb_thread_fd_select()... yes
checking for rb_fdset_t in ruby/intern.h... yes
checking for pipe2() in unistd.h... no
checking for accept4() in sys/socket.h... no
checking for SOCK_CLOEXEC in sys/socket.h... no
checking for rb_wait_for_single_fd()... yes
checking for rb_enable_interrupt()... no
checking for rb_time_new()... yes
checking for windows.h... yes
checking for winsock.h... yes
checking for main() in -lkernel32... yes
checking for main() in -lrpcrt4... yes
checking for main() in -lgdi32... yes
checking for clock_gettime()... yes
checking for CLOCK_MONOTONIC_RAW in time.h... no
checking for CLOCK_MONOTONIC in time.h... yes
CXXFLAGS=$(cxxflags) -Wall -Wextra -Wno-deprecated-declarations -Wno-ignored-qualifiers -Wno-unused-result -Wno-address
creating Makefile

make "DESTDIR=" clean
Makefile:263: *** multiple target patterns.  Stop.

make "DESTDIR="
Makefile:263: *** multiple target patterns.  Stop.

make failed, exit code 2

[li-xin-yi]

The path of makefile contains spaces. Maybe reinstalling ruby with its dev kit in a directory without spaces can avoid the error.

It's always annoying to begin ruby with Windows.