[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool versioning and sonames
From: |
Andreas Metzler |
Subject: |
Re: libtool versioning and sonames |
Date: |
Sun, 28 Oct 2007 13:28:54 +0100 |
User-agent: |
tin/1.9.2-20070201 ("Dalaruan") (UNIX) (Linux/2.6.22-2-686 (i686)) |
Ralf Wildenhues <address@hidden> wrote:
> * Andreas Metzler wrote on Sun, Oct 28, 2007 at 09:34:25AM CET:
>> [...] However, the way libtool
>> tries to represent this information in sonames (on Linux) is rather
>> strange, it goes straight from libgnutls.so.13 to libgnutls.so.23. Is
>> this huge jump just bug or is there a reason for it?
> The reason for it is simplicity in the version number calculation.
> There is no requirement for version numbers to be consecutive except
> for "consecutive looks nicer" and the finite number space. I assume
> its pressure to be far lower than the incompatible change a different
> version number calculation would make.
Hello,
Thanks for the explanation.
> The way libtool computes them, it even causes different major version
> numbers on different systems, so the above jump is even specific to the
> linux version_type and not all types.
I have somehow managed the evade the real question:
Are there libtool-supported archs whose versioning will break if we do
this
num c r a
2.1.1 22 1 9
2.1.2 14 0 0
instead of
num c r a
2.1.1 22 1 9
2.1.2 23 0 0
(I know it would work on linux, resulting in libgnutls.so.14.)
thanks, cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'