From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/kodi: needs .py modules
Date: Sun, 13 Sep 2015 23:29:42 +0200 [thread overview]
Message-ID: <20150913232942.736dea75@free-electrons.com> (raw)
In-Reply-To: <1442178783-27567-1-git-send-email-yann.morin.1998@free.fr>
Yann,
On Sun, 13 Sep 2015 23:13:03 +0200, Yann E. MORIN wrote:
> Kodi segfaults as soon as it tries to load a python module:
>
> Could not find platform independent libraries <prefix>
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> ImportError: No module named site
> Segmentation fault
>
> Turns out that keeping .py modules (with or without .pyc) fixes the
> issue.
>
> Currently, Kodi selects python, but since the format of modules is a
> choice, we can not select it.
>
> Fix that by inverting the dependency on python from Kodi:
> - turn it into a depends rather than a select,
> - add the dependency to ! pyc-only
> - update the comment accordingly.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Do we actually understand why it doesn't work? There is really no
reason for .py files to be necessary. Does it happen with Python 2 or
Python 3? Apparently, Kodi selects Python 2, so there really shouldn't
be any problem with having just .pyc files (Python 3 can be more
tricky in that respect.
> changes v1 -> v2:
> - fix spurious 'i' (vim insert)
But it wasn't enough it seems :)
> -comment "kodi needs a toolchain w/ C++, threads, wchar, dynamic library"
> +comment "kodi needs python and .py modiules, and a toolchain w/ C++, threads, wchar, dynamic library"
^^^^^^^^
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-13 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 21:13 [Buildroot] [PATCHv2] package/kodi: needs .py modules Yann E. MORIN
2015-09-13 21:29 ` Thomas Petazzoni [this message]
2015-09-13 21:35 ` Yann E. MORIN
2015-09-19 12:40 ` Thomas Petazzoni
2015-09-19 15:47 ` Yann E. MORIN
2015-09-20 8:17 ` Thomas Petazzoni
2015-09-26 14:40 ` Bernd Kuhls
2015-09-15 16:37 ` Arnout Vandecappelle
2015-09-15 20:03 ` Yann E. MORIN
2015-09-15 20:52 ` Arnout Vandecappelle
2015-09-15 21:05 ` Yann E. MORIN
2015-12-05 20:38 ` Yann E. MORIN
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=20150913232942.736dea75@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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