This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 869517 - issues with JNI support on ARM
issues with JNI support on ARM
Product: Fedora
Classification: Fedora
Component: java-1.7.0-openjdk (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Deepak Bhole
Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
  Show dependency treegraph
Reported: 2012-10-24 03:14 EDT by Peter Robinson
Modified: 2012-10-30 11:52 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-10-30 11:52:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)

  None (edit)
Description Peter Robinson 2012-10-24 03:14:58 EDT
I'm seeing issues with compilation of packages which require JNI support. 

One example is libgda:

In configure we get the following error:
checking java compiler version... JAVA version used is Sun JRE 1.7 
checking for Java environment... in /usr/lib/jvm/java-1.7.0-openjdk-
checking for /usr/lib/jvm/java-1.7.0-openjdk- no
checking for /usr/lib/jvm/java-1.7.0-openjdk- no
checking for /usr/lib/jvm/java-1.7.0-openjdk- yes
checking for /usr/lib/jvm/java-1.7.0-openjdk- no
checking for /usr/lib/jvm/java-1.7.0-openjdk- yes
checking whether JNI programs can be compiled... configure: error: Cannot compile a simple JNI program. See config.log for details.

We're not getting a different set of deps than x86 but it looks like the openjdk are slightly different from a basic grep:

$ rpm -qlp java-1.7.0-openjdk-devel- | grep jni

$ rpm -qlp java-1.7.0-openjdk-devel- | grep jni
Comment 1 Andrew John Hughes 2012-10-30 09:16:57 EDT
These differences are benign; the ARM version uses an older version of IcedTea which supports the ARM port (hence the 6/9 difference) and doesn't yet have SystemTap support (so the .stp files are missing).

The issue here appears to lie in whatever JNI test is actually being run.  Attaching the config.log might be helpful.
Comment 2 Peter Robinson 2012-10-30 11:52:37 EDT
You are correct and it's now fixed. Thanks

Note You need to log in before you can comment on or make changes to this bug.