Incorrect installation of `lib-dynload` for custom builds on openSUSE

[intel-hm]

Bug report

Bug description:

from Python-3.13.2.tar.xz

./configure --prefix=$RUN/python/3.13.2
make -j 16
make -j 4 install

dynamic libraries are installed to $RUN/3.13.2/lib64/python3.13/lib-dynload
but internally sys.path uses $RUN/3.13.2/lib/python3.13/lib-dynload

setting a link resolves the

errors that show up:

> python3
**Could not find platform dependent libraries <exec_prefix>**
Python 3.13.2 (main, Mar 18 2025, 10:25:05) [GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
**warning: can't use pyrepl: No module named '_opcode'**

pip3 download pip wheel setuptools 
...
 from _posixsubprocess import fork_exec as _fork_exec
**ModuleNotFoundError: No module named '_posixsubprocess'**

CPython versions tested on:

3.13

Operating systems tested on:

Linux

[picnixz]

As an openSUSE user, I had this problem as well. I think I did a combination of --exec-prefix=... and altinstall. I can't remember exactly the command and I won't be back until Sunday. I can check at that time.

[tfpf]

This was previously reported and discussed in #108819. There are workarounds suggested in the comments on that issue, but no comments from any maintainers.

[picnixz]

I think I actually also specified the libdir explicitly so that it doesn't use lib64 but lib instead. I'll see if I can write better installation instructions for openSUSE

[intel-hm]

I think that's an error in the configure script. And it's not only OPENSUSE - it's also SLES

[picnixz]

Yes I think so as well but I'll need to confirm it properly. I'll also tag those responsible for openSUSE contact

[picnixz]

@mcepl From a configure PoV, what's the best? detect that we're on openSUSE or SLES or do something else?