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
------------------------------------------------------------
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to