<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>As many of you know, the <span style="orphans: 2; white-space: pre-wrap; widows: 2;">Rust compiler is self-hosting, so Rust is required to build Rust.</span></div><div>The problem is that the Rust binaries provided by upstream only work on macOS 10.9 and above.</div><div><br></div><div>To get around this, there is a rust-bootstrap port that build Rust binaries on 10.9+ intended to build Rust on previous macOS version.</div><div>Currently, these binaries are stored on using my personal GitHub account.</div><div><br></div><div>So the entire upgrade process is essentially:</div><div>1) Update the version in rust-bootstrap.</div><div>2) Build Rust binaries on a 10.9 VM.</div><div>3) Upload Rust binaries to GitHub account.</div><div>4) On older machines, use MacPorts Rust binaries to build Rust.</div><div> On newer machines, us the upstream provides binaries to build Rust.</div><div><br></div><div>This is far from ideal, but it has allowed us to get Rust working back to 10.5 (both i386 and x86_64).</div><div><br></div><div>This entire procedure may be modified, and there are a few suggestions on the mailing list</div><div>(<a href="https://lists.macports.org/pipermail/macports-dev/2022-December/thread.html#44855">https://lists.macports.org/pipermail/macports-dev/2022-December/thread.html#44855</a>).</div><div><br></div><div>However, until consensus is reached about major changes, it would be nice to make some incremental improvements.</div><div><br></div><div>The easiest change: does anyone know of a better place to store the MacPorts generated binaries?</div><div><br></div><div>More challenging: can anyone think of a way to automate the process of building the MacPorts Rust binaries after rust-bootstrap is update?</div><div><br></div><div>-Marcus</div></body></html>