Linking to libssl, libcrypto and libz breaks manylinux compatibility according to PEP-513

trueagi-io / hyperon-experimental

MeTTa programming language implementation

https://metta-lang.dev

MIT License

153 stars 50 forks source link

Linking to libssl, libcrypto and libz breaks manylinux compatibility according to PEP-513 #752

Open vsbogd opened 4 months ago

vsbogd commented 4 months ago

Reading PyO3 extension-module documentation mentioned in #432 I have found link to the PEP-513 which says that manylinux1 compatible extensions should not be dynamically linked to the shared libraries out of the provided list. Thus libssl, libcrypro and libz which are used by Git feature breaks compatibility.

luketpeterson commented 3 months ago

Hmmm. That's annoying.

It appears that https://pypi.org/project/GitPython/ uses gitoxide-core through https://github.com/Byron/gitoxide/tree/main

So perhaps we can get rid of the libgit2 downstream dependencies by moving to gitoxide-core. I can try that out.

vsbogd commented 3 months ago

It is worth to mention #725 is also related. Dynamic linkage of the system libraries in MacOSX leads to the packages which are incompatible with old MacOSX version and checkers used by cibuildwheel finds this.