Collecting numpy
Using cached https://files.pythonhosted.org/packages/51/60/3f0fe5b7675a461d96b9d6729beecd3532565743278a9c3fe6dd09697fa7/numpy-1.19.5.zip
Building wheels for collected packages: numpy
Running setup.py bdist_wheel for numpy … error
Complete output from command /home/vaibhavi/my_env/bin/python3 -u -c “import setuptools, tokenize;file=‘/tmp/pip-build-94ftb136/numpy/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/tmphx35darxpip-wheel- --python-tag cp36:
Running from numpy source directory.
Cythonizing sources
performance hint: _common.pyx:275:19: Exception check after calling ‘random_func’ will always require the GIL to be acquired. Declare ‘random_func’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:299:19: Exception check after calling ‘random_func’ will always require the GIL to be acquired. Declare ‘random_func’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:322:50: Exception check after calling ‘random_func’ will always require the GIL to be acquired. Declare ‘random_func’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:426:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:465:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:509:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:592:36: Exception check after calling ‘f0’ will always require the GIL to be acquired. Declare ‘f0’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:596:36: Exception check after calling ‘f1’ will always require the GIL to be acquired. Declare ‘f1’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:600:36: Exception check after calling ‘f2’ will always require the GIL to be acquired. Declare ‘f2’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:604:36: Exception check after calling ‘f3’ will always require the GIL to be acquired. Declare ‘f3’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:638:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:675:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:712:63: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:754:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:785:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:903:40: Exception check after calling ‘f0’ will always require the GIL to be acquired. Declare ‘f0’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:907:40: Exception check after calling ‘fd’ will always require the GIL to be acquired. Declare ‘fd’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:911:41: Exception check after calling ‘fdd’ will always require the GIL to be acquired. Declare ‘fdd’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:916:40: Exception check after calling ‘fi’ will always require the GIL to be acquired. Declare ‘fi’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:920:41: Exception check after calling ‘fdi’ will always require the GIL to be acquired. Declare ‘fdi’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:924:38: Exception check after calling ‘fiii’ will always require the GIL to be acquired. Declare ‘fiii’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:960:31: Exception check after calling ‘f’ will always require the GIL to be acquired. Declare ‘f’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
performance hint: _common.pyx:1002:32: Exception check after calling ‘f1’ will always require the GIL to be acquired. Declare ‘f1’ as ‘noexcept’ if you control the definition and you’re sure you don’t want the function to raise exceptions.
Error compiling Cython file:
…
cdef sfc64_state rng_state
def __init__(self, seed=None):
BitGenerator.__init__(self, seed)
self._bitgen.state = <void *>&self.rng_state
self._bitgen.next_uint64 = &sfc64_uint64
^
_sfc64.pyx:90:35: Cannot assign type ‘uint64_t (*)(void ) except? -1 nogil’ to 'uint64_t ()(void *) noexcept nogil’. Exception values are incompatible. Suggest adding ‘noexcept’ to the type of the value being assigned.
Processing numpy/random/_bounded_integers.pxd.in
Processing numpy/random/_common.pyx
Processing numpy/random/mtrand.pyx
Processing numpy/random/_sfc64.pyx
Traceback (most recent call last):
File “/tmp/pip-build-94ftb136/numpy/tools/cythonize.py”, line 235, in
main()
File “/tmp/pip-build-94ftb136/numpy/tools/cythonize.py”, line 231, in main
find_process_files(root_dir)
File “/tmp/pip-build-94ftb136/numpy/tools/cythonize.py”, line 222, in find_process_files
process(root_dir, fromfile, tofile, function, hash_db)
File “/tmp/pip-build-94ftb136/numpy/tools/cythonize.py”, line 188, in process
processor_function(fromfile, tofile)
File “/tmp/pip-build-94ftb136/numpy/tools/cythonize.py”, line 78, in process_pyx
[sys.executable, ‘-m’, ‘cython’] + flags + [“-o”, tofile, fromfile])
File “/usr/lib/python3.6/subprocess.py”, line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[’/home/vaibhavi/my_env/bin/python3’, ‘-m’, ‘cython’, ‘-3’, ‘–fast-fail’, ‘-o’, ‘_sfc64.c’, ‘_sfc64.pyx’]’ returned non-zero exit status 1.
Traceback (most recent call last):
File “”, line 1, in
File “/tmp/pip-build-94ftb136/numpy/setup.py”, line 508, in
setup_package()
File “/tmp/pip-build-94ftb136/numpy/setup.py”, line 488, in setup_package
generate_cython()
File “/tmp/pip-build-94ftb136/numpy/setup.py”, line 285, in generate_cython
raise RuntimeError(“Running cythonize failed!”)
RuntimeError: Running cythonize failed!
Failed building wheel for numpy
Running setup.py clean for numpy
Complete output from command /home/vaibhavi/my_env/bin/python3 -u -c “import setuptools, tokenize;file=‘/tmp/pip-build-94ftb136/numpy/setup.py’;f=getattr(tokenize, ‘open’, open)(file);code=f.read().replace(‘\r\n’, ‘\n’);f.close();exec(compile(code, file, ‘exec’))” clean --all:
Running from numpy source directory.
setup.py clean is not supported, use one of the following instead:
- `git clean -xdf` (cleans all files)
- `git clean -Xdf` (cleans all versioned files, doesn't touch
files that aren't checked into the git repo)
Add --force to your command to use it anyway if you must (unsupported).
Failed cleaning build dir for numpy
Failed to build numpy
Installing collected packages: numpy
Running setup.py install for numpy … error
Complete output from command /home/vaibhavi/my_env/bin/python3 -u -c “import setuptools, tokenize;file=‘/tmp/pip-build-94ftb136/numpy/setup.py’;f=getattr(tokenize, ‘open’, open)(file);code=f.read().replace(‘\r\n’, ‘\n’);f.close();exec(compile(code, file, ‘exec’))” install --record /tmp/pip-br9hog2q-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/vaibhavi/my_env/include/site/python3.6/numpy:
Running from numpy source directory.
Note: if you need reliable uninstall behavior, then install
with pip instead of using `setup.py install`:
- `pip install .` (from a git repo or downloaded source
release)
- `pip install numpy` (last NumPy release on PyPi)
Cythonizing sources
Error compiling Cython file:
------------------------------------------------------------
...
cdef sfc64_state rng_state
def __init__(self, seed=None):
BitGenerator.__init__(self, seed)
self._bitgen.state = <void *>&self.rng_state
self._bitgen.next_uint64 = &sfc64_uint64
^
------------------------------------------------------------
_sfc64.pyx:90:35: Cannot assign type 'uint64_t (*)(void *) except? -1 nogil' to 'uint64_t (*)(void *) noexcept nogil'. Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.
numpy/random/_bounded_integers.pxd.in has not changed
numpy/random/_common.pyx has not changed
numpy/random/mtrand.pyx has not changed
Processing numpy/random/_sfc64.pyx
Traceback (most recent call last):
File "/tmp/pip-build-94ftb136/numpy/tools/cythonize.py", line 235, in <module>
main()
File "/tmp/pip-build-94ftb136/numpy/tools/cythonize.py", line 231, in main
find_process_files(root_dir)
File "/tmp/pip-build-94ftb136/numpy/tools/cythonize.py", line 222, in find_process_files
process(root_dir, fromfile, tofile, function, hash_db)
File "/tmp/pip-build-94ftb136/numpy/tools/cythonize.py", line 188, in process
processor_function(fromfile, tofile)
File "/tmp/pip-build-94ftb136/numpy/tools/cythonize.py", line 78, in process_pyx
[sys.executable, '-m', 'cython'] + flags + ["-o", tofile, fromfile])
File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/vaibhavi/my_env/bin/python3', '-m', 'cython', '-3', '--fast-fail', '-o', '_sfc64.c', '_sfc64.pyx']' returned non-zero exit status 1.
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/pip-build-94ftb136/numpy/setup.py", line 508, in <module>
setup_package()
File "/tmp/pip-build-94ftb136/numpy/setup.py", line 488, in setup_package
generate_cython()
File "/tmp/pip-build-94ftb136/numpy/setup.py", line 285, in generate_cython
raise RuntimeError("Running cythonize failed!")
RuntimeError: Running cythonize failed!
----------------------------------------
Command “/home/vaibhavi/my_env/bin/python3 -u -c “import setuptools, tokenize;file=‘/tmp/pip-build-94ftb136/numpy/setup.py’;f=getattr(tokenize, ‘open’, open)(file);code=f.read().replace(‘\r\n’, ‘\n’);f.close();exec(compile(code, file, ‘exec’))” install --record /tmp/pip-br9hog2q-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/vaibhavi/my_env/include/site/python3.6/numpy” failed with error code 1 in /tmp/pip-build-94ftb136/numpy/
Facing the above error while installing torchvision/zed sdk/numpy/cython on jetson nano. Are there any alternatives to properly install all these dependencies? Previously I could perform object detection using TensorRT engine on jetson nano, although after installing zed sdk was continuosly facing the illegal instruction core dumped error while importing cv2 or torch.