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: ./configure --with-system-ffi=LIBFFI-PATH
Type: enhancement Stage: resolved
Components: Build Versions: Python 3.3
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: Jens.Timmerman, amaury.forgeotdarc, belopolsky, meador.inge, michael.kraus
Priority: normal Keywords:

Created on 2011-11-28 09:24 by michael.kraus, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg148472 - (view) Author: Michael Kraus (michael.kraus) Date: 2011-11-28 09:24
It would be very helpful to have the ability to specify a LIBFFI-PATH during Python configuration via

./configure --with-system-ffi=LIBFFI-PATH

We are using the Intel compiler to build Python, NumPy, SciPy, and Cython on a SuSE Linux Enterprise Server. Libffi uses some 128bit int type which is not defined by the Intel compiler, thus can't be build with it. 

Unfortunately, the ./configure script, if run with --with-system-ffi looks for the ffi includes only in the standard directories (/usr/include, etc.). On our cluster, we are not allowed to install into the main system, we can only add modules. As there is no libffi coming with SLES and we cannot install it into the standard directories, the configure script won't find it. Thus the above request.

Best regards,
msg148533 - (view) Author: Meador Inge (meador.inge) * (Python committer) Date: 2011-11-29 01:22
Also see issue4130.
msg205686 - (view) Author: Jens Timmerman (Jens.Timmerman) Date: 2013-12-09 12:41
As a workaround, you can make the libffi build work by applying this patch.

(indeed, see also )
msg242712 - (view) Author: Jens Timmerman (Jens.Timmerman) Date: 2015-05-07 12:25
Wel, I can confirm that this is fixed in new libffi shipped with python now, and the problem no longer occurs on 3.4.3 (only version I checked)
Date User Action Args
2022-04-11 14:57:24adminsetgithub: 57701
2016-03-02 10:41:46berker.peksagsetstatus: open -> closed
resolution: out of date
stage: needs patch -> resolved
2015-05-07 12:25:32Jens.Timmermansetmessages: + msg242712
2013-12-09 12:41:36Jens.Timmermansetnosy: + Jens.Timmerman
messages: + msg205686
2011-11-29 01:22:31meador.ingesetmessages: + msg148533
2011-11-28 16:46:56pitrousetnosy: + amaury.forgeotdarc, belopolsky

versions: - Python 2.6, Python 3.1, Python 2.7, Python 3.2, Python 3.4
2011-11-28 15:31:31meador.ingesetnosy: + meador.inge

stage: needs patch
2011-11-28 09:24:31michael.krauscreate