I’ve installed the DkML distribution. Trying to install platform tools (typing
opam install ocaml-lsp-server odoc ocamlformat utop), however I first get the following:
[WARNING] Detected that the system native code OCaml compiler is not present. Creating it now. ETA: 15 minutes.
Then some installation takes place, and finally I get the following error:
Alternatively, if you have the time, could you consider trying out the newer Windows installation “opam 2.2” instead? That would be:
Open Add or remove programs from Windows Search (type Windows key and then start typing “Add or remove programs”), and then uninstall DkML Native; you can ignore any failures. You can now close “Add or remove programs”.
Open PowerShell and run the following:
if (Test-Path "$env:LOCALAPPDATA\opam") { del -force - recurse "$env:LOCALAPPDATA\opam" }
Hello, I’ve installed Utop on wsl (and I am still unable to code in OCaml on VSCode) but since I’ve uninstalled everything related to DkML Distribution I don’t have OCaml on Windows…
For a WSL installation, it sounds like you need to setup your editor to play together the subsystem. It would be helpful if you share a more descriptive error message though.
For a native Windows installation, have you tried running the suggested command in a PowerShell after uninstalling the DkML distribution?
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Looks like your Internet traffic is being intercepted or interrupted, or your machine has its own SSL certificates, and that has nothing to do with OCaml.
Could be a MITM proxy (a corporate proxy or a device on your home network) or any overly aggressive anti-malware tool (MacAfee, “web shields”, etc.). There is very little anyone will be able to do for you in this forum if these network failures are repeatable (and it sounds like it is). At best, try disabling your anti-malware/anti-virus before you run opam init --reinit -ni. But I’m not optimistic that will work.