From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Python3 error?
Date: Sat, 4 Jun 2016 08:56:12 +0200 [thread overview]
Message-ID: <57527B8C.1010600@mlbassoc.com> (raw)
In-Reply-To: <1464961293.13979.20.camel@linuxfoundation.org>
On 06/03/2016 03:41 PM, Richard Purdie wrote:
> On Fri, 2016-06-03 at 09:08 +0200, Gary Thomas wrote:
>> After the change over to Python3, I'm getting this error:
>>
>> ERROR: Unable to parse /local/poky-cutting-edge/meta-gnome/recipes
>> -gnome/gnome-vfs/gnome-vfs_2.24.4.bb
>> Traceback (most recent call last):
>> File "/local/poky-cutting-edge/bitbake/lib/bb/siggen.py", line
>> 151, in
>> SignatureGeneratorOEBasicHash.finalise(fn='/local/poky-cutting
>> -edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb',
>> d=<bb.data_smart.DataSmart object at 0x7f3d6ec78b38>, variant=None):
>> try:
>> > taskdeps = self._build_data(fn, d)
>> except:
>> File "/local/poky-cutting-edge/bitbake/lib/bb/siggen.py", line
>> 104, in
>> SignatureGeneratorOEBasicHash._build_data(fn='/local/poky-cutting
>> -edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb',
>> d=<bb.data_smart.DataSmart object at 0x7f3d6ec78b38>):
>>
>> > tasklist, gendeps, lookupcache =
>> bb.data.generate_dependencies(d)
>>
>> File "/local/poky-cutting-edge/bitbake/lib/bb/data.py", line 438,
>> in generate_dependencies(d=<bb.data_smart.DataSmart
>> object at 0x7f3d6ec78b38>):
>> if dep not in deps:
>> > deps[dep], values[dep] =
>> build_dependencies(dep, keys, shelldeps, varflagsexcl, d)
>> newdeps |= deps[dep]
>>
>> This is from a recipe in meta-openembedded
>>
>> Any ideas how to fix it?
>
> Also, this backtrace is unclear. Could you apply:
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/wip&id=02d40b13690ac8e9aaad203d09d5158d2f1c16c8
>
> and see if you get a better backtrace?
>
> If so I'd better get that patch cleaned up.
Per your previous message, indeed I did not have your meta-oe patches applied.
I will do that now to move forward, but I have tested this patch as requested.
The messages are a bit better, but it might not tell me what/where to look for
in the failing recipe. Here's what I see now (head only):
==============================================================================================
WARNING: /local/poky-cutting-edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb: Exception during
build_dependencies for populate_packages
WARNING: /local/poky-cutting-edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb: invalid syntax
(package.bbclass, line 1058)
WARNING: /local/poky-cutting-edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb: Error during finalise of
/local/poky-cutting-edge/meta-oe/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb
ERROR: /local/poky-cutting-edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb: invalid syntax (package.bbclass,
line 1058)
ERROR: Unable to parse /local/poky-cutting-edge/meta-oe/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb
Traceback (most recent call last):
File "/local/poky-cutting-edge/bitbake/lib/bb/siggen.py", line 151, in
SignatureGeneratorOEBasicHash.finalise(fn='/local/poky-cutting-edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb',
d=<bb.data_smart.DataSmart object at 0x7f25fa9aa3c8>, variant=None):
try:
> taskdeps = self._build_data(fn, d)
except Exception as e:
File "/local/poky-cutting-edge/bitbake/lib/bb/siggen.py", line 104, in
SignatureGeneratorOEBasicHash._build_data(fn='/local/poky-cutting-edge/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb',
d=<bb.data_smart.DataSmart object at 0x7f25fa9aa3c8>):
> tasklist, gendeps, lookupcache = bb.data.generate_dependencies(d)
File "/local/poky-cutting-edge/bitbake/lib/bb/data.py", line 439, in generate_dependencies(d=<bb.data_smart.DataSmart
object at 0x7f25fa9aa3c8>):
if dep not in deps:
> deps[dep], values[dep] = build_dependencies(dep, keys, shelldeps, varflagsexcl, d)
newdeps |= deps[dep]
File "/local/poky-cutting-edge/bitbake/lib/bb/data.py", line 368, in build_dependencies(key='populate_pack
...
==============================================================================================
One other python3 comment - my [source] layers are now filling
up with lots of cache files, e.g. .../meta/lib/oe/__pycache__/*
While this may not bother me much, it might do so with some of
my customers as they like to be able to "prove" that their build
came from exactly the same source tree as what we support, etc.
Is this something that can be controlled or even disabled?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2016-06-04 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 7:08 Python3 error? Gary Thomas
2016-06-03 13:39 ` Richard Purdie
2016-06-03 13:41 ` Richard Purdie
2016-06-04 6:56 ` Gary Thomas [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=57527B8C.1010600@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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