From: Anders Fugmann <afu@fugmann.dhs.org>
To: Dian Brits <dian.brits@epiuse.com>
Cc: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: Re: Compile problems with iptables 1.2.7
Date: Tue, 01 Oct 2002 20:13:03 +0200 [thread overview]
Message-ID: <3D99E5AF.8020805@fugmann.dhs.org> (raw)
In-Reply-To: B0A500E93795D311AD4300A0C9A98F4801610ABD@lara.epiuse.co.za
Dian Brits wrote:
> ok i've tried using 1.2.7a but i still get this:
>
> kagisofw:/usr/local/iptables/src/iptables-1.2.7a $ /kernel/src/linux
> <
> Extensions found:
> cc -O2 -Wall -Wunused -I/usr/local/kernel/src/linux/include -Iinclude/
> -DIPTABLES_VERSION=\"1.2.7a\" -fPIC -o extensions/libipt_conntrack_sh.o -c
> extensions/libipt_conntrack.c
> In file included from extensions/libipt_conntrack.c:14:
>/usr/local/kernel/src/linux/include/linux/netfilter_ipv4/ipt_conntrack.h:28:
> `IP_CT_DIR_MAX' undeclared here (not in a function)
I guess the kernel source is located at '/usr/local/kernel/src/linux/'.
What version is it? (the kernel source), and what patches have you
applied from pom?
There should be an enum at the top of
'/usr/local/kernel/src/linux/include/linux/netfilter_ipv4/ipt_conntrack.h',
defining the constant `IP_CT_DIR_MAX'. Either its not there, or the
compiler does not like that one. What compiler are you using?
Also try reproduce with a vanilla 2.4.19 kernel source.
Regards
Anders Fugmann
--
Neo: 'Can you fly that thing?'
Trinity: 'Not yet'.
$ apt-get install pilot-prg-v212helicopter.
next prev parent reply other threads:[~2002-10-01 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 16:28 Compile problems with iptables 1.2.7 Dian Brits
2002-10-01 18:13 ` Anders Fugmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 14:28 Dian Brits
2002-10-01 15:37 ` Anders Fugmann
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=3D99E5AF.8020805@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=dian.brits@epiuse.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox