The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
1–10 of 215 posts
Re: The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
#2Re: The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
#3This seems interesting even regardless of go. Is it realistic to create an executable which would work on very different kinds of Linux distros? e.g. 32-bit and 64-bit? Or maybe some general framework/library for building an arbitrary program at least for "any libc"?
Re: The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
#4This seems interesting even regardless of go. Is it realistic to create an executable which would work on very different kinds of Linux distros? e.g. 32-bit and 64-bit? Or maybe some general framework/library for building an arbitrary program at least for "any libc"?
Re: The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
#5Re: The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
#6This seems interesting even regardless of go. Is it realistic to create an executable which would work on very different kinds of Linux distros? e.g. 32-bit and 64-bit? Or maybe some general framework/library for building an arbitrary program at least for "any libc"?
Cosmopolitan goes one further: [binaries] that runs natively on Linux + Mac + Windows + FreeBSD + OpenBSD + NetBSD + BIOS on AMD64 and ARM64 https://justine.lol/cosmopolitan/
if you configure binfmt_misc
>Windows
if you disable Windows Defender
>OpenBSD
only older versions
Re: The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
#7Is there a tool that takes an executable, collects all the required .so files and produces either a static executable, or a package that runs everywhere?
But you can't take .so files and make one "static" binary out of them.
Re: The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
#8Is there a tool that takes an executable, collects all the required .so files and produces either a static executable, or a package that runs everywhere?