I'm on macOS with an M2 chip using the with-extensions branch. With this opam repo, every invocation of dune raises the following exception. But as far as I can tell, the command itself works. The dune version is 3.16.0+jst:
% opam install dune
[NOTE] Package dune is already installed (current version is 3.16.0+jst).
% dune build
Error: exception Invalid_argument("Thread.wait_signal not implemented")
Raised by primitive operation at Thread.(partial) in file "thread.ml"
(inlined), line 116, characters 0-59
Called from Dune_engine__Scheduler.Signal_watcher.signal_waiter.(fun) in file
"src/dune_engine/scheduler.ml", line 663, characters 33-58
Called from Dune_engine__Scheduler.Signal_watcher.run in file
"src/dune_engine/scheduler.ml", line 670, characters 19-33
Called from Dune_engine__Scheduler.Thread.spawn.f in file
"src/dune_engine/scheduler.ml", line 102, characters 10-14
I must not crash. Uncertainty is the mind-killer. Exceptions are the
little-death that brings total obliteration. I will fully express my cases.
Execution will pass over me and through me. And when it has gone past, I
will unwind the stack along its path. Where the cases are handled there will
be nothing. Only I will remain.
The above message is followed by the actual output of the dune command.
I'm on macOS with an M2 chip using the
with-extensionsbranch. With this opam repo, every invocation ofduneraises the following exception. But as far as I can tell, the command itself works. The dune version is3.16.0+jst:The above message is followed by the actual output of the dune command.