libc6-*-cross, etc
Hello,
as a happy user of gcc-4.9-aarch64-linux-gnu (and several others), I was
glad to notice the new gcc-5-aarch64-linux-gnu and decided to install it,
but I was surprised to notice that it depends on many *-arm64-cross
packages. I already have the regular multiarch :arm64 version of those
packages installed, and that was good enough for
gcc-4.9-aarch64-linux-gnu.
I tried to find an explanation for this change, I assume there are good
reasons for it, but all I found was this email:
https://lists.debian.org/debian-cross/2015/03/msg00001.html
which tells me nothing about *why* this happened. Could someone point me
to the relevant discussion?
Currently, it doesn't make sense to me. I am using multi-arch and
qemu-user-binfmt to test software for various architectures with minimal
hassle. libc6:arm64 will always be needed by the other dependencies I have
(say libmpfr-dev:arm64 for instance) and I don't see why I should install
a second copy in a strange location. The *-cross packages look like a step
backwards, saying that multiarch was a bad idea that we should abandon; is
that the case? Would it be possible to present it as an alternative, so
the *-cross packages are only installed for people who refuse to run 'dpkg
--add-architecture' or for architectures that we cannot multiarch (ld.so
conflict)?
--
Marc Glisse
Reply to: