cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Malte Pickhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8927) Mark libjna-java + libjna-jni as incompatible in debian package
Date Thu, 21 Jan 2016 10:43:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110408#comment-15110408
] 

Malte Pickhan commented on CASSANDRA-8927:
------------------------------------------

I'm not really sure if it's a good idea to override kernel libraries?

> Mark libjna-java + libjna-jni as incompatible in debian package
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-8927
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8927
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: Debian
>            Reporter: Robert Stupp
>            Assignee: Michael Shuler
>            Priority: Minor
>             Fix For: 3.0.x
>
>
> Current Debian (Wheezy) might bring {{libjna-java}} in version 3.2.7-4, which has incompatible
{{libjnadispatch.so}} because since C* 2.1 we use JNA 4.0.0 (the native stuff changed):
> jna.jar includes all binaries for all supported platforms - so there's no need for libjna
installed separately.
> Since CASSANDRA-8714 has been committed, the incompatibility manifests in {{java.lang.NoClassDefFoundError:
Could not initialize class com.sun.jna.Native}} (which is caused by outdated libjna-java installed
via apt).
> Note: Debian jessie adds new package {{libjna-jni}} (4.1.0-1) in addition to {{libjna-java}}
(4.1.0-1) - both contain the {{libjnidispatch.so}}. Although these seem to work, we might
hit the same issue when there's a need to upgrade JNA to 4.2.x sometime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message