From: Phil Oester <kernel@linuxace.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] libiptc symbols clash
Date: Tue, 4 Jul 2006 08:27:37 -0700 [thread overview]
Message-ID: <20060704152737.GA8518@linuxace.com> (raw)
In-Reply-To: <44A95A75.4050205@trash.net>
On Mon, Jul 03, 2006 at 07:57:09PM +0200, Patrick McHardy wrote:
> Phil Oester wrote:
> > As reported by Dmitry Levin, the TC_NUM_RULES and TC_GET_RULE exports
> > clash. His patch below, resolving bug #456
>
> What does clash mean in this context? They both end up in different
> binaries, so I think I might be misunderstanding you.
They end up in libiptc.a twice:
# readelf -s libiptc.a | grep TC
56: 00000b70 81 FUNC GLOBAL DEFAULT 1 TC_GET_RULE
57: 00000bd0 56 FUNC GLOBAL DEFAULT 1 TC_NUM_RULES
57: 00000c10 81 FUNC GLOBAL DEFAULT 1 TC_GET_RULE
58: 00000c70 56 FUNC GLOBAL DEFAULT 1 TC_NUM_RULES
instead of with the standard iptc_ and ip6tc_ naming.
Phil
next prev parent reply other threads:[~2006-07-04 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 21:12 [PATCH] libiptc symbols clash Phil Oester
2006-07-03 17:57 ` Patrick McHardy
2006-07-04 15:27 ` Phil Oester [this message]
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=20060704152737.GA8518@linuxace.com \
--to=kernel@linuxace.com \
--cc=kaber@trash.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.