Hello Sean et. al.,
I've spent the last couple of days trying to clean up the netCDF-Fortran
F90 documentation, as part of the larger documentation overhaul. That is
nearly finished, and I would like to announce new versions of the
netCDF-Fortran and C++ interfaces at the same time I announce the next
netCDF-C release candidate. Barring any more last minute bugs/issues, I'd
like that to happen within the next few (business) days. Incidentally,
thank you to everybody who took the time to provide feedback on the first
netCDF-C 4.4.1 release candidate!
Thanks all, have a great day,
-Ward
On Fri, May 6, 2016 at 8:57 AM, Sean Byland <seanb@xxxxxxxx> wrote:
> Hello,
> I have someone that is looking for a fix for:
> https://github.com/Unidata/netcdf-c/issues/183
>
> and would like to know when netcdf-fotran 4.4.4 will be released?
>
> I downloaded and verified that the fix is netcdf-fortran master branch and
> suggested they could build/use it as a work around, but I’m not sure how
> stable you all consider master to be?
>
> Thanks for any info.
> Sean B.
>
> P.S. If anyone on this forum is using Cray’s Programming environment, this
> is how I built netcdf-fortran with intel’s compiler:
> #!/bin/bash
> source $MODULESHOME/init/bash
>
> wget https://github.com/Unidata/netcdf-fortran/archive/master.zip
> unzip master.zip
> pushd netcdf-fortran-master
> module swap PrgEnv-cray PrgEnv-intel
> export CRAYPE_LINK_TYPE=dynamic
> export CRAY_CPU_TARGET=x86-64
> module load cray-netcdf
> autoreconf -i
> ./configure CC=cc FC=ftn
> make -j
> popd
>
> ftn ncvptg_test.f netcdf-fortran-master/fortran/.libs/libnetcdff.a
>
> _______________________________________________
> netcdfgroup mailing list
> netcdfgroup@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
