The netcdf-c source directory contains is own bzip2 implementation in the plugins directory. My speculation is that somehow, the plugins code is picking up your version and there is some kind of API mismatch. Not sure how to fix. If you are explicitly including bzip with -lbzip2 or -lbz2 you might try removing it. > On a CentOS 7 PC: > > uname -a = Linux genesis 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 > 14:49:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > redhat-release = CentOS Linux release 7.6.1810 (Core) > > bzip2 is installed: > > address@hidden netcdf-c-4.6.2]# rpm -qa |grep bzip > bzip2-libs-1.0.6-13.el7.i686 > bzip2-devel-1.0.6-13.el7.x86_64 > bzip2-1.0.6-13.el7.x86_64 > bzip2-libs-1.0.6-13.el7.x86_64 > > The error from "make check" is not very helpful: > > ----------- > + /local/src/NetCDF/netcdf-c-4.6.2/nc_test4/test_filter > fail (218): NetCDF: Filter error: bad id or parameters or filter library > non-existent > > *** Testing API: bzip2 compression. > show parameters for bzip2: level=9 > show chunks: chunks=4,4,4,4 > FAIL tst_filter.sh (exit status: 1) > =Dennis Heimbigner Unidata Ticket Details =================== Ticket ID: DWJ-218174 Department: Support netCDF Priority: Normal Status: Open =================== 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.
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.