From: Kyle Schmitt <kyleaschmitt@...>
Date: 2008-03-25T22:26:34+09:00
Subject: Re: Static Ruby

Along with Nobuyoshi's excellent advice, make sure you look in the
etc/Setup file.  You will probably need to edit it to select which
libs to include by default.  Very useful for making small static ruby
distributions you can move from machine to machine.

--Kyle

On Mon, Mar 24, 2008 at 1:39 PM, Marc Heiler <shevegen@linuxmail.org> wrote:
> Hi there,
>
>  typically I modify CFLAGS variable to include a pure
>  static version before compiling, as in:
>
>   CFLAGS='-static'
>
>  This works for sed, grep, bash etc.. easily, but for ruby,
>  this does not seem to work as straight forward.
>
>  If i invoke certain scripts that use md5 or similar "add-ons"
>  I get errors such as:
>
>   socket.so: undefined symbol: rb_eSecurityError
>
>  Sometimes different rb_e* Errors occur.
>
>  Someone else said that I should modify ext/Setup
>  but I am wondering whether this is the default route one
>  has to follow to get to a static version of ruby?
>
>  One reason i'd like to have it all inside one ruby
>  binary is that I dont want to have it fail if a host
>  lib is missing or broken.
>  (The size penalty is of no concern at all to me.)
>  --
>  Posted via http://www.ruby-forum.com/.
>
>