From: Dan Hatfield Date: 2006-06-06T00:32:48+09:00 Subject: Windows XP SP2 socket issues ------=_Part_30619_5615307.1149521564457 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I'm trying to determine the best course of action for myself on this issue (windows IFS sockets)... http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/5388 The patch has been applied to 1.9: http://www.ruby-lang.org/cgi-bin/cvsweb.cgi/ruby/win32/win32.c.diff?r1=1.154;r2=1.155;f=h I downloaded the latest 1.9 binary and it is indeed fixed. Of course, I need Ruby 1.8 for Rails... I had started down the path of patching ruby 1.8.4 and recompiling. I grabbed the latest --- 1.8.4-17 release candidate 2. And I patched the source as shown here: http://www.ruby-lang.org/cgi-bin/cvsweb.cgi/ruby/win32/win32.c.diff?r1=1.154;r2=1.155;f=h That's a bit naive I know. :) Interestingly, it generally appears to work but I appear to be blowing up when it tries to close the socket now. The other caveat is that I've been compiling ruby using VS2005 Express Edition (I've followed the exchanges with Austin Ziegler on this mailing list). That's actually been pretty painless as the details are documented well in this mailing list. My questions are: 1) Is there any effort to get this ifs sockets patch into 1.8 currently? With 1.9 being an experimental branch and Ruby 2.0 not coming anytime soon, I'm thinking this problem will be growing an importance as more people end up on XP SP2. 2) Or should I just continue down the path of recompiling my own binaries? And if so, is there anyone out there that knows enough about these ifs sockets to help me debug my patch? 3) Or am I better off trying to get rails to run under 1.9 (that may not be a question for this list, I can post in on rails devel)? 4) Or should I just punt and go for a dual boot with FreeBSD or something? :) Thanks in advance for any advice you can offer. Dan ------=_Part_30619_5615307.1149521564457--