martin at v.loewis.de martin at v.loewis.de
Sun Jun 2 12:37:32 CEST 2013

• Previous message: [Python-Dev] New FreeBSD 10.0-CURRENT buildbot
• Next message: [Python-Dev] PEP 442: Safe object finalization
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Quoting Paul Smith <paul at mad-scientist.net>:

> My case may be unusual but even in a
> more formal cross-compilation environment it's not good to
> add /usr/include/..., or base such a decision on the behavior of the
> _build_ system.

The offical procedure to cover "unusual" cases is to edit Modules/Setup.
If you are not happy with the way in which modules are build, you can
override all flags on a per-module basis there.

> It seems to me (keeping with the theme of this mailing list) that the
> add_multiarch_paths() function in setup.py is not right.

Well, ..., yes. For the last two decades, the build process of Python
was *always* wrong, and it always ever will be, in the sense that it
doesn't support all cases that people come up with. The only way to
deal with this, unfortunately, is to patch the build process for each
new use case discovered.

As Ned says: if you come up with a patch, don't hesitate to post it
to the tracker.

Regards,
Martin

---

• Previous message: [Python-Dev] New FreeBSD 10.0-CURRENT buildbot
• Next message: [Python-Dev] PEP 442: Safe object finalization
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list