Re: opam and myocamlbuild.ml files

[Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>]

On 26 Aug 2012, at 01:52, Anil Madhavapeddy wrote:

> To follow up on this, we should *not* introduce a compile-time dependency
> on OASIS at this stage.
> 
> The reason is that our tool-chains don't do a very good job of cross-compiles
> and so a 'mirage-3.12.1-xen' OPAM toolchain might not be capable of producing
> UNIX binaries.

hm- i guess i don't use the -xen toolchain very often - could you expand a bit 
on why this is an issue?  (or is that tantamount to just fixing it cf the 
mirage/bsd comment below? :)

> And of course, when you are in 'OPAM xen mode', you cannot access the OASIS
> binary, which is probably installed in 'system' mode (in ~/.opam/system/bin).
> I've reverted the DNS dependency on OASIS which fixes the problem for now.

ok- what's the current "best practice" as a replacement for OASIS?

> There'll be plenty of time to worry about cross-compilation when integrating
> Gabor's kFreeBSD backend at the same time, which is even more sensitive to
> such issues than the Xen one :-)


"oh good"? :)

-- 
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.