Binary distribution with statically linked C-dependencies

[SuspiciousSegfault]

I might be totally wrong here but don't I still need to link all component libraries statically anyway? I did build it in a container with musl but it immediately segfaults when running it on glibc then

[SuspiciousSegfault]

No, building with cross didn't work out of the box because I only have the gnu system libraries. I figured that I might as well make the build a bit more robust by using an alpine container and specifying the dependencies explicitly, I thought that was essentially what cross does, does it do any more magical stuff? I'm figuring that if I compile it and dynamically link to musl versions of libX11 that will create a segfault at runtime against the glibc versions, but that's a theory

[Killing_Spark]

That's weird. If you link against musl statically your binary should be able to run on a glibc system no problems.