Re: [OMPI users] compilation aborted for Handler.cpp (code 2)
Dear Jeff Thank you for explaining. Please find attached test logs which explain the error. Regards On Fri, Sep 27, 2013 at 6:12 PM, Jeff Squyres (jsquyres) wrote: > On Sep 27, 2013, at 6:53 AM, Syed Ahsan Ali wrote: > >> Thank you very much Jeff. It worked now. > > Good. > >> But I got error when I ran make check >> >> 1 of 5 tests failed >> Please report to http://www.open-mpi.org/community/help/ >> >> make[3]: *** [check-TESTS] Error 1 >> make[3]: Leaving directory `/home/openmpi-1.6.5/test/datatype' >> make[2]: *** [check-am] Error 2 >> make[2]: Leaving directory `/home/openmpi-1.6.5/test/datatype' >> make[1]: *** [check-recursive] Error 1 >> make[1]: Leaving directory `/home/openmpi-1.6.5/test' >> make: *** [check-recursive] Error 1 >> [root@r720 openmpi-1.6.5]# > > Can you send more info than that? It's not showing which test failed, for > example. > >> But I find openmpi installed. Will it work fine? > > Probably...? But I can't say without seeing which test failed. > > Keep in mind that "make check" is run after "make install", so, yes, it's > expected that OMPI is fully *installed*. But whether OMPI is *functional* > depends on the test(s) that failed... > >> Secondly missing the >> optional package VT will effect functionality of openmpi or it will >> work fine. > > VT = VampirTrace, which is a tracing/logging tool that is technically not > part of MPI. That is, it's a 3rd party tool that provides *additional* > functionality over MPI. Hence, it's totally optional. > > -- > 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 -- Syed Ahsan Ali Bokhari Electronic Engineer (EE) Research & Development Division Pakistan Meteorological Department H-8/4, Islamabad. Phone # off +92518358714 Cell # +923155145014 <>
Re: [OMPI users] users Digest, Vol 2696, Issue 1
Hi all, Does anybody have done experiments comparing the speed between mpich and openmpi? Best regards, Yin Zhao > 在 2013年10月3日，0:00，users-requ...@open-mpi.org 写道： > > Send users mailing list submissions to >us...@open-mpi.org > > To subscribe or unsubscribe via the World Wide Web, visit >http://www.open-mpi.org/mailman/listinfo.cgi/users > or, via email, send a message with subject or body 'help' to >users-requ...@open-mpi.org > > You can reach the person managing the list at >users-ow...@open-mpi.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: Error compiling openmpi-1.9a1r29292 (Jeff Squyres (jsquyres)) > 2. Re: non-functional mpif90 compiler (Gus Correa) > 3. Re: non-functional mpif90 compiler (Jeff Squyres (jsquyres)) > 4. CUDA-aware usage (Rolf vandeVaart) > > > -- > > Message: 1 > Date: Tue, 1 Oct 2013 18:38:15 + > From: "Jeff Squyres (jsquyres)" > To: Siegmar Gross , Open MPI >Users > Subject: Re: [OMPI users] Error compiling openmpi-1.9a1r29292 > Message-ID: > > Content-Type: text/plain; charset="us-ascii" > > These should now be fixed. > >> On Sep 30, 2013, at 3:41 AM, Siegmar Gross >> wrote: >> >> Hi, >> >> today I tried to install openmpi-1.9a1r29292 on my platforms >> (openSuSE 12.1 Linux x86_64, Solaris 10 x86_64, and Solaris 10 Sparc) >> with Sun C 5.12 and gcc-4.8.0. I have the following error on all >> platforms, when I compile a 32- or 64-bit version with Sun C. >> >> ... >> PPFC mpi-f08-interfaces.lo >> >> module mpi_f08_interfaces >> ^ >> "../../../../../openmpi-1.9a1r29292/ompi/mpi/fortran/base/mpi-f08-interfaces.F90", >> Line = 19, Column = 8: ERROR: The compiler has detected >> errors in module "MPI_F08_INTERFACES". No module information >> file will be created for this module. >> >> use :: mpi_f08_types, only : MPI_Datatype, MPI_Comm, MPI_Aint, >>MPI_ADDRESS_KIND >> ^ >> >> "../../../../../openmpi-1.9a1r29292/ompi/mpi/fortran/base/mpi-f08-interfaces.F90", >> Line = 4419, Column = 57: ERROR: "MPI_AINT" is not in module "MPI_F08_TYPES". >> >> f90comp: 4622 SOURCE LINES >> f90comp: 2 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI >> make[2]: *** [mpi-f08-interfaces.lo] Error 1 >> make[2]: Leaving directory >> `.../openmpi-1.9a1r29292-Linux.x86_64.64_cc/ompi/mpi/fortran/base' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory >> `.../openmpi-1.9a1r29292-Linux.x86_64.64_cc/ompi' >> make: *** [all-recursive] Error 1 >> linpc1 openmpi-1.9a1r29292-Linux.x86_64.64_cc 122 >> >> >> >> >> I have the following error on all platforms, when I compile a 32-bit >> version with gcc-4.8.0. >> >> linpc1 openmpi-1.9a1r29292-Linux.x86_64.32_gcc 120 tail -150 >> log.make.Linux.x86_64.32_gcc >> Making all in mca/spml >> make[2]: Entering directory >> `/export2/src/openmpi-1.9/openmpi-1.9a1r29292-Linux.x86_64.32_gcc/oshmem/mca/spml' >> CC base/spml_base_frame.lo >> CC base/spml_base_select.lo >> CC base/spml_base_request.lo >> CC base/spml_base_atomicreq.lo >> CC base/spml_base_getreq.lo >> CC base/spml_base_putreq.lo >> CC base/spml_base.lo >> CCLD libmca_spml.la >> make[2]: Leaving directory >> `/export2/src/openmpi-1.9/openmpi-1.9a1r29292-Linux.x86_64.32_gcc/oshmem/mca/spml' >> Making all in . >> make[2]: Entering directory >> `/export2/src/openmpi-1.9/openmpi-1.9a1r29292-Linux.x86_64.32_gcc/oshmem' >> CC op/op.lo >> ../../openmpi-1.9a1r29292/oshmem/op/op.c: In function >> 'oshmem_op_max_freal16_func': >> ../../openmpi-1.9a1r29292/oshmem/op/op.c:134:15: error: 'a' undeclared >> (first use in this function) >>type *a = (type *) in; \ >> ^ >> ../../openmpi-1.9a1r29292/oshmem/op/op.c:194:1: note: in expansion of macro >> 'FUNC_OP_CREATE' >> FUNC_OP_CREATE(max, freal16, ompi_fortran_real16_t, __max_op); >> ^ >> ../../openmpi-1.9a1r29292/oshmem/op/op.c:134:15: note: each undeclared >> identifier is reported only once for each function it appears in >>type *a = (type *) in; \ >> ^ >> ../../openmpi-1.9a1r29292/oshmem/op/op.c:194:1: note: in expansion of macro >> 'FUNC_OP_CREATE' >> FUNC_OP_CREATE(max, freal16, ompi_fortran_real16_t, __max_op); >> ^ >> ../../openmpi-1.9a1r29292/oshmem/op/op.c:134:26: error: expected expression >> before ')' token >>type *a = (type *) in; \ >> ^ >> ../../openmpi-1.9a1r29292/oshmem/op/op.c:194:1: note: in expansion of macro >> 'FUNC_OP_CREATE' >> FUNC_OP_CREATE(max, freal16, ompi_fortran_real16_t, __max_op); >> ^ >> ../../openmpi-1.9a1r29292/oshme
Re: [OMPI users] users Digest, Vol 2696, Issue 1
You try Google Scholar yet? Always exhaust all nonhuman resources before requesting human assistance. The human brain is a terrible resource to waste when a computer can do the job. Jeff Sent from my iPhone On Oct 3, 2013, at 10:18 AM, Yin Zhao wrote: > Hi all, > > Does anybody have done experiments comparing the speed between mpich and > openmpi? > > Best regards, > Yin Zhao > >> 在 2013年10月3日，0:00，users-requ...@open-mpi.org 写道： >> >> Send users mailing list submissions to >> us...@open-mpi.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://www.open-mpi.org/mailman/listinfo.cgi/users >> or, via email, send a message with subject or body 'help' to >> users-requ...@open-mpi.org >> >> You can reach the person managing the list at >> users-ow...@open-mpi.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of users digest..." >> >> >> Today's Topics: >> >> 1. Re: Error compiling openmpi-1.9a1r29292 (Jeff Squyres (jsquyres)) >> 2. Re: non-functional mpif90 compiler (Gus Correa) >> 3. Re: non-functional mpif90 compiler (Jeff Squyres (jsquyres)) >> 4. CUDA-aware usage (Rolf vandeVaart) >> >> >> -- >> >> Message: 1 >> Date: Tue, 1 Oct 2013 18:38:15 + >> From: "Jeff Squyres (jsquyres)" >> To: Siegmar Gross , Open MPI >> Users >> Subject: Re: [OMPI users] Error compiling openmpi-1.9a1r29292 >> Message-ID: >> >> Content-Type: text/plain; charset="us-ascii" >> >> These should now be fixed. >> >>> On Sep 30, 2013, at 3:41 AM, Siegmar Gross >>> wrote: >>> >>> Hi, >>> >>> today I tried to install openmpi-1.9a1r29292 on my platforms >>> (openSuSE 12.1 Linux x86_64, Solaris 10 x86_64, and Solaris 10 Sparc) >>> with Sun C 5.12 and gcc-4.8.0. I have the following error on all >>> platforms, when I compile a 32- or 64-bit version with Sun C. >>> >>> ... >>> PPFC mpi-f08-interfaces.lo >>> >>> module mpi_f08_interfaces >>> ^ >>> "../../../../../openmpi-1.9a1r29292/ompi/mpi/fortran/base/mpi-f08-interfaces.F90", >>> Line = 19, Column = 8: ERROR: The compiler has detected >>> errors in module "MPI_F08_INTERFACES". No module information >>> file will be created for this module. >>> >>> use :: mpi_f08_types, only : MPI_Datatype, MPI_Comm, MPI_Aint, >>> MPI_ADDRESS_KIND >>> ^ >>> "../../../../../openmpi-1.9a1r29292/ompi/mpi/fortran/base/mpi-f08-interfaces.F90", >>> Line = 4419, Column = 57: ERROR: "MPI_AINT" is not in module >>> "MPI_F08_TYPES". >>> >>> f90comp: 4622 SOURCE LINES >>> f90comp: 2 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI >>> make[2]: *** [mpi-f08-interfaces.lo] Error 1 >>> make[2]: Leaving directory >>> `.../openmpi-1.9a1r29292-Linux.x86_64.64_cc/ompi/mpi/fortran/base' >>> make[1]: *** [all-recursive] Error 1 >>> make[1]: Leaving directory >>> `.../openmpi-1.9a1r29292-Linux.x86_64.64_cc/ompi' >>> make: *** [all-recursive] Error 1 >>> linpc1 openmpi-1.9a1r29292-Linux.x86_64.64_cc 122 >>> >>> >>> >>> >>> I have the following error on all platforms, when I compile a 32-bit >>> version with gcc-4.8.0. >>> >>> linpc1 openmpi-1.9a1r29292-Linux.x86_64.32_gcc 120 tail -150 >>> log.make.Linux.x86_64.32_gcc >>> Making all in mca/spml >>> make[2]: Entering directory >>> `/export2/src/openmpi-1.9/openmpi-1.9a1r29292-Linux.x86_64.32_gcc/oshmem/mca/spml' >>> CC base/spml_base_frame.lo >>> CC base/spml_base_select.lo >>> CC base/spml_base_request.lo >>> CC base/spml_base_atomicreq.lo >>> CC base/spml_base_getreq.lo >>> CC base/spml_base_putreq.lo >>> CC base/spml_base.lo >>> CCLD libmca_spml.la >>> make[2]: Leaving directory >>> `/export2/src/openmpi-1.9/openmpi-1.9a1r29292-Linux.x86_64.32_gcc/oshmem/mca/spml' >>> Making all in . >>> make[2]: Entering directory >>> `/export2/src/openmpi-1.9/openmpi-1.9a1r29292-Linux.x86_64.32_gcc/oshmem' >>> CC op/op.lo >>> ../../openmpi-1.9a1r29292/oshmem/op/op.c: In function >>> 'oshmem_op_max_freal16_func': >>> ../../openmpi-1.9a1r29292/oshmem/op/op.c:134:15: error: 'a' undeclared >>> (first use in this function) >>> type *a = (type *) in; \ >>> ^ >>> ../../openmpi-1.9a1r29292/oshmem/op/op.c:194:1: note: in expansion of macro >>> 'FUNC_OP_CREATE' >>> FUNC_OP_CREATE(max, freal16, ompi_fortran_real16_t, __max_op); >>> ^ >>> ../../openmpi-1.9a1r29292/oshmem/op/op.c:134:15: note: each undeclared >>> identifier is reported only once for each function it appears in >>> type *a = (type *) in; \ >>> ^ >>> ../../openmpi-1.9a1r29292/oshmem/op/op.c:194:1: note: in expansion of macro >>> 'FUNC_OP_CREATE' >>> FUNC_OP_CREATE(max, freal16, ompi_fortran_real16_t, __max_op); >>> ^ >>> ../../openmpi-1.9a1r29292/oshmem/op/op.c:134:26: error: expected expression >>> before ')' token >>>
