Control: severity -1 important
Hello,
Matthias Klose, le Fri 11 Jul 2014 15:48:56 +0200, a écrit :
> > Shouldn't the package for kfreebsd* have the files in a different
> > sub-directory? linux just feels wrong on kfreebsd. I expect (but don't
> > know for sure) that the resolver is smart enough
Processing control commands:
> severity -1 important
Bug #750811 [brltty] brltty: FTBFS on kfreebsd*
Severity set to 'important' from 'serious'
--
750811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBS
> Shouldn't the package for kfreebsd* have the files in a different
> sub-directory? linux just feels wrong on kfreebsd. I expect (but don't
> know for sure) that the resolver is smart enough to look in a
> sub-directory matching the os, but as I would expect not look in the
> directory named by a
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
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.
>
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}/
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
Control: severity 751532 important
Am 15.06.2014 20:43, schrieb Paul Gevers:
> On 15-06-14 17:31, Samuel Thibault wrote:
>> This is most probably similar to #714559 which had the same issue.
>
> Yes, I agree. But interestingly enough, building liblouisutdml already
> failed in gcc-4.8 while brlt
Processing control commands:
> severity 751532 important
Bug #751532 [gcj-4.9-jdk] including /usr/lib/jvm/default-java/include/jni.h
fails on kfreebsd*
Severity set to 'important' from 'serious'
--
750811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750811
751532: http://bugs.debian.org/cg
On 15-06-14 17:31, Samuel Thibault wrote:
> This is most probably similar to #714559 which had the same issue.
Yes, I agree. But interestingly enough, building liblouisutdml already
failed in gcc-4.8 while brltty (and libbluray) only now start to fail
with gcc-4.9, so something must have changed.
Hello,
Paul Gevers, le Fri 13 Jun 2014 22:25:41 +0200, a écrit :
> 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 en
Processing commands for cont...@bugs.debian.org:
> # On 13-06-14 22:27, Debian Bug Tracking System wrote:
> # >> retitle -2 including /usr/lib/jvm/default-java/include/jni.h
> # > Bug #751532 [gcj-4.9-jdk] brltty: FTBFS on kfreebsd*
> # > Changed Bug title to 'including /usr/lib/jvm/default-java/i
Processing control commands:
> clone -1 -2
Bug #750811 [brltty] brltty: FTBFS on kfreebsd*
Bug 750811 cloned as bug 751532
> reassign -2 gcj-4.9-jdk
Bug #751532 [brltty] brltty: FTBFS on kfreebsd*
Bug reassigned from package 'brltty' to 'gcj-4.9-jdk'.
No longer marked as found in versions brltty/5
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/rule
Hi, [e-mail address of the java group was wrong, but ...]
Digging through it somewhat more, I now see in the build log that
gcj-4.9-jdk_4.9.0-5 is installed and is should have the files
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.9/include/jni_md.h
and
/usr/lib/jvm/java-1.5.0-gcj-4.9-kfreebsd-amd64/include
Hi Debian Java maintainers,
May I draw your attention to bug 750811 [1]? A rebuild of brltty fails
because it can't find jni_md.h on kfreebsd* archs. See below.
On 07-06-14 08:22, Paul Gevers wrote:
> On 07-06-14 07:15, Scott Kitterman wrote:
>> FTBFS on kfreebsd* during a binNMU as part of the t
On 07-06-14 07:15, Scott Kitterman wrote:
> FTBFS on kfreebsd* during a binNMU as part of the transition to drop
> python3.3.
Issue seems unrelated to python3.3 transition:
/usr/lib/jvm/default-java/include/jni.h:52:20: fatal error: jni_md.h: No
such file or directory
#include "jni_md.h"
My und
Package: brltty
Version: 5.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
FTBFS on kfreebsd* during a binNMU as part of the transition to drop
python3.3.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
18 matches
Mail list logo
