Jason Vas Dias <jason.vas.d...@gmail.com> added the comment:
OK, the last two comment contained complete instructions for setting
up a working dual 64-bit + 32-bit python installation.
Final, working /usr/bin/python :
$ cat /usr/bin/python
#!/bin/sh
ME=$0
ME=${ME##*/}
VERSION=${ME#python}
VERSION=${VERSION:-2.7}
ARCH=`uname -m`
case $ARCH in
i686)
exec /usr/bin/32/${ME} $*
;;
*)
exec /usr/bin/python${VERSION} $*
;;
esac
So now, in a native 64-bit env :
$ python
Python 2.7.1 (r271:86832, Apr 30 2011, 11:55:52)
[GCC 4.6.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
^D
$ setarch i686
$ python
Python 2.7.1 (r271:86832, Apr 30 2011, 13:29:12)
[GCC 4.6.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
See the build times, they are different executables !
And final, complete working /usr/include/python2.7/pyconfig.h :
$ echo '#include <python2.7/pyconfig.h>' > pyc.c
$ cpp pyc.c
$ cpp pyc.c
# 1 "pyc.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "pyc.c"
# 1 "/usr/include/python2.7/pyconfig.h" 1 3 4
# 1 "/usr/include/python2.7/64/pyconfig.h" 1 3 4
# 5 "/usr/include/python2.7/pyconfig.h" 2 3 4
# 1 "pyc.c" 2
$ cpp -m32 pyc.c
# 1 "pyc.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "pyc.c"
# 1 "/usr/include/python2.7/pyconfig.h" 1 3 4
# 1 "/usr/include/python2.7/32/pyconfig.h" 1 3 4
# 3 "/usr/include/python2.7/pyconfig.h" 2 3 4
# 1 "pyc.c" 2
$ cat /usr/include/python2.7/pyconfig.h
#ifdef __i386__
#include <python2.7/32/pyconfig.h>
#else
#include <python2.7/64/pyconfig.h>
#endif
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11946>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
