* Florent Bayle <[EMAIL PROTECTED]> [2006-03-27 19:11]: > This bug happens when you build with : > - gcc 4.0 and gcj 4.1/libgcj7-dev > - gcc 4.1 and gcj 4.0/libgcj6-dev. > > But it doesn't happens if you build with : > - gcc 4.1 and gcj 4.1/libgcj7-dev > - gcc 4.0 and gcj 4.0/libgcj6-dev. > > So if you want to build it with gcc-4.1, you need to have gcj 4.1/libgcj7-dev > installed (and to modify the debian/control).
Good to know, thanks for investigating! Now I can re-try the other packages that failed with the jni.h error too... I didn't have time to investigate this problem yet, so thanks a lot for doing my work. :) > I don't know if it's a bug, because the option --with-java is passed to > the ./configure, so as it's said in the log, it assume that "the java > directory is specified in CFLAGS". But I will nevertheless report it. > I think that I will let this but open until gcc 4.1 becomes the > official gcc version in sid (I will upload a new version of the > package depending on libgcj7-dev as soon as it will be the case). Oh, I wouldn't leave the bug open for that. Once 4.1 is the default, I'm sure people are told... I'd only leave the bug open if the configure script is buggy (saying it doesn't do java but then doing something to fail when there's no java). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
