Open vsbogd opened 3 days ago
I am tending to think delocate
behaviour on macos-14
is a bug as I manually checked artifacts and I see libraries inside are arm64
ones.
macos-13
behaviour also looks logical as system versions of libssl
and libcrypto
are used and as system version is 13 the libraries version is 13 as well. I am not sure who is responsible for targeting to the proper libraries:
cibuildwheel
environment?cibuildwheel
?
Describe the bug After upgrade to
cibuildwheel
2.19.2 (see PR https://github.com/trueagi-io/hyperon-experimental/pull/724) version0.11.0
of thedelocate
library is used while releasing binaries. This version does additional consistency checks on the Python packages built. It finds out thatlibssl
andlibcrypto
libraries used are targeted for the MacOS 13 while package is built for the MacOS 10.9 which breaks the release of the package onmacos-13
GitHub actions environment. It also fails finding correct minimum MacOS version for thearm64
platform onmacos-14
GitHub actions environment.Full log at https://github.com/trueagi-io/hyperon-experimental/actions/runs/9797477257
To Reproduce Steps to reproduce the behavior:
Expected behavior Python packages for the
macos-13
andmacos-14
are releasedActual behavior Release fails on
macos-13
with the followingdelocate
error message:Release fails on
macos-14
with the followingdelocate
error message:Additional context It should be noted that
libssl
andlibcrypto
shared libraries are included into the packages. See also https://cibuildwheel.pypa.io/en/stable/faq/#macos-library-dependencies-do-not-satisfy-target-macos