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

[michaelkraus]

BPO	13492
Nosy	@amauryfa, @abalkin, @meadori

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2016-03-02.10:41:46.923>
created_at = <Date 2011-11-28.09:24:31.045>
labels = ['type-feature', 'build']
title = './configure --with-system-ffi=LIBFFI-PATH'
updated_at = <Date 2016-03-02.10:41:46.923>
user = 'https://bugs.python.org/michaelkraus'

bugs.python.org fields:

activity = <Date 2016-03-02.10:41:46.923>
actor = 'berker.peksag'
assignee = 'none'
closed = True
closed_date = <Date 2016-03-02.10:41:46.923>
closer = 'berker.peksag'
components = ['Build']
creation = <Date 2011-11-28.09:24:31.045>
creator = 'michael.kraus'
dependencies = []
files = []
hgrepos = []
issue_num = 13492
keywords = []
message_count = 4.0
messages = ['148472', '148533', '205686', '242712']
nosy_count = 5.0
nosy_names = ['amaury.forgeotdarc', 'belopolsky', 'meador.inge', 'michael.kraus', 'Jens.Timmerman']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13492'
versions = ['Python 3.3']

[michaelkraus]

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,
Michael

[meadori]

Also see bpo-4130.

[JensTimmerman]

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 )

[JensTimmerman]

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)