8 ms·
I wonder if this can, in the future, provide yet another alternative to building binaries with statically linked musl libc. People criticise doing that, often d
by GolDDranks 5y ago
I wonder if this can, in the future, provide yet another alternative to building binaries with statically linked musl libc. People criticise doing that, often deservedly so, but having had to build stuff inside containers with deliberately old libc just to get the binary to run on another, older system, I find joy in having a binary that I know to run in "every $HW_ARCH Linux userland". (Of course, even then, calling newer Linux syscalls brings upon some version limitations...)
- BiteCode_dev 5y agoI wish to compile python from source in a way that will work in every $HW_ARCH Linux userland. What are your advices? What does your setup look like? I'm really inexperienced with compiling software, but I'm playing with the idea of automating the creation of stand alone python distributions every time one is release to have a repo of it. It looks full of gotchas though, espacially when you need to deal with ssl and tkinter.
- kkirsche 5y agoI don’t know it’s current status but either PyOxidizer or Nuitka are the two Python compilers I’d look to for that. It is full of trade offs, but to an extent that’s many dynamic languages like Python (said as a Python developer) https://nuitka.net https://nuitka.net https://github.com/indygreg/PyOxidizer https://github.com/indygreg/PyOxidizer
- BiteCode_dev 5y agoI already can compile python using "make altinstall", nuitka is more suited to compile a whole python project. The problem is more, as you said, libc, for compat.
- GoblinSlayer 5y agoYou can just extract that old libc.a and link against it. It's one file.