Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
On 04/06/2011 05:41 PM, Russ Rew wrote: > Andrey, > > >> But there are two changed constants in C interface: NC_WRITE (from 0x1 >> to 0x0001) and NC_NOCLOBBER (from 0x4 to 0x0004) used by ncopen and >> nccreate functions. So, the soname has been bumped: >> >> 4.1.1/lib> readelf -Wa libnetcdf.so.4.0.0|grep SONAME >> 0x0000000e (SONAME) Library soname: [libnetcdf.so.4] >> >> 4.1.2/lib> readelf -Wa libnetcdf.so.7.0.1|grep SONAME >> 0x0000000e (SONAME) Library soname: [libnetcdf.so.7] >> > How are those "changed constants"? "0x1" and "0x0001" are just > different representations of the same integer constant 1. Similarly > with "0x4" and "0x0004" for an integer 4. Changes in syntax for an > integer constant should not result in claims of an incompatible > interface or result in a new soname. This looks like another false > positive to me. > > --Russ > > You are right. It is a false positive too. The only reason for the version bump of C library I see for now is the very long list of improvements and bug-fixes between 4.1.1 and 4.1.2 in the change-log [1]. [1] http://linuxtesting.org/upstream-tracker/changelogs/netcdf/4.1.2/changelog.html -- Andrey Ponomarenko Department for Operating Systems at ISPRAS web: http://www.LinuxTesting.org mail: aponomarenko@xxxxxxxxx
netcdfgroup
archives: