caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Trying out Ocaml CVS HEAD
Date: Wed, 16 Apr 2008 08:55:41 +0200	[thread overview]
Message-ID: <4805A2ED.7010606@frisch.fr> (raw)
In-Reply-To: <708296.53944.qm@web54605.mail.re2.yahoo.com>

Hi Dario,

> I realise that the Ocaml CVS HEAD comes with an implicit "Here be dragons"
> warning.

Sure, but it is very helpful to get some feedback!

> Still, I would like to use it so I can try running Ocsigen in
> native mode (the loading of Ocsigen modules relies on dynlink; native mode
> thus requires the new natdynlink feature).  I've compiled the Ocaml CVS via
> GODI, using the instructions in Alain Frisch's page; though the compilation
> completes with no problems and the compiler itself seems to work fine, I
> always get an error when Ocsigen tries to dynlink (either in byte-code or
> native-code) a module that uses stub libraries.

I've been able to reproduce the problem in byte-code only, when the main 
program is linked in -custom mode. The reason is that the -Wl,-E was not 
passed to the linker. This is now fixed in the CVS. (For a quick test, 
you can try to pass "-ccopt -Wl,-E" explicitly to ocamlc when linking.)

For the native-code, I don't know. Can you show me the command line 
passed to the linker (ocamlopt -verbose)? You should see -Wl,-E.
If you compile with -noautolink, you must add "-ccopt -Wl,-E" manually.


Cheers,

Alain


  reply	other threads:[~2008-04-16  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 13:49 Dario Teixeira
2008-04-16  6:55 ` Alain Frisch [this message]
2008-04-16 21:23   ` [Caml-list] " Dario Teixeira
2008-04-17  8:28     ` Alain Frisch

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=4805A2ED.7010606@frisch.fr \
    --to=alain@frisch.fr \
    --cc=caml-list@yquem.inria.fr \
    --cc=darioteixeira@yahoo.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;
as well as URLs for NNTP newsgroup(s).