Re: [MirageOS-devel] Mirage 1.1.0 pull req

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 9 Feb 2014, at 18:17, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> 
wrote:

> 
> On 9 Feb 2014, at 18:12, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> 
>> On 5 Feb 2014, at 20:20, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> 
>> wrote:
>>> 
>>> i will have a PR for mirage-skeleton ready soon (maybe this evening). have 
>>> been working through trying to organise & update the samples as well as 
>>> incorporate the extra ones from fosdem. i'll see if i can get balraj's 
>>> examples in there too.
>>> 
>> 
>> I've just merged your examples in after verifying that they all build on 
>> Unix and Xen. A couple of minor bugs cropped up:
>> 
>> - We dont seem to include mirage-clock-unix by default, so the ethif example 
>> fails on Unix (but not Xen, where its an implicit dependency of the 
>> console).  Thomas -- should mirage-clock-unix by unconditionally added, 
>> since it's not an explicit device driver at the moment?  See my fixes here: 
>> https://github.com/mirage/mirage-skeleton/commit/95e826ce134f608f943364e212f7e8b083bbe7a0
> 
> ack; it might be useful to write down (or collate) the assumptions we're 
> making about package dependencies to check that we're coherent. i'm having 
> problems at the moment trying to go from a clean opam install on xen to even 
> being able to "mirage configure" my website -- there seem to be some weird 
> package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, 
> the configure step downgrades to 0.5.0; but if mirage-types is not installed 
> at all, it seems to install 1.1.0.)

Be sure to `opam update -u` before attempting a compilation, as that will give 
you the latest package sets and upgrade all relevant packages.

The "opam install" that is invoked by the unikernel build won't upgrade 
everything, hence the problems you're seeing.  If it persists after an upgrade, 
we have a constraint problem.

> 
>> - The stackv4 example used both the socket and direct backends, which 
>> obviously fails to build on Xen.  I used Mirage.get_mode() to make the 
>> socket backend conditional on being compiled onto Unix.  This exposed a 
>> small bug in the mirage command-line tool which I fixed here: 
>> https://github.com/mirage/mirage/pull/212
>> 
>> Other than that, just the mirage-www examples to update before releasing 
>> now. I've pushed a new 1.1.0 tag to reflect the last bugfix above.
> 
> ack. i need to make sure the PR for my fixes to the generation of 
> make-fatN-image.sh has been merged too...

Woops, I did not merge that.  Doing so now, and I'll slip the 1.1.0 tag again 
then.  Is there a example of using this in mirage-skeleton?

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel