4 ms·

I think so - Julia master branch (1.7 precursor) works on M1, but not all the dependencies that some packages require have been built for M1. Though, I understa

I think so - Julia master branch (1.7 precursor) works on M1, but not all the dependencies that some packages require have been built for M1. Though, I understand that the wonderful packaging system and the folks who work on it are working on it. > `git clone https://github.com/JuliaLang/julia https://github.com/JuliaLang/julia` and `make` should be enough at this point. https://github.com/JuliaLang/julia/issues/36617#issuecomment-791110407 https://github.com/JuliaLang/julia/issues/36617#issuecomment...

xiphias2 6y ago
Cool, I'll start with 1.6, but it looks interesting of course :)
staticfloat 6y ago
Yeah, we've managed to get Julia itself running pretty well on the M1, there are still a few outstanding issues such as backtraces not being as high-quality as on other platforms. You can see the overall tracking issue [0] for a more granular status on the platform support. For the package ecosystem as a whole, we will be slowly increasing the number of third-party packages that are built for aarch64-darwin, but this is a major undertaking, so I don't expect it to be truly "finished" for 3-6 months. This is due to both technical issues (packages may not build cleanly on aarch64-darwin and may need some patching/updating especially since some of our compilers like gfortran are prerelease testing builds, building for aarch64-darwin means that the packages must be marked as compatible with Julia 1.6+ only--due to a limitation in Julia 1.5-, etc...) as well as practical (Our packaging team is primarily volunteers and they only have so much bandwidth to help fix compilation issues). [0] https://github.com/JuliaLang/julia/issues/36617 https://github.com/JuliaLang/julia/issues/36617
- xiphias2 6y ago
  That's great, releasing something that isn't yet ready doesn't make sense. But when it works, it's important enough to warrant a release :)

xiphias2 6y ago

Cool, I'll start with 1.6, but it looks interesting of course :)

staticfloat 6y ago

Yeah, we've managed to get Julia itself running pretty well on the M1, there are still a few outstanding issues such as backtraces not being as high-quality as on other platforms. You can see the overall tracking issue [0] for a more granular status on the platform support. For the package ecosystem as a whole, we will be slowly increasing the number of third-party packages that are built for aarch64-darwin, but this is a major undertaking, so I don't expect it to be truly "finished" for 3-6 months. This is due to both technical issues (packages may not build cleanly on aarch64-darwin and may need some patching/updating especially since some of our compilers like gfortran are prerelease testing builds, building for aarch64-darwin means that the packages must be marked as compatible with Julia 1.6+ only--due to a limitation in Julia 1.5-, etc...) as well as practical (Our packaging team is primarily volunteers and they only have so much bandwidth to help fix compilation issues). [0] https://github.com/JuliaLang/julia/issues/36617 https://github.com/JuliaLang/julia/issues/36617

xiphias2 6y ago
That's great, releasing something that isn't yet ready doesn't make sense. But when it works, it's important enough to warrant a release :)