Re: [Caml-list] How to handle system decencies in Ocaml (like O_ASYNC not implemented in cygwin)

[Yaron Minsky <yminsky@janestreet.com>]

Looping in the Core mailing list, since this seems like a core-specific issue.

y

On Fri, May 6, 2016 at 4:48 AM, Soegtrop, Michael
<michael.soegtrop@intel.com> wrote:
> Dear Ocaml users,
>
>
>
> I am working on compiling core with opam on cygwin. My plan is to integrate
> this with the work of whitequark (MinGW cross opam for Linux) to have a
> MinGW cross opam on cygwin.
>
>
>
> I already have a convenient script to setup cygwin with all modules and to
> compile opam and it works fine. Just when compiling core, there are two Unix
> features not implemented in cygwin. One is O_ASYNC. It is easy to patch it
> away and also easy to make this system dependent in the C file
> (unix_stubs.c), but I wonder how I could handle this in a portable way in
> the OCaml wrapper. It looks like this:
>
>
>
> module Open_flags = struct
>
>   external append    : unit -> Int63.t = "unix_O_APPEND"
>
>   external async     : unit -> Int63.t = "unix_O_ASYNC"
>
>   external cloexec   : unit -> Int63.t = "unix_O_CLOEXEC"
>
>
>
> Is there some way to have async on normal Linux and not have it on cygwin?
>
>
>
> Btw.: Opam, batteries and 34 out of the 35 modules of core compile fine on
> cygwin and the remaining module just has two errors, so I think it is
> worthwhile to fix this.
>
> Best regards,
>
> Michael
>
>
>
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928