Open dante-signal31 opened 2 years ago
The musl Linux Python distributions are compiled with clang using a musl-clang
executable. The reference to that compiler and its settings leaks into the Python distribution where it is picked up by Python build tools.
To fix this, you need a musl-clang
in your build environment. I'm not sure if this is something that Linux Mint has a package for.
This is definitely something that should be better documented in PyOxidizer's docs. Ideally we would provide a Docker image or otherwise make it easier to build Python extensions using the same compiler that the Python distributions do.
Thank you for your answer and for the effort to develop PyOxidizer.
Indeed, I've not found any package with musl-clang, so I guess it's something you have to compile from source. I've tried to google it but I haven't found a clear way to get that command up and running (I have to admit I'm not a C/C++ ninja).
If you find the time to document how to prepare your system to have that command it would be great. Until that I guess I'll have to use pyoxidizer without static compiling. :-)
I'm using PyOxidizer to build a binary for my project Cifra (at my "pyoxidizer" branch).
My pyoxidizer.bzl is at root folder, next to setup.py:
With that configuration I get a proper binary file with "pyoxidizer build".
However, problem arises when I try to build a fully statically linked binary. I've followed instructions page build static binaries. I've updated rust:
But when I build process ends with this error:
To make it work, I've installed musl, musl-dev an clang packages but error persists. I'm in a Linux Mint 20.2 (uma).
Is it a bug or am I doing something wrong?