From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/kodi: needs .py modules
Date: Sat, 19 Sep 2015 17:47:35 +0200 [thread overview]
Message-ID: <20150919154735.GA3613@free.fr> (raw)
In-Reply-To: <20150919144017.4fdcc90a@free-electrons.com>
Thomas, All,
On 2015-09-19 14:40 +0200, Thomas Petazzoni spake thusly:
> Hello,
>
> On Sun, 13 Sep 2015 23:35:13 +0200, Yann E. MORIN wrote:
>
> > > Do we actually understand why it doesn't work? There is really no
> > > reason for .py files to be necessary.
> >
> > Well, what do I know about python? ;-)
> >
> > I never said I understood the issue. Just that having only .pyc modules
> > make Kodi segfault, while having .py makes it work... :-(
> >
> > All I got was the trace above. There was nothing (of interest) in Kodi's
> > own log file.
>
> As you can imagine, I'm not too happy with this solution. I believe
> Kodi is doing something incorrect, since if you just run Python with
> the .pyc files, and do "import site", it works just fine.
Yeah, I would not say the patch is the optimal solution.
> There is some logic in Kodi that tries to set the PYTHONHOME
> environment variable. Can you see in the logs if you see the following
> messages (from xbmc/interfaces/python/XBPython.cpp) :
>
> CLog::Log(LOGINFO, "initializing python engine.");
> CLog::Log(LOGDEBUG, "PYTHONHOME -> %s", CSpecialProtocol::TranslatePath("special://frameworks").c_str());
> CLog::Log(LOGDEBUG, "PYTHONPATH -> %s", CSpecialProtocol::TranslatePath("special://frameworks").c_str());
No, those messages I did not see. Only the message about suggesting to
set PYTHONHOME followed by the segfault.
> Alternatively, can you change Python, in file Modules/getpath.c,
> function calculate_path(), and dump all the environment variables?
Sure, I can have a look at it. No promise, though...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-09-19 15:47 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
2015-09-13 21:35 ` Yann E. MORIN
2015-09-19 12:40 ` Thomas Petazzoni
2015-09-19 15:47 ` Yann E. MORIN [this message]
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=20150919154735.GA3613@free.fr \
--to=yann.morin.1998@free.fr \
--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