Ruby 1.8.4 and Windows XP SP2 socket problems

Thread: Ruby 1.8.4 and Windows XP SP2 socket problems

Search this list only Search all lists
Ruby 1.8.4 and Windows XP SP2 socket problems
	2006-06-05 01:16:58

Hi Curt, 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 does indeed solve the issue. Of course, I need Ruby 1.8 for Rails... I had started down the path of patching ruby 1.8.4 and recompiling. I've followed Austin Ziegler's path on Visual Studio C++ 2005 Express Edition with some success and I have a compiled ruby (and the socket problem appears fixed). Now I've just realized I have to also recompile zlib, etc.... So now, I'm wondering - is there any effort to get this patch into 1.8 at all? Or into your one-click installer for Windows? With 1.9 being an experimental branch and Ruby 2.0 not being anytime soon, I'm thinking this problem will be growing an importance as more people end up on XP SP2. Or should I just continue down the path of recompiling my own binaries? And if so, is your one-click installer a good place to go ( i.e. download your tarball and attempt to build from there)? Thanks in advance for any advice you can offer. Dan
Ruby 1.8.4 and Windows XP SP2 socket problems
	2006-06-05 02:15:15

On 6/4/06, Dan Hatfield <gmail.com">dan.hatfieldgmail.com> wrote: Hi Curt, 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 does indeed solve the issue. Of course, I need Ruby 1.8 for Rails... I had started down the path of patching ruby 1.8.4 and recompiling. I've followed Austin Ziegler's path on Visual Studio C++ 2005 Express Edition with some success and I have a compiled ruby (and the socket problem appears fixed). Now I've just realized I have to also recompile zlib, etc.... If you're going to compile yourself, you really want to use VC++ 6,otherwise you'll end up with all kinds of compatibility problems with other binary libs. So now, I'm wondering - is there any effort to get this patch into 1.8 at all? Or into your one-click installer for Windows? With 1.9 being an experimental branch and Ruby 2.0 not being anytime soon, I'm thinking this problem will be growing an importance as more people end up on XP SP2. I have no idea... I'm not part of the core ruby developer team. Or should I just continue down the path of recompiling my own binaries? And if so, is your one-click installer a good place to go ( i.e. download your tarball and attempt to build from there)? I no longer build the Ruby binary from source for the one-click installer. Instead, I pick up the binary built by the core Ruby development team (which is build using VC++ 6). Thanks in advance for any advice you can offer. Dan I'd suggest asking on the ruby-core ML if this fix is going to be back-ported to 1.8.4. Curt
Ruby 1.8.4 and Windows XP SP2 socket problems
	2006-06-05 15:04:33

Ok, thanks. Didn't realize you weren't building the binary on your own. ; On 6/4/06, Curt Hibbs <gmail.com">curt.hibbsgmail.com> wrote: On 6/4/06, Dan Hatfield <gmail.com" target="_blank">dan.hatfieldgmail.com> wrote: Hi Curt, 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 does indeed solve the issue. Of course, I need Ruby 1.8 for Rails... I had started down the path of patching ruby 1.8.4 and recompiling. I've followed Austin Ziegler's path on Visual Studio C++ 2005 Express Edition with some success and I have a compiled ruby (and the socket problem appears fixed). Now I've just realized I have to also recompile zlib, etc.... If you're going to compile yourself, you really want to use VC++ 6,otherwise you'll end up with all kinds of compatibility problems with other binary libs. So now, I'm wondering - is there any effort to get this patch into 1.8 at all? Or into your one-click installer for Windows? With 1.9 being an experimental branch and Ruby 2.0 not being anytime soon, I'm thinking this problem will be growing an importance as more people end up on XP SP2. I have no idea... I'm not part of the core ruby developer team. Or should I just continue down the path of recompiling my own binaries? And if so, is your one-click installer a good place to go ( i.e. download your tarball and attempt to build from there)? I no longer build the Ruby binary from source for the one-click installer. Instead, I pick up the binary built by the core Ruby development team (which is build using VC++ 6). Thanks in advance for any advice you can offer.   Dan I'd suggest asking on the ruby-core ML if this fix is going to be back-ported to 1.8.4. Curt     _______________________________________________ Rubyinstaller-devel mailing list rubyforge.org">Rubyinstaller-develrubyforge.org http://rubyforge.org/mailman/listinfo/rubyinstaller-devel

[1-3]

about | contact Other archives ( Real Estate discussion Medical topics )