I had successfully tested version 3.0.11-rc3 with my work-in-progress port of python-ctypes on iOS.

I tried to use version 3.0.11 final for the same purpose, using the new xcode build system provided in pull requests in issues #15 and #16 :

• I manage to get libffi being built without any warning.
• I manually create an universal library out of the arm and i386 libraries

If I use this new library in my python build, it compiles and link without problem, but does not run anymore : the process halts with a SIGABRT in the simulator.

The signal is issued by assert(cinuse(p)); in do_check_inuse_chunk called by libc's free function, in a portion of code that has nothing to do with libffi.

I've double checked my results : when I build libffi (3.0.11 rc3 or final) with the build-ios.sh script that has been removed it all works fine.

As the new build system has no documentation or rationale, and I'm far from being an Xcode power user, I cannot alas provide any workaround for this problem. Right now I'll keep on using the previous build-ios.sh script.