2017-11-15, 11:15
Either you adjust your attitude or you can go elsewhere for help. First rule when troubleshooting is to follow docs to the point to reproduce.
You can use whatever toolchain you want, but that necessitates that you understand our depends system well and can configure it correctly. Docs simply assume the official RBPI toolchains for a reason: they have been well tested and are what our devs and CI system use. And yes, on ubuntu. We simply cannot test and officially support every distro under the sun, so some issues might pop up when using something else. Doesn't mean we don't try to help, but you have to work with us.
As already said, your current issue is not related to the cross toolchain, since the host native python seems to have some path issue.
It be nice if you could try to troubleshoot the
python install in /usr/local/src/kodi-xbuild/RPi2/kodi-bcm/i686-linux-gnu-native
Play around with
setting $PYTHONHOME, see if python runs in general etc.
edit: make sure "export PYTHONHOME=/usr" is NOT set
You can use whatever toolchain you want, but that necessitates that you understand our depends system well and can configure it correctly. Docs simply assume the official RBPI toolchains for a reason: they have been well tested and are what our devs and CI system use. And yes, on ubuntu. We simply cannot test and officially support every distro under the sun, so some issues might pop up when using something else. Doesn't mean we don't try to help, but you have to work with us.
As already said, your current issue is not related to the cross toolchain, since the host native python seems to have some path issue.
It be nice if you could try to troubleshoot the
python install in /usr/local/src/kodi-xbuild/RPi2/kodi-bcm/i686-linux-gnu-native
Play around with
setting $PYTHONHOME, see if python runs in general etc.
edit: make sure "export PYTHONHOME=/usr" is NOT set
