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.
Benoit, >>>> *** Testing ncgen and ncdump for UTF8 support... >>>> *** creating classic offset file with utf8 characters... >>>> *** dump and compare utf8 output... >>>> Binary files utf8.cdl and ./ref_tst_utf8.cdl differ >>>> FAIL: run_utf8_tests.sh OK, thanks, the file utf8.cdl that you sent appeared to be truncated, so it's first 106 bytes matched what was expected, but the last 54 bytes were not there. The only cause I can think of for this is failure to call fflush(stdout) at the end of the program, before calling exit, although this doesn't seem to be necessary on any of the other platforms on which we test. To determine if this fix makes the problem go away, could you please insert the statement fflush(stdout); in the source file ncdump.c just before the exit call at the end of the file, so that the last few lines of ncdump/ncdump.c would now look like } fflush(stdout); #ifdef vms exit(EXIT_SUCCESS); #else return EXIT_SUCCESS; #endif } Then run "make check" again in the ncdump directtory to see if this fixes the problem. I am also putting this in the snapshot release, becasue it seems harmless on other platforms, so you could also wait to get the next snapshot release and try that instead. In either case, please let me know if this fixes the problem you are seeing on OpenBSD. Thanks! --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: JLS-704865 Department: Support netCDF Priority: Normal Status: Closed