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.

Title: python3 k1om dissociation permanence: libffi
Type: compile error Stage: resolved
Components: Extension Modules Versions: Python 3.6, Python 3.5
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: doko, mancoast, ned.deily
Priority: normal Keywords: patch

Created on 2016-01-24 15:49 by mancoast, last changed 2022-04-11 14:58 by admin. This issue is now closed.

File name Uploaded Description Edit
0001-k1om-libffi.patch mancoast, 2016-01-24 15:49 review
Messages (2)
msg258888 - (view) Author: ƦOB COASTN (mancoast) * Date: 2016-01-24 15:49
initial patch attached for Python-3.4.4
This patch requires rework.

I am willing to implement the __MIC__ or __KNC__ into a new patch if this is in fact the route forward that seems optimal.


> Enabling the build system for Intel MIC k1om is non-trivial using
> Python-3.4.4
> Using Python2 for the k1om is very popular, but I require Python3
> support on k1om.
> The first requirement to complete this build involved the download and
> extraction of pre-built MPSS RPM's.
> Then built required host python bins using GCC.
> Lastly, build MIC bins using ICC.
> The exacts are appended to the end of this message.
> I would like to discuss a few change requirements that trial and error
> has revealed.
> 1.) libffi requires the University OF Cantabria patch because the k1om
> is not binary compatible with x86_64. [attached]
> These libffi changes could be implemented using the __MIC__ or __KNC__
> macros.
> *see
msg368410 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2020-05-08 02:51
Thanks for the patch and sorry for the long delay in replying.  As you may know, as of Python 3.7, we no longer "vendor" a copy of the libffi source in Python source releases; you now have to use either a system-supplied version of libffi or otherwise supply your own copy of the library.  So, if the changes to libffi are still needed, you would need to pursue them with the libffi project.
Date User Action Args
2022-04-11 14:58:26adminsetgithub: 70380
2020-05-08 02:51:58ned.deilysetstatus: open -> closed

nosy: + ned.deily
messages: + msg368410

resolution: out of date
stage: resolved
2016-01-24 16:04:01SilentGhostsetnosy: + doko

components: + Extension Modules
versions: - Python 3.2, Python 3.3, Python 3.4
2016-01-24 15:49:55mancoastcreate