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.
I should say Go doesn't work when an arch:any (usually a C library) is involved. But well most Go programs are pure Go which are not affected by this all-any trap.
(Sent from my mobile device)