package mirage-clock-unix

All checked builds pass
  1. Overview
  2. Docs
Unix-based implementation for the MirageOS Clock interface

Install

dune-project
 Dependency

Authors

Maintainers

Sources

mirage-clock-4.2.0.tbz
sha256=fa17d15d5be23c79ba741f5f7cb88ed7112de16a4410cea81c71b98086889847
sha512=05a359dc8400d4ca200ff255dbd030acd33d2c4acb5020838f772c02cdb5f243f3dbafbc43a8cd51e6b5923a140f84c9e7ea25b2c0fa277bb68b996190d36e3b

Description

The Unix implementation of the MirageOS Clock interface uses gettimeofday or clock_gettime, depending on which OS is in use (see clock_stubs.c).

Tags

org:mirage

Added to opam-repository:

README

mirage-clock -- libraries and module types for portable clocks

This library implements portable support for an operating system timesource that is compatible with the MirageOS library interfaces found in: https://github.com/mirage/mirage

It implements an MCLOCK module that represents a monotonic timesource since an arbitrary point, and PCLOCK which counts time since the Unix epoch.

The following sources are used:

  • The Unix version uses gettimeofday or clock_gettime, depending on which OS is in use (see clock_stubs.c).
  • The freestanding version uses the paravirtual clock source from the hypervisor.

Dependencies (4)

  1. mirage-clock = version
  2. dune-configurator
  3. dune >= "2.8"
  4. ocaml >= "4.08.0"

Dev Dependencies

None

Conflicts

None

Build status

Results of building mirage-clock-unix with each compiler on check.ci.ocaml.org, run of against opam-repository 7cdc698. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
4.2.0 (this version) good good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure