On Friday 2011-12-30 12:54, Pablo Neira Ayuso wrote: >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? Observed it with binutils 2.19+. >Which replies to how many people will experience problems on using >iptables since these changes are applied. Only third party packages using -liptc directly (instead of properly using pkgconfig), which are not that many. And only during compilation. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
