developwithpassion / devtools

53 stars 22 forks source link

patching failing, compiling failing, had to switch versions of ruby to get it to work #4

Open FuriousFapper opened 9 years ago

FuriousFapper commented 9 years ago

When using the original setup with ruby 1.9.3 and 2.0.0. I would get the same errors over and over again no matter what libraries I installed, no matter if I launched cygwin from cygwin.bat or the desktop icon with admin privilleges. The errors I would consistently receive are the following. Oh I also installed dos2unix. First Error: Error running '__rvm_patch -F 25 -p1 -N -f -i /home/xxxxxxx/.rvm/patches/ruby/GH433.patch', showing last 15 lines of /home/xxxxxx/.rvm/log/1444927440_ruby-2.0.0-p643/patchapply.GH-433.log

_rvm_patch _rvm_patch() { \patch "$@" || return $? } current path : /home/xxxxxx/.rvm/src/ruby(either version number applies here) PATH= ALL of my enviromental paths but they lead with cydrive instead of C.

Second Error: ruby-1.9.3-p385 - #compiling.................. Error running '__rvm_make -j2', showing last 15 lines of /home/xxxxxx/.rvm/log/1444927113_ruby-1.9.3-p385/make.log

compiling process.c process.c: In function ‘rb_proc_exec_n’: process.c:1134:9: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable] int ret = -1; ^ process.c: In function ‘proc_initgroups’: process.c:4807:5: error: implicit declaration of function ‘initgroups’ [-Werror=implicit-function-declaration] if (initgroups(StringValuePtr(uname), NUM2GIDT(base_grp)) != 0) { ^ cc1: some warnings being treated as errors Makefile:287: recipe for target 'process.o' failed make: * [process.o] Error 1 make: * Waiting for unfinished jobs.... ++ return 2

Third not an error but an odd thing:

This kept appearing: Searching for binary rubies, this might take some time. No binary rubies available for: cygwin/unknown/i386/ruby-2.0.0-p643. Continuing with compilation. Please read 'rvm help mount' to get more informatin on binary rubies. Not sure what "Unknown" is supposed to be, but it still continued after this would occur.

After much googling and frustration, I found out that their is a bug in Ruby 1.9.3 and 2.0.0. That doesn't get fixed until 2.1.7. So, I am not sure how you were able to install this on a windows machine as I found cases all over the Internet where people were not able to install Ruby, RVM, using Cygwin utilizing these instructions. Yet there isn't even a note of it on this page, or in the "issues". If you are going to spend all of this time creating something like this, it seems logical that you would want people to succeed, so maybe you should make note of the bug, that has been recognized by ruby. Either that or patch the ruby source code, so it compiles properly.

felix-last commented 8 years ago

Thanks for posting this, saved further frustration! Installing 1.9.3-p392 caused the same error for me, but 1.9.3-p551 succeeded.