View Single Post
Old 07-14-2015, 11:16 PM   #11
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
No issues on my end, although that's with a custom, self-built TC (from an x86 or x86_64 host). I don't remember having to jump through extra hoops when moving to a x86_64 host (at least for the core Python distribution itself, third-party modules were another kettle of fish), the only thing that needed hand-holding on that front was strace, IIRC.

I'm also using the exact same version of Python I'm building as the host's default Python interpreter, which possibly helps .

Code:
┌─(ROOT@(none):pts/0)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(/)─┐
└─(1.12:42%:05:11:48%:#)── python                                                                                                                                                                                                                            ──(Wed, Jul 15)─┘
Python 2.7.10 (default, May 31 2015, 03:02:25) 
[GCC 4.9.3 20150413 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import math
>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
>>>
See the rest of the script I linked for the gory details, and this thread for the binaries.

EDIT: And, FWIW:

Code:
┌─(ROOT@(none):pts/0)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(/)─┐
└─(0.63:42%:05:21:47%:#)── eu-readelf -s /mnt/onboard/.niluje/python/lib/libpython2.7.so.1.0 | grep Py_InitModule                                                                                                                                            ──(Wed, Jul 15)─┘
  898: 000c49e9    460 FUNC    GLOBAL DEFAULT       12 Py_InitModule4

Last edited by NiLuJe; 07-14-2015 at 11:28 PM.
NiLuJe is offline   Reply With Quote