On Mon, 2009-07-27 at 23:56 -0700, Jacob Balthazor wrote:
> I ran the command, how would you interpret these results to create a
> path for my include?
>
> [beowulf1@localhost ~]$ whereis libmpi.so
> libmpi:
> [beowulf1@localhost ~]$
I'd interpret it as you've got things stashed in strange plac
I ran the command, how would you interpret these results to create a
path for my include?
[beowulf1@localhost ~]$ whereis libmpi.so
libmpi:
[beowulf1@localhost ~]$
-Jacob B.
On Jul 27, 2009, at 9:55 PM, Terry Frankcombe wrote:
I suspect that my not changing my .bash_profile is inde
Hey, Jacob.
If you are installing OMPI with yum under Fedora 10, you'll get an old
1.2.4 version (that was one of my own mistakes). It is strongly
recommended to get the latest 1.3.3 version - many problems can go away.
Sincerely yours, Alexey.
On Mon, 2009-07-27 at 08:35 -0700, jacob Balthazor
> I suspect that my not changing my .bash_profile is indeed the
> problem unfortunately I do not know were yum placed open's lib and bin
> directories. I tried looking in /usr/local/ but did not find and
> openmpi directory, I suspect this has something to my Fedora
> distribution as apposed
Have you tried just adding -x LD_LIBRARY_PATH to your mpirun cmd line?
This will pickup your local LD_LIBRARY_PATH value and propagate it for
you to the remote node.
On Jul 27, 2009, at 9:58 PM, Jacob Balthazor wrote:
Hey,
I suspect that my not changing my .bash_profile is indeed
Hey,
I suspect that my not changing my .bash_profile is indeed the
problem unfortunately I do not know were yum placed open's lib and bin
directories. I tried looking in /usr/local/ but did not find and
openmpi directory, I suspect this has something to my Fedora
distribution as a
I had a same problem like this.
I am using Debian on my nodes, the problem was with non-interactive
shell invocations,
I added "export LD_LIBRARY_PATH=/usr/local/openMPI/lib" at the top of
the ~/.bashrc files in all nodes then it worked.
Regards.
jacob Balthazor wrote:
Hey,
Please he
Hi Jacob
Did you set the PATH and LD_LIBRARY_PATH according to
http://www.open-mpi.org/faq/?category=running#adding-ompi-to-path
Jody
On Mon, Jul 27, 2009 at 5:35 PM, jacob Balthazor wrote:
>
> Hey,
> Please help me out as I cannot figure out from all the online
> documentation why my cl
Most likely problem is version confusion as Fedora comes with a version of
OMPI pre-installed. Check you LD_LIBRARY_PATH and PATH on both ends to
ensure they are pointing at the same OMPI installation. Remember,
interactive login typically uses a different shell startup then
non-interactive job lau
Hey,
Please help me out as I cannot figure out from all the online
documentation why my cluster wont work.
1) I started with two computers with a fresh install of Fedora 10.
2) Created two user accounts on the two computers with the same user name.
3) Created an rsa keyed ssh between the tw
There's usually an "icc_vars.sh" script somewhere in your intel
compiler installation (and corresponding "icc_vars.csh" if you're
using C-flavored shells) that will do things like add the intel paths
to LD_LIBRARY_PATH, etc. If you source this file, all should be well.
You may also need to
Amos,
The libraries that ldd isn't finding are intel fortran libraries. If
you put that directory in your load library path things should work.
Doug Reeder
On Mar 16, 2009, at 12:05 PM, Amos Leffler wrote:
Hi Josh and Jeff,
I found mpicc in /usr/local/lib (where I put it) and when I
tr
You need to have the Intel compilers (both C and Fortran) in your
LD_LIBRARY_PATH so they can resolve the imf library.
On Mar 16, 2009, at 1:05 PM, Amos Leffler wrote:
Hi Josh and Jeff,
I found mpicc in /usr/local/lib (where I put it) and when I
tried the command "ldd mpicc" I got the f
Hi Josh and Jeff,
I found mpicc in /usr/local/lib (where I put it) and when I
tried the command "ldd mpicc" I got the following;
linux-f2f9:/usr/local/bin # ldd mpicc
libopen-pal.so.0 => /usr/local/lib/libopen-pal.so.0 (0x2afcd6bf6000)
libm.so.6 => /lib64/libm.so.6 (0x
On Mar 13, 2009, at 2:42 PM, Amos Leffler wrote:
Thanks for your advice. I went back carefully through my PATH
file and corrected that so that I compiled openmpi-1.2.9 with the
Intel compilers seemingly without errors. However, the simple test
examples wont run with the same error:
~/Des
Hi Josh,
Thanks for your advice. I went back carefully through my PATH
file and corrected that so that I compiled openmpi-1.2.9 with the
Intel compilers seemingly without errors. However, the simple test
examples wont run with the same error:
~/Desktop/openmpi-1.2.9/examples> mpicc hello_c.
Hi Amos,
It looks like you do not have permission to make the directory /usr/
local/etc. Either you need to run the make all install as root, so
you have permission to that directory, or you need to use the --
prefix= option to configure so that the installation gets
installed into a path
Hello Forum,
Attached is a file of my installation and trying examples
for openmpi-1.2.9 which were not successful. Hopefully the problem is
a simple one and obvious to a more experienced user.
I am trying to install and test openmpi-1.2.9. I found that I
could not use the Intel 11.0
18 matches
Mail list logo
