Hello Jeff,
thank you for your feedback.
I have this problem when I compile c, c++ and fortran code with the mpi
bindings, i.e. mpicc, mpicxx and mpif90. If I compile directly codes with
gcc, g++ or gfortran I do not have this problem. This is why I think it's
something related to openmpi.
Thanks!
I think you cited the correct prior thread on the OMPI users list, and I think
it correctly identifies the problem: the linker is finding the "wrong" library
first, determines that it is wrong, and skips it.
You probably should remove the "wrong" library from your LD_LIBRARY_PATH (e.g.,
if you'
Dear All,
I have recently installed gcc 4.7.3 on my cent OS 6.4. Moreover, I have
compiled openmpi 1.6.4 with the above compiler.
My LD_LIBRARY_PATH is set correctly and it points to both /lib and /lib64
where libgfortran.so and libgcc_s.so for 32 and 64 bits are located.
Every time I compile a F
Thanks!, I was thinking is was something like that.
Gary
Samuel Sarholz wrote:
Hi Gary,
that is a linker warning.
You probably have a libgcc_s.so in 32 and 64 bit. The linker finds the
"wrong" version first and skips it. After that the matching one is
linked and thus your program runs.
So n
Hi Gary,
that is a linker warning.
You probably have a libgcc_s.so in 32 and 64 bit. The linker finds the
"wrong" version first and skips it. After that the matching one is
linked and thus your program runs.
So nothing to worry about.
To avoid the warning you can switch the (default) search o
Hi Everyone,
I'm getting a "/usr/bin/ld: skipping incompatible
/usr/local/lib/libgcc_s.so when searching for -lgcc_s" when compiling
some of the openmpi 1.3 examples. The programs still compile and run.
Does anyone know if this warning is something I should be concerned
about and/or how I c
