From: "Colin Harrison" <colin.harrison@virgin.net>
To: <netfilter-devel@lists.netfilter.org>
Subject: Unable to build iptables on linux kernel 2.6.10 + 2.6.11-rc2 + 2.6.11-rc2-bk5
Date: Thu, 27 Jan 2005 15:53:05 -0000 [thread overview]
Message-ID: <200501271553.j0RFr747004108@StraightRunning.com> (raw)
Hi
I am experimenting with the linux kernel 2.6.10 + 2.6.11-rc2 +
2.6.11-rc2-bk5.
When I try to build CVS snapshot iptables (iptables-1.3.0-20050125) against
this kernel I get:-
make KERNEL_DIR=/home/src/kernel/linux-2.6.10
....
cc -O2 -Wall -Wunused -I/home/src/kernel/linux-2.6.10/include -Iinclude/
-DIPTABLES_VERSION=\"1.3.0-20050125\" -fPIC -o
extensions/libipt_conntrack_sh.o -c extensions/libipt_conntrack.c
In file included from extensions/libipt_conntrack.c:13:
/home/src/kernel/linux-2.6.10/include/linux/netfilter_ipv4/ip_conntrack_tupl
e.h:67: error: parse error before "u8"
/home/src/kernel/linux-2.6.10/include/linux/netfilter_ipv4/ip_conntrack_tupl
e.h:67: warning: no semicolon at end of struct or union
/home/src/kernel/linux-2.6.10/include/linux/netfilter_ipv4/ip_conntrack_tupl
e.h:67: warning: no semicolon at end of struct or union
/home/src/kernel/linux-2.6.10/include/linux/netfilter_ipv4/ip_conntrack_tupl
e.h:70: warning: type defaults to `int' in declaration of `dir'
...
The kernel appears to be patched with all the latest conntrack changes and
compiles cleanly.
More info. can be supplied, as required.
Thanks
Colin Harrison
next reply other threads:[~2005-01-27 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 15:53 Colin Harrison [this message]
2005-01-30 22:27 ` Unable to build iptables on linux kernel 2.6.10 + 2.6.11-rc2 + 2.6.11-rc2-bk5 Pablo Neira
2005-02-01 0:51 ` Thomas Graf
2005-02-01 1:31 ` Pablo Neira
2005-02-01 7:04 ` Tomáš Macek
2005-02-01 13:17 ` Patrick McHardy
2005-02-01 13:17 ` Patrick McHardy
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=200501271553.j0RFr747004108@StraightRunning.com \
--to=colin.harrison@virgin.net \
--cc=netfilter-devel@lists.netfilter.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.