[issue17848] can't compile with clang and build a shared lib due to libffi

Ned Deily added the comment: As of Python 3.7, Python source releases no longer "vendor" the source of libffi for Linux platforms; you need to use either a system-supplied libffi or, if really necessary, build and link with your own copy (not always easy to do). As the supplied patch

[issue17848] can't compile with clang and build a shared lib due to libffi

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17848] can't compile with clang and build a shared lib due to libffi

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17848] can't compile with clang and build a shared lib due to libffi

Changes by Brett Cannon br...@python.org: -- nosy: +amaury.forgeotdarc, belopolsky, meador.inge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17848 ___

[issue17848] can't compile with clang and build a shared lib due to libffi

Changes by Brett Cannon br...@python.org: -- title: issue about compile with clang and build a shared lib - can't compile with clang and build a shared lib due to libffi ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17848

[issue17848] can't compile with clang and build a shared lib due to libffi

Alexander Belopolsky added the comment: Leon, Are you trying to run compiled python binary before it was installed? If so, this is expected and not specific to clang or libffi. If your issue is something else - please explain how to reproduce it and post the error messages that you see.