Is it possible to have two openmpi-s on the same computer? 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:
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.
I am inclined to say that if it is not something that has to do with
the existing openmpi 1.3.2 and gfortran interfering with the 1.4.1 and
Absoft, then it might be a bug in openmpi.
Paul
On Apr 19, 2010, at 11:20 AM, Jeff Squyres wrote:
On Apr 19, 2010, at 12:11 PM, Paul Cizmas wrote:
Here there was a difference - it did work for both cases:
~$ ABSOFT=foo
~$ testme
ABSOFT=foo
~$ export ABSOFT=foo
~$ testme
ABSOFT=foo
~$
This could well be because you had previously exported ABSOFT...?
(I forget the exact semantics offhand)
I'm somewhat at a loss to explain the behavior you're seeing, then.
In this regard, OMPI is a pretty standard configure/make open source
project -- we're not frobbing the environment before calling the
underlying libtool script (this stuff is totally handled by
Automake, actually).
Some off-the-wall-ideas:
1. Is $ABSOFT set to the correct value? I.e., could the error
message be interpreted as "The absoft compiler was unable to find
what it expected to find in $ABSOFT"?
2. Is there anything different/unique about your build environment
compared to the environment you just ran those tests in?
3. You might want to try editing "libtool" script that is emitted
after running OMPI's configure and add some debugging to see if
$ABSOFT really is set when that script is launched.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
