Openembedded Core Discussions
 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 09:24:53 +0000	[thread overview]
Message-ID: <1384853093.3814.56.camel@x121e.pbcl.net> (raw)
In-Reply-To: <2838381.LbivOYPPzY@yiqingliang-pc>

On Tue, 2013-11-19 at 07:21 +0800, Yi Qingliang wrote:
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'sysroot_stage_all', lineno: 6, function: <module>
>      0002:def sysroot_stage_all(d):
>      0003:    oe.path.copyhardlinktree(d.expand("/mnt/src/kl360-
> build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
> gitAUTOINC+5dbff4f559/image/usr/src/kernel"), d.expand("/mnt/src/kl360-
> build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
> gitAUTOINC+5dbff4f559/sysroot-destdir//usr/src/kernel"))

I've been seeing this too (sporadically) and Martin also reported that
it afflicts one of his jenkinses.  What seems to be happening is that,
for unknown reasons, bitbake is omitting to run do_install() on the
kernel before calling do_populate_sysroot(), despite the fact that there
clearly is a declared dependency between these two tasks.

>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.  But that's not to say it isn't related,
of course.  What makes you think that this is the problem?

p.




  reply	other threads:[~2013-11-19  8:26 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 [this message]
2013-11-19 11:35   ` Phil Blundell
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=1384853093.3814.56.camel@x121e.pbcl.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox