We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When insalling semaphore from pip I get the following error:
semaphore
Building wheels for collected packages: symbolic, semaphore Building wheel for symbolic (setup.py) ... error ERROR: Complete output from command /www/sentry/bin/python2 -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-UHxQ89/symbolic/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-ooHfBf --python-tag cp27: ERROR: running `cargo build --release` (release target) running bdist_wheel running build running build_py creating build/lib.linux-armv7l-2.7 creating build/lib.linux-armv7l-2.7/symbolic copying symbolic/debuginfo.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/exceptions.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/symcache.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/sourcemap.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/minidump.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/demangle.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/unreal.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/__init__.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/proguard.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/common.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/_compat.py -> build/lib.linux-armv7l-2.7/symbolic copying symbolic/utils.py -> build/lib.linux-armv7l-2.7/symbolic error: [Errno 2] No such file or directory ---------------------------------------- ERROR: Failed building wheel for symbolic Running setup.py clean for symbolic Building wheel for semaphore (setup.py) ... error ERROR: Complete output from command /www/sentry/bin/python2 -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-UHxQ89/semaphore/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-d9JJB1 --python-tag cp27: ERROR: running bdist_wheel running build running build_py creating build/lib.linux-armv7l-2.7 creating build/lib.linux-armv7l-2.7/semaphore copying semaphore/exceptions.py -> build/lib.linux-armv7l-2.7/semaphore copying semaphore/processing.py -> build/lib.linux-armv7l-2.7/semaphore copying semaphore/__init__.py -> build/lib.linux-armv7l-2.7/semaphore copying semaphore/_compat.py -> build/lib.linux-armv7l-2.7/semaphore copying semaphore/utils.py -> build/lib.linux-armv7l-2.7/semaphore copying semaphore/auth.py -> build/lib.linux-armv7l-2.7/semaphore error: [Errno 2] No such file or directory ---------------------------------------- ERROR: Failed building wheel for semaphore Running setup.py clean for semaphore Failed to build symbolic semaphore
This happens on a "Linux 4.9.93-mainline-rev1 #1 SMP Tue Apr 10 09:42:40 UTC 2018 armv7l armv7l armv7l GNU/Linux"
The text was updated successfully, but these errors were encountered:
We don't provide wheels for armv7, so you will have to install Rust to be able to build and install semaphore.
Sorry, something went wrong.
Just in case somebody else fall into this error. The missing file is cargo the rust package installer.
cargo
You're a hero. This sudo apt-get install -y cargo solved the problem for me.
sudo apt-get install -y cargo
No branches or pull requests
Description
When insalling
semaphore
from pip I get the following error:This happens on a "Linux 4.9.93-mainline-rev1 #1 SMP Tue Apr 10 09:42:40 UTC 2018 armv7l armv7l armv7l GNU/Linux"
The text was updated successfully, but these errors were encountered: