Summary: | media-tv/xbmc-11.0_rc1 with python3.2 - src_configure(): File "<string>", line 1, in <module> TypeError: unorderable types: str() >= float() | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | mingdao <bruce> |
Component: | Current packages | Assignee: | Gentoo Xbox project <xbox> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | scarabeus |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/var/tmp/portage/media-tv/xbmc-11.0_rc1/temp/build.log
Ebuild fix to choose python-2 during build process xbmc-11.0_rc1.ebuild |
Description
mingdao
2012-03-15 00:07:02 UTC
The only thing I see in the build.log is: configure: error: this package requires Python >= 2.4. However: mingdao@HTPC ~ $ eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 * Simply don't set python 3.2 as your "system" python for now. Builds fine with python2.7 ... thanks. Created attachment 305535 [details, diff]
Ebuild fix to choose python-2 during build process
Tested this fix today; had Python-3.1 eselected instead of 3.2, but I expect it would have failed without this anyways.
Patch is against the 11.0_rc1 ebuild.
Note, this just fixes compilation -- i have no idea what will happen at runtime, but I expect that there will be issues, given all the scripts seem to use '/usr/bin/python' shebangs, instead of '/usr/bin/python2' (or the specific python2 flavour xbmc was compiled against) looks like people are making commits without talking to anyone http://sources.gentoo.org/media-tv/xbmc/xbmc-9999.ebuild?r1=1.102&r2=1.103 Hmm, yes. That PYTHON_DEPEND in -9999 should change to "2" though; given that upstream still (only) supports python-2.4 ... maybe ... but seeing as we don't have python-2.4 in the tree, and no one really cares about python-2.5 anymore, it's kind of a moot point ... Created attachment 306429 [details]
xbmc-11.0_rc1.ebuild
(In reply to comment #5) > Note, this just fixes compilation -- i have no idea what will happen at > runtime, but I expect that there will be issues, given all the scripts seem > to use '/usr/bin/python' shebangs, instead of '/usr/bin/python2' (or the > specific python2 flavour xbmc was compiled against) I replied to this and attached the ebuild in the above comment. When I hit submit it didn't have this reply. I don't know how to use this bug tracker. Anyway... I've built it with the above attachment with python2.7 selected as default, and with python3.2 selected as default. It runs either way. Currently using it with python3.2 set as default. |