All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Yi Qingliang <niqingliang2003@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: kernel build fail after update
Date: Tue, 19 Nov 2013 11:35:14 +0000	[thread overview]
Message-ID: <1384860914.23724.83.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1384853093.3814.56.camel@x121e.pbcl.net>

On Tue, 2013-11-19 at 09:24 +0000, Phil Blundell wrote:
> On Tue, 2013-11-19 at 07:21 +0800, Yi Qingliang wrote:
> >I found one patch 'Use hardlinks for do_populate_sysroot for speed' 
> >may be related with this error.
> 
> The failure only seems to occur with the kernel, whereas I think that
> patch applies to all recipes. 

I realise now that this isn't true; assuming you meant
13259459e200a237ca486cbe1123a0b0a4d1eebf then this is indeed specific to
kernel.bbclass.

p.




  reply	other threads:[~2013-11-19 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 23:21 kernel build fail after update Yi Qingliang
2013-11-19  9:24 ` Phil Blundell
2013-11-19 11:35   ` Phil Blundell [this message]
2013-11-20  0:35     ` Yi Qingliang
2013-11-20  4:32 ` ChenQi

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=1384860914.23724.83.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=niqingliang2003@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.