[issue28125] identify cross builds by a more generic environment setting.

Change by Xavier de Gaye : -- nosy: -xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28125] identify cross builds by a more generic environment setting.

STINNER Victor added the comment: @Matthias Klose: I concur with Xavier, can you please behave as a professional and "keep exchanges on the bug tracker strictly on a technical level"? Personal attacks doesn't help us to contribute with you. I didn't follow the discussion, but I'm sure that we

[issue28125] identify cross builds by a more generic environment setting.

Xavier de Gaye added the comment: > please try to build extension modules with mismatching abi flags (pydebug is > the relevant one). Post your results for both mismatch cases. Hum, you are claiming that there is a problem with mismatching abi flags but don't care to explain why or to

[issue28125] identify cross builds by a more generic environment setting.

Xavier de Gaye added the comment: > but not having the existing cross build infrastructure being replaced by some > new android concepts. Running 'hg log' on configure.ac and Makefile.pre.in shows that there is not a single change in the cross build infrastructure done for some new android

[issue28125] identify cross builds by a more generic environment setting.

Xavier de Gaye added the comment: What do you mean ? When cross-compiling, _PYTHON_HOST_PLATFORM is defined as $MACHDEP-$_host_cpu, but _PYTHON_SYSCONFIGDATA_NAME is suffixed with $(MACHDEP)_$(MULTIARCH) instead. -- ___ Python tracker

[issue28125] identify cross builds by a more generic environment setting.

Matthias Klose added the comment: On 13.09.2016 23:43, Xavier de Gaye wrote: > > Xavier de Gaye added the comment: > > You do not answer my questions and resort to sarcasm instead: "How did you > make it more difficult?". I understand that you may be upset because issue > 23968 has been

[issue28125] identify cross builds by a more generic environment setting.

Xavier de Gaye added the comment: You do not answer my questions and resort to sarcasm instead: "How did you make it more difficult?". I understand that you may be upset because issue 23968 has been dismantled by the recent decision of removing the platdir files, but please keep exchanges on

[issue28125] identify cross builds by a more generic environment setting.

Matthias Klose added the comment: On 13.09.2016 16:40, Xavier de Gaye wrote: > > Xavier de Gaye added the comment: > >> Plus the abi flags should not be set by hand, you'll get in trouble at least >> for naming extensions, or building extensions for the wrong abi flags. This >> was an

[issue28125] identify cross builds by a more generic environment setting.

Xavier de Gaye added the comment: > Plus the abi flags should not be set by hand, you'll get in trouble at least > for naming extensions, or building extensions for the wrong abi flags. This > was an explicit decision when I first started adding the cross-build changes. What do you mean ? The

[issue28125] identify cross builds by a more generic environment setting.

Changes by Chi Hsuan Yen : -- nosy: +Chi Hsuan Yen ___ Python tracker ___ ___

[issue28125] identify cross builds by a more generic environment setting.

Changes by Xavier de Gaye : -- nosy: +xdegaye ___ Python tracker ___ ___ Python-bugs-list

[issue28125] identify cross builds by a more generic environment setting.

Changes by STINNER Victor : -- nosy: +haypo, zach.ware ___ Python tracker ___ ___

[issue28125] identify cross builds by a more generic environment setting.

New submission from Matthias Klose: I don't like the _PYTHON_SYSCONFIGDATA_NAME hack introduced in #28046. This should be based on the target, not on a name for just a particular file. Plus the abi flags should not be set by hand, you'll get in trouble at least for naming extensions, or