Skip to content
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

Lazy.undefined is raised during the link phase #63

Open
ivg opened this issue Aug 29, 2016 · 7 comments
Open

Lazy.undefined is raised during the link phase #63

ivg opened this issue Aug 29, 2016 · 7 comments

Comments

@ivg
Copy link

ivg commented Aug 29, 2016

At first I created an dsheets/codoc#95 issue in codoc repository, but it looks like that this repository is more suitable. On the link phase I've got a Lazy.Undefined exception. Not sure if it helps, but here is the backtrace:

OCAMLRUNPARAM=b codoc link --index -f opam-doc
Fatal error: exception Lazy.Undefined
Raised at file "camlinternalLazy.ml", line 18, characters 48-57
Called from file "camlinternalLazy.ml", line 25, characters 17-27
Re-raised at file "camlinternalLazy.ml", line 32, characters 10-11
Called from file "camlinternalLazy.ml", line 25, characters 17-27
Re-raised at file "camlinternalLazy.ml", line 32, characters 10-11
Called from file "_build/lib-doc-ock/docOckComponentTbl.cml-native", line 398, characters 17-49
Called from file "_build/lib-doc-ock/docOckComponentTbl.cml-native", line 165, characters 19-56
Called from file "camlinternalLazy.ml", line 25, characters 17-27
Re-raised at file "camlinternalLazy.ml", line 32, characters 10-11
Called from file "camlinternalLazy.ml", line 25, characters 17-27
Re-raised at file "camlinternalLazy.ml", line 32, characters 10-11
Called from file "_build/lib-doc-ock/docOckResolve.cml-native", line 231, characters 18-31
Called from file "_build/lib-doc-ock/docOckResolve.cml-native", line 839, characters 31-71
Called from file "list.ml", line 55, characters 20-23
Called from file "_build/lib-doc-ock/docOckResolve.cml-native", line 832, characters 12-1001
Called from file "_build/lib-doc-ock/docOckMaps.cml-native", line 1268, characters 22-48
Called from file "_build/lib-doc-ock/docOckMaps.cml-native", line 9, characters 15-18
Called from file "_build/lib-doc-ock/docOckMaps.cml-native", line 12, characters 19-31
Called from file "_build/lib-doc-ock/docOckMaps.cml-native", line 1960, characters 23-43
Called from file "_build/lib-doc-ock/docOckMaps.cml-native", line 1977, characters 19-44
Called from file "_build/lib-doc-ock/docOckResolve.cml-native", line 912, characters 18-29
Called from file "map.ml", line 192, characters 19-42
Called from file "map.ml", line 192, characters 26-41
Called from file "_build/lib-codoc/codocIndex.ml", line 405, characters 14-103
Called from file "map.ml", line 192, characters 19-42
Called from file "map.ml", line 192, characters 26-41
Called from file "map.ml", line 192, characters 26-41
Called from file "_build/bin-codoc/codocCliLink.ml", line 116, characters 13-54

I will be happy to provide more info, don't hesitate to ask. (It could be hard to reproduce, though, but maybe I can just tar-ball the opam folder or maybe just the output folder of opam doc).

@lpw25
Copy link
Collaborator

lpw25 commented Sep 14, 2016

I don't think codoc is up-to-date with this library at the moment. odoc is more up-to-date, can you reproduce the issue with that?

There have been a few Lazy.Undefined bugs, but all of the ones I'm aware of have been fixed, so I'm interested if you have discovered another case.

@ivg
Copy link
Author

ivg commented Sep 15, 2016

Do you have suggestions on how to switch opam-doc from codoc to odoc?

@lpw25
Copy link
Collaborator

lpw25 commented Sep 15, 2016

Hmm, the best thing might be to wait a couple of weeks and then try with opkg which subsumes opam-doc and supports odoc.

@lpw25
Copy link
Collaborator

lpw25 commented Sep 15, 2016

(Wait a couple of weeks because opkg should be released by then)

@dbuenzli
Copy link
Contributor

Just don't try opkg odoc right now there's still a bug in odoc that will muddy your cwd.

@dbuenzli
Copy link
Contributor

(opkg ocamldoc is fine if you are interested).

@ivg
Copy link
Author

ivg commented Sep 15, 2016

That's alright, we can wait, so far we felt back to the argot for our documentation. But we're anticipating a move to the newer infrastructure, so don't hesitate to use us a alpha testers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants