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

ocamldep bug? #2956

Closed
vicuna opened this issue Sep 5, 2001 · 2 comments
Closed

ocamldep bug? #2956

vicuna opened this issue Sep 5, 2001 · 2 comments
Labels

Comments

@vicuna
Copy link

vicuna commented Sep 5, 2001

Original bug ID: 512
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

I notice that if foo.ml contains the following:

module Orange = Apple

and both orange.ml and apple.ml exist, then

% ocamldep foo.ml
foo.cmo: apple.cmo orange.cmo
foo.cmx: apple.cmx orange.cmx

even though orange.ml is not a dependency.

@vicuna
Copy link
Author

vicuna commented Sep 10, 2001

Comment author: administrator

I notice that if foo.ml contains the following:
module Orange = Apple
and both orange.ml and apple.ml exist, then
% ocamldep foo.ml
foo.cmo: apple.cmo orange.cmo
foo.cmx: apple.cmx orange.cmx
even though orange.ml is not a dependency.

There was such a bug in version 3.01, but it is fixed in 3.02. The
working version give the right dependencies (foo depends only on apple).

Best wishes,

  • Xavier Leroy

@vicuna
Copy link
Author

vicuna commented Sep 10, 2001

Comment author: administrator

Was a 3.01 bug, fixed in 3.02

@vicuna vicuna closed this as completed Sep 10, 2001
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant