[issue13492] ./configure --with-system-ffi=LIBFFI-PATH

Changes by Berker Peksag : -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue13492] ./configure --with-system-ffi=LIBFFI-PATH

Jens Timmerman added the comment: 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) -- ___ Python tracker rep...@bugs.python.org

[issue13492] ./configure --with-system-ffi=LIBFFI-PATH

Jens Timmerman added the comment: As a workaround, you can make the libffi build work by applying this patch. https://github.com/atgreen/libffi/pull/43 (indeed, see also http://bugs.python.org/issue4130 ) -- nosy: +Jens.Timmerman ___ Python tracker

[issue13492] ./configure --with-system-ffi=LIBFFI-PATH

New submission from Michael Kraus krausmic...@gmail.com: 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

[issue13492] ./configure --with-system-ffi=LIBFFI-PATH

Changes by Meador Inge mead...@gmail.com: -- nosy: +meador.inge stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13492 ___ ___

[issue13492] ./configure --with-system-ffi=LIBFFI-PATH

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +amaury.forgeotdarc, belopolsky versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13492

[issue13492] ./configure --with-system-ffi=LIBFFI-PATH

Meador Inge mead...@gmail.com added the comment: Also see issue4130. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13492 ___ ___