From: Arif Hossain <aftnix@gmail.com>
To: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Building iptables from source with kernel source
Date: Mon, 30 Jul 2012 17:01:22 +0600 [thread overview]
Message-ID: <1343646082.3347.7.camel@localhost> (raw)
Hi,
I'm trying to build iptables from git tree.
The extension i've written resides in extensions/libxt_mymatch.c
Now the header is in
<kernel_source>/include/linux/netfilter/xt_mymatch.h
But when i'm trying to build iptables, its not finding xt_mymatch.h.
I've tried these configure options
$./configure --with-ksource=<kernel_source_path>
and
$./configure --with-ksource=<kernel_source_path>/include
But both failed.
On the side not I want to prevent the build process to look up for
declarations in "kernel-devel" that is /usr/src/linux. I want the build
to be dependent only to the kernel_source i'm supplying. (Its because
i'm using a modified kernel source, so i don't want to take any
declaration from distribution's kernel package.
--
Cheers
aft
aftnix@gmail.com
next reply other threads:[~2012-07-30 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 11:01 Arif Hossain [this message]
2012-07-30 11:58 ` Building iptables from source with kernel source Jan Engelhardt
2012-07-30 12:11 ` Arif Hossain
2012-07-30 12:32 ` Jan Engelhardt
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=1343646082.3347.7.camel@localhost \
--to=aftnix@gmail.com \
--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 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.