-
Notifications
You must be signed in to change notification settings - Fork 226
Description
Hello.
I am trying to build a very simple project based on python-manylinux-demo for all available architectures and I've discovered a problem on ppc64le.
The problem is that in a wheel produced by the latest manylinux container image (for example simple_manylinux_demo-1.0-cp38-cp38-manylinux2014_ppc64le.whl
), I have an compiled extension with the following name: extension.cpython-38-powerpc64le-linux-gnu.so
when I believe that the correct name is extension.cpython-38-ppc64le-linux-gnu.so
.
We have discovered the problem on a system where sysconfig.get_config_var("EXT_SUFFIX")
is '.cpython-38-ppc64le-linux-gnu.so'
and therefore Python cannot find the extension with a different architecture name in the file name.
All Pythons in the container image are configured with powerpc64le:
# for PYBIN in /opt/python/*/bin/; do "${PYBIN}/python" -c 'import sysconfig; print(sysconfig.get_config_var("EXT_SUFFIX"))'; done
.cpython-35m-powerpc64le-linux-gnu.so
.cpython-36m-powerpc64le-linux-gnu.so
.cpython-37m-powerpc64le-linux-gnu.so
.cpython-38-powerpc64le-linux-gnu.so
.cpython-39-powerpc64le-linux-gnu.so
I think that they should be configured with '.cpython-XY-ppc64le-linux-gnu.so'
. What do you think about it?