Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • diffoscope diffoscope
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 145
    • Issues 145
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Reproducible BuildsReproducible Builds
  • diffoscopediffoscope
  • Issues
  • #67
Closed
Open
Issue created Sep 05, 2019 by Mattia Rizzolo@mattiaOwner

Test failures with OCaml 4.08

Forwarded from https://bugs.debian.org/939386 by @glondu

Your package diffoscope FTBFS with OCaml 4.08.0.

The failure is due to a test that inspects a .cmi file that is shipped by the source package, using the "ocamlobjinfo" command. This cannot work.

Indeed there is no compatibility guarantee on .cmi (or any other type of object files) between different versions of OCaml. And this incompatibility is what hurts here: the .cmi shipped in the source package was made with OCaml < 4.08.0. The difference in version can be seen with the "file" command.

I have two suggestions:

  • Handle gracefully the case where ocamlobjinfo rejects an object file because it was not compiled with the same version of OCaml.
  • Instead of shipping a .cmi file in the source package, generate one at build time.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking