How does the target application compile / link itself?
Try running "file" on the Open MPI libraries and/or your target application .o files to see what their bitness is, etc.
On Sep 22, 2011, at 3:15 PM, Dmitry N. Mikushin wrote:
> Hi Jeff,
> You're right because I also tried 1.4.3, and it's the same issue
> there. But what could be wrong? I'm using the simplest form -
> ../configure --prefix=/opt/openmpi_gcc-1.4.3/ and only installed
> compilers are system-default gcc and gfortran 4.6.1. Distro is ubuntu
> 11.10. There is no any mpi installed from packages, and no -m32
> options around. What else could be the source?
> - D.
> 2011/9/22 Jeff Squyres <jsquyres_at_[hidden]>:
>> This usually means that you're mixing compiler/linker flags somehow (e.g., built something with 32 bit, built something else with 64 bit, try to link them together).
>> Can you verify that everything was built with all the same 32/64?
>> On Sep 22, 2011, at 1:21 PM, Dmitry N. Mikushin wrote:
>>> OpenMPI 1.5.4 compiled with gcc 4.6.1 and linked with target app gives
>>> a load of linker messages like this one:
>>> /usr/bin/ld: ../../lib/libutil.a(parallel_utilities.o)(.debug_info+0x529d):
>>> unresolvable R_X86_64_64 relocation against symbol
>>> There are a lot of similar messages about other mpi_fortran_ symbols.
>>> Is it a known issue?
>>> - D.
>>> users mailing list
>> Jeff Squyres
>> For corporate legal information go to:
>> users mailing list
> users mailing list
For corporate legal information go to: