From: Chris Mason <lists@masonc.com>
To: netfilter@lists.netfilter.org
Subject: iptables-1.3.5 patch-o-matic-ng policy patch does not build
Date: Sun, 26 Feb 2006 21:12:38 -0400 [thread overview]
Message-ID: <44025206.7020805@masonc.com> (raw)
I am trying to patch iptables-1.3.5 using patch-o-matic-ng to include
the policy patch. I am building against the 2.6.12 kernel from an source
rpm. I get these errors when I build:
cc -O2 -g -pipe -m32 -march=i386 -mtune=pentium4
-I/usr/src/redhat/BUILD/iptables-1.3.5/include -fPIC -Wall -Wunused
-I/usr/include -Iinclude/ -DIPTABLES_VERSION=\"1.3.5\" -fPIC -o
extensions/libipt_policy_sh.o -c extensions/libipt_policy.c
extensions/libipt_policy.c: In function `parse_direction':
extensions/libipt_policy.c:104: error: `POLICY_MATCH_IN' undeclared
(first use in this function)
extensions/libipt_policy.c:104: error: (Each undeclared identifier is
reported only once
extensions/libipt_policy.c:104: error: for each function it appears in.)
extensions/libipt_policy.c:106: error: `POLICY_MATCH_OUT' undeclared
(first use in this function)
extensions/libipt_policy.c: In function `parse_policy':
extensions/libipt_policy.c:113: error: `POLICY_MATCH_NONE' undeclared
(first use in this function)
extensions/libipt_policy.c: In function `parse_mode':
extensions/libipt_policy.c:122: error: `POLICY_MODE_TRANSPORT'
undeclared (first use in this function)
extensions/libipt_policy.c:124: error: `POLICY_MODE_TUNNEL' undeclared
(first use in this function)
extensions/libipt_policy.c: In function `parse':
extensions/libipt_policy.c:143: error: `POLICY_MATCH_IN' undeclared
(first use in this function)
extensions/libipt_policy.c:143: error: `POLICY_MATCH_OUT' undeclared
(first use in this function)
extensions/libipt_policy.c:160: error: `POLICY_MATCH_STRICT' undeclared
(first use in this function)
extensions/libipt_policy.c:200: error: incompatible types in assignment
extensions/libipt_policy.c:201: error: incompatible types in assignment
extensions/libipt_policy.c:215: error: incompatible types in assignment
extensions/libipt_policy.c:216: error: incompatible types in assignment
extensions/libipt_policy.c:246: error: `POLICY_MAX_ELEM' undeclared
(first use in this function)
extensions/libipt_policy.c: In function `final_check':
extensions/libipt_policy.c:268: error: `POLICY_MATCH_IN' undeclared
(first use in this function)
extensions/libipt_policy.c:268: error: `POLICY_MATCH_OUT' undeclared
(first use in this function)
extensions/libipt_policy.c:272: error: `POLICY_MATCH_NONE' undeclared
(first use in this function)
extensions/libipt_policy.c:273: error: `POLICY_MATCH_STRICT' undeclared
(first use in this function)
extensions/libipt_policy.c:290: error: `POLICY_MODE_TUNNEL' undeclared
(first use in this function)
extensions/libipt_policy.c:291: error: `POLICY_MODE_TRANSPORT'
undeclared (first use in this function)
extensions/libipt_policy.c: In function `print_mode':
extensions/libipt_policy.c:303: error: `POLICY_MODE_TRANSPORT'
undeclared (first use in this function)
extensions/libipt_policy.c:306: error: `POLICY_MODE_TUNNEL' undeclared
(first use in this function)
extensions/libipt_policy.c: In function `print_flags':
extensions/libipt_policy.c:369: error: `POLICY_MATCH_IN' undeclared
(first use in this function)
extensions/libipt_policy.c:374: error: `POLICY_MATCH_NONE' undeclared
(first use in this function)
extensions/libipt_policy.c:379: error: `POLICY_MATCH_STRICT' undeclared
(first use in this function)
make: *** [extensions/libipt_policy_sh.o] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.86614 (%build)
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next reply other threads:[~2006-02-27 1:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 1:12 Chris Mason [this message]
2006-02-28 0:53 ` iptables-1.3.5 patch-o-matic-ng policy patch does not build Jorge Davila
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=44025206.7020805@masonc.com \
--to=lists@masonc.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