You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2018/12/10 19:23:00 UTC

[jira] [Resolved] (AVRO-2063) C: VERSION, SOVERSION not set correctly for shared library

     [ https://issues.apache.org/jira/browse/AVRO-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved AVRO-2063.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

> C: VERSION, SOVERSION not set correctly for shared library
> ----------------------------------------------------------
>
>                 Key: AVRO-2063
>                 URL: https://issues.apache.org/jira/browse/AVRO-2063
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: c
>    Affects Versions: 1.8.2
>            Reporter: Robert Edmonds
>            Priority: Minor
>             Fix For: 1.9.0
>
>
> Hi,
> I'm attempting to package avro-c for Debian. While doing so, I noticed that the libavro.so symlink that gets installed points directly to the libavro.so.23.0.0 library file, without an intermediate "libavro.so.23" symlink, and that the SONAME embedded in the library file is set to "libavro.so.23.0.0", rather than "libavro.so.23", which is what I would expect for a library trying to follow the libtool-style current/revision/age scheme on Linux systems.
> It looks like the recommended way to get CMake to produce the typical symlink chain and SONAME is to set the VERSION property to "23.0.0" and the SOVERSION to 23 on the shared library target. See this article for details: http://pusling.com/blog/?p=352.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)