[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20010920: building Fortran interface using sgif90

Crystal,

>Date: Thu, 20 Sep 2001 12:41:58 -0500 (CDT)
>From: Crystal Shaw <address@hidden>
>Organization: NCSA
>To: address@hidden (Steve Emmerson)
>Subject: Re: 20010920: building Fortran interface using sgif90
>Keywords: 200109201638.f8KGcg105025

The above message contained the following:

> 0000000000005300 T nf_get_att_double__
> 0000000000002780 T nf_get_att_int1__
> 0000000000003260 T nf_get_att_int2__
> 0000000000003d40 T nf_get_att_int__
> 0000000000004820 T nf_get_att_real__
> 0000000000001c10 T nf_get_att_text__
> 0000000000004d50 T nf_put_att_double__
> 00000000000021d0 T nf_put_att_int1__
> 0000000000002cb0 T nf_put_att_int2__
> 0000000000003790 T nf_put_att_int__
> 0000000000004270 T nf_put_att_real__
> 0000000000001600 T nf_put_att_text__
> 0000000000001ab0 T nf__create__
> 0000000000003470 T nf__create_mp__
> 0000000000002cd0 T nf__enddef__
> 0000000000002510 T nf__open__
> 0000000000003a40 T nf__open_mp__
> 0000000000002f40 T nf_abort__

The double underscore suffix on the above is consistent with the use
of the "f2cFortran" macro. Apparently, however, the sgif90 compiler
doesn't use that form; consequently, we need to use a different naming
convention in the Fortran-calling-C interface.

There are many such conventions to choose from. The following is the
corresponding macro list:

    NAGf90Fortran
    f2cFortran
    hpuxFortran
    apolloFortran
    sunFortran
    IBMR2Fortran
    CRAYFortran
    pgiFortran
    mipsFortran
    DECFortran
    vmsFortran
    CONVEXFortran
    PowerStationFortran
    AbsoftUNIXFortran
    AbsoftProFortran
    SXFortran

I suggest trying "mipsFortran":

    1.  Go to the top-level source directory.

    2.  Perform steps 3 through 5 mentioned near the end of the file
        INSTALL.html.

    3.  Ensure that the environment variable CPPFLAGS contains the
        string "-DmipsFortran", e.g.

            export CPPFLAGS=-DmipsFortran

    4.  Perform steps 6 through 9 mentioned near the end of the file
        INSTALL.html.

Please let me know how this works.

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>