On Jul 12, 2007, at 4:42 PM, George Bosilca wrote:
> The INTFACE is for the namespace interface in order to allow the
> Fortran code to call a C function. So it should be dependent on the
> compiler. Btw, for some reasons I was quite sure we generate all 4
> versions of the Fortran interface ... If this is true is doesn't
> really mater what you have in the INTFACE.
It would except this flag not only affects the names BLACS uses to
link to OpenMPI but also what interfaces it generates (based on my
experience), which then for example affects what happens when you
build ScalaPack. I believe that was what I was seeing when building
those three with the Intel compiler and g95, the latter was harder
> The option Jeff is refering to is the TRANSCOMM define. It allow
> BLACS to know how to convert between Fortran and C handlers. For Open
> MPI this should be set to -DUseMpi2.
Fortunately documented on the web FAQ but not in the BLACS
> On Jul 12, 2007, at 2:41 PM, Jeff Squyres wrote:
>> On Jul 12, 2007, at 2:28 PM, Michael wrote:
>>> In the FAQ <http://www.open-mpi.org/faq/?category=mpi-apps>, section
>>> 12. How do I build BLACS with Open MPI?
>>> INTFACE = -Df77IsF2C
>>> That INTFACE value is only for G77, G95, and related compilers.
>>> For the Intel Fortran compiler it is: -DAdd_
>> Really? I always thought that this flag discussed how to convert F77
>> MPI handles to C handles (some MPI implementations use integers for
>> MPI handles in C, so there's no conversion necessary, but LAM and
>> Open MPI use pointers, so using the MPI_*_f2c() functions are
>> necessary). Hence, it's not specific to a given fortran compiler.
>> But I could be completely misunderstanding this value...
>> UTK: can you confirm/deny both of these values? (I do not claim to
>> be a BLACS expert...)
>>> I have successfully built the combination of OpenMPI 1.2.3, ATLAS,
>>> BLACS, ScalaPack, and MUMPS using the Intel Fortran compiler on two
>>> different Debian Linux systems (3.0r3 on AMD Opterons and 4.0r0 on
>>> Intel Woodcrest/MacPro).
>>> users mailing list
>> Jeff Squyres
>> Cisco Systems
>> users mailing list
> users mailing list