Re: netcdf packages
I wanted to reply to the two parts of your mail separately, so please check
out this one and the next one.
On Thursday 14 December 2006 11:09, Kevin B. McCarty wrote:
> think it must have at least been built with the new g++:
>
> benjo (sid)[2]:~% apt-cache show libnetcdf++3| grep Depends
> Depends: [...], libstdc++6 (>= 4.1.0)
> ^^^^^^^^^^
>
> According to packages.qa.debian.org, the version of kst in Sid/Etch was
> built in November '06, long after the current version of netcdf was
> uploaded (in July '06). So any problems with kst's use of netcdf in
> Sid/Etch are not likely to be due to the C++ ABI transition.
>
>
> I don't quite understand the exact problem you are facing, though. If
> I have read your email correctly, you see the following:
>
> a) libnetcdf++3 package from Sid, kst-plugins package from Sid ==> Crash
> b) libnetcdf++3 package from your new .debs, kst-plugins package from
> Sid ==> Crash
> c) libnetcdf++3 package from your new .debs, kst-plugins package rebuilt
> against your new .debs ==> Works OK
Correct.
> This is weird: if you install your new packages of netcdf, the existing
> kst-plugins package (from Sid) on your system should automatically pick
> up the new libnetcdf_c++.so.3 library and function properly, fixing the
> crash. I can only think of two reasons why this would not work:
This could have something to do with the largefile support.
The --enable-64bits enables support for netcdf files over 2GB. This probably
changes some functions to return 64 bit instead of 32 bit numbers. Is the
appropriate solution to bump the soname in this case?
The crappy thing about this situation is that you can build the library with
or without the support for the large files. The good thing is the following:
if you opt for --enable-64bits, you can read all files, you will only write
new style files, however. If you don't --enable-64bits, you can only read and
write old style files. This may be why my netcdf files crash with kst. They
may be new style, and the kst plugin for netcdf may not handle the error
correctly when the netcdf lib says it can't read the file, or kst could be
failing when getting back an improperly sized return value.
To be perfectly honest with you, netcdf support is worthless if it doesn't
support the new style files. Most people are using them now.
> *) the soname of libnetcdf_c++.so has changed since the version in Sid
> (in which case the binary package name must be changed and indeed kst
> must then be rebuilt against the new library),
I think this is what you are referring to.
Was: libnetcdf.so.3.6.1
Now: libnetcdf.so.3.6.2
You may also be referring to the links to those files, which are
libnetcdf.so.3 in both cases.
> *) OR, the soname was not changed even though it should have been.
> (This is not an uncommon situation since C++ is hard to maintain a
> stable ABI in.) Actually, I seem to remember you saying that shared lib
> support was hacked into the Debian packages, meaning you will need to
> care for the soname yourself.
The sonames in the old version were an illusion. Should we diverge from
upstream on the soname?
wt
--
Warren Turkal
Reply to: