This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients Alex.Willmer, barry, doko, dstufft, eric.araujo, martin.panter, vstinner, xdegaye, yan12125, zach.ware
Date 2016-11-30.21:32:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480541542.68.0.294125189944.issue28833@psf.upfronthosting.co.za>
In-reply-to
Content
So I suggest we start with this patch as it works for:
* The standard library extension modules (for debian as well).
* The third-party extension modules on platforms that have multiarch defined and on platforms that do not have multiarch defined (on debian systems one can only use the build directory for XBUILD_PYTHON_DIR, the other systems can use the three options described in msg281993).

Then we can later extend the semantics of XBUILD_PYTHON_DIR to include the multiarch triplet if this is necessary for debian systems, unless the debian developers want to continue using the system they have developed and are currently using to cross compile third-party extension modules.
History
Date User Action Args
2016-11-30 21:32:22xdegayesetrecipients: + xdegaye, barry, doko, vstinner, eric.araujo, martin.panter, zach.ware, dstufft, Alex.Willmer, yan12125
2016-11-30 21:32:22xdegayesetmessageid: <1480541542.68.0.294125189944.issue28833@psf.upfronthosting.co.za>
2016-11-30 21:32:22xdegayelinkissue28833 messages
2016-11-30 21:32:22xdegayecreate