Would someone please point me
 

Would someone please point me in the correct direction to download and install the libelf.so.0 file so that I may get FoamX to work.

I am only just starting with OpenFOAM and am using Ubuntu 6.06 LTS (Dapper Drake).

Thanks for your help in advance.

Regards

Shaun.D

Well I found the libelf packag
 

Well I found the libelf package at http://packages.ubuntu.com/dapper/

and then went to install it using Gdebi. Turns out that libelf.so.0 was already installed at usr/lib/libelf.so.0

So, I tried running the command FoamX and still got the same error that everyone else I have noticed on this discussion forum has had in the past. I.e

Starting NameServer with inet:darmodys-desktop:1234 ...
nsd: error while loading shared libraries: libelf.so.0: cannot open shared object file: No such file or directory

So, now I am thinking that somehow FoamX is looking in the wrong directory for this file.

Has anyone had this problem with OpenFOAM in Ubuntu and if so how do you reslove it? My group here in AUS are keen to have OpenFOAM up and running. If needs be, I will reinstall with SUSE if I cannot resolve this issue.

Any help will be much appreciated.

Regards

Shaun.D

I recently installed OpenFOAM
 

I recently installed OpenFOAM 1.4 in Ubuntu 7.04 Feisty Fawn. The installation instructions could be followed with very detail from this sites:

http://ubuntuforums.org/showthread.php?t=156298
https://help.ubuntu.com/community/OpenFOAM

The only difference between sites it's the version number (1.4 in the first and 1.3 in the second). This only affects the filenames on the command line

When I try to run FoamX, received the following error message:

nsd: error while loading shared libraries: libssl.so.0.9.7: cannot open shared object file: No such file or directory

To solve that problem, I simply went to Synaptic, and install the libssl.so.0.9.7 package.

Regards

Felix

PD: Sorry if the help it's late

Thanks for the post Felix. I h
 

Thanks for the post Felix. I had solved the problem a while ago, and also came across the same issue for OF1.4. I was able to quickly resolve that.

Cheers

Shaun.D