Created attachment 409056 [details] build.log Even with the pcap useflag unset, configure still fails, complaining about missing libpcap.
Created attachment 409058 [details] config.log
From configure script of iptables-1.4.21-r2: if test "x$enable_bpfc" = "xyes" || test "x$enable_nfsynproxy" = "xyes"; then { $as_echo "$as_me:${as_lineno-$LINENO}: checking for pcap_compile in -lpcap" >&5 $as_echo_n "checking for pcap_compile in -lpcap... " >&6; } ...................................... So libcap check depends on either bpfc or nfsynproxy. From the build.log: ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --libdir=/usr/lib64 --sbindir=/sbin --libexecdir=/lib64 --enable-devel --enable-shared --disable-bpf-compiler --disable-static --enable-ipv6 bpf-compiler is disabled, but not nfsynproxy. In iptables-1.4.21-r2.ebuild: RDEPEND=" conntrack? ( net-libs/libnetfilter_conntrack ) netlink? ( net-libs/libnfnetlink ) pcap? ( net-libs/libpcap ) " No use flag related to nfsynproxy. Either add nfsynproxy use flag to depend on libpcap, or depend on libpcap unconditionally. Temporary workaround without modify the ebuild is enabling the pcap use flag in package.use to pull in libcap
libcap->libpcap in comment 2
Duplicate of bug 557586
*** This bug has been marked as a duplicate of bug 557586 ***