Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Failure "Windows only. This function isn't implemented." #122

Open
mlasson opened this issue Nov 17, 2020 · 5 comments
Open

Failure "Windows only. This function isn't implemented." #122

mlasson opened this issue Nov 17, 2020 · 5 comments
Labels
bug Something isn't working upstream Fix has to be implemented upstream

Comments

@mlasson
Copy link

mlasson commented Nov 17, 2020

Hello !

I used to be able to use duniverse to build ocaml-lsp on windows without opam nor ocamlfind, and it worked like a charm !

But since the upgrade to "opam core 2.1" (commit f133ee6)
the executable is throwing an uncaught failure exception:

opam-monorepo: internal error, uncaught exception:
               (Failure "Windows only. This function isn't implemented.")
               Raised at file "stdlib.ml", line 29, characters 17-33
               Called from file "duniverse/opam-core.2.1.0-beta/src/core/opamStubs.ml.dummy" (inlined), line 13, characters 23-80
               Called from file "duniverse/opam-core.2.1.0-beta/src/core/opamStd.ml", line 800, characters 36-66
               Called from file "duniverse/opam-core.2.1.0-beta/src/core/opamStd.ml" (inlined), line 1268, characters 44-71
               Called from file "duniverse/opam-core.2.1.0-beta/src/core/opamConsole.ml", line 585, characters 41-76
               Called from file "duniverse/opam-core.2.1.0-beta/src/state/opamFormatUpgrade.ml", line 1128, characters 4-401
               Called from file "duniverse/opam-core.2.1.0-beta/src/state/opamGlobalState.ml", line 62, characters 15-43
               Called from file "duniverse/opam-core.2.1.0-beta/src/state/opamGlobalState.ml", line 169, characters 11-20
               Called from file "cli/lock.ml", line 109, characters 2-57
               Called from file "duniverse/cmdliner.1.0.4+dune/src/cmdliner_term.ml", line 25, characters 19-24
               Called from file "duniverse/cmdliner.1.0.4+dune/src/cmdliner.ml", line 33, characters 27-34
               Called from file "duniverse/cmdliner.1.0.4+dune/src/cmdliner.ml", line 117, characters 32-39

I guess there must be a "configure step" required to be able to compile opam-core on windows to avoid the selection of the dummy implementation of these stubs.

What am I missing ?

@NathanReb
Copy link
Contributor

Thanks for reporting this!

That's unfortunate indeed, I'll investigate and report to opam maintainers, we might need a proper dune port in the meantime!

@emillon
Copy link
Collaborator

emillon commented Jul 12, 2021

This is tracked on the opam side as ocaml/opam#4726

@dra27
Copy link
Member

dra27 commented Jul 29, 2021

Tentative fix in ocaml/opam#4777

@tmattio tmattio added bug Something isn't working upstream Fix has to be implemented upstream labels Jan 10, 2023
@tmattio
Copy link
Contributor

tmattio commented Jan 10, 2023

@dra27 is the above PR still relevant?

@dra27
Copy link
Member

dra27 commented Jan 10, 2023

Yes (🙂)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working upstream Fix has to be implemented upstream
Projects
None yet
Development

No branches or pull requests

5 participants