You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no need to define CTYPES_PASS_BY_REF_HACK on aarch64 or riscv64. This was a bug in libffi that has since been been fixed, for riscv64 in commit 4b0c358 and for aarch64 in commit e409225.
Unconditionally removing the workaround for aarch64 could break builds on macOS that use the system install of libffi, including the installers on our website. Therefore I'm -1 on unconditionally removing the workaround.
Is the need for using the workaround something that can be tested in the configure script?
Even then it would be preferable to continue using the workaround on macOS because we also target older macOS versions that likely will never see this bug fix in the system install of libffi. Using the system install of libffi is desirable due to code signing "tricks" in that build of libffi.
There is no need to define CTYPES_PASS_BY_REF_HACK on aarch64 or riscv64. This was a bug in libffi that has since been been fixed, for riscv64 in commit 4b0c358 and for aarch64 in commit e409225.
Linked PRs
The text was updated successfully, but these errors were encountered: