You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
opam-monorepo: [ERROR] Some dependencies cannot be built with dune!
opam-monorepo requires that all dependencies use dune as their build system.
These dependencies (possibly transitive) don't use dune as their build system:
- ocaml-compiler
Now, I understand there's been some shuffling around with opam package names and ocaml 5.3 - but I'm a bit stuck what opam-monorepo intends to do here. Would it be possible to fix that?
The text was updated successfully, but these errors were encountered:
hannesm
changed the title
Trying with Mirage, and llikely with the newly released ocaml-solo5 (1.0.0) supporting OCaml 5.x
Trying with Mirage, and llikely with the newly released ocaml-solo5 (1.0.0) supporting OCaml 5.x -- and OCaml 5.3 being released
Jan 19, 2025
This has as well been reported on discord on the mirage channel. Would any of those knowing more details of opam-monorepo be able to take a look into how to deal with OCaml 5.3? Thanks a lot!
Please have a look in #407. It would be great to get that merged and released ASAP. Of course any "better" fix is very welcome.
The issue I ran into (and @PizieDust as well) is that albatross has specified a bound on ptime >= 1.2.0, which is not available in the dune-opam-overlays repository. But the ocaml-compiler issue shadowed the underlying issue.
Now, of course it would be great if you could as well put the ptime 1.2.0 package into the dune-opam-overlays repository. In the meantime, I as well opened ocaml/opam-repository#27417 as a workaround.
It would also be nice if your code would print not only the first error, but as well other errors if there are some.
In a
make lock
, I get the following error:Now, I understand there's been some shuffling around with opam package names and ocaml 5.3 - but I'm a bit stuck what opam-monorepo intends to do here. Would it be possible to fix that?
The text was updated successfully, but these errors were encountered: