Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
	Robert Yang <liezhi.yang@windriver.com>
Subject: Re: Robert Yang : perf: fix for rebuilding
Date: Wed, 2 Sep 2015 18:00:35 +0200	[thread overview]
Message-ID: <20150902160035.GD2470@jama> (raw)

[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

I'm still seeing issues when perf is rebuilt

The original issue was:
OSError: [Errno 2] No such file or directory: 'BUILD/work/qemux86-webos-linux/perf/1.0-r9/perf-1.0'

as described here:
http://patches.openembedded.org/patch/94719/

First part of fix is now backported to dizzy:
commit 40aeb23c427e0c56f7073fc54ea63bf0eabbe092
Author: Robert Yang <liezhi.yang@windriver.com>
Date:   Wed Mar 11 01:35:38 2015 -0700

    license.bbclass: set dirs for do_populate_lic_setscene

but perf is still failing in some builds with the same error when
do_configure and do_populate_lic are executed at the same time:

NOTE: recipe perf-1.0-r9: task do_configure: Started
NOTE: recipe perf-1.0-r9: task do_populate_lic: Started
ERROR: Build of do_populate_lic failed
ERROR: Traceback (most recent call last):
  File "bitbake/lib/bb/build.py", line 497, in exec_task
    return _exec_task(fn, task, d, quieterr)
  File "bitbake/lib/bb/build.py", line 440, in _exec_task
    exec_func(func, localdata)
  File "bitbake/lib/bb/build.py", line 212, in exec_func
    exec_func_python(func, d, runfile, cwd=adir)
  File "bitbake/lib/bb/build.py", line 237, in exec_func_python
    os.chdir(cwd)
OSError: [Errno 2] No such file or directory: '....../perf/1.0-r9/perf-1.0'

NOTE: recipe perf-1.0-r9: task do_populate_lic: Failed
ERROR: Task 3826 (../oe-core/meta/recipes-kernel/perf/perf.bb, do_populate_lic) failed with exit code '1'
NOTE: recipe perf-1.0-r9: task do_configure: Succeeded

So is there some 2nd/3rd part of this fix or is it broken in master?

I haven't found any other commit related to this perf configure or
populate_lic in master and fido.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2015-09-02 16:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 16:00 Martin Jansa [this message]
2015-09-10 16:05 ` Robert Yang : perf: fix for rebuilding Martin Jansa
2015-09-15  5:29   ` [PATCH][master][fido][dizzy] Revert "perf: fix for rebuilding" Martin Jansa
2015-09-15  5:53     ` Robert Yang
2015-09-16  7:48       ` Robert Yang
2015-09-16  8:57         ` Burton, Ross
2015-09-16  9:07           ` Robert Yang
2015-09-21 19:04         ` Martin Jansa
2015-09-21 19:36           ` [RFC][PATCH] perf: don't re-create ${B} Martin Jansa
2015-09-21 20:33           ` [RFC][PATCHv2] cmake.bbclass, " Martin Jansa
2015-09-21 20:55             ` Burton, Ross
2015-09-22  5:44               ` Martin Jansa
2015-09-22  8:10             ` Richard Purdie
2015-09-22  9:36               ` Burton, Ross
2015-09-22  5:48           ` [RFC][PATCHv3] autotools.bbclass, " Martin Jansa

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=20150902160035.GD2470@jama \
    --to=martin.jansa@gmail.com \
    --cc=liezhi.yang@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