avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suraj Acharya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-2063) C: VERSION, SOVERSION not set correctly for shared library
Date Sat, 05 Aug 2017 01:31:02 GMT

    [ https://issues.apache.org/jira/browse/AVRO-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115191#comment-16115191

Suraj Acharya commented on AVRO-2063:

Hey [~edmonds],
Can you make a similar patch on the avro project.
I am pretty sure others will appreciate the fix too.


> C: VERSION, SOVERSION not set correctly for shared library
> ----------------------------------------------------------
>                 Key: AVRO-2063
>                 URL: https://issues.apache.org/jira/browse/AVRO-2063
>             Project: Avro
>          Issue Type: Bug
>          Components: c
>    Affects Versions: 1.8.2
>            Reporter: Robert Edmonds
>            Priority: Minor
> 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

View raw message