pub fn musl_loader(target: TargetTuple) -> &'static strExpand description
The absolute path musl’s loader is installed at on the target.
It goes in the program header of a dynamically linked binary, so it is a string about the target machine’s filesystem and not about ours, and it has to be right without anything to check it against at link time. A wrong one produces a binary that the kernel refuses to start with a message about a missing file that is on nobody’s disk.
32-bit ARM is the row with two answers, because musl names the hard float and soft float builds differently and they are not interchangeable. PowerPC is the other row with two, and there the endianness picks, because musl treats the two byte orders as separate ports.