Michael Biebl:
Am 06.09.2013 02:49, schrieb Michael Biebl:
/usr/include/sys/vnode.h:41:27: fatal error: sys/rangelock.h: No such
file or directory
#include sys/rangelock.h
FWIW, this looks like a bug in sys/vnode.h or kfreebsd-kernel-headers.
Thanks. Fixed in 9.2~2.
--
Robert Millan
Michael Biebl:
Source: libgtop2
Version: 2.28.5-1
Severity: serious
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
libgtop2 FTBFS [1] with the following error:
make[4]: Entering directory `/«PKGBUILDDIR»/sysdeps/common'
/bin/bash ../../libtool --tag=CC --mode=compile gcc
Am 05.09.2013 17:29, schrieb Robert Millan:
Michael Biebl:
Source: libgtop2
Version: 2.28.5-1
Severity: serious
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
libgtop2 FTBFS [1] with the following error:
make[4]: Entering directory `/«PKGBUILDDIR»/sysdeps/common'
/bin/bash
On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote:
Am 05.09.2013 17:29, schrieb Robert Millan:
Michael Biebl:
Source: libgtop2
Version: 2.28.5-1
Severity: serious
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
libgtop2 FTBFS [1] with the following error:
Am 05.09.2013 19:53, schrieb Julien Cristau:
On Thu, Sep 5, 2013 at 19:52:13 +0200, Michael Biebl wrote:
Why do libc-dev and libbsd-dev have conflicting files in the first place
and why not move just the conflicting (BSD) files to bsd/ ?
I don't understand what you mean here, sorry...
Am 05.09.2013 19:29, schrieb Julien Cristau:
On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote:
Am 05.09.2013 17:29, schrieb Robert Millan:
-#include nlist.h
+#include bsd/nlist.h
Does that also work with FreeBSD so can be pushed upstream?
Apparently libgtop2 has native FreeBSD
Am 05.09.2013 19:42, schrieb Julien Cristau:
On Thu, Sep 5, 2013 at 19:40:18 +0200, Michael Biebl wrote:
Am 05.09.2013 19:29, schrieb Julien Cristau:
On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote:
Am 05.09.2013 17:29, schrieb Robert Millan:
-#include nlist.h
+#include
On Thu, Sep 5, 2013 at 19:52:13 +0200, Michael Biebl wrote:
Why do libc-dev and libbsd-dev have conflicting files in the first place
and why not move just the conflicting (BSD) files to bsd/ ?
I don't understand what you mean here, sorry...
Cheers,
Julien
signature.asc
Description:
Julien Cristau:
That's confusing tbh. Why is libbsd-dev using different paths in the
first place which requires such hacks?
Because the normal bsd paths would conflict with gnu libc-dev headers
(maybe not for nlist.h, but for others).
nlist.h is provided by libelf-dev and libelfg0-dev. If
Hi!
On Thu, 2013-09-05 at 19:52:13 +0200, Michael Biebl wrote:
Am 05.09.2013 19:42, schrieb Julien Cristau:
On Thu, Sep 5, 2013 at 19:40:18 +0200, Michael Biebl wrote:
Am 05.09.2013 19:29, schrieb Julien Cristau:
On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote:
Am 05.09.2013
tags 721886 + help
thanks
Am 05.09.2013 23:08, schrieb Guillem Jover:
Hi!
On Thu, 2013-09-05 at 19:52:13 +0200, Michael Biebl wrote:
Am 05.09.2013 19:42, schrieb Julien Cristau:
On Thu, Sep 5, 2013 at 19:40:18 +0200, Michael Biebl wrote:
Am 05.09.2013 19:29, schrieb Julien Cristau:
On
Am 06.09.2013 02:49, schrieb Michael Biebl:
/usr/include/sys/vnode.h:41:27: fatal error: sys/rangelock.h: No such
file or directory
#include sys/rangelock.h
FWIW, this looks like a bug in sys/vnode.h or kfreebsd-kernel-headers.
--
Why is it that all of the instruments seeking intelligent
Source: libgtop2
Version: 2.28.5-1
Severity: serious
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
libgtop2 FTBFS [1] with the following error:
make[4]: Entering directory `/«PKGBUILDDIR»/sysdeps/common'
/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../..
13 matches
Mail list logo