A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-November/050081.html below:

[Python-Dev] Multilib strikes back

[Python-Dev] Multilib strikes back [Python-Dev] Multilib strikes backSkip Montanaro skip at pobox.com
Mon Nov 22 21:01:24 CET 2004
    Mihai> How about a _pyconfig_32.h and a _pyconfig_64.h and have
    Mihai> pyconfig.h include one or the other, depending on the
    Mihai> environment?

How would that be detected?  As I understand the original bug report, the
user gave gcc a -m32 flag.  How would that be reflected in the environment?

Let's assume you can coax libxml into compiling in 32-bit mode with Python
support enabled even though you have a 64-bit mode Python installed.  Won't
that just push the problem further down the tool chain?  Instead of a
compilation failure wouldn't you get a runtime error of some sort, or would
the two coexist?

Skip
More information about the Python-Dev mailing list

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