From: Mike McClurg <mike.mcclurg@gmail.com>
To: Jeremy Yallop <yallop@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ctypes with -thread: inconsistent assumptions over implementation Foreign
Date: Wed, 20 Nov 2013 08:55:20 -0700 [thread overview]
Message-ID: <CALru5wWn5kJH3z=bOW0VBxzUr3COV6QJ1qw5SCG5+nJjKGDwjA@mail.gmail.com> (raw)
In-Reply-To: <CAAxsn=HAMkhmnm7HH1F9ZXHwgeRL177ZEDZov1o60Sz2V4s2-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
On Wed, Nov 20, 2013 at 8:28 AM, Jeremy Yallop <yallop@gmail.com> wrote:
> > It's a packaging problem.
>
> The problem is fixed in ctypes 0.2.2, which is now available via OPAM.
>
Awesome, thanks Jeremy! I've tested 0.2.2 from opam on my test program and
confirmed it works. I'm updating my ctypes RPM now.
Mike
[-- Attachment #2: Type: text/html, Size: 685 bytes --]
prev parent reply other threads:[~2013-11-20 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 22:57 Mike McClurg
2013-11-20 8:23 ` Jeremy Yallop
2013-11-20 15:28 ` Jeremy Yallop
2013-11-20 15:55 ` Mike McClurg [this message]
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='CALru5wWn5kJH3z=bOW0VBxzUr3COV6QJ1qw5SCG5+nJjKGDwjA@mail.gmail.com' \
--to=mike.mcclurg@gmail.com \
--cc=caml-list@inria.fr \
--cc=yallop@gmail.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