In https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea04a1d2939affe00cea7dbf57dbbede5c1c6481 these packages were masked: dev-lang/rust-bin dev-lang/rust virtual/rust Only dev-lang/rust-bin should be masked. dev-lang/rust and virtual/rust should not be masked; users can still build rust from source for these architectures. Reproducible: Always
prove me wrong, but this mask has been added because there is no rustc stage for armv4/5, and that means no rust-bin but also no dev-lang/rust because there's nothing to bootstrap from in the first place! rust-std is available for armv4/5, so users are able to cross compile binaries if they want to from other and more powerfull devices.
(In reply to tt_1 from comment #1) > prove me wrong, but this mask has been added because there is no rustc stage > for armv4/5, and that means no rust-bin but also no dev-lang/rust because > there's nothing to bootstrap from in the first place! > > rust-std is available for armv4/5, so users are able to cross compile > binaries if they want to from other and more powerfull devices. That's exactly it. Let's see what gyakovlev says but we essentially discussed this the other day and the conclusion was there's no point in unmasking (nor would it preserve the integrity of the depgraph) because we can't satisfy virtual/rust on armv4/5. What we do instead is mask Rust-dependent packages on those earlier arm architectures, while making it available for >= armv6j.
yeah it's kinda possible to cross-build rust on those arches now (patches needed and work in progress, but getting close). but bootstrap problem still stands, like described above. There's no rust-bin/upstream tarball for those arm subarches, hence not possible to emerge rust. the only possibility is to cross-emerge rust from somewhere else. it does not work by default and that's why it's masked.