From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Diaz de Grenu, Jose" <Jose.DiazdeGrenu@digi.com>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Trying to use python3-pygobject-native to compile NetworkManager
Date: Tue, 2 Jan 2018 15:06:55 +0200 [thread overview]
Message-ID: <e33e41cc-fe8d-36e7-4204-0e690b9aa16c@linux.intel.com> (raw)
In-Reply-To: <0B2EBCD48D33654381E736352034C70C01B40158@dor-sms-xch01.digi.com>
On 01/02/2018 02:55 PM, Diaz de Grenu, Jose wrote:
> -----Original Message-----
> From: Alexander Kanavin [mailto:alexander.kanavin@linux.intel.com]
>
>> Also, where is the networkmanager recipe from? meta-oe has its own recipe for it, and it does not match what you posted to pastebin.
>
> It is a custom recipe, as I need to use a newer version of NetworkManager. This recipe was working fine on Yocto 2.2, and I suspect that the problem may be in the python3 package, not in the recipe itself.
I think that's correct - the older version from meta-oe does not have a
hard failure if pygobject isn't working. I can't help you with the error
itself that python is printing; you need to dig into the point in the
code where it happens and take it from there.
Generally, calling host python to establish (via module import) if
pygobject is available for the target is incorrect, you can simply patch
configure.ac to remove the check. That wouldn't however fix the
underlying problem (that of host pygobject being broken).
Alex
next prev parent reply other threads:[~2018-01-02 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 11:59 Trying to use python3-pygobject-native to compile NetworkManager Diaz de Grenu, Jose
2018-01-02 12:12 ` Alexander Kanavin
2018-01-02 12:26 ` Diaz de Grenu, Jose
2018-01-02 12:30 ` Alexander Kanavin
2018-01-02 12:55 ` Diaz de Grenu, Jose
2018-01-02 13:06 ` Alexander Kanavin [this message]
2018-01-02 13:34 ` Alexander Kanavin
2018-01-02 17:36 ` Diaz de Grenu, Jose
2018-01-03 9:53 ` Alexander Kanavin
2018-01-05 19:46 ` Tim Orling
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=e33e41cc-fe8d-36e7-4204-0e690b9aa16c@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=Jose.DiazdeGrenu@digi.com \
--cc=poky@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.