From: Christoph Paasch <christoph.paasch@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables specify path to kernel headers
Date: Tue, 21 Apr 2009 16:44:02 +0200 [thread overview]
Message-ID: <200904211644.06139.christoph.paasch@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0904211615040.26689@fbirervta.pbzchgretzou.qr>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
On Tue April 21 2009 wrote Jan Engelhardt:
> On Tuesday 2009-04-21 16:13, Christoph Paasch wrote:
> >is there a way to specify a custom path to the kernel headers when
> > compiling iptables?
>
> iptables does not rely on external kernel headers anymore.
Ups, right...
I was asking myself, how libip6t_ipv6header.c knows IPPROTO_HOPOPTS. It comes
from <netinet/in.h>. :-)
Thanks...
--
Christoph Paasch
www.rollerbulls.be
--
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-04-21 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 14:13 iptables specify path to kernel headers Christoph Paasch
2009-04-21 14:15 ` Jan Engelhardt
2009-04-21 14:44 ` Christoph Paasch [this message]
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=200904211644.06139.christoph.paasch@gmail.com \
--to=christoph.paasch@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).