[#7955] Failing tests in ruby since 1.8.2 — "Caleb Tennis" <caleb@...>
The following tests have been failing in Ruby for a long time, including
[#7978] Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...>
This patch adds support for getting the uid and gid of the peer
In article <200606091528.30171.jfh@cise.ufl.edu>,
On Friday 16 June 2006 11:51, Tanaka Akira wrote:
In article <200606161327.35948.jfh@cise.ufl.edu>,
On Saturday 17 June 2006 06:27, Tanaka Akira wrote:
In article <200607101352.16804.jfh@cise.ufl.edu>,
On Tuesday 11 July 2006 00:10, Tanaka Akira wrote:
Hi,
On Thursday 13 July 2006 22:48, nobu@ruby-lang.org wrote:
On Jul 18, 2006, at 12:27 PM, James F. Hranicky wrote:
On Tuesday 18 July 2006 15:52, Eric Hodel wrote:
[#7994] Ruby Kaigi date confusion — "Charles O Nutter" <headius@...>
I'm quite confused by the dates I have seen reported on various Ruby Kaigi
[#8013] Download page on ruby-lang has numeric URL — Hugh Sasse <hgs@...>
This is off-topic to ruby-core, but possibly core to ruby's uptake:
On Jun 19, 2006, at 3:32 AM, Hugh Sasse wrote:
[#8038] bug in $. ? — Wybo Dekker <wybo@...>
wybo>cat t
Wybo Dekker schrieb:
Pit Capitain wrote:
[#8050] Thank-you to the Rails Core Team — Dave Teare <devlists-ruby-core@...>
While we were listening to Dave Thomas' Keynote address today at
[#8061] Win32 Extension Issues Wanted! — "Austin Ziegler" <halostatue@...>
Everyone. I had a conversation with folks from Microsoft today about
[#8065] Core documentation patches — Alex Young <alex@...>
Hi there,
Hi,
Yukihiro Matsumoto wrote:
[#8073] 1.8.5p1 build failure on Solaris 10 — "Daniel Berger" <Daniel.Berger@...>
Solaris 10
Hi,
Yukihiro Matsumoto wrote:
>>>>> "D" == Daniel Berger <Daniel.Berger@qwest.com> writes:
ts <decoux@moulon.inra.fr> wrote on 28.06.2006 17:37:00:
Hi,
Yukihiro Matsumoto <matz@ruby-lang.org> wrote on 29.06.2006 20:02:11:
Hi,
Yukihiro Matsumoto <matz@ruby-lang.org> wrote on 29.06.2006 20:53:20:
ville.mattila@stonesoft.com wrote:
[#8087] optparse.rb to RDoc documentation patch — <noreply@...>
Patches item #4879, was opened at 2006-06-28 20:50
On Jun 28, 2006, at 11:50 AM, <noreply@rubyforge.org>
[#8102] Reorganizing configure.in by platform? — "Daniel Berger" <Daniel.Berger@...>
Hi,
Re: Windows XP SP2 socket issues
|Can you explain it more? |Do you mean that there are some bugs? Sorry, I didn't mean to apply there were bugs with the patch. I think the patch is fine - it works great in 1.9...I assume it is something about the way I applied the patch and compiled the binaries on my machine. |Ruby 1.8 is compiled with winsock1, not winsock2. |To maintain the binary compatibility, I didn't scheduled to |backport the patch (which need to use winsock2). |However, in answer to your request, I decide to prepare a |little mechanism in 1.8. |In using a new configure option, users come to be able to |select whether to use winsock2. |I'll commit it later into 1.8, with ifs sockets patch. That would be great! Very much appreciated!!! On 6/6/06, U.Nakamura <usa@garbagecollect.jp> wrote: > > Hello, > > In message "Windows XP SP2 socket issues" > on Jun.06,2006 00:32:48, <dan.hatfield@gmail.com> wrote: > | 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. > > Can you explain it more? > Do you mean that there are some bugs? > > > | 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? > | :) > > Ruby 1.8 is compiled with winsock1, not winsock2. > To maintain the binary compatibility, I didn't scheduled to > backport the patch (which need to use winsock2). > > However, in answer to your request, I decide to prepare a > little mechanism in 1.8. > In using a new configure option, users come to be able to > select whether to use winsock2. > > I'll commit it later into 1.8, with ifs sockets patch. > > > Regards, > -- > U.Nakamura <usa@garbagecollect.jp> > > > >