ocaml / ocaml/dune

odoc required by cram depending on objs/byte

Open
#11,633 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

acknowledged
Dominant language
OCaml
Stars
1.9k
Forks
500
Avg merge
15h 21m
Merged PRs (30d)
277

Description

Expected Behavior

> dune runtest
> echo $?
0

Actual Behavior

> dune runtest
File ".foo.objs/byte/_unknown_", line 1, characters 0-0:
Error: Program odoc not found in the tree or in PATH
 (context: default)
Hint: opam install odoc

Reproduction

  1. Create and check into an opam switch with only ocaml and dune
  2. Create a file dune-project with (lang dune 3.18)
  3. Create empty files foo.ml and foo.t
  4. Create the following dune file:
(library (name foo))

(cram
 (deps
  (glob_files .foo.objs/byte/*)))
  1. Run dune runtest

Specifications

  • Dune 3.18.0
  • OCaml 5.3.0
  • Ubuntu 24.10

Additional information

Local switch contents

base-bigarray         base
base-domains          base
base-effects          base
base-nnp              base
base-threads          base
base-unix             base
dune                  3.18.0
ocaml                 5.3.0
ocaml-base-compiler   5.3.0
ocaml-compiler        5.3.0
ocaml-config          3
ocaml-options-vanilla 1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report with the shown dune-project, dune file, foo.ml, and foo.t files in a switch containing only OCaml and Dune. Run dune runtest and inspect how the cram dependency glob over .foo.objs/byte causes odoc to be required. Done means the reproduction no longer requires odoc or reports an unexplained missing program.

Written by the indexing model from the issue text.

Assessment

Tech stack
ocaml
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.