> Thanks. I updated my -rumprun packages to those versions manually and I now > have mirage-http built. However, am running into other errors when trying > to build some unikernels that use conduit: > > conduit_server: > > File "unikernel.ml", line 12, characters 34-42: > Error: Unbound module CON.Flow > > static_website: > > File "dispatch.ml", line 46, characters 16-29: > Error: Unbound module S.Request > > Again, given that I'm in an alternate universe of opam files, I have no > easy way of telling what constraints have changed upstream [*]. > > Is there something else I need to upgrade to match the new conduit? Mirage > itself?
Yes, you need mirage 2.5.0 and the `mirage-dev` branch of mirage-skeleton. I can help you upgrade your unikernel code if it is published somewhere. Thomas > [*] Getting the cross-compilation work into upstream OPAM and packages is > on my list, but I want to get the whole stack working first as the former > is going to take some discussion and time. > > > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
