[ https://issues.apache.org/jira/browse/CASSANDRA-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980627#comment-14980627 ]
Michael Shuler commented on CASSANDRA-8927: ------------------------------------------- I see three different {{cassandra.in.sh}} files in bin/, debian/, and tools/bin/ - is this relevant to all of them? > 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 > Fix For: 2.1.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)