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

ocamlbuild does not work well with ocamldep to generate dependency #5760

Closed
vicuna opened this issue Sep 17, 2012 · 6 comments
Closed

ocamlbuild does not work well with ocamldep to generate dependency #5760

vicuna opened this issue Sep 17, 2012 · 6 comments

Comments

@vicuna
Copy link

vicuna commented Sep 17, 2012

Original bug ID: 5760
Reporter: @bobzhang
Status: closed (set by @xavierleroy on 2015-12-11T18:20:57Z)
Resolution: unable to duplicate
Priority: normal
Severity: minor
Target version: 4.01.0+dev
Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues
Monitored by: @gasche

Bug description

ocamlbuild invoke ocamldep to generate dependency, when both A.ml and A.mli exists, it will only pick A.mli, some dependency is missing which results in a linking error

@vicuna
Copy link
Author

vicuna commented Sep 17, 2012

Comment author: @gasche

Thanks for the report.

Could you provide a sequence of shell commands that would allow to reproduce the problem?

@vicuna
Copy link
Author

vicuna commented Sep 17, 2012

Comment author: @bobzhang

I spot this error from a large project, it may be hard to reproduce in a minimal examlpe.
But it may be easy to verify this problem: by
ocamlbuild -verbose 1 binary.byte
and read the log
Here is a sample output

ocamlfind ocamldep -pp 'boot/fan -parser rf -parser debug -printer p -D OPT' -modules src/Camlp4/Struct/Grammar/Print.mli > src/Camlp4/Struct/Grammar/Print.mli.depends

It will not use Print.ml to generate dependency, if Print.mli is very succinct, it will not generate dependency correctly

@vicuna
Copy link
Author

vicuna commented Sep 17, 2012

Comment author: @gasche

I'm sorry, hongbo, but I'm afraid the issue would be quite hard to understand and debug without a test case. Please try to see if you can produce a test case, otherwise the bug is unlikely to go away from this report alone.

@vicuna
Copy link
Author

vicuna commented Oct 1, 2012

Comment author: @damiendoligez

I agree with gasche, we need a repro case, even if it's a big one.

@vicuna
Copy link
Author

vicuna commented Oct 1, 2012

Comment author: @bobzhang

I would try to make a reproducible case by tuesday. The problem is that for small repos, it's hard to cause a failure

@vicuna
Copy link
Author

vicuna commented Oct 2, 2012

Comment author: @bobzhang

Sorry, I can not reproduce the problem any more, my repo was changed a lot(directory structure flattened).

But I remembered if I have two files Printer.ml Printer.mli, if I remove Printer.mli, then everything went smoothly. Sorry for the in-convenience.

@vicuna vicuna closed this as completed Dec 11, 2015
@vicuna vicuna added this to the 4.01.0 milestone Mar 14, 2019
@vicuna vicuna added the bug label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant