Solaris and ruby libraries

ruby-talk
1

Are there any well-known gotchas/pitfalls when configuring and compiling
ruby on Solaris? Someone I know has done an installation and found that
the interpreter can’t find its shared libraries (e.g., “require
’socket’” fails). I don’t know any more details than that yet. Maybe
they did something dumb, but I thought I’d check here before diving into
troubleshooting with them.

TIA

Mark

2

I’ve found that if you comment out the “socket” lib in the ext/Setup file
when you install Ruby, this error can occur (which seems rather
counter-intuitive to me). In fact, what is the “socket” in ext/Setup? How
is it different from the regular socket lib?

If this happens for every lib you try to require (and not just socket),
then try rebuilding with the --enable-shared option.

If that still doesn’t work, try setting your LD_LIBRARY_PATH to point to
the Ruby lib path.

Regards,

Dan

Mark Slagell wrote:

···

Are there any well-known gotchas/pitfalls when configuring and compiling
ruby on Solaris? Someone I know has done an installation and found that
the interpreter can’t find its shared libraries (e.g., “require
‘socket’” fails). I don’t know any more details than that yet. Maybe
they did something dumb, but I thought I’d check here before diving into
troubleshooting with them.

TIA

Mark

3

I've found that if you comment out the "socket" lib in the ext/Setup file

From the README

  4. Remove comment mark(#) before the module names from ext/Setup (or
     add module names if not present), if you want to link modules
     statically.

Guy Decoux

4

Thanks for the replies. I’ll pass the information along and see if any
of it helps.

Mark

ts wrote:

···

“D” == Daniel Berger djberge@qwest.com writes:

I’ve found that if you comment out the “socket” lib in the ext/Setup file

From the README

  1. Remove comment mark(#) before the module names from ext/Setup (or
    add module names if not present), if you want to link modules
    statically.

Guy Decoux

5

I’ve found that if you comment out the “socket” lib in the
ext/Setup file

From the README

  1. Remove comment mark(#) before the module names from ext/Setup (or
    add module names if not present), if you want to link modules
    statically.

Guy Decoux

Well, they reinstalled it and all was fine. They must have done
something differently the second time.