Virtual envs: ImportError with `bin/opensfm_run_all`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 899
- PR merge metrics
- No merged PRs in 30d
Description
Building OpenSfM
What I have
Operating System: Manjaro Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.15.94-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
System Version: ThinkPad T580
What I did
- cloned recursively the repo
- installed
opencvandceres-solver(with paru package manager) - created virtual env using conda called
opensfm-envand activated it - runned
pip install -r requirements - runned
python setup.py buildall went well
What I got
But when I want to test bin/opensfm_run_all data/berlin I get this error:
Traceback (most recent call last):
File "/source/OpenSfM/bin/opensfm_main.py", line 9, in <module>
from opensfm import commands
File "/source/OpenSfM/opensfm/__init__.py", line 1, in <module>
from opensfm import pybundle
ImportError: /home/ayoubf/miniconda3/envs/opensfm-env/bin/../lib/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib/libtbb.so.12)
What could possibly have gone wrong ?
Thank you.
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 failure with bin/opensfm_run_all data/berlin, then inspect the environment and dependency setup in requirements and setup.py. Trace the import path through bin/opensfm_main.py and opensfm/init.py; done means the command starts without the reported ImportError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- opencv, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100