Announcement: Macos nightlies no longer contain a version number, backwards compatibility seems to be working, so for x86_64, nightlies are generated on macos 11 and for apple silicon they are generated on macos 12. Trying to use zig 0.9.1 on macos 13 still does not work though, so zig platforms can't be used.
Hi, just downloaded the apple silicon nightly on MacOS 13, but I can't get it to work – even with platforms other than Zig. Here's what I get for ./roc examples/platform-switching/rocLovesRust.roc
:
🔨 Rebuilding platform...
An internal compiler expectation was broken.
This is definitely a compiler bug.
Please file an issue here: https://github.com/roc-lang/roc/issues/new/choose
thread '<unnamed>' panicked at 'Error:
Failed to rebuild src/lib.rs:
The executed command was:
cargo build --lib
stderr of that command:
error: failed to load manifest for dependency `roc_std`
Caused by:
failed to parse manifest at `/Users/nikitamounier/Desktop/roc_nightly-macos_apple_silicon-2022-12-09-234f9f5/crates/roc_std/Cargo.toml`
Caused by:
namespaced features with the `dep:` prefix are only allowed on the nightly channel and requires the `-Z namespaced-features` flag on the command-line
', crates/compiler/build/src/link.rs:1597:21
Here's the rust backtrace if that's helpful:
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: roc_build::link::run_build_command
3: roc_build::link::rebuild_host
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at 'Failed to (re)build platform.: Any { .. }', crates/cli/src/build.rs:342:46
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: roc_cli::build::build_file
4: roc_cli::build
5: roc::main
what is your rust version?
it looks like it might be outdated?
We are on rust 1.64.0, I'll add a rust-toolchain file to the example to prevent this in the future.
I had this error, then fixed it with rustup update 1.64
, but found another error which required updating my xcode command line tools (in case someone else runs into the same problem)
Nice that it works :)
Do you still have the error message that required updating xcode? I'd like to save it in an issue so that it is easier to discover.
I don't, sorry! Updating xcode was a big endeavor with as little free space as I have left :sweat_smile:
All good, xcode is indeed ridiculously large
Last updated: Jul 06 2025 at 12:14 UTC