[ https://issues.apache.org/jira/browse/MESOS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14607576#comment-14607576 ]
Jihun Kang commented on MESOS-2216: ----------------------------------- Does anyone work on this issue? If not, can I start to work on this issue? > The "configure" phase breaks with the IBM JVM. > ---------------------------------------------- > > Key: MESOS-2216 > URL: https://issues.apache.org/jira/browse/MESOS-2216 > Project: Mesos > Issue Type: Bug > Affects Versions: 0.20.1, 1.0.0 > Environment: Ubuntu / x86_64 > Reporter: Tony Reix > > ./configure does not work with IBM JVM, since it looks for a directory: > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server x86_64 > /usr/lib/jvm/ibm-java-ppc64le-71/jre/lib/ppc64le/server PPC64 LE > that does not exist for the IBM JVM. > Though this directory does exist for Oracle JVM and Open JDK: > /usr/lib/jvm/jdk1.7.0_71/jre/lib/amd64/server Oracle JVM > /usr/lib/jvm/java-1.7.0-openjdk-amd64/jre/lib/amd64/server OpenJDK > However, the files: > libjsig.so > libjvm.so (3 versions) > do exist for IBM JVM. > Anyway, creating the server directory and copying the files (tried with the 3 > versions of libjvm.so) does not fix the issue: > checking whether or not we can build with JNI... > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlopen' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlclose' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlerror' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlsym' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dladdr' > Something (dlopen, dlclose, dlerror, dlsym, dladdr) is missing in IBM JVM. > So, either the configure step relies on a feature that is not in the Java > standard but only in the Oracle JVM and OpenJDK, or the IBM JVM lacks part of > the Java standard. > I'm not an expert about this. So, I'd like Mesos people to experiment with > IBM JVM. Maybe there is another solution for this step of the Mesos configure > that would work with all 3 JVMs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)