From: Philippe Veber <philippe.veber@gmail.com>
To: "Stéphane Glondu" <steph@glondu.net>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Current SVN head and findlib.
Date: Thu, 12 Apr 2012 16:25:56 +0200 [thread overview]
Message-ID: <CAOOOohS1pJQRJ1M8vErXhMVwHB9+ddCvCYLRanqhHZsM=ZnKfA@mail.gmail.com> (raw)
In-Reply-To: <4F86D859.6020308@glondu.net>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
2012/4/12 Stéphane Glondu <steph@glondu.net>
> Le 12/04/2012 14:30, Philippe Veber a écrit :
> > While playing with the upcoming features of our favorite compiler, I
> > found that the current trunk and version/4.00 branch do not work well
> > with findlib (version 1.2.8). I report it here so others might confirm
> > (or not) what I say.
> >
> > OCaml version 4.01.0+dev1_2012-03-31
> >
> > # #use "topfind";;
> > - : unit = ()
> > File "/home/pveber/usr/ocamlbrew/ocaml-svn/trunk/lib/ocaml/topfind",
> > line 37, characters 0-22:
> > Error: Unbound module Topfind
> >
> > What is really surprising is that the toplevel doesn't complain if I
> > copy/paste the contents of topfind directly in the compiler:
> > [...]
>
> It works if you execute (replace /usr/lib/ocaml by `ocamlc -where`)
>
> #directory "/usr/lib/ocaml/findlib";;
>
> before calling
>
> #use "topfind";;
>
Indeed, it works fine with that trick. Thanks !
>
> The #directory is present in /usr/lib/ocaml/topfind, but it seems that
> now, they don't have immediate effect.
>
Yes, that is a really surprising issue for me.
Thanks again,
ph.
[-- Attachment #2: Type: text/html, Size: 1734 bytes --]
next prev parent reply other threads:[~2012-04-12 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 12:30 Philippe Veber
2012-04-12 12:57 ` Jonathan Protzenko
2012-04-12 14:24 ` Philippe Veber
2012-04-12 13:27 ` Stéphane Glondu
2012-04-12 14:25 ` Philippe Veber [this message]
2012-04-16 15:46 ` Gerd Stolpmann
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='CAOOOohS1pJQRJ1M8vErXhMVwHB9+ddCvCYLRanqhHZsM=ZnKfA@mail.gmail.com' \
--to=philippe.veber@gmail.com \
--cc=caml-list@inria.fr \
--cc=steph@glondu.net \
/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