Tree/branch: poky/1.2_M4 Commit: 4d9f4d6ac25f39fe6d5491d05c7a26195bab648b Image location: http://autobuilder.pokylinux.org/nightly/20120328-1/ When we compile iptables-1.4.11 with toolchain or on sdk-image. We got the following error message: ################### In file included from libxt_pkttype.c:10:0: /usr/include/linux/if_packet.h:176:2: error: unknown type name '__aligned_u64' make[2]: *** [libxt_pkttype.oo] Error 1 make[2]: Leaving directory `/opt/tests/compile_packages/compile_packages/test_iptables/iptables-1.4.11/extensions' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/tests/compile_packages/compile_packages/test_iptables/iptables-1.4.11' make: *** [all] Error 2 Making install in extensions make[1]: Entering directory `/opt/tests/compile_packages/compile_packages/test_iptables/iptables-1.4.11/extensions' CC libxt_NFLOG.oo CCLD libxt_NFLOG.so CC libxt_string.oo CCLD libxt_string.so CC libxt_length.oo CCLD libxt_length.so CC libxt_iprange.oo CCLD libxt_iprange.so CC libxt_tcpmss.oo CCLD libxt_tcpmss.so CC libxt_owner.oo CCLD libxt_owner.so CC libxt_pkttype.oo In file included from libxt_pkttype.c:10:0: /usr/include/linux/if_packet.h:176:2: error: unknown type name '__aligned_u64' make[1]: *** [libxt_pkttype.oo] Error 1 make[1]: Leaving directory `/opt/tests/compile_packages/compile_packages/test_iptables/iptables-1.4.11/extensions' make: *** [install-recursive] Error 1 ################### The iptables-1.4.12 also compile failed with the same error. But the iptables-1.4.13 could compile successfully. You can get the iptables-1.4.13 from http://www.netfilter.org/projects/iptables/downloads.html I noticed there is a related bug 2053 also report the same error in poky. Maybe we need to update the iptables version in our test case.
I'd suggest you use a recent version of iptables for this since the bug has been fixed in recent versions...
The fix that I put into master: 1c19181599c41d8f0bd7f06efc654fe61c3d0bb1 is against iptables_1.4.12.2. So as Richard indicated, bumping to that version should solve this issue.
Please use a more recent version of iptables for testing.
With the latest version of iptables project, the bug is fixed and verified. And i update the case to use the recent version of iptables. Tree/branch: poky/1.2_M4 Commit: 4d9f4d6ac25f39fe6d5491d05c7a26195bab648b