Cloud9 libssl problems

I'm trying to run Cloud9 but I'm getting this error when I try to run "bin/could9.sh"

support/node-builds-v4/node-linux32: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory

Any ideas?

Thanks

--edit--

AFTER the symbolic link test fix:

I did the symbolic link trick and I had to do it with libcrypto.so.0.9.8(e) too. Now I'm getting thoses errors..

support/node-builds-v4/node-linux32: /home/wobsite/lib/libssl.so.0.9.8: no version information available (required by support/node-builds-v4/node-linux32)
support/node-builds-v4/node-linux32: /home/wobsite/lib/libcrypto.so.0.9.8: no version information available (required by support/node-builds-v4/node-linux32)
support/node-builds-v4/node-linux32: /lib/libc.so.6: version `GLIBC_2.9' not found (required by support/node-builds-v4/node-linux32)
support/node-builds-v4/node-linux32: /lib/libc.so.6: version `GLIBC_2.7' not found (required by support/node-builds-v4/node-linux32)
support/node-builds-v4/node-linux32: /lib/libc.so.6: version `GLIBC_2.6' not found (required by support/node-builds-v4/node-linux32)

Thanks

node.js cloud9 libssl

asked Apr 09 '11 at 17:38

cedric
3●1●4

edited Apr 09 '11 at 20:15

This seems like a compatibility issue.

Are you running a precompiled binary, or did you compile this from source?

(Apr 09 '11 at 20:25) ryans ♦♦

I was running a precompiled binary.

(Apr 10 '11 at 18:11) cedric

2 Answers:

oldest newest most voted

Our systems don't have the libssl.so.0.9.8 file; we have a slightly updated version which is likely compatible:

1	/lib/libssl.so.0.9.8e

If it is indeed compatible with your software, you should be able to make use of it using something like this:

1
2
3

ln -s /lib/libssl.so.0.9.8e $HOME/lib/libssl.so.0.9.8
export LD_LIBRARY_PATH=$HOME/lib:$LD_LIBRARY_PATH
bin/cloud9.sh

If this does work, then the easiest way to package the solution into a convenient executable is to create a simple shell script wrapper; something like this:

(in a file called cloud9_start.sh in the same directory as cloud9.sh)

#!/bin/bash
export LD_LIBRARY_PATH=$HOME/lib:$LD_LIBRARY_PATH
exec ./cloud9.sh $@        # it's actually best to use the full path to cloud9.sh here

Then, just run cloud9_start.sh instead.

Alternatively (simpler, but less elegant), just set LD_LIBRARY_PATH in your ~/.bash_profile file so that it's always active.

Hope that helps!

answered Apr 09 '11 at 19:36

ryans ♦♦
2936●1●4●20

edited Apr 09 '11 at 19:37

Problem solved!

With those instructions : http://blog.area256.com/?p=944

At step 3 I had this error : o3.node: undefined symbol: __sync_add_and_fetch_4

To fix it, edit the CCFLAGS and CXXFLAGS in wscript like this (add '-march=i686') before building :

1 2	conf.env.append_value('CCFLAGS', ['-O3', '-msse2', '-ffast-math', '-march=i686']) conf.env.append_value('CXXFLAGS', ['-O3', '-msse2', '-ffast-math', '-march=i686'])

Thanks for the help

answered Apr 10 '11 at 18:10

cedric
3●1●4

Your answer

If you have an answer to the above question, then use the form below. Otherwise, use the appropriate 'add new comment' button above to post your feedback.

toggle preview

community wiki

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

node.js ×21
cloud9 ×3
libssl ×1

Asked: Apr 09 '11 at 17:38

Seen: 2,754 times

Last updated: Apr 10 '11 at 18:11

Cloud9 libssl problems

Follow this question

Got questions? We have answers!

Related questions