Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

barracuda156

macrumors 68040
Original poster
Sep 3, 2021
3,505
2,033
rust.png
 
Really incredible! Will test on Tiger once it is ready for the main tree.

The issue is that mrustc itself and rustc for it are in a single port, and while mrustc is functional, FWIW, rustc fails to build, on all archs (I tried x86_64 and arm64) and with different errors, which is annoying, to say the least LOL
And I am hesitant to commit a half-fixed port.

I will probably try to fix 1.54 for LLVM-7, because if that works, we know for sure that at least on x86 bootstrapping worked fine. While re 1.39 I am not sure it ever worked for anyone at all (not in MacPorts, but whether upstream tested it on macOS and in what set-up).
 
  • Like
Reactions: Forest Expertise
BTW, if we have someone here who knows Rust and its build process on some common platform, please get in touch, since what I am currently having the most problem with are issue unrelated to powerpc as such.
 
The issue is that mrustc itself and rustc for it are in a single port, and while mrustc is functional, FWIW, rustc fails to build, on all archs (I tried x86_64 and arm64) and with different errors, which is annoying, to say the least LOL
And I am hesitant to commit a half-fixed port.

I will probably try to fix 1.54 for LLVM-7, because if that works, we know for sure that at least on x86 bootstrapping worked fine. While re 1.39 I am not sure it ever worked for anyone at all (not in MacPorts, but whether upstream tested it on macOS and in what set-up).
Quite reasonable. I also suspect 1.54 will allow a lot more software in Rust to work. I am glad llvm-powerpc is now fixed for Tiger, so whenever mrustc and rustc are ready for the main tree, Tiger is ready for them.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.