homepage

Compiling Python 3.4.2 32-bit using GCC under RHEL6.4 and RHEL5.5 yields to crash:
*** WARNING: renaming "_ctypes" since importing it failed: build/lib.linux-x86_64-3.4/_ctypes.cpython-34m.so: undefined symbol: ffi_call_win32
Why is it referring to a win32 api when i'm compiling under Linux?
This failure causes pip installation to also fail due to missing ctypes module.
FYI - 3.4.1 under exact same env. builds fine.

Similar issue on old FreeBSD versions: issuee #22521.

This appears to be caused by the update to libffi version 3.1 in 3.4.2.

could somebody attach a build log from such a system? and the libffi config.log?

attached python 3.4.2 configure log on RHEL6.4

make log from RHEL 6.4 for python 3.4.2.
Also got this on the STDERR:
$ make > ../make.log
build/temp.linux-x86_64-3.4/opt/python-3.4.2/Python-3.4.2/Modules/_ctypes/libffi/src/x86/ffi.o: In function `ffi_prep_closure_loc':
/opt/python-3.4.2/Python-3.4.2/Modules/_ctypes/libffi/src/x86/ffi.c:679: undefined reference to `ffi_closure_FASTCALL'
/usr/bin/ld: build/temp.linux-x86_64-3.4/opt/python-3.4.2/Python-3.4.2/Modules/_ctypes/libffi/src/x86/ffi.o: relocation R_386_GOTOFF against undefined hidden symbol `ffi_closure_FASTCALL' can not be used when making a shared object
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status

configure arguments:
BASECFLAGS=-m32 LDFLAGS=-m32 CFLAGS=-m32 ./configure --prefix=/opt/python-3.4.2/ > ../configure.log
attached system rpm information. no additional binaries/PATHs/LD_LIB_PATHs

> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
and using -m32 explicitly.
so you'll get what you deserve ;-)

[siyuan@siyuan-lnx:siyuan-ott]$ lsb_release -a 
LSB Version:	:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID:	RedHatEnterpriseWorkstation
Description:	Red Hat Enterprise Linux Workstation release 6.4 (Santiago)
Release:	6.4
Codename:	Santiago
[siyuan@siyuan-lnx:siyuan-ott]$ uname -a 
Linux siyuan-lnx 2.6.32-358.0.1.el6.x86_64 #1 SMP Wed Feb 20 11:05:23 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
:( there's nothing special..

What does "-m32" mean?

"-m32" means "compile a 32-bit build though I'm on a 64-bit platform". I'm not sure why Matthias says this is "getting what you deserve", since everytime I've tried, "-m32" worked properly for building Python.

Comparing this to issue23042, this same behavior appears on i386 releases of FreeBSD 8.3 and 10.1 (the i386-RELEASE means it's 32-bit as opposed to 64-bit build). Given that this issue is being triggered here with -m32 (triggers building of 32-bit binaries) and yet we don't appear to be having this issue on 64-bit builds, that could be a useful clue.

This is likely also related to issue23042.
The precompiler #ifdefs were mixed up, causing Win32 code to be compiled in on other platforms as well.

There is now a proposed patch on issue23042 which, having gone through those changes, may well address this issue too.
Testing that patch on multiple platforms (including the RHEL variants relevant here) would be much appreciated.
Thanks goes to @lemburg for doing the investigative work and providing the diffs that occurred to the Modules/_ctypes/libffi/src/x86/ffi.c file in the past -- that work made the patch possible to sort out.

@davin @lemburg
just tested with the provided patch in http://bugs.python.org/issue23042, the partch works.
dupe the bug?

@siyuan: Duping it -- thanks for trying that patch out so quickly!