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, First, you can finish the netCDF installation by just commenting out the last test in the file ncdump/tst_lengths.sh, by changing the line: test `ls -l small2.nc | awk '{print $5}'` = 105; to # test `ls -l small2.nc | awk '{print $5}'` = 105; The specific problem that's breaking the test is that your "ls" command is not printing the "group" field or the name of your group is blank, so the fifth field that's being tested in the line -rw-r----- 1 chrisc 105 Feb 19 15:01 small2.nc is not "105", but "Feb". If I'd looked at the output more carefully last week, I should have seen this. It's possible you are using a non-standard "ls" command or you have "ls" aliased to something that omits the group name, such as "ls -o". One possible fix would be to use "/bin/ls -l -n small2.nc" instead of just "ls -l small2.nc", which would print the group GID number instead of group name, in case the group name is blank, and would avoid use of any alias defined for "ls". You could test that this works by making the appropriate substitution. Anyway, thanks for persisting and demonstrating the problem with the test. We'll have to think about the best fix for the next release. --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