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

20040617: G95 netCDF support (cont.)

Andy & Charlie,

> To: netCDF Support <address@hidden>
> cc: Charlie Zender <address@hidden>
> From: "Andy Vaught" <address@hidden>
> Subject: Re: G95 netCDF support
> Organization: ?
> Keywords:  200406161842.i5GIgetK014375 netCDF g95

The above message contained the following:

>   I just wanted to add that g95 (available at http://www.g95.org)
> follows the f2c calling conventions where possible.  Fortran 95
> extentions to f77 require extensions to the ABI, but calls to
> netcdf subroutines should be identical to g77.  If they're not, I'm
> considering them bugs.

Perhaps that explains the problem Charlie encountered: g95(1) follows
the f2c(1) calling-conventions but Charlie appears to have told the
netCDF build to use PGI calling-conventions:

    Making `test' in directory /data/zender/tmp/netcdf-3.5.1/src/nctest

    make[2]: Entering directory `/data/zender/tmp/netcdf-3.5.1/src/nctest'
    /usr/bin/gcc -c -O -g -I../libsrc  -D_FILE_OFFSET_BITS=64
    -D_LARGEFILE_SOURCE -DNDEBUG -DpgiFortran varget.c

Note the "-DpgiFortran" in the above.

Charlie, try again from scratch (do a "make distclean") only this time
ensure that the environment variable CPPFLAGS contains the string
"-Df2cFortran" rather than "-DpgiFortran" before executing the configure
script.

>    Thanks,
>      Andy

Regards,
Steve Emmerson

> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publically available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.