[Win32utils-devel] win32-daemon 0.6.1 problem

Heesob Park phasis at gmail.com
Wed Nov 5 20:08:34 EST 2008


2008/11/6 Berger, Daniel <Daniel.Berger at qwest.com>:
>
>
>> -----Original Message-----
>> From: win32utils-devel-bounces at rubyforge.org
>> [mailto:win32utils-devel-bounces at rubyforge.org] On Behalf Of
>> Park Heesob
>> Sent: Wednesday, November 05, 2008 8:56 AM
>> To: Development and ideas for win32utils projects
>> Subject: Re: [Win32utils-devel] win32-daemon 0.6.1 problem
>>
>>
>> ----- Original Message -----
>> From: "Berger, Daniel" <Daniel.Berger at qwest.com>
>> To: "Development and ideas for win32utils projects"
>> <win32utils-devel at rubyforge.org>
>> Sent: Tuesday, November 04, 2008 1:23 AM
>> Subject: Re: [Win32utils-devel] win32-daemon 0.6.1 problem
>> >
>> > PS - Maybe it's time to revisit
>> >
>> http://rubyforge.org/tracker/index.php?func=detail&aid=16627&group_id=
>> > 85
>> > &atid=413, too.
>> >
>> Here is the new version using TCP protocal.
>
> <snip>
>
> Wow, excellent. Thanks for all your hard work!
>
> Do you prefer this implementation to the other one?
>
> The _only_ downside I see here is the socket/runtime issue with the one
> click installer. If we ship this version, I think we must ship our own
> socket.so, too. That, or we rewrite the socket library using win32-api
> or ffi, and make that a dependency, but I think that's a last resort.
>
The socket/runtime issue is a ruby-core win32.c issue related with the
USE_WINSOCK2 macro. The current quick workaround is running
configure.bat without --with-winsock2 option. Is there any special
reason One-Click Ruby Installer team built Ruby with --with-winsock2
option?

Regards,

Park Heesob


More information about the win32utils-devel mailing list