[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#750811: brltty: FTBFS on kfreebsd*



Control: clone -1 -2
Control: reassign -2 gcj-4.9-jdk
Control: retitle -2 including /usr/lib/jvm/default-java/include/jni.h
fails on kfreebsd*
Control: block -1 by -2

On 13-06-14 20:45, Paul Gevers wrote:
> I am investigating the situation in a porterbox.

I think I found the issue. In debian/rules we declare the $JAVA_HOME as
/usr/lib/jvm/default-java. This is a softlink that finally ends in
/usr/lib/jvm/java-1.5.0-gcj-4.9-kfreebsd-amd64/ From the include
directory there we include jni.h. jni.h itself includes jni_md.h that is
found in the linux subfolder (we are building on kfreebsd, so what is
linux doing here?) It seems that in the past this used to work, however,
now it does not anymore (maybe in gcc-4.9 the logic got improved?)

I can confirm that if I set the $JAVA_HOME to
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.9 (which is the canonical location of
the header files) than the package builds. In that directory there is no
sub-directory so the jni_md.h file is found. Of course, coding that
directory in d/rules defeats the purpose of the default-jdk dependency
chain, so I think it should be fixed in gcj-4.9-jdk. Please correct me
if I am wrong.

Paul
P.S. one other issue that I found was that the debian/rules file does
not define $DEB_HOST_ARCH_OS. Fix is trivial of course.

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: