Etienne Marais
Etienne Marais
I agree with @Leonidas-from-XIV: in the "real build instruction" we write to files (many times it's just a call to `dune build`). Also, relying on `INSIDE_DUNE` would not reflect the...
> Let me clarify what I meant; there are some packages where configure outputs things like paths to stdout. We also have tests that mimic that with echo %{lib}%, those...
After an offline discussion with @emillon, I agree with his suggestion of adding a flag for printing the output when present, `--debug-package-logs`. This way, it provides access to the output...
@emillon @Leonidas-from-XIV I updated the tests and rebase on master. If that's good for you, it should be possible to merge it :+1:
Possible solution mentioned during the Dune dev meeting here: https://github.com/ocaml/dune/issues/8652
> Any updates? We are still discussing on the way to solve the problem. Today, it seems to require a lot of changes to fix it, and we want to...
On @gridbugs and my computer, the produced binary works as expected: - No need to add some flags to get the compiler installed (no error about Ocaml when doing the...
I have rebased and cleaned the history. If the tests pass, I think it's ok to merge it :+1:
@gridbugs @emillon, I don't have the merge right: can I gently ask one of you to do the merge? :)
Considering it is a problem from the compiler, should we close this issue?