Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
unmask iptables 1.3.7, since prior versions do not compile against 2.6.19.5 kernel extensions headers (l7-filter)
It's not masked at all...
It does not compile using extensions useflag.
Sigh; post some errors, emerge --info and reopen. There's no linux-header-2.6.19.5 either.
Steps to reproduce: 1. configure kernel with all netfilter options 2. build iptables with USE="extensions" In file included from extensions/libipt_iprange.c:9: /usr/src/linux/include/linux/netfilter_ipv4/ipt_iprange.h:11: error: expected specifier-qualifier-list before ‘__be32’ extensions/libipt_iprange.c: In function ‘parse_iprange’: extensions/libipt_iprange.c:43: error: ‘struct ipt_iprange’ has no member named ‘min_ip’ extensions/libipt_iprange.c:50: error: ‘struct ipt_iprange’ has no member named ‘max_ip’ extensions/libipt_iprange.c:52: error: ‘struct ipt_iprange’ has no member named ‘max_ip’ extensions/libipt_iprange.c:52: error: ‘struct ipt_iprange’ has no member named ‘min_ip’ extensions/libipt_iprange.c: In function ‘print_iprange’: extensions/libipt_iprange.c:116: error: ‘const struct ipt_iprange’ has no member named ‘min_ip’ extensions/libipt_iprange.c:117: error: ‘const struct ipt_iprange’ has no member named ‘max_ip’ make: *** [extensions/libipt_iprange_sh.o] Error 1 !!! ERROR: net-firewall/iptables-1.3.6-r1 failed. Call stack: ebuild.sh, line 1614: Called dyn_compile ebuild.sh, line 971: Called qa_call 'src_compile' environment, line 3936: Called src_compile iptables-1.3.6-r1.ebuild, line 131: Called die !!! failure - with l7filter or imq patch added See upstream: http://www.netfilter.org/news.html#2006-12-04 iptables 1.3.7 was released extra for 2.6.19.x kernels for compatibility issues. It is ridiculous to mark gentoo-sources 2.6.19.x as stable but stick with iptables 1.3.5 in the stable tree. It is time to mark 1.3.7 as stable, please.
*** This bug has been marked as a duplicate of bug 156723 ***