From: "Greg Steuck" <greg@nest.cx>
To: linux-kernel@vger.kernel.org
Subject: Fwd: include/linux/netfilter.h after make headers_install is incomplete
Date: Tue, 20 May 2008 11:44:56 -0700 [thread overview]
Message-ID: <a27c0c970805201144j12189201g9567460d4d3d8361@mail.gmail.com> (raw)
In-Reply-To: <a27c0c970805201139i38e12d15ue807fc0239b1c10e@mail.gmail.com>
Hello,
I asked this on netfilter list, but it doesn't seem to be generating any
interest there. Maybe the question belongs on this list?
I ran make headers_install in 2.6.25 tree and the installed netfilter.h is
not complete. Namely, it declares
union nf_inet_addr {
__u32 all[4];
__be32 ip;
__be32 ip6[4];
...
}
The __u32, __be32 types are declared in <linux/types.h> and the #include
directive is removed by the installation process. This in turn makes some
applications unbuildable against such an exported tree, e.g.
busybox-1.10.1/networking/tcpudp.c:#include <linux/netfilter_ipv4.h>
If I correctly understand the purpose of make headers_install, it is
supposed to generate an API for applications. I could certainly
make tcpudp.c include linux/types.h, but given that the application
does not even use nf_inet_addr, this would be the wrong place for
the fix.
Is kernel the right place then?
Thanks
Greg
--
nest.cx is Gmail hosted, use PGP for anything private. Key:
http://tinyurl.com/ho8qg
Fingerprint: 5E2B 2D0E 1E03 2046 BEC3 4D50 0B15 42BD 8DF5 A1B0
next parent reply other threads:[~2008-05-20 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a27c0c970805161521k332fba8cg808d52396b5cdce5@mail.gmail.com>
[not found] ` <a27c0c970805201139i38e12d15ue807fc0239b1c10e@mail.gmail.com>
2008-05-20 18:44 ` Greg Steuck [this message]
2008-05-20 21:21 ` David Miller
2008-05-21 9:56 ` Patrick McHardy
2008-05-21 10:04 ` Sam Ravnborg
2008-05-21 10:31 ` Patrick McHardy
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=a27c0c970805201144j12189201g9567460d4d3d8361@mail.gmail.com \
--to=greg@nest.cx \
--cc=linux-kernel@vger.kernel.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®