Re: Location to store Rust binaries

Thu, 22 Dec 2022 05:13:37 -0800

although the 10.9 one needed has not as yet been built it seems.

You would also have to manually access and download the 10.9 binary on older systems, as the automatic mechanism to install it wouldn’t work where it’s needed.

K

On Dec 22, 2022, at 05:02, Ken Cunningham <ken.cunningham.web...@gmail.com> wrote:


they are there


On Dec 22, 2022, at 01:30, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote:




On 22 Dec 2022, at 4:02 am, mcalh...@macports.org wrote:


As many of you know, the Rust compiler is self-hosting, so Rust is required to build Rust.
The problem is that the Rust binaries provided by upstream only work on macOS 10.9 and above.

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.
Currently, these binaries are stored on using my personal GitHub account.

So the entire upgrade process is essentially:
1) Update the version in rust-bootstrap.
2) Build Rust binaries on a 10.9 VM.
3) Upload Rust binaries to GitHub account.
4) On older machines, use MacPorts Rust binaries to build Rust.
    On newer machines, us the upstream provides binaries to build Rust.

This is far from ideal, but it has allowed us to get Rust working back to 10.5 (both i386 and x86_64).

This entire procedure may be modified, and there are a few suggestions on the mailing list

However, until consensus is reached about major changes, it would be nice to make some incremental improvements.

The easiest change: does anyone know of a better place to store the MacPorts generated binaries?

More challenging: can anyone think of a way to automate the process of building the MacPorts Rust binaries after rust-bootstrap is update?

I am sure I am missing something but if the bootstrap binaries are generated via a port, rust-bootstrap, why cannot the usual mechanism for distributing the port as a binary not be used ?

Chris


-Marcus

Reply via email to