John,

do you have shell access? Have you tried installing libopenssl-ruby1.8  
using something like apt-get or emerge if that is possible?

-----
Ryan Bigg
Freelancer
http://frozenplague.net







On 29/11/2008, at 9:32 AM, John Lane wrote:

>
>
>> The openssl library is probably there, I'd guess you're only missing
>> the ruby bindings for it. You could probably build those in your home
>> directory (the source is part of the standard ruby distribution) but
>> that assumes you have access to gcc and all that sort of jazz.
>>
>
> Openssl is there. The ruby bindings are not. I presume these are what
> the file /usr/lib/ruby/1.8/i486-linux/openssl.so would normally be.
>
> Now I don't have gcc access on the remote host so I tried to locally
> rebuild the same ruby as on the hosting service and upload openssl.so
> onto into the ruby library path. This allows me the privilege of  
> seeing
> a different error message:
>
> openssl.so: /lib/tls/i686/cmov/libc.so.6: version `GLIBC_2.4' not  
> found
>
> Which makes me think that the two systems have different toolchains,
> reinforced by this:
>
> rwxrwxrwx 1 root root 13 Jul 26  2007 /lib/tls/i686/cmov/libc.so.6 ->
> libc-2.3.6.so
>
> Where the host used to build has this:
>
> lrwxrwxrwx 1 root root 11 2007-05-17 21:11 /lib/tls/i686/cmov/ 
> libc.so.6
> -> libc-2.5.so
>
> I don't think I want to wander down the route of matching toolchains  
> so
> unless there are any clever ideas, I think it's time to give up on  
> this
> until the hosting provider can rebuild Ruby with the openssl  
> toolchain.
> -- 
> Posted via http://www.ruby-forum.com/.
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to