This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients christian.heimes, ncopa
Date 2021-02-03.11:02:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1612350142.91.0.857420020917.issue43112@roundup.psfhosted.org>
In-reply-to
Content
SOABI basically contains the CPU architecture and Kernel ABI. The libc ABI is yet another dimension that is not encoded in the shared library ABI. 

The libc ABI is more complex than just glibc or musl. You need to include the ABI version of all core components. For example manylinux2014 defines the ABI for glibc as GLIBC_2.17, CXXABI_1.3.7, CXXABI_TM_1, GLIBCXX_3.4.19, GCC_4.8.0.

As a rule of thumb, a SOABI like ".cpython-39-x86_64-linux-gnu.so" only works the current host. You cannot safely move the file to another host or bump the SO version of any library, unless you ensure that the ABIs of all libraries are compatible.
History
Date User Action Args
2021-02-03 11:02:22christian.heimessetrecipients: + christian.heimes, ncopa
2021-02-03 11:02:22christian.heimessetmessageid: <1612350142.91.0.857420020917.issue43112@roundup.psfhosted.org>
2021-02-03 11:02:22christian.heimeslinkissue43112 messages
2021-02-03 11:02:22christian.heimescreate