Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Jérôme Benoit" <jerome.benoit@grenouille.com>
To: Yaron Minsky <yminsky@janestreet.com>
Cc: "Soegtrop, Michael" <michael.soegtrop@intel.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>,
	"ocaml-core@googlegroups.com" <ocaml-core@googlegroups.com>
Subject: Re: [Caml-list] How to handle system decencies in Ocaml (like O_ASYNC not implemented in cygwin)
Date: Fri, 6 May 2016 23:41:33 +0200	[thread overview]
Message-ID: <20160506234133.6f1cb28c@nemesis> (raw)
In-Reply-To: <CACLX4jRYhcZ4XZCDKGODYd1PPBcqCcfGUU2aVU=VJskipxiLUg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

On Fri, 6 May 2016 10:33:32 -0400 in
<CACLX4jRYhcZ4XZCDKGODYd1PPBcqCcfGUU2aVU=VJskipxiLUg@mail.gmail.com>,
Yaron Minsky <yminsky@janestreet.com> wrote:

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

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

Most people that need to make portable code handle flag dependencies on
open() - or other flags on standard functions - in the buildsystem
with a little piece of C code that open() a file created by the
buildsystem with different flags and catch the return code : 

#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
...
int retasync = open(/path/to/test/file, O_ASYNC);
...
 
then define a boolean inside the buildsystem to make conditional
compilation based on the boolean. 

Cheers. 

-- 
Jérôme Benoit aka fraggle
Piment Noir - http://piment-noir.org
OpenPGP Key ID : 9FE9161D
Key fingerprint : 9CA4 0249 AF57 A35B 34B3 AC15 FAA0 CB50 9FE9 161D

[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-05-06 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06  8:48 Soegtrop, Michael
2016-05-06 14:33 ` Yaron Minsky
2016-05-06 21:41   ` Jérôme Benoit [this message]
2016-05-07  8:37     ` Soegtrop, Michael
2016-05-07 14:23       ` Jérôme Benoit
2016-05-09  7:08         ` Soegtrop, Michael
2016-05-14  8:50           ` Adrien Nader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160506234133.6f1cb28c@nemesis \
    --to=jerome.benoit@grenouille.com \
    --cc=caml-list@inria.fr \
    --cc=michael.soegtrop@intel.com \
    --cc=ocaml-core@googlegroups.com \
    --cc=yminsky@janestreet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox