precice / precice/python-bindings
Installing with pip requires call to ldconfig if preCICE is built from source
Nobody has claimed this yet.
- Dominant language
- Cython
- Stars
- 30
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
I built preCICE from source yesterday (on Linux Mint, with parameters suggested here) and installed it succesfully, but then, running pip install --user pyprecice generates an error libprecice.so.2 not found. Running sudo ldconfig before running pip is enough to fix it.
The issue doesn't appear if we install a .deb package for libprecice. I noticed that the post-installation script of the .deb does include a call to sudo ldconfig, which explains a lot.
Suggested fix : Either add a call to ldconfig in the installation instructions (on the website) or the the install script (probably hard, since ldconfig requires superuser, it would break install into a user-chosen path without superuser). Unless something is wrong on the binding side, but I doubt it.
Contributor guide
No contributing guide indexed for this repository
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
The report concerns the source-build installation instructions, install script, and .deb post-installation script; begin by comparing those paths with the pip binding installation. Done means a source build followed by pip install works without a manual ldconfig call, or the required step is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100