[#237] object.c ruby.h (fwd) — Robert Skarwecki <skaav@...>

Hello everybody,

42 messages 2002/07/24
[#239] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/24

At Thu, 25 Jul 2002 00:02:28 +0900,

[#240] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/24

GOTO Kentaro <gotoken@notwork.org> writes:

[#246] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/25

At Thu, 25 Jul 2002 05:05:46 +0900,

[#247] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

GOTO Kentaro <gotoken@notwork.org> writes:

[#248] Re: [PATCH] object.c ruby.h (fwd) — nobu.nokada@... 2002/07/25

Hi,

[#249] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

nobu.nokada@softhome.net writes:

[#250] Re: [PATCH] object.c ruby.h (fwd) — nobu.nokada@... 2002/07/25

Hi,

[#252] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/25

At Fri, 26 Jul 2002 03:11:02 +0900,

[#253] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

GOTO Kentaro <gotoken@notwork.org> writes:

Re: Questions about installing in a corporate WAN

From: ts <decoux@...>
Date: 2002-07-28 12:04:45 UTC
List: ruby-core #273
>>>>> "J" == Jim Freeze <jim@freeze.org> writes:

J>  1) A statically linked ruby.
J>     This may or may not be the best solution. I have considered
J>     this becuase there is one site that may not have the standard
J>     libraries (see ext/Setup) needed to have ruby execute 
J>     successfully. I have tried static linking, but the .so
J>     files are still required. I am definitly lacking in my 
J>     understanding of static/shared libraries.

 Well, if you want a statically linked ruby, you must compile it with
 -static but I think that it's not possible to do it on Solaris

J>    a) have each sysadmin install ruby as they see fit.
J>       This means setting the with-sitedir as they wish.

 The installation of ruby is made from the official ruby distribution
 (ie. ruby-1.6.7.tar.gz) or this package can be modified ?

J>    b) have the wrapper set RUBYLIB (and possibly DLN_LIBRARY_PATH)
J>       so local installs can find the ruby libs pushed out in the workflow.

 If you can modify it, just add an extension which will be build
 *statically* when the sysadmin install ruby and this extension just
 modify RUBYLIB (internally). Because it do this when ruby call the
 initialisation you don't have problems with $SAFE


Guy Decoux

In This Thread