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-18.104.22.168/jre
checking for /usr/lib/jvm/java-1.7.0-openjdk-22.214.171.124/jre/include/jni.h... no
checking for /usr/lib/jvm/java-1.7.0-openjdk-126.96.36.199/jre/jni.h... no
checking for /usr/lib/jvm/java-1.7.0-openjdk-188.8.131.52/jre/../include/jni.h... yes
checking for /usr/lib/jvm/java-1.7.0-openjdk-184.108.40.206/jre/../include/./jni_md.h... no
checking for /usr/lib/jvm/java-1.7.0-openjdk-220.127.116.11/jre/../include/linux/jni_md.h... 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-18.104.22.168-2.3.3.fc17.1.x86_64.rpm | grep jni
$ rpm -qlp java-1.7.0-openjdk-devel-22.214.171.124-2.3.1.fc17.2.armv7hl.rpm | grep jni
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.
You are correct and it's now fixed. Thanks