Re: n00b question- rebuilding mirage tree

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

We could also get rid of that tag now. It's only use is to add -nostdlib and 
-annot to the ocaml invocations:

     (* do not compile and pack with the standard lib *)
     flag ["ocaml"; "compile"; "mirage" ] & S [A"-nostdlib"; A"-annot"];
     flag ["ocaml"; "pack"; "mirage"] & S [A"-nostdlib"];

Nowadays, everything is built against the standard library, so I see no reason 
why it shouldn't just be removed. I've pushed Raphel's patch for now, to ensure 
everything builds reliably. I wonder why it was working for me all this time?? 
:-)

Anil

On 11 Aug 2011, at 14:06, Raphael Proust wrote:

> @Thomas: can you try with my repository? I just added `true: mirage`
> to all _tags under /lib.
> 
> On Thu, Aug 11, 2011 at 1:52 PM, Raphael Proust <raphlalou@xxxxxxxxx> wrote:
>> That's probably because (for a reason I don't know) lib/os/xen/_tags
>> lacks the `true: mirage` assertion.
>> 
>> (See difference between
>> https://github.com/avsm/mirage/blob/master/lib/os/xen/_tags and
>> https://github.com/avsm/mirage/blob/master/lib/os/unix/_tags )
>> 
>> Curiously, the problem isn't raised on my machine with a fresh
>> repository. Probably because my two pervasives are similar…
>> 
>> I think `true: mirage` should be added to all the _tags files under
>> /lib/ (and any subdirectories), but I'm not sure. I'm especially not
>> sure for some parts of OS and Flow…
>> 
>> On Thu, Aug 11, 2011 at 1:41 PM, Thomas Gazagnaire
>> <thomas.gazagnaire@xxxxxxxxx> wrote:
>>> I've just tried to build mirage as well, and I get:
>>> 
>>> File "os/xen/oS.cmx", line 1, characters 0-1:
>>> Error: The files os/xen/io_page.cmi and /usr/local/lib/ocaml/pervasives.cmi
>>>       make inconsistent assumptions over interface Pervasives
>>> Command exited with code 1.
>>> 
>>> on a fresh clone (on ubuntu)
>>> 
>>> 2011/8/11 Raphael Proust <raphlalou@xxxxxxxxx>:
>>>> AFAICT, this is a bug in mirage's build process.
>>>> 
>>>> After
>>>> $ make
>>>> 
>>>> you just need to do
>>>> $ cd lib
>>>> $ make
>>>> 
>>>> and then
>>>> $ cd ..
>>>> $ make install
>>>> 
>>>> should work.
>>>> 
>>>> 
>>>> I don't know why this particular backend is not compiled when invoking
>>>> `make` from the top-level directory.
>>>> 
>>>> On Thu, Aug 11, 2011 at 1:02 PM, Richard Mortier
>>>> <Richard.Mortier@xxxxxxxxxxxxxxxx> wrote:
>>>>> just doing a rebuild after not merging for a while - am being told
>>>>> 
>>>>> : mort@greyjay:mirage.git$; make PREFIX=~/research/mirage/install all 
>>>>> install
>>>>> /Users/mort/research/mirage/mirage.git/tools/crunch
>>>>> Finished, 0 targets (0 cached) in 00:00:00.
>>>>> Finished, 6 targets (6 cached) in 00:00:00.
>>>>> /Users/mort/research/mirage/mirage.git/tools/mir
>>>>> make[1]: Nothing to be done for `all'.
>>>>> /Users/mort/research/mirage/mirage.git/syntax
>>>>> Finished, 0 targets (0 cached) in 00:00:00.
>>>>> Finished, 106 targets (106 cached) in 00:00:00.
>>>>> /Users/mort/research/mirage/mirage.git/lib
>>>>> OS: unix
>>>>> Flow: socket
>>>>> # No parallelism done
>>>>> OS: unix
>>>>> Flow: direct
>>>>> # No parallelism done
>>>>> Assembling: camlp4 extensions
>>>>> Skipping: Xen
>>>>> Assembling: UNIX direct
>>>>> Assembling: UNIX socket
>>>>> Assembling: node socket
>>>>> Must build node-socket first
>>>>> make: *** [install] Error 1
>>>>> 
>>>>> 
>>>>> ...what is node-socket, and how should i install it?  (npm search throws 
>>>>> up many socket related things, but nothing called node-socket)
>>>>> 
>>>>> (on osx 10.5/64bit if it makes a difference.)
>>>>> --
>>>>> Cheers,
>>>>> 
>>>>> R.
>>>>> 
>>>>> This message and any attachment are intended solely for the addressee and 
>>>>> may contain confidential information. If you have received this message 
>>>>> in error, please send it back to me, and immediately delete it.   Please 
>>>>> do not use, copy or disclose the information contained in this message or 
>>>>> in any attachment.  Any views or opinions expressed by the author of this 
>>>>> email do not necessarily reflect the views of the University of 
>>>>> Nottingham.
>>>>> 
>>>>> This message has been checked for viruses but the contents of an 
>>>>> attachment
>>>>> may still contain software viruses which could damage your computer 
>>>>> system:
>>>>> you are advised to perform your own checks. Email communications with the
>>>>> University of Nottingham may be monitored as permitted by UK legislation.
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> _______
>>>> Raphael
>>>> 
>>>> 
>>> 
>> 
>> 
>> 
>> --
>> _______
>> Raphael
>> 
> 
> 
> 
> -- 
> _______
> Raphael
>