On Mar 22, 2013, at 8:06 AM, Siegmar Gross <siegmar.gr...@informatik.hs-fulda.de> wrote:
> openSuSE Linux 12.1, x86_64, SunC 5.12, 32-bit > ---------------------------------------------- > > tyr openmpi-1.7-Linux.x86_64.32_cc 547 tail log.make.Linux.x86_64.32_cc > Making all in mpi/fortran/use-mpi-f08 > make[2]: Entering directory `.../ompi/mpi/fortran/use-mpi-f08' > PPFC mpi-f08-sizeof.lo > PPFC mpi-f08.lo > "../../../../../openmpi-1.7rc8r28201/ompi/mpi/fortran/use-mpi-f08/mpi-f08.F90", > Line = 1, Column = 1: INTERNAL: Interrupt: Segmentation fault > make[2]: *** [mpi-f08.lo] Error 1 > make[2]: Leaving directory `.../ompi/mpi/fortran/use-mpi-f08' For this one, it looks like your Fortran compiler is borked (i.e., it's seg faulting!). You might want to --disable-mpi-fortran. This will make your build faster, too. :-) > Solaris 10, x86_64 and sparc, SunC 5.12, 64-bit > ----------------------------------------------- > > tyr openmpi-1.7-SunOS.x86_64.64_cc 565 tail -15 log.make.SunOS.x86_64.64_cc > F77 libvt_fmpi_la-vt_fmpiconst_2.lo > F77LD libvt-fmpi.la > ld: fatal: file .libs/libvt_fmpi_la-vt_fmpiconst_1.o: wrong ELF class: > ELFCLASS32 > ld: fatal: file processing errors. No output written to > .libs/libvt-fmpi.so.0.0.0 > make[5]: *** [libvt-fmpi.la] Error 2 > make[5]: Leaving directory `.../ompi/contrib/vt/vt/vtlib' I pinged the VT guys about your other post -- they don't always keep a close watch in the OMPI users list, and sometimes rely on an out-of-band nudge to get a reply. But when they're nudged (which they just were), they're pretty good about replying. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
