From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B07EFE004D2 for ; Tue, 6 Mar 2012 07:21:46 -0800 (PST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail1.windriver.com (8.14.3/8.14.3) with ESMTP id q26FLYSO013165 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Mar 2012 07:21:35 -0800 (PST) Received: from [128.224.162.196] (128.224.162.196) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 6 Mar 2012 07:21:34 -0800 Message-ID: <4F562B7C.4020105@windriver.com> Date: Tue, 6 Mar 2012 23:21:32 +0800 From: Robert Yang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111229 Thunderbird/9.0 MIME-Version: 1.0 To: Khem Raj References: <1331010578.2107.2.camel@elnicho> <4F55A7D7.8020100@windriver.com> <1331016505.2107.37.camel@elnicho> <4F55D32F.6050705@windriver.com> <4F562A34.2020304@gmail.com> In-Reply-To: <4F562A34.2020304@gmail.com> Cc: yocto@yoctoproject.org Subject: Re: iptables not building on master X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 15:21:46 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 03/06/2012 11:16 PM, Khem Raj wrote: > On 03/06/2012 01:04 AM, Robert Yang wrote: >> >> Hi Tom, >> >> Thanks for the update, the root cause is that iptables offers >> a kernel header file include/linux/types.h, but it mis-matches >> the kernel in the sysroot, we can add this: >> >> #define __aligned_u64 __u64 __attribute__((aligned(8))) >> >> to: >> >> iptables-1.4.12.2/include/linux/types.h >> >> to fix this problem. > > find out why iptables has its own copy of linux/types.h that file should be > deleted if there is no reason to have it. > Here is the reply from Bruce: iptables has always done this .. and it has periodically caused issues like this in the past. Typically something like you have above is done, or iptables is updated to a newer version (I assume we can't do that in this case?), to fix any build issues. I've had iptables in a directory/location with a dependency on a particular kernel version (to show the coupling) in the past to enforce a check before the build breaks. // Robert >> >> Another solution is that as Dexuan suggested we change the order of >> the include header files, but I'm afraid that may cause other problems, >> since I think that the pkg's own header file should have a higher priority >> than the system's, so I think that the current order is correct. >> >> I will send a pull request after enough testing. > >> https://lists.yoctoproject.org/listinfo/yocto > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >