[#995] Mathn crashes the interpreter on PPC — Dave Thomas <dave@...>
The following code crashes the interpreter on my Powerbook:
4 messages
2003/05/01
[#1004] irb doesn't work, because tempfile doesn't work — Dave Thomas <dave@...>
Try
7 messages
2003/05/02
[#1005] Re: irb doesn't work, because tempfile doesn't work
— matz@... (Yukihiro Matsumoto)
2003/05/02
Hi,
[#1018] Re: ext/syck problems — why the lucky stiff <ruby-core@...>
U.Nakamura (usa@osb.att.ne.jp) wrote:
8 messages
2003/05/13
[#1037] ping.rb — Dave Thomas <dave@...>
On my Mac OSX,
15 messages
2003/05/14
[#1039] Re: ping.rb
— Ryan Davis <ryand@...>
2003/05/15
[#1040] Re: ping.rb
— Dave Thomas <dave@...>
2003/05/15
Ryan Davis wrote:
[#1042] Re: ping.rb
— nobu.nokada@...
2003/05/15
Hi,
[#1043] Re: ping.rb
— Dave Thomas <dave@...>
2003/05/15
nobu.nokada@softhome.net wrote:
[#1057] Fwd: ping.rb — "J.Herre" <jlst@...>
7 messages
2003/05/16
[#1066] YAML problem — Tanaka Akira <akr@...17n.org>
I found a problem with yaml.
12 messages
2003/05/22
[#1067] Re: YAML problem
— "NAKAMURA, Hiroshi" <nahi@...>
2003/05/22
Hi,
[#1068] Re: YAML problem
— why the lucky stiff <ruby-core@...>
2003/05/22
Concerning error from:
[#1069] Re: YAML problem
— Tanaka Akira <akr@...17n.org>
2003/05/22
In article <20030522064450.GA14175@rysa.inetz.com>,
[#1077] terminated object / invalid inspect_tbl — ts <decoux@...>
10 messages
2003/05/26
[#1078] Re: [1.8] terminated object / invalid inspect_tbl
— nobu.nokada@...
2003/05/26
Hi,
[#1079] Re: [1.8] terminated object / invalid inspect_tbl
— ts <decoux@...>
2003/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#1080] Re: [1.8] terminated object / invalid inspect_tbl
— nobu.nokada@...
2003/05/26
Hi,
[#1081] Re: [1.8] terminated object / invalid inspect_tbl
— ts <decoux@...>
2003/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#1085] Re: [1.8] terminated object / invalid inspect_tbl
— nobu.nokada@...
2003/05/26
Hi,
[#1082] Possible problem with mkmf under Darwin — Dave Thomas <dave@...>
I've been having fun getting readline support to work on OSX. My latest
7 messages
2003/05/26
[#1094] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c — Dave Thomas <dave@...>
> * eval.c (rb_mod_autoload, rb_mod_autoload_p): new method;
12 messages
2003/05/29
[#1095] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— nobu.nokada@...
2003/05/29
Hi,
[#1097] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— Dave Thomas <dave@...>
2003/05/29
nobu.nokada@softhome.net wrote:
[#1101] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— nobu.nokada@...
2003/05/29
Hi,
[#1102] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— matz@... (Yukihiro Matsumoto)
2003/05/30
Hi,
Re: large file compilation issue on solaris with 1.8
From:
Johan Holmberg <holmberg@...>
Date:
2003-05-30 21:56:14 UTC
List:
ruby-core #1108
On Sat, 31 May 2003, Daniel Berger wrote:
>
> When I try to include the sys/procfs.h lib (in this case, from my
> sys-proctable package), I get this:
>
[...]
> /usr/include/sys/procfs.h:44:2: #error "Cannot use procfs in the large
> file compilation environment"
> make: *** [proctable.o] Error 1
>
> I don't have this issue with 1.6.8
>
> Any ideas?
>
I think Ruby has started to support large files since 1.6.8.
As far as I understand large files can be supported in two ways on
Solaris:
1) by making an application a 64-bit application
2) by enabling large file support by setting _FILE_OFFSET_BITS = 64.
The "configure" step of Ruby does this automatically on Solaris.
I assume that 1) was never an option for Ruby (e.g. pointer would
be 64-bit then). I also think that the #error line in "procfs.h"
just states the fact that you pay a price if you choose 2) above.
The little things I know about this I learned from "Solaris 7 64-bit
Developer's Guide" (available on Suns web-site). The /proc stuff is
mentioned explicitly there as an issue to think about.
( I hope my description above is consistent with that paper ... )
If you don't need large file support, I guess you could just disable
that and get your /proc stuff working in a "pure 32-bit world".
Does this help ?
/Johan Holmberg