[issue28491] Remove bundled libffi for OSX

2020-11-08 Thread Ronald Oussoren
Ronald Oussoren added the comment: This was implemented in bpo-41100 -- dependencies: -Build failure on macOS 11 (beta) resolution: -> fixed stage: test needed -> resolved status: open -> closed superseder: -> Build failure on macOS 11 (beta) ___

[issue28491] Remove bundled libffi for OSX

2020-10-23 Thread Ronald Oussoren
Ronald Oussoren added the comment: added 41100 as a dependency because that switches to the system libffi (as a side effect of larger changes) -- dependencies: +Build failure on macOS 11 (beta) ___ Python tracker

[issue28491] Remove bundled libffi for OSX

2017-03-15 Thread Chi Hsuan Yen
Chi Hsuan Yen added the comment: Update: my pull request at https://github.com/libffi/libffi/pull/288 is merged. Future libffi releases don't need pkg-config anymore. However, I guess the system copy won't be updated in near future. -- ___ Python tr

[issue28491] Remove bundled libffi for OSX

2016-10-21 Thread Kubilay Kocak
Changes by Kubilay Kocak : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue28491] Remove bundled libffi for OSX

2016-10-21 Thread Stéphane Wirtel
Stéphane Wirtel added the comment: Hi Ronald, As you can see in my message #msg279069 I have tested with the last version of libffi (installed with HomeBrew), so in this case, I think we can say "Yes" to your question, the current release of libffi works fine with OSX. Now, I can check more d

[issue28491] Remove bundled libffi for OSX

2016-10-21 Thread Ronald Oussoren
Ronald Oussoren added the comment: Does the upstream libffi work reliably on OSX by this time? The bundled version of libffi was extracted from PyObjC, and that copy is itself a patched version of the system libffi on OSX. The reason I don't use the system libffi is both that I don't want to

[issue28491] Remove bundled libffi for OSX

2016-10-20 Thread Stéphane Wirtel
Stéphane Wirtel added the comment: On my OSX with El Capitan and HomeBrew Configuration: env PKG_CONFIG_PATH=/usr/local/opt/libffi/lib/pkgconfig ./configure --prefix=$PWD-build Compilation: make Tests: ./python.exe -c 'import ctypes' Results: * No SIGSEGV * Add a new dependency to pkg-con

[issue28491] Remove bundled libffi for OSX

2016-10-20 Thread Ned Deily
Ned Deily added the comment: Yes, we shouldn't be depending on pkg-config being available. I am not at all keen on adding a dependency on a third-party library supplied by another distributor. What I would like to see is: (1) add libffi to the third-party libs built and used for the macOS ins

[issue28491] Remove bundled libffi for OSX

2016-10-20 Thread Chi Hsuan Yen
Chi Hsuan Yen added the comment: With this change pkg-config becomes mandatory on macOS, too. As Ned has mentioned in issue28207, pkg-config is not pre-installed with macOS. -- ___ Python tracker _

[issue28491] Remove bundled libffi for OSX

2016-10-20 Thread Stéphane Wirtel
Stéphane Wirtel added the comment: I will test on my OSX (El Capitan) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue28491] Remove bundled libffi for OSX

2016-10-20 Thread Zachary Ware
New submission from Zachary Ware: Here's a patch that at least allows _ctypes to be built against a Homebrew libffi and pass the test_ctypes. It is almost certainly not a complete patch, but may serve as a basis for something that will actually work. -- components: Build, ctypes, macO