Joe,
I will issue the command tomorrow and try to verify this problem. Thank you
for your help.
Tony
Anthony C. Iannetti, P.E.
NASA Glenn Research Center
Aeropropulsion Division, Combustion Branch
21000 Brookpark Road, MS 5-10
Cleveland, OH 44135
phone: (216)433-5586
email: anthony.c.
Hi Tony,
Brian pointed out that the commands are compiling different items.
The issue is why is the atomic-asm.S not in the old make, but
is in the new make.
Your logs have a lower case s, atomic-asm.s, but not an uppercase S:
rm -f atomic-asm.s
ln -s "../../opal/asm/generated/atomic-ia64-lin
On Feb 9, 2009, at 6:41 PM, Brett Pemberton wrote:
Hey,
I've just installed OpenMPI 1.3 on our cluster, and am getting this
issue on jobs > 1 node.
mpiexec: symbol lookup error: /usr/local/openmpi/1.3-pgi/lib/openmpi/
mca_plm_tm.so: undefined symbol: tm_init
As reported before, I saw so
I need to support multiple compilers: Portland, Intel and GCC, so I've
been compiling OpenMPI with each compiler, to avoid the Fortran symbol
naming problems. When compiling, I'd use the --prefix and -exec-prefix
switches like so:
GCC:
../configure CC=gcc CXX=g++ F77=gfortran FC=gfortran
--prefix=
I have searched for solutions to this problem, but have not been successful.
The following command works okay when using Open MPI 1.2.8:
shell$ mpirun --hostfile procs -np 5 my_app < my_input
However, the above command produces the following error message when using Open
MPI 1.3:
f
It's a known race condition problem that has been fixed for the 1.3.1
release - hope to have that out in the near future.
Sorry
Ralph
On Feb 10, 2009, at 10:16 AM, Champagne, Nathan J. (JSC-EV)[ESCG] wrote:
I have searched for solutions to this problem, but have not been
successful. The fo
Hello Prentice:
On Tue, Feb 10, 2009 at 12:04:47PM -0500, Prentice Bisbal wrote:
> I need to support multiple compilers: Portland, Intel and GCC, so I've
> been compiling OpenMPI with each compiler, to avoid the Fortran symbol
> naming problems. When compiling, I'd use the --prefix and -exec-prefi
Dear everyone,
I apologize in advance for coming back with a common issue again.
Differently from other threads though, I was able to configure, make
and make install openMPI on my macbook 10.5.
What I used was the fowlling configure call:
./configure --prefix=/usr/local --enable-mpi-f77 --enab
What output do you get if you run /usr/local/bin/mpif77 or /usr/local/
bin/mpif90 ?
george.
On Feb 10, 2009, at 14:59 , simone marras wrote:
Dear everyone,
I apologize in advance for coming back with a common issue again.
Differently from other threads though, I was able to configure, mak
>It's a known race condition problem that has been fixed for the 1.3.1 release
>- hope to have that out in the near future.
Thanks for the info. I'll revert to 1.2.8 until 1.3.1 is released.
10 matches
Mail list logo