From: Ralf Treinen <treinen@free.fr>
To: Kaspar Rohrer <krohrer@student.ethz.ch>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Building a toplevel with threads
Date: Thu, 31 May 2007 07:29:17 +0200 [thread overview]
Message-ID: <20070531052917.GA4144@seneca.free.fr> (raw)
In-Reply-To: <40168660-516C-40A1-AD7D-2963D9566B5A@student.ethz.ch>
On Thu, May 31, 2007 at 07:19:20AM +0200, Kaspar Rohrer wrote:
> I'm currently trying to build a toplevel with thread support, but
> somehow the final executable is missing the Thread module. Findlib is
> out of question because dynamic loading is not supported on my
> platform (Intel OS X, OCaml 3.09.3).
> So what would be the correct way to build a custom toplevel with
> support for threads? This is what I have so far:
>
> ocamlmktop -thread -custom unix.cma threads.cma -o thtop
>
> which gives:
>
> # Thread.create;;
> Unbound value Thread.create
I have seen this before. Try calling your toplevel as "thtop -I +threads".
-Ralf.
prev parent reply other threads:[~2007-05-31 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 5:19 Kaspar Rohrer
2007-05-31 5:29 ` Ralf Treinen [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=20070531052917.GA4144@seneca.free.fr \
--to=treinen@free.fr \
--cc=caml-list@yquem.inria.fr \
--cc=krohrer@student.ethz.ch \
/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