On 23 Mar 2017, at 15:14, Hannes Mehnert <[email protected]> wrote: > > On 23/03/2017 16:04, Daniel J Williams wrote: >> >> "MirageOS-devel" <[email protected]> wrote on >> 03/23/2017 08:41:44 AM: >>> From: Hannes Mehnert <[email protected]> >> >>> I'm not sure what the way forward is here -- the current opam-repository >>> doesn't let anyone build any MirageOS unikernels which depend on (uri, >>> cstruct, vchan, tls, x509, mirage-net-xen, ..) unless pinning sexplib to >>> 113.33.03 ("opam pin add sexplib 113.33.03" should do the trick). >> >> I'm trying to pin sexplib to 113.33.03 as suggested, but that isn't working >> because of a restriction on ocaml 4.02.3... is anyone using a workaround >> that uses ocaml 4.04.0 and mirage 3.0? How do you get around sexplib >> 113.33.03 requiring 4.02.3? > > I have `opam pin add sexplib 113.33.00+4.03` installed using 4.04.0 > (although its version mentions 4.03).
There were a couple of transitionary packages to adapt sexplib to 4.03 and 4.04. Hopefully this will not be necessary in the future thanks to the new 'ocaml-migrate-parsetree' package that abstracts away PPX from the specific compiler version in use. Dan, I've merged in various conflicts on the new sexplib into opam-repository upstream, so if you "opam update" now the v0.9.0 series should not be pulled in and you no should not need a pin. regards, Anil _______________________________________________ MirageOS-devel mailing list [email protected] https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
