[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#677260: xserver-xorg-video-openchrome: FTBFS[kfreebsd]: error: unknown type name 'uint8_t'

2012/6/13 Julien Cristau <jcristau@debian.org>:
>> I'm not sure what you mean here.  You want <sys/types.h> to define
>> uintXX_t?  Then you need to request this to Glibc maintainers.
> Yes, I'd like kfreebsd sys/types.h to look like freebsd sys/types.h.

It seems you're regarding <sys/types.h> as a kernel-related header,
but this is not at all accurate.  Let me try to clarify things.

On FreeBSD, <sys/types.h> is a kernel header.  On GNU systems, it is
part of the C library.  Specifically in Debian, it is provided by
eglibc package.  Unlike many of the glibc headers from <bits/*>
hierarchy, <sys/types.h> is not kernel-specific at all.  It's the same
header for all glibc systems, regardless of their kernel.

As for kernel side of things, kFreeBSD provides its own set of
headers, which in Debian they're packaged as kfreebsd-kernel-headers.
<sys/types.h> is not among them.

In summary: none of this has anything to do with the kernel, it's a
pure userland issue.  The problem is simply that libdrm-dev attempts
to use uintXX_t without including the header that provides them.

>> Or perhaps you want to emulate a FreeBSD-like build environment,
>> regardless of GNU <sys/types.h> behaviour?  There's a package
>> specifically for this purpose: freebsd-glue.
> How is one supposed to use that?  By passing -I/usr/include/freebsd to
> gcc?

Yes.  I fail to see how's that better than fixing a one-line bug [1].
That burden is not mine to carry though.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677260#25

Robert Millan

Reply to: