[#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: 1.8.5p1 build failure on Solaris 10
ville.mattila@stonesoft.com wrote: > "Daniel Berger" <Daniel.Berger@qwest.com> wrote on 29.06.2006 22:57:10: > >> ville.mattila@stonesoft.com wrote: >>> -solaris*2.10) ac_cv_func_isinf=yes >>> +solaris*2.10) if test -z "$GCC"; then >>> + ac_cv_func_isinf=yes >>> + fi >>> LIBS="-lm $LIBS" >>> ;; >>> *) LIBS="-lm $LIBS";; >>> >>> >> Actually, shouldn't we test for the feature instead of the platform? I > don't >> remember if older versions of Solaris have this. >> >> So, AC_CHECK_LIB(sunmath, isinf) && AC_CHECK_HEADER(sunmath.h, isinf), > with >> #ifdef's in the source? >> > > I think this would add more code to source, now we only have to touch to > > configure.in. > > - Ville > > I don't totally understand how the build process works, which is part of my problem. For example, I see a missing.h, and I can see AC_REPLACE_FUNCS in the configure.in file, but I'm not sure if/how they're tied together. Within missing.h I see this: #ifndef HAVE_ISINF # if defined(HAVE_FINITE) && defined(HAVE_ISNAN) # define isinf(x) (!finite(x) && !isnan(x)) # else extern int isinf _((double)); # endif #endif So, in simple terms I think the logic should be: a) On the Solaris platform... b) If a) is true and the sunmath lib is present, and it contains the isinf function, then link against it. c) If both a) and b) are true and the sunmath.h header file is present, and it contains the isinf function, then include it. d) If a) or b) fail then resort to the implementation in missing.h. This wouldn't require adding more source code from what I can gather, though I'm not positive. Does that seem reasonable? I would try to implement this myself, but I'm not sure how. Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.