Bug#640938: tijmp: FTBFS: configure: error: Does JAVA_HOME point to the java SDK directory?
Package: tijmp
Version: 0.8+dfsg-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)
tijmp fails to build as it can't find the path to openjdk:
| checking dynamic linker characteristics... GNU/Linux ld.so
| checking how to hardcode library paths into programs... immediate
| checking whether stripping libraries is possible... yes
| checking if libtool supports shared libraries... yes
| checking whether to build shared libraries... yes
| checking whether to build static libraries... no
|
| checking /usr/lib/jvm/java-6-openjdk/include/linux/jni_md.h usability... no
| checking /usr/lib/jvm/java-6-openjdk/include/linux/jni_md.h presence... no
| checking for /usr/lib/jvm/java-6-openjdk/include/linux/jni_md.h... no
| checking /usr/lib/jvm/java-6-openjdk/include/jni_md.h usability... no
| checking /usr/lib/jvm/java-6-openjdk/include/jni_md.h presence... no
| checking for /usr/lib/jvm/java-6-openjdk/include/jni_md.h... no
| configure: error: Does JAVA_HOME point to the java SDK directory?
| make: *** [debian/stamp-autotools] Error 1
It sets JAVA_HOME to /usr/lib/jvm/java-6-openjdk, but this path has
changed starting with openjdk-6 version 6b23~pre8-2.
Full build log is available (s390x, but also fails on other
architectures):
http://buildd.debian-ports.org/status/fetch.php?pkg=tijmp&arch=s390x&ver=0.8%2Bdfsg-5&stamp=1314740547
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Reply to: