cross-toolchains VS cargo-bisect-rustc

Looks like cross is the easiest way to get something cross-compiled but its Mac support is blocked behind building your own build image. Even that repo says that it might be broken.

Your target is not directly supported (licensing issues I presume), but there seems to be a way to create your own image and then use it. It's worth a try.

A lot of work has been spent making the process as painless as possible. A crosstool-ng image is slightly more complex, but still quite easy: you just need a valid config file. The basic logic can be found here, and cross-toolchains has a few more examples.

> One big downside is losing the ability to build any commit from source without meta-complexity creeping in. For example, let’s say that you are trying to do git bisect. At some point, git checks out an older commit, but the script fails to build from source because the binary that is being used to build the compiler is now the wrong version. Sure, this can be addressed, but this introduces unwanted complexity that contributors would rather not deal with.

If it's the main concern of using a prior build of the compiler, an alternative solution is to develop a tool for contributors to automate and ease the process. For example, Rust has this: https://github.com/rust-lang/cargo-bisect-rustc

Added support for tools like cargo-bisect-rustc.

Finally, https://github.com/rust-lang/cargo-bisect-rustc/blob/master/TUTORIAL.md can bisect Nightlies or (if recent enough, I think CI artifacts are kept 3 months) PRs to tell you one introduced a problem.