[#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,

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


In This Thread

Prev Next