Problems while installing boschshcpy
MiGro1194 opened this issue · comments
Hello everybody,
I hope you are doing fine and have a nice weeked.
I am working on my Home Assistant Project today and unfortunately I have no climate control sensors - so I decided to use the "boschshcpy" component, to rescan my environment.
Unfortunately there are some errors while installing the component (also with the operator --use-pep517).
Maybe someone has an idea what to do (I have to use a ocr scanner because I am using the onboard shell client from home assistant, i hope there are no scanning mistakes):
Running setup.py install for cffi: started
Running setup.py install for cffi: finished with status 'error' error: subprocess-exited-with-error
x Running setup.py install for cffi did not run successfully. exit code: 1 —> (49 lines of output]
1
No working compiler found, or bogus compiler options passed to the compiler from Python's standard "distutils" module. See the error messages above. Likely, the problem is not related to CFFI but generic to the setup.py of any Python package that tries to compile C code. (Hints: on OS/X 10.8, for errors about -mno-fused-madd see http://stackoverflaw.corn/questions/22313407/ Otherwise, see https://wiki.python.org/moin/CompLangPython or the IRC channel gpython on irc.libera.chat.)
Trying to continue anyway. If you are trying to install CFFI from a build done in a different context, you can ignore this warning.
/usr/lib/python3.10/site-packages/setuptools/config/setupcfg.py:508: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead. warnings.warn(msg, warning_class) running install /usr/lib/python3.10/site-packages/setuptools/ccomand/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn( running build running build_py creating build creating build/lib.linux-aarch64-cpython-310
creating build/lib.linux-aarch64-cpython-310/cffi copying cffi/vengine_cpy.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/recompiler.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/verifier.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/api.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/cffi_opcode.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/cparser.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/error.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/commontypes.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/__init__.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/vengine_gen.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/setuptools_ext.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/pkgconfig.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/lock.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/model.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/ffiplatform.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/backend_ctypes.py
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/_cffi_include.h
-> build/lib.linux-aarch64-cpython-310/cffi copying cffi/parse_c_type. h
-> build/lib.linux-aarch64-cpython-310/cffi copying cffii_embedding.h
-> build/lib.linux-aarch64-cpython-310/cffi copying cffii_cffi_errors.h
-> build/lib.linux-aarch64-cpython-310/cffi running build_ext building '_cffi_backend' extension creating build/temp.linux-aarch64-cpython-310 creating build/temp.linux-aarch64-cpython-310/c gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -03 -Wall -Os -g -02 -Os -g -02 -Os -g -02 -DTHREAD_STACK_SIZE=Ox100000 -fPIC -DFFI_BUILDING=1 -I/usr/include/python3.10 -c c/_cffi_backend.c -o build/temp.linux-aarch64-cpython-310/c/_cffi_backend.o error: command 'gcc' failed: No such file or directory (end of output]
Solved the problem on my own
pip install --upgrade cffi==1.15.0