On 2019-11-08 13:04 +0100, Steve Keller wrote:
> Could someone please explain how library version numbers, shared object
> names (SONAME), and symbol version are used in Debian?
>
> I have a problem with libcurl.so.4 and a binary linked against it. In
> Debian stretch I have the package libcurl3
On Friday, November 08, 2019 10:54:31 AM Roberto C. Sánchez wrote:
> On Fri, Nov 08, 2019 at 10:49:47AM -0500, rhkra...@gmail.com wrote:
> > On Friday, November 08, 2019 09:08:07 AM Roberto C. Sánchez wrote:
> > > For example, the return type of a function can be changed from bool to
> > > int and
On Fri, Nov 08, 2019 at 10:49:47AM -0500, rhkra...@gmail.com wrote:
> On Friday, November 08, 2019 09:08:07 AM Roberto C. Sánchez wrote:
> >
> > For example, the return type of a function can be changed from bool to
> > int and that will not change the SONAME.
>
> The items mentioned in the nex
On Friday, November 08, 2019 09:08:07 AM Roberto C. Sánchez wrote:
> On Fri, Nov 08, 2019 at 01:04:14PM +0100, Steve Keller wrote:
...
> > - Why do many libraries have version numbers that don't match their
> >
> > SONAME? I often find that confusing.
>
> Because changes which do not change
On Fri, Nov 08, 2019 at 01:04:14PM +0100, Steve Keller wrote:
> Could someone please explain how library version numbers, shared object
> names (SONAME), and symbol version are used in Debian?
>
This is a complex set of interactions (that I am fairly certain I do not
fully understand myself), but
On Fri, Nov 08, 2019 at 01:04:14PM +0100, Steve Keller wrote:
> I have a problem with libcurl.so.4 and a binary linked against it. In
> Debian stretch I have the package libcurl3 installed and can run a
> binary (I have no source code for it) linked against that libcurl.
>
> Although the package
On 2019-11-08, Steve Keller wrote:
> Could someone please explain how library version numbers, shared object
> names (SONAME), and symbol version are used in Debian?
>
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
--
“The cradle rocks above an abyss, and common sense tells us th
Could someone please explain how library version numbers, shared object
names (SONAME), and symbol version are used in Debian?
I have a problem with libcurl.so.4 and a binary linked against it. In
Debian stretch I have the package libcurl3 installed and can run a
binary (I have no source code for
8 matches
Mail list logo