3 ms·
You include the target glibc as part of your toolchain And, I always prefer to actually pick my glibc independently from the host os and ship it with the binar
by lokar 1y ago
You include the target glibc as part of your toolchain
And, I always prefer to actually pick my glibc independently from the host os and ship it with the binary (generally in an OCI image). This way you can patch/update the host without breaking the service.
- remexre 1y agoDoes that result in working NSS?
- lokar 1y agoI normally statically link as much as possible and avoid nss, but you can make that work as well, just include it along with glibc.
- jmmv 1y agoRight, so you need to end up creating a container to package the glibc with the binary. Which is not very different from having sysroots. But what about any tools compiled from source and used during the build? Those can also suffer from these issues.
- lokar 1y agoYeah, ideally you could build your toolchain from source on any platform. But, in some cases that’s not possible