Bug#751532: Bug#750811: Bug#751532: Bug#750811: brltty: FTBFS on kfreebsd*

2014-06-23 Thread Matthias Klose
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 /inclu

Bug#751532: Bug#750811: Bug#751532: Bug#750811: brltty: FTBFS on kfreebsd*

2014-06-23 Thread 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 > >> /include > >> and /include/linux on the include path. >

Bug#751532: Bug#750811: Bug#751532: Bug#750811: brltty: FTBFS on kfreebsd*

2014-06-23 Thread Matthias Klose
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 /include >> and /include/linux on the include path. > > Well, this looks a bit odd. Upstream is used to just > -I${JAVA_HOME}/

Bug#751532: Bug#750811: Bug#751532: Bug#750811: brltty: FTBFS on kfreebsd*

2014-06-23 Thread 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 /include > and /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, should it re