From: Alain Frisch <alain@frisch.fr>
To: "Gabriel Scherer" <gabriel.scherer@gmail.com>,
"Christoph Höger" <christoph.hoeger@tu-berlin.de>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] 4.04 linker woes
Date: Mon, 7 Nov 2016 23:04:57 +0100 [thread overview]
Message-ID: <01907fd4-be1f-351e-d5a0-0a644c29eb9d@frisch.fr> (raw)
In-Reply-To: <CAPFanBGETRiXqSQhXXDHBUUj3HJre=rR9k-KshgU0PDmQ-=t9w@mail.gmail.com>
On 07/11/2016 21:30, Gabriel Scherer wrote:
> Compplugin is a module from the compiler distribution that indeed is new
> in 4.04.0. It is not included in ocamlcommon.cma. It is part of
> ocamlbytecomp.cma, but not of ocamloptcomp.cma, and I believe that the
> latter omission is a bug (as Optcompile depends on it), so maybe it
> should really be in ocamlcommon.cma.
ocamlopt now includes ocamlbytecomp.cma. The reason is that the copy of
Dynlink which is now included in ocamlopt relies on many modules found
in this library. This is not ideal, as this will force linking
unneeded modules in ocamlopt (well, -linkall is not currently used, but
to make ocamlc/ocamlopt work well with plugins, it probably should).
I guess the fix is to add ocamlbytecomp wherever ocamloptcomp is required.
> As a workaround, you may be able to link to the compplugin module
> separately, it is installed in the $(ocamlfind query compiler-libs)
> directory.
Compplugin depends on Compdynlink (which depends on many modules in
ocamlbytecomp.cma); it cannot simply be linked separately, I think.
-- Alain
prev parent reply other threads:[~2016-11-07 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 20:10 Christoph Höger
2016-11-07 20:30 ` Gabriel Scherer
2016-11-07 20:46 ` Christoph Höger
2016-11-07 21:21 ` Gabriel Scherer
2016-11-08 8:28 ` Jeremie Dimino
2016-11-07 22:04 ` Alain Frisch [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=01907fd4-be1f-351e-d5a0-0a644c29eb9d@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=christoph.hoeger@tu-berlin.de \
--cc=gabriel.scherer@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;
as well as URLs for NNTP newsgroup(s).