[MINC-development] MINC with NetCDF 4.4?

[Steve M. Robbins]

Hi,

On August 23, 2015 08:21:02 AM Robert D. Vincent wrote:

> Yes, we are mostly building directly off the github tree these days. I have
> not tried building with NetCDF > 4.X. As you probably know, it's surprising
> to see these particular test failures, as the general transform code should
> not contain many code paths that rely on NetCDF.

Yes, but note that tests only fail if I enable MINC1 support (which is off by 
default).  Without MINC1 there are no failures.

 
> How did you add 4.4 to the build - i.e. what is the URL of the NetCDF
> tarball you are using?

I am using Debian "unstable" which contains 4.4 by default as of a few days 
ago.  Actually, I see the version tag is "4.4.0~rc2", so probably this:

http://www.unidata.ucar.edu/mailing_lists/archives/netcdfgroup/2015/msg00189.html

 
> Which project are you building - libminc, minc-tools, or minc-toolkit (the
> all-encompassing meta-project)?

I am presently building libminc.  Both master and develop branches show test 
failures.

Previously, I was building the old minc 2.2.00 (which I believe is the same as 
the current libminc + minc-tools ?) using netcdf 4.3.  I configured that with 
both MINC1 and MINC2 support and there were no test failures.  When netcdf 4.4 
showed up, there were test failures with this source base -- which is what 
prompted me to look at updating the minc sources.  

GIven all that, it really smells like netcdf 4.4 has changed something that 
minc1 fundamentally relies on.  I haven't had a chance to actually look at 
code, though.

Thanks,
-Steve

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: This is a digitally signed message part.
URL: <http://www.bic.mni.mcgill.ca/pipermail/minc-development/attachments/20150823/ed3f8f17/attachment.pgp>