-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Incorrect module name is passed to Persistent_env.acknowledge_pers_struct with -annot on OCaml 4.10 #9218
Comments
Note: on my machine (opam 2.0.4), |
oh I forgot to add the |
I don't know what the issue is, but I will try to reproduce locally. I think the easiest way to locate a compatibility issue is to bisect (one could start by checking #2228, which included a fair amount of code churn in this part of the compiler, as a potential culprit), and then work from the patch that provoked the failure. Note that |
Edit: Nevermind, resetting |
Unfortunately I have no progress to report here; reproducing the build with earlier versions of the 4.10 development branch is difficult, and I couldn't do any actual bisecting. (One option I would consider is to not rebuild the opam switch each time, but simply rebuild the compiler and change-in-place the compiler installation. Hopefully the regression is within a range of commits where this approach is possible -- the object file formats are stable enough.) |
#9218: wrong file name error with -annot and inline records
links.0.9
does not compile with OCaml 4.10, after a bit of clean up, the following error message appears when compiling several modules, e.g.:I tried to reproduce it with a smaller test case but I wasn't able to get one, so here is as far as I went in my debugging session:
modname = "result"
andps.ps_name = "Result"
, I'm guessingmodname
should be a capitalized and something went wrong along the way.-annot
is removed from the arguments.And I'm afraid that's all I have for now, I don't know enough about the internals of the compiler to guess where to poke further in a clever way. I might add more debug message to the functions shown above in the backtrace later but it might take some time so if someone here has a good enough guess that might speed up the debugging process.
To test it locally here are the necessary steps:
Happy new year!
The text was updated successfully, but these errors were encountered: