Closed jonawald closed 11 months ago
It's likely not an issue with KIAUH. If you have any issues when following third party instructions, please contact the creator of those instructions for support. KIAUH is tested and reported to work on Debian Buster, though, that does not include Debian Buster installs running in Android Smartphones.
For the sake of documentation, the problem seems to be caused by non default installation of those libraries. In my case I managed to fix it by finding where they were installed and then linking those files to the "standard" library path.
Use find / -name libz.so 2>/dev/null
to find where the libraries were installed. The 2>/dev/null
is there to filter the "permission denied" errors. In my case they were located in /usr/lib/arm-linux-gnueabihf/
.
Place the libraries somewhere they are being searched, like so: sudo ln -s /usr/lib/arm-linux-gnueabihf/libz.* /usr/lib/
.
Now Pillow should build without issues, but in case you find additional errors, you can try some things listed in the official docs, like installing the dependencies and setting CFLAGS
to the directory your libz.so
is currently at. After this you'll most likely going to have the same error for libjpeg.so
, so just do the same for it.
Link to the docs: https://pillow.readthedocs.io/en/latest/installation/building-from-source.html#building-from-source
Linux Distribution
Debian Buster running on Moto G7 Play phone
What happened
note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for pillow Running setup.py clean for pillow Failed to build pillow ERROR: Could not build wheels for pillow, which is required to install pyproject.toml-based projects
What did you expect to happen
Moonraker did not install failed with the above error. I have done this several times. It always consistently fails at this junction.
How to reproduce
Install Klipper on Moto G7 Play phone using Debian Buster. Follow the instructions here . When using Kiauh to install moonraker I get this error.
Additional information
No response