Hello everyone! For the first time, I tried to build the compiler. I cloned the repository, ran nix develop
, then cargo run help
.
The cargo build seems to fail with
error[E0432]: unresolved import `crate::expr::AccessorData`
--> crates/compiler/can/src/def.rs:14:5
|
14 | use crate::expr::AccessorData;
| ^^^^^^^^^^^^^^^^^^^^^^^^^ no `AccessorData` in `expr`
error[E0425]: cannot find function, tuple struct or tuple variant `Accessor` in this scope
--> crates/compiler/can/src/def.rs:2324:25
|
2324 | Accessor(AccessorData {
| ^^^^^^^^ not found in this scope
Compiling target-lexicon v0.12.4
Compiling strum_macros v0.24.3
Compiling crossbeam-epoch v0.9.9
Some errors have detailed explanations: E0425, E0432.
For more information about an error, try `rustc --explain E0425`.
error: could not compile `roc_can` due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
Hi @dank, there's a build failure on main because we have not found a good merge queue solution yet, it should be resolved soon.
In the meantime you can check out the branch fix-record-accessor
which contains the fix.
Anton said:
Hi dank, there's a build failure on main because we have not found a good merge queue solution yet, it should be resolved soon.
In the meantime you can check out the branchfix-record-accessor
which contains the fix.
thank you! Now that I've checked out the fix-record-accessor branch, build fails with a different error;
error: linking with `cc` failed: exit status: 1
|
...
= note: Terminated
collect2: error: ld returned 143 exit status
error: could not compile `roc_cli` due to previous error
perhaps you can help me with this error aswell?
thanks for the reply!
Hmm, I can't reproduce this error and I'm on NixOS as well. I assume this second error was thrown when using the command cargo run help
?
Anton said:
Hmm, I can't reproduce this error and I'm on NixOS as well. I assume this second error was thrown when using the command
cargo run help
?
yes
Are you on NixOS 22.11?
22.11.1705.b83e7f5a04a (Raccoon)
Quite the mystery :p can you do cargo clean
followed by cargo build --release
?
Can you share the output of the lscpu
command?
Anton said:
Quite the mystery :p can you do
cargo clean
followed bycargo build --release
?
wow that actually worked
Anton said:
Can you share the output of the
lscpu
command?
if you wanna see anyway it's here https://termbin.com/e14x
Great :) does cargo run help
work as well now?
let me see.. (slow computer)
yes that works aswell
weird that issue's just gone lol
but thanks a lot!!
Happy to help :)
Anton said:
Happy to help :)
Hey Anton, this is half related but- I want to start contributing to Roc . so now to PR it means I would need to checkout fix-record-accessor and then you guys cherry pick my commit from the new branch? like what's the workflow now with main being broken?
main is fixed again
so if you use latest main, you should be good
Folkert de Vries said:
so if you use latest main, you should be good
ahh great. thanks
Hey Anton, this is half related but- I want to start contributing to Roc .
@dank awesome :) feel free to post something to #contributing if you need help!
Last updated: Jul 06 2025 at 12:14 UTC