[MINC-development] MINC with NetCDF 4.4?

[Robert D. Vincent]

Hi Steve,

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.

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

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

    -bert

On Sat, Aug 22, 2015 at 11:20 PM, Steve M. Robbins <steve at sumost.ca> wrote:

> Hi,
>
> Debian just upgraded NetCDF to version 4.4.0, which broke the MINC build.
> Debian was using MINC 2.2.00, so I spent some time today updating MINC.
>
> I can't find any release tarballs more recent than 2.2.00 (from 2012!).
> So I
> presume everyone is working from github tree?  I updated to the tip of the
> 'master' branch and discovered that if compiled with MINC1 support, some
> tests
> fail.  They fail also in develop:
>
> The following tests FAILED:
>          25 - test_xfm_3 (Failed)
>          26 - copy_xfm (Failed)
>          27 - verify_xfm_1 (Failed)
>          28 - verify_xfm_float (Failed)
>          29 - verify_xfm_short (Failed)
>          30 - verify_xfm_byte (Failed)
>          31 - verify_xfm_2 (Failed)
>
>
> Anyone have experience with NetCDF 4.4?
>
> Thanks,
> -Steve
>
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bic.mni.mcgill.ca/pipermail/minc-development/attachments/20150823/66e29468/attachment.html>