From: Phil Oester <kernel@linuxace.com>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH] libiptc symbols clash
Date: Fri, 30 Jun 2006 14:12:48 -0700 [thread overview]
Message-ID: <20060630211248.GB9243@linuxace.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
As reported by Dmitry Levin, the TC_NUM_RULES and TC_GET_RULE exports
clash. His patch below, resolving bug #456
Phil
[-- Attachment #2: patch-libiptc-rules --]
[-- Type: text/plain, Size: 902 bytes --]
diff -ru ipt-orig/libiptc/libip4tc.c ipt-new/libiptc/libip4tc.c
--- ipt-orig/libiptc/libip4tc.c 2005-06-23 01:51:18.000000000 -0700
+++ ipt-new/libiptc/libip4tc.c 2006-06-30 14:05:11.000000000 -0700
@@ -94,6 +94,8 @@
#define TC_FREE iptc_free
#define TC_COMMIT iptc_commit
#define TC_STRERROR iptc_strerror
+#define TC_NUM_RULES iptc_num_rules
+#define TC_GET_RULE iptc_get_rule
#define TC_AF AF_INET
#define TC_IPPROTO IPPROTO_IP
diff -ru ipt-orig/libiptc/libip6tc.c ipt-new/libiptc/libip6tc.c
--- ipt-orig/libiptc/libip6tc.c 2005-06-23 01:51:18.000000000 -0700
+++ ipt-new/libiptc/libip6tc.c 2006-06-30 14:05:30.000000000 -0700
@@ -89,6 +89,8 @@
#define TC_FREE ip6tc_free
#define TC_COMMIT ip6tc_commit
#define TC_STRERROR ip6tc_strerror
+#define TC_NUM_RULES ip6tc_num_rules
+#define TC_GET_RULE ip6tc_get_rule
#define TC_AF AF_INET6
#define TC_IPPROTO IPPROTO_IPV6
next reply other threads:[~2006-06-30 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 21:12 Phil Oester [this message]
2006-07-03 17:57 ` [PATCH] libiptc symbols clash Patrick McHardy
2006-07-04 15:27 ` Phil Oester
2006-07-05 9:06 ` 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=20060630211248.GB9243@linuxace.com \
--to=kernel@linuxace.com \
--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.