-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bonsai no longer builds with dune package management #10473
Labels
Comments
gridbugs
added a commit
to gridbugs/dune
that referenced
this issue
May 1, 2024
In 3ea5444 the order of env updates performed by packages was reversed. This brought the behaviour of dune closer to opam but introduced a regression which prevents ocamlfind from building with dune package management. Here's an issue for tracking investigating why this change caused the regression: ocaml#10473 Signed-off-by: Stephen Sherratt <stephen@sherra.tt>
gridbugs
added a commit
to gridbugs/dune
that referenced
this issue
May 1, 2024
In 3ea5444 the order of env updates performed by packages was reversed. This brought the behaviour of dune closer to opam but introduced a regression which prevents ocamlfind from building with dune package management. Here's an issue for tracking investigating why this change caused the regression: ocaml#10473 Signed-off-by: Stephen Sherratt <stephen@sherra.tt>
gridbugs
added a commit
to gridbugs/dune
that referenced
this issue
May 1, 2024
In 3ea5444 the order of env updates performed by packages was reversed. This brought the behaviour of dune closer to opam but introduced a regression which prevents ocamlfind from building with dune package management. Here's an issue for tracking investigating why this change caused the regression: ocaml#10473 Signed-off-by: Stephen Sherratt <stephen@sherra.tt>
Complete shot in the dark, but maybe it has something to do with |
gridbugs
added a commit
to gridbugs/dune
that referenced
this issue
May 1, 2024
In 3ea5444 the order of env updates performed by packages was reversed. This brought the behaviour of dune closer to opam but introduced a regression which prevents ocamlfind from building with dune package management. Here's an issue for tracking investigating why this change caused the regression: ocaml#10473 Signed-off-by: Stephen Sherratt <stephen@sherra.tt>
gridbugs
added a commit
to gridbugs/dune
that referenced
this issue
May 2, 2024
In 3ea5444 the order of env updates performed by packages was reversed. This brought the behaviour of dune closer to opam but introduced a regression which prevents ocamlfind from building with dune package management. Here's an issue for tracking investigating why this change caused the regression: ocaml#10473 Signed-off-by: Stephen Sherratt <stephen@sherra.tt>
gridbugs
added a commit
that referenced
this issue
May 2, 2024
In 3ea5444 the order of env updates performed by packages was reversed. This brought the behaviour of dune closer to opam but introduced a regression which prevents ocamlfind from building with dune package management. Here's an issue for tracking investigating why this change caused the regression: #10473 Signed-off-by: Stephen Sherratt <stephen@sherra.tt>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's a regression resulting in the following error when using dune to build the dependencies of the package "bonsai" (which we've been using to evaluate dune package management):
The regression was introduced in 3ea5444
PR which changes back the offending line: #10474
I don't yet understand why that change caused the regression.
The text was updated successfully, but these errors were encountered: