Help with installation error

[NSDodgers]

Hello! On installation I am getting a bunch of errors in red in the logs. I was hoping for some assistance:

[11/29/2023, 12:43:17 PM] [Apple TV Enhanced] Python check:   error: subprocess-exited-with-error
  
  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [98 lines of output]
      Collecting setuptools>=61.0.0
        Using cached setuptools-69.0.2-py3-none-any.whl.metadata (6.3 kB)
      Collecting wheel
        Using cached wheel-0.42.0-py3-none-any.whl.metadata (2.2 kB)
      Collecting cffi>=1.12
        Using cached cffi-1.16.0.tar.gz (512 kB)
        Installing build dependencies: started
        Installing build dependencies: finished with status 'done'
        Getting requirements to build wheel: started
        Getting requirements to build wheel: finished with status 'done'
        Installing backend dependencies: started
        Installing backend dependencies: finished with status 'done'
        Preparing metadata (pyproject.toml): started
        Preparing metadata (pyproject.toml): finished with status 'done'
      Collecting setuptools-rust>=0.11.4
        Using cached setuptools_rust-1.8.1-py3-none-any.whl.metadata (9.4 kB)
      Collecting pycparser (from cffi>=1.12)
        Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
      Collecting semantic-version<3,>=2.8.2 (from setuptools-rust>=0.11.4)
        Using cached semantic_version-2.10.0-py2.py3-none-any.whl (15 kB)
      Collecting tomli>=1.2.1 (from setuptools-rust>=0.11.4)
        Using cached tomli-2.0.1-py3-none-any.whl (12 kB)
      Using cached setuptools-69.0.2-py3-none-any.whl (819 kB)
      Using cached wheel-0.42.0-py3-none-any.whl (65 kB)
      Using cached setuptools_rust-1.8.1-py3-none-any.whl (26 kB)
      Building wheels for collected packages: cffi
        Building wheel for cffi (pyproject.toml): started
        Building wheel for cffi (pyproject.toml): finished with status 'error'
        error: subprocess-exited-with-error
      
        × Building wheel for cffi (pyproject.toml) did not run successfully.
        │ exit code: 1
        ╰─> [59 lines of output]
            Package libffi was not found in the pkg-config search path.
            Perhaps you should add the directory containing `libffi.pc'
            to the PKG_CONFIG_PATH environment variable
            No package 'libffi' found
            Package libffi was not found in the pkg-config search path.
            Perhaps you should add the directory containing `libffi.pc'
            to the PKG_CONFIG_PATH environment variable
            No package 'libffi' found
            Package libffi was not found in the pkg-config search path.
            Perhaps you should add the directory containing `libffi.pc'
            to the PKG_CONFIG_PATH environment variable
            No package 'libffi' found
            Package libffi was not found in the pkg-config search path.
            Perhaps you should add the directory containing `libffi.pc'
            to the PKG_CONFIG_PATH environment variable
            No package 'libffi' found
            Package libffi was not found in the pkg-config search path.
            Perhaps you should add the directory containing `libffi.pc'
            to the PKG_CONFIG_PATH environment variable
            No package 'libffi' found
            running bdist_wheel
            running build
            running build_py
            creating build
            creating build/lib.linux-aarch64-cpython-310
            creating build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/lock.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/setuptools_ext.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/recompiler.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/model.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/_shimmed_dist_utils.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/cparser.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/ffiplatform.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/cffi_opcode.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/commontypes.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/_imp_emulation.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/pkgconfig.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/backend_ctypes.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/vengine_gen.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/verifier.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/vengine_cpy.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/__init__.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/api.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/error.py -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/_cffi_include.h -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/parse_c_type.h -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/_embedding.h -> build/lib.linux-aarch64-cpython-310/cffi
            copying src/cffi/_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/src
            creating build/temp.linux-aarch64-cpython-310/src/c
            arm-linux-gnueabihf-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/var/lib/homebridge/appletv-enhanced/.venv/include -I/usr/include/python3.10 -c src/c/_cffi_backend.c -o build/temp.linux-aarch64-cpython-310/src/c/_cffi_backend.o
            src/c/_cffi_backend.c:15:10: fatal error: ffi.h: No such file or directory
               15 | #include <ffi.h>
                  |          ^~~~~~~
            compilation terminated.
            error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1
            [end of output]
      
        note: This error originates from a subprocess, and is likely not a problem with pip.
        ERROR: Failed building wheel for cffi
      Failed to build cffi
      ERROR: Could not build wheels for cffi, which is required to install pyproject.toml-based projects
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.

[11/29/2023, 12:43:17 PM] [Apple TV Enhanced] Python check: error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

[11/29/2023, 12:43:18 PM] [Apple TV Enhanced] Python check: Finished
[11/29/2023, 12:43:18 PM] [Apple TV Enhanced] Platform: Starting device discovery ...
[11/29/2023, 12:43:18 PM] [Apple TV Enhanced] Platform: Error: spawn /var/lib/homebridge/appletv-enhanced/.venv/bin/atvscript ENOENT
[11/29/2023, 12:43:18 PM] [Apple TV Enhanced] Platform: Error: spawn /var/lib/homebridge/appletv-enhanced/.venv/bin/atvscript ENOENT

[maxileith]

You should install the packages libffi and libffi-dev assuming that you are on a Debian based distro.

command: sudo apt install libffi libffi-dev

[NSDodgers]

Thanks! however I'm getting Unable to locate package libffi, even after sudo apt-get update

[NSDodgers]

when I use sudo apt-get install libffi-dev, it is already installed

[maxileith]

What is your distro?

[NSDodgers]

Raspbian GNU/Linux 11 (bullseye)

[maxileith]

Sorry for the late reply. Are you using a 32 or 64Bit installation? Only 64Bit is supported.

Of this discussion is no longer required to be open, please close the thread @NSDodgers.