Bug 196229
| Summary: | lang/python27: Build (ctypes) fails on i386 with LIBFFI option off | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Adam Weinberger <adamw> | ||||||
| Component: | Individual Port(s) | Assignee: | freebsd-python (Nobody) <python> | ||||||
| Status: | Closed Overcome By Events | ||||||||
| Severity: | Affects Only Me | CC: | edacval, w.schwarzenfeld | ||||||
| Priority: | --- | Keywords: | needs-patch, needs-qa | ||||||
| Version: | Latest | Flags: | koobs:
maintainer-feedback+
|
||||||
| Hardware: | i386 | ||||||||
| OS: | Any | ||||||||
| URL: | http://bugs.python.org/issue22521 | ||||||||
| See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194684 | ||||||||
| Attachments: |
|
||||||||
Auto-assigned to maintainer python@FreeBSD.org Created attachment 150913 [details]
showing the full build with LIBFFI off
Oh hey it assigned it to python@ anyway. Bugzilla is smarter than me! Looks like some of the backports from 3.4 will cause 2.7 to break now, too. Bug 194684 and http://bugs.python.org/issue22521 contain those information. Unfortunately there is no fix for that issue as of now. The current recommendation is to keep LIBFFI enabled on the i386 arch. If there are no news within the next few days, we will add a BROKEN message for i386, if LIBFFI is disabled. The Broken statement is in the Makefile. The PR on python.org is closed with broken. I think it is nothing to do, and this can be closed. (In reply to w.schwarzenfeld from comment #5) I agree. Closing this out. |
Created attachment 150912 [details] showing just the FFI failure If the LIBFFI option is off (i.e., use python's libffi) the _ctypes.so module gets a build failure. The port still builds, but then it fails during packaging. I'm attaching a log of just the failure and a full build log. I'm making an assumption and assigning the PR to you, but please forgive me if I should have assigned it to python@ instead.