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

Duplicate .cmo in ocamldoc #8241

Closed
vicuna opened this issue Aug 12, 2003 · 1 comment
Closed

Duplicate .cmo in ocamldoc #8241

vicuna opened this issue Aug 12, 2003 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented Aug 12, 2003

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

Bug description

Full_Name: Christopher Dutchyn
Version: 3.07+beta1
OS: Solaris
Submission from: cypress.cs.ubc.ca (142.103.11.23)

There is a duplicate include in the ocamldoc/Makefile, causing
$(OCAMLSRCDIR)/typing/typedtree.cmo to be included twice. This is OK for make
world, make bootstrap, make opt, but crashes make opt.opt with
Files ../typing/typedtree.cmx and ../typing/typedtree.cmx
both define a module named Typedtree
The fix is to remove the second entry -- you must have typedtree.cmo before
parmatch.cmo.

@vicuna
Copy link
Author

vicuna commented Aug 13, 2003

Comment author: administrator

Full_Name: Christopher Dutchyn
Version: 3.07+beta1
OS: Solaris
Submission from: cypress.cs.ubc.ca (142.103.11.23)

There is a duplicate include in the ocamldoc/Makefile, causing
$(OCAMLSRCDIR)/typing/typedtree.cmo to be included twice. This is OK for make
world, make bootstrap, make opt, but crashes make opt.opt with
Files ../typing/typedtree.cmx and ../typing/typedtree.cmx
both define a module named Typedtree
The fix is to remove the second entry -- you must have typedtree.cmo before
parmatch.cmo.

Oups !
Thank you for reporting this bug.

--Luc

@vicuna vicuna closed this as completed Aug 13, 2003
@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