Hello Lothar,

LS> Hello Erik,

EV>> The problem with Linux is how to determine which dependencies
EV>> are to be distributed in the binary. On my system (RH8), Ruby
EV>> (the core and *.so) needs at least the following files (both
EV>> direct and indirect):

EV>>  /lib/ld-linux.so.2
EV>>  /lib/libNoVersion.so.1
EV>>  /lib/libc.so.6
EV>>  /lib/libcrypt.so.1
EV>>  /lib/libdl.so.2
EV>>  /lib/libgcc_s.so.1
EV>>  /lib/libm.so.6
EV>>  /lib/libnss_files.so.2
EV>>  /usr/lib/libgdbm.so.2
EV>>  /usr/lib/libncurses.so.5
EV>>  /usr/lib/libreadline.so.4

EV>> Can I assume that these are available on all modern
EV>> distributions, so I only need to distribute /usr/bin/ruby and
EV>> /usr/lib/libruby.so.1.6 (besides the "application-specific"
EV>> stripped rubylib tree)? What about the versions? Is 1.8 more 
EV>> complex? How can I test on several distributions,
EV>> cross-distribution? Anybody?


LS> Read Chapter 3 from

LS> http://www.linuxbase.org/modules.php?name=specrev&url=http://www.linuxbase.org/spec/booksets/LSB-Core/LSB-Core.html

Sorry hit the send button to quickly.
/lib/ld-linux.so.2 is AFAIK always absolutely addressed for security
reasons so you can't change it with your own LD_LIBRARY_PATH accessible lib.
And never bundle libgdbm.so.2/libreadline.so.4 without an explicit
request from the user. They are GPL not LGPL.




-- 
 Best regards,                        emailto: scholz at scriptolutions dot com
 Lothar Scholz                        http://www.ruby-ide.com
 CTO Scriptolutions                   Ruby, PHP, Python IDE 's