This adds support for using system-bootstrap to build Rust for the
armv5tel profile.  It does not add binary bootstrap compilers.

Signed-off-by: David Michael <>


I have an ARM9 chip that I'd like to be able to target for Rust
packages.  Things are getting masked in the armv5tel profile due to it
not having Rust binaries.  Can we start fixing this?

I've bootstrapped armv5te Rust by cross-compiling it, and it seems to
work.  I can send my ebuild changes if anyone wants to build their own
armv5te compiler, but the eclass should at least define its default
builtin target so that it can be built with USE=system-bootstrap.



 eclass/rust-toolchain.eclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/eclass/rust-toolchain.eclass b/eclass/rust-toolchain.eclass
index 9d7360ed1c4..9ae4ad93945 100644
--- a/eclass/rust-toolchain.eclass
+++ b/eclass/rust-toolchain.eclass
@@ -41,6 +41,7 @@ rust_abi() {
                powerpc64*)   echo powerpc64-unknown-linux-gnu;;
                x86_64*gnu)       echo x86_64-unknown-linux-gnu;;
                x86_64*musl)  echo x86_64-unknown-linux-musl;;
+               armv5te*)         echo armv5te-unknown-linux-gnueabi;;
                armv6j*s*)        echo arm-unknown-linux-gnueabi;;
                armv6j*h*)        echo arm-unknown-linux-gnueabihf;;
                armv7a*h*)        echo armv7-unknown-linux-gnueabihf;;

Reply via email to