On Apr 20, 2010, at 7:03 PM, Paul Cizmas wrote:

> Is it possible to have two openmpi-s on the same computer?  

Yes.  As an OMPI developer, I have dozens of different OMPI installs on my 
cluster (for various stages of development and testing, etc.).  The only real 
issue is to ensure that you set your PATH (and possibly LD_LIBRARY_PATH) 
correctly to point to the one that you want.  If you use the 
--enable-mpirun-prefix-by-default configure option, then you don't need to 
worry about paths on the remote nodes.

> I have 
> openmpi 1.3.2 working fine with gfortran but I cannot build openmpi 
> 1.4.1 with Absoft - I get this message from libtool:
> 
> /bin/sh ../../../libtool   --mode=compile /Applications/Absoft11.0/bin/
> f90 -I../../../ompi/include -I../../../ompi/include -p. -I. -I../../../
> ompi/mpi/f90  -lU77 -c -o mpi.lo mpi.f90
> libtool: compile:  /Applications/Absoft11.0/bin/f90 -I../../../ompi/
> include -I../../../ompi/include -p. -I. -I../../../ompi/mpi/f90 -lU77 -
> c mpi.f90  -o .libs/mpi.o
> Can't find the absoft directory.
> Please set the ABSOFT environment variable and try again.
> make[4]: *** [mpi.lo] Error 1
> 
> Note that ABSOFT is properly set as in fact shown above on the first 
> line.  In addition, the absolute address of the f90 (/Applications/
> Absoft11.0/bin/f90) is correct.
> 
> To recreate the problem I went to folder openmpi-1.4.1/ompi/mpi/f90, 
> checked again ABSOFT variable and called libtool.  The result is 
> obviously the same:
> 
> sudo /bin/sh ../../../libtool   --mode=compile /Applications/
> Absoft11.0/bin/f90 -I../../../ompi/include -I../../../ompi/include -p. 
> -I. -I../../../ompi/mpi/f90  -lU77 -c -o mpi.lo mpi.f90
> Password:

Why are you sudo'ing here?

We just had another user on the list have a problem compiling because they were 
doing "sudo make all" instead of just "make all".  I'm not sure what exactly 
happened, but "sudo make all" apparently had some weird side effects whereas 
"make all" did not.  

FWIW: Most users compile Open MPI as a non-privlidged user and then only use 
sudo to "make install".

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/


Reply via email to