Hi, [e-mail address of the java group was wrong, but ...] Digging through it somewhat more, I now see in the build log that gcj-4.9-jdk_4.9.0-5 is installed and is should have the files /usr/lib/gcc/x86_64-kfreebsd-gnu/4.9/include/jni_md.h and /usr/lib/jvm/java-1.5.0-gcj-4.9-kfreebsd-amd64/include/linux/jni_md.h So, is the problem in brltty that it doesn't look in these multiarch locations? I am investigating the situation in a porterbox. Paul On 13-06-14 20:06, Paul Gevers wrote: > Hi Debian Java maintainers, > > May I draw your attention to bug 750811 [1]? A rebuild of brltty fails > because it can't find jni_md.h on kfreebsd* archs. See below. > > On 07-06-14 08:22, Paul Gevers wrote: >> On 07-06-14 07:15, Scott Kitterman wrote: >>> FTBFS on kfreebsd* during a binNMU as part of the transition to drop >>> python3.3. >> >> Issue seems unrelated to python3.3 transition: >> /usr/lib/jvm/default-java/include/jni.h:52:20: fatal error: jni_md.h: No >> such file or directory >> #include "jni_md.h" >> >> My understanding is that the file should come from gcj-4.*-jdk which we >> like to pull in via build-dep default-jdk. However, on kfreebsd* that is >> rather a low version. I have no knowledge of java at all, but I expect >> the default-jdk to be so low for a reason. /do we need to explicitly add >> the gcj package for kfreebsd*? > > Do you consider this a bug in default-jdk (that it does not depend on > the right version of gcj on kfreebsd*)? Or should it just be expected > that default-jdk does not provide the required file and do we (for > kfreebsd* need to explicitly depend on the gcj package? > > Please clone this bug if appropriate. > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750811 >
Attachment:
signature.asc
Description: OpenPGP digital signature