Am 23.06.2014 17:06, schrieb Samuel Thibault:
> Matthias Klose, le Mon 23 Jun 2014 16:12:11 +0200, a écrit :
>> Am 23.06.2014 16:05, schrieb Samuel Thibault:
>>> Matthias Klose, le Mon 23 Jun 2014 15:50:49 +0200, a écrit :
>>>> so for now packages building jni bindings should have both
>>>> <jdk_home>/include
>>>> and <jdk_home>/include/linux on the include path.
>>>
>>> Well, this looks a bit odd. Upstream is used to just
>>> -I${JAVA_HOME}/include, and it works fine with other JDKs,
>>
>> can you prove your claim? I don't see any java upstream providing jni_md.h in
>> ${JAVA_HOME}/include (besides the openjdk debian package).
>
> I was using openjdk from Debian indeed, but also some cygwin java
> installation, which doesn't happen to make jni.h unconditionally include
> jni_md.h, thus no such issue.
>
> I've dug a bit and found
> https://web.archive.org/web/20120630000332/http://java.sun.com/products/jdk/faq/jni-j2sdk-faq.html
> which doesn't even talk about linux/ ... So I don't really know what
> I'm supposed to tell upstream, which does support most OS, including
> windows, solaris, freebsd, etc.
in FAQ 13 it does talk about solaris, and mentions that "Just <jdk>/include is
not suffcient". However the name of this OS directory is not standardized,
except for solaris, linux, and maybe macosx.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53a848e6.6070...@debian.org
