Sandor, I'm not sure if it is a SUSE problem. As described the same setup works perfectly on SLES 9 32 bit workstations. I more think there is something wrong with the 64 bit rpms or the 64 bit ruby version.
I used now the ldd command to list the libraries ruby is linked against. As you recognized already the openssl is actually not linked to ruby. libdl.so.2 => /lib64/libdl.so.2 (0x0000002a9566d000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000002a95770000) libm.so.6 => /lib64/tls/libm.so.6 (0x0000002a958a8000) libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a95a00000) /lib64/ld-linux-x86-64.so.2 (0x0000002a95556000) Your solution suggestion i don't understand completely ... $ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"' Which term i should use to replace "foo"? Sorry i'm not (yet) a ruby expert. Christian On Oct 1, 8:50 am, Sandor Szuecs <sandor.szu...@fu-berlin.de> wrote: > On Oct 1, 2010, at 10:29 AM, Christian wrote: > > > Some idea how to solve that problem and how i can make the ./ > > openssl.so loadable? > > You can try the following: > $ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"' > > Is you ruby installation linked against openssl.so? > > I am not sure if it should be, because on my system it's not linked or I > just do not understand how it is working. > $ otool -L /usr/bin/ruby /usr/bin/ruby: > > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/libruby.1.dylib > (compatibility version 1.8.0, current version 1.8.7) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 125.2.0) > > Anyway in my opinion this should be fixed by the SuSe team. > > All the best, Sandor Szücs > -- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
