public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@ThinRope.net>
To: Andrew Walrond <andrew@walrond.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Iptables-1.2.9/10 compile failure with linux 2.6.7 headers
Date: Sat, 19 Jun 2004 01:56:06 +0900	[thread overview]
Message-ID: <40D31EA6.5030207@ThinRope.net> (raw)
In-Reply-To: <200406181721.47968.andrew@walrond.org>

Andrew Walrond wrote:
> Hi David,
> 
> On Friday 18 Jun 2004 17:10, David Ford wrote:
> 
>>Iptables should be using linux-libc-headers headers instead of kernel
>>headers.
> 
> 
> Is this acquired knowledge, or new Netfilter policy?
> How dependant are the iptables tools on the specifc kernel running?
> 
> Ie
> Can I build iptables for use on 2.6.7 kernel with 2.6.6 linux-libc-headers? 
> (probably)
> 
> But could I build iptables for 2.6.7 kernel with 2.4.20 linux-libc-headers? 
> (probably not?)
> 
> The INSTALL file states specifically to use 
> KERNEL_DIR=<<where-you-built-your-kernel>>
> 
> Andrew

Yes, I confirm with linux-2.6.7 and iptables-1.2.9 I got:
gcc -march=athlon-xp -m3dnow -msse -mfpmath=sse -mmmx -O3 -pipe -Iinclude -Wall -Wunused -I/usr/src/linux/include  -DIPTABLES_VERSION=\"1.2.9\"  -fPIC -o extensions/libipt_stealth_sh.o -c extensions/libipt_stealth.c
distcc[6323] ERROR: compile on localhost failed
In file included from include/libiptc/libiptc.h:6,
                 from include/iptables.h:5,
                 from extensions/libipt_stealth.c:10:
/usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:255: warning: no semicolon at end of struct or union
/usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:255: error: syntax error before '*' token
/usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:259: error: syntax error before '}' token
/usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:339: warning: type defaults to `int' in declaration of `DECLARE_MUTEX'
/usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:339: warning: parameter names (without types) in function declaration
/usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:339: warning: `DECLARE_MUTEX' declared `static' but never defined
make: *** [extensions/libipt_stealth_sh.o] Error 1

Last time I recompiled it with 2.6.6 it was ok. The compiled version still seems to work with 2.6.7 for now.

However, isn't that supposed to be filed with iptables (@netfilter.org)?

Kalin.

-- 
||///_ o  *****************************
||//'_/>     WWW: http://ThinRope.net/

  parent reply	other threads:[~2004-06-18 16:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 15:11 Iptables-1.2.9/10 compile failure with linux 2.6.7 headers Andrew Walrond
2004-06-18 16:10 ` David Ford
2004-06-18 16:21   ` Andrew Walrond
2004-06-18 16:39     ` David Ford
2004-06-18 16:56     ` Kalin KOZHUHAROV [this message]
2004-06-18 17:18       ` YOSHIFUJI Hideaki / 吉藤英明
2004-06-18 18:36         ` Kalin KOZHUHAROV
2004-06-18 22:51           ` YOSHIFUJI Hideaki / 吉藤英明
     [not found]         ` <200406191038.51118.andrew@walrond.org>
2004-06-19 16:35           ` YOSHIFUJI Hideaki / 吉藤英明
2004-06-19 18:59             ` David S. Miller
2004-06-18 17:46       ` Andrew Walrond
2004-06-18 18:35         ` Kalin KOZHUHAROV

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=40D31EA6.5030207@ThinRope.net \
    --to=kalin@thinrope.net \
    --cc=andrew@walrond.org \
    --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