caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: <RABIH.EL-CHAAR@lyxor.com>
To: <caml-list-bounces@yquem.inria.fr>, <caml-list@inria.fr>
Subject: RE: [Caml-list] Creating an lwt toplevel
Date: Tue, 6 Oct 2009 16:56:57 +0200	[thread overview]
Message-ID: <0172C3AE3A0E964797AF43E206C1048F04A390F6@FRCOR-EXMB06.europe.am.socgen> (raw)
In-Reply-To: <25ec8ca60910060748v89d8b6ck28706826bb836876@mail.gmail.com>

You are probably missing the .cmi files.
The .cma contains the bytecode, but not module signatures.

The toplevel has to see the corresponding .cmi files (#directory might help from the toplevel).

Rabih

-----Message d'origine-----
De : caml-list-bounces@yquem.inria.fr [mailto:caml-list-bounces@yquem.inria.fr] 
Envoyé : mardi 6 octobre 2009 16:48
À : caml-list@inria.fr
Objet : [Caml-list] Creating an lwt toplevel


Hello,

I am trying to experiment with some code that uses lwt, and I would
like to do it in a toplevel. Unfortunately I seem to be missing a
step. Here is what I tried:

# #load "unix.cma";;
# #load "/Users/schmitta/godi/lib/ocaml/pkg-lib/lwt/lwt.cma";;
# open Lwt;;
Error: Unbound module Lwt

I then tried:

$ ocamlfind ocamlmktop -o lwtcaml -package lwt unix.cma lwt.cma
$ ./lwtcaml
        Objective Caml version 3.11.1

# open Lwt;;
Error: Unbound module Lwt

I feel like I'm missing something obvious, but cannot see what it is right
now.

Thanks for any suggestion,

Alan

_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

*************************************************************************
This message and any attachments (the "message") are confidential, intended solely for the addressee(s), and may contain legally privileged information.
Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration.   
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or
falsified.
                              ************
Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et susceptibles de contenir des informations couvertes 
par le secret professionnel. 
Ce message est etabli a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration. 
La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie.
*************************************************************************


  reply	other threads:[~2009-10-06 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 14:48 Alan Schmitt
2009-10-06 14:56 ` RABIH.EL-CHAAR [this message]
2009-10-06 15:01 ` [Caml-list] " Chantal KELLER
2009-10-06 15:13   ` Alan Schmitt
2009-10-06 15:26 ` Jérémie Dimino
2009-10-07  8:25   ` Alan Schmitt

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=0172C3AE3A0E964797AF43E206C1048F04A390F6@FRCOR-EXMB06.europe.am.socgen \
    --to=rabih.el-chaar@lyxor.com \
    --cc=caml-list-bounces@yquem.inria.fr \
    --cc=caml-list@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).