* Elliott Sales de Andrade:
On Mon, 10 Jun 2019 at 16:46, Tom Callaway
> Reviving this. I do not have the time nor the energy to attempt to keep this going,
so I am going to disable the shared bits in cross-gcc and kill off glibc-arm-linux-gnu.
It's been broken for a while, so I doubt anyone will be seriously impacted by this.
Ah that's unfortunate. I've been working on something that could
possibly make use of this, but I haven't quite reached the stage of
testing this out with it, and since it wasn't in Rawhide, I hadn't
taken much look into it.
I see that Debian has pretty much every cross version of libc6:
What makes it so easy for them? / What makes it difficult for us? How
can we make cross toolchains easier?
They just did the work, like Fedora did for Windows.
The benefits that GNU/Linux cross-toolchains provide to Debian is
greater than it would be on Fedora because most of Debian's development
packages install header files and libraries into directories with
multi-arch tuples, and dpkg supports installation of such packages from
foreign architectures, using their package repositories. This means
that the Debian cross-toolchain can use all these development packages,
and Debian developers are not stuck with glibc/libstdc++ only for