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

[netCDF #GYB-190937]: NetCDF 4.6.1 build issue on Windows with HDF5 1.10.2

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #GYB-190937]: NetCDF 4.6.1 build issue on Windows with HDF5 1.10.2
  • Date: Thu, 26 Jul 2018 10:57:14 -0600
Hello Nalini,

I will review these logs and follow up soon. Thanks!

-Ward

> Adding Ward to the mail.
> 
> Thanks,
> Nalini
> 
> From: Nalini Vishnoi
> Sent: Wednesday, July 25, 2018 1:58 PM
> To: address@hidden; Ellen Johnson <address@hidden>
> Subject: NetCDF 4.6.1 build issue on Windows with HDF5 1.10.2
> 
> Hello NetCDF developers,
> 
> I am a developer at MathWorks who works on netcdf functionality. Recently we 
> upgraded our netCDF version to 4.6.1 and also our HDF5 library to 1.10.2.
> While the build and tests run fine on Mac and Linux OS, the netCDF build 
> fails on Windows.
> 
> I have attached the logs to this email. I also found a similar issue 
> discussed over here:
> https://www.unidata.ucar.edu/support/help/MailArchives/netcdf/msg13415.html
> 
> Can you point us in the right direction? Is there something we need to change 
> in order to make the build pass on Windows?
> 
> Please note that I have tried the above with 2 different Visual Studio 
> compilers 2013 and 2015 but both of them fail with the same log.
> 
> Looking forward to your reply.
> 
> Thanks,
> Nalini
> 
> 


Ticket Details
===================
Ticket ID: GYB-190937
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.