On Sun, 31 May 2020, Matti Picus wrote:
This is due to macOS 10.15.3 not shipping its own libffi (is this
true?), so the buildbot owner (CC) had to install it via homebrew. I
don't know anything about macOS:
It still seems to be included with the Command Line Tools, which can be
installed using `xcode-select --install`:
zaytsev:~ zaytsev$ locate ffi.h
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/ffi/ffi.h
- should we bundle libffi together in the tarball we supply?
Well, if you opt for using homebrew version, you'd have to do that, unless
you want to force all users to install libffi via homebrew.
- is there a way to tell clang to statically link libffi.a rather than
dynamically link to libffi.dylib? Is that desirable?
Try giving a full path like
-l/usr/local/Cellar/libffi/3.2.1/lib/libffi.a
It is probably easier, than copying libffi.6.dylib in your distribution
and setting RPATH on the executable to make sure the loader is able to
find it.
--
Sincerely yours,
Yury V. Zaytsev
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
