New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libffi assembler relocation check is not robust, fails with clang #55938
Comments
The check under Modules/_ctypes/libffi/configure.ac does;
With clang; we get: clang: warning: argument unused during compilation: '-g' So it fails to detect pc relocation support due to an unrelated warning. |
I suggest you complain to the libffi maintainers. |
This is already fixed in upstream, check has been changed into: libffi_cv_as_x86_pcrel=no
echo '.text; foo: nop; .data; .long foo-.; .text' > conftest.s
if $CC $CFLAGS -c conftest.s > /dev/null; then
libffi_cv_as_x86_pcrel=yes
fi
]) |
You can install the newest libffi and pass --with-system-ffi option to main |
Yes I can workaround it but I'd like to get it fixed inside Python too ;) |
Internal copies of third-party libraries are rather always outdated, so it's better to always use system libraries. IMHO Python shouldn't bundle any third-party libraries and should force users to use system libraries. At least, system libraries could be used by default and main |
Ping? Shall I submit a fix for Modules/_ctypes/libffi/configure.ac or better yet will you sync in-tree libffi? |
Well, ctypes is kindof unmaintained right now, and the private libffi copy belongs to that module. |
Patch for configure.ac then? |
See also bpo-12081. |
In 3.3 libffi has been updated to 3.0.11. Our clang buildbot does not It would help if you provided a link to the upstream patch. |
See http://sourceware.org/ml/libffi-discuss/2011/msg00024.html for the libffi patch. |
New changeset 190a115b7748 by Stefan Krah in branch '3.3': |
Thanks for the link. The diff was committed last week to the upstream |
Stefan, can we merge this to the 2.7 branch as well please? |
koobs <report@bugs.python.org> wrote:
If Benjamin is okay with it, yes. The problem with these configure fixes |
Thanks for the quick response. I'd be happy for it to be FreeBSD conditional/specific if that's more suitable, safer? Having said that, our buildbot OS coverage is pretty good, no? |
The buildbot coverage is good, but the number of (OS, shell, compiler) |
Okay with me to backport. |
New changeset b9792b27d410 by Stefan Krah in branch '2.7': |
New changeset 7a2e0c1bb1a9 by Gregory P. Smith in branch '3.2':
New changeset aa3371fa9773 by Gregory P. Smith in branch '3.3':
New changeset e0fdc21c7d13 by Gregory P. Smith in branch 'default':
|
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: