I ran into the same reported issue attempting to cross-compile to aarch64 with musl.
The proposed solution seems reasonable to me: - Move the specs file to musl-dev - Move the musl-gcc wrapper to musl-dev, name it with a target prefix (aarch64-linux-musl-gcc), and have it call the corresponding cross-gcc (aarch64-linux-gnu-gcc). - Have musl-tools just ship musl-gcc as a symlink to the musl-dev wrapper for the native architecture. Do the musl maintainers consider this a reasonable solution?
