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

[netCDF #OFK-443206]: iso_c_binding

Hi Dan,

It looks like this problem has been fixed in the current development version,
where the relevant statments in fortran/module_netcdf_nc_data.F90 are:

#ifndef HAVE_TS29113_SUPPORT
! Integer, Parameter :: C_PTRDIFF_T = C_SIZE_T
 Integer, Parameter :: C_PTRDIFF_T = C_INTPTR_T

There may be other related differences as well between our 4.4-beta4 version and
the beta1 version you are using.  Please try accessing the latest development
version, either from our new GitHub repository or our svn repository.  These two
versions currently match, but the svn repository is now frozen, as we've moved 


You can get the 4.4=beta4 distribution with:

  git clone http://github.com/Unidata/netcdf-fortran.git


> Full Name: Dan Nagle
> Email Address: address@hidden
> Organization: NCAR/CISL
> Package Version: netcdf-fortran-4.4-beta1
> Operating System: RHEL6 Yellowstone
> Hardware: x86_64
> Description of problem: make[2]: Entering directory 
> `/glade/u/apps/opt/netcdf/4.3.0/netcdf-fortran-4.4-beta1/fortran'
> gfortran -DHAVE_CONFIG_H -I. -I.. -I../libsrc     -g -O2 -c -o 
> module_netcdf_nc_data.o module_netcdf_nc_data.F90
> module_netcdf_nc_data.F90:73.34:
> Integer, Parameter :: C_PTRDIFF_T = C_SIZE_T
> 1
> module_netcdf_nc_data.F90:30.5:
> USE ISO_C_BINDING  ! All subsequent USE associations of netcdf_nc_data
> 2
> Error: Symbol 'c_ptrdiff_t' at (1) conflicts with symbol from module 
> '__iso_c_binding', use-associated at (2)
> make[2]: *** [module_netcdf_nc_data.o] Error 1
Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu

Ticket Details
Ticket ID: OFK-443206
Department: Support netCDF
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly 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.