'make' errors, and RF24 on RPi, aarch64-linux-gnu

Question

'make' errors, and RF24 on RPi, aarch64-linux-gnu

Givy opened this issue 10 months ago · comments

I can't get around this issue on RPi 4 and RPi 3, both ARM64 OS. Connecting NRF24L01+ to the GPIO pins using any of the packages and libraries, /rf24libs/RF24, Raspberry-Pi-NRF24-master, RF24Network-master, etc.

#Linux RaXXXX 5.10.103-v8+ #1529 SMP PREEMPT Tue Mar 8 12:26:46 GMT 2022 aarch64 GNU/Linux
#Linux MiXXXX 6.1.0-rpi6-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2 (2023-10-27) aarch64 GNU/Linux

/rf24libs/RF24# make
arm-linux-gnueabihf-g++ -fPIC -marm -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard -Ofast -Wall -pthread
arm-linux-gnueabihf-g++ -fPIC -marm -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard -Ofast -Wall -pthread
arm-linux-gnueabihf-gcc -fPIC -marm -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard -Ofast -Wall -pthread
arm-linux-gnueabihf-gcc -fPIC -marm -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard -Ofast -Wall -pthrea
arm-linux-gnueabihf-g++ -fPIC -marm -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard -Ofast -Wall -pthread
[Linking]
arm-linux-gnueabihf-gcc -shared -Wl,-soname,librf24.so.1 -marm -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi.o spi.o bcm2835.o compatibility.o interrupt.o -lpigpio
**_/lib/libpigpio.so: file not recognized: file format not recognized
collect2: error: ld returned 1 exit status
make: *** [Makefile:46: librf24.so.1.4.8] Error 1_**

Thank you in advance.
Givi

More info::

g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/10/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-10/REAjc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=aarch64-linux-gnu- --enr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocime=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libquadmath --disable-libquadmath-supportlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --enablcking=release --build=aarch64-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu --with-build-config=bootstr
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.1 20210110 (Debian 10.2.1-6)
g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/12/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 12.2.0-14' --with-bugurl=file:///usr/share/obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-12 --program-prefix=aarch64-linux-without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enaxx-abi=new --enable-gnu-unique-object --disable-libquadmath --disable-libquadmath-support --enable-plugin lease --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --enable-fix-cortex-a53-8434u --host=aarch64-linux-gnu --target=aarch64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Debian 12.2.0-14)

TMRh20 · Answer 1 · Sun Dec 03 2023 10:05:29 GMT+0800 (China Standard Time)

Have you tried https://nrf24.github.io/RF24/md_docs_using_cmake.html

Brendan · Answer 2 · Sun Dec 03 2023 10:21:07 GMT+0800 (China Standard Time)

The configure script was really designed with the 32 bit armhf compiler in mind. We moved to cmake for several reasons, one reason was to support 64 bit aarch64 compiler better. Please use the newer cmake instructions.

Brendan · Answer 3 · Sun Dec 03 2023 10:28:39 GMT+0800 (China Standard Time)

I'm curious why pigpio was being linked to if the driver was not found. This shouldn't be a problem using cmake, but there may be something else we haven't coded for in the configure script.

Givi · Answer 4 · Mon Dec 04 2023 23:37:05 GMT+0800 (China Standard Time)

I looked and followed the URL, https://nrf24.github.io/RF24/md_docs_using_cmake.html;;
The files are not there to begin with. Something didn't get installed, or I ran a wrong install.sh looks likes it. The new install.sh ran smoth. Below, I passted the completion that showes a Warrning and Error and some during the execution for your info. I'll test it out and will let you know. Thank you Gents.

/# rm /usr/local/lib/librf24.*
rm: cannot remove '/usr/local/lib/librf24.*': No such file or directory

# cd /usr/local/lib/
root@Rakhsh:/usr/local/lib# ls -la librf24-bcm.so
ls: cannot access 'librf24-bcm.so': No such file or directory

# rm -r /usr/local/include/RF24
rm: cannot remove '/usr/local/include/RF24': No such file or directory
________________
.
.
Scanning dependencies of target rf24_mesh
[  4%] Building CXX object CMakeFiles/rf24_mesh.dir/src/pyRF24Mesh.cpp.o
In file included from /root/rf24libs/pyRF24/src/pyRF24Network.cpp:2,
                 from /root/rf24libs/pyRF24/src/pyRF24Mesh.cpp:2:
/root/rf24libs/pyRF24/src/pyRF24.cpp: In function ‘void pybind11_init_rf24(pybind11::module_&)’:
/root/rf24libs/pyRF24/src/pyRF24.cpp:888:97: **_error_**: no matches converting function ‘begin’ to type ‘bool (class RF24Wrapper::*)(uint16_t, uint16_t)’ {aka ‘bool (class RF24Wrapper::*)(short unsigned int, short unsigned int)’}
  888 |         .def("begin", static_cast<bool (RF24Wrapper::*)(uint16_t, uint16_t)>(&RF24Wrapper::begin), R"docstr(
      |                                                                                                 ^

.
.
self.build_extension(ext)
  File "/root/rf24libs/pyRF24/setup.py", line 73, in build_extension
    subprocess.check_call(["cmake", "--build", "."] + build_args, cwd=build_temp)
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '.']' returned non-zero exit status 2.
**_WARNING: Requirement 'dist/pyrf24*.whl' looks like a filename, but the file does not exist_**
**_ERROR: pyrf24*.whl is not a valid wheel filename._**


*** Installer Complete ***
See http://tmrh20.github.io for documentation
See http://tmrh20.blogspot.com for info

Listing repositories in ~/rf24libs
pyRF24  RF24  RF24Gateway  RF24Mesh  RF24Network

Brendan · Answer 5 · Tue Dec 05 2023 00:17:09 GMT+0800 (China Standard Time)

The "No such file or directory" errors just mean the previous attempt to install didn't complete (as evident by the error posted in OP). I'm not worried about that, but it is good that you tried to uninstall any previously installed RF24 drivers.

As for the pyrf24 package, I have not seen that error when building it from source. You should still be able to install the pre-compiled python wrappers using pip without problems:

pip install pyrf24

Then try any of the examples in ~/rf24libs/pyRF24/examples folder:

python ~/rf24libs/pyRF24/examples/scanner.py

Brendan · Answer 6 · Tue Dec 05 2023 01:04:45 GMT+0800 (China Standard Time)

I was able to reproduce the build error for pyRF24 when using the RPi driver. I should have a fix committed soon.

@Givy Please specify the SPIDEV driver when install.sh asks. The SPIDEV driver is much faster than the RPi driver and doesn't require sudo permission to run examples.

Givi · Answer 7 · Tue Dec 05 2023 08:02:15 GMT+0800 (China Standard Time)

I sure will, At the moment I am doing much better than before, and getting to know what's what. Thank you again. ;-]

Brendan · Answer 8 · Tue Dec 05 2023 12:35:08 GMT+0800 (China Standard Time)

Ok, I'm closing this as we've worked through the problems presented. Just to summarize:

CMake install instructions must be used on 64-bit OS (also recommended for cross-compiling)
Found and fixed a problem when building pyRF24 package from source code.

@Givy If you want to build the pyRF24 package from source then you must either

update the local git clone:
```
cd ~/rf24libs/pyRF24
git pull
```
just delete the pyRF24 folder

and then run the install.sh again.

Givi · Answer 9 · Tue Dec 05 2023 23:29:59 GMT+0800 (China Standard Time)

RPi-3 is working and "scanner" runs OK. However, on RP-4 I have problem with the "pip install pyrf24", which I am sure I did that earlier at the same time with the RP-3. I am gettinig below issues on the RPi-4::

:~/rf24libs# pip install pyrf24
error: externally-managed-environment

This environment is externally managed

To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.

If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.

For more information visit http://rptl.io/venv

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Brendan · Answer 10 · Tue Dec 05 2023 23:58:02 GMT+0800 (China Standard Time)

If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.

For more information visit http://rptl.io/venv

This is the solution you seek. It is generally good practice to use a python virtual environment ("venv" for short). You should not use sudo when working in a python venv (& when using pip) because it invokes the system python install instead of the venv python install.

The problem you are experiencing is actually not specific to pyRF24 at all. But I will try to clarify as simply as possible.

🚫 DO NOT DO THIS!!!

sudo pip install pyrf24
sudo python ~/rf24libs/pyRF24/examples/scanner.py

The above commands will only use python (interpreter and packages) installed for the entire system. 👎🏼

✔️ DO THIS!

pip install pyrf24
python ~/rf24libs/pyRF24/examples/scanner.py

The above commands will use the packages specifically installed for the current user.

⭐ Most recommended!

Create a venv in the current directory
```
python -m venv env
```
Activate the python venv
```
source env/bin/activate
```
If you want to deactivate a python venv (typically done for using different packages for different projects), then you can use the command deactivate.
Install pyrf24 (while venv is active)
```
pip install pyrf24
```

Run the examples (while venv is active)

python ~/rf24libs/pyRF24/examples/scanner.py

Important

Using the RPi driver requires sudo permission to run the examples (or any code using RF24 with RPi driver employed). If you need to use RPi driver, then you must specify the venv install of python (while venv is active):

sudo env/bin/python ~/rf24libs/pyRF24/examples/scanner.py

Brendan · Answer 11 · Wed Dec 06 2023 00:10:48 GMT+0800 (China Standard Time)

Installing pyrf24 with pip uses the SPIDEV driver and does not require the C++ RF24* libraries installed. Again, SPIDEV is recommended for speed, and it does not require sudo permission to execute examples (or any code using RF24 with SPIDEV driver employed).

Givi · Answer 12 · Wed Dec 06 2023 00:22:43 GMT+0800 (China Standard Time)

I also tried the following and got these errors::

# apt install python pyRF24
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package python is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  python-is-python3 2to3

E: Package 'python' has no installation candidate
E: Unable to locate package pyRF24

Brendan · Answer 13 · Wed Dec 06 2023 00:27:18 GMT+0800 (China Standard Time)

I'm sorry, but you clearly are not very familiar with using Debian's apt program or python CLI. I cannot help you there because it is not my job (& I'm not getting paid for this). No offense intended.

Givi · Answer 14 · Wed Dec 06 2023 00:33:30 GMT+0800 (China Standard Time)

I appreciate your help. I am not sure about the "venv ", but I guess I have to try it. Thank you so much.

Brendan · Answer 15 · Fri Dec 08 2023 03:21:41 GMT+0800 (China Standard Time)

I recently ran into a similar problem with using pip install as a non-root user... Apparently, python's pip package recently implemented a "feature" proposed by PEP668. PEP668 basically states that pip should be run only from within a venv by end-users (see the full proposal for justified rationality). This is a new restriction rolled out sometime in 2023 and most notably has affected Linux workflows.

This is what happens when python has been greatly adopted over 20+ years despite the many difficulties that python package management had from the beginning.

Givi · Answer 16 · Tue Dec 26 2023 05:49:15 GMT+0800 (China Standard Time)

Just FYI:
After more reading and additional pkg/s and re-install. Your automated shell script worked on the RPi-3. Will let you know on the RPi-4::

[100%] Built target rf24
/usr/local/lib/python3.9/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

    ********************************************************************************
    Please avoid running ``setup.py`` directly.
    Instead, use pypa/build, pypa/installer or other
    standards-based tools.

    See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
    ********************************************************************************

!!
self.initialize_options()
installing to build/bdist.linux-aarch64/wheel
running install
running install_lib
creating build/bdist.linux-aarch64
creating build/bdist.linux-aarch64/wheel
creating build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/init.py -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/rf24_network.cpython-39-aarch64-linux-gnu.so -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/rf24_network.pyi -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/rf24_mesh.pyi -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/py.typed -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/rf24_mesh.cpython-39-aarch64-linux-gnu.so -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/fake_ble.py -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/rf24.pyi -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-39/pyrf24/rf24.cpython-39-aarch64-linux-gnu.so -> build/bdist.linux-aarch64/wheel/pyrf24
running install_egg_info
Copying pyrf24.egg-info to build/bdist.linux-aarch64/wheel/pyrf24-0.2.4.post1.dev3-py3.9.egg-info
running install_scripts
adding license file "LICENSE" (matched pattern "LICEN[CS]E*")
creating build/bdist.linux-aarch64/wheel/pyrf24-0.2.4.post1.dev3.dist-info/WHEEL
creating 'dist/pyrf24-0.2.4.post1.dev3-cp39-cp39-linux_aarch64.whl' and adding 'build/bdist.linux-aarch64/wheel' to it
adding 'pyrf24/init.py'
adding 'pyrf24/fake_ble.py'
adding 'pyrf24/py.typed'
adding 'pyrf24/rf24.cpython-39-aarch64-linux-gnu.so'
adding 'pyrf24/rf24.pyi'
adding 'pyrf24/rf24_mesh.cpython-39-aarch64-linux-gnu.so'
adding 'pyrf24/rf24_mesh.pyi'
adding 'pyrf24/rf24_network.cpython-39-aarch64-linux-gnu.so'
adding 'pyrf24/rf24_network.pyi'
adding 'pyrf24-0.2.4.post1.dev3.dist-info/LICENSE'
adding 'pyrf24-0.2.4.post1.dev3.dist-info/METADATA'
adding 'pyrf24-0.2.4.post1.dev3.dist-info/WHEEL'
adding 'pyrf24-0.2.4.post1.dev3.dist-info/top_level.txt'
adding 'pyrf24-0.2.4.post1.dev3.dist-info/RECORD'
removing build/bdist.linux-aarch64/wheel
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Processing ./dist/pyrf24-0.2.4.post1.dev3-cp39-cp39-linux_aarch64.whl
Installing collected packages: pyrf24
Attempting uninstall: pyrf24
Found existing installation: pyrf24 0.2.4
Uninstalling pyrf24-0.2.4:
Successfully uninstalled pyrf24-0.2.4
Successfully installed pyrf24-0.2.4.post1.dev3

*** Installer Complete ***
See http://tmrh20.github.io for documentation
See http://tmrh20.blogspot.com for info

Listing repositories in ~/rf24libs
pyRF24 RF24 RF24Gateway RF24Mesh RF24Network

Thank you.

Givi · Answer 17 · Tue Dec 26 2023 07:43:38 GMT+0800 (China Standard Time)

Hi,
Your automated shell script also worked on the RPi-4 with some complaining::

-- Configuring done
-- Generating done
-- Build files have been written to: /root/rf24libs/pyRF24/build/temp.linux-aarch64-cpython-311/pyrf24
[ 4%] Building CXX object CMakeFiles/rf24.dir/src/pyRF24.cpp.o
[ 9%] Building CXX object CMakeFiles/rf24.dir/RF24/RF24.cpp.o
[ 14%] Building CXX object CMakeFiles/rf24.dir/RF24/utility/SPIDEV/gpio.cpp.o
[ 19%] Building CXX object CMakeFiles/rf24.dir/RF24/utility/SPIDEV/spi.cpp.o
[ 23%] Building CXX object CMakeFiles/rf24.dir/RF24/utility/SPIDEV/compatibility.cpp.o
[ 28%] Linking CXX shared module /root/rf24libs/pyRF24/build/lib.linux-aarch64-cpython-311/pyrf24/rf24.cpython-311-aarch64-linux-gnu.so
lto-wrapper: warning: using serial compilation of 6 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information
[ 28%] Built target rf24
[ 33%] Building CXX object CMakeFiles/rf24_network.dir/src/pyRF24Network.cpp.o
[ 38%] Building CXX object CMakeFiles/rf24_network.dir/RF24/RF24.cpp.o
[ 42%] Building CXX object CMakeFiles/rf24_network.dir/RF24/utility/SPIDEV/gpio.cpp.o
[ 47%] Building CXX object CMakeFiles/rf24_network.dir/RF24/utility/SPIDEV/spi.cpp.o
[ 52%] Building CXX object CMakeFiles/rf24_network.dir/RF24/utility/SPIDEV/compatibility.cpp.o
[ 57%] Building CXX object CMakeFiles/rf24_network.dir/RF24Network/RF24Network.cpp.o
[ 61%] Linking CXX shared module /root/rf24libs/pyRF24/build/lib.linux-aarch64-cpython-311/pyrf24/rf24_network.cpython-311-aarch64-linux-gnu.so
lto-wrapper: warning: using serial compilation of 7 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information
[ 61%] Built target rf24_network
[ 66%] Building CXX object CMakeFiles/rf24_mesh.dir/src/pyRF24Mesh.cpp.o
[ 71%] Building CXX object CMakeFiles/rf24_mesh.dir/RF24/RF24.cpp.o
[ 76%] Building CXX object CMakeFiles/rf24_mesh.dir/RF24/utility/SPIDEV/gpio.cpp.o
[ 80%] Building CXX object CMakeFiles/rf24_mesh.dir/RF24/utility/SPIDEV/spi.cpp.o
[ 85%] Building CXX object CMakeFiles/rf24_mesh.dir/RF24/utility/SPIDEV/compatibility.cpp.o
[ 90%] Building CXX object CMakeFiles/rf24_mesh.dir/RF24Network/RF24Network.cpp.o
[ 95%] Building CXX object CMakeFiles/rf24_mesh.dir/RF24Mesh/RF24Mesh.cpp.o
[100%] Linking CXX shared module /root/rf24libs/pyRF24/build/lib.linux-aarch64-cpython-311/pyrf24/rf24_mesh.cpython-311-aarch64-linux-gnu.so
lto-wrapper: warning: using serial compilation of 9 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information
[100%] Built target rf24_mesh
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
installing to build/bdist.linux-aarch64/wheel
running install
running install_lib
creating build/bdist.linux-aarch64
creating build/bdist.linux-aarch64/wheel
creating build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/rf24_network.cpython-311-aarch64-linux-gnu.so -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/rf24.cpython-311-aarch64-linux-gnu.so -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/rf24_network.pyi -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/fake_ble.py -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/rf24_mesh.cpython-311-aarch64-linux-gnu.so -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/rf24_mesh.pyi -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/py.typed -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/rf24.pyi -> build/bdist.linux-aarch64/wheel/pyrf24
copying build/lib.linux-aarch64-cpython-311/pyrf24/init.py -> build/bdist.linux-aarch64/wheel/pyrf24
running install_egg_info
Copying pyrf24.egg-info to build/bdist.linux-aarch64/wheel/pyrf24-0.0.0.egg-info
running install_scripts
creating build/bdist.linux-aarch64/wheel/pyrf24-0.0.0.dist-info/WHEEL
creating 'dist/pyrf24-0.0.0-cp311-cp311-linux_aarch64.whl' and adding 'build/bdist.linux-aarch64/wheel' to it
adding 'pyrf24/init.py'
adding 'pyrf24/fake_ble.py'
adding 'pyrf24/py.typed'
adding 'pyrf24/rf24.cpython-311-aarch64-linux-gnu.so'
adding 'pyrf24/rf24.pyi'
adding 'pyrf24/rf24_mesh.cpython-311-aarch64-linux-gnu.so'
adding 'pyrf24/rf24_mesh.pyi'
adding 'pyrf24/rf24_network.cpython-311-aarch64-linux-gnu.so'
adding 'pyrf24/rf24_network.pyi'
adding 'pyrf24-0.0.0.dist-info/LICENSE'
adding 'pyrf24-0.0.0.dist-info/METADATA'
adding 'pyrf24-0.0.0.dist-info/WHEEL'
adding 'pyrf24-0.0.0.dist-info/top_level.txt'
adding 'pyrf24-0.0.0.dist-info/RECORD'
removing build/bdist.linux-aarch64/wheel
error: externally-managed-environment

This environment is externally managed

To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.

If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.

For more information visit http://rptl.io/venv

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

*** Installer Complete ***
See http://tmrh20.github.io for documentation
See http://tmrh20.blogspot.com for info

Listing repositories in ~/rf24libs
env pyRF24 RF24 RF24Gateway RF24Mesh RF24Network

Thanks.

Brendan · Answer 18 · Tue Dec 26 2023 20:12:35 GMT+0800 (China Standard Time)

This environment is externally managed

Again, that entire complaint is a user problem. Our install script should not manage a python venv. It is better to run the install script in an activated python venv (which would silence that warning).