All of lore.kernel.org
 help / color / mirror / Atom feed
* Building iptables from source with kernel source
@ 2012-07-30 11:01 Arif Hossain
  2012-07-30 11:58 ` Jan Engelhardt
  0 siblings, 1 reply; 4+ messages in thread
From: Arif Hossain @ 2012-07-30 11:01 UTC (permalink / raw)
  To: netfilter-devel

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Building iptables from source with kernel source
  2012-07-30 11:01 Building iptables from source with kernel source Arif Hossain
@ 2012-07-30 11:58 ` Jan Engelhardt
  2012-07-30 12:11   ` Arif Hossain
  0 siblings, 1 reply; 4+ messages in thread
From: Jan Engelhardt @ 2012-07-30 11:58 UTC (permalink / raw)
  To: Arif Hossain; +Cc: netfilter-devel


On Monday 2012-07-30 13:01, Arif Hossain wrote:

>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

iptables is independent of any particular kernel tree. Copy (or
symlink) your file into <iptables>/include/linux/netfilter, that is
easiest.

>
>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.

That is too unspecified to derive any cause.
(Also note that ksource uses the source dir, not the include dir.)

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Building iptables from source with kernel source
  2012-07-30 11:58 ` Jan Engelhardt
@ 2012-07-30 12:11   ` Arif Hossain
  2012-07-30 12:32     ` Jan Engelhardt
  0 siblings, 1 reply; 4+ messages in thread
From: Arif Hossain @ 2012-07-30 12:11 UTC (permalink / raw)
  To: Jan Engelhardt; +Cc: netfilter-devel

On Mon, 2012-07-30 at 13:58 +0200, Jan Engelhardt wrote:
> On Monday 2012-07-30 13:01, Arif Hossain wrote:
> 
<snip>
> iptables is independent of any particular kernel tree. Copy (or
> symlink) your file into <iptables>/include/linux/netfilter, that is
> easiest.
> 

I've thought this easy way out actually. But i just hate the manual
copying of same file. If i update something in one, i will have to
remember to copy it before building it,because build will be ok with old
file. That may lead to undefined behavior.

Not a great fan of symlinks either.

<snip>

> That is too unspecified to derive any cause.
> (Also note that ksource uses the source dir, not the include dir.)

Error message is trivial, "can not find file <xt_mymatch.h>.


-- 
Cheers

aft
aftnix@gmail.com


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Building iptables from source with kernel source
  2012-07-30 12:11   ` Arif Hossain
@ 2012-07-30 12:32     ` Jan Engelhardt
  0 siblings, 0 replies; 4+ messages in thread
From: Jan Engelhardt @ 2012-07-30 12:32 UTC (permalink / raw)
  To: Arif Hossain; +Cc: netfilter-devel

On Monday 2012-07-30 14:11, Arif Hossain wrote:

>On Mon, 2012-07-30 at 13:58 +0200, Jan Engelhardt wrote:
>> On Monday 2012-07-30 13:01, Arif Hossain wrote:
>> 
><snip>
>> iptables is independent of any particular kernel tree. Copy (or
>> symlink) your file into <iptables>/include/linux/netfilter, that is
>> easiest.
>> 
>
>I've thought this easy way out actually. But i just hate the manual
>copying of same file. If i update something in one, i will have to
>remember to copy it before building it,because build will be ok with old
>file. That may lead to undefined behavior.
>
>Not a great fan of symlinks either.
>
><snip>
>
>> That is too unspecified to derive any cause.
>> (Also note that ksource uses the source dir, not the include dir.)
>
>Error message is trivial, "can not find file <xt_mymatch.h>.

That is because you are supposed to

  #include  <linux/netfilter/xt_mymatch.h>

provided the file is in

  $kerneldir/include/linux/netfilter/  or
  $iptablesinclude/include/linux/netfilter/

Looking at the existing extensions can help ;)


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-07-30 12:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-30 11:01 Building iptables from source with kernel source Arif Hossain
2012-07-30 11:58 ` Jan Engelhardt
2012-07-30 12:11   ` Arif Hossain
2012-07-30 12:32     ` Jan Engelhardt

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.