On 20 Sep, 2010,at 04:31 PM, Tom Browder <tom.browder at gmail.com> wrote: Continuing on with investigating Python 2.7 build problems, one problem I just discovered is a different installation on one 64-bit system (Debian Lenny) versus another (Ubuntu 10.04.1 LTS). I used gcc-4.51 on both systems, with no *PY* environment variables set. On Debian I got two directories: /usr/local/lib64/python2.7 /usr/local/lib/python2.7 and only the first had the "config" subdirectory. On Ubuntu I got only /usr/local/lib/python2.7 I see that the configure file has some architecture choices (--with-universal-archs=ARCH) but no explanation about the consequences. Can anyone explain the two different "default" installations I got? It seems to me I should force the Ubuntu-style installation by the "--with-universal-archs=64-bit" configure option, and I will try that on Debian while I await expert help. --with-universal-archs only does something on OSX, and then only when --with-universalsdk is specified. It is used to select which processor architectures are included in a "universal binary" build of Python. Ronald Thanks. -Tom _______________________________________________ Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/ronaldoussoren%40mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100920/79b1d180/attachment-0001.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4