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.
Chris, Thanks for running the tests, and sorry it's taken so long to respond. You ran everything correctly, and I'm assuming you get compiler warnings where we don't just because of different versions of the compiler. Please, at your convenience, run these 2 commands in the ncdump directory of your source distribution, after the "make check" fails, and send me the outputs: ../ncgen/ncgen -b -k64-bit-offset -x small2.cdl ls -l small2.nc For comparison, here's what I see when I run these: $ ../ncgen/ncgen -b -k64-bit-offset -x small2.cdl $ ls -l small2.nc -rw-rw-r-- 1 russ ustaff 105 Feb 19 14:07 small2.nc It's the "105" file size that is being tested. If that's different for you, we may be making assumptions that may not be true on all file systems. If you get a file size of 105, then there's sometthing wrong with the way that is being tested. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: CSW-380765 Department: Support netCDF Priority: Normal Status: Closed