Iptables-1.2.9/10 compile failure with linux 2.6.7 headers

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

On Friday 18 Jun 2004 17:56, Kalin KOZHUHAROV wrote:

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

My original mail was addressed to , and cc'ed to
lkml

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/