[issue23966] More clearly expose/explain native and cross-build target information

2015-04-21 Thread Toshio Kuratomi
Toshio Kuratomi added the comment: Note for doko/barry: The multiarch/Tuples page should have a section on how the MultiArch Tuples interact with hwcaps (or a link to such a section in a different document). The rationale for not using Gnu-Triplets in MulitArch/Tuples currently says that we d

[issue23966] More clearly expose/explain native and cross-build target information

2015-04-17 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23966] More clearly expose/explain native and cross-build target information

2015-04-16 Thread Nick Coghlan
Nick Coghlan added the comment: Capturing some additional notes regarding the purpose of multiarch platform triplets. These triplets should unambiguously capture: * syscall ABI (~= kernel) * instruction set (IA-32, IA-64, PowerPC, ARM, ARM64, etc) * endianĀ­ness (big- or little- * word size (32-

[issue23966] More clearly expose/explain native and cross-build target information

2015-04-15 Thread Nick Coghlan
New submission from Nick Coghlan: Discussion of issue 22980 made it clear to me that part of the problem with the cross-build support is that the difference between the build time information exposed in sysconfig and the live system information exposed in the platform module isn't clear. Debi