On 8 Jun 2001, Linus Torvalds wrote:
> The basic issue is that the kernel will _refuse_ to follow the
> "namespace of the day" rules of C89, C99, POSIX, BSD, SuS, GNU .. the
> list goes on. The kernel headers are not meant to be used in user space,
> and will not have the strict namespace rules
In article <[EMAIL PROTECTED]>,
Felix von Leitner <[EMAIL PROTECTED]> wrote:
>Thus spake David S. Miller ([EMAIL PROTECTED]):
>> > glibc works around this, but the diet libc uses the kernel headers and
>> > thus exports the wrong API to user land.
>> Don't user kernel headers for userspace.
>
glibc works around this, but the diet libc uses the kernel headers and
thus exports the wrong API to user land.
Here is what RFC2553 mandates:
struct ipv6_mreq {
struct in6_addr ipv6mr_multiaddr; /* IPv6 multicast addr */
unsigned intipv6mr_interface; /* interface index */
glibc works around this, but the diet libc uses the kernel headers and
thus exports the wrong API to user land.
Here is what RFC2553 mandates:
struct ipv6_mreq {
struct in6_addr ipv6mr_multiaddr; /* IPv6 multicast addr */
unsigned intipv6mr_interface; /* interface index */
In article [EMAIL PROTECTED],
Felix von Leitner [EMAIL PROTECTED] wrote:
Thus spake David S. Miller ([EMAIL PROTECTED]):
glibc works around this, but the diet libc uses the kernel headers and
thus exports the wrong API to user land.
Don't user kernel headers for userspace.
What choice do
On 8 Jun 2001, Linus Torvalds wrote:
The basic issue is that the kernel will _refuse_ to follow the
namespace of the day rules of C89, C99, POSIX, BSD, SuS, GNU .. the
list goes on. The kernel headers are not meant to be used in user space,
and will not have the strict namespace rules that a
6 matches
Mail list logo
