[MPICH] mpich2-1.0.5p4 build failure with PGI 6.2

[William Gropp]

In MPICH1, the Fortran interface library was separate, and the values  
of true and false were set during the Fortran Init, just to handle  
these issues.  MPICH2 has the infrastructure to support this, but we  
haven't provided it because everyone seemed to just build the zillion  
different libraries instead of building just what was needed.

Bill

On Apr 20, 2007, at 4:10 PM, David Gunter wrote:

> I've always followed the idea that you need to build each MPI (at  
> least the Fortran bits) with each Fortran compiler you use.  There  
> are a few reasons for this:  1) F90/F95 module bindings are  
> compiler specific; 2) Different compilers return different values  
> and sizes for Fortran boolean types (some use true/false = -1/0,  
> others use true/false = +1/0 for example).
>
> Granted, this is only an issue if your users are writing actual MPI  
> codes inside Fortran modules and/or using MPI boolean types in  
> Fortran, unless I'm missing something else.
>
> -david
> --
> David Gunter
> HPC-4: HPC Environments: Parallel Tools Team
> Los Alamos National Laboratory
>
>
> On Apr 20, 2007, at 2:52 PM, Garrick Staples wrote:
>
>> On Fri, Apr 20, 2007 at 03:44:03PM -0500, William Gropp alleged:
>>> Ah, but you don't need to use the same compiler to built the MPI
>>> libraries as the compiler that the user is using, they only need to
>>> make the same decisions about basic datatype lengths and they  
>>> need to
>>> have compatible libraries.  You should be able to use gcc to build
>>> MPICH2 with Nemesis, then use pgcc for the user program, with
>>> possibly a little tweeking of the compilation scripts.  Its that
>>> little tweeking that makes it easier to simply build with the same
>>> compiler, but it isn't a requirement.
>>
>> I'm playing with these different combinations now.  I have to support
>> gcc 3.4 (base compiler with centos4), gcc 4.1, intel 9.1, and pgi 6.2
>> (and probably now pgi 7.0).
>>
>> It would make sense to use gcc 3.4 for everything, except that it
>> doesn't have f90; so I'm wondering which f90 compiler I should use.
>>
>> With mpich1, I've always just done multiple builds with everything I
>> need in multiple directories.
>>
>> -- 
>> Garrick Staples, GNU/Linux HPCC SysAdmin
>> University of Southern California
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20070423/6410e1da/attachment.htm>