Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: Incomplete runtime dependencies for gdb python PACKAGECONFIG
Date: Sat, 20 Jun 2015 17:11:09 +0200	[thread overview]
Message-ID: <5585828D.90002@opendreambox.org> (raw)
In-Reply-To: <CAJ86T=W1YVmDnA6PfkUDRaGsftRt8+1MhWcN2U-DFUAjzoct5g@mail.gmail.com>

Hello Andre,

On 20.06.2015 05:00, Andre McCurdy wrote:
> The runtime dependencies for gdb seem to be incomplete when python
> support is enabled via gdb's PACKAGECONFIG.
> 
> gdb ends up with a runtime dependency on libpython, but not on python
> or any python modules, and gdb then fails to run:
> 
>   root@7401:~# gdb

just curious, is this a BCM7401?

>   Could not find platform independent libraries <prefix>
>   Could not find platform dependent libraries <exec_prefix>
>   Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
>   ImportError: No module named site
> 
> Manually installing python and all python modules seems to be a fix,
> but I haven't narrowed down which specific python modules are
> required.
> 
> The issue is a little more serious for anyone using meta-qt5, since
> meta-qt5 (fido and later) contains a .bbappend for gdb which enables
> the python PACKAGECONFIG by default:
> 
>   https://github.com/meta-qt5/meta-qt5/commit/9d17546d56b5e710a6420b482514202236f410e3
> 

Here's a patch for fido that I was going to submit after testing
with master, whenever that may be.

http://git.openembedded.org/openembedded-core-contrib/commit/?h=obi/fido&id=5461b4a6db9b9429132952ce31d293550c945179

Feel free to adapt, test and submit.

Regards,
Andreas


  reply	other threads:[~2015-06-20 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20  3:00 Incomplete runtime dependencies for gdb python PACKAGECONFIG Andre McCurdy
2015-06-20 15:11 ` Andreas Oberritter [this message]
2015-06-23  5:01   ` Andre McCurdy

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=5585828D.90002@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=openembedded-core@lists.openembedded.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