From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: KeyError in siggen.py
Date: Fri, 24 Feb 2012 23:15:19 +0000 [thread overview]
Message-ID: <1330125319.9617.14.camel@ted> (raw)
In-Reply-To: <20120224211914.GN3769@jama.jama.net>
On Fri, 2012-02-24 at 22:19 +0100, Martin Jansa wrote:
> Any idea what could cause this?
>
> OE qemux86-64@ ~/oe-core $ bitbake -c configure -b /OE/oe-core/openembedded-core/meta/recipes-devtools/gcc/gcc-cross-initial_4.6.bb -f
> WARNING: Buildfile specified, dependencies will not be handled. If this is not what you want, do not use -b / --buildfile.
> ERROR: Command execution failed: Traceback (most recent call last):
> File "/usr/lib64/python2.7/site-packages/bb/command.py", line 87, in runAsyncCommand
> commandmethod(self.cmds_async, self, options)
> File "/usr/lib64/python2.7/site-packages/bb/command.py", line 203, in buildFile
> command.cooker.buildFile(bfile, task)
> File "/usr/lib64/python2.7/site-packages/bb/cooker.py", line 1076, in buildFile
> bb.build.del_stamp('do_%s' % task, self.status, fn)
> File "/usr/lib64/python2.7/site-packages/bb/build.py", line 441, in del_stamp
> stamp = stamp_internal(task, d, file_name)
> File "/usr/lib64/python2.7/site-packages/bb/build.py", line 411, in stamp_internal
> stamp = bb.parse.siggen.stampfile(stamp, file_name, taskname, extrainfo)
> File "/usr/lib64/python2.7/site-packages/bb/siggen.py", line 222, in stampfile
> h = self.taskhash[k]
> KeyError: '/OE/oe-core/openembedded-core/meta/recipes-devtools/gcc/gcc-cross-initial_4.6.bb.do_configure'
The -f triggers a del_stamp so I'm looking at that with suspicion...
No fix but I suspect its where we need to look. I can reproduce with -b
and -f combined.
Cheers,
Richard
prev parent reply other threads:[~2012-02-24 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 21:19 KeyError in siggen.py Martin Jansa
2012-02-24 23:15 ` Richard Purdie [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=1330125319.9617.14.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=martin.jansa@gmail.com \
/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.