Bug 2607

Summary: cannot compile iptables-1.4.11.tar.bz2
Product: [Build System, Metadata & Runtime] BSPs Reporter: Alexandru Georgescu <alexandru.c.georgescu>
Component: bsps-configurationAssignee: Saul Wold <sgw>
Status: VERIFIED NOTABUG QA Contact:
Severity: normal    
Priority: Medium CC: jiajun.xu, laurentiu.serban, sgw, yp.bsp.watcher, yp.watcher
Version: 1.3   
Target Milestone: 1.3 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Alexandru Georgescu 2012-06-14 15:05:19 UTC
iptables-1.4.11.tar.bz2 fails to compile on the following image: core-image-sato-sdk-sugarbay-20120613171206.hddimg   

The output here:

root@sugarbay:~/iptables2/iptables-1.4.11# make
make  all-recursive
make[1]: Entering directory `/home/root/iptables2/iptables-1.4.11'
Making all in extensions
make[2]: Entering directory `/home/root/iptables2/iptables-1.4.11/extensions'
  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[2]: *** [libxt_pkttype.oo] Error 1
make[2]: Leaving directory `/home/root/iptables2/iptables-1.4.11/extensions'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/root/iptables2/iptables-1.4.11'
make: *** [all] Error 2
root@sugarbay:~/iptables2/iptables-1.4.11# 



Iptables tarball downloaded from: http://netfilter.org/projects/iptables/files/iptables-1.4.11.tar.bz2
Comment 1 Bruce Ashfield 2012-06-14 15:09:11 UTC
why isn't this using 1.4.13 ? this bug is fixed there, if you use another
version, you'd need to port the 1.4.13 fix.
Comment 2 Jiajun Xu 2012-06-17 14:10:20 UTC
(In reply to comment #1)
> why isn't this using 1.4.13 ? this bug is fixed there, if you use another
> version, you'd need to port the 1.4.13 fix.

Yes, we should use 1.4.13. Sorry, Alex, we used to find the issue and update the test cases for ADT, but not for the compiling testing for real target. I will update the test plan.
Comment 3 Saul Wold 2012-06-21 16:45:04 UTC
Is this a bug that we need to worry about or was this just a bad test case?
Comment 4 Jiajun Xu 2012-06-22 08:28:29 UTC
(In reply to comment #3)
> Is this a bug that we need to worry about or was this just a bad test case?

Mark the bug as NOTABUG. We should update the test case to use 1.4.13.
Comment 5 Laurentiu Serban 2012-07-11 11:36:50 UTC
verified