[#3726] Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...>

Hi --

15 messages 2004/11/12
[#3749] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3751] Re: Fixnum#clone and Float#clone raise different exceptions — Yukihiro Matsumoto <matz@...> 2004/11/16

Hi,

[#3752] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3785] The latest 1.8.2 cvs prints parse error when starting extension compiling — Yukihiro Matsumoto <matz@...>

Hi,

13 messages 2004/11/23
[#3787] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling — Johan Holmberg <holmberg@...> 2004/11/23

Re: The latest 1.8.2 cvs prints parse error when starting extension compiling

From: Yukihiro Matsumoto <matz@...>
Date: 2004-11-23 16:11:46 UTC
List: ruby-core #3792
Hi,

In message "Re: The latest 1.8.2 cvs prints parse error when starting extension compiling"
    on Tue, 23 Nov 2004 23:04:42 +0900, ts <decoux@moulon.inra.fr> writes:

| Apparently this is 
|
|#define HAVE___FPENDING 1
|
|  which it don't like

I see.  This was introduced to solve [ruby-code:3766] submitted by
Steven Lumos (slumos).  He said the fix was required for 64 bit
Solaris, which apparently break Ruby on 32 bit Solaris.

Would somebody with Solaris platform (32 bit and 64 bit) supply the
following information?

  * is there any way to 32 bit Solaris to make __fpending() work as
    expected?

  * or compiler flags (that can be checked by defined()) to
    distinguish 64 bit Solaris from 32 bit Solaris?

Thanks in advance.

							matz.

In This Thread