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

Re: gcj-4.4-jdk misses jni_md.h on kfreebsd platform

reassign 621878 db5.1

you have to include both <java_home>/include and <java_home>/include/linux.

On 04/20/2011 07:20 AM, Ondřej Surý wrote:
Just a quick note, the difference in gcj version between successful and unsuccessfull build is 4.4.5-9 vs 4.4.5-14

Ondřej Surý

On 20.4.2011, at 0:59, Ondřej Surý<ondrej@sury.org>  wrote:

On Tue, Apr 19, 2011 at 23:34, Matthias Klose<doko@debian.org>  wrote:
On 04/19/2011 11:11 PM, Ondřej Surý wrote:

reopen 621878
reassign 621878 gcj-4.4-jdk
retitle 621878 gcj-4.4-jdk misses jni_md.h on kfreebsd
affects 621878 +db4.6 db4.7 db4.8 db
thank you

Dear Debian GCC Team please look at http://bugs.debian.org/621878, it
looks like jni_md.h header is missing there which is causing FTBFSes
for dbX.Y packages.

You can find failed build logs here:



is this a kfreebsd issue?

Version 5.1.25-1 built fine:

Version 5.1.25-2 started to fail on kfreebsd-{amd64,amd32}. The buildd
failures on ia64, mips, s390 and sparc are of different nature.

The error from 5.1.25-2 build is:
libtool: compile:  gcc -c -I. -I../src -I/usr/include/tcl8.5
-D_GNU_SOURCE -D_REENTRANT -I/usr/lib/jvm/default-java/include -Wall
-g -O2 -I/usr/lib/jvm/default-java/include -fno-strict-aliasing
../lang/java/libdb_java/db_java_wrap.c -fPIC -DPIC -o
In file included from ../lang/java/libdb_java/db_java_wrap.c:137:0:
/usr/lib/jvm/default-java/include/jni.h:52:20: fatal error: jni_md.h:
No such file or directory

The same line compiles with lots of warnings, but compiles. So
something must have changed on gcj side between the two builds which
broke it.

looks more like you are assuming that the default
version of gcc matches the one for gcj. please reassign back.

Could you please elaborate? Are you trying to say that calling:

gcc -c -I. -I../src -I/usr/include/tcl8.5 -D_GNU_SOURCE -D_REENTRANT -I/usr/lib/jvm/default-java/include -Wall -g -O2 -I/usr/lib/jvm/default-java/include -fno-strict-aliasing ../lang/java/libdb_java/db_java_wrap.c  -fPIC -DPIC -o .libs/db_java_wrap.o

is wrong when gcc is different version than gcj? Well the build log
say gcc-4.4 and gcj-4.4-*, so there should be nothing wrong.

Ondřej Surý<ondrej@sury.org>

Reply to: