-
Notifications
You must be signed in to change notification settings - Fork 393
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
bigarray compatibility library not linked #1845
Comments
@TheLortex has also been running into this as part of mirage/mirage#969 |
@nojb any idea? |
Hmm, testing this out a bit it seems like it's not an issue with dune. In 4.07, I get this in the REPL:
While in 4.08, I get:
|
Can you check if there is a |
I am guessing that ocaml/ocaml#2041 may be involved: as per the explanation in that PR the initial environment is now built as:
which would effectively hide any module in @diml ? |
@rgrinberg can you try doing |
There is.
That seems to fix things:
|
This is in fact a bug in the compiler. It is fixed in ocaml/ocaml#2256 |
After ocaml/ocaml#1685, projects requiring compatibility with OCaml < 4.06 that use the
Bigarray.*.map_file
functions need to link in thebigarray
library. However, this seems to be broken on OCaml 4.08 and Dune 1.7.0 (though I suspect it's not specific to this Dune version).Bigarray
seems to resolve to the stdlib instance rather than thebigarray
one, resulting inHere is a sample project reproducing the issue.
map_file
to any other function fromBigarray.Array1
makes compilation succeed, so an instance ofBigarray
is being linked.map_file
, demonstrating resolution).(libraries bigarray)
has no effect on the outcome.The text was updated successfully, but these errors were encountered: