From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/3] libiptc: remove libiptc.so
Date: Fri, 30 Dec 2011 12:54:44 +0100 [thread overview]
Message-ID: <20111230115444.GB12204@1984> (raw)
In-Reply-To: <1325209595-23244-2-git-send-email-jengelh@medozas.de>
On Fri, Dec 30, 2011 at 02:46:32AM +0100, Jan Engelhardt wrote:
> When Linux distributions started to ship binutils-ld defaulting to
> -Wl,--as-needed, we had to add a hack (-Wl,--no-as-needed) to the
> iptables build such that libiptc.so continued to link to libip4tc.so
> and libip6tc.so despite not requesting any symbols from there.
>
> Given that distros start shipping binutils-ld defaulting to
> -Wl,--no-copy-dt-needed-entries, 3rd-party programs linking
> to -liptc will ignore libiptc.so's DT_NEEDED entries by default and
> not search for symbols there. So libiptc.so has finally become
> useless, so remove it. Dependent programs should have been using the
> pkg-config infrastructure, where quering for "iptc" returned "-lip4tc
> -lip6tc" for long enough.
My only concern here, as usual, is if people with old distros (I know
a handful of them that use it in productive environments as firewalls,
with very basic package set, that only update necessary things
like iptables and the Linux kernel) may experience problems.
So, my question is since how long do distros include this mechanism?
Which replies to how many people will experience problems on using
iptables since these changes are applied.
next prev parent reply other threads:[~2011-12-30 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 1:46 iptables: response to modern linkers, and symbol maps Jan Engelhardt
2011-12-30 1:46 ` [PATCH 1/3] libiptc: remove libiptc.so Jan Engelhardt
2011-12-30 11:54 ` Pablo Neira Ayuso [this message]
2011-12-31 20:14 ` Jan Engelhardt
2011-12-30 1:46 ` [PATCH 2/3] libiptc: add symbol maps to libiptc Jan Engelhardt
2011-12-30 11:48 ` Pablo Neira Ayuso
2011-12-30 13:49 ` Jan Engelhardt
2011-12-31 16:36 ` Pablo Neira Ayuso
2011-12-30 1:46 ` [PATCH 3/3] libipq: add symbol map to libipq Jan Engelhardt
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=20111230115444.GB12204@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).