Getting started: python3 install_requirements.py Error preventing demo
See original GitHub issueconsole output here
host: ubuntu 18.04 (tegra/jetson) fresh install
WARNING: The scripts f2py, f2py3 and f2py3.6 are installed in '/home/toaster/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behavio ur is the source of the following dependency conflicts.
uff 0.6.9 requires protobuf>=3.3.0, but you have protobuf 3.0.0 which is incompatible.
Once this completes, attempting to run python3 depthai_demo.py causes
Illegal instruction (core dumped)
Issue Analytics
- State:
- Created 3 years ago
- Comments:23
Top Results From Across the Web
12. Virtual Environments and Packages — Python 3.11.1 ...
The solution for this problem is to create a virtual environment, ... This will create the tutorial-env directory if it doesn't exist, and...
Read more >python pip trouble installing from requirements.txt
UPDATE: This command upgrades all packages that have been explicitly listed in your requirements.txt file. Your requirements.txt file is just a list of...
Read more >Error in Terminal when trying to install requirements.txt.
Trying to install the requirements.txt file in the terminal throws an error. I've tried manually installing each separately, ...
Read more >Get Started Tutorial for Python in Visual Studio Code
Getting Started with Python in VS Code. In this tutorial, you use Python 3 to create the simplest Python "Hello World" application in...
Read more >How to Manage Python Dependencies with Conda - ActiveState
By comparison, Pip installs all package dependencies regardless of whether they conflict with other packages already installed. To avoid ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Confirmed. Jetson (nx) with OOB image, then completing the instructions from getting started results in seg fault. so for the timebeing, “modern” Jetpacks are not usable. just downloaded latest 4.5 just released will try again
I will reconfirm again tomorrow morning, but it appears that virgin 4.4 jetpack produced this seg fault on both nano and nx (which are same version, but different binary images)