From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org,
Patrick McHardy <kaber@trash.net>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: Fix --with-kernel for libnfnetlink
Date: Fri, 21 Apr 2006 15:12:10 +0200 [thread overview]
Message-ID: <20060421131210.GA10173@localhost.localdomain> (raw)
In-Reply-To: <4448D4A9.1080809@ufomechanic.net>
On Fri, Apr 21, 2006 at 01:48:41PM +0100, Amin Azez wrote:
> Pablo Neira Ayuso wrote:
>
> >Why do you need this parameter? the netfilter libraries don't require
> >kernel headers anymore since they are already bundled in the package
> >provided. For example, see include/libnfnetlink/linux_nfnetlink.h. We
> >have had several problems with iptables and the kernel headers in the
> >past: compilation warnings, breakages... That is the reason why we
> >decided to do so.
> >
> >On the other hand, autogen.sh automates the copy of these headers,
> >so you could choose them via KERNEL_DIR but you need some important
> >reason to do that.
>
> I needed it because (at the time) I was working on netfilter and
> changing it. I was building multiple kernels with different modifications.
>
> It's possibly only useful for developers (but this is netfilter-devel).
Still, why such thing would be useful?
I just noticed that this thread started from "Problem with compiling
libnfnetlink". Could you check that you have /usr/include/asm/types.h
installed? it seems that your system doesn't find the definition of
__u32.
It's true that this is defined in a kernel header but such file is usually
provided by the linux-kernel-header package, that is the case of debian.
I think that is a reasonable requirement to compile libnfnetlink.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2006-04-21 13:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 15:25 Fix --with-kernel for libnfnetlink David Vogt
2006-04-20 16:33 ` Amin Azez
2006-04-20 16:50 ` Sven-Haegar Koch
2006-04-20 18:51 ` Patrick McHardy
2006-04-20 18:53 ` Patrick McHardy
2006-04-20 19:38 ` KOVACS Krisztian
2006-04-20 22:52 ` Patrick McHardy
2006-04-21 15:25 ` Pablo Neira Ayuso
2006-04-21 20:02 ` Harald Welte
2006-04-20 19:34 ` Patrick McHardy
2006-04-21 7:21 ` David Vogt
2006-04-21 11:09 ` Pablo Neira Ayuso
2006-04-21 12:48 ` Amin Azez
2006-04-21 13:12 ` Pablo Neira Ayuso [this message]
2006-04-21 13:56 ` Amin Azez
2006-07-26 14:06 ` Amin Azez
2006-07-26 14:11 ` quick fix " Amin Azez
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=20060421131210.GA10173@localhost.localdomain \
--to=pablo@netfilter.org \
--cc=azez@ufomechanic.net \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.