Re: rust-*/librust-* arch:any vs. arch:all and cross-compilation support
However, adding a question to the mix, why does arch all work for go
Do they not care about cross compilation, or are concerns somehow
Go doesn't work. I guess we started from the common sense that arch-indepent files should be arch:all. Or at that time Multi-Arch is not widely recognized.
(There is also a cross compile related patch in golang-defaults that haven't been merged yet for some years.)
(Sent from my mobile device)