From: Stanislav Vlasic <svlasic@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Isengard 15.0 python issue - solution
Date: Fri, 24 Jul 2015 23:08:28 +0200 [thread overview]
Message-ID: <55B2A94C.9050607@gmail.com> (raw)
In-Reply-To: <XnsA4E1EA4505855berndkuhlsPkbjNfxxIA@bernd-kuhls.de>
On 07/24/2015 11:01 PM, Bernd Kuhls wrote:
> [posted and mailed]
>
> Stanislav Vlasic <svlasic@gmail.com> wrote
> in news:mou1bv$4au$1 at ger.gmane.org:
>
>> Problem was isolated and fixed by Corey Moyer. I will not submit patch
>> as I'm not original author of it, will just describe it:
>>
>> Python addons are crashing because of
>> https://github.com/xbmc/xbmc/blob/master/xbmc/interfaces/python/XBPython.
>> cpp#L565
>>
>> Patch would be to remove defined(TARGET_LINUX) from #if statement in
>> line above. I'm not sure if this issue affects all Linux builds (Kodi
>> 15.0 works fine on my Linux Mint 17.1).
>>
>> This is tested on Buildroot 2015.02 and 2015.05, Python 2.7.8, 2.7.9 and
>> 2.7.10.
>
> Hi,
>
> I never had any problems with python addons in Kodi, here is a snippet of
> my .config:
>
> BR2_PACKAGE_PYTHON=y
> BR2_PACKAGE_PYTHON_PY_ONLY=y
> # BR2_PACKAGE_PYTHON_PYC_ONLY is not set
> # BR2_PACKAGE_PYTHON_PY_PYC is not set
>
> Maybe these options have an influence?
>
> Regards, Bernd
>
Difference is that I have BR2_PACKAGE_PYTHON_PYC_ONLY selected but I'm
not sure if that could be the case because everything was working with
BR2_PACKAGE_PYTHON_PYC_ONLY as default option since XBMC 12 (I'm working
with Amlogic SoCs).
I will test with BR2_PACKAGE_PYTHON_PY_ONLY enabled and patch disabled
and will report back results.
prev parent reply other threads:[~2015-07-24 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 18:49 [Buildroot] Isengard 15.0 python issue - solution Stanislav Vlasic
2015-07-24 21:01 ` Bernd Kuhls
2015-07-24 21:08 ` Stanislav Vlasic [this message]
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=55B2A94C.9050607@gmail.com \
--to=svlasic@gmail.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