mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihun Kang (JIRA)" <>
Subject [jira] [Updated] (MESOS-2216) The "configure" phase breaks with the IBM JVM.
Date Wed, 01 Jul 2015 02:21:04 GMT


Jihun Kang updated MESOS-2216:
    Attachment: MESOS-2216_1.patch

This patch made for Mesos 0.22.1.

> The "configure" phase breaks with the IBM JVM.
> ----------------------------------------------
>                 Key: MESOS-2216
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.20.1, 1.0.0
>         Environment: Ubuntu / x86_64
>            Reporter: Tony Reix
>         Attachments: MESOS-2216_1.patch
> ./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:
>   (3 versions)
> do exist for IBM JVM.
> Anyway, creating the server directory and copying the files (tried with the 3 versions
of 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/
undefined reference to `dlopen'
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/ undefined reference to
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/ undefined reference to
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/ undefined reference to
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/ undefined reference to
> 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

This message was sent by Atlassian JIRA

View raw message