All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Autif Khan <autif.mlist@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: iptables not building on master
Date: Mon, 05 Mar 2012 23:09:38 -0600	[thread overview]
Message-ID: <1331010578.2107.2.camel@elnicho> (raw)
In-Reply-To: <CADzUK1JCDWysYpL=7JZARZ=Lmgh+4izk5k-3nwX-nnODTHmQqA@mail.gmail.com>

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 <autif.mlist@gmail.com> 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 <autif.mlist@gmail.com> 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




  reply	other threads:[~2012-03-06  5:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 21:03 iptables not building on master Autif Khan
2012-03-05 21:27 ` Autif Khan
2012-03-05 22:44   ` Autif Khan
2012-03-06  5:09     ` Tom Zanussi [this message]
2012-03-06  5:35       ` Cui, Dexuan
2012-03-06  5:59         ` Robert Yang
2012-03-06  6:48           ` Tom Zanussi
2012-03-06  9:04             ` Robert Yang
2012-03-06  9:47               ` Cui, Dexuan
2012-03-06 10:05                 ` Robert Yang
2012-03-06 11:41                 ` Robert Yang
2012-03-06 14:21                   ` Bruce Ashfield
2012-03-06 15:16               ` Khem Raj
2012-03-06 15:21                 ` Robert Yang
2012-03-06 15:24                   ` Khem Raj
2012-03-06 15:27                     ` Bruce Ashfield
2012-03-06 17:28                       ` Khem Raj
2012-03-06 17:32                         ` Bruce Ashfield
2012-03-06 12:14             ` Koen Kooi
2012-03-06 16:44               ` Tom Zanussi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1331010578.2107.2.camel@elnicho \
    --to=tom.zanussi@intel.com \
    --cc=autif.mlist@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.