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

ocaml 4.03 failure in oUnitRunner.ml #10

Closed
olafhering opened this issue Oct 1, 2019 · 1 comment · Fixed by ocaml/opam-repository#14987
Closed

ocaml 4.03 failure in oUnitRunner.ml #10

olafhering opened this issue Oct 1, 2019 · 1 comment · Fixed by ocaml/opam-repository#14987

Comments

@olafhering
Copy link

Commit 624337a causes a build failure with ocaml-4.03:

[   65s] Command [82] exited with code 2:
[   65s] $ (cd _build/default && /usr/bin/ocamlc.opt -w @1..3@5..28@30..39@43@46..47@49..57@61..62-40 -strict-sequence -strict-formats -short-paths -keep-locs -g -bin-annot -I src/lib/ounit2/advanced/.oUnitAdvanced.objs/byte -I /usr/lib64/ocaml/bytes -I /usr/lib64/ocaml/stdlib-shims -no-alias-deps -opaque -o src/lib/ounit2/advanced/.oUnitAdvanced.objs/byte/oUnitRunner.cmo -c -impl src/lib/ounit2/advanced/oUnitRunner.ml)
[   65s] File "src/lib/ounit2/advanced/oUnitRunner.ml", line 150, characters 0-7:
[   65s] Warning 50: ambiguous documentation comment
[   65s] File "src/lib/ounit2/advanced/oUnitRunner.ml", line 1:
[   65s] Error: Some fatal warnings were triggered (1 occurrences)
[   65s] error: Bad exit status from /var/tmp/rpm-tmp.j4u04i (%build)

Not that it matters much for me, just want to mention it.

gildor478 added a commit to gildor478/opam-repository that referenced this issue Oct 2, 2019
@gildor478
Copy link
Owner

gildor478 commented Oct 2, 2019

I have sent a fix to opam (ocaml/opam-repository#14985) and 0dcf269 should fix the problem.

gildor478 added a commit to gildor478/opam-repository that referenced this issue Oct 2, 2019
CHANGES:

### Fixed
- Fix problem with  OCaml 4.03 and ambiguous command (Closes: gildor478/ounit#10).
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

Successfully merging a pull request may close this issue.

2 participants