It's probably a packaging error, if he used the distribution'sOn Fri, Mar 12, 2010 at 6:02 PM, Samuel K. Gutierrez <email@example.com> wrote:
> One more thing. The line should have been:
> export LD_LIBRARY_PATH=/home/jess/local/ompi/lib64
> The space in the previous email will make bash unhappy 8-|.
> Samuel K. Gutierrez
> Los Alamos National Laboratory
> On Mar 12, 2010, at 1:56 PM, Samuel K. Gutierrez wrote:
>> It sounds like you may need to set your LD_LIBRARY_PATH environment
>> variable correctly. There are several ways that you can tell the dynamic
>> linker where the required libraries are located, but the following may be
>> sufficient for your needs.
>> Let's say, for example, that your Open MPI installation is rooted at
>> /home/jess/local/ompi and the libraries are located in
>> /home/jess/local/ompi/lib64, try (bash-like shell):
>> export LD_LIBRARY_PATH= /home/jess/local/ompi/lib64
>> Hope this helps,
>> Samuel K. Gutierrez
>> Los Alamos National Laboratory
>> On Mar 12, 2010, at 1:32 PM, vaibhav dutt wrote:
>>> I have installed openmpi on an Kubuntu , with Dual core Linux AMD Athlon
>>> When trying to compile a simple program, I am getting an error.
>>> mpicc: error while loading shared libraries: libopen-pal.so.0: cannot
>>> open shared object file: No such file or dir
>>> I read somewhere that this error is because of some intel compiler
>>> being not installed on the proper node, which I don't understand as I
>>> am using AMD.
>>> Kindly give your suggestions
>>> Thank You
packages. In that case, he should report the bug to downstream.
If he installed from source, then it's most likely installed somewhere
outside the library path, and the LD_LIBRARY_PATH trick might work (if
it doesn't, make sure there are no leftovers, recompile, reinstall and
it should work fine).
users mailing list