Incorrect installation of `lib-dynload` for custom builds on openSUSE
Open
Nobody has claimed this yet.
OS-linux
topic-installation
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the custom build using the reported ./configure, make, and make install commands on Linux, then inspect how the installed lib-dynload path differs from sys.path. The fix is complete when extension modules such as _opcode and _posixsubprocess are found without a symlink and pip can run successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100