Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: kernel build fail after update
Date: Wed, 20 Nov 2013 12:32:32 +0800	[thread overview]
Message-ID: <528C3B60.1000705@windriver.com> (raw)
In-Reply-To: <2838381.LbivOYPPzY@yiqingliang-pc>

I met the same error when I inherited 'rm_work' in local.conf and 
performed a world build.

This is reproducible with the latest code.

1. add in local.conf
     INHERIT += "rm_work"
2. bitbake world

//Chen Qi


On 11/19/2013 07:21 AM, Yi Qingliang wrote:
> after update poky, I got error when compile my own kernel, it looks like there
> is no directory '/mnt/src/kl360-build/tmp/work/kl360-jilong-linux-
> gnueabi/linux-jilong/3.9.4-gitAUTOINC+5dbff4f559/image'.
>
> in my bb file, I only inherit kernel.
>
> I found one patch 'Use hardlinks for do_populate_sysroot for speed' may be
> related with this error.
>
>
>
>
>
> ERROR: Error executing a python function in /mnt/src/optimus/poky/../meta-
> jilong/recipes-kernel/linux/linux-jilong.bb:
>
> 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"))
>       0004:
>       0005:
>   *** 0006:sysroot_stage_all(d)
>       0007:
> File: 'sysroot_stage_all', lineno: 3, function: sysroot_stage_all
>       0001:
>       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"))
>       0004:
>       0005:
>       0006:sysroot_stage_all(d)
>       0007:
> File: '/mnt/src/optimus/poky/meta/lib/oe/path.py', lineno: 93, function:
> copyhardlinktree
>       0089:    bb.utils.mkdirhier(dst)
>       0090:    if os.path.isdir(src) and not len(os.listdir(src)):
>       0091:        return
>       0092:
>   *** 0093:    if (os.stat(src).st_dev ==  os.stat(dst).st_dev):
>       0094:        # Need to copy directories only with tar first since cp will
> error if two
>       0095:        # writers try and create a directory at the same time
>       0096:        cmd = 'cd %s; find . -type d -print | tar -cf - -C %s -p --
> files-from - --no-recursion | tar -xf - -C %s' % (src, src, dst)
>       0097:        check_output(cmd, shell=True, stderr=subprocess.STDOUT)
> Exception: OSError: [Errno 2] No such file or directory: '/mnt/src/kl360-
> build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
> gitAUTOINC+5dbff4f559/image/usr/src/kernel'
>
> ERROR: Function failed: sysroot_stage_all
> ERROR: Logfile of failure stored in: /mnt/src/kl360-build/tmp/work/kl360-
> jilong-linux-gnueabi/linux-jilong/3.9.4-
> gitAUTOINC+5dbff4f559/temp/log.do_populate_sysroot.5146
> ERROR: Task 3 (/mnt/src/optimus/poky/../meta-jilong/recipes-
> kernel/linux/linux-jilong.bb, do_populate_sysroot) failed with exit code '1'
>
>



      parent reply	other threads:[~2013-11-20  4:32 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
2013-11-20  0:35     ` Yi Qingliang
2013-11-20  4:32 ` ChenQi [this message]

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=528C3B60.1000705@windriver.com \
    --to=qi.chen@windriver.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