On Mar 7, 2013, at 5:24 PM, Limin Gu <lgu_at_[hidden]> wrote:
> On the same system,
> with 1.6.3:
> [root_at_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_at_tesla examples]#
>
> With 1.6.4:
> [root_at_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_at_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.
Huh! This is surprising.
Can you send me the config.log from each of your 1.6.3 and 1.6.4 builds?
--
Jeff Squyres
jsquyres_at_[hidden]
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}