De mon côté :
Raspberry Pi Zéro W v1.1
FCC ID : 2ABCB-RPI0W
IC : 20953-RPI0W
Hello,
J’ai le même type de soucis. Une mise à jour de l’antenne plante, une réinstallation plante également.
[2025-05-12 15:58:20] *************************************
[2025-05-12 15:58:20] * Launch install of dependencies *
[2025-05-12 15:58:20] *************************************
1e erreur
[2025-05-12 19:03:20] Installing build dependencies: finished with status 'error'
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [906 lines of output]
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple, https://www.piwheels.org/simple
Collecting setuptools
Using cached setuptools-80.4.0-py3-none-any.whl.metadata (6.5 kB)
Collecting wheel
Using cached https://www.piwheels.org/simple/wheel/wheel-0.45.1-py3-none-any.whl (72 kB)
Collecting scikit-build
Using cached https://www.piwheels.org/simple/scikit-build/scikit_build-0.18.1-py3-none-any.whl (85 kB)
Collecting cmake
Using cached cmake-4.0.2.tar.gz (34 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'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting ninja
Using cached https://www.piwheels.org/simple/ninja/ninja-1.11.1.4-py3-none-linux_armv6l.whl (134 kB)
Collecting distro (from scikit-build)
Using cached https://www.piwheels.org/simple/distro/distro-1.9.0-py3-none-any.whl (20 kB)
Collecting packaging (from scikit-build)
Using cached packaging-25.0-py3-none-any.whl.metadata (3.3 kB)
Collecting tomli (from scikit-build)
Using cached https://www.piwheels.org/simple/tomli/tomli-2.2.1-py3-none-any.whl (14 kB)
Using cached setuptools-80.4.0-py3-none-any.whl (1.2 MB)
Using cached packaging-25.0-py3-none-any.whl (66 kB)
Building wheels for collected packages: cmake
Building wheel for cmake (pyproject.toml): started
Building wheel for cmake (pyproject.toml): still running...
Building wheel for cmake (pyproject.toml): still running...
2e erreur
Building wheel for cmake (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
× Building wheel for cmake (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [749 lines of output]
---------------------------------------------
CMake 4.0.2, Copyright 2000-2025 Kitware, Inc. and Contributors
Found GNU toolchain
C compiler on this system is: gcc
C++ compiler on this system is: g++
Makefile processor on this system is: /usr/bin/gmake
---------------------------------------------
Makefile processor /usr/bin/gmake does not support parallel build
---------------------------------------------
g++ has setenv
g++ has unsetenv
g++ does not have environ in stdlib.h
g++ has stl wstring
g++ has <ext/stdio_filebuf.h>
---------------------------------------------
g++ -D_FILE_OFFSET_BITS=64 -DCMAKE_BOOTSTRAP -DCMake_HAVE_CXX_MAKE_UNIQUE=1 -I/tmp/tmp2018rquf/cmake-4.0.2/Bootstrap.cmk -I/tmp/tmp2018rquf/cmake-4.0.2/Source>
g++ -D_FILE_OFFSET_BITS=64 -DCMAKE_BOOTSTRAP -DCMake_HAVE_CXX_MAKE_UNIQUE=1 -I/tmp/tmp2018rquf/cmake-4.0.2/Bootstrap.cmk -I/tmp/tmp2018rquf/cmake-4.0.2/Source>
g++ -D_FILE_OFFSET_BITS=64 -DCMAKE_BOOTSTRAP -DCMake_HAVE_CXX_MAKE_UNIQUE=1 -I/tmp/tmp2018rquf/cmake-4.0.2/Bootstrap.cmk -I/tmp/tmp2018rquf/cmake-4.0.2/Source>
g++ -D_FILE_OFFSET_BITS=64 -DCMAKE_BOOTSTRAP -DCMake_HAVE_CXX_MAKE_UNIQUE=1 -I/tmp/tmp2018rquf/cmake-4.0.2/Bootstrap.cmk -I/tmp/tmp2018rquf/cmake-4.0.2/Source>
g++ -D_FILE_OFFSET_BITS=64 -DCMAKE_BOOTSTRAP -DCMake_HAVE_CXX_MAKE_UNIQUE=1 -I/tmp/tmp2018rquf/cmake-4.0.2/Bootstrap.cmk -I/tmp/tmp2018rquf/cmake-4.0.2/Source>
g++ -D_FILE_OFFSET_BITS=64 -DCMAKE_BOOTSTRAP -D
Puis
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for cmake
Failed to build cmake
ERROR: Failed to build installable wheels for some pyproject.toml based projects (cmake)
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
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.
[2025-05-12 19:03:29] ***************************
[2025-05-12 19:03:29] * Install ended *
[2025-05-12 19:03:29] ***************************
Si besoin de l’ensemble du log, je peux le collecter.
Merci
Bien que je ne sois pas un expert en cmake, il semble que la construction sur un RPi Zero échoue en raison de contraintes de ressources.
Avez-vous d’abord essayé d’installer cmake en tant que paquet déjà construit?
pip install cmake
et assurez-vous aussi que vos outils d’empaquetage Python sont à jour
pip install --upgrade pip setuptools wheel
Essayez ensuite d’installer à nouveau Theengs Gateway
Hello
L’installation de cmake ne progresse pas depuis 2h
user@raspberrypi:~ $ pip install cmake
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting cmake
Using cached cmake-4.0.2.tar.gz (34 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing wheel metadata ... done
Building wheels for collected packages: cmake
Building wheel for cmake (PEP 517) ... -
Je laisse faire mais je pense que ce sera KO.
Installation failed
Log_cmake_KO.txt (192,3 Ko)
Je ne pense pas que ce soit nécessaire que je lance la seconde commande?
C’est le même problème avec le RPi qui n’a pas assez de ressources pour construire cmake en tant qu’installation pip 
Pouvez-vous essayer d’installer cmake à partir des dépôts RPi OS?
sudo apt update
alors
sudo apt install cmake
Vérifiez si cela a réussi
cmake --version
Ce cmake devrait ensuite être utilisé lors de l’installation de TGW et, espérons-le, vous n’obtiendrez plus d’erreurs.
Bonjour,
pour ma part sur Raspberry PI Zero V1 2017 toutes les solutions ont echoué y compris l’installation de Cmake
Je viens de basculer sur un Raspberry PI Zero 2W : installation OK en 17 minutes (image debian 12 32 bits)
Pour moi conclusion : Theengs Gateway n’est pas ou plus compatible avec Raspberry PI Zero V1 2017 du fait des performances de son CPU trop limité.
Migrez sur Raspberry PI Zero 2W
Je suis en version cmake 3.18.4
user@raspberrypi:~ $ sudo apt update
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages [13.2 MB]
Fetched 13.3 MB in 26s (505 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
user@raspberrypi:~ $ sudo apt install cmake
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
cmake-data libarchive13 libjsoncpp24 librhash0
Suggested packages:
cmake-doc ninja-build lrzip
The following NEW packages will be installed:
cmake cmake-data libarchive13 libjsoncpp24 librhash0
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,336 kB of archives.
After this operation, 28.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.raspberrypi.org/debian bullseye/main armhf cmake-data all 3.18.4-2+rpt1+rpi1+deb11u1 [1,726 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libarchive13 armhf 3.4.3-2+deb11u2 [299 kB]
Get:5 http://archive.raspberrypi.org/debian bullseye/main armhf cmake armhf 3.18.4-2+rpt1+rpi1+deb11u1 [3,104 kB]
Get:3 http://mirrors.ircam.fr/pub/raspbian/raspbian bullseye/main armhf libjsoncpp24 armhf 1.9.4-4 [67.0 kB]
Get:4 http://mirrors.ircam.fr/pub/raspbian/raspbian bullseye/main armhf librhash0 armhf 1.4.1-2 [141 kB]
Fetched 5,336 kB in 2s (2,647 kB/s)
Selecting previously unselected package cmake-data.
(Reading database ... 44815 files and directories currently installed.)
Preparing to unpack .../cmake-data_3.18.4-2+rpt1+rpi1+deb11u1_all.deb ...
Unpacking cmake-data (3.18.4-2+rpt1+rpi1+deb11u1) ...
Selecting previously unselected package libarchive13:armhf.
Preparing to unpack .../libarchive13_3.4.3-2+deb11u2_armhf.deb ...
Unpacking libarchive13:armhf (3.4.3-2+deb11u2) ...
Selecting previously unselected package libjsoncpp24:armhf.
Preparing to unpack .../libjsoncpp24_1.9.4-4_armhf.deb ...
Unpacking libjsoncpp24:armhf (1.9.4-4) ...
Selecting previously unselected package librhash0:armhf.
Preparing to unpack .../librhash0_1.4.1-2_armhf.deb ...
Unpacking librhash0:armhf (1.4.1-2) ...
Selecting previously unselected package cmake.
Preparing to unpack .../cmake_3.18.4-2+rpt1+rpi1+deb11u1_armhf.deb ...
Unpacking cmake (3.18.4-2+rpt1+rpi1+deb11u1) ...
Setting up libarchive13:armhf (3.4.3-2+deb11u2) ...
Setting up libjsoncpp24:armhf (1.9.4-4) ...
Setting up librhash0:armhf (1.4.1-2) ...
Setting up cmake-data (3.18.4-2+rpt1+rpi1+deb11u1) ...
Setting up cmake (3.18.4-2+rpt1+rpi1+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u12) ...
user@raspberrypi:~ $ cmake --version
cmake version 3.18.4
CMake suite maintained and supported by Kitware (kitware.com/cmake).
Je vais tenter de relancer l’installation de l’antenne.
je pense que ca ne sert à rien d’essayer d’installer cmake
j’ai déjà investigué des problèmes similaires dans le passé et pendant l’installation une version de cmake est installée dans un venv donc on n’arrive jamais à avoir la bonne version: la version utilisée ne sera pas celle que l’on pense
je pense qu’il faut oublier le pi0 qui est bloquer en 32 bits malheureusement
1 « J'aime »
J’ai fait une enième et dernière tentative qui s’est soldée par un échec
Du coup j’abandonne. Mais j’ai un pi0W que je ne sais pas quoi faire…
Heureusement, j’ai eu de l’aide et j’ai pu créer une antenne OMG pour compenser mon antenne sur le PI0W.
Merci pour votre aide
Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.