This bug is due to an API change appeared in OCamlgraph 1.8.4 and then reverted back in 1.8.5. OCamlgraph 1.8.3 (present testing's version) is not affected.