From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A0CF0E0044D for ; Mon, 5 Mar 2012 21:09:39 -0800 (PST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 05 Mar 2012 21:09:39 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,352,1309762800"; d="scan'208";a="114920116" Received: from unknown (HELO [10.255.15.96]) ([10.255.15.96]) by orsmga001.jf.intel.com with ESMTP; 05 Mar 2012 21:09:38 -0800 From: Tom Zanussi To: Autif Khan In-Reply-To: References: Date: Mon, 05 Mar 2012 23:09:38 -0600 Message-ID: <1331010578.2107.2.camel@elnicho> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 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 05:09:40 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Hi Autif, I'm sure it's nothing to do with crownbay or meta-intel, but I'll fire off a build anyway. I only have my laptop available, so it may take all night, but will let you know what I find. FWIW I normally build on master of both meta-intel and poky and haven't seen this, so it must be very recent. Tom On Mon, 2012-03-05 at 17:44 -0500, Autif Khan wrote: > Interesting - core image minimal builds fine - it does not actually > build iptables. So the point is moot. > > I did a clean build for core-image-sato and it failed at the same > place for the same error. > > I am no sure how meta-intel + meta-crownbay can interact with iptables > - there is no recipe for iptables in meta-intel anywhere. > > Tom - If you have the bandwidth - can you please see if you can > replicate my woes. > > I do not know anyone else who is on master and crownbay. If there - > please let me know if things work for you. > > This broke for me when I moved from M2 to master. > > Thanks > > Autif > > On Mon, Mar 5, 2012 at 4:27 PM, Autif Khan wrote: > > I love working with master: > > > > work/i586-poky-linux/polkit-0.104-r4/temp/log.do_configure says: > > > > configure: error: Could not find pam/pam-devel, please install the > > needed packages. > > > > It seems like pam/pam-dev is needed in the target environment and not > > in the host environment. > > > > Although, iptables seem to have built. I can't imagine how it will be > > affected by meta-intel and meta-crownbay - they do not do anything > > with iptables. > > > > Trying to build core-image-minimal for crownbay now. Will report when done. > > > > On Mon, Mar 5, 2012 at 4:03 PM, Autif Khan wrote: > >> I was working with M2 until recently and had to switch to master. > >> After I switched to master, I tried to bitbake core-image-sato for > >> machine crownbay. The build fails with the following error: > >> > >> unknown type name '__aligned_u64' > >> > >> The file in question is extenstions/libxt_pkttypes.c > >> > >> After a bit of investigation (thanks Khem) it seems like instead of > >> /usr/include/linux/types.h, the include/linux/types.h from iptables > >> source is being included. These a bit incompatible - specifically - > >> the definition for __aligned_u64 is not in the latter. > >> > >> I am building core-image-sato for qemux86 and will report when the > >> build reaches that point. > >> > >> Is this a known issue? > >> > >> *** This issue should be hitting anyone doing a clean build on master. > >> Or at the very least someone who builds iptables recipe*** > >> > >> I looked at the recent change (post M2) that iptables was updated to > >> 1.2.12.2 (from 1.2.12.1). There was a patch included for > >> extensions/GNUmakefile which does not build "check" target. I looked > >> at what it does and realized that someone more experienced that I am > >> should look into this. > >> > >> Thanks > >> > >> Autif