All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Another python3 error?
Date: Fri, 10 Jun 2016 10:39:11 +0200	[thread overview]
Message-ID: <575A7CAF.2050207@mlbassoc.com> (raw)
In-Reply-To: <575A7B40.9050509@mlbassoc.com>

On 2016-06-10 10:33, Gary Thomas wrote:
> BB_VERSION        = "1.31.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-15.10"
> meta              = "master:40e789d1fee7f0df2d23230fff38325119ad2935"
>
> $ bitbake my-demo-image -g -u depexp
> Traceback (most recent call last):
>    File "/local/poky-cutting-edge/bitbake/bin/bitbake", line 48, in <module>
>      cookerdata.CookerConfiguration()))
>    File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 374, in bitbake_main
>      ui_module = import_extension_module(bb.ui, configParams.ui, 'main')
>    File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 104, in import_extension_module
>      module = __import__(pkg.__name__, fromlist=[modulename])
>    File "/local/poky-cutting-edge/bitbake/lib/bb/ui/depexp.py", line 21, in <module>
>      import gobject
> ImportError: No module named 'gobject'
>
> bitbake -g by itself works fine.  Is this a [new] issue with my
> build host, or just the change over to python3?
>

Any hints on which (and why it's not being recommended by the sanity checker)?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  parent reply	other threads:[~2016-06-10  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10  8:33 Another python3 error? Gary Thomas
2016-06-10  8:36 ` Burton, Ross
2016-06-10  8:39 ` Gary Thomas [this message]
2016-06-10  8:42   ` Burton, Ross
2016-06-10 10:06     ` Gary Thomas
2016-06-10  5:54       ` Maxin B. John
2016-06-10 10:48         ` Burton, Ross
2016-06-10 10:07       ` Burton, Ross

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=575A7CAF.2050207@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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 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.