Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: xtide - Calculate tide all over the world
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211626
------- Additional Comments From pertusus(a)free.fr 2006-10-21 11:34 EST -------
(In reply to comment #9)
> /sbin/ldconfig $(pwd)/libtcd || :
> is very dubious. In my opinion it shouldn't be there.
I thought that, however, without this I get:
+ LD_LIBRARY_PATH=/home/tasaka1/rpmbuild/BUILD/xtide-2.9dev/libtcd
+ ./tcd-utils/build_tide_db harmonics-2004-06-14.tcd harmonics-2004-06-14.txt
./tcd-utils/build_tide_db: error while loading shared libraries: libtcd.so.2:
cannot open shared object file: No such file or directory
Strange. It works for me when I go to the tcd-utils directory
and run it by hand. It gives me the error without LD_LIBRARY_PATH=
> I don't see why the somajor/minor/ver should be different
from 0.0.0.
Umm, upstream has released libtcd version 1, which is API imcompatible
with version 2. Through version 2 libctd seems API compatible.
So I want to have SOMAJOR number 2 (and others similar).
How do you think of soname versioning?
If I'm not wrong upstream has never release any dynamic library, they
may (in fact they should) begin with a soname of 0. The soname tracks
ABI incompatible changes, not API changes.
-------------------------------------------------------------------------
In short:
Well, before fixing this, will you tell me how do you think of
A. libtcd and tcd-utils release numbering (0<->1)
libtcd 0., tcd-utils directly the release number
B. libtcd.so share object loading problem
It works when doing things by hand, I'll try a rpmbuild.
C. soname versioning
Begin with 0 for soname and 0.0.0 for library.
--
Configure bugmail:
https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.