-
Notifications
You must be signed in to change notification settings - Fork 389
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
GCC and GLIBC supported minimums for Dune on Linux #10423
Comments
I agree with you that an official policy for this is important to have, and we're working on that at the moment. I think that the answer is going to be a variant of 1. |
(and I realize that this is not the crux of the issue, but this particular gcc fix is going to be fixed in 3.16.0 and 3.15.1, the latter this week or next one) |
Expected Behavior
TLDR: My expectation is that Dune works on the same platforms that OCaml works on.
In my case the offending GCC is:
Yes, that is a GCC from RHEL/CentOS 7 but that doesn't change the fact that OCaml builds perfectly fine on it while the conventional OCaml build tool (Dune) does not.
I'd like to know what the expectations are for Dune. While I could "fix" the issue below by upstreaming a patch to the vendored
spawn
library, doing so completely misses the point that it will be a tremendous waste of time for me to use Dune as a foundation to build OCaml software if someone (ex. Dune or thespawn
owner Jane Street) arbitrarily decides in the future that they won't support what OCaml supports. I don't think anyone should be in that position. It would be better for me to know now so I have time to course correct.Ideally, I'm expecting to see one of the following:
If "1" or "2", I'd be happy to submit an upstream patch. If "3" I can start planning to rely less on Dune. Thx.
Actual Behavior
Specifications
dune
(output ofdune --version
): 3.15.0ocaml
(output ofocamlc --version
): 4.14.2The text was updated successfully, but these errors were encountered: