myserver ~ # USE="l7filter extensions" emerge -v iptables Calculating dependencies... done! >>> Emerging (1 of 1) net-firewall/iptables-1.3.7 to / * iptables-1.3.7.tar.bz2 MD5 ;-) ... [ ok ] * iptables-1.3.7.tar.bz2 RMD160 ;-) ... [ ok ] * iptables-1.3.7.tar.bz2 SHA1 ;-) ... [ ok ] * iptables-1.3.7.tar.bz2 SHA256 ;-) ... [ ok ] * iptables-1.3.7.tar.bz2 size ;-) ... [ ok ] * netfilter-layer7-v2.8.tar.gz MD5 ;-) ... [ ok ] * netfilter-layer7-v2.8.tar.gz RMD160 ;-) ... [ ok ] * netfilter-layer7-v2.8.tar.gz SHA1 ;-) ... [ ok ] * netfilter-layer7-v2.8.tar.gz SHA256 ;-) ... [ ok ] * netfilter-layer7-v2.8.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking iptables-1.3.7.tar.bz2 ;-) ... [ ok ] * checking netfilter-layer7-v2.8.tar.gz ;-) ... [ ok ] * WARNING: 3rd party extensions has been enabled. * This means that iptables will use your currently installed * kernel in /usr/src/linux as headers for iptables. * * You may have to patch your kernel to allow iptables to build. * Please check http://ftp.netfilter.org/pub/patch-o-matic-ng/snapshot/ for patches * for your kernel. * * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.19-server-r4/build * Found sources for kernel version: * 2.6.19-server-r4 !!! ERROR: net-firewall/iptables-1.3.7 failed. Call stack: ebuild.sh, line 1627: Called dyn_setup ebuild.sh, line 702: Called qa_call 'pkg_setup' ebuild.sh, line 38: Called pkg_setup iptables-1.3.7.ebuild, line 45: Called die !!! For layer 7 support emerge net-misc/l7-filter-2.8 before this !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/net-firewall/iptables-1.3.7/temp/build.log'. Reproducible: Always
> !!! For layer 7 support emerge net-misc/l7-filter-2.8 before this Did you even read the message before filing a bug?
It haven't other error information..
(In reply to comment #2) > It haven't other error information.. This bug is INVALID. Read the message and do what it tells you to do...