Reiner Herrmann dixit:
>Enabling M-A:foreign for musl-tools is unfortunately currently not
>possible. It's not arch:all, as it ships a few arch-dependent files.
That’s true for other packages as well.
A package can, generally, be made Multi-Arch: foreign, if it, and
all of its dependencies, can be used on a foreign system which has
the capability to execute its code (e.g. i386 on an amd64 system,
or anything with qemu-user-static).
>E.g. the spec file, /usr/bin/musl-gcc (which hardcodes the arch-dependent
>path to the spec file), and /usr/bin/musl-ldd, which is a symlink to
>libc.so.
Yes, but that’d be deliberate. Installing a foreign-architecture
musl-tools would then enable one to cross-compile. At least that’s
the idea. I’m not completely sure it’s the right way or even a good
way, or whether it’ll break $things, which is why I added the two
“cross” guys in Cc.
bye,
//mirabilos
--
11:56⎜«liwakura:#!/bin/mksh» also, i wanted to add mksh to my own distro │
i was disappointed that there is no makefile │ but somehow the Build.sh is
the least painful built system i've ever seen │ honours CC, {CPP,C,LD}FLAGS
properly │ looks cleary like done by someone who knows what they are doing
