On Thu, Mar 7, 2013 at 4:01 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com>wrote:
> > This doesn't sound right -- I don't think we changed how linking worked in > 1.6.3 and 1.6.4. > > Are you sure that, on that same machine with MPICH installed in > /usr/lib64, you're also able to compile/link/use 1.6.3 properly? > Yes, on the same system, 1.6.3 openmpi works with MPICH installed in /usr/lib64 > > A wild guess: you have some kind of linker configuration that is putting > /usr/lib64 ahead of -L-specified paths on the compiler command line. > > On the same system, with 1.6.3: [root@tesla examples]# mpicc --showme hello_c.c gcc hello_c.c -I/opt/scyld/openmpi/1.6.3/gnu/include -pthread -L/opt/scyld/openmpi/1.6.3/gnu/lib -lmpi -libverbs -ldat -lrt -lnsl -lutil -lm -ltorque -lm -lnuma -lrt -lnsl -lutil -lm [root@tesla examples]# With 1.6.4: [root@tesla examples]# mpicc --showme hello_c.c gcc hello_c.c -I/opt/scyld/openmpi/1.6.4/gnu/include -pthread -L/usr/lib64 -Wl,-rpath -Wl,/usr/lib64 -L/opt/scyld/openmpi/1.6.4/gnu/lib -lmpi -libverbs -ldat -lrt -lnsl -lutil -lm -ltorque -lm -lnuma -lrt -lnsl -lutil -lm [root@tesla examples]# So indeed, for 1.6.4, the linker is putting /usr/lib64 ahead of openmpi library path, but I don't know why. I used the same configure options when I did these builds. I didn't change linker configuration from 1.6.3 to 1.6.4 either, the only difference I can tell is the openmpi source code. Thank you! Limin -- > 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 >
