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
ocaml 4.06.0 #20239
ocaml 4.06.0 #20239
Conversation
cc @ilovezfs |
|
1703239
to
09e9e8d
Compare
This will fix OPAM: #20251 |
This fixes the coccinelle test: 5063c2c |
This will fix lablgtk: #20252 |
This will fix ocamlsdl: #20253 |
🍏 but it seems to break a lot of the things with a build-time-only dependency so we may need to do some more surgery before merging. |
This gets |
|
🍪 |
Eh... @ilovezfs FWIW, ocaml 4.06.0 wreaks havoc when attempting to build haxe from source. To build haxe: This works fine on older ocaml versions, but 4.06.0 fails to install various libraries during the This fixes most of the problems:
However, At that point haxe compiles successfully. You can reproduce the issue:
Hope this helps! |
Nah, it's horrible. I don't know ocaml at all, so I did the bare minimum hack to get it to compile: let rec update x f = function
Empty ->
begin match f None with
| None -> Empty
| Some data -> add x data empty
end
| Leaf (k,j) as t -> t
| Branch (p,m,t0,t1) as t -> t If you put that into ptmap.ml, it compiles and all the tests pass. But that update function is obviously bogus. It doesn't actually update anything. The compile error was due to the fact that ptmap.ml has no That only works because apparently nothing calls Good enough for me :P I'm out of time, so someone else will have to carry this from here. |
CC @andyli have you hit the above issue yet? |
ah, I see.. 7f64c31 you changed haxe's brew formula to set Makes sense. It might be good to add that |
@shawwn well really it needs to be fixed so that it works with safe-string on :) |
good luck! :) You'll have to submit patches to 3 or 4 opam repos. e.g. |
@shawwn yeah the whole ecosystem is going to take time to catch up. |
It's unfortunate that this got merged so quickly. We're working hard on getting opam-repository to be compliant with safe-string, but it does take a few weeks to work through all the libraries. In the meanwhile, upgrading to 4.06.0 does break users as a result. |
@avsm we merge stable versions of each package as soon as they're green for our CI. |
@avsm my suggestion would be that you ship an opam version 1.2.3 that sets |
Created with
brew bump-formula-pr
.