Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] [EXTERNAL] Re: [OMPI users] Error in openmpi-1.9a1r29179
From: Barrett, Brian W (bwbarre_at_[hidden])
Date: 2013-09-17 09:31:34


I agree on the shmem.fh statements. There are a couple of really painful interfaces to prototype, but for the most part, it should be straight forward. There's nothing in the OpenSHMEM specification that suggests providing a Fortran module, so I believe you got bad advice there. Brian -- Brian W. Barrett Scalable System Software Group Sandia National Laboratories ________________________________________ From: devel [devel-bounces_at_[hidden]] on behalf of Jeff Squyres (jsquyres) [jsquyres_at_[hidden]] Sent: Tuesday, September 17, 2013 4:37 AM To: Siegmar Gross; Open MPI Developers List Subject: [EXTERNAL] Re: [OMPI devel] [OMPI users] Error in openmpi-1.9a1r29179 ...moving over to the devel list... Dave and I looked at this during a break in the EuroMPI conference, and noticed several things: 1. Some of the shmem interfaces are functions (i.e., return non-void) and some are subroutines (i.e., return void). They're currently all using a single macro to declare the interfaces, which assume functions. So this macro is incorrect for subroutines -- you really need 2 macros. 2. The macro name is OMPI_GENERATE_FORTRAN_BINDINGS -- why isn't is SHMEM_GENERATE_FORTRAN_BINDINGS? 3. I notice that none of the Fortran interfaces are prototyped in shmem.fh. Why not? A shmem person here in Madrid mentioned that there is supposed to be a shmem.fh file and a shmem modulefile. On Sep 17, 2013, at 8:49 AM, Siegmar Gross <Siegmar.Gross_at_[hidden]> wrote: > Hi, > > I tried to install openmpi-1.9a1r29179 on "openSuSE Linux 12.1", > "Solaris 10 x86_64", and "Solaris 10 sparc" with "Sun C 5.12" in > 64-bit mode. Unfortunately "make" breaks with the same error on > all platforms. > > tail -15 log.make.Linux.x86_64.64_cc > > CCLD libshmem_c.la > make[3]: Leaving directory `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/c' > make[2]: Leaving directory `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/c' > Making all in shmem/fortran > make[2]: Entering directory `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/fortran' > CC start_pes_f.lo > "../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 16: void function cannot return value > "../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 16: void function cannot return value > "../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 16: void function cannot return value > cc: acomp failed for ../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c > make[2]: *** [start_pes_f.lo] Error 1 > make[2]: Leaving directory `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/fortran' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem' > make: *** [all-recursive] Error 1 > > > I configured with the following command. > > ../openmpi-1.9a1r29179/configure --prefix=/usr/local/openmpi-1.9_64_cc \ > --libdir=/usr/local/openmpi-1.9_64_cc/lib64 \ > --with-jdk-bindir=/usr/local/jdk1.7.0_07-64/bin \ > --with-jdk-headers=/usr/local/jdk1.7.0_07-64/include \ > JAVA_HOME=/usr/local/jdk1.7.0_07-64 \ > LDFLAGS="-m64" \ > CC="cc" CXX="CC" FC="f95" \ > CFLAGS="-m64" CXXFLAGS="-m64 -library=stlport4" FCFLAGS="-m64" \ > CPP="cpp" CXXCPP="cpp" \ > CPPFLAGS="" CXXCPPFLAGS="" \ > --enable-mpi-cxx \ > --enable-cxx-exceptions \ > --enable-mpi-java \ > --enable-heterogeneous \ > --enable-opal-multi-threads \ > --enable-mpi-thread-multiple \ > --with-threads=posix \ > --with-hwloc=internal \ > --without-verbs \ > --without-udapl \ > --without-sctp \ > --with-wrapper-cflags=-m64 \ > --enable-debug \ > |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_cc > > > > I would be grateful if somebody can fix the bug. Thank you very > much for any help in advance. > > > Kind regards > > Siegmar > > > _______________________________________________ > users mailing list > users_at_[hidden] > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ devel mailing list devel_at_[hidden] http://www.open-mpi.org/mailman/listinfo.cgi/devel