Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Olivier Andrieu <andrieu@ijm.jussieu.fr>
Cc: radugrigore@gmail.com, caml-list@inria.fr
Subject: Re: [Caml-list] glibc and ocaml/libasmrun.a
Date: Wed, 12 Jan 2005 16:45:54 +0100	[thread overview]
Message-ID: <20050112154554.GA8652@yquem.inria.fr> (raw)
In-Reply-To: <20050112.100059.112626362.oandrieu@nerim.net>

> This means the runtime (libasmrun.a) contains calls to dlopen(). Now
> I'm not sure why there are dlopen's in the native (ocamlopt)
> runtime. I thought only the bytecode one is using dlopen (to
> dynamically link stub libraries). If that is correct (ie the native
> runtime doesn't actually use dlopen) then I guess you can ignore the
> warning. 

This is entirely correct.  The reason why the native-code runtime
system contains the wrappers around dlopen() is that there exists
exactly one ocamlopt-compiled program that needs them: it's ocamlc.opt,
the natively-compiled bytecode compiler, which needs to dlopen()
shared libraries to check for the existence of symbols referenced from
external declarations in the Caml source.  

So, unless the Caml program happens to embark most of ocamlc
(unlikely!), you can safely ignore the warning at static linking time.

- Xavier Leroy


  reply	other threads:[~2005-01-12 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12  7:29 Radu Grigore
2005-01-12  7:50 ` Radu Grigore
2005-01-12  9:00 ` [Caml-list] " Olivier Andrieu
2005-01-12 15:45   ` Xavier Leroy [this message]
2005-01-13  7:05     ` Radu Grigore

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=20050112154554.GA8652@yquem.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=andrieu@ijm.jussieu.fr \
    --cc=caml-list@inria.fr \
    --cc=radugrigore@gmail.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