Bug#714559: gcj-4.8-jdk: jni_md.h not found

[Matthias Klose <doko@debian.org>]

On 06/30/13 21:58, Samuel Thibault wrote:
> Package: gcj-4.8-jdk
> Version: 4.8.1-5
> Severity: important
> 
> Hello,
> 
> See this build log for the details:
> 
> https://buildd.debian.org/status/fetch.php?pkg=liblouisutdml&arch=kfreebsd-amd64&ver=2.4.0-1&stamp=1371429318
> 
> But basically the interesting part is:
> 
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLBU_PATH=\"/usr/share/liblouisutdml/lbu_files/\" -DLIBLOUIS_TABLES_PATH=\"/usr/share/liblouis/tables/\"  -I/usr/lib/jvm/default-java/include -I/usr/include/liblouis -I/usr/include/libxml2   -O2 -MT liblouisutdml_la-Jliblouisutdml.lo -MD -MP -MF .deps/liblouisutdml_la-Jliblouisutdml.Tpo -c -o liblouisutdml_la-
> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLBU_PATH=\"/usr/share/liblouisutdml/lbu_files/\" -DLIBLOUIS_TABLES_PATH=\"/usr/share/liblouis/tables/\" -I/usr/lib/jvm/default-java/include -I/usr/include/liblouis -I/usr/include/libxml2 -O2 -MT liblouisutdml_la-Jliblouisutdml.lo -MD -MP -MF .deps/liblouisutdml_la-Jliblouisutdml.Tpo -c ../java/Jliblouisutdml.c  -fPIC -DPIC -o .libs/liblo
> In file included from ../java/Jliblouisutdml.h:2:0,
>                  from ../java/Jliblouisutdml.c:29:
> /usr/lib/jvm/default-java/include/jni.h:52:20: fatal error: jni_md.h: No such file or directory
> compilation terminated.
> 
> The Debian package build-depends on default-jdk, and uses
> CPPFLAGS += -I/usr/lib/jvm/default-java/include

this looks incomplete in the package build. The os directory should be added too.

> to point at the default java implementation. However, on kfreebsd this
> directory points at /usr/lib/jvm/java-1.5.0-gcj-4.7/include, which has a
> jni.h which unconditionally #includes "jni_md.h", assuming they are in> 

> the same directory, but jni_md.h is in a linux/ subdirectory.

I think I have one compat link, maybe where it shouldn't be. The right thing
from my point of view is to add both include directories.

> At this point I'm not sure what we are supposed to do: disable Java
> extensions on such platforms (because jni_md.h perhaps doesn't work on
> kfreebsd?), or is there a standard way to get jni.h working?

well, maybe just try to use the linux one for kfreebsd as well?  didn't test it,
but maybe the openjdk kfreebsd porters will know.

  Matthias