M
Marc Heiler
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.)
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.)