From: "Gerd Stolpmann" <info@gerd-stolpmann.de>
To: "Philippe Veber" <philippe.veber@gmail.com>
Cc: "\"Stéphane Glondu\"" <steph@glondu.net>,
"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Current SVN head and findlib.
Date: Mon, 16 Apr 2012 17:46:59 +0200 [thread overview]
Message-ID: <d5daf098e9ef1a156e9226fe99ab2d31.squirrel@gps.dynxs.de> (raw)
In-Reply-To: <CAOOOohS1pJQRJ1M8vErXhMVwHB9+ddCvCYLRanqhHZsM=ZnKfA@mail.gmail.com>
> 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";;
I tried to debug this, but the result is strange. First, I tried to create
a reproduction case which is independent of findlib (i.e. using the same
topfind script, but loading a different module). I was not successful.
There must be something very special triggering the problem. I also read
the relevant parts of the Ocaml sources to get an idea - again, no result,
the search path is simply a global variable.
The only thing I found out: If you change the topfind script so that the
#directory directive is executed before loading the modules (i.e. move
this directive right to the beginning of the script), everything works
again. Somehow the load must be incomplete when the directory of the .cma
files is not in the search path (although we load by absolute path). Maybe
the behaviour has to do with bug
http://caml.inria.fr/mantis/view.php?id=5551 .
Gerd
>>
> 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.
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
--
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
*** Searching for new projects! Need consulting for system
*** programming in Ocaml? Gerd Stolpmann can help you.
prev parent reply other threads:[~2012-04-16 15:47 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
2012-04-16 15:46 ` Gerd Stolpmann [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=d5daf098e9ef1a156e9226fe99ab2d31.squirrel@gps.dynxs.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=philippe.veber@gmail.com \
--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