From: David Woodhouse <dwmw2@infradead.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: Jeff Chua <jeffchua@silk.corp.fedex.com>,
Stephen Hemminger <shemminger@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, linux-net@vger.kernel.org,
LARTC@mailman.ds9a.nl
Subject: Re: iproute2 and 2.6.9 kernel headers (was Re: [ANNOUNCE] iproute2 2.6.9-041019)
Date: Wed, 20 Oct 2004 11:41:25 +0100 [thread overview]
Message-ID: <1098268885.3872.81.camel@baythorne.infradead.org> (raw)
In-Reply-To: <20041020094123.GF19899@sunbeam.de.gnumonks.org>
On Wed, 2004-10-20 at 11:41 +0200, Harald Welte wrote:
> On Wed, Oct 20, 2004 at 09:00:17AM +0200, Harald Welte wrote:
> > I'll take care of this. sorry fort he inconvenience.
>
> I should actually read mails befor replying ;) I thought the bug was in
> lnstat - but apparently it wasn't.
>
> The include bug seems non-trivial to fix. (how do I hate kernel include
> from userspace issues):
>
> apparently __KERNEL_STRICT_NAMES is definde somewhere (glibc?) which
> prevents __le16, __le64 and others from being defined in linux/types.h.
>
> Just reietting it like this doesn't help much:
No, it wouldn't.
The time has come to fix it properly instead. Anything which these tools
actually need from the kernel headers should be moved into a separate
header file (still in the kernel source) which is usable from _both_
kernel and userspace. It should use standard types (like uint16_t etc)
instead of kernel-private types, and shouldn't have any #if{n,}def
__KERNEL__ in it. Ideally, it would be in a different directory too --
but we can worry about that later.
--
dwmw2
next prev parent reply other threads:[~2004-10-20 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 20:59 [ANNOUNCE] iproute2 2.6.9-041019 Stephen Hemminger
2004-10-20 0:21 ` Jeff Chua
2004-10-20 7:00 ` Harald Welte
2004-10-20 9:41 ` iproute2 and 2.6.9 kernel headers (was Re: [ANNOUNCE] iproute2 2.6.9-041019) Harald Welte
2004-10-20 10:41 ` David Woodhouse [this message]
2004-10-20 11:52 ` David Vrabel
2004-10-20 12:19 ` David Woodhouse
2004-10-20 16:15 ` [ANNOUNCE] iproute2 2.6.9-041019 Stephen Hemminger
2004-10-21 2:53 ` Jeff Chua
2004-10-20 16:18 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1098268885.3872.81.camel@baythorne.infradead.org \
--to=dwmw2@infradead.org \
--cc=LARTC@mailman.ds9a.nl \
--cc=jeffchua@silk.corp.fedex.com \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®