Regarding the Open64. It's that strange thing that I need two different versions of the compilers:
one for Opteron family 15h and one for general x86-64 architecture. This makes things quite complicated since my head node doesn't have Opteron family 15h processor. You can have a look at this topic: http://devgurus.amd.com/thread/160180

I've tried building the same version on a node with 6380 processors. Configuration was successful. But make failed in the following way:
libtool: compile:  opencc -DHAVE_CONFIG_H -I. -DLTDLOPEN=libltdlc "-DLT_CONFIG_H=<config.h>" -DLTDL -I. -I. -Ilibltdl -I./libltdl -I./libltdl -I/tmp/mpi_install_tmp26482/openmpi-1.7rc8/opal/mca/hwloc/hwloc151/hwloc/include -I/tmp/mpi_install_tmp26482/openmpi-1.7rc8/opal/mca/event/libevent2019/libevent -I/tmp/mpi_install_tmp26482/openmpi-1.7rc8/opal/mca/event/libevent2019/libevent/include -I/usr/include/infiniband -I/usr/include/infiniband -I/usr/include/infiniband -I/usr/include/infiniband -I/usr/include/infiniband -I/usr/include/infiniband -O3 -DNDEBUG -fvisibility=hidden -MT libltdlc_la-ltdl.lo -MD -MP -MF .deps/libltdlc_la-ltdl.Tpo -c ltdl.c  -fPIC -DPIC -o .libs/libltdlc_la-ltdl.o
/tmp/ccspin#.cVv00f.s: Assembler messages:
/tmp/ccspin#.cVv00f.s:860: Error: no such instruction: `bextr $257,%esi,%esi'
/tmp/ccspin#.cVv00f.s:868: Error: no such instruction: `bextr $258,%edi,%edi'
/tmp/ccspin#.cVv00f.s:876: Error: no such instruction: `bextr $259,%eax,%eax'
make[3]: *** [libltdlc_la-ltdl.lo] Error 1
make[3]: Leaving directory `/tmp/mpi_install_tmp26482/openmpi-1.7rc8/opal/libltdl'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/mpi_install_tmp26482/openmpi-1.7rc8/opal/libltdl'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/mpi_install_tmp26482/openmpi-1.7rc8/opal'
make: *** [all-recursive] Error 1

I guess that this issue has more to do with the compiler than with OpenMPI.


Let me know if you need me to run any additional tests.

Regards, Pavel Mezentsev.



2013/2/28 Jeff Squyres (jsquyres) <jsquyres@cisco.com>
On Feb 28, 2013, at 12:04 PM, Pavel Mezentsev <pavel.mezentsev@gmail.com> wrote:

> Do you mean the logs from failed attempts? They are enclosed. If you need the successful logs I'll need to make them again since the files from successful builds are deleted.

You guessed right; I need the logs from the failed builds.

It looks like your openf95 compiler is generating borked executables:

-----
configure:31019: checking KIND value of Fortran C_SIGNED_CHAR
configure:31046: openf95 -o conftest    conftest.f90  >&5
configure:31046: $? = 0
configure:31046: ./conftest
./configure: line 4343:  1234 Illegal instruction     (core dumped) ./conftest$ac_exeext
configure:31046: $? = 132
configure: program exited with status 132
configure: failed program was:
|       program main
|
|         use, intrinsic :: ISO_C_BINDING
|         open(unit = 7, file = "conftest.out")
|         write(7, *) C_SIGNED_CHAR
|         close(7)
|
|       end
-----

There's no reason the above Fortran program should fail with "illegal instruction".

> I am not using  MXM. The results with the option you suggested are the same as before:

We're investigating the latency issue.

--
Jeff Squyres
jsquyres@cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/


_______________________________________________
devel mailing list
devel@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel