Yes, this is a correct report.

In short, the MPI_SIZEOF situation before the upcoming 1.8.4 was a bit of a 
mess; it actually triggered a bunch of discussion up in the MPI Forum Fortran 
working group (because the design of MPI_SIZEOF actually has some unintended 
consequences that came to light when another OMPI user noted the same thing you 
did a few months ago).

Can you download a 1.8.4 nightly tarball (or the rc) and see if MPI_SIZEOF is 
working for you there?



On Nov 5, 2014, at 6:24 AM, <michael.rach...@dlr.de> <michael.rach...@dlr.de> 
wrote:

> Sorry, Gilles, you might be wrong:
> 
> The error occurs also with gfortran-4.9.1, when running my small shared 
> memory testprogram:
> 
> This is the answer of the linker with gfortran-4.9.1 :  
>     sharedmemtest.f90:(.text+0x1145): undefined reference to `mpi_sizeof0di4_'
> 
> and this is the answer with intel-14.0.4:
>    sharedmemtest.f90:(.text+0x11c3): undefined reference to `mpi_sizeof0di4_'
> 
> 
> If openmpi  actually provides a module file   mpi.mod,  that was  precompiled 
> by openmpi for a certain Fortran compiler,
> then the whole installation of openmpi on a User machine from the 
> openmpi-sourcecode for a User chosen Ftn-compiler would be a farce.
> The module file  mpi.mod  must be either generated during the installation 
> process of openmpi on the User-machine for the User chosen Ftn-compiler,
> or alternatively Openmpi must provide the module not by a  mpi.mod file,  but 
> a mpi.f90 file.  MS-MPI does it that way.
> In my opinion, providing a  mpi.f90  file is indeed  better than providing an 
>  mpi.mod file, because the User can look inside the module
> and can directly see, if something is missing or possibly wrongly coded. 
> 
> Greetings 
>  Michael Rachner
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: users [mailto:users-boun...@open-mpi.org] Im Auftrag von Gilles 
> Gouaillardet
> Gesendet: Mittwoch, 5. November 2014 11:33
> An: Open MPI Users
> Betreff: Re: [OMPI users] OPENMPI-1.8.3: missing fortran bindings for 
> MPI_SIZEOF
> 
> Michael,
> 
> the root cause is openmpi was not compiled with the intel compilers but the 
> gnu compiler.
> fortran modules are not binary compatible so openmpi and your application 
> must be compiled with the same compiler.
> 
> Cheers,
> 
> Gilles
> 
> On 2014/11/05 18:25, michael.rach...@dlr.de wrote:
>> Dear OPENMPI developers,
>> 
>> In OPENMPI-1.8.3 the Ftn-bindings for  MPI_SIZEOF  are missing, when using 
>> the mpi-module and when using mpif.h .
>> (I have not controlled, whether they are present in the mpi_08 
>> module.)
>> 
>> I get this message from the linker (Intel-14.0.2):
>>     /home/vat/src/KERNEL/mpi_ini.f90:534: undefined reference to 
>> `mpi_sizeof0di4_'
>> 
>> So can you add  the Ftn-bindings for MPI_SIZEOF?
>> 
>> Once again I feel, that Fortran-bindings are unloved step-children for 
>> C-programmers. 
>> 
>> Greetings to you all
>> Michael Rachner
>> _______________________________________________
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2014/11/25676.php
> 
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2014/11/25682.php
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2014/11/25683.php


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

Reply via email to